Related
OK, this is unbelievable.
The battery drain on XXJVO was driving me crazy. Reading the forums I noticed some people said the Android OS issue was fixed on 2.3.4. Yesterday, I flashed XXJVR with re-partition and bootloaders via Odin, using the OXAJVQ CSC. I also installed the Voodoo lagfix for XXJVR.
I did a factory reset before and after the flash. Did a battery pull, all the steps that we're used to.
For my surprise, a few minutes ago, the phone discharged in 8 hours to 47%. Guess what? Its the Android OS again. Take a look at the attached screenshots.
Did I do something wrong? Is this normal on 2.3.4?
EDIT: Following $omator and madrooster's advice, I decided to flash everything again from scratch and install all the apps directly from the Android Market. Apparently, the issue was being triggered by a restored appdata backup via TitaniumBackup. I've been using the phone for about a week now, with no issues at all.
im running custom rom gingerreal 7.1.4 JVQ with galaxianEE kernel and lagfix enabled. my modem is ZSJPG and csc XAJVQ.
no issues like u have.
but i have to say, that the battery drain is heavier than on froyo.
Man, that's pretty serious drain. I'm running Ramad's stock deodexed JVR since it was postes with semaphore kernel and my usage is never more than 15%. Why don't you post a pic of the bigger graph?
only way to avoid battery drain is that you remove the battery from phone
have no idea haw did you managed to break jvr but you did it =)
i guess youve runed some app that was not letting phone to sleep
or the system got some broken ones tat caused this (yes wrongly flashed system maybe hehe)
btw notice the blue line under your graph - it should look more like on attached screen
Im also running gingerreal 7.1.4 JVQ with semaphore 1.32 and after 2 weeks of use no battery drain.
Android OS is always below 10% (mostly on 4-5%)
The Android OS bug was fixed from stock JVQ onwards. The reason you guys experience that is because you are using custom kernels built from old source codes released by Samsung or heavily modified by the developer. Go complain to your respective custom kernel thread.
jbdroid said:
The Android OS bug was fixed from stock JVQ onwards. The reason you guys experience that is because you are using custom kernels built from old source codes released by Samsung or heavily modified by the developer. Go complain to your respective custom kernel thread.
Click to expand...
Click to collapse
Thanks jb. That could be the reason. I am using Voodoo kernel, maybe that's what causing the drain. Has anyone else on Voodoo experienced the same problem?
Heritz said:
Thanks jb. That could be the reason. I am using Voodoo kernel, maybe that's what causing the drain. Has anyone else on Voodoo experienced the same problem?
Click to expand...
Click to collapse
Were you playing orientation/sensor-based games?
jbdroid said:
Were you playing orientation/sensor-based games?
Click to expand...
Click to collapse
jb, I remember that I played Captain America in the morning, but the phone froze and I had to battery pull it. After the restart, I didn't touch it again for like 6 hours. In the night, the phone rang and when I tried to pick up the call, the screen wouldn't turn on, so I had to battery pull it again.
After I turned it back on, I checked the battery stats and noticed the Android OS was running crazy, as you can see in the screenshots.
Captain America afaik is not sensor based, and I battery pulled the phone after I played, cuz it froze. I'd love to blame the game, but I cannot.
Edit: But... looking at the stats, the orientationd process is right next to the Android OS. Could this happen if the phone wasn't resting on a flat surface? :S
Yup the orientationd process was burning you battery juice, the reason why you got Android OS bug. I guess you should try to change your custom kernel or if you really like your current phone setup, you should install Watchdog lite or any similar app to monitor system processes, such as Android OS, for unusually high cpu usage and just reboot your phone when it does occur
i wonder what else is broken in this guys phone that wathcdog and reserting will not fix =)
$omator said:
i wonder what else is broken in this guys phone that wathcdog and reserting will not fix =)
Click to expand...
Click to collapse
$omator help me out here. What kernel would you recommend for JVR that keeps everything as stock as possible but includes lagfix? I use Voodoo since it is pretty light, but it doesn't seem to behave so well after all.
stock + cfroot is always a win
jbdroid said:
The Android OS bug was fixed from stock JVQ onwards. The reason you guys experience that is because you are using custom kernels built from old source codes released by Samsung or heavily modified by the developer. Go complain to your respective custom kernel thread.
Click to expand...
Click to collapse
+1 very true the kernels for me to showd diffrnt results
No battery drain for me here I've been on it for weeks with heavy use friend, never pass 5 hours in any froyo firmware
Sent from my GT-I9000 using xda premium
Android os drain goes away for my 2.3.3 kg3 stock setup after wiping cache partition and dalvik cache. Ran for weeks and never came back.
Sent from my GT-I9000M using XDA app
This battery drain problem is caused by the kernel you have. It is caused by a bug in a specific device driver.
The phone tries to go into power save mode but something prevents it. When the phone fails to reach a low power mode, you see the battery drain. In summary, if you run a custom, non stock Rom you might not have the battery drain fix. Try to make sure that any custom kernel you use has the same kernel version as stock.
Wow that is pretty big drain.. On my xxjvr (2.3.4 ) it only uses 9 to 10% don't know what's wrong though
Sent from my GT-I9000 using xda premium
$omator said:
stock + cfroot is always a win
Click to expand...
Click to collapse
Not for me...
1. Clean the phone.
Flashed JVR (from samfirmware). Flashed CF-Root-XX_OXA_JVR-v4.1-CWM3RFS. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX.
All closed by me in settings (NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 22.00 hour battery was at 98%.
Next day in the morning at 10.30 hour, the phone beeps that the battery is at 15%... Looking in the Battery use, discover that in about 12 hours, the Android OS (90%) is draining the battery. OMG...
2. Fully charge the phone, clean the phone.
Flashed JVR (from samfirmware). Flashed speedmod-kernel-k15i-t10. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX.
All closed by me in settings(NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 22.00 hour battery was at 96%. Next day in the morning at 09.30 hour, check the phone.
Surprise! At about 12 hours, the battery "lose" only 4%. And NO Android OS in the battery use.
3. Next day, clean the phone. Fully charge the phone.
Flashed JVR (from samfirmware). Flashed TalonDEV-0.4.4.22-1200-I9000-BIGMEM-CWM3. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX. All closed by me in settings(NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 23.00 hour battery was at 98%. Next day in the morning at 08.00 hour, check the phone.
Surprise! At about 10 hours, the battery "lose" only 5%. And NO Android OS in the battery use.
4. Next day, clean the phone. Fully charged battery.
Download again the CF-Root-XX_OXA_JVR-v4.1-CWM3RFS.
Flashed JVR (from samfirmware). Flashed again CF-Root-XX_OXA_JVR-v4.1-CWM3RFS. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX.
All closed by me in settings (NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 21.00 hour battery was at 90%. Next day in the morning at 07.00 hour, looking in the Battery use, discover that in about 8 hours, the Android OS (90%) is draining the battery and the battery is at 25%...
I'm not a specialist in Android, but with this experiment, understand that in my case, the "drayner" of the battery was decided by the kernel, and I decided to flash the JVR stock+ with speedmod-kernel-k15i-t10.
I don't say that the CFroot is bad or that another kernel is good, but for me CFroot don't works good.
Kernels no longer work for me. I was running _Motley's build 49 kernel and the stock ROM for a few months and never had any issues and had excellent battery life. Then I decided to flash PA and _Motley to give Halo a try and noticed my battery wasn't all too great. I then nandroid back to my previous setup and then my battery life went to ****. Android OS was my biggest drain so I reflashed my stock rooted ROM and kernel and still had the same issue.
Then I flashed Faux's reset kernel and was stuck in a boot loop but was unable to get past the Google logo. Flashed another reset kernel, can't remember who's, and everything was fine. Android OS wasn't an issue anymore but my battery life went back to being mediocre. So I tried flashing other kernels, _Motley's included, and Android OS would still be on top.
So for some reason, only the stock kernel is working for me. Any ideas why? I'm about to just restore the factory image and start over again. I heard PA uses a custom kernel from Franco so could that be why I'm having issues?
Edit: I also fully charged my battery and left it overnight unplugged last night and went from 100%-64% in 8 hours
Sent from my Nexus 4 using xda app-developers app
Hero_Guy said:
Kernels no longer work for me. I was running _Motley's build 49 kernel and the stock ROM for a few months and never had any issues and had excellent battery life. Then I decided to flash PA and _Motley to give Halo a try and noticed my battery wasn't all too great. I then nandroid back to my previous setup and then my battery life went to ****. Android OS was my biggest drain so I reflashed my stock rooted ROM and kernel and still had the same issue.
Then I flashed Faux's reset kernel and was stuck in a boot loop but was unable to get past the Google logo. Flashed another reset kernel, can't remember who's, and everything was fine. Android OS wasn't an issue anymore but my battery life went back to being mediocre. So I tried flashing other kernels, _Motley's included, and Android OS would still be on top.
So for some reason, only the stock kernel is working for me. Any ideas why? I'm about to just restore the factory image and start over again. I heard PA uses a custom kernel from Franco so could that be why I'm having issues?
I also fully charged my battery and left it overnight unplugged last night and went from 100%-64% in about 8 hours.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Here's a logcat
How is your battery life under Android Marshmallow 6.0.1?
I updated the new N920CXXU2BPB6 (CAM) and after 2hours and 20mins its down to 77% from full charged (( and also the fast charging is slowly
a2kay said:
How is your battery life under Android Marshmallow 6.0.1?
I updated the new N920CXXU2BPB6 (CAM) and after 2hours and 20mins its down to 77% from full charged (( and also the fast charging is slowly
Click to expand...
Click to collapse
You had a root b4 M
I'm none root
I think there is issue with the drain, but it's not sammy fault. if you google Android 6.0.1 problem you'll see many nexus users pointing out that their is a battery drain issue, hope sammy can fix it or it won't affect us as much, Android M suppose to kill those issues it seems like Lollipop 5.0 again.
Here are my battery usage. I think thats not good. Lollipop was better.
Sync, Bluetooth, wlan is off. Screen is autobrightness at 100%
Anybdoy a idea?
One day is not enought to say anything about battery life ... maybe after couple of days .
Android os consumes my battery 8%... is this a fee for root my device by samsung??? What the f.... is that?? I cant use my phone without root or custom kernel??? F.... off samsung!!
Sent from my SM-N920C using Tapatalk
Thought I'm alone, anyways, the screen on-time is not bad and can go to 6 hours (if used at once), however when the phone is off, the battery drain is huge and doze mode doesn't seem to be working either..
from 2 to 6 am, the phone was on a table and I was asleep and the drains looks to be huge
No problem with drain for me
Laurentiu27 said:
No problem with drain for me
Click to expand...
Click to collapse
What your settings? Display brightness? What apps deactivate? Thanks
Stock settings nothing done to the system display brightness on auto but to full brightness nothing deactivated
Guys i think the issue is with root. IF you rooted your phone before, installed customer rom, installed kernel or installed recovery this issue will happen .
Someone on the forum point it to knox fused burn and it can no longer go back to normal.
Yathani said:
Guys i think the issue is with root. IF you rooted your phone before, installed customer rom, installed kernel or installed recovery this issue will happen .
Someone on the forum point it to knox fused burn and it can no longer go back to normal.
Click to expand...
Click to collapse
+1
Rightly said.
If you have tripped Knox while rooting previously, never ever installing a STOCK ROM (May it be lollipop or MM) will fix the battery drain issue since there is some read cycle which the kernel does continuously if the Knox is tripped which can only be overridden with a Custom Kernel.
So, either wait till we get a custom Kernel on MM and root (Ofcourse) or enjoy the new Look n Feel at the cost of battery drain
Btw, I am un-rooted on Stock N9208 (Waiting for MM in my region)
anmolkakkar said:
+1
Rightly said.
If you have tripped Knox while rooting previously, never ever installing a STOCK ROM (May it be lollipop or MM) will fix the battery drain issue since there is some read cycle which the kernel does continuously if the Knox is tripped which can only be overridden with a Custom Kernel.
So, either wait till we get a custom Kernel on MM and root (Ofcourse) or enjoy the new Look n Feel at the cost of battery drain
Btw, I am un-rooted on Stock N9208 (Waiting for MM in my region)
Click to expand...
Click to collapse
Check this guy out. He revert back from root and kernel but he doesn't have the wakelock issue. Interesting to say atleast
http://forum.xda-developers.com/note5/help/deep-sleep-64gb-version-revert-to-stock-t3280042
Yathani said:
Check this guy out. He revert back from root and kernel but he doesn't have the wakelock issue. Interesting to say atleast
http://forum.xda-developers.com/note5/help/deep-sleep-64gb-version-revert-to-stock-t3280042
Click to expand...
Click to collapse
Yeah Man, i was just reading this post before you quoted me
I too am surprised, maybe the UAE room has some Deep Sleep fix in it built?
Can we confirm? :fingers-crossed:
anmolkakkar said:
Yeah Man, i was just reading this post before you quoted me
I too am surprised, maybe the UAE room has some Deep Sleep fix in it built?
Can we confirm? :fingers-crossed:
Click to expand...
Click to collapse
no it doesn't not but maybe the way he fully clear all data from the phone then installed a clear version.
so far so good for me.
ram management is better than lollipop an doze mode work perfect!
i factory reset my phone after MM and i use dual sim phone !
but i disable facebook , skyp , Svoice and google music
Yathani said:
no it doesn't not but maybe the way he fully clear all data from the phone then installed a clear version.
Click to expand...
Click to collapse
I installed MM yesterday with a full wipe, cleared all my storage and i had deep sleep issue coz i have knox 0x1.
Sent From Samsung Galaxy Note 5
So, either wait till we get a custom Kernel on MM and root (Ofcourse) or enjoy the new Look n Feel at the cost of battery drain
Btw, I am un-rooted on Stock N9208 (Waiting for MM in my region)[/QUOTE]
so there is no any way to fix battery drain after tripped knox we can never get deep sleep on stock 6.0?
mtayabkk said:
So, either wait till we get a custom Kernel on MM and root (Ofcourse) or enjoy the new Look n Feel at the cost of battery drain
Btw, I am un-rooted on Stock N9208 (Waiting for MM in my region)
Click to expand...
Click to collapse
so there is no any way to fix battery drain after tripped knox we can never get deep sleep on stock 6.0?[/QUOTE]
You will never get stock everything deepsleep. So all future updates are null and void for everyone. Unless you get a modified stock kernel to fix the deepsleep. Or a custom kernel. Unrooting doesn't help as Knox ix 0x1
Is it only for me or the battery life has been drastically reduced after the nougat update ? If I'm the only one who has this , any possible fix ?
sam sundar said:
Is it only for me or the battery life has been drastically reduced after the nougat update ? If I'm the only one who has this , any possible fix ?
Click to expand...
Click to collapse
Try factory resetting.
I always get 30-40 hours with 4 hours SOT.
Caliberate it once.. drain the battery till your phone switches off and then charge it with the official cable and switch on only when 100% is complete... that should help... The SOT is not real, it depends on the usage....and can change drastically... when u keep the phone idle or when u start using it....
Iqbal Ansari said:
Try factory resetting.
I always get 30-40 hours with 4 hours SOT.
Click to expand...
Click to collapse
My phone came from service centre yesterday only .
abhi212b said:
Caliberate it once.. drain the battery till your phone switches off and then charge it with the official cable and switch on only when 100% is complete... that should help... The SOT is not real, it depends on the usage....and can change drastically... when u keep the phone idle or when u start using it....
Click to expand...
Click to collapse
Have tried it in marshmallow , should try now .. thanks
Same for me, fixed with ElementalX kernel.
I had the same problem with stock Nougat and AOSP extended. At the same time my phone was heating up. So, I go back to stock MM.
titou4488 said:
Same for me, fixed with ElementalX kernel.
Click to expand...
Click to collapse
Which version of Elemental X kernel did you flash in the stock N OS buddy? And are you rooted as well? when I flashed the Elemental X 1.02 and flashed the root file, it kind of disabled the notification sounds totally.
Now i flashed elemental x 1.04 for stock N firmware and rooted with phh's superuser and no issue at all
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672
I flashed my SM-G900V a few weeks ago from 6.0.1 QB2 to 5.0 PB1 and I noticed the battery life is worse than it was before. The battery life on 6.0.1 was not the greatest in the first place. I was only able to get 3 hours of screen on time, if I was lucky I could reach 3 hours 30 mins. Now I am averaging about 2 hours 30 minutes and if I am lucky I can reach 3 hours. I took a look at the battery stats and I noticed mdnsd is the first thing using up 13% of my battery. What is mdnsd and is there a way to improve battery life a bit? I do not want to revert back to 6.0.1 as I want to root my phone in the future, 5.0 was what came with the phone when I got it in 2015.
Pb1 is and order stock rom qb2 is one of latest updates from g900v
Sent from my SM-G900V using Tapatalk
Kastro1784 said:
Pb1 is and order stock rom qb2 is one of latest updates from g900v
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Yes my S5 was running qb2 until I flashed it back to PB1.
Yes, older versions of the OS had worse battery life.
Sent from my SM-G900V using Tapatalk
I went the other way about two weeks ago. Battery life on PB1 was never great and over the prior ~2 months I kept getting these episodes where something would go into turbo and crush the battery. I'm now on QB2 and it is very good.