I updated to the CM7.1 from rooted NC1.3 by using clockwork-3.0.2.8 on SD card
recently. Before I install the CM7.1 and latest gapps 20110828, I format the
system, data, boot. Everything seems perfect until I found this battery drain
problem.
My NC's battery life is very bad on CM7.1. I don't expect it can perform as stock 1.3,
but what I experience is terrible. I checked the "Battery use" and found that "Android OS"
almost occupy whole battery usage, over 60%. It seems my NC doesn't sleep or go to
suspend. I found a old thread mentioned about the same problem, but it is quiet old CM
nightly. Is there anyone in the some situation like me with CM7.1 stable?
hsiangyang said:
My NC's battery life is very bad on CM7.1. I don't expect it can perform as stock 1.3,
but what I experience is terrible. I checked the "Battery use" and found that "Android OS"
almost occupy whole battery usage, over 60%. It seems my NC doesn't sleep or go to
suspend.
Click to expand...
Click to collapse
Only time I've had such stuff happen was with bad software, particularly widgets, being used.
I would also recommend updating to one of the latest nightly releases of CM7 as well. I forget when, but there was a deep-sleep fix introduced a while back that made a huge improvement in battery life. Despite the name, the nightlies are generally very stable at this point.
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
khaytsus said:
Only time I've had such stuff happen was with bad software, particularly widgets, being used.
Click to expand...
Click to collapse
Same here. On my phone I had an app that would drain the battery overnight while it was plugged in and charging.
Here is the thread I started before about this issue. You can read what I went through to eliminate various culprits:
http://forum.xda-developers.com/showthread.php?t=1187672
ponyboy82 said:
I would also recommend updating to one of the latest nightly releases of CM7 as well. I forget when, but there was a deep-sleep fix introduced a while back that made a huge improvement in battery life. Despite the name, the nightlies are generally very stable at this point.
Click to expand...
Click to collapse
Thanks for the comment. I am in nightly 250 now, just format catch, wipe dalvik cache and install the
cm_encore_full-250.zip over the 7.1 stable. This battery drain problem still there.
This time, I found a reboot (hold power key to shoot down and boot it again) can temporarily fix it.
Leave the NC along without playing with it, the deep sleep does work and no more battery drain.
But it comes back when I just play the cordy game downloaded from market. I play the game for
few minutes, then exit it correctly by click the exit button of the game. Leave the device for awhile
and the "Android OS" comes back. It start to drain my battery again. Seems the game starts a service
or application on the background.
I download the "Advance task killer" and use it to kill those service, application I don't use from the
list. But I still losing my battery very fast because of the "Android OS". Any good idea??
Sincitybronze said:
Here is the thread I started before about this issue. You can read what I went through to eliminate various culprits:
http://forum.xda-developers.com/showthread.php?t=1187672
Click to expand...
Click to collapse
Thanks for your sharing of this thread. I do found some useful info. in it.
Now my battery drain issue is gone, but I don't know which action I did
take effect.
This is what I did. Format cache, Wipe dalvik cache, install cm_encore_full-253.zip,
apply signal_bar-kernel-patch-SOD.zip, reset battery stats and fix permission.
Then reboot. No more battery drain caused by "Android OS".
hsiangyang said:
Thanks for your sharing of this thread. I do found some useful info. in it.
Now my battery drain issue is gone, but I don't know which action I did
take effect.
This is what I did. Format cache, Wipe dalvik cache, install cm_encore_full-253.zip,
apply signal_bar-kernel-patch-SOD.zip, reset battery stats and fix permission.
Then reboot. No more battery drain caused by "Android OS".
Click to expand...
Click to collapse
Install CPU spy and you can verify sleep and CPU stepping rates.
Ian
Sent from space
Related
Dear all,
I just upgraded my tab into overcome 3.1 from my initial GB 2.3 . The reason why i started to discover some issue on my batt usage is within 2hrs it will take off 20% of my batt when i fully charged in the morning.
After which i check on my application - batt use - it show "display" is at 92% on the top and android system is at 2% at the bottom. Whereby when i use GB 2.3 rom, it will show andoid system is at 80~90% and display is at the bottom of 3%.
(Note: i have even set my display to the lowest and set it to Auto mode, some of the un use application i also shut down)
I have started to think should i change back to GB 2.3 or is there any brother outside can advise what should i do to change this situation. Hope someone can help me on this ..... Thanks in advance.
nikes60 said:
Dear all,
I just upgraded my tab into overcome 3.1 from my initial GB 2.3 . The reason why i started to discover some issue on my batt usage is within 2hrs it will take off 20% of my batt when i fully charged in the morning.
After which i check on my application - batt use - it show "display" is at 92% on the top and android system is at 2% at the bottom. Whereby when i use GB 2.3 rom, it will show andoid system is at 80~90% and display is at the bottom of 3%.
(Note: i have even set my display to the lowest and set it to Auto mode, some of the un use application i also shut down)
I have started to think should i change back to GB 2.3 or is there any brother outside can advise what should i do to change this situation. Hope someone can help me on this ..... Thanks in advance.
Click to expand...
Click to collapse
dear all, after further confirmed, my colleagues also having the same problem as my, I was wonder is there a bug in this version as em not sure why the consumption of the battery was so high after installing overcome 3.1
First of all, old ROM had a bug, battery usage was displayed wrong. That is fixed, but they are now working on R2 version of kernel (Reverted lowmemkiller change which may have been blocking kswapd0 from sleeping, resulting in battery leakage).
This last kernel has a new ROM as it's base, so you have to install new ROM first and then full wipe version of kernel.
Good to hear I am not the only one.
Hermes was an awesome rom concerning battery stamina. I hope the guys from Overcome will make this R2 release just as good.
Dardevil1977 said:
First of all, old ROM had a bug, battery usage was displayed wrong. That is fixed, but they are now working on R2 version of kernel (Reverted lowmemkiller change which may have been blocking kswapd0 from sleeping, resulting in battery leakage).
This last kernel has a new ROM as it's base, so you have to install new ROM first and then full wipe version of kernel.
Click to expand...
Click to collapse
Thanks for updating this good news as today I almost wanted to flash my rom again. from the moment upgraded to overcome 3.1, I have discovered this issue as I previously use g b 2.3. not sure how soon the r2 will be out ya?
Dunno that, i'm waiting too
Dardevil1977 said:
Dunno that, i'm waiting too
Click to expand...
Click to collapse
Bro, how do we got to know whenever there is a update on this R2 kind of version or we have to daily refer to this forum. Thanks in advance.
There will be new topic about it on Galaxy Tab Android Development as soon as they finish it
Dardevil1977 said:
There will be new topic about it on Galaxy Tab Android Development as soon as they finish it
Click to expand...
Click to collapse
thanks for your quick response.
The latest version of the overcome kernel is pretty good on battery life for me.. the only thing that seems to be wrong is the reported charge level against the battery display level..
Even after calibration its still way off (20%)..
Gainn said:
The latest version of the overcome kernel is pretty good on battery life for me.. the only thing that seems to be wrong is the reported charge level against the battery display level..
Even after calibration its still way off (20%)..
Click to expand...
Click to collapse
i think you need to perform a "wipe on batt" in cwm maybe can help. Anyway i also discover that my tap below 4 buttons occasionally the light will be blinking on and off during at the standby mode, i belived this also can cus some batt drain off too. Anyway, most of the people are concerning about batt duration especially devise such as non-detachable batt. For me, i use my tap outside most of the time especially during business trip hangging in the train station or airport.... Well, i think we appreciate the overcome team and the rest of you guys to test it out and gain feedback for improment.... cheerss... and Selamat Hari Raya to all muslim people ya.
did you try the tweaks here re: Battery Recalibration and Reconditioning…
http://p1000.teamovercome.net/?page_id=68
and do note that:
battery wipe by itself would not immediately “improve” your battery life. IN FACT, during the first charge cycle after a battery wipe, you might notice a slightly less than optimal battery-life! This is because, the stats have to be rebuilt, which is why after a couple of FULL charge cycles after the battery wipe, when the stats are properly “repopulated”, which is when you’ll see the difference.
eongab said:
did you try the tweaks here re: Battery Recalibration and Reconditioning…
http://p1000.teamovercome.net/?page_id=68
and do note that:
battery wipe by itself would not immediately “improve” your battery life. IN FACT, during the first charge cycle after a battery wipe, you might notice a slightly less than optimal battery-life! This is because, the stats have to be rebuilt, which is why after a couple of FULL charge cycles after the battery wipe, when the stats are properly “repopulated”, which is when you’ll see the difference.
Click to expand...
Click to collapse
yes, i have did that after going through the forum, and today is a second day after the wipe, but i would recognized that if you put the tab in Normal stanby mode, the batt will drop about 1% in about 4hrs since i have started to monitor this morning... well, i will continue to monitor aand post it again. thanks for your advise.
my one on overcome 3.3.1 seems to last at least 1 hr when the battery notification show 0!!!
I have tested my second days after batt wipe, it seem that if we put at standby mode the batt really better then earlier versions, i can notice that last night was 26% at 2.30am and this morning waikup at 7.15am, the batt indicate 24%. (Note : my wifi is on, except BT and GPS is off).
My conclusion for now is that the OC 3.1 batt life is ok and even better when it was in standby mode, however whenever any application for example browsing internet or starting reading news, the batt will start to drain off like 1% every 3min (my estimation point of view).
Hope the OC team can help to improve from here OR the nature of this OC 3.1 is normal on this circumstanses. Cheerssss....
I picked up a Galaxy Note the other day to mess around with, and have noticed that the battery life isn't fantastic.
I'm running Slim Bean 4.2.2 build 7, and NX OC kernal. The only relevant settings I've changed in the kernel utility are the clockspeed (from 1.4 to 1.6) and the governor (from Hyper to SmartassV2). Battery is stock.
Here's an Imgur album with screenshots of everything I think you'd need to see: http://imgur.com/a/fAUR7
Now, am I missing something, or does this look right? Should 'Android OS' be using that much battery?
Thanks a lot in advance for anyone that can help.
What's your screen-on time? To check that then go to battery and tap the screen. (report when the batter is nearly dead - below 5%).
XxPixX said:
What's your screen-on time? To check that then go to battery and tap the screen. (report when the batter is nearly dead - below 5%).
Click to expand...
Click to collapse
Whoops, I missed that.
At the time of those screenshots, it was at 1 hour and 15 minutes, give or take a few minutes.
Ran the battery down playing some games. Updated screenshots are here: http://imgur.com/a/16ZRk
OK, so first and foremost then playing games will use a lot of battery. Usually you can't get more than 2h of intensive games. However the android OS usage is very high, install Better Battery Stats (search on XDA) and post the result. Also did you perform a clean install? As in did you perform the following wipes: system, data, cache, dalvik cache, preload?
The battery seems fine. It is normal with high Android OS. Same on my phone. Beanstalk + NX kernel. I managed to get around 2-3 hours of on screen time with gaming.
szunyiap said:
The battery seems fine. It is normal with high Android OS. Same on my phone. Beanstalk + NX kernel. I managed to get around 2-3 hours of on screen time with gaming.
Click to expand...
Click to collapse
That's good to know.
I just bought myself a 7000mAh battery from Hong Kong, so I shouldn't have any issues with battery life now.
Do please keep us posted with how the battery performance is. Could u post a link if you bought it online..
Hello to all,
I have two problems that are almost making me go back to stock 4.3 ROM
The first is related to the battery, the android system appears first with 25% + battery drain, and in most cases equal to or greater than the battery consumption of the screen! This makes my battery does not pass a day, and the stock I went much further (without STAMINA MODE).
The second issue is regarding the performance measured by AnTuTu. I know that does not mean much, but in the STOCK I get 25.5k and I read out there that people also manages the same in CM11 LBL (the MrSteve555 and also bagyusz), I do not understand why I can here the maximum 22.5K .
Independent of ROM I have put the same results. Tested in all versions of MrSteve555 and in the last two of bagyusz. Also tested in the PAC-man RC-1 neXus PRIME, same result and battery consumption.
In all ROMs I wipe system, data, cache, dalvik cache.
Does anyone have any idea how to solve this? I am discouraged because I love the CM11.
Ps: I use .207 kernel and I've tried with .205 also, same result. (I have LBL)
Damn what is that screenshot supposed to show?? 30 minutes off charge and it is at 99%!!! It's obvious that the screen consumption will be minimum, it was on for a minute or so probably... I know that usually android system drain is higher in cm than stock but you should compare your battery stats at the end of the day...
Please reset the counter by tapping on the trash icon on the activity bar. Then please post a screenshot after hours of usage. This will enable other people to properly interpret your battery stats.
Some tips though, you will most likely encounter a slight battery drain while using custom ROMs. This is due to the fact that stock ROM and custom ROM works differently. You might actually having a normal drain than a supposedly "bad" one.
By the end of the day will be the same... Anyway I will post later.
I attached new images for better understanding.
Does anyone have any idea?
Firstly, Antutu scores mean sh*t...
In the past I've had allot of ROMs with very bad Antutu scores which performed much better in terms of speed and general user experience than a standard ROM with higher Antutu score.
Furthermore, install better battery stats or any other wakelock detector app to see what is draining your battery. The pictures you are showing us now don't help at all.
I've exactly the same problem, android consumes always more than 25% battery too...
Silver Wx said:
I've exactly the same problem, android consumes always more than 25% battery too...
Click to expand...
Click to collapse
As I mentioned above, you need to identify what is causing the wakelocks first. Untill then there's absolutely no solution that can be presented to both of you.
By pointed by Gamm86, it might be due to wakelocks. Once the wakelocks are found, you may use Greenify to hibernate that rogue app. When the app is selected within Greenify, you will find it easier to see the wakeup path and cut it off through Greenify.
Wakelock Detector
Greenify
TechnoSparks said:
By pointed by Gamm86, it might be due to wakelocks. Once the wakelocks are found, you may use Greenify to hibernate that rogue app. When the app is selected within Greenify, you will find it easier to see the wakeup path and cut it off through Greenify.
Wakelock Detector
Greenify
Click to expand...
Click to collapse
It's not always apps themselves that cause wakelocks.
Background services related to phone or app settings are usually the culprits, meaning greenify won't resolve all wakelocks.
Gamm86 said:
It's not always apps themselves that cause wakelocks.
Services related to phone or app settings are usually the culprits, meaning greenify won't resolve all wakelocks.
Click to expand...
Click to collapse
yes I understand. Hmm i believe you are more experienced in this matter. Would you tell me how to stop those wakelocks that caused from other services? I would really appreciate that, cause I find many people solve this problem but they never did expose where they learn from or the methods they use. and yea, I've googled but I got nothing
TechnoSparks said:
yes I understand. Hmm i believe you are more experienced in this matter. Would you tell me how to stop those wakelocks that caused from other services? I would really appreciate that, cause I find many people solve this problem but they never did expose where they learn from or the methods they use. and yea, I've googled but I got nothing
Click to expand...
Click to collapse
Use Disable service app. Check which wakelock is occurring and disable that service.
Or get the donate version of unbounce and delay the wakelocks like every hour or so.
I already use Greenify and hibernate all apps that are not chat, not solved.
I also noticed that while I sleep and the phone remains idle the android system does not consume a lot of battery, something around 6%, but when you turn on the screen and the phone is active it starts to drain. So the problem is not in the wakelock, but elsewhere.
I'm using the applications suggested to post new screenshots later.
I used the apps for a day and I'm posting the screenshots of the result ... the system keeps draining and I don't see any information that would help me on the images.
Anyone have any ideas?
Jeanborba said:
Hello to all,
The second issue is regarding the performance measured by AnTuTu. I know that does not mean much, but in the STOCK I get 25.5k and I read out there that people also manages the same in CM11 LBL (the MrSteve555 and also bagyusz), I do not understand why I can here the maximum 22.5K .
Click to expand...
Click to collapse
I'm on MrSteve555's CM for LBL and was also wondering why I was getting a much lower AnTuTu score than stock. Then I discovered that I get 22.5K scores WHEN CHARGING and 25.5K scores running off the battery!
Jeanborba said:
I used the apps for a day and I'm posting the screenshots of the result ... the system keeps draining and I don't see any information that would help me on the images.
Anyone have any ideas?
Click to expand...
Click to collapse
I have noticed the same issues on all 4.4.x based roms (slimkat, pac, PA etc.). The only fix i found was to disable the automatic screen brightness. After disabling it the system_server service became normal and Android System dropped to 9-8% of overall battery consumption.
Good luck
Diablo.69 said:
I have noticed the same issues on all 4.4.x based roms (slimkat, pac, PA etc.). The only fix i found was to disable the automatic screen brightness. After disabling it the system_server service became normal and Android System dropped to 9-8% of overall battery consumption.
Good luck
Click to expand...
Click to collapse
I've exactly the same problem of you : thanks very much for find!
My phone never enters deep sleep when i lock it with WiFi on, this happens on cm11 by steve it drains a lot overnight
4.00 - 4.30 hours on screen = 2 days with playing fifa 15 and facebook + viber. 1-2 photos, 60 mins browsing and about 30 mins talk good for me without using battery safe apps - lock my bl and using .207's kernel on mr.steve555's Weeklies CM11 lbl
try CM11 Mahdi Rom 4.4.4 with gapps minimal 23mb ,my battery work as well after play music,game and facebook
Just when I think I've got it all setup nicely...
Latest AOSIP rom with Hellscore kernel, stock settings greenify, full discharge and recharge, all seemed so good....
And then boom. Go to reboot to recovery and I get the little empty battery icon upon reboot - but I was at around 40%?!
I use the battery calibration app, for what it's worth knowing the debate about the battery stats file. I've done the bootloader logs 'trick' and still I get a random occurrence like this?!
Anyone else been plagued with this randomly happening to them?
There are so many reasons it can happen. on thing id recommend is install ampere form play. Using this you should be able to monitor the voltage of the battery and at least know that it is operating within the correct range. if your 0% voltage is too high, it could rule some stuff out.
rootSU said:
There are so many reasons it can happen. on thing id recommend is install ampere form play. Using this you should be able to monitor the voltage of the battery and at least know that it is operating within the correct range. if your 0% voltage is too high, it could rule some stuff out.
Click to expand...
Click to collapse
Many thanks for the suggestion, gonna give that a try now!
cd993 said:
Many thanks for the suggestion, gonna give that a try now!
Click to expand...
Click to collapse
Cool. Just periodically check the app and jot down the percentage and voltage. keep doing that until its ready to shut down. preferably a reading every 10-15% if you can but really important is to try and capture readings just before and after any drop off you may see.
rootSU said:
Cool. Just periodically check the app and jot down the percentage and voltage. keep doing that until its ready to shut down. preferably a reading every 10-15% if you can but really important is to try and capture readings just before and after any drop off you may see.
Click to expand...
Click to collapse
Perfect thanks for the advice, I've got it installed and now juts doing a full charge.
Following that drop out, the device then reported 7% battery so I let that go flat and now fully recharging.
If it's the case that there is something going on here, how can the issue be corrected? Does Ampere help configure reported VS actual readings, or does it purely show what's being drained?
cd993 said:
Perfect thanks for the advice, I've got it installed and now juts doing a full charge.
Following that drop out, the device then reported 7% battery so I let that go flat and now fully recharging.
If it's the case that there is something going on here, how can the issue be corrected? Does Ampere help configure reported VS actual readings, or does it purely show what's being drained?
Click to expand...
Click to collapse
Its worth getting a voltage reading now too then, to see if it is as low as expected. As for solution, we need a root cause first.
rootSU said:
Its worth getting a voltage reading now too then, to see if it is as low as expected. As for solution, we need a root cause first.
Click to expand...
Click to collapse
Ok here is my first screen. I'd browsed Facebook (web version) and watched a video or 2, battery dropped to 97% soon after.
Yep. Just keep going. Every 10% is fine. No more than that. Actual battery charge is voltage so we just want to see if there are any conflicting data sets later on
rootSU said:
Yep. Just keep going. Every 10% is fine. No more than that. Actual battery charge is voltage so we just want to see if there are any conflicting data sets later on
Click to expand...
Click to collapse
Thank you, I'll keep you posted.
danarama said:
Yep. Just keep going. Every 10% is fine. No more than that. Actual battery charge is voltage so we just want to see if there are any conflicting data sets later on
Click to expand...
Click to collapse
It just did it again!!?
I had even doing the Ampere monitoring but didn't go all the way down. But today I just experienced the random drop out again. Strangely when I booted back up, it was as if the cache had been wiped as the Android Optimising app screen came on.
This was from the other day though, if this helps?
The other day did it seem to deplete normally? I'm around 20%/right now and see similar voltage to you.
Sometimes my phone used to crash and when it booted up I had this graph / drainage issue. It's as if it goes into some manic sleep that kills everything. What you've got here seems similar. I don't think there's an issue with the battery cycle itself.
I'd be tempted to do a factory reset and start clean to be honest.
Is the back of your N6 lifting away from the frame? I had this issue too and ended up doing a RMA because the battery was bulging.
danarama said:
The other day did it seem to deplete normally? I'm around 20%/right now and see similar voltage to you.
Sometimes my phone used to crash and when it booted up I had this graph / drainage issue. It's as if it goes into some manic sleep that kills everything. What you've got here seems similar. I don't think there's an issue with the battery cycle itself.
I'd be tempted to do a factory reset and start clean to be honest.
Click to expand...
Click to collapse
Weird and annoying isn't it!
I've recently flashed this new rom and so has been a fresh start so I'm kind of at a loss as to what to try next.
drkboze said:
Is the back of your N6 lifting away from the frame? I had this issue too and ended up doing a RMA because the battery was bulging.
Click to expand...
Click to collapse
Just took off my case and checked and all seems normal, back doesn't appear to be coming away and seems to be ok.
It's times like this I miss my good old Note 3, never had a battery life like it for its flat lining ability!! (see attached)
If it were the battery capacity due to bloating, I would expect to see the Voltage value to be wrong
Go back to stock and run it with no restored apps / data. If it still happens RMA
cd993 said:
Just when I think I've got it all setup nicely...
Latest AOSIP rom with Hellscore kernel, stock settings greenify, full discharge and recharge, all seemed so good....
And then boom. Go to reboot to recovery and I get the little empty battery icon upon reboot - but I was at around 40%?!
I use the battery calibration app, for what it's worth knowing the debate about the battery stats file. I've done the bootloader logs 'trick' and still I get a random occurrence like this?!
Anyone else been plagued with this randomly happening to them?
Click to expand...
Click to collapse
Your battery calibration is messed up. It happens.
DO NOT waste your time with "battery calibration app" -- there is NO software you can install and run from Android that will have ANY impact AT ALL on the battery calibration. All those "battery calibration" programs do, is delete the battery stats file, and all the battery stats file does, is store a log of what programs are responsible for how much resource utilization -- nothing at all to do with calibration.
Battery calibration reset is done through the BOOTLOADER.
Reboot your phone to bootloader. Scroll to "bootloader logs". Press and hold power button until the phone shuts down.
And that is all there is to it.
doitright said:
Your battery calibration is messed up. It happens.
DO NOT waste your time with "battery calibration app" -- there is NO software you can install and run from Android that will have ANY impact AT ALL on the battery calibration. All those "battery calibration" programs do, is delete the battery stats file, and all the battery stats file does, is store a log of what programs are responsible for how much resource utilization -- nothing at all to do with calibration.
Battery calibration reset is done through the BOOTLOADER.
Reboot your phone to bootloader. Scroll to "bootloader logs". Press and hold power button until the phone shuts down.
And that is all there is to it.
Click to expand...
Click to collapse
Thanks for the reply.
Unfortunately, I have tried this many times and so there must be more to it than this. On my latest rom, I had wiped phone and clean flashed whilst phone was connected and at 100%. Therefore a new clean install whilst phone was at 100%. I cleaned that stats (for what it was worth) and also did the bootloader logs trick. I would have thought that would have solved the issue, but as reported it still happened.
cd993 said:
Thanks for the reply.
Unfortunately, I have tried this many times and so there must be more to it than this. On my latest rom, I had wiped phone and clean flashed whilst phone was connected and at 100%. Therefore a new clean install whilst phone was at 100%. I cleaned that stats (for what it was worth) and also did the bootloader logs trick. I would have thought that would have solved the issue, but as reported it still happened.
Click to expand...
Click to collapse
Your calibration is fine because the % matches up to the voltage, which is all calibration matches.
danarama said:
Your calibration is fine because the % matches up to the voltage, which is all calibration matches.
Click to expand...
Click to collapse
Thanks yeah, I thought as much.
The question remains then..... What in earth causes these drop outs!
cd993 said:
Thanks yeah, I thought as much.
The question remains then..... What in earth causes these drop outs!
Click to expand...
Click to collapse
It's hard to say. It seems like the system may be crashing or something at that time and causing an inordinate drain. Thats what mine used to do sometimes.
I finally managed to fix the battery drain issue. After flashing DN7 BOOM v4 ROM or any Note 7 ported ROM, I faced severe battery drain. My battery will last only 8 hours or less. Even on standby mode my battery drains. When I check the Battery usage, it show "Android System" and "Android OS" the most. In that "Android System" drains the battery big time. I tried many fixed and still I see "Android System" will start draining. To cut the story short, these are the 2 fixes I did and I was able to get almost 2 days on my N910c, with my old battery. Screenshot attached.
1. I installed "Wakelock Detector" from play store which shows "Android System" the culprit.
2. Go to settings - application - "OM Customize" - Force Stop it. This showed a bit of improvement, but this process will start again. I don't know exactly what this process do.
3. Go to settings - Cloud and Accounts - Samsung Cloud. I switched off all items in sync settings. This was the main reason for drain.
4. Go to settings - Cloud and Accounts - Backup and Reset - Backup my data - Switch this OFF. Then reboot your phone into RECOVERY, Wipe CACHE and reboot your phone. Switch ON "Backup my data" again.
5. Forgot this important point to add. When you initially setup your device, DO NOT RESTORE APPS from previous backup from Google. I restored only Phone logs, Messages, Settings (wifi and other) only from Samsung account. When I restored APPS before, it keeps Android OS and Android System high.
In case you restored app, then do a factory reset and redo step 5. When you factory restore, In some roms you will need to re-root and install TWRP again.
After doing these 5 steps my phone battery last from 8 hours to 45 hours. For those who are having battery issue, try this. It may work for you too.
Screen on time?
ajueapen said:
I finally managed to fix the battery drain issue. After flashing DN7 BOOM v4 ROM or any Note 7 ported ROM, I faced severe battery drain. My battery will last only 8 hours or less. Even on standby mode my battery drains. When I check the Battery usage, it show "Android System" and "Android OS" the most. In that "Android System" drains the battery big time. I tried many fixed and still I see "Android System" will start draining. To cut the story short, these are the 2 fixes I did and I was able to get almost 2 days on my N910c, with my old battery. Screenshot attached.
1. I installed "Wakelock Detector" from play store which shows "Android System" the culprit.
2. Go to settings - application - "OM Customize" - Force Stop it. This showed a bit of improvement, but this process will start again. I don't know exactly what this process do.
3. Go to settings - Cloud and Accounts - Samsung Cloud. I switched off all items in sync settings. This was the main reason for drain.
4. Go to settings - Cloud and Accounts - Backup and Reset - Backup my data - Switch this OFF. Then reboot your phone into RECOVERY, Wipe CACHE and reboot your phone. Switch ON "Backup my data" again.
After doing these 4 steps my phone battery last from 8 hours to 45 hours. For those who are having battery issue, try this. It may work for you too.
Click to expand...
Click to collapse
On note 7 port roms my phone can last 5-6,5hs onscreen, and can last 7 days (or more) on stand by. 1,5-2 days for usual for calling and some internet check. U should try this way:
https://forum.xda-developers.com/an...ggbMAA&usg=AFQjCNGcUcSBA0JXcOvzipXgx0yZosEMow
-----
But the most important things are on app "Appopsxposed". Try it and enjoy.
More screen shots
beefx said:
Screen on time?
Click to expand...
Click to collapse
I forgot the screen shot for that. But I guess I got 2 hours 28 minutes on that single charge.
Previously it was around 1 hour.
claiphenter said:
On note 7 port roms my phone can last 5-6,5hs onscreen, and can last 7 days (or more) on stand by. 1,5-2 days for usual for calling and some internet check. U should try this way:
https://forum.xda-developers.com/an...ggbMAA&usg=AFQjCNGcUcSBA0JXcOvzipXgx0yZosEMow
-----
But the most important things are on app "Appopsxposed". Try it and enjoy.
Click to expand...
Click to collapse
Thanks for the link. I will try those and see if there is any difference. But without installing any battery related app, but just SAM battery to check battery log and Wakelock detector, i'm getting around 2 days juice.
Thanks for the info! Battery really resurrected back in life !
Aprt from SAMSUNG cloud service which i already disabled, this is the first time i identified OM Service which drains almost 6-8% battery!
Don't know what exactly this service is, It's like a system app which we can't disable though. Trying out with TITANIUM
ROM - DN7 E-Team
N910C
Stock Kernel
CODENEX said:
Thanks for the info! Battery really resurrected back in life !
Aprt from SAMSUNG cloud service which i already disabled, this is the first time i identified OM Service which drains almost 6-8% battery!
Don't know what exactly this service is, It's like a system app which we can't disable though. Trying out with TITANIUM
ROM - DN7 E-Team
N910C
Stock Kernel
Click to expand...
Click to collapse
I guess in Doola Rom v12, I managed to disable it. It's a silent killer. Nothing happened after disabling it, but saves a lot of battery.
Oh sweet! Can I find the link to download that ROM.
Thanks.
CODENEX said:
Oh sweet! Can I find the link to download that ROM.
Thanks.
Click to expand...
Click to collapse
To get the link, search that rom name in youtube and in the video's description you will find the link to download the rom.
ajueapen said:
To get the link, search that rom name in youtube and in the video's description you will find the link to download the rom.
Click to expand...
Click to collapse
Thanks. Saw your videos though