Related
TheManii said:
It's widely known that the s7 has pretty weak battery life.
In general all qisda dell devices do (the s5/s7/venue).
Many of the bugs exist in the phone/ril and some exist in the logging systems.
In a bug free rom these workarounds should be completely meaningless, but stock roms are not at all bug free.
Recommendation one: Enable airplane mode on wifi s7's
The wifi and 3/4g roms are nearly identical, including the fact that wifi roms still have a full RIL. It apparently is also still enabled even in wifi s7's. Turning airplane mode on while leaving wifi/bluetooth on (as desired) does in fact affect the system.
Ways of checking: with airplane mode off on mine, the s7 has major issues going into sleep mode. Even with the screen off if you check the battery graph it's still active most of the time. Airplane mode more or less fixes this.
Potential gains: 20-30% or so more life, I've only been testing this for half a day or so but it seems to be draining signifigantly slower in sleep.
Recommendation two: (this one is more valid for the s5 then the s7) Connect the s7 to a pc with the android SDK installed and run 'adb logcat'
The qisda devices are known to have far too much logging enabled and included in stock roms. Virtually all the custom roms for the s5/7 have it removed, but there is a known bug with logging.
If you run logcat so the output is directed to it, afterwards it takes care of another one of the bugs. I have not actually tested this specifically on the s7, but it likely is equally valid as the differences from AOSP (ie the customizations qisda does to the roms) are pretty similar in the s5 and s7.
Potential gains: nearly triple battery life after logcat and avoiding a yet different ril bug on the s5. The s5 can go from potentially 10%/hour to 0.3%/hour due to all/no bugs being active. The s7 MAY be a valid target too, but I havnt actually tested this one on the s7.
Roms used to compare:
S7: Stock 506-wifi
S5: Custom 406 based rom
Click to expand...
Click to collapse
Crosspost from the S7 forum, both are valid on the s5.
The largest battery bug is in the RIL, way of activing the bug: make a call. If you reboot everytime after making a call the battery life is much better then if you dont restart. Depending on how often you make calls though this is completly unacceptable to reboot after each call.
Are you saying that removing logcat daemon would give more battery life?
If I am not mistaken, that seems a obvious thing, am I wrong?
But if you remove the logcat daemon, then you can't hunt the bugs anymore, so for custom Roms that would be a very high price to pay for so little gain.
Running logcat with the device attached actually affects it. You dont remove it, you merely run it and let it write to your screen for a bit
TheManii said:
Running logcat with the device attached actually affects it. You dont remove it, you merely run it and let it write to your screen for a bit
Click to expand...
Click to collapse
So redirecting output from /dev/null to /dev/tty1 improves battery life ? Seems highly unlikely to me.
Can you explain the methodology used in your tests, bcs we can go somewhere this way, bcs s5 seems to have not a good battery life, and some strange things i have observed too in this device.
It's redirecting it to the adb console, this is why the bugs inherently make no sense as it should be otherwise discarding the log safely when not attached to adb.
But it's really consistant/reproducable on my device. Until it's attached it contributes about +2-3%/hour drain on standby.
TheManii said:
It's redirecting it to the adb console, this is why the bugs inherently make no sense as it should be otherwise discarding the log safely when not attached to adb.
But it's really consistant/reproducable on my device. Until it's attached it contributes about +2-3%/hour drain on standby.
Click to expand...
Click to collapse
2-3 % standby per hour is way too much , i am running the latest DSC 0.64b on top of 407 BB and have around 1-1.5 % , but that seems too much for me , you should check the background processes i think.
I can consistantly get 0.3/hour drain if the bugs taken care of.
If you also encounter the RIL bug you can easily hit 10%/hour possibly in combination with the log bug, it's relatively common too.
TheManii said:
I can consistantly get 0.3/hour drain if the bugs taken care of.
If you also encounter the RIL bug you can easily hit 10%/hour possibly in combination with the log bug, it's relatively common too.
Click to expand...
Click to collapse
So then something wrong with my system then, what Rom you running ?
TheManii said:
Running logcat with the device attached actually affects it. You dont remove it, you merely run it and let it write to your screen for a bit
Click to expand...
Click to collapse
I have the stock Olleh 407 ROM installed on my Streak. If I run the ADB LOGCAT with my Streak attached for a while, then the bug will be gone, even if I disconnect from my PC? Or the bug is only gone when Im connected to the ADB LOGCAT?
It's a heavily modified SD 2.4.4
The RIL bug seems to be more noticible in GB, I dont recall if it existed in 3xx roms. The logcat one is possible in 3xx or newer roms.
lunadomain said:
I have the stock Olleh 407 ROM installed on my Streak. If I run the ADB LOGCAT with my Streak attached for a while, then the bug will be gone, even if I disconnect from my PC? Or the bug is only gone when Im connected to the ADB LOGCAT?
Click to expand...
Click to collapse
It's really voodoo/magic, attaching it for <some unknown amount of time> will fix it for <some random amount of time>
For me it seems I just attach it until the battery is charged (as I would charge it anyway) and it seems to last for a day to a couple days. It's as voodoo as it sounds.
It doesnt stick past a reboot and more importantly the RIL bug is the more noticable one anyway.
It's only really noticible when the ril bug isnt active, as then you're going from 2-3% to 0.3%/hour. Going from <10% to 3% overshadows it if it's even active at all.
I cant really say for certian if it even effects everyone or happens every boot. I've been on the same rom for 2 months and have extremely consistant data with regards to these two bugs.
The logcat one is just as consistant for me on SD 19x roms.
You can also do it without SDK installed, you just need to download terminal emulator from market and enter:
su
logcat
And you are ready
At least when I do it, i use it as an opportunity to charge anyway. I always do it on my pc as I need the SDK for other things so I always have it installed.
On a custom SD244 not OCed with airplane mode and after running logcat previously with wifi turning off when screen is off:
getting 15hours @5% lost.
I'm gonna keep testing till tomorrow then install 407
Surprisingly: the s5 has even better battery life then the s10 (ignoring the differences in battery life).
The s10 has amazing battery life too.
Current results:
S5 : 31 hours = 24%
S7 : 54 hours = 48%
S10:61 hours = 13%
Normalizing their results to the size of the S10's batt:
S5: 5.17 hours each %
S7: 2.63 hours each %
S10: 4.7 hours each %
Roms used:
S5: SD 2.4.4 <2.3.3>
S7: Stock 506-wifi <3.2>
S10: Chimeradroid r2 <3.2>
The S5 can be explained by the RIL bugs as mentioned earlier, and by airplane mode is also turning off the radio too. All 3 devices were left to idle for the entirety, with only battery graph checks and no actual use.
Guys , i have a really vad problems with my battery life. After i go on to Power Rom EVG (before that i was with StreakDroid 2.4.4) my battery is absolutely not good. I do this logcat trick, just a few programs is running, auto-brighness and ... nothing! please, help!
Hello everyone I hope I got the right forum
I have a problem with the new system update released
The new update did not help at all to my nexus
I ran out of battery really fast, before the update it was fine
Battery had stayed a long time
What should I do?
1headshot said:
Hello everyone I hope I got the right forum
I have a problem with the new system update released
The new update did not help at all to my nexus
I ran out of battery really fast, before the update it was fine
Battery had stayed a long time
What should I do?
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=2385843
To get battery like this:
http://forum.xda-developers.com/showpost.php?p=44364085&postcount=5089
:cyclops:
Galaxo60 said:
Read this:
http://forum.xda-developers.com/showthread.php?t=2385843
To get battery like this:
http://forum.xda-developers.com/showpost.php?p=44364085&postcount=5089
:cyclops:
Click to expand...
Click to collapse
A quick look through that thread shows that it is focused on problems relating to Google Services. Since the update, I too am having issues with the battery draining more quickly than it ever did before. However, it appears to be msm_hsic_host wakelock causing the problem. Google services are a very small part of my battery usage.
I have posted a couple times about it in various threads, but I haven't seen a fix that applies to 4.3.
The battery drain is out of hand. I love my N4, but this is a big turn off for me.
I have tried these configurations to make sure it wasn't an oddball app causing the problem -
Stock 4.3 with stock Kernel - no root/stock recovery - Only apps being the ones that load on a factory reset
Wiped all partitions and reloaded stock 4.3/gapps/no root/stock recovery
Stock 4.3/rooted/TWRP/Stock gapps
Stock 4.3/rooted/TWRP/gapps+ a handful of other apps (photobucket/es file explorer/bbs - essentially, my normal config)
Added note - I also have cell broadcasts of all types turned off.
All of the above combinations respond the same way in regard to battery drain overnight. 7-9 hours off the charger/no screen time nets me 25-30% loss of battery from a full charge. msm_hsic shows up in BBS with 1.75 to 2.5 hours of wake time and is the highest power consumer. Putting the phone in flight mode reduces power consumption to ~2% over the same 7-9 hour timeframe. Just turning wifi off doesn't change anything.
Ideas anyone?
Calebz said:
A quick look through that thread shows that it is focused on problems relating to Google Services. Since the update, I too am having issues with the battery draining more quickly than it ever did before. However, it appears to be msm_hsic_host wakelock causing the problem. Google services are a very small part of my battery usage.
I have posted a couple times about it in various threads, but I haven't seen a fix that applies to 4.3.
The battery drain is out of hand. I love my N4, but this is a big turn off for me.
I have tried these configurations to make sure it wasn't an oddball app causing the problem -
Stock 4.3 with stock Kernel - no root/stock recovery - Only apps being the ones that load on a factory reset
Wiped all partitions and reloaded stock 4.3/gapps/no root/stock recovery
Stock 4.3/rooted/TWRP/Stock gapps
Stock 4.3/rooted/TWRP/gapps+ a handful of other apps (photobucket/es file explorer/bbs - essentially, my normal config)
Added note - I also have cell broadcasts of all types turned off.
All of the above combinations respond the same way in regard to battery drain overnight. 7-9 hours off the charger/no screen time nets me 25-30% loss of battery from a full charge. msm_hsic shows up in BBS with 1.75 to 2.5 hours of wake time and is the highest power consumer. Putting the phone in flight mode reduces power consumption to ~2% over the same 7-9 hour timeframe. Just turning wifi off doesn't change anything.
Ideas anyone?
Click to expand...
Click to collapse
As far as I know, this wakelock is caused because of the usage of 3G, like browsing, syncing, or any other thing that consumes data. This drain for me is usually between 10%-15%. There is no way t completely get rid of it, because it is part of the Android system.
There are many kernels that tried to fix this, about stock image and JW branch I don´t know, but maybe you should try to install an AOSP variant, because AOSP has many bugs fixed.
Also I remember I read somewhere that also bad radio could be causing this kind of issues, so try to get latest radio/bootloader for 4.3.
Hope it helps.
:highfive:
Galaxo60 said:
As far as I know, this wakelock is caused because of the usage of 3G, like browsing, syncing, or any other thing that consumes data. This drain for me is usually between 10%-15%. There is no way t completely get rid of it, because it is part of the Android system.
There are many kernels that tried to fix this, about stock image and JW branch I don´t know, but maybe you should try to install an AOSP variant, because AOSP has many bugs fixed.
Also I remember I read somewhere that also bad radio could be causing this kind of issues, so try to get latest radio/bootloader for 4.3.
Hope it helps.
:highfive:
Click to expand...
Click to collapse
To avoid having loose ends out there (in case anyone finds this thread during a search) - The problem turned out to be the latest radio. Not my lack of it :lol:
After flashing back to the .48 radio, from the .84 radio - everything is back to normal. No more weird Android OS wakelocks. ~3-4% battery drain overnight instead of 20-30%
There are more and more people popping up on XDA with this problem. So far, all of them that I have seen are outside the US. A few have even discovered the same fix.
So - future person that finds this thread during a search, look into the possibility of flashing back to version .48 of the radio. Hopefully this saves someone the trouble of experimenting with a bunch of different ROMs and kernels.
Calebz said:
To avoid having loose ends out there (in case anyone finds this thread during a search) - The problem turned out to be the latest radio. Not my lack of it :lol:
After flashing back to the .48 radio, from the .84 radio - everything is back to normal. No more weird Android OS wakelocks. ~3-4% battery drain overnight instead of 20-30%
There are more and more people popping up on XDA with this problem. So far, all of them that I have seen are outside the US. A few have even discovered the same fix.
So - future person that finds this thread during a search, look into the possibility of flashing back to version .48 of the radio. Hopefully this saves someone the trouble of experimenting with a bunch of different ROMs and kernels.
Click to expand...
Click to collapse
I put your post into my thread for people looking for an answer to this wakelock. Hope you don´t mind. Credits to you are there.
http://forum.xda-developers.com/showthread.php?p=44122105
:fingers-crossed:
Hello all,
I own an international N9005.
Up until recently, I used the stock Samsung ROM with good battery life.
A couple of weeks ago, with no apparent reason, I started getting horrid battery life - in access of 10% drop -per hour- in idle (as opposed to 1-3%).
I removed more-or-less everything, disabled more-or-less everything but nothing seems to work.
Got root (there goes the warranty) tried looking for Wake-locks and nothing. The Note3 is 97% (!!!) awake even with everything disabled, and in the wake looks screen both user and kernel I only see 1-2 minutes (!).
Tried resetting the ROM, tried installing other custom ROMs (X-Note, Omega, etc). Nothing seems to work.
Currently I'm running Omera v20, with *zero* applications installed (including all the Google and Samsung applications beyond Google Playstore) and all external services (location, WIFI, et-al) disabled, my note 3 is still 95-99% awake, and the list of wake lockers is, errr, empty.
FWIW I'm ~100m from the nearest cell tower.
EDIT: According to battery meter, Android OS is keeping the phone up.
Any ideas?
- Gilboa
gilboa said:
Hello all,
I own an international N9005.
Up until recently, I used the stock Samsung ROM with good battery life.
A couple of weeks ago, with no apparent reason, I started getting horrid battery life - in access of 10% drop -per hour- in idle (as opposed to 1-3%).
I removed more-or-less everything, disabled more-or-less everything but nothing seems to work.
Got root (there goes the warranty) tried looking for Wake-locks and nothing. The Note3 is 97% (!!!) awake even with everything disabled, and in the wake looks screen both user and kernel I only see 1-2 minutes (!).
Tried resetting the ROM, tried installing other custom ROMs (X-Note, Omega, etc). Nothing seems to work.
Currently I'm running Omera v20, with *zero* applications installed (including all the Google and Samsung applications beyond Google Playstore) and all external services (location, WIFI, et-al) disabled, my note 3 is still 95-99% awake, and the list of wake lockers is, errr, empty.
FWIW I'm ~100m from the nearest cell tower.
EDIT: According to battery meter, Android OS is keeping the phone up.
Any ideas?
- Gilboa
Click to expand...
Click to collapse
Buy a new battery, maybe this will solve the problem...
gilboa said:
Hello all,
I own an international N9005.
Up until recently, I used the stock Samsung ROM with good battery life.
A couple of weeks ago, with no apparent reason, I started getting horrid battery life - in access of 10% drop -per hour- in idle (as opposed to 1-3%).
I removed more-or-less everything, disabled more-or-less everything but nothing seems to work.
Got root (there goes the warranty) tried looking for Wake-locks and nothing. The Note3 is 97% (!!!) awake even with everything disabled, and in the wake looks screen both user and kernel I only see 1-2 minutes (!).
Tried resetting the ROM, tried installing other custom ROMs (X-Note, Omega, etc). Nothing seems to work.
Currently I'm running Omera v20, with *zero* applications installed (including all the Google and Samsung applications beyond Google Playstore) and all external services (location, WIFI, et-al) disabled, my note 3 is still 95-99% awake, and the list of wake lockers is, errr, empty.
FWIW I'm ~100m from the nearest cell tower.
EDIT: According to battery meter, Android OS is keeping the phone up.
Any ideas?
- Gilboa
Click to expand...
Click to collapse
Indexing your external SD maybe?
You could try the link in my sig and try again for your custom ROM.
First, thanks all for taking the time to answer.
I'm thinking about getting a new battery, but my gut feeling is that its not the source of amazing battery drain - ~20%/h while completely [!] idle (auto-sync/location/etc completely off).
I've attaching /d/wakeup_source in excel format sorted by count and total time - in-case someone has any idea what's completely broken.
As far as I can see, qpnp-vadc-ebd30a00, sec-battery-monitor, mmc0:0001:2 are the main culprits.
nicholaschum,
Before I attempt a complete wipe (as opposed to the normal wipe data / cache), how can I detect if someone is indexing my sdcard? (which may account for the mmc0:0001:2 in the wake lock dump).
- Gilboa
I know this is a long shot but try turning off developer options if you have it turned on(especially force gpu rendering). Somehow I found out that when I turned it on and the screen is idle. I get a battery drain. Not as big as yours. But not really sure because if I use the phone, the battery is actually pretty great(an hour of screen time is about 10% even more with internet apps like facebook youtube chrome etc.).
Clear cache. I know this is too common but it actually works for a lot of people.
Lastly, try airplane mode overnight and see if it doesn't drain. It might be your network that is causing the drain.
gilboa said:
First, thanks all for taking the time to answer.
I'm thinking about getting a new battery, but my gut feeling is that its not the source of amazing battery drain - ~20%/h while completely [!] idle (auto-sync/location/etc completely off).
I've attaching /d/wakeup_source in excel format sorted by count and total time - in-case someone has any idea what's completely broken.
As far as I can see, qpnp-vadc-ebd30a00, sec-battery-monitor, mmc0:0001:2 are the main culprits.
nicholaschum,
Before I attempt a complete wipe (as opposed to the normal wipe data / cache), how can I detect if someone is indexing my sdcard? (which may account for the mmc0:0001:2 in the wake lock dump).
- Gilboa
Click to expand...
Click to collapse
Hi, basically just check your phone using BBS (BetterBatteryStats), and see which individual process is eating up your battery.
Graffiti Exploit said:
I know this is a long shot but try turning off developer options if you have it turned on(especially force gpu rendering). Somehow I found out that when I turned it on and the screen is idle. I get a battery drain. Not as big as yours. But not really sure because if I use the phone, the battery is actually pretty great(an hour of screen time is about 10% even more with internet apps like facebook youtube chrome etc.).
Click to expand...
Click to collapse
I had the developer options off and on. Didn't seem to help.
Clear cache. I know this is too common but it actually works for a lot of people.
Lastly, try airplane mode overnight and see if it doesn't drain. It might be your network that is causing the drain.
Click to expand...
Click to collapse
If the current state doesn't hold (see below), I'll give it a try. Good thinking
nicholaschum said:
Hi, basically just check your phone using BBS (BetterBatteryStats), and see which individual process is eating up your battery.
Click to expand...
Click to collapse
Already installed - together with WakeLockDetector.
Short update, out of pure desperation I completely wiped the phone (including sdcard), tried installing stock ROM and, err, Odin failed. Managed to get CWM running again and installed the latest CM nightly.
...
As weird as it sounds, going from NF4 based ROMs (including stock) to CM nightly dropped to idle battery usage to ~2-6%/h, a huge drop from ~20%/h.
I'll update and mark resolved if this situation holds (crosses fingers).
- Gilboa
gilboa said:
I had the developer options off and on. Didn't seem to help.
If the current state doesn't hold (see below), I'll give it a try. Good thinking
Already installed - together with WakeLockDetector.
Short update, out of pure desperation I completely wiped the phone (including sdcard), tried installing stock ROM and, err, Odin failed. Managed to get CWM running again and installed the latest CM nightly.
...
As weird as it sounds, going from NF4 based ROMs (including stock) to CM nightly dropped to idle battery usage to ~2-6%/h, a huge drop from ~20%/h.
I'll update and mark resolved if this situation holds (crosses fingers).
- Gilboa
Click to expand...
Click to collapse
I heard there were problems with NF4 battery. But I haven't been on TW since ND4. No matter what on Note 3 TW the battery sucks. AOSP is great. But actually S5 port has the best battery.
Solved, at least for now.
nicholaschum said:
I heard there were problems with NF4 battery. But I haven't been on TW since ND4. No matter what on Note 3 TW the battery sucks. AOSP is great. But actually S5 port has the best battery.
Click to expand...
Click to collapse
I use Nova (and not TW)
Either way, latest nightly seems to solve the battery drain problem completely - using the same Nova and system configuration (widgets, active syncs, etc). Currently I'm at ~1.5-0.8%/h when idle with no issues going into deep sleep.
Seems that my specific model really dislikes NF4.
Thanks again for trying to help.
This thread has been quite helpful as I was suffering with a Battery Drain after the NF4 Upgrade.
Planning to go back to ND5, which was the last stable version.
JazonX said:
This thread has been quite helpful as I was suffering with a Battery Drain after the NF4 Upgrade.
Planning to go back to ND5, which was the last stable version.
Click to expand...
Click to collapse
I was thinking about doing the same, but in the CM 11 runs circles around both NF4 (duh!) and my previous ROM (not sure which revision it was) - plus I can actually get 2 days of standby time, even with the old batteries, so I'll stick with CM 11 for now.
- Gilboa
gilboa said:
I was thinking about doing the same, but in the CM 11 runs circles around both NF4 (duh!) and my previous ROM (not sure which revision it was) - plus I can actually get 2 days of standby time, even with the old batteries, so I'll stick with CM 11 for now.
- Gilboa
Click to expand...
Click to collapse
CM11 is not an option for me. No 4k Video Recording, Worse Camera than TW, S-Pen Functions Removed... Nope. Cant survive with CM11.
JazonX said:
CM11 is not an option for me. No 4k Video Recording, Worse Camera than TW, S-Pen Functions Removed... Nope. Cant survive with CM11.
Click to expand...
Click to collapse
I can relate.
Good luck, and post if you find a solution (in-case I decide to switch back to Samsung based).
hi guys first of all i apologize for this post not having detailed info such as ss from BBS,GSAM and WLD and will post them later !!
and as always i guess with most battery related problems it happened suddenly and i really mean suddenly the day before yesterday everything was perfectly fine and i didn't have that ridiculous battery drain !!
i woke up yesterday only to find out that Android OS is taking more than 50% of battery usage with a drain like 20% over night
restarted many times and by the end of the day i installed GSAM and WLD (wakelock detector)
froze most of apps including the ones i installed recently but i didn't install that battery hog apps (nothing unusual) and also they didn't appear in partial wakelocks section of BBS
btw i don't use any fake battery extender tools or memory boosters it's just Greenify
i observed that sometimes when i unlock my device (i use knock code btw if that matter!!) wifi gets disconnected and reconnect again (wifi icon disappear and re-appear again in 3 secs or so)
i'll upload ss in a couple of mins
thank you
Edit: SS Added
and notice how it drained 5% in just 40 mins (20 mins SOT) !!!
ADM!RAL said:
hi guys first of all i apologize for this post not having detailed info such as ss from BBS,GSAM and WLD and will post them later !!
and as always i guess with most battery related problems it happened suddenly and i really mean suddenly the day before yesterday everything was perfectly fine and i didn't have that ridiculous battery drain !!
i woke up yesterday only to find out that Android OS is taking more than 50% of battery usage with a drain like 20% over night
restarted many times and by the end of the day i installed GSAM and WLD (wakelock detector)
froze most of apps including the ones i installed recently but i didn't install that battery hog apps (nothing unusual) and also they didn't appear in partial wakelocks section of BBS
btw i don't use any fake battery extender tools or memory boosters it's just Greenify
i observed that sometimes when i unlock my device (i use knock code btw if that matter!!) wifi gets disconnected and reconnect again (wifi icon disappear and re-appear again in 3 secs or so)
i'll upload ss in a couple of mins
thank you
Edit: SS Added
and notice how it drained 5% in just 40 mins (20 mins SOT) !!!
Click to expand...
Click to collapse
Little more details about rom,kernel but wifi is destroying your battery,that is for sure. It's waking the phone thousands of time as you can see yourself
Sent from my LG-D802 using Tapatalk
Stevica Smederevac said:
Little more details about rom,kernel but wifi is destroying your battery,that is for sure. It's waking the phone thousands of time as you can see yourself
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
yea i noticed that i read about something related to wifi driver issue idk
thx for reply tho and for my device it's stock D800y20 rom just rooted and even with stock recovery if it matter
This has started for me today also! Not sure what is causing it but I was fine prior to today. Maybe its a google Play services update?
keeepinitgansta said:
This has started for me today also! Not sure what is causing it but I was fine prior to today. Maybe its a google Play services update?
Click to expand...
Click to collapse
idk but last google play service update was 10 days ago here !!
ADM!RAL said:
hi guys first of all i apologize for this post not having detailed info such as ss from BBS,GSAM and WLD and will post them later !!
and as always i guess with most battery related problems it happened suddenly and i really mean suddenly the day before yesterday everything was perfectly fine and i didn't have that ridiculous battery drain !!
i woke up yesterday only to find out that Android OS is taking more than 50% of battery usage with a drain like 20% over night
restarted many times and by the end of the day i installed GSAM and WLD (wakelock detector)
froze most of apps including the ones i installed recently but i didn't install that battery hog apps (nothing unusual) and also they didn't appear in partial wakelocks section of BBS
btw i don't use any fake battery extender tools or memory boosters it's just Greenify
i observed that sometimes when i unlock my device (i use knock code btw if that matter!!) wifi gets disconnected and reconnect again (wifi icon disappear and re-appear again in 3 secs or so)
i'll upload ss in a couple of mins
thank you
Edit: SS Added
and notice how it drained 5% in just 40 mins (20 mins SOT) !!!
Click to expand...
Click to collapse
Hello,
I have at 80% the same problem, I loose 7-10% of battery per hours, without SIM, wifi, bluetooth...
I already tried most of all roms, kernel, try all cpu governor.
If you want to see my topic : http://forum.xda-developers.com/lg-g2/help/lg-g2-d802-battery-draining-5-0-2-t3256313/
If you are ready to dismantlle the phone, do it, and see if there is a problem inside. I hope you will resolve your problem and tell me if one day you gonna have a better battery
Dlazzy said:
Hello,
I have at 80% the same problem, I loose 7-10% of battery per hours, without SIM, wifi, bluetooth...
I already tried most of all roms, kernel, try all cpu governor.
If you want to see my topic : http://forum.xda-developers.com/lg-g2/help/lg-g2-d802-battery-draining-5-0-2-t3256313/
If you are ready to dismantlle the phone, do it, and see if there is a problem inside. I hope you will resolve your problem and tell me if one day you gonna have a better battery
Click to expand...
Click to collapse
yea almost identical problem
i did tot reinstall and see how things go !!
sadly nothing changed and wifi still eats huge amount of battery idk how did this happen
well i'll update thread if anything changed
peace out guys
I had the same problem with battery drain(although not as severe) along with huge data consumption when using a significantly modified(i.e. heavy debloat and ota disabled) rooted stock rom. I tried a few customs roms and dorimanx kernel(not at the same time), and even though battery drain wasn't as bad, they were are waaaay to buggy to be used everyday(especially the dorimanx kernel, it's really bad).
Just last week I tot back to KK and ota updated to the latest LP rom(lost root unfortunately). Then I uninstalled/disabled every app I could/needed. Everything is very fast, smooth, and stable again. I now lose 1-2% every 8hrs in standby with syncing and wifi/data enabled, bluetooth and nfc disabled. I regularly get 5-6hrs sot over 48hrs with moderate use and brightness on auto.
I do have a new battery though - my old one( came with my "refurbished" phone from freedompop) gave me 2-3hrs of sot - but that was when I first got it and before I started modifying anything.
stan54 said:
I had the same problem with battery drain(although not as severe) along with huge data consumption when using a significantly modified(i.e. heavy debloat and ota disabled) rooted stock rom. I tried a few customs roms and dorimanx kernel(not at the same time), and even though battery drain wasn't as bad, they were are waaaay to buggy to be used everyday(especially the dorimanx kernel, it's really bad).
Just last week I tot back to KK and ota updated to the latest LP rom(lost root unfortunately). Then I uninstalled/disabled every app I could/needed. Everything is very fast, smooth, and stable again. I now lose 1-2% every 8hrs in standby with syncing and wifi/data enabled, bluetooth and nfc disabled. I regularly get 5-6hrs sot over 48hrs with moderate use and brightness on auto.
I do have a new battery though - my old one( came with my "refurbished" phone from freedompop) gave me 2-3hrs of sot - but that was when I first got it and before I started modifying anything.
Click to expand...
Click to collapse
How is dorimanx kernel bad? How many user downloads he has,lots and lots then are we thousands of user wrong using a bad kernel, come on . Maybe it didnt work for you. But out of those thousands of users cant be wrong. If it was that bad no one would download. Just saying , you should just say it didnt work for you.
stan54 said:
I had the same problem with battery drain(although not as severe) along with huge data consumption when using a significantly modified(i.e. heavy debloat and ota disabled) rooted stock rom. I tried a few customs roms and dorimanx kernel(not at the same time), and even though battery drain wasn't as bad, they were are waaaay to buggy to be used everyday(especially the dorimanx kernel, it's really bad).
Just last week I tot back to KK and ota updated to the latest LP rom(lost root unfortunately). Then I uninstalled/disabled every app I could/needed. Everything is very fast, smooth, and stable again. I now lose 1-2% every 8hrs in standby with syncing and wifi/data enabled, bluetooth and nfc disabled. I regularly get 5-6hrs sot over 48hrs with moderate use and brightness on auto.
I do have a new battery though - my old one( came with my "refurbished" phone from freedompop) gave me 2-3hrs of sot - but that was when I first got it and before I started modifying anything.
Click to expand...
Click to collapse
Can you tell us what app have you uninstalled and disable ?
What have you debloat ?
Thank you very much
My G2 (vs980) has also been suffering from a sudden battery drain. Android OS and Android System seem to be the problem. They are now second and third on the list of battery usage, after the screen. Before now, they were never that high on the list. I noticed this last weekend, when I kdz to the latest update for the vs980, which is 3AA. After noticing this, I flashed the xceed kernel, then cloudy with dorimanx kernel, and the battery drain continued. I even kdz back to kitkat, still the same, then I flashed AICP 11, and still the same battery drain by Android OS and system. Finally, I restored a backup of stock lollipop 39A but, the issue continued so I turned on airplane mode and it seems to help a bit. I still notice battery life isn't the same as before. The os and system still drain more than usual even on airplane mode.
Kind of glad to hear I'm not the only one with this issue. I don't think I need a new battery, since I bought the phone new in April 2015 from Bestbuy.
Also Gsam, shows the temperature of phone between 80°-90°F, where before it would be in the low to mid 70s. One time, it even got up to 104°F, funny thing is, it doesn't even feel that hot in my hand.
Hopefully, we can find out what's causing this because I really liked the battery life on this phone. Even when people complained about the battery life being worse on 5.0.2, I was pretty happy with it. All my previous phones can't compare to the g2. Now I feel like upgrading though lol.
Sent from my VS980 4G using Tapatalk
raptorddd said:
How is dorimanx kernel bad? How many user downloads he has,lots and lots then are we thousands of user wrong using a bad kernel, come on . Maybe it didnt work for you. But out of those thousands of users cant be wrong. If it was that bad no one would download. Just saying , you should just say it didnt work for you.
Click to expand...
Click to collapse
When I tried the version that was out a month or two ago it wasn't nearly as smooth as stock, even after conservatively messing with the kernel app settings. The worst was that it also cut out tethering and my flashlight when the screen shut off. Maybe the recent updates have fixed some of the issues, but I doubt it. Could be that he doesn't have access to the sprint variant which I have...
Either way, just because 'thousands' of people use it doesn't necessarily mean that it's good - 99.9% of those users have no idea how to code or how a kernel is written. Their knowledge goes as far as following picture guides online - which a 5 years old could do. Just look at the most recent change log - those 'fixes' were to glaringly huge problems that shouldn't have been made in the first place and people were blissfully using it the whole time. Think about how many thousands of other bugs their must be. Not to mention hacking up code made by professionals at huge companies could lead to many other problems. Obliviously the stock kernel has bugs as well, but it works and is fast and stable so I see no need for using a hacked together kernel made by one amateur that doesn't even have my version of the phone to test it on. I wanted it to be good - which Is why I went to the trouble of installing it, but it's definitely NOT.
Dlazzy said:
Can you tell us what app have you uninstalled and disable ?
What have you debloat ?
Thank you very much
Click to expand...
Click to collapse
I uninstalled ALL of the stock apps that can be uninstalled. The ones I disabled are aosp keyboard, app updates, browser, calendar, cloud print, favorite contact widget, google play books, games, movies & tv, newstand, google+, lg voice command speech pack, music, music(the widget - it always runs in the background even without being on the homescreen), notebook, polaris viewer, quicktranslator, swype, talkback, voice command. I would have liked to disable a few more but I'm not rooted so I couldn't.
I use nearly all of the google products like chrome,gmail, calendar, docs, keep, music, photos, news and weather,translate,etc...so having the stock lg ones enabled was redundant. I also only have the bare minimum of installed apps that I need. Nearly all of them are made my major corporations i.e Chase, BofA, ebay, paypal, freedompop, microsoft, swiftkey etc. I have NO games or any small apps that need a ton of permissions. The only small apps are feedly, print hammermill, privacy flashlight(240kb, no ads, no permissions) and bubble level(180kb, no ads, no permissions).
I also go through every settings in every app to make sure it's what I want. And I restart my phone every time I take it off the charger. IMO having a clean and no frills system that is set correctly is the key to performance and battery life.
I just want want to clarify that I average 4-5hrs per 1% in standby since it doesn't seem to hold as well as it gets closer to 0%.
theres this app that have lots of info on battery..
thx guys for adding your experience
i hoped moded kernels would've reduced that amount as they should have necessary drivers for wifi which was somehow got messed up but from your reply i guess i've to look somewhere else
idk how to put this, well this isn't a solution at all i actually didn't start working on it yet just thought to share what i found so far !!
so it's just a reference for any one whose luck was bad enough to have a wakelock like that !
1st of all in most cases neither the device nor it's battery are at fault *you need to understand that*
faulty battery doesn't show up kernel related wakelocks instead they drain without a reason so i hope ppl stop accusing battery in every battery drain thread!
2nd after understanding that you'll have to deal with the environment your phone is used in
to put it simple it's your router and all devices in your current network !! (idk though why not all devices get affected by that or why it just started now, tough luck yea)
those threads may help
http://forum.xda-developers.com/showpost.php?p=31975007&postcount=2
http://forum.xda-developers.com/google-nexus-5/help/getting-rid-wlanrxwake-wakelocks-t2519294
what i'll try to do is add an old access point to my router and connect my phone to it as i don't have a replacement router right now!!
i'll let you know if things were improved !
hey guys
i thought to share what i did so far and before i go on there is a bad news and a good news !!
i would start with the bad news first !
-no rom could solve this issue so you don't really need to format everything and start from scratch especially if you didn't mess around too much and you found it started suddenly like here, i've tried couple of roms including latest CM13 build it wasn't that bad but it didn't solve the drain that much either !!
-now some ppl may see this bad and some may don't care (which means good!!) google services are the ones responsible for this drain
well man you didn't come up with anything new and i see you've got a problem getting straight to the point besides you talk too much
i'm sorry
now you have to sacrifice your google services background sync including "GCM" if you are using any services similar to pushbullet or notification mirroring you'd understand why it's important
anyway if you are good with that you may install and yea it works with latest google play services
https://play.google.com/store/apps/details?id=com.playfulgeeks.gservicefix
and do as instructions (and believe it'll work if you did steps right)
if you prefer manual way then you'll need "app ops xposed module" and deactivate every "wake up" permission from google services
this guide may help but remember we don't have tools natively in our roms so don't bother downloading "shortcut maker" and go through your settings app to find "privacy guard" or "app ops" we don't have those natively like them
http://forum.xda-developers.com/oneplus-one/general/guide-google-play-services-battery-t2832525
i'll share some ss from stock battery stats
i'm sorry for my long post and i hope it'll help someone with same issue
idk if it solved issue completely but things are stabilized a lot now and i just lost 1% over night not 20% or 30% like before !!
and i'm using lollipop now so i guess it's not that bad for what i heard about bad lollipop battery since it's my first time trying it !!
and btw real SOT should be +40 mins so the real SOT is 2H-47M cuz i restarted my phone to apply that fix and for some reason battery stats doesn't stick between reboots !!
if anyone interested in trying that rom it's for D800 only btw and thx to @Swetnes for his work rom feels pretty stable and solid :good:
link: http://forum.xda-developers.com/att-g2/development/rom-t3152368/
good luck everyone
Since the first release of oreo I started using the rom as a daily driver, later on paired with a good kernel it had some good perfomance
But after some days of using the rom i started to notice a huge battery drain caused by the Mobile network standby process?
My battery was old (OEM 2014 battery) so i decided to revert back to lineageOS just after a couple of days where I haven't had any issues with that mobile network standby
Now I'm really curious what is causing this issue,drain because I am using the phone on the same settings as on 7.1 nougat, I am living in a country where all networks run on 3G,H+,2G etc. so no 4G if this can be a cause
Changed the network modes many times and tested throughout the days but there was no sucess the drain was still persist, tried updating,downgrading bootloaders swithing modems but again no sucess
If there, in the world of android is any solution, here is the thread to discuss about this issue. :fingers-crossed:
I've wondered this too. I've been running los15 on my g900v , I rooted and boot the first ROM that would work without having or remembering todomuch, I ran the first custom kernal I could find via google, and ran whatever was noted as the latest Verizon modems. its like right off the bat, smooth , consistent battery life and nice. Then the next day I noticed things would crash, my Bt temperamental at best and restarted it just to get by. if I have sync on at home, WiFi off, it just chills , if I turn sync off and drive around town, my battery life gets eaten by the unknown. I pulled some logs to see whats up with my BT but haven't got around to it yet. But my battery too is old (I literally found my s5 in the trash) and I run weird processes and tweak settings all the time just to mess with it, so that could be it to. If I see anything weird I'll let you know.
I'm struggling with this issue for months, since the first port of an Oreo custom ROM (LOS and RR) for the Galaxy A3 Duos (my device) started being developed.
From the beginning I had this problem, and what, since then, puzzles me the most is the fact that only some of us, flashing the same ROM in the same device, experience the issue. Whenever I flash any of those ROMs, even before installing any user apps (or when running in safe mode), the drain is there, which leads me to think that the culprit must be some setting: not an app, because I have none installed; not the ROM itself, because not everybody has this problem.
Unfortunately there seems to be no developers looking into this bug.
For the sake of information, I've observed two things that should help to narrow down the issue; or maybe not.
First, all the devices affected, as far as I've searched, are double SIM.
Second, the Mobile Network Standby (MNS from now on) drain is narrowy connected with the Bluetooth drain (which "also" occurs in Oreo). I've experienced the following: If, after a full charge, I don't switch on Bluetooth at all, then what drains my battery (according to Advanced Battery Usage information) is MNS. However, if I switch bluetooth on -even if only for one minute- then what apparentlyh drains my battery is Bluetooth, at the same speed as MNS did before switching bluetooth on.
Funny enough, the battery use info reports zero minutes activity for both Bluetooth and MNS. But how can a process which runs zero minutes drain 50% of the battery?? I'm afraid that the battery use information isn't reliable. But then that's very bad news, since, in such case, it might well happen that the real juice sucker is neither MNS nor Bluetooth!! We might be dealing with a "ghost" here, since we can't even trust the battery use information provided by the OS.
If someone has something with which to contribute to this research, or any ideas, please comment.
I'm having the same trouble on android 9 betas, even better, my phone gets without signal during those times and there's nothing I could do but rebooting the phone.
How can we help solve this? it looks like it's annoying a lot of people now