The Android Doze problem will only be experienced by phones on Android 6.0 and above and will not occur when the device is on the charger
- Users with adequate WiFi, but poor cell service, can find their incoming calls going to voicemail if their phone has been sleeping for a while. This happens because after sleeping for some period of time, the Android Doze function turns off WiFi. When a call comes in, RW attempts to awaken the phone but if it doesn’t wake up fast enough to reply to RW’s interrogation they sends the call via cell … but if cell service is unavailable the call goes to voicemail.
Current work around’s
There are currently 3 versions of work arounds available.for the problem that have been developed by community members … these all work with the free version of MacroDroid
Published Method to Manage Doze by @jBen
Some devices and later levels of OS have shown to use a different interval of time before Doze turns off the WiFi made it was necessary to take a different approach. This combined with the major improvements in the Connectivity Status Notifications resulted in the following
The latest iteration has been uploaded to MacroDroid on June 16, 2019 and it is available to anyone as a Template and prevents you from having to build it yourself .
- Download from the Play Store and Open the free MacroDroid
- Select Templates (center left grey) Home Screen
- Search for Doze Detect 9.0 and below - ver 0.9.6 (current version is labeled 0.9.6 and valid for 3.0 RW App 126.96.36.199 and higher) …(‘Doze Detect’ is a valid search argument)
- Once located TAP the Macro, then hit the Plus (bottom right in the White circle) to save local on your phone .
- This should put it in the Macros section of the Home page
- Ensure it is toggled on … both slides to the right: Category/Communication and Doze Detect (not grayed out).
6/13/19 Removed the 15 sec timer that changed the basic Android display timeout that users had set, and added the constraint to Not Trigger when in a Call
Due to the occasional failure that required the screen to be turned on and let time out, it is now turned on when the RW Notification is ‘On Cell’, and then when the 2nd RW Notification (which normally will be On WiFi) is detected the display is turned off to conserve battery life
Note: If this doesn’t work for you, it would be helpful if you could provide some feedback, either as a Comment or DM to me @jBen
- Which Phone & OS level
- Your description of the problem encountered.
- Screenshot of the last couple pages of User Logs
- Logs are accessible from the MacroDroid App / Menu (top left) / User Logs
Original Method to Manage Doze by @billg
- Go to the Play store and install the free Macrodroid app:
- Make this macro:
The macro turns the screen on every 50 minutes preventing the phone from entering the Doze mode. This will drain the battery a little faster depending on one’s display settings. The app can be turned on and off with a simple toggle.
Turning the screen off immediately after turning it on can extend the battery life BUT on Samsung phones this forces you to use a PIN instead of the fingerprint sensor on your next access. On my S7 I deleted this step and let the screen turn off by itself.
It is quite likely this work-around will also fix a problem where WiFi disconnects in Doze which, in turn, causes the phone to use cellular data (if LTE service is available) while connected to WiFi. That problem can also be fixed by toggling WiFi off and back on again but the Macrodroid work-around makes that unnecessary.
Alternate version for Android 10, by @littletoucan
This is my final solution for my Pixel running Android 10, a combination of Doze and my few additions:
This discussion has been ‘trimmed’ to just contain the original and latest iteration of the available fix. It is readily admitted that this does not ‘fix’ all the problems that users may encounter when the WiFi is disabled by Doze (an Android function), but it has been a help to some
- If you try this and it doesn’t work for you, please provide feedback via a comment or DM to @jben, so we can understand how the problem manifests itself in your environment