Related
Ayo mates.
So who doesn't have battery problems? Probably everyone has. Even if you don't you'd want more ? huh ?
So after owning the phone for almost 3 months I had serious variations in battery life from 10 hours screen on to 7 hours screen on (*cough* 4.1.2) and back to 10 hours with xxdmb6 (YEAH!)
Also the screen off consumption.
So I am gonna talk about wakelocks in this thread. So what can use battery when you aren't using your phone... can also use the battery when you are using it. So fixes or possible fixes should improve the total battery life as well.
This thread is divided into 3 parts - basic tips , wakelock fixes and advanced fixes.
Install BetterBatteryStats. This is gonna monitor the wakelocks and the elements that drain the battery.
Tip 1 - (Install CurrentWidget) If you keep charging the battery even after it has reached 100% you will see that the battery continues to accept charge. This is true. If you charge the battery till it stops accepting power(by monitoring it through currentwidget) you will see that 100% lasts for a long time. i mean that suppose your phone uses 1% battery per 10 minutes, now if you just unplug and start using the phone, it will stay at 100% for a long time.
But this may even damage your battery. I am not sure. I do it considering how much technology has advanced.
Tip 2 - So from wanam's thread -
wanam said:
Disable auto sync for accounts if you don't need it
Disable GPS (and wifi gps) when not in use
Disable auto backup of Google account
Set brightness level to automatic
Disable motion if you don't use it
Check your apps settings and disable useless background sync
Disable useless animations
Click to expand...
Click to collapse
List of general Wakelocks -
PowerManagerService - It is a sum up of partial wakelocks.
MultiPDP - This indicates a high network usage(2g/3g/4g).
AlarmManager -
AlarmManager provides access to the system alarm services. These allow you to schedule an application to be run at some point in the future. When an alarm goes off, the Intent that had been registered for it is broadcast by the system, automatically starting the target application if it is not already running. Registered alarms are retained while the device is asleep (and can optionally wake the device up if they go off during that time), but will be cleared if it is turned off and rebooted. The Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. This guarantees that the phone will not sleep until you have finished handling the broadcast.
Click to expand...
Click to collapse
These are the findings of asksven, so have been quoted. So it is a sum up of different wakelocks again
AudioOut_2 - When apps run in the background that use sounds, this wakelock is always there.
deleted_wake_locks - A wakelock that is no more, generally when you turn wifi or data or gps on and off. But it still reflects wifi wakelock. You can sum it up as a wifi wakelock and some other wakelocks.
network-location - This is a gps wakelock.
wlan_rx - Wifi wakelock
wlan_wake - Wifi wakelock
mediaserver - when something uses media files or may even when you play heavy games like real racing 3 which uses data on internal sd card
l2_hsic - A possible explanation is unplugging the charger while phone is asleep.
I have attached a pic. You can see the difference
Wakelock Fixes
AudioOut_2 - AudioOut_2 is a major wakelock on many devices. The solution is simple. Before turning the screen off. remove all recent apps and in task manager , go to ram tab and hit clear memory. Then close task manager and swipe it away from recent apps as well. Then lock the phone. Alternatively you can download advanced task killer. (Viber seems to cause this on many devices.)
MediaServer - Flash the attached fix via a custom recovery. Someone posted this and said that he got from alliance rom ota app. I asked the Dev and he said that I can use it but it may cause a boot loop. So keep nandroid a ready. Credits go to comnam90.
Other fixes could be to download Rescan Media Root. This app fixes wakelock but it might still come up sometime.
If you are comfortable with decompiling try this.
l2_hsic - This wakelock is incorrigible. But possible fixes are in thread. I will jot down what works for me.
NetworkLocation/SignalCollector Hierarchy - Many wakelocks happen due to this maps app. This is because maps app try to update the location of the device. Modify the settings according to the image attached. But better is to disable all location services. This will also decrease AlarmManager wakelock.
But if you really don't use maps then best is to Freeze local app, maps app, navigation app. This wouldn't harm the phone as they can also be downloaded from play store which means android os can cope without it.
Processes - There are many user apps which are a necessity but eat up the battery. We can't freeze it nor uninstall it due to the need. What can we do about 'em ? This is where Greenify comes in. Don't let the uber simple UI fool you. The app is simple and self explanatory. I have greenified almost all the apps and this app doesn't eat up your battery !
I will be adding more as I find more...
Advanced Fixes
These aren't very advanced if you know what you are doing.
Try another kernel. (like perseus, uneak, redpill). I find almost similar results but it may vary as we move to the next parts
Undervolt(CPU). Believe me it will help. You should start off by reducing each voltage by 25m for each step. This requires a custom kernel and a compatible app. STweaks for redpill or perseus or uNeak Engine for uneak kernel.
Do stress tests after reducing value. It is recommended not to go below 800mV.
Thanks!
One of the best things I did to save battery is to remove Facebook and Viber.
Now I'm trying to Greenify Facebook. I hope it will not do any wake locks.
Nice article Utkarsh.
Those are general wakelocks, but there are others as well, like in the attached pic.
Btw- What's that wakelockfix.zip?
'Swyped' from my GT-N7100
jujuburi said:
Nice article Utkarsh.
Those are general wakelocks, but there are others as well, like in the attached pic.
Btw- What's that wakelockfix.zip?
'Swyped' from my GT-N7100
Click to expand...
Click to collapse
That wakelock is generic with exchange services. Remove it to get rid of it.
Well that will probably fix media server. It did for me but I will see if it comes up again.
Sent from my GT-N7100
UtkarshGupta said:
That wakelock is generic with exchange services. Remove it to get rid of it.
Well that will probably fix media server. It did for me but I will see if it comes up again.
Sent from my GT-N7100
Click to expand...
Click to collapse
Yeah, I know. But I use that on daily purpose. No question of removing it
'Swyped' from my GT-N7100
jujuburi said:
Yeah, I know. But I use that on daily purpose. No question of removing it
'Swyped' from my GT-N7100
Click to expand...
Click to collapse
Well you gotta try hampering with update settings. I am a student and not in business so email delay is not gonna hurt me at all.
It would hurt business men(that's what I derive of you) or someone whose most work is done through mails.
Nice thread, but I'd like to chime in that wakelocks aren't necessarily an absolute evil. You will always have some wakelocks, and it's supposed to be that way. Network, wifi, location services and some apps won't work properly without being able to wake the phone from time to time. It's when these wakelocks sum up to a considerable ratio of your uptime that you should begin to worry.
Might I also suggest you add greenify to your list of countermeasures.
Sent from my GT-N7100 using Tapatalk 2
UtkarshGupta said:
Undervolt. Believe me it will help. You should start off by reducing each voltage by 25m for each step. This requires a custom kernel and a compatible app. STweaks for redpill or perseus or uNeak Engine for uneak kernel.
Do stress tests after reducing value. It is recommended not to go below 900mV.
Click to expand...
Click to collapse
Is this for cpu or gpu? Thanks for the guide.
gyxter said:
Is this for cpu or gpu? Thanks for the guide.
Click to expand...
Click to collapse
Thanks should have mentioned. It is CPU.
Sent from my GT-N7100
adytum said:
Nice thread, but I'd like to chime in that wakelocks aren't necessarily an absolute evil. You will always have some wakelocks, and it's supposed to be that way. Network, wifi, location services and some apps won't work properly without being able to wake the phone from time to time. It's when these wakelocks sum up to a considerable ratio of your uptime that you should begin to worry.
Might I also suggest you add greenify to your list of countermeasures.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Greenify is already there. Check in 2nd post processes part.
Sent from my GT-N7100
UtkarshGupta said:
These aren't very advanced if you know what you are doing.
Try another kernel. (like perseus, uneak, redpill). I find almost similar results but it may vary as we move to the next parts
Undervolt(CPU). Believe me it will help. You should start off by reducing each voltage by 25m for each step. This requires a custom kernel and a compatible app. STweaks for redpill or perseus or uNeak Engine for uneak kernel.
Do stress tests after reducing value. It is recommended not to go below 900mV.
Click to expand...
Click to collapse
Hi, just one question, why not go below 900mV? Is there any reason for that? I´ve got my Note 2 uVd to these values (762, 775, 800, 825, 850, 875, 925, 950, 1000, 1050, 1075, 1125, 1150, 1175, 1250) for the frequencies from 200Mhz to 1600Mhz, I don´t think it wil harm it as I´ve been running these settings with RedPill Kernel and STweaks app for a couple of months now and I haven´t had any freezes at all or any issues, could you explain why it´s not recommended to go below 900mV? Is it just for the different tolerance to uV every chip has? Thank you anyway for your marvelous post and for the greenify app, looks promising, I´ll report how it goes since I´ve just started using it today, thanks.
thecrab93 said:
Hi, just one question, why not go below 900mV? Is there any reason for that? I´ve got my Note 2 uVd to these values (762, 775, 800, 825, 850, 875, 925, 950, 1000, 1050, 1075, 1125, 1150, 1175, 1250) for the frequencies from 200Mhz to 1600Mhz, I don´t think it wil harm it as I´ve been running these settings with RedPill Kernel and STweaks app for a couple of months now and I haven´t had any freezes at all or any issues, could you explain why it´s not recommended to go below 900mV? Is it just for the different tolerance to uV every chip has? Thank you anyway for your marvelous post and for the greenify app, looks promising, I´ll report how it goes since I´ve just started using it today, thanks.
Click to expand...
Click to collapse
Well I read somewhere. But I will update the op.
Sent from my GT-N7100
Deep sleep results....
Sent from my GT-N7100
how about just use the power-saving mode...
thanks for guide...
fly2dheaven said:
thanks for guide...
Click to expand...
Click to collapse
Welcome but plz use thanks button. It isn't about no of thanks but it helps prevent clogging of threads
Sent from my GT-N7100
Audio out 2 for me has been causing an annoying battery drain. Turns out viber is causing it for me. Yesterday it was the best part of two hours.
Today I quarantined viber and my audio out 2 dropped to 6 seconds after the phone being on for 6 hours. Half an hour ago I re started viber and my wakelock now reads 22 minutes. So I have now uninstalled viber.
How this info helps others.
arjunr24724 said:
how about just use the power-saving mode...
Click to expand...
Click to collapse
Well this doesn't hit performance.
Sent from my GT-N7100
Hello everyone!
I've been having excessive wakelocks from "wakelockmanager", check out Wakelock Detector stats on the attached image. I'm using CleanROM 1.5 with Galaxy Gear connected all the time. Anyone else experiencing this problem?
Thanks!
XanoZuke said:
Hello everyone!
I've been having excessive wakelocks from "wakelockmanager", check out Wakelock Detector stats on the attached image. I'm using CleanROM 1.5 with Galaxy Gear connected all the time. Anyone else experiencing this problem?
Thanks!
Click to expand...
Click to collapse
I've done some other tests and I only see the wakelocks when I'm connected to the mobile network (with or without data). I use my Verizon Note 3 on GSM/WCDMA.
Sent from my SM-N900V using xda app-developers app
Any follow up on this? Having the same problem all of a sudden
Do you have Android Firewall and/or XPrivacy XPosed module?
I have T-Mobile Note 3 with stock ROM and I noticed this battery drain also when I have both installed. I actually have these wakelocks within 3 hours after rebooting.
- WakelockManagertimeout (runs 808 times)
- WakeLockManager (runs 1107 times)
So maybe it is something that is universal rather than restricted to a particular model (Verizon, T-Mobile, etc.)
I actually just installed xprivacy and rebooted. So far I don't have the wakelock anymore but has it within 6 hours or so after the first reboot... Frigging strange I can't pinpoint what it is even in BBS.
fookea said:
I actually just installed xprivacy and rebooted. So far I don't have the wakelock anymore but has it within 6 hours or so after the first reboot... Frigging strange I can't pinpoint what it is even in BBS.
Click to expand...
Click to collapse
Probably the Android Firewall then. Some networking related process must be running in the background that intercept network request from the application.
However, if OP doesn't have these 2 apps, I am not sure what caused the excessive wakelocks...
Wakelock Detector quit working for me on 4.4.2. It crashes shortly after opening the app and giving it SU permissions.
i don't have Android firewall at all. I did deny some location and wakelock permissions in AppOps and it's better now. I'll post some pictures with the apps i have maybe we can compare them and find the culprit this way.
https://mega.co.nz/#!dIl3mRoa!XK4Yg1Dh-9E-AXgoA5BAIJm9qV-Y6QA2ewGU_JMuDUk
https://mega.co.nz/#!JZFm0RLY!V4Pu8elpJJN8Ufk8_k3qj-P1yoY_zruuv07wV84EM8A
https://mega.co.nz/#!tEUwVT4T!-UQPZdIGhCHgbvRvSe57l2i4ccPegRmUjDtr2OlCXoM
https://mega.co.nz/#!dF9jDDBY!sLRsk5b_Nur22gADlKx6vG7NcJ9T81lU5E0QpQXkOhA
Ignore the obvious ones like facebook and games.
I solved my issue. I ran Catlog and found that the csc was causing me a lot of wake locks. I have ORO CSC and flashed a SIN CSC. Somehow it was constantly trying something in the background. I deleted all the CSC folders except the common one and everything is back to normal. Also my Android OS and Android system are low now. The folders are located in /system/csc. I do advise backing them up in case something goes wrong.
Hope this helps
Hello to everyone. I'm using version B35. But other versions have the same problem. Often the performance is very low when the charge goes down. Performance is selected from the power manager, but I am still experiencing this problem. I think it's related to Kernel, but I can not find a solution. I am sure everyone is having this problem. Can you find a solution?
WesTD said:
Hello to everyone. I'm using version B35. But other versions have the same problem. Often the performance is very low when the charge goes down. Performance is selected from the power manager, but I am still experiencing this problem. I think it's related to Kernel, but I can not find a solution. I am sure everyone is having this problem. Can you find a solution?
Click to expand...
Click to collapse
Don't be so sure... I've been using Simple Planes @ max settings and with about 5% battery, and never got below 40-50 fps which is what i always get
Try other governors maybe? Like conservative? I usually find it better than Interactive for performance, especially concerning frame drops, as ironic as that may sound
Lately I have been struggling with some very bad battery drain. I'm a very light user. Before the Oreo update by the end of the day I would have 80% battery left. Now I'd be happy to have 40% left. I tried everything including greenify to no avail. Something keeps my phone awake. I found that a partial wakelock caused by LgeGnssLocationProvider is the culprit.
The fun part is when you google it.
Any ideas what the hell I'm supposed to do? I'm considering rooting my phone to get rid of all the bloatware. Would that also allow me to get a better insight of what is causing this wakelock?
I'm also have notice this, but the wakelock seems to be related with some LG bloatware. I have disabled multiple GNSS LG apps running in background, and that solve the issue. (i have root)
DJPRMF said:
I'm also have notice this, but the wakelock seems to be related with some LG bloatware. I have disabled multiple GNSS LG apps running in background, and that solve the issue. (i have root)
Click to expand...
Click to collapse
Which applications did you disable? I listed all the packages that contained gnss and disabled those without any luck. Worst part is, it does not always happen. Sometimes I can go the entire day without the wakelock.
I can not believe I am the only one who is experiencing this issue.
You are not the only one, I am having the same problem on my V30. Any ideas how to solve that problem??
I'm still working on figuring out what is causing the wakelock. Can't seem to find it though
I'm going to bump this again in the hope that someone sees it and know's what is going on.
Is there a way to find what triggered a wakelock?
Ortix92 said:
I'm going to bump this again in the hope that someone sees it and know's what is going on.
Is there a way to find what triggered a wakelock?
Click to expand...
Click to collapse
https://www.xda-developers.com/stop-wakelocks-android-without-root/
Flashing_Expert said:
https://www.xda-developers.com/stop-wakelocks-android-without-root/
Click to expand...
Click to collapse
I've come across this many many times but it doesn't help me. The wakelock is caused by Android System, but I want to know what exactly triggered it. Because it does not occur all the time.
Ortix92 said:
I've come across this many many times but it doesn't help me. The wakelock is caused by Android System, but I want to know what exactly triggered it. Because it does not occur all the time.
Click to expand...
Click to collapse
it's not system itself it's always some app using system interface...
posibly even some LG bloatware that uses location...
weather and so on...
Has anyone managed to solve this absurd wakelock?
Hello, there is a problem with the phone, the idle battery drain is too high, something is keeping it awake.
I've attached the screenshots of battery stats.
My mother is using the phone, so I don't have it with me all the time.
Any help is much appreciated!
adsubzero said:
Hello, there is a problem with the phone, the idle battery drain is too high, something is keeping it awake.
I've attached the screenshots of battery stats.
My mother is using the phone, so I don't have it with me all the time.
Any help is much appreciated!
Click to expand...
Click to collapse
Well Android system has lots of packages, check what packages are activated that includes ones in notification bar, GPS, NFC, Backup, Bluetooth, etc. They all absorb power at some point if they are always on it can drain the battery power. Also go to Settings / Autostart and check what packages are enabled to autostart.
hwandroid said:
Well Android system has lots of packages, check what packages are activated that includes ones in notification bar, GPS, NFC, Backup, Bluetooth, etc. They all absorb power at some point if they are always on it can drain the battery power. Also go to Settings / Autostart and check what packages are enabled to autostart.
Click to expand...
Click to collapse
This was with mobile data mostly disabled, and gps was not used heavily, as you can see from the screenshot.
I'll get back when I get more info.
Btw what I forgot to mention, the phone is brand new, like it was freshly set up a couple of days ago, and the baterry was bad since the first day.
She doesn't have a lot of apps, so it's really weird to see this battery drain.
What should I be looking for in the autostart settings?
adsubzero said:
This was with mobile data mostly disabled, and gps was not used heavily, as you can see from the screenshot.
I'll get back when I get more info.
Btw what I forgot to mention, the phone is brand new, like it was freshly set up a couple of days ago, and the baterry was bad since the first day.
She doesn't have a lot of apps, so it's really weird to see this battery drain.
What should I be looking for in the autostart settings?
Click to expand...
Click to collapse
It says Android system 34% that is too much, if you click on Android system it will list you the services and more info on power drain. For example on my device Android system does not go higher 15% usually, I have disabled autostart for the apps and services I don't really need to be running in background.
You can debloat the ROM by using xiaomi adb tools, no root needed. Then I believe battery will be much better. Search the thread in the forum
it's here, the second post
https://forum.xda-developers.com/mi-9t/how-to/debloating-mi-9t-t3958145
Also turn sync apps off automaticly.
hwandroid said:
It says Android system 34% that is too much, if you click on Android system it will list you the services and more info on power drain. For example on my device Android system does not go higher 15% usually, I have disabled autostart for the apps and services I don't really need to be running in background.
Click to expand...
Click to collapse
Yes, I've seen that it lists all the processes under Android system, but that didn't mean much, because there's a lot of them and it doesn't specify what drains the battery the most or any other details.
SUMMERBREEZE said:
You can debloat the ROM by using xiaomi adb tools, no root needed. Then I believe battery will be much better. Search the thread in the forum
it's here, the second post
https://forum.xda-developers.com/mi-9t/how-to/debloating-mi-9t-t3958145
Also turn sync apps off automaticly.
Click to expand...
Click to collapse
Perhaps the sync is on, and that might be what's causing the drain, I'll look into it.
Speaking of debloating, is there a fail safe of some kind? If something goes wrong, would a factory reset bring back the disabled/removed modules?
Thanks to both of you for the help.
I'll see if any of that fixes the issue.
adsubzero said:
Perhaps the sync is on, and that might be what's causing the drain, I'll look into it.
Speaking of debloating, is there a fail safe of some kind? If something goes wrong, would a factory reset bring back the disabled/removed modules?
Thanks to both of you for the help.
I'll see if any of that fixes the issue.
Click to expand...
Click to collapse
I think the program list only the apps that are safe to debloat and also it just disable so choose the one you don't like and leave the ones you are not sure about and if you want to know about them Google is you best friend
i have this issue as well and i think it appeared when i started using chinese vendor
adsubzero said:
Perhaps the sync is on, and that might be what's causing the drain, I'll look into it.
Speaking of debloating, is there a fail safe of some kind? If something goes wrong, would a factory reset bring back the disabled/removed modules?
Thanks to both of you for the help.
I'll see if any of that fixes the issue.
Click to expand...
Click to collapse
Factory reset would bring everything back of course but not necessary. The debloat app will bring everything back if you need. You can read many people wrote that it fixed their battery drain issue.
SUMMERBREEZE said:
Factory reset would bring everything back of course but not necessary. The debloat app will bring everything back if you need. You can read many people wrote that it fixed their battery drain issue.
Click to expand...
Click to collapse
Indeed, I believe that debloating fixed, or at least alleviated the issue.
Thanks to everyone for the help.
I haven't updated my Xiaomi Mi 9T yet to MIUI 11. And I don't have any problem with the battery on MIUI 10. Should I wait until this bug is patched to get the update ?
Hussein912 said:
I haven't updated my Xiaomi Mi 9T yet to MIUI 11. And I don't have any problem with the battery on MIUI 10. Should I wait until this bug is patched to get the update ?
Click to expand...
Click to collapse
It's hardly a bug you just have to manually configure the apps that you want to autostart in background.
Hussein912 said:
I haven't updated my Xiaomi Mi 9T yet to MIUI 11. And I don't have any problem with the battery on MIUI 10. Should I wait until this bug is patched to get the update ?
Click to expand...
Click to collapse
I would definately wait. Since MIUI 11 both my wifes and my own phone have massive drain issues. They work fine for days and all of a sudden they fully drain within a few hours without noticing any app really doing anything.
Mine is more or less fully debloated and my wifes is not but has only a few apps.
I think there is really something wrong with the update.
hwandroid said:
It's hardly a bug you just have to manually configure the apps that you want to autostart in background.
Click to expand...
Click to collapse
You know nothing. Is a major bug. Was present in miui 10 and is worse in miui 11.
So is debloat necessary again after updating to MIUI 11 (I disabled the apps, didn't remove them)?
Same finding here
(And maybe an ongoing solution)
hwandroid said:
It's hardly a bug you just have to manually configure the apps that you want to autostart in background.
Click to expand...
Click to collapse
How do I know which apps need to be autostart and which not? Example, I have sharing of my location set up with someone. How do I know if google maps needs to be autostarted, or it's handeled by some api?
It's a huge problem for me. It keeps happening and reappearing every few days.
d.a.v.o.r said:
How do I know which apps need to be autostart and which not? Example, I have sharing of my location set up with someone. How do I know if google maps needs to be autostarted, or it's handeled by some api?
It's a huge problem for me. It keeps happening and reappearing every few days.
Click to expand...
Click to collapse
Turn all off, its the same, wont break anything.
Any solutions? Happened for the first time for me too.