-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
When starting OpenTracks via GadgetBridge no data is being recorded #1904
Comments
Might be #1653. If the screen is off, some Android devices might enforce permission to access the location in the background. Can you check if it works, if the screen is on? |
Also does not work with screen on. I see that only Gadgetbridge is accessing Location and on Opentracks a new record is being created but directly stopped with no data. |
Can you check if there is a crash happening (check logcat)? |
Can you start a recording (that has data) via the UI? |
Yes, with the UI it works. |
I have the same issue when starting to track via intents (I have a device that I use only for sport activities and use tasker to start tracking once the connection is established). It creates a track of 0 seconds and that's all. Manually starting to track works without issues. |
Same here |
Came here to report this exact issue, glad to find it's already known! |
Logcat:
Specifically this line seems to be the culprit:
|
I have the same issue and I observed the following:
Those issues did not occur before 03 APR 2024. I'm using nightly via F-Droid on Andorid 12. |
When starting a new recording with my Mi Band 7 via Gadgetbridge a new recording is being started with opentracks but directly after the start stopped and no data is being recorded.
I know from old recordings that is worked until at least 2024-03-02, I just discovered that all other recordings are empty since then.
This is only the case when started via Gadgetbridge (via intent?), normal recording works. I checked all the settings, they seem to be correct.
...
Checklist
Technical information
The text was updated successfully, but these errors were encountered: