-
Notifications
You must be signed in to change notification settings - Fork 608
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
Crashes on startup. Missing SCHEDULE_EXACT_ALARM or USE_EXACT_ALARM permission? #1187
Comments
I am guessing that the problem might be this bit: gpslogger/gpslogger/src/main/java/com/mendhak/gpslogger/GpsLoggingService.java Lines 333 to 338 in cde1f9f
The app hasn't been allowed to use exact alarms so it's just crashing. That said, there's the proper fix for it which is to see if exact alarms are allowed, and to fall back to normal alarms. I've done it here: gpslogger/gpslogger/src/main/java/com/mendhak/gpslogger/GpsLoggingService.java Lines 1101 to 1110 in cde1f9f
But of course I missed it for the auto sender. Yes it's somewhat related, if you enabled SFTP uploads then the 'auto send timer' alarm code kicked in which I missed in the Android 15 prep work. |
Thank you! I had to open App settings → App battery usage: “Allow background usage” was enabled, but I had to change it from “Optimized” to “Unrestricted”. Now, GPSLogger is opening properly again. |
…on Android 15 when background usage was denied. Issue #1187
OK thanks for confirming that. I've just pushed a fix to the pull request, I'll include it in v133. |
GPSLogger was working fine until a few days ago, when it suddenly started to misbehave. The background service is no longer running, and when I try to open GPSLogger, it crashes immediately:
I am using GrapheneOS on a Pixel 8, with Android 15. I activated SFTP upload a few days ago (which was working). Not sure if that is related.
The text was updated successfully, but these errors were encountered: