Doze behaviour has been [changed](https://developer.android.com/about/versions/nougat/android-7.0-changes.html) in Nougat. Doze is implemented in two stages > When a device is on battery power, and the screen has been off for a certain time, the device enters Doze and applies the *first* subset of restrictions: It shuts off app network access, and defers jobs and syncs. > > If the device is stationary for a certain time after entering Doze, the system applies the *rest of the Doze restrictions* to PowerManager.WakeLock, AlarmManager alarms, GPS, and Wi-Fi scans. My question: **What are the typical timings for steps 1 and 2?** * Even in Marshmallow, I could not find a reference to the exact timing, but it was reportedly between 20 and 40 minutes. * I am wondering if timings have been specified now, though my search didn't yield anything

Since Android 14, I'm no longer able to log into my phone remotely via a reverse tunnel to a server with a static IP. It appears that Doze is the underlying issue; it stops termux, which stops the sshd child process, so the tunnel goes away, and it doesn't come back, despite my having scheduled (in termux-land) a check-and-restore process every few minutes. It does not help to turn off battery optimizations or to enable wake-lock. Is there is a way to exempt termux (for example) from Doze in Android 14 without rooting the phone?

Recently I've been trying to optimize the doze settings for my device. I found many guides that date back to 2015/16. All of them say something similar: To change a deviceidle setting, I have to input adb shell settings put global device_idle_constants inactive_to=30000,sensing_to=0 (for example) in a terminal. When typing in adb shell settings list global, device_idle_constants doesn't get listed tho. Seems to me it's deprecated. **My Problem:** This setting doesn't change anything at all. When I change sensing_to to 0 like I have shown above, it's still at 4m0s0ms. I can confirm this by putting adb shell dumpsys deviceidle in the terminal. Does anyone know how to change those doze parameters in Android 12(L)? Btw: I have a Poco F3 with LineageOS 19.1

**EDIT** Ever since I installed the latest security patch available for my Phone (October 5 patch), there has been insane idle battery usage. More like 1% dropping sequentially whenever I'm sleeping *It's worth noting that, this doesn't happen when the phone is in Airplane mode, or switched off*. I picked up the Paid version of Accu Battery, it doesn't show background battery usage. Better Battery Stats (BBS) was recommended and I went for it but it doesn't work most of the time (shows *No stats have been collected yet*). But I slept for the past 4 hours and it worked, but I need someone the translate it's output for me, so I can recognize what's draining my battery. Attached are the screenshots Model: **TECNO KF7j** Android Version: **11** Device name: **TECNO SPARK 7P**       

I have two OnePlus 7Pro devices, both running OOS 10.3.8 and both rooted. On one of these devices, I can go to ***Settings=>System=>Developer options=>Standby apps***, and in the resulting list of installed apps, I can successfully change the status of any app from "ACTIVE" to other values ("WORKING_SET", "FREQUENT", "RARE"). On the other device, when I go to ***Settings=>System=>Developer options=>Standby apps***, I also see the list of installed apps, but all are showing as "ACTIVE", and when I try to change that status for any app, the status does not change, and it remains "ACTIVE". This unchangeability persists after reboots. I have been trying to deal with doze-related issues on the second device, and I'm guessing that one of the many things I was experimenting with might have caused AppStandbyBucket values to become unmodifiable. What could I have done on this second device to prevent the Standby-app status from being changeable? ... and what can I do on that device to enable those status values to be changed? Thank you in advance for any thoughts and suggestions. **PS**: I'm wondering if there might be some config file somewhere on the device which should be writable, but whose permissions might have gotten changed to read-only. Is that possible? If so, what could be the file (or files) in question?

I have a Samsung Galaxy Tab Active2 (SM-T390) tablet with Android 9 and One UI 1.1 and the latest available updates. An app with an WebView looses connection after about six minutes of standby. I tried to disable enrgy saving for the app as well as Chrome and Android System WebView (Chrome and WebView disables each other). This approach does work for another Samsung device with Android 10, but not on Android 9. Is there another app, which I have to exclude from power saving? Or is this a bug in Android or from Samsung?

I have a Samsung S20FE (Android 11 + OneUI 3.1). I was learning about the different battery optimization settings. I think I have a good understanding of Android's Doze mode. Now, I've seen there is (under Battery → Background usage limits) something called "Deep Sleep". According to this question , it seems "Deep Sleep" is OEM specific, and is not found in every manufacturer's device. I noticed that an application that is already excluded from "Doze mode" (in other words, an application that is NOT optimized) can not be excluded from "deep sleep mode" (in other words, can not be added to the never-sleeping-apps list). Thus, I suppose an application goes first into "doze mode", and then into "deep sleep". Am I correct ? If yes, under what circumstances does an app go into Deep Sleep ? Could an app like Skype (that is natively allowed to wake up the phone even in Doze Mode, I believe) go into Deep Sleep if it isn't used for a while ? Does it make sense to add Skype to Deep Sleep's never-sleeping-apps list if I want it to be always responsive (i.e., I want to receive Skype calls even if I haven't used Skype for some time) ? Or is it unnecessary ?

