I got one of these things and put it in my sock as the Apple store clerk said he did with his. I ran about five miles and it tracked me for a total 1.5. Now I understand how it works, and that it needs to be as parallel as possible to the bottom of the shoe. Easy enough.
My new concern is that I run a lot of intense hills. Think Griffith Park in LA, or Buena Vista Park in SF. I can't seem to find much written about how running up and down really steep hills for the majority of my run might affect mileage tracking. And how I should go about calibrating the inconsistent pace.
The whole line-up consists of the $60 Amps in-ears and $100 Tracks on-ear headphones, which both also come in slightly souped-up and pricier HD variations at $100 and $130, respectively.
The most commented posts on Engadget over the past 24 hours.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
I got one of these things and put it in my sock as the Apple store clerk said he did with his. I ran about five miles and it tracked me for a total 1.5. Now I understand how it works, and that it needs to be as parallel as possible to the bottom of the shoe. Easy enough.
My new concern is that I run a lot of intense hills. Think Griffith Park in LA, or Buena Vista Park in SF. I can't seem to find much written about how running up and down really steep hills for the majority of my run might affect mileage tracking. And how I should go about calibrating the inconsistent pace.
Anyone have feedback on this? Thanks!