-
Notifications
You must be signed in to change notification settings - Fork 107
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
question about partial wakelock #15
Comments
Some extra comments: I believe that in your plugin, window.powerManagement.acquire uses FULL_WAKE_LOCK However, for my app I think I would need PARTIAL_WAKE_LOCK to have the screen go off while still keeping the app running. |
isn't that already managed by @boltex solution? |
indeed |
@boltex after acquiring wakelock the screen stays Active after implementing release function the screen is still in active state.it stays active until we terminate the app.Does the release function revokes the powermanagement.acquire()-if it does then it should come back to normal state then the screen should go inactive(OFF) as we mentioned in device settings for screen saver.! |
Hi,
thanks for the useful plugin, and also for the enhancement by Boltex.
My Android app fetches data periodically from a server. In order to keep the app running at all times I'm using Katzer's background plugin along with your powermanagemen plugin.
This works very well, however there is still one problem: the screen remain on all the time (unless I manually switch it off with the power button). Even when I switch to another app the screen remains on all the time.
I would like to have the screen go off automatically after some time of inactivity, just like any other app.
When I use window.powerManagement.acquire, the screen remains on with full brightness.
When I use window.powerManagement.dim, the screen will go dim after a while, but it will never go off completely.
How can I have the screen go completely off automatically as usual (while still keeping the app running)?
The text was updated successfully, but these errors were encountered: