OnMove100 is buggy (at least some versions of the firmware) and reports the
average speed from the beginning of the session instead of the instant speed.
This issue occurs both with official software and with kalenji_reader, so it's
clearly an issue with the watch. There's nothing to be fixed in its support
(later versions of the firmware may fix it).
But it would be nice to implement a ComputeInstantSpeed filter that would
compute the speed from coordinates and time.
Original issue reported on code.google.com by colin.pi...@gmail.com on 3 Jun 2014 at 8:14
Original issue reported on code.google.com by
colin.pi...@gmail.com
on 3 Jun 2014 at 8:14