I have no idea what approach the Any Screen Timeout Plus app is using if it's able to keep the screen on. I'm using the WindowManager flag to keep the screen on: https://developer.android.com/reference/..._SCREEN_ON
This is what is recommended by Google as described here in the "Keep the screen on" section: https://developer.android.com/training/s...g/wakelock
If you go into the MobileSheets settings and switch the "Keep CPU On" setting to "While Viewing Scores", that uses a wakelock, which keeps the CPU running as described on that same page. I don't think this gets past the problem, but if it does, that certainly wastes a lot more battery power. I have not tried using a broadcast receiver, as that's really meant for services, but it's another thing I could test. Really, BOOX should just fix their firmware to allow the screen to stay on if the app requests it.
Mike
UPDATE:
The CPU wakelock does not work to keep the screen on.
This is what is recommended by Google as described here in the "Keep the screen on" section: https://developer.android.com/training/s...g/wakelock
If you go into the MobileSheets settings and switch the "Keep CPU On" setting to "While Viewing Scores", that uses a wakelock, which keeps the CPU running as described on that same page. I don't think this gets past the problem, but if it does, that certainly wastes a lot more battery power. I have not tried using a broadcast receiver, as that's really meant for services, but it's another thing I could test. Really, BOOX should just fix their firmware to allow the screen to stay on if the app requests it.
Mike
UPDATE:
The CPU wakelock does not work to keep the screen on.