Maps are sluggish and have low update frequency
-
@Stanislav-Damjanov I see it as a benefit in running activities. With so much arm swing, it would be quite difficult to judge direction of travel if the maps are always rotating. Not to mention battery draw.
The behavior is normal and similar to how most other companies handle mapping while moving. It works as I’d expect it to.
-
@duffman19 Thank you for clarification. For me, it looks quite strange that I need to make a stop in order for compass to work. But now I know that it isn’t a bug, though I would still like option to turn compass on during movement.
-
@Egika said in Maps are sluggish and have low update frequency:
@Stanislav-Damjanov said in Maps are sluggish and have low update frequency:
Has anyone found solution for this problem? Or, at least reason why it’s happening? I experience slow map movement until I make full 360 degree rotation just like OP stated. After that map “unlocks” smoother performance, only until I start walking or breadcrumb navigation screen shows up again. It’s really frustrating, I had Race S before and this doesn’t seem to be happening on Race S, map performance was always smooth.
still very likely magnetic interference…
No it is definitely not magnetic interference. This is super easy to re-create. And as is said, this only happens during navigation, not during normal map usage. To me it seems like a bad power savings feature that takes too long to become disabled. I can understand that the update frequency can be lowered while walking and not looking at the watch, but the watch takes too long to “flip back” to full perf mode when raised and used.
-
@borgein
did you read above potential explanation ? map orientation is based on compass when not moving under a specific speed (thus reacting quickly to you moving your wrist around) and map is pointing to movement(gps) direction above this speed --> map is only responsive following your movement direction and position change