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.
Related
Hi all I installed JT's super clean rom a few days ago with the 11/11 kernal nonvoodoo (all other kernals killed my battery) and my phone still dies way faster than it did on stock. I dont want to do a backup quite yet because i love the look and feel of this rom. My display on time went from 3.5-4.0 hours to just over 2 after i installed this rom and kernal. Also no new apps or changes in my day to day activites. I have wiped battery stats but it didnt help much, so Im hoping if i restore the stock fascinate kernal, my battery will be great again but i cant find the stock kernal anywhere. Could someone point me in the right direction. Thanks
Check you applications that you have installed as one of them may be preventing the phone from sleeping, which drains the battery. You could also go to Settings>About Phone>Battery Use and see what is draining the battery as well to see if anything jumps out.
justinc101011 said:
Hi all I installed JT's super clean rom a few days ago with the 11/11 kernal nonvoodoo (all other kernals killed my battery) and my phone still dies way faster than it did on stock. I dont want to do a backup quite yet because i love the look and feel of this rom. My display on time went from 3.5-4.0 hours to just over 2 after i installed this rom and kernal. Also no new apps or changes in my day to day activites. I have wiped battery stats but it didnt help much, so Im hoping if i restore the stock fascinate kernal, my battery will be great again but i cant find the stock kernal anywhere. Could someone point me in the right direction. Thanks
Click to expand...
Click to collapse
Look under the ODIN post, it should be there
I'm using a 9020A model purchased on Ebay for 2 weeks now.
twice already within a few days the phone will not turn on in the morning after charging it all night (in stand-by).
It will not turn on even into boot-loader.
if I take out the battery it turns on like nothing happened.
Any idea what the problem is ?
kalda01 said:
I'm using a 9020A model purchased on Ebay for 2 weeks now.
twice already within a few days the phone will not turn on in the morning after charging it all night (in stand-by).
It will not turn on even into boot-loader.
if I take out the battery it turns on like nothing happened.
Any idea what the problem is ?
Click to expand...
Click to collapse
Thats what you called "SOD" screen of death. Just pull your batery when it happen. Also it might be kernel related try changing kernel
Sent from my Nexus S
I'm running CM7 since day one with whatever kernel it came with.
What other kernel might work with CM7 ?
There are still a couple though i don't think any are in development any more. Since it seems to have only happened once so no need to try out different kernels. I wouldn't worry about it at all unless it becomes a regular occurrence.
This seems to have happened to many others with the stable CM7 rom version.
In another post someone who had the issue reported that switching to Netarchy's kernel addressed the problem for him.
This happened already twice today so looks like I need to find a solution.
How difficult it is to replace just the kernel?
Get ahold of a GB compatible kernel, wipe dalvik cache and flash the kernel .zip file. Do a NANDROID backup beforehand (CWM -> backup) if you don't have a recent one already.
In another post someone suggested the following Kernel:
http://forum.xda-developers.com/showthread.php?t=936219
There are CFS & BFS builds. which one should I use? what is the difference ?
Also the kernels are labeled as "2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones)", However the CM7 rom is based on 2.3.7. would that work ?
kalda01 said:
In another post someone suggested the following Kernel:
http://forum.xda-developers.com/showthread.php?t=936219
There are CFS & BFS builds. which one should I use? what is the difference ?
Also the kernels are labeled as "2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones)", However the CM7 rom is based on 2.3.7. would that work ?
Click to expand...
Click to collapse
CFS is a fairer CPU allocation scheduler, and generally better for multitasking as well as overall performance. BFS is, in theory, better at doing only the "task at hand", but so far hasn't proven any better than CFS, and is additionally less stable most of the time. tl;dr, get CFS.
Kernel should work fine on 2.3.7, don't stress about it. In the event that something goes wrong, just make sure you have a backup anyway.
netarchy-nexus 1.4.1 CFS Kernel is labeled "experimental" since october 2011. Is it OK to use it anyway ? how exactly is a kernel flashed ? via recovery ?
kalda01 said:
netarchy-nexus 1.4.1 CFS Kernel is labeled "experimental" since october 2011. Is it OK to use it anyway ? how exactly is a kernel flashed ? via recovery ?
Click to expand...
Click to collapse
Yup, it's OK to use it anyway. Also kernel is flashed via recovery.
Sent from my Nexus S from Tapatalk
Any need to wipe or reset the phone before flashing a new Kernel ?
kalda01 said:
Any need to wipe or reset the phone before flashing a new Kernel ?
Click to expand...
Click to collapse
No need. Simply flash the kernel, via fastboot
flashed the kernel via recovery. I'll report back if the SOD problem is resolved.
5 days later and not even a single "SOD" freeze. looks like changing the stock kernel
did the trick.
3 weeks after flashing the Kernel and the SOD problem is back. 3 times in last 2 days.
Anything I can tweak to avoid these freezes ?
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
Hi,
I hope I made this in the right section but I've got myself into a really nasty problem and I know how to fix it after spending full 10 hours. Maybe this will help anybody.
I re-used my Arc after a while and learned about custom roms and all. I've updated to Stock 2.3.4 - Stock 4.0.4 - Ultrakitkat 2.0.1 - Stock 4.0.4 (back because of trying to compare performances between custom and stock) - Ultimate HD 5.0.1.
When going from Ultrakitkat to Stock 4.0.4, after a day I woke up and found my phone rebooting Android on a loop while in the wall-charger. Went to take a shower and the phone was dead.
Charger didn't work, put it on my laptop USB and went on, only to find the battery at 100%. When disconnecting the phone, it immediately went blank and didn't turned on. I've looked for this problem for so many hours and tried flashing my romand kernel for some time (including phone drops dead WHILE in flashing) and trying out different way's to connect and boot but nothing worked. Installed many battery tools and apps but still nothing.
I;ve searched a lot and didn't found any conclusion anywhere, but combining every information online I've solved it!!
Apperantly there is an error inbetween roms, that when you go from custom rom + certain kernels, back to stock rom, it stops recognizing the battery.
To solve this (for me it worked):
Flashtool stock TFT 4.0.4
Fastboot flash the LUPUSV16 kernel (the magic trick!)
Turn on phone, and put it on a charger for 15 minutes, it should start recharging somewhere and show the correct battery %
I wanted to use the Ultimate HD just for a try and when flashing (I use Advanced Stock Kernel) + Ultimate HD
DO NOT WIPE BATTERY STATS! This will recreate the problem.
This worked for me and I hope this will help someone too who's thinking there is a problem with the battery.
Mostly reflashing the kernel does the job
Sent from my LT18i using xda app-developers app
0 or 100 percent battery
hridayharia said:
Mostly reflashing the kernel does the job
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Leaving the phone turned off for some hours worked for me!
Thank you!
if you dont want see this problem
do not downgrade to stock kernel
Same issue here.. after fastbooting stock ftf.. Phone not charging and not recognized in fastboot/flashmode
Guys worked for me
Flash rush kernel after downgrading and tada its done.
Its just coz rush recognizes the hardware chip algorithm for battery stats
Sent from my Xperia Arc S using Tapatalk
Swapyyyyy said:
Guys worked for me
Flash rush kernel after downgrading and tada its done.
Its just coz rush recognizes the hardware chip algorithm for battery stats
Sent from my Xperia Arc S using Tapatalk
Click to expand...
Click to collapse
yes, it works flashing other kernel but i encountered a another problem. I lost some of the apps and keep geeting crashing report from diferent sistem apps Does some know how to extract those battery fix from those kernel am apllly it to stock kernel?
hey guys, so i have a retgb stock rom for lollipop, how would i go about just flashing the modem from that rom. I want to do this to test a theory i have about the battery drain on marshmallow, to see if its caused by the new modem, any help would be appreciated...
certainly not caused by the modem. Did you clean flash? What did you do to upgrade? etc? have you disabled wifi/bluetooth scanning in the extended location settings, deleted play services data yet?
Benjamin_L said:
certainly not caused by the modem. Did you clean flash? What did you do to upgrade? etc? have you disabled wifi/bluetooth scanning in the extended location settings, deleted play services data yet?
Click to expand...
Click to collapse
updated from a stock moto x play single sim, retgb to marshmellow via normal ota, had no root or bootloader unlocked. After the ota i installed twrp and rooted, wiped cache and data, did a factory reset. Then did everything you said above. Then tried with squid kernel, still have massive battery drain about 1 hour sot and barely lasts me 1 day. So yea... i thought it was worth a shot just trying my idea about the modem...
Tvman1231 said:
updated from a stock moto x play single sim, retgb to marshmellow via normal ota, had no root or bootloader unlocked. After the ota i installed twrp and rooted, wiped cache and data, did a factory reset. Then did everything you said above. Then tried with squid kernel, still have massive battery drain about 1 hour sot and barely lasts me 1 day. So yea... i thought it was worth a shot just trying my idea about the modem...
Click to expand...
Click to collapse
Really strange. Any special apps you use? Whats the app on top of your battery stats?
Benjamin_L said:
Really strange. Any special apps you use? Whats the app on top of your battery stats?
Click to expand...
Click to collapse
Mobile standby and phone idle, i have xposed and greenify installed, no speacial apps installed if you dont include kernel adiutor. Im gonna try going back to 5.1.1 stock and try a 6.0 stock rom via twrp, il post the results later.
Frequency stats probably show deep sleep as unused state?
Benjamin_L said:
Frequency stats probably show deep sleep as unused state?
Click to expand...
Click to collapse
no, deep sleep is being used like 92% of the time
So basically everything is working fine. In some other thread I read xposed seriously cripples battery life. I'm not using it so I can't tell
Benjamin_L said:
So basically everything is working fine. In some other thread I read xposed seriously cripples battery life. I'm not using it so I can't tell
Click to expand...
Click to collapse
well im currently going back to stock 5.1.1 for now, im gonna try my therory, then i try with and without xposed, see if it makes a difference
@Benjamin_L well i can safely say that xposed makes no differece that i can see to the battery life so far. After flashing the old stock (5.0, including the modem, through fastboot) then going back to 6.0 by flashing the stock rom by GtrCraft via twrp my battery life seems to have improved quite a bit. So maybe it is the modem after all? Also why did you say it cant be the modem in the first post? just curious...
Tvman1231 said:
@Benjamin_L well i can safely say that xposed makes no differece that i can see to the battery life so far. After flashing the old stock (5.0, including the modem, through fastboot) then going back to 6.0 by flashing the stock rom by GtrCraft via twrp my battery life seems to have improved quite a bit. So maybe it is the modem after all? Also why did you say it cant be the modem in the first post? just curious...
Click to expand...
Click to collapse
I ran both modems on 5.1.1 and 6.0 on several roms and stock firmwares and there was no difference, except for rom related things. And I never heard modem influences battery life dramtically if at all. On my old n4 i flashed several basebands and never noticed any difference in battery consumption at all.
Benjamin_L said:
I ran both modems on 5.1.1 and 6.0 on several roms and stock firmwares and there was no difference, except for rom related things. And I never heard modem influences battery life dramtically if at all. On my old n4 i flashed several basebands and never noticed any difference in battery consumption at all.
Click to expand...
Click to collapse
well, my phones now getting around 4hrs sot so im happy. XD