I noticed that some applications are whitelisted from doze-mode on samsung devices without having ever asked the user. I tested this on a galaxy s8, galaxy A5 2016, 2017 all running android 7.0 or 7.1. These apps are for instance Viber, WhatsApp, Messenger - they're what I have seen. When I first noticed this on a samsung I was not 100% sure that I have not by chance given them that permission myself... So I have done a fresh test by hard resetting a Samsung A5 2016 and installing only Viber onto the fresh phone. After the install, I have not even logged into Viber (and it had not had a chance to ask me of any permissions at all), I immediately checked the Battery Optimisation whitelist and Viber was there. So the first question is how - according to Android specs an app must ask the user to explicitly allow whitelisting (Am I wrong here)? The second question - is this maybe possible on Samsung despite the spec. The third question - maybe Samsung just knows some well known apps and whitelists them by default itself? --EDIT The initial research on this was hindered by the fact that if you google "samsung doze-mode whitelist" maybe with "not asking the user" it still serves you many links to the official doze mode specs and media articles, but not Samsung related. But then I searched with "samsung smart manager whitelist" and found the following 1. Question on SO (second answer gives a list of apps which are whitelisted) https://stackoverflow.com/questions/37205106/how-do-i-avoid-that-my-app-enters-optimization-on-samsung-devices the list of apps in the second answer was of undisclosed source but I can confirm that I checked nearly 10 of them and they are whitelisted by default 2.https://seap.samsung.com/forum-topic/whitelist-app-batteryoptimization-smart-manager-application Funny thing - the user asks a question and a part of the question is the same as mine - why Viber etc are whitelisted. The answer is carefully avoiding that part and only answers the other part - that he should ask the users consent or use Knox (also asking the user for permission) So answers to my own questions 1. According to the spec the app must ask users consent to be whitelisted - yes. 2. not possible on Samsung for a simple app, either 3. Yes, Samsung has a whitelist of well-known apps in its Smartmanager 2 more pieces of info A. Samsung is reluctant to talk about it(see above SEAP link) or maybe not everybody there is aware of the fact. B. If you have an issue with Samsung doze-mode, do not google for "Samsung doze-mode", google for smth. like "Samsung smart manager doze-mode" (add "smart manager"), because it will yield more Samsung specific results (And Samsung part of battery optimizations is pretty specific).

How do I keep my WiFi running when my phone's screen is off and locked? Facts: 1. The biggest battery drain is my screen usage 1. WiFi uses your battery, but not nearly as badly as the screen 1. I use my phone to stream audio 1. I intentionally turn off my phone's screen to save my phone's battery 1. If I'm playing a local file that I previously downloaded, then I have no issues with the audio stopping when my screen is off. 1. If I'm streaming audio, then sometime after I turn off my phone's screen, the audio streaming stops (I guess after it locks and the the stream buffer is empty) 1. Immediately after I wake my screen, the audio stream resumes. Unlocking the phone is not necessary to resume the audio stream. I assume, therefore, that my phone is disabling my WiFi sometime after my handset's screen is turned off. I am running LineageOS 18 (Android 11). How do I prevent my android device from disabling my WiFi when the screen is off?

