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

Samsung galaxy s10 not tracking in Background #1902

Closed
1 task done
FirstWithThisName opened this issue Apr 24, 2024 · 8 comments
Closed
1 task done

Samsung galaxy s10 not tracking in Background #1902

FirstWithThisName opened this issue Apr 24, 2024 · 8 comments
Labels
potential bug A bug that could not (yet) be reproduced

Comments

@FirstWithThisName
Copy link

Please describe the problem and how to reproduce it:

...

Checklist

  • Consulted [https://dontkillmyapp.com/]
  • [x ] Power management: battery optimization is disabled for OpenTracks

Technical information

  • Device: [Samsung Galaxy s10]
  • OS: 12
  • OpenTracks version: 4.12.0

OT only records if the screen is on.
I only can allow using the location while app usage.
Other app have the option to always allow using the location.

@FirstWithThisName FirstWithThisName added the potential bug A bug that could not (yet) be reproduced label Apr 24, 2024
@ghost
Copy link

ghost commented Apr 25, 2024

Could #1653 be related?

@dennisguse
Copy link
Member

How do you start OpenTracks?

@FirstWithThisName
Copy link
Author

FirstWithThisName commented Apr 28, 2024 via email

@FirstWithThisName
Copy link
Author

How do you start OpenTracks?

With the red button at the lower right corner

@dennisguse
Copy link
Member

That's a different problem than.

PERMISSION_LOCATION_BACKGROUND is not required if started via the UI.
In this case: it is usually a misconfiguration with power saving - e.g. something like Android OS optimizing for low power consumption.

@FirstWithThisName
Copy link
Author

I set it to not optiomize in the app settings but, my phone maybe been in energie saving mode. I will test tomorrow if switching of the energie saving mode fixed the issue.

@dennisguse
Copy link
Member

And?

@FirstWithThisName
Copy link
Author

Oh, sorry it seams like the e-mail resonse didn't work.

Disableing the engerie save mode fixed it.

Thanks for your help!

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