-
Notifications
You must be signed in to change notification settings - Fork 2
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
Android app to keep screen on #1
Comments
You should be able to run the app with the screen off -- I've had a similar report in the past and I think it may be due to Doze Mode introduced in Android 9 where it prevents some tasks from running when the device is detected as idle or standby. Open the app settings screen (Android 'App info' screen) and try enabling Allow background activity or disabling battery optimisation for the app to see if this makes a different. The timer does hold the data until powered off -- however the app is only polling the current lap data. There is an unused API command for retrieving lap information for a specific lap number too (will be documented eventually in the wiki). Let me know how you go :) |
Ah that sounds like a workaround but I did some tests and the app is not just requesting to keep the screen all (that might be a simple addition in settings). Newer android (9/10) are quite agressive killing apps (at least on my two huawei phones) so for now the only way I am able to keep the screen on is: setting that on Developer options and plugging the phone to a powerbank. |
I personally turn off the screen and listen to the callouts. However I agree it would be good as a feature to have a setting in the app for users to toggle on to request screen to be awake whilst in foreground. I've made note of this for an iteration for the app :) |
Oh, I see. I get immediately disconnected when the screen goes off. I will do futher tests overriding the battery saving settings |
Hi, I am not sure where to submit this issue but: on app switch or screen off, the android app loses the current run data and connection with the BT timer. This is clearly a big issue considering the pidflight timer device itself is not recording anything.
The text was updated successfully, but these errors were encountered: