Related
On my Pixel XL, I had to essentially whitelist certain apps to make sure I got notifications in a timely manner (Aquamail, etc) since doze would put them to sleep after the phone sat for a while. It has been one of my biggest peevs with Android since they introduced doze and it's worse on some devices than others.
On my GS8+, I see no options anywhere to whitelist apps from battery savings. And all of my emails and other notifications have been coming in just fine. It's like Samsung just left doze off permanently or something.
greyhulk said:
On my Pixel XL, I had to essentially whitelist certain apps to make sure I got notifications in a timely manner (Aquamail, etc) since doze would put them to sleep after the phone sat for a while. It has been one of my biggest peevs with Android since they introduced doze and it's worse on some devices than others.
On my GS8+, I see no options anywhere to whitelist apps from battery savings. And all of my emails and other notifications have been coming in just fine. It's like Samsung just left doze off permanently or something.
Click to expand...
Click to collapse
You can manually add and remove packages with a shell script. Do dumpsys deviceidle for instructions. You're looking for dumpsys deviceidle whitelist [see instructions for syntax to add/remove].
RuggedHunter said:
You can manually add and remove packages with a shell script. Do dumpsys deviceidle for instructions. You're looking for dumpsys deviceidle whitelist [see instructions for syntax to add/remove].
Click to expand...
Click to collapse
So is doze on or off by default, then? Because I haven't made any exceptions (obviously) and I'm getting all notifications without delay.
On my Pixel, I HAD to make exceptions to ensure no delays.
Sent from my SM-G955U using Tapatalk
Doze should be on by default.
I tried excluding Gmail (and Google Photos) from doze using adb and it stayed excluded even after device restart.
Code:
adb shell dumpsys deviceidle whitelist +com.google.android.gm
adb shell dumpsys deviceidle whitelist +com.google.android.apps.photos
(Use minus sign instead of plus to remove package from list)
Verify:
Code:
adb shell dumpsys deviceidle whitelist
I attempted the same on Android 9 before but it always got lost shortly after reboot. On Android 10, it seems like it sticks (and works - based on my first few tries).
I also noticed that com.android.settings.Settings$HighPowerApplicationsActivity no longer lists system apps. OnePlus also removed the more aggressive power saving option.
moneytoo said:
I tried excluding Gmail (and Google Photos) from doze using adb and it stayed excluded even after device restart.
(Use minus sign instead of plus to remove package from list)
Verify:
I attempted the same on Android 9 before but it always got lost shortly after reboot. On Android 10, it seems like it sticks (and works - based on my first few tries).
I also noticed that com.android.settings.Settings$HighPowerApplicationsActivity no longer lists system apps. OnePlus also removed the more aggressive power saving option.
Click to expand...
Click to collapse
Nice findings and thx for sharing it with us
Great! Thanks for sharing
Edit:
Gmail notifications are still delayed by around 10min.
Isn't it true that whitelisting only DISABLES Battery Optimization for a particular app, and you can do the same thing via the Android interface?
And we all know that turning Battery Optimization off doesn't do squat to get notifications sooner.
OR does whitelisting via ADB (supposed to) do something more powerful than disabling Battery Optimization? Thanks so much.
Looking forward to your reply
wgraz said:
Isn't it true that whitelisting only DISABLES Battery Optimization for a particular app, and you can do the same thing via the Android interface?
And we all know that turning Battery Optimization off doesn't do squat to get notifications sooner.
OR does whitelisting via ADB (supposed to) do something more powerful than disabling Battery Optimization? Thanks so much.
Looking forward to your reply
Click to expand...
Click to collapse
Nope, via settings do not work, i disabled battery optimization as a whole but i have delays on sms and alarms, unless i wake up manually the phone, then the sms and alarms arrived all together.
Confirm that the setting is permanent, i'm using android 11 (custom rom), see the last two entries added to the system.
Code:
E:\Adb>adb shell dumpsys deviceidle whitelist
system-excidle,com.android.providers.calendar,10134
system-excidle,com.android.providers.downloads,10124
system-excidle,com.android.messaging,10183
system-excidle,com.qualcomm.qti.telephonyservice,1001
system-excidle,com.qualcomm.qcrilmsgtunnel,1001
system-excidle,com.android.cellbroadcastreceiver,10133
system-excidle,com.android.proxyhandler,10121
system-excidle,com.android.cellbroadcastreceiver.module,10205
system-excidle,com.android.shell,2000
system-excidle,com.android.deskclock,10182
system-excidle,com.qualcomm.atfwd,10197
system-excidle,com.android.providers.contacts,10132
system,com.android.providers.downloads,10124
system,com.android.messaging,10183
system,com.qualcomm.qti.telephonyservice,1001
system,com.qualcomm.qcrilmsgtunnel,1001
system,com.android.cellbroadcastreceiver,10133
system,com.android.cellbroadcastreceiver.module,10205
system,com.android.shell,2000
system,com.android.deskclock,10182
system,com.qualcomm.atfwd,10197
user,com.android.messaging,10183
user,com.android.deskclock,10182
When I added com.google.android.gm and com.google.android.apps.messaging, adb shell dumpsys deviceidle whitelist shows them in the "user" section, not the "system" section. Did I do something wrong? I notice the other apps in the "user" section are the ones I set to "Never Optimize" under battery preferences. I feel like adding these two are not going to make any difference since the "Never Optimize" setting doesn't help.
xda6969 said:
When I added com.google.android.gm and com.google.android.apps.messaging, adb shell dumpsys deviceidle whitelist shows them in the "user" section, not the "system" section. Did I do something wrong? I notice the other apps in the "user" section are the ones I set to "Never Optimize" under battery preferences. I feel like adding these two are not going to make any difference since the "Never Optimize" setting doesn't help.
Click to expand...
Click to collapse
No, is ok, the change is at user level. I disabled doze in the settings too under battery management.
In my case they do a huge different, i do not have anymore the delay on notifications, expecially sms and clock alarms.
kd276 said:
No, is ok, the change is at user level. I disabled doze in the settings too under battery management.
In my case they do a huge different, i do not have anymore the delay on notifications, expecially sms and clock alarms.
Click to expand...
Click to collapse
In my case, this didn't help. Gmail notifications are delayed randomly, sometimes like 7 minutes, other times until I unlock the phone. I have a Pixel 5a. Now I'm gonna try to the turn off doze altogether. I know this method requires it to be redone every reboot. Incidentally, I was able to reverse the whitelisting by using...
adb shell dumpsys deviceidle whitelist -com.google.android.gm
xda6969 said:
In my case, this didn't help. Gmail notifications are delayed randomly, sometimes like 7 minutes, other times until I unlock the phone. I have a Pixel 5a. Now I'm gonna try to the turn off doze altogether. I know this method requires it to be redone every reboot. Incidentally, I was able to reverse the whitelisting by using...
adb shell dumpsys deviceidle whitelist -com.google.android.gm
Click to expand...
Click to collapse
Sorry this trick didn't help your case, i'm on Poco X3 Pro.
Turned of Doze totally using...
adb shell dumpsys deviceidle disable
... and now notifications work correctly. This disable both deep doze and light doze.
Yes it seems like whitelisting com.google.android.gm isn't enough to keep it awake. There must be other package(s) that need to be whitelisted as well.
Its an odd one was working for a few days then now GSAM ceases to show application battery usage .
I tried placing GSAM app exempt for battery optimization and also even tried putting it inside the never sleeping app list under battery usage menu.
Anything I missed ? Cheers
I'm using GSAM Pro on my N9860 and I have all my app stats showing since I used the ADB command to enable more stats a few days ago. I've disabled battery optimisation altogether for the app. I have not added it to the never sleeping apps because it cannot be added there once optimisation is disabled.
tdodd said:
I'm using GSAM Pro on my N9860 and I have all my app stats showing since I used the ADB command to enable more stats a few days ago. I've disabled battery optimisation altogether for the app. I have not added it to the never sleeping apps because it cannot be added there once optimisation is disabled.
Click to expand...
Click to collapse
I remember having the same issue after some time with my s10 plus also, don't remember how I resolved it. But it appears samsung is using aggressive hibernation methods within their devices OS according to
https://dontkillmyapp.com/
Either way, I deleted app and reinstalled again and added to my never sleeping app list. So far working .
THIS IS A SUGGESTED CONFIGURATION FOR GOOGLE DEVICESOUT OF SUPPORT/CLOSEDRECOMMENDED SETTINGSTo Start With- Factory Reset (RECOMMENDED)
- Remove SIM before first boot
- Follow setup OFFLINE (DON'T restore anything during setup)
- Reboot, insert SIM then continue setup online.
System Settings- Auto-Rotate: DISABLED
- Notification Bubbles: DISABLED
- Notification History: DISABLED
- Synchronization: DISABLED (turn it off again when not in use).
- Location: DISABLED (turn it off again when not in use).
- Display Resolution: FHD/1080p
- Advanced features: ALL DISABLED
- Motions and Gestures: ALL DISABLED
- Auto download System Update over Wi-Fi: DISABLED
- Bluetooth Scanning (Location services): DISABLED
- Usage & Diagnostics: DISABLED
- Advertising ID: RESET & DELETE
- System Sound/Vibration feedback: OFF
- Network Mode: 4G
- Always On Display (AoD): DISABLED
- Dark Mode: ENABLED
- Trust Agent: DISABLED
- Turn Screen On: DISABLED
- Suggestions/Recommendations: ALL DISABLED
- Gestures/Shortcuts: DISABLED.
- Adaptive Battery: DISABLED
- Adaptive Connectivity: DISABLED.
Google Settings- Nearby connections: DISABLED
- Devices: DISABLED
- Nearby Share: DISABLED (turn it off again when not in use).
- Nearby Share Notification: DISABLED
- Location Services: ALL DISABLED
Developer Options:- Allow window-level blurs: DISABLED
- Background Check: DISABLED
- Suspend execution of Cached apps: ENABLED
- Animation scale (3 entries) : x0.5
- Logger Buffer Sizes: OFF
- Predictive Back Animations: ON
Camera Settings- Turn off location permission for the camera app.
- Face Beautification: DISABLED
- Video Stabilization: DISABLED
- Video Resolution: 4K30
- Social share: DISABLED.
- Google lens suggestions: DISABLED
Advanced
- Show dirty lens warning: DISABLED
- Store videos efficiently: DISABLED
Google Play Store Settings- Google Play Protect: DISABLED
- Autoplay: DISABLED
- Auto Update Apps: DISABLED
- App Installation Optimization: DISABLED
Google Chrome SettingsSettings
- Page Preloading: DISABLED
Chrome Flags
- Smooth Scrolling: ENABLED
- Parallel Downloading: ENABLED
Social Media Apps Settings- Theme: AMOLED/DARK
- Autoplay videos: DISABLED
- Log out of all Old sessions.
- Delete old logged in devices.
Spotify Settings- Canvas: DISABLED
- Gapless: ENABLED
- Normalize volume: DISABLED
- Device broadcast status: DISABLED
- Spotify connect in the background: DISABLED
Add "Sync" Quick Toggle- Download Quick Settings
- Enable it under "System no root"
- Add the tile normally through the edit button
GENERAL FIXESDiagnose Your Problem- Go to Device care, battery, check your battery usage. If nothing shows, it's battery leak.
Fix Battery Leak (IMPORTANT)- Go to Permission Manager, enable "Show system apps" and check for any excess permissions, especially hardware like location, camera or nearby devices.
Fix Battery Calibration- Use your phone normally till it dies off automatically.
- Plug it into the charger and leave it charging for 2h while it's still off.
- Turn it on, calibrate the battery then unplug your phone and use it normally until it dies again.
- Plug it into the charger and leave it charging for 2h while it's still off.
- Turn it on, calibrate the battery again and unplug it, enjoy
Fix Google Apps Battery drainGo to Settings, Apps. Enable "Show system apps" then look for each of:
- Google Play Store
- Google Services Framework
- Google Play Services
- Android System WebView"
Uninstall Updates, Clear data & Cache, Force Stop, Reboot, update and follow setup.
Fix Camera Experience- Wipe Data & Cache, reboot to Safe mode, do it again, then reboot normally.
Fix OLED Burn-in/Ghosting- Download LCD Burn-in Wiper
- Disable Auto-brightness & set Brightness to 100%
- Leave on for at least 1 hour
Fix Speaker crackling- Download Speaker cleaner
- Set your volume to max
- Put your phone face down & launch
Remove Ads System-WideGo to settings, connections, more connections settings, look for Private DNS.
- dns.adguard-dns.com or dns.adguard.com
- Close all apps then reboot.
Apps Alternatives- Apps list
What's wrong with Adaptive Battery? AFAIK it just slows down charging through the night when u have alarm turned on.
reas0n said:
What's wrong with Adaptive Battery? AFAIK it just slows down charging through the night when u have alarm turned on.
Click to expand...
Click to collapse
That's adaptive charging you're describing
What kind of battery improvement/screen on time can we expect from these optimizations? I'm currently getting 6-8h of screen time or 40~ hours of standby with 4~ hours of screentime.
devilsshadow said:
What kind of battery improvement/screen on time can we expect from these optimizations? I'm currently getting 6-8h of screen time or 40~ hours of standby with 4~ hours of screentime.
Click to expand...
Click to collapse
All kinds actually, from smoother phone to longer battery life.
I wouldn't follow this guide, especially since it recommends malware (ccleaner hasn't been good for a looooong time).
There's also no need for draining your battery until the phone turns off multiple times to "calibrate" it, and disabling stuff that many people find useful (like location for Maps)... going through ADB to turn off settings available through the UI is also strange... Seems like snake oil.
Reserved
rydare said:
I wouldn't follow this guide, especially since it recommends malware (ccleaner hasn't been good for a looooong time).
There's also no need for draining your battery until the phone turns off multiple times to "calibrate" it, and disabling stuff that many people find useful (like location for Maps)... going through ADB to turn off settings available through the UI is also strange... Seems like snake oil.
Click to expand...
Click to collapse
Then don't .
rydare said:
I wouldn't follow this guide, especially since it recommends malware (ccleaner hasn't been good for a looooong time).
There's also no need for draining your battery until the phone turns off multiple times to "calibrate" it, and disabling stuff that many people find useful (like location for Maps)... going through ADB to turn off settings available through the UI is also strange... Seems like snake oil.
Click to expand...
Click to collapse
Agreed. CCleaner is garbage malware and most of the tips cripple your device's capabilities. One example from the rec'd settings... Turn off WiFi/Bluetooth scanning/GPS. Sure you'll save battery.. at the expense of losing location results. Also many apps require GPS permissions so this suggestion isn't even really practical.
Battery Calibration Pro? Hasn't been updated since 2017. If you want to know what's going on with your battery get a relevant app like Ampere. And why do we even need to "calibrate" our batteries?
And many of the apps listed in PixelSafe.txt marked as "bloatware" are definitely not safe to uninstall..
com.android.omadm.service
com.google.android.ims
com.google.android.carrier
Good luck using your phone without these.
And if AppControl OP is suggesting to use to uninstall the listed apps is doing so by modifying system partition say goodbye to passing safetynet.
100% do not use anything suggested here lol
bobbarker2 said:
Agreed. CCleaner is garbage malware and most of the tips cripple your device's capabilities. One example from the rec'd settings... Turn off WiFi/Bluetooth scanning/GPS. Sure you'll save battery.. at the expense of losing location results. Also many apps require GPS permissions so this suggestion isn't even really practical.
Battery Calibration Pro? Hasn't been updated since 2017. If you want to know what's going on with your battery get a relevant app like Ampere. And why do we even need to "calibrate" our batteries?
And many of the apps listed in PixelSafe.txt marked as "bloatware" are definitely not safe to uninstall..
com.android.omadm.service
com.google.android.ims
com.google.android.carrier
Good luck using your phone without these.
And if AppControl OP is suggesting to use to uninstall the listed apps is doing so by modifying system partition say goodbye to passing safetynet.
100% do not use anything suggested here lol
Click to expand...
Click to collapse
Im going to call bull**** on you here
Ive had omadm disabled for over 2 months with zero issues
OMA DM server development cooperation in the air, mobile phones and wireless devices to provide remote configuration, configure and update device management (DM) client enables operators and handset manufacturers outbreak system dependencies between DM tight.
if you can explain exactly why something should not be disabled and why it will cause a bootloop or failure to boot great.
if you are just blowing smoke out your ass because you think your phone should wipe your ass for you and everyone else.
then go away you are not helping the discussion.
i also dont think any non opensource app should be used as snake oil to fix issues unless we know exactly how it works.
people should always do their own research on everything, XDA is not for sheep following a guide word for word because they don't understand why things work or don't work
bobbarker2 said:
Agreed. CCleaner is garbage malware and most of the tips cripple your device's capabilities. One example from the rec'd settings... Turn off WiFi/Bluetooth scanning/GPS. Sure you'll save battery.. at the expense of losing location results. Also many apps require GPS permissions so this suggestion isn't even really practical.
Battery Calibration Pro? Hasn't been updated since 2017. If you want to know what's going on with your battery get a relevant app like Ampere. And why do we even need to "calibrate" our batteries?
And many of the apps listed in PixelSafe.txt marked as "bloatware" are definitely not safe to uninstall..
com.android.omadm.service
com.google.android.ims
com.google.android.carrier
Good luck using your phone without these.
And if AppControl OP is suggesting to use to uninstall the listed apps is doing so by modifying system partition say goodbye to passing safetynet.
100% do not use anything suggested here lol
Click to expand...
Click to collapse
PLEASE, READ OP CAREFULLY BEFORE COMMENTING. THANK YOU- CCleaner does the job, also, uninstalling it right after you're done using it is a key step.
- Doesn't matter when has it been updated, it does the job.
- I actually have a pixel 6, and those apps listed are ALREADY UNINSTALLED for me, and i'm running fine as you can see .
- Bootloader locked, no root, and you're worried about system partitions ? And safetynet too ?
- OMADM was shipped disabled for me, i never needed to take it out.
- Literally NO ONE forced you to do what i said, all of those are suggestions, feel free to do, or not do them.
- You don't like my suggestions ? Skip them, go away, don't come posting nonsense, please, i want to keep my thread clean of bull****.
- 100% nobody asked your opinion.
nutzfreelance said:
Im going to call bull**** on you here
Ive had omadm disabled for over 2 months with zero issues
OMA DM server development cooperation in the air, mobile phones and wireless devices to provide remote configuration, configure and update device management (DM) client enables operators and handset manufacturers outbreak system dependencies between DM tight.
if you can explain exactly why something should not be disabled and why it will cause a bootloop or failure to boot great.
if you are just blowing smoke out your ass because you think your phone should wipe your ass for you and everyone else.
then go away you are not helping the discussion.
i also dont think any non opensource app should be used as snake oil to fix issues unless we know exactly how it works.
people should always do their own research on everything, XDA is not for sheep following a guide word for word because they don't understand why things work or don't work
Click to expand...
Click to collapse
As i already stated in the past post, those apps are already uninstalled on my phone and i don't have any problem. Everything is working as intended, but with less heat, faster charging and better battery life
OMA DM and it's associated apps are frozen out of the box (for my carrier anyway). Can't speak for all carriers.
Lol I just copy/pasted from where I saw in the txt to uninstall com.google.android.ims and
com.google.android.carrier.. my bad if I included one that can be removed "safely".
Though how would it be beneficial to battery life to remove a frozen system app?
You missed my point. There are apps in the txt that should never be removed or even be suggested to be removed because without them, you no longer have a phone.
This entire battery optimization guide is full of bad advice at best and changes that will break your phone. What's the point of having a phone with amazing battering life but no functionality?
Don't believe me than go ahead and disable/remove com.google.android.ims and the other ims services. See how well sms/mms/telephony work through an IP network.
Literally NO ONE forced you to do what i said, all of those are suggestions, feel free to do, or not do them. You don't like my suggestions ? Skip them, go away, don't come posting nonsense, please, i want to keep my thread clean of bull****.
Click to expand...
Click to collapse
XDA is a community with lots of people who don't have in-depth knowledge of Android. Some people may not know better.
So as a community, we also want to stop the spread of bad information. You can't post a guide for better battery life and then say "but no one look into them or question them they work 100%". That's not how things work.
And with that not wasting more time on this thread. Best of luck!
To everyone coming here, please, if you don't have serious issues with your battery, never ever drain it to 0. And over all, never ever try to start a phone with a 0% battery.
A battery is always better at 40-60%, not more, not less (you can find a lot of battery care articles on the web explaining why).
This calibration method is probably a way to solve a problem after flashing your phone with a custom ROM and after that, you see wrong battery percentage (like if your phone switch off before 3% remaining).
But please note that draining your battery to 0 will decrease its capacity permanently (and it can be by a huge amount if you insist to much). Also charging it to 100% everyday can decrease your battery life faster.
In an everyday use of your phone, it's better by a huge amount to charge your phone as often as you can and unplug it around 60-80%. You will see a difference after years.
Do you know why a new phone is around 50-60% battery when you buy it and switch it on for the first time ? Now you know
bobbarker2 said:
XDA is a community with lots of people who don't have in-depth knowledge of Android. Some people may not know better.
So as a community, we also want to stop the spread of bad information. You can't post a guide for better battery life and then say "but no one look into them or question them they work 100%". That's not how things work.
And with that not wasting more time on this thread. Best of luck!
Click to expand...
Click to collapse
The OP isn't going to love me at all. I just know I'm going to get a "nobody asked for your opinion" comment from him. He's right, nobody did ask my opinion, but that doesn't mean I'm not allowed to give it anyway. So, while I thank the OP for his enthusiasm and his attempts to provide something useful for Pixel 6 owners, I strongly advise caution in following these tweaks.
Out of the OP's list, the only things I could agree with would as follows: advertising ID, always on display, system dark mode, animation scale, and systemwide removal of ads. That last one however, I use Blokada for as I feel it's more effective.
OP should explain his reasoning behind each and every one of these changes in this list, so the people he is trying to help can understand his reasoning here. I've been mucking around the guts of Android devices since Android 2.1 and even I would like to know why he chose these things. I'd like to know because most of them seem to cripple the functions of the unit, i.e. negatively impact the Google experience. For example, gestures - gesture navigation - he says to disable. Why?
Some of these tweaks have little to no effect, could actually do more harm than good, or have better options available.
Battery Calibration - Totally unnecessary and only serves to waste battery charge cycles, which you do NOT want to do with a battery trapped in an aluminum frame between two slabs of glass. Battery calibration apps are unnecessary as the only thing they do is delete batterystats.bin, which Android automatically does upon removing the unit from a charger. This has been a known fact since around 2012.
Apps lag using CCleaner - Ignoring CCleaner's reputation since its purchase by Avast, lag from apps on a Pixel 6 is debatable. In any event, SDMaid I feel is a better option than CCleaner, especially as it functions quite nicely for debloating.
Fix OLED Burn-in/Ghosting - The disable gestures tweak could accelerate burn-in along the bottom of the display as the device would have to revert to the 3-dot navigation option. Any burn-in the screen does acquire would have to be rather light in order for an app to fix it, but so long as the wear is light an app will work. I have seen some very extreme examples of burn-in on an OLED screen, and no app would help those.
And then there is the bloatware section. Why in the hell is it that everyone and their mother still recommends deleting apps from the system partition instead of disabling them? Seriously, in the early days of Android it made sense. Now, it's only a waste of time, especially on a device whose system partitions are set to read-only in the first place. Using SDMaid or Titanium Backup and freezing, i.e. disabling, apps is far less likely to cause problems. If I recall correctly, the freezing function does not require root access to work.
My thoughts...take them as you will. Most of this stuff I won't bother with, and the things I do bother with I've already done.
I use the following :
Nova launcher pro
Appdash pro
SD Maid pro
Adaway
Modules - systemless and safety net V2.
Updated Google Pixel debloat list:- Added overlays
i smell snake oil.
Hamid Chikh said:
From the author of Complete Samsung OneUI Optimization
GENERAL BATTERY/PERFORMANCE SETTINGSTo Start With- Factory Reset.
Settings App- Adaptive Battery: DISABLED.
- Synchronization: DISABLED (turn it off again when not in use).
- Location: DISABLED (turn it off again when not in use).
- Advanced features/Gestures: DISABLED
- Bluetooth Scanning (Location services): DISABLED
- Usage & Diagnostics: DISABLED
- Advertising ID: DELETE
- Sound/Vibration feedback: ALL OFF
- Network Mode: 4G
- Always On Display (AoD): DISABLED
- System-Wide Dark Mode: ENABLED
Google Settings- Nearby connections: DISABLED
- Devices: DISABLED
- Nearby Share: DISABLED (turn it off again when not in use).
- Emergency Location Service: DISABLED
Developer Options:- Background Check: DISABLED
- Suspend execution of Cached apps (under dev options): ENABLED
- Animation scale (3 entries) : x0.5
Home Screen- Apply dark black Amoled Wallpaper
- Apply dark theme to Wallpaper
GENERAL BATTERY/PERFORMANCE FIXESBattery Calibration (Method #1)- Fully charge your phone, then use it normally till it turns off automatically.
- Wait a few minutes, try to turn it on again, to make sure it's really dead.
- Plug it into the charger and leave it charging for 2h while it's still off.
- Unplug it, turn it on, use it normally it dies again
- Wait a few minutes, try to turn it on again, to make sure it's really dead.
- Plug it into the charger and leave it charging for 2h while it's still off.
- Unplug it, turn it on, and you're done! Enjoy.
Battery Calibration (Method #2)- Download Battery Calibration Pro
- Fully charge your phone
- Calibrate
- Restart
- Unplug your phone
Other calibration methods can be found here
Fix General Battery Drain- Go to Permission Manager, check for any excess permissions, like location, camera or nearby devices.
Fix Apps Lag- Download CCleaner
- Give it all permissions required
- Delete all apps caches
- Go to apps and Force stop all apps
- Uninstall CCleaner then reboot.
Fix Google Apps Battery drainGo to Settings, Apps. Enable "show system apps" then look for each of:
"Google Play Store", "Google Services Framework", "Google Play Services", "Chrome", "WebView" & "Google App".
- Clear data & cache
- Uninstall Updates
- Force Stop
- Reboot, let them update and follow setup.
- Turn Sync Off
- Auto Update Apps: DISABLED
Fix Camera Experience- Wipe Data & Cache of Camera app, reboot to Safe mode, do it again, then reboot normally.
Fix Spotify Battery Drain- Under Spotify settings, turn off "Spotify connect in the background" (This won't stop background music playing).
Remove Ads System-WideGo to settings, connections, more connections settings, look for Private DNS.
- Set: dns.adguard.com as custom dns & save.
- Close all apps then reboot.
Fix Slow App Install TimeUnder General Google Play Store settings
- "App Install Optimisation": DISABLED
Fix OLED Burn-in/Ghosting- Download LCD Burn-in Wiper
- Disable Auto-brightness
- Set Brightness to 100%
- Launch a 2 hours session
Fix Speaker Crackling- Download Speaker cleaner
- Set your volume to max
- Put your phone face down
Fix Google Chrome- Page Preloading: DISABLED
Chrome Flags
- QUIC protocol: ENABLED
- Smooth Scrolling: ENABLED
- Parallel Downloading: ENABLED
- Auto Dark Mode for Web Content: ENABLED
Fix Reddit- Theme: AMOLED
- Autoplay videos: OFF
REMOVE BLOATWAREYou're gonna need:
- ADB AppControl (Windows)
- Samsung USB Drivers
- Latest presets attached at the bottom of this post
- You have to enable USB debugging and "Always authorise" on your phone
In AppControl
- Load "PixelSafe"
- Take a look at all what's going to be removed then unselect apps & features you need.
- Apply Uninstall while checking "delete data & cache".
- Restart your phone.
Important Notes
- Uncheck features and apps you need.
- You can always go to "Uninstall" section in AC, search and restore the features you need.
- Keep in mind that deleted apps stay in the phone and will all be restored after factory reset.
- Restore all apps before updating your phone
ADB OPTIMISATIONS#BACKUP FIRST- adb devices
- adb shell settings list global > global_stock.txt
- adb shell settings list system > system_stock.txt
- adb shell settings list secure > secure_stock.txt
If you want to check parameter's state, replace "put" with "get" and remove value.
Ex: For "animator_duration_scale"
- adb shell settings get global animator_duration_scale
Change Refresh rate- adb shell settings put system peak_refresh_rate 90.0
- adb shell settings put system min_refresh_rate 60.0
Change Animation scale- adb shell settings put global window_animation_scale 0.35
- adb shell settings put global transition_animation_scale 0.35
- adb shell settings put global animator_duration_scale 0.35
Enable Suspend execution of cached apps- adb shell settings put global cached_apps_freezer enabled
Change Adaptive Brightness Bias (1 = Brighter, -1 = Darker)- adb shell settings put system screen_auto_brightness_adj 1
Disable Gestures- adb shell settings put secure double_tap_to_wake 0
- adb shell settings put secure wake_gesture_enabled 0
- adb shell settings put secure camera_double_twist_to_flip_enabled 0
- adb shell settings put secure volume_hush_gesture 0
- adb shell settings put secure hush_gesture_used 0
- adb shell settings put secure silence_gesture 0
- adb shell settings put secure skip_gesture 0
Disable Sound Effects on Interaction- adb shell settings put system sound_effects_enabled 0
Disable Haptic Feedback- adb shell settings put system haptic_feedback_enabled 0
- adb shell settings put system haptic_feedback_intensity 0
Disable Screen Saver- adb shell settings put secure screensaver_enabled 0
- adb shell settings put secure screensaver_activate_on_sleep 0
- adb shell settings put secure screensaver_activate_on_dock 0
Enable Hidden Wifi/Data Toggle- adb shell settings put global settings_provider_model false
- adb shell settings put secure sysui_qs_tiles "wifi,cell,$(settings get secure sysui_qs_tiles)"
Stay tuned, more is coming ...
#I'M NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE
Click to expand...
Click to collapse
Bravissimo !
thanks a lot my friend !!!
Hey xda-Community!
I recently wanted to reduce my idle drain and searched for ways to edit Android Doze settings, because I remembered seeing a tutorial that said you can change deviceidle-constants, that dictate how Doze works (how fast it kicks in, how long it kicks in, light/deep doze).
I tried all those old tutorials, but I quickly realized the old ways to change the parameters are deprecated, so I asked people on android.stackexchange.com and someone actually gave me the answer (thanks Andrew) (https://android.stackexchange.com/questions/247680/is-device-idle-constants-deprecated-in-android-12).
This works from Android 12 on and is achieved using a shell.
Commands:
Note: When using an adb shell, you have to put "adb shell" before those commands. I'll just put the bare commands here, you add what you have to add.
Checking the settings:
You can check your current Doze settings (and statistics) with "dumpsys deviceidle".
Changing a setting;
Every parameter has to be set individually. It's not that bad tho, as you only have to do this once.
Syntax is: "device_config put device_idle [KEY] [VALUE]".
One example: "device_config put device_idle light_after_inactive_to 30000"
You can check "dumpsys deviceidle" to see what keys there even are. To help you out, here's an explanation of what each key actually sets. You can also get a visual sense of how the light mode and the deep mode work (not my work, thanks to easz from github).
Spoiler: My recommended settings
First; reset parameters with: "device_config reset trusted_defaults device_idle"
light_after_inactive_to 30000
light_pre_idle_to 120000
light_idle_to 300000
light_idle_factor 2
light_max_idle_to 900000
light_idle_maintenance_min_budget 30000
light_idle_maintenance_max_budget 180000
inactive_to 900000
sensing_to 0
locating_to 0
motion_inactive_to 0
idle_after_inactive_to 900000
idle_pending_to 60000
max_idle_pending_to 120000
idle_pending_factor 2
idle_to 900000
max_idle_to 21600000
idle_factor 2
wait_for_unlock true
I also wrote a windows batch script (works via adb, you have to rename the .txt file to .bat) and a bash file that changes the parameters to my recommendations. See attachments.
will these settings persists even after a reboot? or upgrading rom?
maxs8007 said:
will these settings persists even after a reboot? or upgrading rom?
Click to expand...
Click to collapse
yes, these will stick after a reboot. Not sure about upgrading, but I would guess that it'll stay, because we don't actually modify anything on the system partition
@Doomkopf for me those settings won't stick.
For testing purpose I just applied those yesterday morning:
adb shell device_config put device_idle motion_inactive_to 300000
adb shell device_config put device_idle light_after_inactive_to 180000
This morning they are back to stock values. Any ideas? :S
Utini said:
@Doomkopf for me those settings won't stick.
For testing purpose I just applied those yesterday morning:
adb shell device_config put device_idle motion_inactive_to 300000
adb shell device_config put device_idle light_after_inactive_to 180000
This morning they are back to stock values. Any ideas? :S
Click to expand...
Click to collapse
I set mine like 6 weeks ago, it's still set. I miss many information, what phone do you use, what ROM, how you check if it's still set etc
Doomkopf said:
I set mine like 6 weeks ago, it's still set. I miss many information, what phone do you use, what ROM, how you check if it's still set etc
Click to expand...
Click to collapse
Hi, oh well here are some more infos:
Pixel 6 Pro
Latest Android 13 Stock ROM
Kirisakura Kernel
I check via "adb shell dumpsys deviceidle".
I set it all your settings on friday and today (monday) there are back to stock values.
Previously I tried settings my own settings on wednesday morning and had stock values on the next day already as well :S
Utini said:
Hi, oh well here are some more infos:
Pixel 6 Pro
Latest Android 13 Stock ROM
Kirisakura Kernel
I check via "adb shell dumpsys deviceidle".
I set it all your settings on friday and today (monday) there are back to stock values.
Previously I tried settings my own settings on wednesday morning and had stock values on the next day already as well :S
Click to expand...
Click to collapse
That doesn't sound good I'd check right after setting it, so you can see if it was changed at all (which I assume). If it indeed gets set and unset again, you could check this github repo (https://github.com/easz/doze-tweak) at "Caveat".
Those values got reset in the past already, but as it didn't happen to me, I thought Google stopped doing that. Maybe that old workaround still works Otherwise, you'll have to flash a custom rom I guess xD
EDIT: I also recommend looking at values easy to distinguish. For example, "sensing_to" and "locating_to" were nonzero before, now they are zero (for me), so these values are easy to compare for me. The values you need to look at are at the most upper part of the output, but I guess you already knew that
Doomkopf said:
That doesn't sound good
Click to expand...
Click to collapse
Did you ever mess with any other settings using device_config before? Like the number phantom processes, empty or cached processes, ActivityManager tweaks or anything else? Because I assume you did (and using Android 10 or higher) and disabled the settings sync back to the defauls.
Did you ever use the below command?
device_config set_sync_disabled_for_tests persistent
What does the below commands says?
device_config is_sync_disabled_for_tests
Perhaps it says true? If yes that's why your settings aren't changing.
crok.bic said:
Did you ever mess with any other settings using device_config before? Like the number phantom processes, empty or cached processes, ActivityManager tweaks or anything else? Because I assume you did (and using Android 10 or higher) and disabled the settings sync back to the defauls.
Did you ever use the below command?
device_config set_sync_disabled_for_tests persistent
What does the below commands says?
device_config is_sync_disabled_for_tests
Perhaps it says true? If yes that's why your settings aren't changing.
Click to expand...
Click to collapse
You quoted the wrong man
@Utini How'd it work out? If my last response doesn't help, maybe this one helps u
Doomkopf said:
You quoted the wrong man
@Utini How'd it work out? If my last response doesn't help, maybe this one helps u
Click to expand...
Click to collapse
No, logically I quoted the correct man Just wanted to indirectly tell others about the above trick / setting
Doomkopf said:
Hey xda-Community!
I recently wanted to reduce my idle drain and searched for ways to edit Android Doze settings, because I remembered seeing a tutorial that said you can change deviceidle-constants, that dictate how Doze works (how fast it kicks in, how long it kicks in, light/deep doze).
I tried all those old tutorials, but I quickly realized the old ways to change the parameters are deprecated, so I asked people on android.stackexchange.com and someone actually gave me the answer (thanks Andrew) (https://android.stackexchange.com/questions/247680/is-device-idle-constants-deprecated-in-android-12).
This works from Android 12 on and is achieved using a shell.
Commands:
Note: When using an adb shell, you have to put "adb shell" before those commands. I'll just put the bare commands here, you add what you have to add.
Checking the settings:
You can check your current Doze settings (and statistics) with "dumpsys deviceidle".
Changing a setting;
Every parameter has to be set individually. It's not that bad tho, as you only have to do this once.
Syntax is: "device_config put device_idle [KEY] [VALUE]".
One example: "device_config put device_idle light_after_inactive_to 30000"
You can check "dumpsys deviceidle" to see what keys there even are. To help you out, here's an explanation of what each key actually sets. You can also get a visual sense of how the light mode and the deep mode work (not my work, thanks to easz from github).
Spoiler: My recommended settings
First; reset parameters with: "device_config reset trusted_defaults device_idle"
light_after_inactive_to 30000
light_pre_idle_to 120000
light_idle_to 300000
light_idle_factor 2
light_max_idle_to 900000
light_idle_maintenance_min_budget 30000
light_idle_maintenance_max_budget 180000
inactive_to 900000
sensing_to 0
locating_to 0
motion_inactive_to 0
idle_after_inactive_to 900000
idle_pending_to 60000
max_idle_pending_to 120000
idle_pending_factor 2
idle_to 900000
max_idle_to 21600000
idle_factor 2
wait_for_unlock true
I also wrote a windows batch script (works via adb, you have to rename the .txt file to .bat) and a bash file that changes the parameters to my recommendations. See attachments.
Click to expand...
Click to collapse
Hi, currently I am using Naptime by Franco with ADB permissions. I'm not sure, but it should work by using the following options (maybe not only these, but I don't know well if there are other places where Doze options are stored):
inactive_to=2592000000,
motion_inactive_to=2592000000,
light_after_inactive_to=0,
light_pre_idle_to=30000,
light_max_idle_to=86400000,
light_idle_to=43200000,
light_idle_maintenance_max_budget=30000,
light_idle_maintenance_min_budget=10000,
min_time_to_alarm=60000,
min_light_maintenance_time=10000,
wait_for_unlock=0,
quick_doze_delay_to=86400000
It's working very well (I get 2% drain in 8 hours of sleep), but I wanted to try and improve it further, because the App tells you when and how much Doze is enforced and when maintenances are performed.
In my case, from my understanding, I don't need maintanances so often, or maybe I don't need it at all, because all the apps of which I need notifications are in non-optimized battery mode.
For reference, during night it performs 4-6 maintenances circa.
Coming to the point, I wanted to ask you I can use you settings even if they have further options like:
sensing_to 0
locating_to 0
and if I can make your settings even more extreme on some values.
For further reference, I have disabled through adb the "motion_engine", any system gesture and I have the Location always disabled (through UI shortcut, not ADB or advanced options).
NovaProspekt70 said:
Hi, currently I am using Naptime by Franco with ADB permissions. I'm not sure, but it should work by using the following options (maybe not only these, but I don't know well if there are other places where Doze options are stored):
inactive_to=2592000000,
motion_inactive_to=2592000000,
light_after_inactive_to=0,
light_pre_idle_to=30000,
light_max_idle_to=86400000,
light_idle_to=43200000,
light_idle_maintenance_max_budget=30000,
light_idle_maintenance_min_budget=10000,
min_time_to_alarm=60000,
min_light_maintenance_time=10000,
wait_for_unlock=0,
quick_doze_delay_to=86400000
It's working very well (I get 2% drain in 8 hours of sleep), but I wanted to try and improve it further, because the App tells you when and how much Doze is enforced and when maintenances are performed.
In my case, from my understanding, I don't need maintanances so often, or maybe I don't need it at all, because all the apps of which I need notifications are in non-optimized battery mode.
For reference, during night it performs 4-6 maintenances circa.
Coming to the point, I wanted to ask you I can use you settings even if they have further options like:
sensing_to 0
locating_to 0
and if I can make your settings even more extreme on some values.
For further reference, I have disabled through adb the "motion_engine", any system gesture and I have the Location always disabled (through UI shortcut, not ADB or advanced options).
Click to expand...
Click to collapse
Hey; please don't quote the whole post, it doesn't really tell me anything
I don't really understand: What do you want to know from me/what is your question? ^^
Yes, you can make some values more extreme, but you said you already did (less maintenance, more idle)
Doomkopf said:
Hey; please don't quote the whole post, it doesn't really tell me anything
I don't really understand: What do you want to know from me/what is your question? ^^
Yes, you can make some values more extreme, but you said you already did (less maintenance, more idle)
Click to expand...
Click to collapse
Hey, I'm really sorry, I'm new on XDA.
I wanted to know why you have some options valued that I don't, like for example:
light_idle_factor 2
sensing_to 0
locating_to 0
and if using them might improve even more my doze.
Also, even if I have Naptime installed, which already improved things by a lot, I wanted to know if some of my values could be improved further to avoid useless maintenances (like I said I have between 4 and 6 maintenances during night, but I barely need 1).
NovaProspekt70 said:
Hey, I'm really sorry, I'm new on XDA.
I wanted to know why you have some options valued that I don't, like for example:
light_idle_factor 2
sensing_to 0
locating_to 0
and if using them might improve even more my doze.
Also, even if I have Naptime installed, which already improved things by a lot, I wanted to know if some of my values could be improved further to avoid useless maintenances (like I said I have between 4 and 6 maintenances during night, but I barely need 1).
Click to expand...
Click to collapse
Doomkopf said:
You can check "dumpsys deviceidle" to see what keys there even are. To help you out, here's an explanation of what each key actually sets. You can also get a visual sense of how the light mode and the deep mode work (not my work, thanks to easz from github).
Click to expand...
Click to collapse
I linked a xda post that explains every value in detail (first link in second quote/my post);
locating_to and sensing_to: By the pictures (also in second quote/my post), you can see how deep doze works; before going into IDLE mode of deep doze, it goes through a sensing phase (motion detection starts) and locating phasing. Default behavior of doze is to not go sleep when you move the device. This skips this phase (time for detecting motion with sensor is 0). Same with locating; when android notices that you move the device (train, car, ...) via gps (or wifi triangulation, etc) it doesn't go to sleep. This also skips that phase
light_idle_factor 2: This multiplies light_idle_to with 2 everytime if goes thorugh a idle/maintenance cycle until it reaches light_max_idle_to. So this basically doubles your light idle time every cycle until it reaches a max duration (which you can set, I also did in my recommended settings)
In that overview you could also think about how to tweak your values so you get less maintenances during night, as you wanted. Basically you have to make both (deep and light) idle_to's longer. I recommend to increase light idle_to first (more light idle, less maintenance), before going too deep on deep sleep - sometimes your phone needs to do backups at night, etc. Dont be afraid to set a "too large" maintenance window, your phone won't suddenly start to draw much power for nothing. You just have a few seconds/minutes less deep sleep (which is ok, little percentage). Give it something like 2 minutes per night, if you're afraid a backup will take longer, you can even go for 3-4 minutes per night.
Doomkopf said:
I linked a xda post that explains every value in detail (first link in second quote/my post);
locating_to and sensing_to: By the pictures (also in second quote/my post), you can see how deep doze works; before going into IDLE mode of deep doze, it goes through a sensing phase (motion detection starts) and locating phasing. Default behavior of doze is to not go sleep when you move the device. This skips this phase (time for detecting motion with sensor is 0). Same with locating; when android notices that you move the device (train, car, ...) via gps (or wifi triangulation, etc) it doesn't go to sleep. This also skips that phase
light_idle_factor 2: This multiplies light_idle_to with 2 everytime if goes thorugh a idle/maintenance cycle until it reaches light_max_idle_to. So this basically doubles your light idle time every cycle until it reaches a max duration (which you can set, I also did in my recommended settings)
In that overview you could also think about how to tweak your values so you get less maintenances during night, as you wanted. Basically you have to make both (deep and light) idle_to's longer. I recommend to increase light idle_to first (more light idle, less maintenance), before going too deep on deep sleep - sometimes your phone needs to do backups at night, etc. Dont be afraid to set a "too large" maintenance window, your phone won't suddenly start to draw much power for nothing. You just have a few seconds/minutes less deep sleep (which is ok, little percentage). Give it something like 2 minutes per night, if you're afraid a backup will take longer, you can even go for 3-4 minutes per night.
Click to expand...
Click to collapse
Thank you very much, very helpuful!!
Based on your information, I think I understand better how Naptime works. It increases the parameters of Light Doze making them similar to those of Deep Doze, and also increases the duration.
Wouldnt it be easier to just create a routine or mode ?
Like when I am around my work place I have set it to turn wifi off so it dont keep scanning for wifi and stuff.
I personally feel with Samsung most things can be controlled within their phone and developer settings and not to mention their add on apps like Good Guardian and Good lock.
tfn said:
Wouldnt it be easier to just create a routine or mode ?
Like when I am around my work place I have set it to turn wifi off so it dont keep scanning for wifi and stuff.
I personally feel with Samsung most things can be controlled within their phone and developer settings and not to mention their add on apps like Good Guardian and Good lock.
Click to expand...
Click to collapse
I do use Samsung Routines to Enable Offline Mode and Battery Saving at night, which along with Naptime gives me 2% used battery in 8 hours over night, but during the day I can't find a good usage for it.
tfn said:
Wouldnt it be easier to just create a routine or mode ?
Like when I am around my work place I have set it to turn wifi off so it dont keep scanning for wifi and stuff.
I personally feel with Samsung most things can be controlled within their phone and developer settings and not to mention their add on apps like Good Guardian and Good lock.
Click to expand...
Click to collapse
I don't know what it would be easier as; this method?
This basically just configures doze to better fit your needs. It already had values in it before and it was activated before. You can (and should) do all this and still create a routine or mode additionally.
Doze is android's main internal battery saving feature, so tweaking it goes a long way.