02-10-2016 00:58
02-10-2016 00:58
02-10-2016 07:31 - edited 02-10-2016 07:32
02-10-2016 07:31 - edited 02-10-2016 07:32
I've found that tucking some cloth under the strap (buckle side) helps keep it in place - and tight without pinching - during weight training (and running). (As an aside, heart rate during weight training is a generally meaningless data point. Moderate weight training is only worth 3 METs. Less than a leasurly bike ride.)
Yes, these suggestions (tighter, higher) suck, they aren't foolproof, and they shouldn't be necessary of the tracker performed as we expect it to. Then again, I have to really tighten my running shoes at the start of run because they loosen up after a few miles, so why would a watch be any different?
As to the GPS, I am lucky to have no issues. Oh, what it shows in the Dashboard or the phone App is complete bollocks, so I don't even look at that any more. But when I look at the actual TCX file, compare that data with the actual route I have mapped, it is as accurate as my Android phone's GPS.
02-10-2016 12:50
02-10-2016 12:50
@Halset wrote:
Also in the gym the HR noticeabily runs at 50% of the true reading when doing any upper body work, I'll be running at 140bpm then wedge a set on the bench and it drops like a stone to 70bpm then when switch back to interval running 140bpm.
Yes, both Surge and Apple Watch will drop to 60-80bpm when I bench press or do other weight lifting. The Surge is a complete fail, however with Apple Watch I can pair it to a Bluetooth chest strap or upper arm (Scosche Rhythm+) heart rate monitor and then get accurate HRM data!
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze