Database Develop

[Fix/Tips] Battery drain and performance problems

Hello guys, I want to try to help everyone who has problems with battery life and performance.
First of all, I want to say that you shouldnt have any problems if you use your device in a normal way(calling ,social networking apps, playing light games etc)
A SOT of around 4-5h on mobile network or a SOT of 5-6h on WiFi is really good and in my opinion normal and you shouldnt need to worry about. Over night while you are sleeping (8h for example) your battery shouldnt drain more than 3-5%.
If you have much less SOT or much more battery drain over night, you should read the following steps and try them.
(I can tell you that my OP3 never drains more than 3-4% over night and I have no problem getting 4-5h SOT on mobile network or 5-6h or even more on WiFi use only. I have to say I dont use Facebook or twitter for example, but I have my Bluetooth always turned on because i use a mi band)
Please try the following steps and tell me if it did help you. (Please choose one option in the pool)
1. Activate doze mode and aggressive doze mode in developer options and change the animation scale
- Go into settings -> developer options -> Doze mode -> activate it
- Go into Settings ->Battery ->3 Dots Menu ->Agressive doze & app hibernation ->Tap the slider and activate for apps
- Go into settings -> developer Options -> Window Animation scale/Transitions Animation scale/Animator duration scale -> set them to .5x or even off
2. Install Greenify from Google Play Store and activate it
Activate it for every app you can, except for apps with a little blue cloud as they need to work in background to sync data. (WhatsApp for example)
3. Wipe cache after every update and from time to time (I recommend once a week)
Turn off your phone -> hold power button and volume down button -> release the power when your phone turns on -> select english by pressing the volume down button and then the power button -> go to wipe cache and data -> select cache (and nothing else!) and press the power button -> reboot now
4. Turn off potential power hogs you dont necessarily need
- For example turn off Bluetooth, GPS Location and Location history, Mobile Data if not in use, WiFi if not in use and NFC -> you can find them in settings under their name
- Also turn off things like gestures in settings: Go into settings -> Gestures -> turn them off
5. Use pocket mode
Settings -> Advanced -> Pocket Mode
6. Turn off Android Device Manager and Google Now Cards
- Settings -> Security & Fingerprint -> Device Administrators -> Android Device-Manager -> turn it off
- Open your Google App -> Settings -> Your Feed -> Turn off Feed
7. Configure your WiFi
- Settings -> Wifi -> tap the gear symbol -> turn off "Scanning always available"
- You can also turn off "Keep wifi on during sleep" but i dont recommend it as apps like WhatsApp will only receive messages when you turn your screen back on!
8. Use adaptive brightness
Use the little "A" in the dropdown settings menu next to your screen brigthness bar
9. Use a Browser that is developed for Snapdragon devices
I recommend using Gello Mod or TugaBrowser as they are developed especaily for using with a device with a snapdragon CPU to save battery -> just search for them in Google
10. Disable permissions of apps
Try disabling permissions of apps if possible. This should prevent apps from using your internet connection and staying in background keeping your CPU awake. Please be aware that some specific apps need some specific rights to work properly. Use the try and error method here.
11. If u have custom recovery installed you can use custom kernels such as ex kernel ,boeffla kernel, blu spark etc for better battery and performance.
Link to ex kernel
https://forum.xda-developers.com/oneplus-3/development/kernel-elementalx-op3-0-01-t3404879
Link to boeffla kernel
https://forum.xda-developers.com/oneplus-3/development/kernel-boeffla-kernel-xx-09-2016-t3455467
Link to blu spark kernel
https://forum.xda-developers.com/oneplus-3/development/kernel-t3404970
12.AKT are is another way to save battery and performance tweaks.(requires root)
Link to thread of AKT
https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589
13.Have a look at this thread too
https://forum.xda-developers.com/oneplus-3/how-to/potential-fix-cpu-battery-drain-aosp-t3543369
If you follow these 10(Normal everyone can do)+3(require twrp/root) simple steps you should not have any problems with battery life or performance.
If you need any further help please ask and please share your suggestions and results!
Source one plus forums , XDA and me
This is a big guide and it's worth reading
Hit the thanks button if this helps:good:

These tips are like from 2010 which you come across random articles from web.. I thought you would post something new...
Also 3h sot on mobile network... I have used couple of phones past year never got such a bad backup on any of them..

Really stupid article.
For OB9 and above, what i have found that if you are using both greenify and aggressive doze, battery would drain like hell, Android System used to be always on top of stats with 25-30% of drain. Disabling aggressive doze and just using greenify solved this issue, and now Android System is back to normal.

pls guys, he trying to help .
if it works thanks him, if not find other tips
dont be so rude :fingers-crossed:
Sent from my OnePlus3 using XDA Labs

Wipeing is not necessary if not dump cause the phone has to build it up again and will use resources for that.

Thanks man, in my opinion, it's a good guide for beginners I'm not a beginner, I've just created a new user name

Thanks for sharing all these tips and references. As some mentioned I'd refrain or at least keep greenify as a last resort. Cheers

Is my developer options back to default?

Hi,
I have unlocked a developer options by clicking 7 times firmware compilation number. Than a go to developer option to check what can I change in my phone. When I was scrolling down I've notice that some of options were ON. Than I decide to change nothing. When I press slider at the top to set OFF and hide developer options some of option before set as ON goes OFF. My question is: if by clicking OFF at the top of developer options all setting back to default? If yes. why some of that was set ON when I unlocked developer options at first?

Well some options are on by default, like the automatic update... the default would be on, regardless for developers options turned on or off. Once in developer mode, some developers would like to freeze these updates while working/developing for the phone, hence you have the option now to turn it off in developer mode. Same for the wifi data option thing.

How to bring them back to default? Or maybe some of you can post screenshots with default developer options like it was fabric. Thank you.

lucas0 said:
How to bring them back to default? Or maybe some of you can post screenshots with default developer options like it was fabric. Thank you.
Click to expand...
Click to collapse
Just turn developer options off.

If you turn off developer options, the menu vanishes as well.
This will also reset the settings.
You can bring it back the usual way, which will turn it on again.

Accidental touches

Hi,
I'm starting to get really frustrated with my S10! When I have it in my pocket it's registering touches even though I'm not even touching my pocket I have my phone in.
I just got back home from my local gym and while I was exercising it has sent a photo from my gallery to different people on Facebook, even people from other places in the world who is not on my friend list.
I have enabled the option in settings to avoid accidental touches and the increased sensibility option is disabled as well and so is the raise to wake option.
Any ideas on how to solve this?

Heya,
I think that's an issue with all Samsung devices running on Android 9. Its actually the Fingerprint icon and/or double tap to wake up feature.
Try doing the following :-
1> Go to Settings > Advanced Features > Motion and Gestures and then turn off "Double Tap to Wake".
2> Go to Settings > Biometrics and Security > Fingerprints then Turn off "Show icon when screen is off".
If that still doesn't works, go to the same settings page in Step 1, and turn off "Lift to Wake Up" too.
Let me know if it works out for you.
Regards,
Ankit S.

Pr0Ankit said:
Heya,
I think that's an issue with all Samsung devices running on Android 9. Its actually the Fingerprint icon and/or double tap to wake up feature.
Try doing the following :-
1> Go to Settings > Advanced Features > Motion and Gestures and then turn off "Double Tap to Wake".
2> Go to Settings > Biometrics and Security > Fingerprints then Turn off "Show icon when screen is off".
If that still doesn't works, go to the same settings page in Step 1, and turn off "Lift to Wake Up" too.
Let me know if it works out for you.
Regards,
Ankit S.
Click to expand...
Click to collapse
Thanks for the great answer, I will give it a try

Themes / Apps / Mods [App] Fix of buggy proximity sensor - Locking screen from being pressed during phone call

Note: app compatible with any phone with 1080x2400 screen or lower. Probably higher too, try it. Also it's impossible to make such block when talking in messengers (more precisely, it's difficult). App won't work without gapps, rare case.
Instead of classic reliable optical sensor we have sucky ultrasonic one.
Sometimes it does not turn off the screen while phone call and something is pressed with ear or cheek up to dropping call.
Popular workaround is app "Call Proximity Sensor Fix" which automatically turns off the screen. Or you can press the power button immediately after the answer.
But IMHO this is inconvenient because if you need to look at something on the screen it will not turn on by itself which is so familiar.
My simple application makes screen insensitive to taps. And unlike analogs soft buttons and status bar are blocked too (but not gestures).
On screen will be translucent button that disables lock if you need to use the phone:
– Long tap on button - unlock (button will turn green)
– Short tap when unlocked - lock again
– Long tap when unlocked - remove button at all so as not to interfere with e.g. for entering text
When second call comes in screen will automatically unlock so you can easily answer or hang up. Then it blocks again.
When manually launching the application there will be a question whether to enable 4 seconds delay for an outgoing call. So you able to choose SIM card.
Made by powerful Tasker, the project was exported as standalone application via App Factory. Implemented via scenes with new full-screen blocking type.
Location of button adapted for default AOSP / Google Dialer. It can be misplaced for third-party dialers and / or interface scale. It's impossible to cover all possible variants. So if it really bothers you, install Tasker and project below. Then change coordinates of the buttons.
Installation
Follow manual carefully, otherwise nothing will work.
Application is safe and doesn't have internet access.
1. Download APK below this post
2. Install it via file manager and launch
3. Answer the question about delay, decision can be changed later by launching app again
4. Open Settings > Apps & Notifications > In-Call Screen Lock
5. In "Notifications" turn off them all completely, otherwise they will be annoy you
6. In "Permissions" enable everything: Contacts, Call List and Phone
7. MIUI: right there in application settings enable "Autostart"
8. MIUI: and in "Background" select "No restrictions"
9. Custom: Settings > Apps & Notifications > Advanced > Special app access > Battery optimization > All apps > In-Call Screen Lock > Don't optimize
10. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
11. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
12. Settings > [MIUI: Advanced settings] > Accessibility > In-Call Screen Lock > enable "Use In-Call Screen Lock"
If you using Tasker
1. Download ZIP archive below this post
2. Extract file from it to phone/Tasker/projects
3. Tap on "House" icon at the bottom > Import Project > In-Call_Screen_Lock
4. If you don't need a delay on an outgoing call: delete / disable action #3 ("Wait") from the "In-Call Lock Start" task
5. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > Tasker > Allow display over other apps
6. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > Tasker > Allow display over other apps
7. Settings > [MIUI: Advanced settings] > Accessibility > Tasker > enable "Use Tasker"
UPD: files updated, fixed small bug.

does this affect battery life

shakeelbirmani said:
does this affect battery life
Click to expand...
Click to collapse
No.

Tested now on my RN10-pro... works just fine! Thank you!

Tested without gapps and it didn't work. I use the standard phone app from Arrow OS. I do all settings from your instruction.
There was no 4 seconds query of the sim card. The and no lock screen button.

Social_Work said:
Tested without gapps and it didn't work.
Click to expand...
Click to collapse
Unfortunately, APK's exported by Tasker always have dependencies from GMS no matter actions it should perform. Sorry, I can't fix that.

I reinstal Arrow with Gapps and Install tasker. IT works great! Thx a lot! Now ist this Phone uesable.

Great application. Tested it via Tasker and works. Thank you so much!
Small question, if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again. How do I get the button back then?

Note: sensors are automatically calibrated and sometimes this creates a problem.
To cleanup and recalibrate the sensors, all you need to do is this:
Bash:
# dd if=/dev/block/by-name/persistbak of=/dev/block/by-name/persist conv=notrunc
For me that solved everything on official MIUI V13.0.12.0 (and previously on V12.5.9.0).

