-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speed jumps to 0.0 repeatedly during run/ride #2043
Comments
This should happen if you become idle. If OpenTracks becomes idle, there can be a voice announcement. |
It's definitively not while me being idle that it jumps to 0, I was definitely multiple times heading downhill at a reasonable (30+km/h) speed! Next time I go for a ride, I'll see if I can get some logging going, and/or video of it |
Idle can also be triggered by low GPS reception. Anyhow, there was a change in v4.17.0. |
Here's a screen-capture of a few seconds of me riding. I'm fairly certain it's not bad GPS reception, as the tracks import fine in FitTrackee, with the correct locations, and speeds, hence my thought originally, that it's purely a visual/on-screen thing. I can share the GPX with you (still haven't enabled logging) via email, if that would be helpful? |
Thanks Can you upload the video directly to Github? |
Hello, |
Found the problem: it is a side effect of AggregatorGPS.reset() [trigger on new GPS data] and the TrackPointCreator.createCurrentTrackPoint() No effect on recorded data; only UI. Will take some days to fix. |
Thanks for the explanation and taking care of it.
OpenTracks is really a great ap, I'm happy to use it as soon as I'm on my bike.
Take care 💪
Envoyé depuis Proton Mail pour Android
…-------- Message d'origine --------
Le 06/01/2025 22:27, Dennis Guse a écrit :
Found the problem: it is a side effect of AggregatorGPS.reset() [trigger on new GPS data] and the TrackPointCreator.createCurrentTrackPoint()
No effect on recorded data; only UI.
Just looks ugly.
Will take some days to fix.
—
Reply to this email directly, [view it on GitHub](#2043 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AEASWTXJ73WPYLM4TKORSRL2JLYLBAVCNFSM6AAAAABUPCAYT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTHE2TKOBUGE).
You are receiving this because you commented.Message ID: ***@***.***>
|
Describe the bug
As of recently, the speed shows on screen as 0.0 a lot.
The speed jumps between the actual speed and 0.0, while the distance/altitude etc. measurements keep going as normal.
When importing in to FitTrackee, I don't see these drops in speed in the uncleaned charts generated, hence I'm assuming it's a display issue and not an actual recording issue.
To Reproduce
If applicable:
Technical information
The text was updated successfully, but these errors were encountered: