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

Open tracks does not record correctly the trace anymore #2056

Open
lanigb opened this issue Feb 14, 2025 · 2 comments
Open

Open tracks does not record correctly the trace anymore #2056

lanigb opened this issue Feb 14, 2025 · 2 comments
Labels
potential bug A bug that could not (yet) be reproduced

Comments

@lanigb
Copy link

lanigb commented Feb 14, 2025

Describe the bug
Since maybe 2 weeks, Open tracks doesn't record correctly the trace anymore.

To Reproduce

  1. Start recording in Opentracks
  2. walk or drive
  3. Stop recording
  4. recorded distance is very short though time is correct.

If applicable:

  • add screenshots
  • add logcat output

Technical information

  • Device:Samsung A13
  • OS: Android 14
  • OpenTracks version: V4.17.irreproductible.v4.17.5
@lanigb lanigb added the potential bug A bug that could not (yet) be reproduced label Feb 14, 2025
@dennisguse
Copy link
Member

dennisguse commented Feb 15, 2025

Can you check if data was recorded?
You can use OSM Dashboard for this.

In general: sounds like a power saving problem.
Was battery saver on?

@lanigb
Copy link
Author

lanigb commented Feb 16, 2025

In short : yes, it is a power saving issue.

After having discovered that power saving was the culprit, I have tried a bunch of settings: power saving off, never suspended apps (not sure of the name of the setting in English) don't lock screen when phone is on you, and so on all in vain.

I have also read a closed discussion similar to my problem where you explained why you couldn't fix the bug. I understand your reasons.
I have also a very cheap Huawei bought for this use, phone where OpenTracks works as it should so I am ok with that.

Just one more information that could be useful to you : on the same phone where OpenTracks fails, AAT works well (nevertheless, I do prefer OpenTracks). Maybe the dev has find a clever way to work around this problem.
Best regards, and thanks for your app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
potential bug A bug that could not (yet) be reproduced
Projects
None yet
Development

No branches or pull requests

2 participants