Almost all the posts I saw imply that WhatsApp does not use GCM. Instead, it uses two sockets to communicate using FunXMPP. Then how is the App active on Marshmallow even in Doze mode ? I don't remember giving the permission REQUEST_IGNORE_BATTERY_OPTIMIZATIONS to the Application. And yes, the app is not whitelisted

Assume that I'm a user who doesn't like some system apps being automatically white-listed under Battery optimization settings and immune from battery optimization or is fed up with Play services consuming more than its fair share of battery. I'm looking for a solution which would revoke this privilege enjoyed by those apps and add them into the line where the rest of the ordinary comrade apps are waiting for the user to mark them with *Don't optimize*. (Click image to enlarge) " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> I've already seen [this answer](https://android.stackexchange.com/a/137699/96277) and as noted in a [comment](https://android.stackexchange.com/questions/129074/is-there-a-way-to-exclude-an-app-from-doze/137699#comment176869_137699) it doesn't work for apps white-listed by system. As of now, these are the apps white-listed by Android 6.0.1 in my rooted Nexus 6: I'm most interested in removing *com.google.android.gms*.

# Background SleepBot is a freeware sleep-tracking app. It includes a ["smart alarm"](http://en.wikipedia.org/wiki/SleepBot#Features) feature which claims to help prevent early-morning grogginess and [sleep inertia](http://enwp.org/Sleep_inertia) . There are other competing free apps, but they aren't great. There's also [Sleep as Android](https://play.google.com/store/apps/details?id=com.urbandroid.sleep&hl=en) , which is a very good app; but it's trialware, and it costs US$4 to remove the [restrictions](http://sleep.urbandroid.org/documentation/trial/) after the trial ends. # The problem Various individuals, such as [this one](https://www.reddit.com/r/nexus5x/comments/3zflgf/3rd_party_alarm_apps_not_waking_device/cz6adte) and [this one](https://www.facebook.com/sleepbot/posts/1097826330280187) , complain of problems with SleepBot's alarm functionality when using Android 6.x "Marshmallow". They tend to complain about problems regarding SleepBot's smart alarms never ringing at all, or about problems with the alarms' snooze function. # My questions I don't own any Android 6.x device. But I wonder: * Does Android 6.x "Marshmallow" truly cause problems with SleepBot? * Are any of these problems due to "Doze" mode? * Is there any workaround for any of these problems? ----- Possibly related: ["Alarm clocks aren't working on Android 6"](https://android.stackexchange.com/questions/145848/alarm-clocks-arent-working-on-android-6) .

I've got a Galaxy S8 and have come across an interesting situation. Now, either something strange is going on, or I've got no clue how it actually works! I've downloaded an FTP Server app on my phone which I wanted to leave running in the background. The problem was that, once the screen turned off, the wifi connection would drop after 5 mins and I couldn't connect to my phone. I had enabled the setting for WiFi to always be connected and I know that the app has both PARTIAL_WAKE_LOCK and WifiLocks so I had expected the connection to remain in place. I added the app to the list of "Unmonitored Apps" in the battery optimisation settings but this had no effect. Using adb I could see that the UID of the service holding the WAKE_LOCK was not listed in mDeviceIdleWhitelist so I ran adb shell dumpsys deviceidle whitelist +PACKAGE_NAME and saw that the UID was now in the list. After running this command, the app behaves as expected and I can continue to connect once the screen has been off for a while. So my question is whether there is a difference between "Unmonitored Apps" and the mDeviceIdleWhitelist? If there isn't, is this a bug in the phone software?