Amazfit User said:
if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again
Click to expand...
Click to collapse
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
Zibri said:
sensors are automatically calibrated and sometimes this creates a problem
Click to expand...
Click to collapse
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.

Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
Thanks for the information. Tested it and ticking the block overlay + fixes the issue. I guess it's because even though I'm able to tap the icon and other call icons the phone is still locked. I guess the overlay + makes sure that the lock off scene is still visible on the "lock" screen. I'm on Samsung One UI 4.1 with the native Google dialer.
Thanks for the help.

Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
ultrasonic sensor can be even manually calibrated and the calibration is indeed stored and used.
Also: the ultrasonic sensor works in software, relying also on the position and angle of the phone.
If that measurement fails or is inaccurate, everything is ruined.
Trust me: try to do a fastboot flash of V13.0.12.0 then reset that partition as I said.
Then you can tell me if it improves or not.
For me now it works perfect both in DUO both in the stock dialer and messenger.

You can find the latest stock firmwares here:
Codes and study of the Redmi Note 10 PRO (SWEET) and some findings
code name 76937 com.miui.powerkeeper.cloudcontrol.CloudUpdateReceiver 8437625 com.miui.powerkeeper.thermalconfig.ThermalConfigReceiver 37263 com.miui.powerkeeper.ui.framerate.FrameRateSecretCodeReceiver 2877...
forum.xda-developers.com

AOD off task when face down

Can somebody help me with a task to turn off aod when face down or in pocket on a samsung s21 FE?
Thanks!

Not bullet proof but you can give it a try...........
creat a new task > custom setting > system > aod_mode > value 0
create a new profile > find sensor or gesture > find face down
add the above task to the profile.
** you can reverse aod on I believe is using value 1

eeeemc said:
Not bullet proof but you can give it a try...........
creat a new task > custom setting > system > aod_mode > value 0
create a new profile > find sensor or gesture > find face down
add the above task to the profile.
** you can reverse aod on I believe is using value 1
Click to expand...
Click to collapse
Sadly it doesn't work.
But thanks

last resort ............
same as previous nmethod but change aod_mode to:
aod_tap_to_show_mode
use value 0
Actually I'm on Samsung A71 and using such methods
Mrawy said:
Sadly it doesn't work.
But thanks
Click to expand...
Click to collapse

eeeemc said:
last resort ............
same as previous nmethod but change aod_mode to:
aod_tap_to_show_mode
use value 0
Actually I'm on Samsung A71 and using such methods
Click to expand...
Click to collapse
It doen't work, maybe I need to give tasker some permissions trough adb?

Mrawy said:
It doen't work, maybe I need to give tasker some permissions trough adb?
Click to expand...
Click to collapse
I'm not sure if extra permission is required as not in my case.
May be try below experimental task if it works so that it proofs tasker custom settings is available on your device :
custom settings > system > blue_light_filter > value 1
This turn on Samsung's reading mode and if you manually hit play button from within tasker after you create this blue light test task , then you check from the dropdown tilt to see if the blue light icon is on or not.
if it is on , means custom setting is availble on your device without extra permission.
if this is the case , use custom setting to use the 'FIND' button step-by-step go to AOD on/off menu and set it. ( hope you know custom setting has 'FIND' function to manually choose the require action in your case is to find the AOD )

On Huawei P30 Pro, to disable AOD make task like a photos in attachment.
To use this task You Need use ADB DEBUGGING and Tasker Permissions app or adb command. Read more:
https://tasker.joaoapps.com/userguide/en/help/ah_secure_setting_grant.html

I toggle my AOD on my Samsung device. It's just as the first reply said.
custom setting > system > aod_mode > value 0 to turn it off, and 1 to turn it on.
To test the adb setting on your device, just create a simple task that toggles AOD. EG when you are connected to wifi, set it off, or somethign else you can use to easily test.
If that works (which it should), then it's the sensor part that has the issue.