It’s an issue that is difficult to address - if there were one easy fix, it would have been deployed by now. If any app had the right to overrule Doze Mode, then every app would overrule Doze Mode, so Android makes it, by design, nearly impossible to overrule.
Even the user of the phone can’t configure the phone to avoid Doze Mode without issuing an ADB command that then has to be re-issued upon each reboot.
What would help, though, would be examples that elevate the issue and help us prioritize it. I’ve reviewed your Help Ticket history and I don’t see that you’ve opened a Help Ticket on the matter. While our technicians won’t be able to resolve the issue for you, it would be worthwhile and very helpful to have examples from members who are plagued by the issue.
Examples can be difficult to come by, because you have to know you’ve missed a call. But if you see voicemail for a call the phone never received (it must not appear in “missed calls”) then that would be a great example to provide to our technicians.
(Unfortunately, with recent updates to Android, we see a lot of reports of people saying their calls go straight to voicemail without ever ringing simply because they have enabled “Do not disturb” mode or have accidentally silenced their ringtone. It’s very important that there not be a “missed call” record logged for the call if we are to investigate it as a possible Doze Mode conflict.)
When we do have examples, we would need to pull call logs and your device logs fairly quickly (while relevant data is still available in those logs).
If you see this issue frequently and have examples to share, please open a ticket, with the following information:
- The complete date and time (including timezone) of the call that went straight to voicemail
- The caller’s phone number and intended recipient’s phone number (if you have multiple phones on your account).
- Confirmation that you have submitted device logs: open your phone dialer as if you were going to make a call and dial * # * # 5647 # * # *
- A request that your report be attached to master ticket 1829384 along with the device logs and call trace logs (the agent will have to pull these “trace” logs).