I’ve been trying to get Smart Lock to work on my Android device (OnePlus One on Cyanogen OS 13.1.2, i. e. Android 6.0.1/“Marshmallow”). I’ve configured an NFC tag as a trusted device and want to use this NFC tag to unlock my phone instead of having to type my long password every time. The problem is that unlocking using the NFC tag is really unreliable. Most of the time, when I activate my NFC tag on the lock screen, nothing happens, even though the pulsing circle around the lock icon at the bottom of the screen is present (indicating that Smart Lock is active). Sometimes, however, the NFC tag is recognized and unlocks the phone without problems. I haven’t really figured out the circumstances under which it happens. For example, when I turn NFC off and then on again in the settings and lock the phone then, unlocking using the NFC tag once always works without problems, but the next time, it won’t work again. What could be the issue here? Am I somehow using Smart Lock incorrectly? Does Android perhaps turn off NFC or the process responsible for Smart Lock after a while when the phone is locked (Doze mode)? If so, how do I prevent this? ---------- *Note:* Also tried on someone else’s phone running Android 7 (“Nougat”), same thing: after setup, unlocking the phone using NFC works exactly *once*, but immediately locking the phone again and then trying to unlock doesn’t work.

On my Samsung Galaxy S7, whenever the device goes to sleep, the Wifi goes to sleep as well. Meaning: * If I'm connected to a WiFi network and the device is idle for about 10 minutes (tested it), the device won't be connected to the WiFi network anymore (ping is unreachable) * If entering a WiFi network area and device is idle, it won't connect to the network until I turn on the device manually. *There are exceptions:* * While charging * When disabling deviceidle option via adb (adb shell dumpsys deviceidle disable), the problem is the option is reset after reboot *What I've checked so far ?* * Different Wifi networks * All 'Keep WiFi on during sleep' options * All 'Smart network switch' options * Setting my router to specific channel and not auto * Manually disabling almost all possible apps under 'doze' option * An app to 'keep the device alive' IMHO, as disabling 'deviceidle' actually fixes the issue (until next reboot), it's some kind of a bug in Android which tries to optimize the WiFi process, but, I hope someone proves me wrong.

I own a gallaxy s5. And my battery really sucks so I often switch to ultra power saving mode. I type a lot and I don't really like the default Samsung keyboard. I want to change the default to Gboard. Any help is greatly appreciated!

My LG G3 with Android 6.0 uses the built in Doze mode to save some battery. At the first setup, I set applications to ignore Doze mode (like chat apps, Gmail, Viber etc.). I also set the "app" called Wifi to make my Wifi enabled while in Doze mode. They worked okay, I get my messages even if my phone is in Doze mode. After 1 year of usage, when I unlock my phone, I can see that my phone is switching from _mobile data_ to _Wifi_ and my data package is being used up by the aforementioned disabled programs. Why? And how can I make my phone to use Wifi permanently? What changed after 1 year?

I'm using Nexus 5 and 6P, Android 6 having a feature called "Battery optimization mode" or Doze mode (in short). It is allowing apps not to run, if they aren't used to avoid battery consumption. Google play services consumes more battery, RAM and CPU. But it is not included in Doze mode. I've sent multiple feedback from my devices about this issue, but Google is not hearing at all. Anyone please help me clarify, Why Google play services not included in Doze mode?

I do not see any reason mentioned by Google for [Doze mode](https://developer.android.com/preview/features/power-mgmt.html#behavior-doze) to get activated only when the device is stationary. Is there any specific advantage for doing this only when the device is stationary? What is the need to even waste resources checking for motion detector readings, when this can simply be achieved whenever the screen is off. I am asking this because my phone is in my pocket for most of the time and because of that Doze mode will not get activated. I think there are many more people like me, so I don't understand why google chose these specific constraints for Doze mode.

Prior to Android M there was something called sleep mode in Android. With Android M Google introduced the so called Doze Mode. Can anyone please elaborate the difference between these modes?