Difference between revisions of "Garmin 225"
User:Fellrnr (User talk:Fellrnr | contribs) |
User:Fellrnr (User talk:Fellrnr | contribs) m |
||
(5 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{DISPLAYTITLE:Garmin 225 Review}} | {{DISPLAYTITLE:Garmin 225 Review}} | ||
− | + | [[File:Garmin 225-top.JPG|thumb|right|300px|The {{Garmin 225}}, showing the display of Heart Rate from its Optical Heart Rate Sensor.]] | |
+ | The big difference between the 225 and the [[Garmin 620]] is the addition of [[Optical Heart Rate Monitoring]] (OHRM). I've found that OHRM is not ready for real world usage. I'm also a little disappointed in the way Garmin has crippled the 225's software compared with the 620. The older 225 doesn't have Garmin's [[Connect IQ]] which is another significant shortcoming, and I'd argue it should be a major factor in your choice of watches. For a more fundamental look, there are four basic questions: | ||
* '''How far did I run?''' This is the most basic question, and the 225 has rather poor GPS accuracy, so its estimate of how far you've run needs to be treated with a quite a bit of caution. | * '''How far did I run?''' This is the most basic question, and the 225 has rather poor GPS accuracy, so its estimate of how far you've run needs to be treated with a quite a bit of caution. | ||
* '''How fast am I running?''' Knowing how fast you're running can be a nice to know, or it can be vital for your training or race performance. Because of the nature of GPS, watches that rely on GPS signal alone tend to have serious problems with current pace. Without the ability to display current [[Pace From A Footpod]] while getting all other data from GPS, the 225 can't answer this question. The poor GPS accuracy exacerbates this issue, and I've seen the pace estimate wildly wrong on the 225. The 225 would be my top pick for marathon runners, but I firmly believe that this is a killer feature, as accurate pacing is essential for a good marathon performance. (I've some slight hope that Garmin will add this feature in with a firmware update, as they have to a number of their newer watches.) | * '''How fast am I running?''' Knowing how fast you're running can be a nice to know, or it can be vital for your training or race performance. Because of the nature of GPS, watches that rely on GPS signal alone tend to have serious problems with current pace. Without the ability to display current [[Pace From A Footpod]] while getting all other data from GPS, the 225 can't answer this question. The poor GPS accuracy exacerbates this issue, and I've seen the pace estimate wildly wrong on the 225. The 225 would be my top pick for marathon runners, but I firmly believe that this is a killer feature, as accurate pacing is essential for a good marathon performance. (I've some slight hope that Garmin will add this feature in with a firmware update, as they have to a number of their newer watches.) | ||
Line 6: | Line 7: | ||
* '''What's my cadence? '''[[Cadence]]''' '''is one of the most critical and often overlooked aspects of running. If you get your Cadence right, many other things naturally fall into place. There is support for Cadence from the internal accelerometer, though I find that's not as accurate as the [[Footpod]] which it supports. | * '''What's my cadence? '''[[Cadence]]''' '''is one of the most critical and often overlooked aspects of running. If you get your Cadence right, many other things naturally fall into place. There is support for Cadence from the internal accelerometer, though I find that's not as accurate as the [[Footpod]] which it supports. | ||
The 225 is not a good choice for ultrarunners, as its battery life is too short. See [[Best Running Watch#Watches for Ultrarunning| Watches for Ultrarunning]] for more details. (Turning off the optical heart rate monitor only increases the battery life a couple of hours.) | The 225 is not a good choice for ultrarunners, as its battery life is too short. See [[Best Running Watch#Watches for Ultrarunning| Watches for Ultrarunning]] for more details. (Turning off the optical heart rate monitor only increases the battery life a couple of hours.) | ||
− | + | {{BuyAmazon|AZID=B00XKRWTUE|AZN=Garmin 225}} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | | | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=Garmin 225 Pros= | =Garmin 225 Pros= | ||
* The GPS accuracy of the 225 is reasonable. It's not as good as the [[Polar V800]] or some of the other watches, but it's okay for most usage. Not surprisingly, the accuracy is about the same as the similar [[Garmin 620]]. | * The GPS accuracy of the 225 is reasonable. It's not as good as the [[Polar V800]] or some of the other watches, but it's okay for most usage. Not surprisingly, the accuracy is about the same as the similar [[Garmin 620]]. | ||
Line 36: | Line 15: | ||
* The 225 has some basic activity monitoring built in, which is not as good as the [[Basis Activity Tracker]] but it's nice to have. | * The 225 has some basic activity monitoring built in, which is not as good as the [[Basis Activity Tracker]] but it's nice to have. | ||
=Garmin 225 Cons= | =Garmin 225 Cons= | ||
− | * The Optical HRM is not suitable for real world usage, but it's on a par with other systems. | + | * The Optical HRM is not suitable for real world usage, but it's on a par with other systems. See [[Optical Heart Rate Monitoring]] for more details. |
* A lot of the missing features from the [[Garmin 620]] are from Garmin crippling the software rather than hardware limitations. I always like to see a company make the best product they can for a given price point, rather than using software crippling. Things like only displaying 3 data fields, or limiting the number of screens of data on the 225 is needlessly annoying. It's particularly bad when you want the optical heart rate monitoring, and can't get the advanced features on the 620. | * A lot of the missing features from the [[Garmin 620]] are from Garmin crippling the software rather than hardware limitations. I always like to see a company make the best product they can for a given price point, rather than using software crippling. Things like only displaying 3 data fields, or limiting the number of screens of data on the 225 is needlessly annoying. It's particularly bad when you want the optical heart rate monitoring, and can't get the advanced features on the 620. | ||
* There is no way of displaying your current pace from the [[Footpod]] while using GPS for overall distance and course. While the 225 now has good GPS accuracy, it is not sufficient to give useful current pace information. For situations where pacing is critical, such as running a marathon, a Footpod works better. (Earlier versions of the firmware would always display the pace and distance from the Footpod when it's connected, but this was fixed in a recent update.) | * There is no way of displaying your current pace from the [[Footpod]] while using GPS for overall distance and course. While the 225 now has good GPS accuracy, it is not sufficient to give useful current pace information. For situations where pacing is critical, such as running a marathon, a Footpod works better. (Earlier versions of the firmware would always display the pace and distance from the Footpod when it's connected, but this was fixed in a recent update.) | ||
Line 45: | Line 24: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- valign="top" | |- valign="top" | ||
− | |[[File:BridgeGarmin 225.jpg|none|thumb|x300px| You can see the 225 has rather mediocre accuracy, and is rather worse than the similar [[Garmin 620]]. It does badly around the twisty section, cutting the corners too much due to smoothing. It does a little better with the sharp turn seen on the right side of the diagram. It gets a little lost going under the bridge on occasion, but that's not too much of an issue. The lap markers in blue are more widely dispersed than they would be with a better device. (This diagram has tracks color coded with green indicating good accuracy through to | + | |[[File:BridgeGarmin 225.jpg|none|thumb|x300px| You can see the 225 has rather mediocre accuracy, and is rather worse than the similar [[Garmin 620]]. It does badly around the twisty section, cutting the corners too much due to smoothing. It does a little better with the sharp turn seen on the right side of the diagram. It gets a little lost going under the bridge on occasion, but that's not too much of an issue. The lap markers in blue are more widely dispersed than they would be with a better device. (This diagram has tracks color coded with green indicating good accuracy through to red indicating poor accuracy, and the lap markers as blue dots.)]] |
|- valign="top" | |- valign="top" | ||
− | |[[File:AccuracyGarmin 225.jpg|none|thumb|x300px| This close up section of a zigzag shows the 225 tracking okay most of the time, but a disturbing number of the tracks are poor. (This diagram has tracks color coded with green indicating good accuracy through to | + | |[[File:AccuracyGarmin 225.jpg|none|thumb|x300px| This close up section of a zigzag shows the 225 tracking okay most of the time, but a disturbing number of the tracks are poor. (This diagram has tracks color coded with green indicating good accuracy through to red indicating poor accuracy, and the lap markers as blue dots.)]] |
|- valign="top" | |- valign="top" | ||
|[[File:ZigZagGarmin 225.jpg|none|thumb|x300px| Here you can see the 225 displaying the typical GPS behavior with the tracks that have the green lines shifted slightly down and to the left, blue up and to the right. This is less marked that other devices, but you can see the pattern. You can also see the lap markers shifted based on direction. (This image has the tracks color-coded for direction, with green coming from the right, blue from the left.)]] | |[[File:ZigZagGarmin 225.jpg|none|thumb|x300px| Here you can see the 225 displaying the typical GPS behavior with the tracks that have the green lines shifted slightly down and to the left, blue up and to the right. This is less marked that other devices, but you can see the pattern. You can also see the lap markers shifted based on direction. (This image has the tracks color-coded for direction, with green coming from the right, blue from the left.)]] | ||
Line 64: | Line 43: | ||
* '''Alerts'''. Some watches will alert you when a metric is out of range. The alert for [[Cadence]] is really useful and one of my favorite features. | * '''Alerts'''. Some watches will alert you when a metric is out of range. The alert for [[Cadence]] is really useful and one of my favorite features. | ||
* '''Web Configuration'''. Some watches allow you to setup the configuration via a web site, and then download your changes. This is vastly easier than fiddling with the watch. | * '''Web Configuration'''. Some watches allow you to setup the configuration via a web site, and then download your changes. This is vastly easier than fiddling with the watch. | ||
− | |||
=Visual Comparison= | =Visual Comparison= | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 91: | Line 69: | ||
|[[File:Polar V800-side.JPG|none|thumb|150px|Polar V800 side]] | |[[File:Polar V800-side.JPG|none|thumb|150px|Polar V800 side]] | ||
|} | |} | ||
+ | =Teardown= | ||
+ | There's a nice teardown of the Garmin 220 (the 225 without the OHRM) on [http://www.microcontrollertips.com/teardown-garmin-forerunner-220-sport-watch-heart-monitor/ microcontrollertips.com]. | ||
=Comparison Table= | =Comparison Table= | ||
{{:Best Running Watch-table}} | {{:Best Running Watch-table}} |
Latest revision as of 04:57, 11 August 2017
The big difference between the 225 and the Garmin 620 is the addition of Optical Heart Rate Monitoring (OHRM). I've found that OHRM is not ready for real world usage. I'm also a little disappointed in the way Garmin has crippled the 225's software compared with the 620. The older 225 doesn't have Garmin's Connect IQ which is another significant shortcoming, and I'd argue it should be a major factor in your choice of watches. For a more fundamental look, there are four basic questions:
- How far did I run? This is the most basic question, and the 225 has rather poor GPS accuracy, so its estimate of how far you've run needs to be treated with a quite a bit of caution.
- How fast am I running? Knowing how fast you're running can be a nice to know, or it can be vital for your training or race performance. Because of the nature of GPS, watches that rely on GPS signal alone tend to have serious problems with current pace. Without the ability to display current Pace From A Footpod while getting all other data from GPS, the 225 can't answer this question. The poor GPS accuracy exacerbates this issue, and I've seen the pace estimate wildly wrong on the 225. The 225 would be my top pick for marathon runners, but I firmly believe that this is a killer feature, as accurate pacing is essential for a good marathon performance. (I've some slight hope that Garmin will add this feature in with a firmware update, as they have to a number of their newer watches.)
- Where am I? The 225 has no navigation features. If you're lost, the 225 won't be much help.
- What's my cadence? Cadence is one of the most critical and often overlooked aspects of running. If you get your Cadence right, many other things naturally fall into place. There is support for Cadence from the internal accelerometer, though I find that's not as accurate as the Footpod which it supports.
The 225 is not a good choice for ultrarunners, as its battery life is too short. See Watches for Ultrarunning for more details. (Turning off the optical heart rate monitor only increases the battery life a couple of hours.)
This review was made possible by readers like you buying products via my links. I buy all the products I review through normal retail channels, which allows me to create unbiased reviews free from the influence of reciprocity, or the need to keep vendors happy. It also ensures I don't get "reviewer specials" that are better than the retail versions.
|
Contents
1 Garmin 225 Pros
- The GPS accuracy of the 225 is reasonable. It's not as good as the Polar V800 or some of the other watches, but it's okay for most usage. Not surprisingly, the accuracy is about the same as the similar Garmin 620.
- The 225 is small and light, but the display is quite legible for its size. The display is color, but really this isn't much use on the 225. There is a display of HR with a color indicator of zone, but that's more of a novelty than a useful feature.
- The 225 will cache the locations of the GPS satellites for the next few days, makes for faster satellite lock. However, if you've not connected the 225 to the internet for a few days, the 225 can be painfully slow to acquire a lock.
- I like the small size of the 225, which feels more like a watch than a dive computer or 80's calculator watch.
- The 225 has some basic activity monitoring built in, which is not as good as the Basis Activity Tracker but it's nice to have.
2 Garmin 225 Cons
- The Optical HRM is not suitable for real world usage, but it's on a par with other systems. See Optical Heart Rate Monitoring for more details.
- A lot of the missing features from the Garmin 620 are from Garmin crippling the software rather than hardware limitations. I always like to see a company make the best product they can for a given price point, rather than using software crippling. Things like only displaying 3 data fields, or limiting the number of screens of data on the 225 is needlessly annoying. It's particularly bad when you want the optical heart rate monitoring, and can't get the advanced features on the 620.
- There is no way of displaying your current pace from the Footpod while using GPS for overall distance and course. While the 225 now has good GPS accuracy, it is not sufficient to give useful current pace information. For situations where pacing is critical, such as running a marathon, a Footpod works better. (Earlier versions of the firmware would always display the pace and distance from the Footpod when it's connected, but this was fixed in a recent update.)
- The 225 includes an internal accelerometer to give you an idea of pace and distance while running on a treadmill without a footpod, but I found it was too far out to be of any use. A lot will depend on your running style and how you use a treadmill.
- The battery life is short for ultramarathons, but it is fine for the most runners.
3 GPS Accuracy
The Garmin 225 does rather poorly for GPS accuracy, and rather worse than the similar Garmin 620. I was expecting it to be using the same chipset and antenna as the 620, which I would expect to give similar GPS performance. It's hard to be sure of the underlying chipset without disassembly, but the problem could also be due to a change in the antenna due to the extra optical HRM.
4 What's Missing
While I don't consider these missing features as 'cons', it's worth understanding the features that are missing compared with other watches.
- Altimeter. GPS is far less accurate vertically than horizontally, so a barometric altimeter can provide a much better idea of your ascent and descent. It can also be useful for navigation if you're ascending or descending a mountain. In some races I've been far more interested in how much ascent is left rather than the distance to the top.
- Navigation. The navigation capabilities are useful if there is a risk of getting lost. I've made good use of this feature when running in an unfamiliar city, or when running remote trails. (On a screen this small it might not be much use anyway.)
- Downloadable Apps. Smart watches have got is used to the idea of a device that can be extended with new functionality, and this concept is being introduced to running watches.
- Extended battery life. Some porches can extend the battery life by turning the GPS reception off for short periods. This can dramatically reduce GPS accuracy, but it's a useful trade-off for some ultramarathons.
- Graphs. Instead of simply displaying a numeric value for things like heart rate, some watches will display a graph of the value over time, giving you a sense of how things are progressing.
- Training Effect. The Firstbeat Training Effect gives you a sense of how hard each workout is, and this sometimes includes the time for recovery.
- Graphs. Instead of simply displaying a numeric value for things like heart rate, some watches will display a graph of the value over time, giving you a sense of how things are progressing.
- WiFi/Bluetooth Uploads. While the automatic upload of workouts via WiFi or Bluetooth to a Smartphone is nice, the upload will typically only go to the manufacturer's web site.
- Running Dynamics. Some of the newer Garmin watches can show and record Vertical Oscillation (VO) and Ground Contact Time (GCT).
- Alerts. Some watches will alert you when a metric is out of range. The alert for Cadence is really useful and one of my favorite features.
- Web Configuration. Some watches allow you to setup the configuration via a web site, and then download your changes. This is vastly easier than fiddling with the watch.
5 Visual Comparison
6 Teardown
There's a nice teardown of the Garmin 220 (the 225 without the OHRM) on microcontrollertips.com.
7 Comparison Table
I evaluate running watches in three distinct ways. Firstly, you can use a watch on its own, without any kind of Footpod. This is probably the most common way runners use their watch, but you miss out on a lot. The second rating is with a standard Footpod that is available quite cheaply. These Footpod's can be reasonably accurate once the calibrated, but calibration is a little tedious. The final evaluation is with the Stryd Footpod, which is vastly more accurate than any other type of Footpod, or and more accurate than GPS. The table below looks at the score, and the value for money of each watch for each of the three conditions. (I’ve also tested the Apple Watch 3, but I’ve not included it in these tables as it’s not really a running watch.)
Review | With Stryd Score | With Stryd Value for money | With Footpod Score | With Footpod Value for money | Without Footpod Score | Without Footpod Value for money | Price at Amazon.com |
---|---|---|---|---|---|---|---|
Garmin Epix Review | 47 | 4.5 | 31 | 3.9 | 23 | 3.4 | Error: Could not parse data from Amazon! |
Garmin Fenix 5X Review | 47 | 2.9 | 32 | 2.3 | 24 | 1.9 | Error: Could not parse data from Amazon! |
Garmin Fenix 3 Review | 45 | 3.8 | 28 | 3.1 | 24 | 3 | Error: Could not parse data from Amazon! |
Garmin 935 Review | 45 | 3.6 | 30 | 3 | 22 | 2.4 | Error: Could not parse data from Amazon! |
Garmin Vivoactive HR Review | 40 | 4.9 | 21 | 3.8 | 17 | 3.8 | Error: Could not parse data from Amazon! |
Garmin 920XT Review | 39 | 4.4 | 30 | 4.7 | 24 | 4.5 | Error: Could not parse data from Amazon! |
Suunto Spartan Ultra Review | 37 | 2.6 | 27 | 2.3 | 23 | 2.1 | Error: Could not parse data from Amazon! |
Garmin Vivoactive 3 Review | 36 | 4 | 19 | 2.9 | 15 | 2.8 | Error: Could not parse data from Amazon! |
Garmin Vivoactive Review | 34 | 5.1 | 14 | 3.4 | 10 | 3.3 | Error: Could not parse data from Amazon! |
Suunto Spartan Trainer Review | 34 | 3.9 | 23 | 3.7 | 18 | 3.4 | Error: Could not parse data from Amazon! |
Polar V800 Review | 33 | 2.8 | 26 | 2.8 | 22 | 2.7 | Error: Could not parse data from Amazon! |
Suunto Ambit2 Review | 32 | 3.9 | 25 | 4.3 | 21 | 4.5 | Error: Could not parse data from Amazon! |
Suunto Ambit3 Peak Review | 32 | 3.4 | 29 | 4.1 | 25 | 4.2 | Error: Could not parse data from Amazon! |
Garmin Fenix 2 Review | 31 | 2.9 | 22 | 2.7 | 18 | 2.5 | Error: Could not parse data from Amazon! |
Suunto Ambit3 Run Review | 30 | 4 | 27 | 5.5 | 23 | 5.9 | Error: Could not parse data from Amazon! |
Suunto Ambit2 R Review | 30 | 3.5 | 23 | 3.8 | 19 | 3.8 | Error: Could not parse data from Amazon! |
Garmin 235 Review | 28 | 2.9 | 20 | 2.8 | 12 | 2 | Error: Could not parse data from Amazon! |
Garmin 620 Review | 27 | 3.8 | 24 | 5.1 | 20 | 5.6 | Error: Could not parse data from Amazon! |
Garmin 910XT Review | 26 | 3.9 | 26 | 6.1 | 21 | 6.7 | Error: Could not parse data from Amazon! |
Garmin 310XT Review | 25 | 4.6 | 24 | 8.3 | 18 | 10 | Error: Could not parse data from Amazon! |
Polar M400 Review | 25 | 4.3 | 15 | 4.5 | 11 | 4.9 | Error: Could not parse data from Amazon! |
Garmin 225 Review | 25 | 3.8 | 13 | 3.1 | 9 | 2.9 | Error: Could not parse data from Amazon! |
TomTom Cardio Runner Review | 25 | 3.3 | 10 | 2 | 10 | 2.5 | Error: Could not parse data from Amazon! |
Polar M430 Review | 25 | 3.2 | 15 | 2.9 | 11 | 2.7 | Error: Could not parse data from Amazon! |
Garmin 610 Review | 24 | 3.3 | 20 | 4.3 | 14 | 3.9 | Error: Could not parse data from Amazon! |
Leikr Review | 10 | 1 | 20 | 2.5 | 14 | 2 | Leikr ($380) |
Epson SF-510 Review | 4 | 0.7 | 6 | 2 | 6 | 3 | Error: Could not parse data from Amazon! |
Epson SF-810 Review | 4 | 0.6 | 6 | 1.6 | 6 | 2.3 | Error: Could not parse data from Amazon! |
Garmin 10 Review | 2 | 0.3 | 2 | 0.6 | 2 | 0.9 | Error: Could not parse data from Amazon! |
The score is the sum of how well each watch can answer the four basic questions (how far, how fast, where are you, what's your cadence), plus some bonus points.
- The "How far you've run" will be based on GPS only for "without Footpod" and "with Standard Footpod", but based on Stryd if supported in the "with Stryd Footpod" table..
- How fast you're running assumes you're using a Footpod if it's supported, otherwise the rating is 0-2 based on GPS accuracy.
- The "Where are you?" is based on various navigation features such as back to start, breadcrumbs, and preloaded maps. For some watches, you have to turn GPS off to get the benefit of Stryd, so those watches have worse "where are you scores" with Stryd than without.
- The cadence score uses 1 point for an internal cadence sensor, 2 points for footpod support, 1 point for support from chest strap cadence, and 1 point for cadence alerts.
- I give 1-2 bonus points for application support, 1-2 bonus points for data upload, 1-2 bonus points for Optical Heart Rate Monitoring, and 0-1 bonus points for battery life.
- Value for money is the score divided by the price (at the time I last updated the table.) Your needs may be different, so you might weight the different aspects of the watches differently, or be basing your decision on different criteria totally. Hopefully this table will give you a good starting point for your decision.
7.1 Score Breakdown without a Footpod
Review | Score | Value for money6 | How far did you run?1 |
How fast are you running?2 |
Where are you?3 |
What's your cadence?4 |
Bonus Points5 | class="unsortable" |
Price at Amazon.com |
---|---|---|---|---|---|---|---|---|
Suunto Ambit3 Peak Review | 25 | 4.2 | 8 | 3 | 6 | 2 | 6 | Error: Could not parse data from Amazon! |
Garmin 920XT Review | 24 | 4.5 | 1 | 2 | 7 | 6 | 8 | Error: Could not parse data from Amazon! |
Garmin Fenix 3 Review | 24 | 3 | 2 | 1 | 7 | 6 | 8 | Error: Could not parse data from Amazon! |
Garmin Fenix 5X Review | 24 | 1.9 | 1 | 0 | 9 | 6 | 8 | Error: Could not parse data from Amazon! |
Suunto Ambit3 Run Review | 23 | 5.9 | 8 | 3 | 5 | 2 | 5 | Error: Could not parse data from Amazon! |
Garmin Epix Review | 23 | 3.4 | 0 | 0 | 9 | 6 | 8 | Error: Could not parse data from Amazon! |
Suunto Spartan Ultra Review | 23 | 2.1 | 8 | 2 | 6 | 2 | 5 | Error: Could not parse data from Amazon! |
Polar V800 Review | 22 | 2.7 | 9 | 4 | 3 | 2 | 4 | Error: Could not parse data from Amazon! |
Garmin 935 Review | 22 | 2.4 | 1 | 0 | 7 | 6 | 8 | Error: Could not parse data from Amazon! |
Garmin 910XT Review | 21 | 6.7 | 5 | 3 | 6 | 2 | 5 | Error: Could not parse data from Amazon! |
Suunto Ambit2 Review | 21 | 4.5 | 4 | 3 | 6 | 2 | 6 | Error: Could not parse data from Amazon! |
Garmin 620 Review | 20 | 5.6 | 3 | 2 | 2 | 6 | 7 | Error: Could not parse data from Amazon! |
Suunto Ambit2 R Review | 19 | 3.8 | 4 | 3 | 5 | 2 | 5 | Error: Could not parse data from Amazon! |
Garmin 310XT Review | 18 | 10 | 7 | 2 | 4 | 0 | 5 | Error: Could not parse data from Amazon! |
Suunto Spartan Trainer Review | 18 | 3.4 | 5 | 3 | 4 | 2 | 4 | Error: Could not parse data from Amazon! |
Garmin Fenix 2 Review | 18 | 2.5 | 1 | 0 | 6 | 6 | 5 | Error: Could not parse data from Amazon! |
Garmin Vivoactive HR Review | 17 | 3.8 | 0 | 0 | 2 | 6 | 9 | Error: Could not parse data from Amazon! |
Garmin Vivoactive 3 Review | 15 | 2.8 | 0 | 0 | 4 | 4 | 7 | Error: Could not parse data from Amazon! |
Garmin 610 Review | 14 | 3.9 | 3 | 2 | 3 | 2 | 4 | Error: Could not parse data from Amazon! |
Leikr Review | 14 | 2 | 5 | 2 | 4 | 0 | 3 | Leikr ($380) |
Garmin 235 Review | 12 | 2 | 0 | 0 | 2 | 2 | 8 | Error: Could not parse data from Amazon! |
Polar M400 Review | 11 | 4.9 | 3 | 1 | 1 | 2 | 4 | Error: Could not parse data from Amazon! |
Polar M430 Review | 11 | 2.7 | 3 | 1 | 1 | 2 | 4 | Error: Could not parse data from Amazon! |
Garmin Vivoactive Review | 10 | 3.3 | 0 | 0 | 0 | 6 | 4 | Error: Could not parse data from Amazon! |
TomTom Cardio Runner Review | 10 | 2.5 | 2 | 1 | 0 | 2 | 5 | Error: Could not parse data from Amazon! |
Garmin 225 Review | 9 | 2.9 | 1 | 1 | 0 | 2 | 5 | Error: Could not parse data from Amazon! |
Epson SF-510 Review | 6 | 3 | 0 | 0 | 0 | 2 | 4 | Error: Could not parse data from Amazon! |
Epson SF-810 Review | 6 | 2.3 | 1 | 0 | 0 | 2 | 3 | Error: Could not parse data from Amazon! |
Garmin 10 Review | 2 | 0.9 | 0 | 0 | 0 | 0 | 2 | Error: Could not parse data from Amazon! |
7.2 Score Breakdown with a Standard Footpod
Review | Score | Value for money6 | How far did you run?1 |
How fast are you running?2 |
Where are you?3 |
What's your cadence?4 |
Bonus Points5 | class="unsortable" |
Price at Amazon.com |
---|---|---|---|---|---|---|---|---|
Garmin Fenix 5X Review | 32 | 2.3 | 1 | 4 | 9 | 10 | 8 | Error: Could not parse data from Amazon! |
Garmin Epix Review | 31 | 3.9 | 0 | 4 | 9 | 10 | 8 | Error: Could not parse data from Amazon! |
Garmin 920XT Review | 30 | 4.7 | 1 | 4 | 7 | 10 | 8 | Error: Could not parse data from Amazon! |
Garmin 935 Review | 30 | 3 | 1 | 4 | 7 | 10 | 8 | Error: Could not parse data from Amazon! |
Suunto Ambit3 Peak Review | 29 | 4.1 | 8 | 3 | 6 | 6 | 6 | Error: Could not parse data from Amazon! |
Garmin Fenix 3 Review | 28 | 3.1 | 2 | 1 | 7 | 10 | 8 | Error: Could not parse data from Amazon! |
Suunto Ambit3 Run Review | 27 | 5.5 | 8 | 3 | 5 | 6 | 5 | Error: Could not parse data from Amazon! |
Suunto Spartan Ultra Review | 27 | 2.3 | 8 | 2 | 6 | 6 | 5 | Error: Could not parse data from Amazon! |
Garmin 910XT Review | 26 | 6.1 | 5 | 4 | 6 | 6 | 5 | Error: Could not parse data from Amazon! |
Polar V800 Review | 26 | 2.8 | 9 | 4 | 3 | 6 | 4 | Error: Could not parse data from Amazon! |
Suunto Ambit2 Review | 25 | 4.3 | 4 | 3 | 6 | 6 | 6 | Error: Could not parse data from Amazon! |
Garmin 310XT Review | 24 | 8.3 | 7 | 4 | 4 | 4 | 5 | Error: Could not parse data from Amazon! |
Garmin 620 Review | 24 | 5.1 | 3 | 2 | 2 | 10 | 7 | Error: Could not parse data from Amazon! |
Suunto Ambit2 R Review | 23 | 3.8 | 4 | 3 | 5 | 6 | 5 | Error: Could not parse data from Amazon! |
Suunto Spartan Trainer Review | 23 | 3.7 | 5 | 4 | 4 | 6 | 4 | Error: Could not parse data from Amazon! |
Garmin Fenix 2 Review | 22 | 2.7 | 1 | 0 | 6 | 10 | 5 | Error: Could not parse data from Amazon! |
Garmin Vivoactive HR Review | 21 | 3.8 | 0 | 0 | 2 | 10 | 9 | Error: Could not parse data from Amazon! |
Garmin 610 Review | 20 | 4.3 | 3 | 4 | 3 | 6 | 4 | Error: Could not parse data from Amazon! |
Garmin 235 Review | 20 | 2.8 | 0 | 4 | 2 | 6 | 8 | Error: Could not parse data from Amazon! |
Leikr Review | 20 | 2.5 | 5 | 4 | 4 | 4 | 3 | Leikr ($380) |
Garmin Vivoactive 3 Review | 19 | 2.9 | 0 | 0 | 4 | 8 | 7 | Error: Could not parse data from Amazon! |
Polar M400 Review | 15 | 4.5 | 3 | 1 | 1 | 6 | 4 | Error: Could not parse data from Amazon! |
Polar M430 Review | 15 | 2.9 | 3 | 1 | 1 | 6 | 4 | Error: Could not parse data from Amazon! |
Garmin Vivoactive Review | 14 | 3.4 | 0 | 0 | 0 | 10 | 4 | Error: Could not parse data from Amazon! |
Garmin 225 Review | 13 | 3.1 | 1 | 1 | 0 | 6 | 5 | Error: Could not parse data from Amazon! |
TomTom Cardio Runner Review | 10 | 2 | 2 | 1 | 0 | 2 | 5 | Error: Could not parse data from Amazon! |
Epson SF-510 Review | 6 | 2 | 0 | 0 | 0 | 2 | 4 | Error: Could not parse data from Amazon! |
Epson SF-810 Review | 6 | 1.6 | 1 | 0 | 0 | 2 | 3 | Error: Could not parse data from Amazon! |
Garmin 10 Review | 2 | 0.6 | 0 | 0 | 0 | 0 | 2 | Error: Could not parse data from Amazon! |
7.3 Score Breakdown with a Stryd Footpod
Review | Score | Value for money6 | How far did you run?1 |
How fast are you running?2 |
Where are you?3 |
What's your cadence?4 |
Bonus Points5 | class="unsortable" |
Price at Amazon.com |
---|---|---|---|---|---|---|---|---|
Garmin Epix Review | 47 | 4.5 | 10 | 10 | 9 | 10 | 8 | Error: Could not parse data from Amazon! |
Garmin Fenix 5X Review | 47 | 2.9 | 10 | 10 | 9 | 10 | 8 | Error: Could not parse data from Amazon! |
Garmin Fenix 3 Review | 45 | 3.8 | 10 | 10 | 7 | 10 | 8 | Error: Could not parse data from Amazon! |
Garmin 935 Review | 45 | 3.6 | 10 | 10 | 7 | 10 | 8 | Error: Could not parse data from Amazon! |
Garmin Vivoactive HR Review | 40 | 4.9 | 10 | 10 | 1 | 10 | 9 | Error: Could not parse data from Amazon! |
Garmin 920XT Review | 39 | 4.4 | 10 | 10 | 1 | 10 | 8 | Error: Could not parse data from Amazon! |
Suunto Spartan Ultra Review | 37 | 2.6 | 10 | 10 | 6 | 6 | 5 | Error: Could not parse data from Amazon! |
Garmin Vivoactive 3 Review | 36 | 4 | 10 | 10 | 1 | 8 | 7 | Error: Could not parse data from Amazon! |
Garmin Vivoactive Review | 34 | 5.1 | 10 | 10 | 0 | 10 | 4 | Error: Could not parse data from Amazon! |
Suunto Spartan Trainer Review | 34 | 3.9 | 10 | 10 | 4 | 6 | 4 | Error: Could not parse data from Amazon! |
Polar V800 Review | 33 | 2.8 | 10 | 10 | 3 | 6 | 4 | Error: Could not parse data from Amazon! |
Suunto Ambit2 Review | 32 | 3.9 | 10 | 10 | 6 | 0 | 6 | Error: Could not parse data from Amazon! |
Suunto Ambit3 Peak Review | 32 | 3.4 | 10 | 10 | 6 | 0 | 6 | Error: Could not parse data from Amazon! |
Garmin Fenix 2 Review | 31 | 2.9 | 10 | 10 | 6 | 0 | 5 | Error: Could not parse data from Amazon! |
Suunto Ambit3 Run Review | 30 | 4 | 10 | 10 | 5 | 0 | 5 | Error: Could not parse data from Amazon! |
Suunto Ambit2 R Review | 30 | 3.5 | 10 | 10 | 5 | 0 | 5 | Error: Could not parse data from Amazon! |
Garmin 235 Review | 28 | 2.9 | 10 | 10 | 0 | 0 | 8 | Error: Could not parse data from Amazon! |
Garmin 620 Review | 27 | 3.8 | 10 | 10 | 0 | 0 | 7 | Error: Could not parse data from Amazon! |
Garmin 910XT Review | 26 | 3.9 | 10 | 10 | 1 | 0 | 5 | Error: Could not parse data from Amazon! |
Garmin 310XT Review | 25 | 4.6 | 10 | 10 | 0 | 0 | 5 | Error: Could not parse data from Amazon! |
Polar M400 Review | 25 | 4.3 | 10 | 10 | 1 | 0 | 4 | Error: Could not parse data from Amazon! |
Garmin 225 Review | 25 | 3.8 | 10 | 10 | 0 | 0 | 5 | Error: Could not parse data from Amazon! |
TomTom Cardio Runner Review | 25 | 3.3 | 10 | 10 | 0 | 0 | 5 | Error: Could not parse data from Amazon! |
Polar M430 Review | 25 | 3.2 | 10 | 10 | 1 | 0 | 4 | Error: Could not parse data from Amazon! |
Garmin 610 Review | 24 | 3.3 | 10 | 10 | 0 | 0 | 4 | Error: Could not parse data from Amazon! |
Leikr Review | 10 | 1 | 5 | 2 | 0 | 0 | 3 | Leikr ($380) |
Epson SF-510 Review | 4 | 0.7 | 0 | 0 | 0 | 0 | 4 | Error: Could not parse data from Amazon! |
Epson SF-810 Review | 4 | 0.6 | 1 | 0 | 0 | 0 | 3 | Error: Could not parse data from Amazon! |
Garmin 10 Review | 2 | 0.3 | 0 | 0 | 0 | 0 | 2 | Error: Could not parse data from Amazon! |
7.4 Basic Features
Review |
Released | GPS Accuracy |
Weight (oz) | Size (CM3) | Display (mm) | Resolution (Pixels) | Waterproofing | Heart Rate Monitor |
Cadence | Data Upload |
---|---|---|---|---|---|---|---|---|---|---|
Garmin Epix Review | 2015 | 6.2 | 3.0 | 48 | 29 x 21 (609mm2) | 205 x 148 (30.3K total) | Good (50m) | Yes | Internal/Footpod/Heart Rate Monitor/Alert | Yes |
Garmin Fenix 5X Review | 2017 | 5.6 | 3.5 | 36 | 30.5 (round) (731mm2) | 240 diameter (45.2K total) | Good (100m) | Yes | Internal/Footpod/Heart Rate Monitor/Alert | Yes |
Garmin Fenix 3 Review | 2015 | 6.2 | 2.9 | 33 | 30 (round) (726mm2) | 218 diameter (37.3K total) | Good (100m) | Yes | Internal/Footpod/Heart Rate Monitor/Alert | Yes |
Garmin 935 Review | 2017 | 5.6 | 1.7 | 24 | 30.5 (round) (731mm2) | 240 diameter (45.2K total) | Good (100m) | Yes | Internal/Footpod/Heart Rate Monitor/Alert | Yes |
Garmin Vivoactive HR Review | 2016 | 4.9 | 1.7 | 19 | 21 x 29 (609mm2) | 148 x 205 (30.3K total) | Good (50m) | Yes (+OHRM) | Internal/Footpod/Heart Rate Monitor/Alert | Yes |
Garmin 920XT Review | 2014 | 6.6 | 2.2 | 35 | 29 x 21 (609mm2) | 205 x 148 (30.3K total) | Good (50m) | Yes | Internal/Footpod/Heart Rate Monitor/Alert | Yes |
Garmin Vivoactive 3 Review | 2017 | 1.5 | 17 | 30.5 (round) (731mm2) | 240 diameter (45.2K total) | Good (50m) | Yes (+OHRM) | Internal/Footpod | Yes | |
Garmin Vivoactive Review | 2015 | 5.4 | 1.3 | 13 | 29 x 21 (592mm2) | 205 x 148 (30.3K total) | Good (50m) | Yes | Internal/Footpod/Heart Rate Monitor/Alert | Yes |
Suunto Spartan Trainer Review | 2017 | 7.8 | 2.0 | 25 | 24 x 23 (529mm2) | 128 diameter (12.9K total) | Good (50m) | Yes (+OHRM) | Internal/Footpod | Yes |
Suunto Ambit2 Review | 2013 | 7.6 | 3.1 | 30 | 29 (round) (661mm2) | 128 diameter (12.9K total) | Good (100m) | Yes | Internal/Footpod | Yes |
Suunto Ambit3 Peak Review | 2014 | 7.9 | 2.9 | 30 | 29 (round) (661mm2) | 128 diameter (12.9K total) | Good (100m) | Yes | Internal/Footpod | Yes |
Suunto Spartan Ultra Review | 2016 | 7.1 | 2.7 | 38 | 32 (round) (804mm2) | 320 diameter (80.4K total) | Good (100m) | Yes | Internal (Limited Footpod) | Yes |
Garmin Fenix 2 Review | 2014 | 5.7 | 3.2 | 32 | 31 (round) (755mm2) | 70 diameter (3.8K total) | Good (50m) | Yes | Internal/Footpod/Heart Rate Monitor/Alert | Yes |
Suunto Ambit3 Run Review | 2014 | 7.9 | 2.5 | 30 | 29 (round) (661mm2) | 128 x 128 (16.4K total) | Good (50m) | Yes | Internal/Footpod | Yes |
Suunto Ambit2 R Review | 2013 | 7.6 | 2.5 | 30 | 29 (round) (661mm2) | 128 diameter (12.9K total) | Good (50m) | Yes | Internal/Footpod | Yes |
Garmin 235 Review | 2015 | 4.9 | 1.5 | 19 | 31 (round) (755mm2) | 215 diameter (36.3K total) | Good (50m) | Yes (+OHRM) | Internal/Footpod | Yes |
Garmin 620 Review | 2013 | 7.1 | 1.5 | 20 | 25.4 (round) (507mm2) | 180 diameter (25.4K total) | Good (50m) | Yes | Internal/Footpod/Heart Rate Monitor/Alert | Yes |
Garmin 910XT Review | 2011 | 7.5 | 2.5 | 49 | 33 x 20 (660mm2) | 160 x 100 (16K total) | Good (50m) | Yes | Footpod/Alert | Yes |
Garmin 310XT Review | 2009 | 7.5 | 2.5 | 63 | 33 x 20 (660mm2) | 160 x 100 (16K total) | Good (50m) | Yes | Footpod | Yes |
Garmin 225 Review | 2015 | 6.2 | 1.5 | 24 | 25.4 (round) (507mm2) | 180 diameter (25.4K total) | Good (50m) | Yes (+OHRM) | Internal/Footpod | Yes |
TomTom Cardio Runner Review | 2015 | 6.0 | 2.2 | 30 | 22 x 25 (550mm2) | 144 x 168 (24.2K total) | Good (50m) | Yes (+OHRM) | Internal/Footpod | Yes |
Polar V800 Review | 2014 | 8.0 | 2.8 | 31 | 23 x 23 (529mm2) | 128 x 128 (16.4K total) | Good (30m) | Yes | Internal/Footpod | Yes |
Polar M430 Review | 2017 | 7.2 | 2.0 | 24 | 23 x 23 (529mm2) | 128 x 128 (16.4K total) | Good (50m) | Yes (+OHRM) | Internal/Footpod | Yes |
Polar M400 Review | 2014 | 6.6 | 2.0 | 24 | 23 x 23 (529mm2) | 128 x 128 (16.4K total) | Good (30m) | Yes | Internal/Footpod | Yes |
Garmin 610 Review | 2011 | 7.3 | 2.5 | 41 | 25.4 (round) (507mm2) | 128 diameter (12.9K total) | Fair (IPX7) | Yes | Footpod/Alert | Yes |
Leikr Review | 2013 | 7.3 | 2.4 | 25 | 41 x 31 (1271mm2) | 206 x 148 (76.8K total) | Fair (IPX6) | Yes | Footpod | Limited |
Epson SF-510 Review | 2015 | 4.4 | 1.7 | 24 | 28 x 22 (616mm2) | 128 x 96 (12.3K total) | Good (50m) | Yes | Limited Internal | Limited |
Epson SF-810 Review | 2015 | 5.5 | 1.8 | 28 | 28 (round) (616mm2) | 128 diameter (12.9K total) | Good (50m) | OHRM Only) | Limited Internal | Limited |
Garmin 10 Review | 2012 | 3.8 | 1.3 | 33 | 25 x 24 (600mm2) | 55 x 32 (1.8K total) | Good (50m) | No | No | Yes |
Review |
Battery Life (hr) |
Tested Battery Life (hr) |
Extended Battery Life (hr) |
Charge On The Run? | Training Effect |
HRV | GPS cache | Sensors |
---|---|---|---|---|---|---|---|---|
Garmin Epix Review | 24 | 17.6 | 50 | Yes (with USB=Garmin) | Yes | Record | Yes | Ant+ |
Garmin Fenix 5X Review | 20 | 23 | 35 | Yes, but can't be worn | Yes | Record | Yes | Bluetooth/Ant+ |
Garmin Fenix 3 Review | 20 | 22 | 50 | Yes (with USB=Garmin) | Yes | No | Yes | Ant+ |
Garmin 935 Review | 24 | 24.5 | 60 | Yes, but can't be worn | Yes | Record | Yes | Bluetooth/Ant+ |
Garmin Vivoactive HR Review | 13 | 13 | Yes (with USB=Garmin) | No | No | Yes | Ant+ | |
Garmin 920XT Review | 24 | 19 | 40 | No (terminates) | Yes | Record | Yes | Ant+ |
Garmin Vivoactive 3 Review | 13 | 13 | No | Yes | Bluetooth/Ant+ | |||
Garmin Vivoactive Review | 10 | 10 | 10 | Yes (with USB=Garmin) | No | No | Yes | Ant+ |
Suunto Spartan Trainer Review | 10 | 11 | 30 | Yes | Yes | No | Yes | Bluetooth |
Suunto Ambit2 Review | 15 | 50 | Yes | Yes | Record | Yes | Ant+ | |
Suunto Ambit3 Peak Review | 20 | 100 | Yes | Yes | Record | Yes | Bluetooth | |
Suunto Spartan Ultra Review | 18 | 17 | 26 | Yes, but can't be worn | Yes | Record | Yes | Bluetooth |
Garmin Fenix 2 Review | 15 | 50 | Yes (with USB=Garmin) | Yes | No | Yes | Ant+ | |
Suunto Ambit3 Run Review | 10 | 10.5 | 100 | Yes | Yes | Record | Yes | Bluetooth |
Suunto Ambit2 R Review | 8 | 7.3 | 25 | Yes | Yes | Record | Yes | Ant+ |
Garmin 235 Review | 11 | 11 | Yes, but no optical HR | Yes | No | Yes | Ant+ | |
Garmin 620 Review | 10 | 10 | No (resets) | Yes | Record | Yes | Ant+ | |
Garmin 910XT Review | 20 | 20 | Yes, but no display | Yes | Record | No | Ant+ | |
Garmin 310XT Review | 20 | 20 | Yes, but no display | No | No | No | Ant+ | |
Garmin 225 Review | 10 | 11 | 10 | No (resets) | No | No | Yes | Ant+ |
TomTom Cardio Runner Review | 8 | 6.3 | 8 | No (resets) | No | No | Yes | Bluetooth HR |
Polar V800 Review | 13 | 24 | 50 | No (terminates) | Yes | Display | Predictive | Bluetooth |
Polar M430 Review | 8 | 8 | 8 | No | No | No | Yes | Bluetooth |
Polar M400 Review | 8 | 8 | Yes, but can't be worn | No | No | No | Bluetooth | |
Garmin 610 Review | 8 | 8 | Yes, but no display | Yes | Record | No | Ant+ | |
Leikr Review | 5 | 6.5 | 5 | Yes, but can't be worn | No | No | Yes (few hours) | Ant+ |
Epson SF-510 Review | 30 | 30 | 30 | No | No | No | Yes (few hours) | Bluetooth HR |
Epson SF-810 Review | 20 | 26 | 20 | No | No | No | Yes (few hours) | None |
Garmin 10 Review | 5 | 5 | No | No | No | No | None |
Review |
Color Maps | Breadcrumbs | Courses | To Waypoint | Compass | Reverse course | Beeline to start | Connect IQ | Altimeter |
---|---|---|---|---|---|---|---|---|---|
Garmin Epix Review | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes |
Garmin Fenix 5X Review | Yes | Yes | Yes | Yes | Yes | Yes | No | No | Yes |
Garmin Fenix 3 Review | No | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes |
Garmin 935 Review | No | Yes | Yes | Yes | Yes | Yes | No | No | Yes |
Garmin Vivoactive HR Review | No | No | No | No | No | No | No | Yes | Yes |
Garmin 920XT Review | No | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes |
Garmin Vivoactive 3 Review | No | No | No | No | No | No | No | No | No |
Garmin Vivoactive Review | No | No | No | No | No | No | Yes | Yes | No |
Suunto Spartan Trainer Review | No | No | No | No | No | No | Yes | No | No |
Suunto Ambit2 Review | No | No | Yes | Yes | Yes | Yes | Yes | No | Yes |
Suunto Ambit3 Peak Review | No | No | Yes | Yes | Yes | Yes | Yes | No | Yes |
Suunto Spartan Ultra Review | No | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes |
Garmin Fenix 2 Review | No | Yes | Yes | Yes | Yes | Yes | No | No | Yes |
Suunto Ambit3 Run Review | No | No | Yes | Yes | Yes | Yes | Yes | No | No |
Suunto Ambit2 R Review | No | No | Yes | Yes | Yes | Yes | Yes | No | No |
Garmin 235 Review | No | No | No | No | No | No | Yes | Yes | No |
Garmin 620 Review | No | No | No | No | No | No | No | No | No |
Garmin 910XT Review | No | Yes | Yes | Yes | No | Yes | Yes | No | Yes |
Garmin 310XT Review | No | Yes | Yes | Yes | No | Yes | No | No | No |
Garmin 225 Review | No | No | No | No | No | No | No | No | No |
TomTom Cardio Runner Review | No | No | No | No | No | No | No | No | No |
Polar V800 Review | No | No | Yes | No | No | No | Yes | No | Yes |
Polar M430 Review | No | No | No | No | No | No | Yes | No | No |
Polar M400 Review | No | No | No | No | No | No | Yes | No | No |
Garmin 610 Review | No | No | Yes | Yes | No | No | Yes | No | No |
Leikr Review | Yes | Yes | Yes | No | No | No | No | No | No |
Epson SF-510 Review | No | No | No | No | No | No | No | No | No |
Epson SF-810 Review | No | No | No | No | No | No | No | No | No |
Garmin 10 Review | No | No | No | No | No | No | No | No | No |
For "navigation":
- Color Maps gives you full color maps, rather like a smart phone, with roads and paths marked out.
- Track Outline is a display of where you've run, rather like a breadcrumb trail. If there are maps, the outline is superimposed otherwise this is just the outline on its own without any context.
- Course Outline is an outline of a route that can be downloaded. I've found this useful during ultras or in unfamiliar cities where I've needed to know where to go.
- Back To Start is a simple arrow point to your starting point, so it won't help you backtrack.
- Back To Waypoint returns you to a previously marked location using a simple arrow to point.
- Compass. A magnetic compass can help you orient yourself or the map. Without a magnetic compass you have to be moving for the GPS to give you a sense of direction.
(Older Reviews: Polar RC3 GPS, Soleus 1.0, Motorola Motoactv.)