Skip to content
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

Open
Firesphere opened this issue Jan 1, 2025 · 10 comments
Open

Speed jumps to 0.0 repeatedly during run/ride #2043

Firesphere opened this issue Jan 1, 2025 · 10 comments
Labels
bug Something isn't working

Comments

@Firesphere
Copy link

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

  1. Start a new track
  2. Start moving
  3. Keep an eye on the current speed
  4. Notice the speed jumping to 0

If applicable:

  • Can't really screenshot while cycling
  • Would love to, if possible... How can I get a log output?

Technical information

  • Device: Oppo Find X2 Lite
  • OS: ColourOS V12.1
  • OpenTracks version: v4.17.0
@Firesphere Firesphere added the potential bug A bug that could not (yet) be reproduced label Jan 1, 2025
@Firesphere Firesphere changed the title Speed jumps to 0.0 Speed jumps to 0.0 repeatedly during run/ride Jan 1, 2025
@dennisguse
Copy link
Member

This should happen if you become idle.
Can you check if the time to idle is too low in your case?

If OpenTracks becomes idle, there can be a voice announcement.
This helps to identify it.

@Firesphere
Copy link
Author

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

@dennisguse
Copy link
Member

Idle can also be triggered by low GPS reception.
Default is: 10s no movement reported.

Anyhow, there was a change in v4.17.0.
I hope I didn't break anything...

@Firesphere
Copy link
Author

Firesphere commented Jan 3, 2025

Here's a screen-capture of a few seconds of me riding.
https://static.firesphere.dev/Record_2025-01-03-14-22-38.mp4

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?

@dennisguse dennisguse added bug Something isn't working and removed potential bug A bug that could not (yet) be reproduced labels Jan 3, 2025
@dennisguse
Copy link
Member

Thanks
I have a gut feeling where I broke something...
Somewhere in the reset() part.

Can you upload the video directly to Github?
Then it is also available in the future.

@dennisguse
Copy link
Member

Likely are those two:

@Firesphere
Copy link
Author

As per request :)
https://github.com/user-attachments/assets/002bae37-bc7a-4918-98c8-237f1e4c71f3

@Stephane-74
Copy link

Hello,
I have the same problem here. Sorry I couldn't make a screenshot, but I experienced it today. The speed stays at 0, but shows the value once n a while, for one or two seconds. Same thing with the altitude. Max speed, duration and time were OK.
Sorry I can't help more.

@dennisguse
Copy link
Member

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.

@Stephane-74
Copy link

Stephane-74 commented Jan 6, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants