Related
Hello all. Ever since I got my EVO, I've been experiencing random restarts, even before I was rooted. Right now, I am running CM7.1 and Tiamat from kernel manager, and I probably have to do about 8 restarts and 5 battery pulls a day, no matter how often I use the phone. For instance, today I woke up and had to do a battery pull because the screen would not turn on. The light was also still orange despite the battery being fully charged. I unplugged it at about 8 in the morning and by 10 with no use, I had to pull the battery again because the screen was frozen off once again. Once I got it back on, the battery was down to 80%. I tried using it and half the apps would force close immediately, so I restarted... You get the picture. Some roms have been better than others, and kernels don't seem to make any difference, and I figured it was about normal. Then, I installed what is supposed to be a really buggy CM7 on my touchpad, and have only had to restart it once in the past 2 days, which makes me question how stable my phone actually should be. Does it seem like I should take it in to sprint, or is my experience about normal?
I also never overclock because of my already poor battery life and have tried underclocking, but don't see any noticible difference
bump. should I post somewhere else?
Run an RUU but stay s-off for the moment and see if the problem persists. If your phone begins working properly, then you can flash a recovery and flash whatever rom you want - but don't restore your backup. I'd start totally fresh if RUUing fixes your problems, don't restore your apps and data, just download them from the Market as you need them.
If the RUU doesn't help and the problem continues, take it in to Sprint. It's up to you if you want to s-on before taking it in - I've never heard of anyone getting problems from Sprint with s-off but without root, but I think it's a general rule to do so.
I hope everything works out for you!
Sent from my Evo + MIUI using Tapatalk!
I have heard and seen on here many times that random reboots are caused by battery problems, and bad software installs. Try calibrating the battery, also use battery monitor widget to see what ur batt temps are. Then reinstall all your apps, do not restore them then see if that helps.
Sent from my PC36100 using XDA App
I'll try an RUU when I get enough time to do some thorough testing. I have reinstalled everything directly from the market multiple times since I've had the phone, and also have used a total of four batteries with no change in behavior. I Will try the RUU soon though. Thanks for the replies
I flashed a custom ROM [unofficial CM9 ICS4.0.4]. Everything seems to be working fine, but there are a few problems and I'm wondering if this is normal for those using this. It's my first time flashing a ROM on my android and I'm not sure if it's normal. Did some searching in the forum, couldn't find much info too. Maybe I didn't search hard enough!
Anyway, here are some issues, I'm not even sure if it's the ROM.
1. Sometimes, the apps just bring me back to the home screen several times. Example: Running whatsapp brings me to home screen a few times, or when I go into a conversation, it brings me back to the conversation list but eventually it works.
2. On another occasion, every app that I ran would be unresponsive and I needed to end it. Solved it by rebooting.
3. Battery drain is very fast with little usage. I thought running a custom ROM usually provides better battery life.
I've not overclocked it, it's still in it's default value after flashing 1024. So I doubt it's anything to do with that. But since we're on the topic on overclocking. Desire HD didn't have anything beyond Gingerbread. So if we're flashing anything greater, is there a need overclock to be able to work comfortably on a higher OS? Is there a minimum or maximum for it to function comfortably?
Thanks!
Hmm, did more reading up.
Could it be I didn't calibrate my battery after flashing a new ROM?
Just flashed ARHD 6.4, will try to calibrate after that.
Appreciate any other advice though
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
crayonslayer said:
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Generally these issues are user related and not ROM related.
I was so frustrated with some of the ROMs when I first started out but then realized I was doing a few things wrong (mainly because these ROMs, including CM10 have very decent battery life).
First, I would recommend a clean reflash:
factory wipe / reset
wipe cache (some say twice)
wipe dalvik cache
install ROM
after rom loads, wait 5 minutes (don't touch at all) then reboot
now you must wait.. sometimes it takes 24 hrs or so for a ROM to correctly load.
Not sure how true it is, but some say to now drain battery down, then fully charge.
At any rate, I follow these steps all the time and works great!
Also, keep in mind that most of battery issues are user related.. so think about what settings, apps and kernels are being used on your end before question a ROM. This is why waiting 24 hours or so before installing all of our "crap" will give give the ROM more time to settle.
Hope this help!!!! Happy Flashing
Thanks for the reply. However, I have looked at what apps and processes are draining my battery. And it appears it is the "phone" process that is doing this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Just to piggyback on spenny88's reply, exactly what did you come from (stock?) and how did you wipe and flash?
This is all key as to how well your device will perform.
xBeerdroiDx said:
Just to piggyback on spenny88's reply, exactly what did you come from (stock?) and how did you wipe and flash?
This is all key as to how well your device will perform.
Click to expand...
Click to collapse
I have noticed something similar. I am coming from stock. I am going to guess my battery life is in the neighborhood of 10% less. I wiped everything before I installed CM. That said, this feels so much faster than stock.
Same Battery Issue on p1 (TMobile original Galaxy Tab 7.0)
spenny88 said:
Generally these issues are user related and not ROM related.
I was so frustrated with some of the ROMs when I first started out but then realized I was doing a few things wrong (mainly because these ROMs, including CM10 have very decent battery life).
First, I would recommend a clean reflash:
factory wipe / reset
wipe cache (some say twice)
wipe dalvik cache
install ROM
after rom loads, wait 5 minutes (don't touch at all) then reboot
now you must wait.. sometimes it takes 24 hrs or so for a ROM to correctly load.
Not sure how true it is, but some say to now drain battery down, then fully charge.
At any rate, I follow these steps all the time and works great!
Also, keep in mind that most of battery issues are user related.. so think about what settings, apps and kernels are being used on your end before question a ROM. This is why waiting 24 hours or so before installing all of our "crap" will give give the ROM more time to settle.
Hope this help!!!! Happy Flashing
Click to expand...
Click to collapse
Having the same issue with my Samsung Galaxy Tab P1000 (p1 in Cyanogenmod). "Cell Standby" is taking as much juice as "Screen", and I am using Wifi only. I don't even have a sim card in the device. Wish there was a way to disable Mobile Networks without disabling Wifi via Airplane Mode.
I installed through Rom Manager as upgrade from CyanogenMod 9.1 with wipe. I will try the recommendations above and report back.
Try the latest nightly (or RC4) of CM10.1. The battery life has definitely improved a bit.
Samsung Galaxy s3 intl battery drain cm10.1
I recently installed cm10.1 nightly on my international S3, it has cut the battery life down drastically and seems to drain over 10% an hour, even when not being used.
I've tried everything that i've came across by searching and still haven't had any real gain on battery life. Doing a full wipe and reinstalling doesn't help, and i've given it time for battery to calibrate; no difference. Even with wi-fi and location services off i'm getting a big drain. I've even tried switching to Slim Bean, if anything the battery was worse still.
Firstly i'm getting that Android OS is eating up a large chunk (usually above 60%) and using BetteryBatteryStats i don't see anything out of the ordinary in terms of partial and/or kernel wakelocks. I really don't wanna have to put the stock Touchwiz rom back on but that seems like the ways it's going. Any help would be greatly appreciated. Is there anything else i can try?
i find i get terrrible battery life on AOSP when i restore google through the setup. i skip thru the installation and open the play store to enter my gmail. then, before restoring my apps, i let it charge to 100%. honestly AOSP still doesnt have decent battery life, but it does improve if you play with it and try different things
hapticxchaos said:
i find i get terrrible battery life on AOSP when i restore google through the setup. i skip thru the installation and open the play store to enter my gmail. then, before restoring my apps, i let it charge to 100%. honestly AOSP still doesnt have decent battery life, but it does improve if you play with it and try different things
Click to expand...
Click to collapse
I would respectfully disagree with you. I have run a number of ASOP based ROMs and find them better than stock in terms of battery life. Certainly better in terms of not making my eye bleed (as I hate touchwiz, but that is a personal preference). I find that SlimBean gets me the best battery life of the CM based ROMs.
To clarify, I get just over 1%/hour battery drain, when idle (as measured by BBS) with GPS and google sync enabled, mostly on LTE. My phone happily spends almost all the time I am not actively using it in deep sleep.
The recipe to achieve this is to disable google location reporting and history, avoid tons of widgets that constantly update themselves, disable samsung services that you do not use, and monitor battery usage to look out for rogue apps that do stupid thengs, like hold wakelocks when they should be idle. Dropping the minimum frequency to 192 MHz, and going to ASSWAX (CPU scheduler) and ROW (I/O scheduler) also helps.
To get decent performance you do need to install things properly. Which means ensuring that you don't have conflicting settings or random leftovers. I tend to dirty flash updates but you reallly do get better and more consistent performance going through the pain of a complete clean install (format system, clear cache, reload apps from the store) when you are switching ROMs. Only use TiBu to restore app data. Once you do this, in my experience rogue wakelocks are the biggest cause of lousy bettery perfromance, and you can track down and eliminate these. I have around 150 apps loaded and do not run any task manager/autokiller. My phone typically runs without any reboots or power cycles between ROM updates which equates to rebooting every couple of weeks to a month. I have seen over 2 months of uptime.
Certainly should be able to go 16-20 hours between charges which I would consider real world all day functionality. I guess my point is that rock solid stability and all day battery life is possible if you are systematic about how you do things.
crayonslayer said:
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem..... Battery lose 1 % every 2 mins thats terible. :crying:
How could i find a fix ? plz if u have fix yours tell me ???
Hi Guys,
i have a bit of a problem with the battery in my GNex maguro.
I'm an avid Rom flasher, but when i have something that works well i usually settle with it for a while. So i flashed Cataclysm (http://forum.xda-developers.com/showthread.php?t=1995801) sometime in the last months and it was running great. Best bettery life i had so far.
Then with the release of Android 4.4 i looked for a rom to test it. I flashed XP (http://forum.xda-developers.com/showthread.php?t=2539201) and i really like the 4.4 changes.
But since then my battery won't even last a day in standby mode. I thought maybe it's an issue with 4.4. still, but even after flashing back to Cataclysm (newest release) i still had the same issues. I thought it may well be, that the final version isn't what it used to be, so i flashed another rom again. This time Purity (http://forum.xda-developers.com/showthread.php?t=2012706) aaaand... still the same problem. So now i'm pretty much lost. I also tried different kernels (lean kernel specifically) but to no avail.
My battery used to last 2+ days in idle mode. Now i can see my battery drop every minute. It barely holds over 10 hours. I already did a full phone wipe and flashed back to stock before installing cataclysm again but still no improvement.
I hope someone can help me here or point in the right direction.
Sorry if this topic already exists, but the search funtion doesn't seem to work right now and google didn't show something helpfull.
Thank you all in advance.
I don't know why you would still have bad battery life moving back to the original rom you used but.. on 4.4 it is most likely the new Google Now features that constantly listen for voice commands. Disable it by long pressing on an empty part of the home screen and go to settings. Slide Google Now Off and go to voice and turn off hotword detection as well.
I get great standby battery life on 4.4. I'm running the 11/29 ART build of cmetal(toro), 150ish hours of uptime without any issues so far.
Re: Bad Battery Life since KK
What kernel are you running? Are you just using whatever kernels come with each ROM?
I'll try turning off google now and the voice stuff and report back.
It still seems really weird to me, that the problem still persists after flashing back to 4.3. My guess would be, that 4.4 flashes something hidden that messes with the battery. But i don't know where or what.
Especially since it persists after a complete wipe (/data, /system and /cache).
Well, i'll see how it behaves without google now.
What kernel are you running? Are you just using whatever kernels come with each ROM?
Click to expand...
Click to collapse
Well i used mostly lean Kernel with 4.3 roms but i can't find any 4.4 kerneles besides CM. I have XP installed right know which uses CM Kernel.
Re:Bad Battery
Make sure your governor is set to interactive or ondemand...it could be seeing power drain from being set to one of the performance settings.
It's also possible that your battery is just going bad...do you have a backup battery you can try?
Well i used mostly lean Kernel with 4.3 roms but i can't find any 4.4 kerneles besides CM. I have XP installed right know which uses CM Kernel.[/QUOTE]
It could just be that you need to replace your battery. They are only good for so many charges and do degrade.
-----------------------------------------------------
Sign up for COPY with this link, and we'll both get 5 GB of free cloud storage in addition to the usual 15 GB: https://copy.com?r=m3arsR
Free GiffGaff SIM with £5 credit: http://redir.info.giffgaff.com/r/?id=h4d8d850,c0e1337,c0e139c&p1=d3xp2pc
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Reporting back. After deactivating google now yesterday my battery is still ****. It's at 50% after 2h idle and 30 minutes screentime. Before the 4.4 flash it would be at around ~85-90% now. I suspect that 4.4 flashes something in some hidden partition that i don't have access to, that messes with the battery. Users on other boards report the same issues as i have.
dwoods1983 said:
Make sure your governor is set to interactive or ondemand...it could be seeing power drain from being set to one of the performance settings.
It's also possible that your battery is just going bad...do you have a backup battery you can try?
Click to expand...
Click to collapse
Just checked. Governor is set to interactive. It's also the default setting.
I sadly don't have a backup battery.
It could just be that you need to replace your battery. They are only good for so many charges and do degrade.
Click to expand...
Click to collapse
Could be, of course. But it's kinda weird that the decline is so dramatic and it has to be a pretty big coincidence that it just happend after a 4.4 flash. Seems unlikely to me.
edit: I'll order a new battery just to eliminate the battery as the source of error.
Mine is pretty bad but it's running google play to death so maybe gapps flash was bad? dunno
merid14 said:
Mine is pretty bad but it's running google play to death so maybe gapps flash was bad? dunno
Click to expand...
Click to collapse
this maybe issue of ram management.. try some good apps to control those background & foreground app from running without control. dont use any task killer.. please
i recommend using greenify.apk. donate version much better.
sorry for my bad english
galaxy nexus i9250
Same problem here. Since I flashed Kitkat on my phone, battery life isn't enough to last a day on standby. I tried installing another kernel (ASKP) but to no avail. Please keep in mind that I'm not very experienced with custom roms and rooting my phone. Does anyone have some good tips to improve battery life?
Update: After fiddling around a bit with better battery stats, greenify and a bunch of other stuff... i still don't have a solution. I made some screenshots of my stats, but can't post them here because i don't have permission to do that...
So i reflashed swordrune's cm11 rom and it seems to be working better with 1080p kernel w/o art enabled. i'm 11 hrs in with 80% battery on the extended battery (toro btw)
Un4s said:
Update: After fiddling around a bit with better battery stats, greenify and a bunch of other stuff... i still don't have a solution. I made some screenshots of my stats, but can't post them here because i don't have permission to do that...
Click to expand...
Click to collapse
are u sure greenify didnt helping??? already got rooted & exposed installer running??
can u state your screen on time??
usually gnex can handle 3-4 hour screen on depend on battery condition n phone performance... not include idle n stanby time.
galaxy nexus i9250
memaro_maro said:
are u sure greenify didnt helping??? already got rooted & exposed installer running??
can u state your screen on time??
Click to expand...
Click to collapse
Yes, i am rooted, but i didn't have the donate version of greenify. Bought it now and will test again.
Screen on time ~1:30h
Un4s said:
Yes, i am rooted, but i didn't have the donate version of greenify. Bought it now and will test again.
Screen on time ~1:30h
Click to expand...
Click to collapse
that will help.
if u lightweight user, i suggest u to optimized performance. use apps such trickster mod, rom toolbox, or in addition of any light battery saving apps ( for optimization)
should be improve on screen time.
galaxy nexus i9250
Not to hijack your thread, but I'm also experiencing battery issues after flashing the XP 4.4 rom. I did enjoy it but the battery drain was terrible. Not only that, for some reason my charger drains on a 1A charger but charges slowly on a .7A somehow. I only have 1 micro usb cable so I can't test if it's the cable and I can't find any apps to check the current speed. I tried downgrading and flashing to Slimbean but so far it's been no dice.
memaro_maro said:
that will help.
if u lightweight user, i suggest u to optimized performance. use apps such trickster mod, rom toolbox, or in addition of any light battery saving apps ( for optimization)
should be improve on screen time.
Click to expand...
Click to collapse
Ok, back again. hibernated every app and system-app that was running in background. Still wasn't getting better. I then saw the only services still running are google location services. I deactivated them now to see if these are causing it.
The biggest wakelocks i have are "wlan_rx_wake" which seem to be a known problem with KK:
http://forum.xda-developers.com/showthread.php?t=2519294
I then researched again and found several threads in google groups which describe the same problems that i have. Across several devices (though mostly Nexus 4, 5 and 7).
Google seems to be aware of that issue and is working on it.
Not to hijack your thread, but I'm also experiencing battery issues after flashing the XP 4.4 rom. I did enjoy it but the battery drain was terrible. Not only that, for some reason my charger drains on a 1A charger but charges slowly on a .7A somehow. I only have 1 micro usb cable so I can't test if it's the cable and I can't find any apps to check the current speed. I tried downgrading and flashing to Slimbean but so far it's been no dice.
Click to expand...
Click to collapse
Yes, same for me. Charging is really slow since 4.4 as is the bootprocess of my phone. From the first vibrate when switching the phone on it takes ~10 seconds until the google logo pops up.
i dont know any about gapps issues bcoz not running any gapps in my phone since last year.
1. try searching for updated radio.img (baseband/ radio) if got any network issue.
2. try install trickster mod app. this app can help you for tweaking into deep sleep, also help for optimizing.
galaxy nexus i9250
crayjin said:
Not to hijack your thread, but I'm also experiencing battery issues after flashing the XP 4.4 rom. I did enjoy it but the battery drain was terrible. Not only that, for some reason my charger drains on a 1A charger but charges slowly on a .7A somehow. I only have 1 micro usb cable so I can't test if it's the cable and I can't find any apps to check the current speed. I tried downgrading and flashing to Slimbean but so far it's been no dice.
Click to expand...
Click to collapse
try this for helping you go into deep sleep
galaxy nexus i9250
memaro_maro said:
try this for helping you go into deep sleep
galaxy nexus i9250
Click to expand...
Click to collapse
Hmm I don't know if this is going to resolve the charging problem but i will try it and also try and use a battery calibrater and come back.
Hey guys,
my Endeavoru PVT (Tegra3 International) is now about one and a half year old, I can't remember how it was in the beginning, but now my battery drain is too heavy in my opinion.
At first I had AHRD, then I switched between some ROMs but now I am stuck at CyanogenMod 10.1.3 because as time went by, I started to hate Sense and I love the standard Android look. The thing is, since I switched from OrDroid to CM 10.2 or better said from Android 4.1 to 4.2+, the drain got heavy.
I removed all wakelocks, I use XM-Kernel with Smartmax+Row and limited the CPU freq, I turned off sync, gps and I only use 3G if I need the speed.
I mostly use whatsapp and rarely browse the internet with my phone, when I wake up at 7:00 AM I disconnect it from the charging cable, then I go to work etc. and at about 9:00 PM the battery only has 20-30% left and the average screen on time is maximum 2 hours overall and that's clearly not ok...
As I already said, I removed all wakelocks, the only wakelocks come from the kernel when the screen is active. So please do not link the ultimate battery life thread or something like that... I have no wakelocks and my settings are ok.
And when I start gaming, the battery drains 1% per minute which is insane! So I can't play any games at all.
With OrDroid and XM-Kernel I had the best battery life and almost no bugs.
Today I wanted to install Skydragon 2.0, but it was pretty buggy. So I switched to AHRD but with the XM-Kernel (17 beta for Sense5) my computer didn't detect the One X, I switched back to Stock Kernel, then it got recognized but the files were all displayed like a mess and I couln't copy any files onto the One X. Then I was pissed and restored my CM 10.1.3 backup... Is there any way to fix this??? Please no mass storage mods, these are not stable and don't work sometimes..
A few days ago I bought a One X+ battery, it should arrive next week. Maybe the battery is broken, but that doesn't explain why it drains so fkng much battery when I start to play games! And it doesn't fix my problems with Skydragon or AHRD. I would love to stay at CM, but there are the common issues which force me to switch to a sense rom.
I will probably switch back to OrDroid with XM-Kernel when the new battery arrives, hopefully it will fix the heavy drain. Can someone explain what could cause this massive drain? I mean, a phone should last at least 24 hours not 14...
Or is there any fully working AOSP rom with Android 4.1 for the One X? So I could benefit from the battery life and the look of Android 4.1.
Did you try erasing your sd card? Corrupt files might cause heavy media drain on aosp without showing wakelocks. I would recommend trying a sense 5 Rom, get a custom kernel and set it to smartmax and row like you are used to. If that doesn't work, replacing the battery is your last call. Good luck!
Go for a full wipe of your device & SD card first than try installing anew sense 5 rom and see whether the issue still persists?
donkyshot said:
Did you try erasing your sd card? Corrupt files might cause heavy media drain on aosp without showing wakelocks. I would recommend trying a sense 5 Rom, get a custom kernel and set it to smartmax and row like you are used to. If that doesn't work, replacing the battery is your last call. Good luck!
Click to expand...
Click to collapse
My sdcard is almost empty and the problem doesn't only happen on aosp but on all Android 4.2 or higher roms.
Did you even read my post? I already said, I tried Skydragon and ARHD and I had bugs... and yes, I made a full wipe 3 times.
shawly said:
My sdcard is almost empty and the problem doesn't only happen on aosp but on all Android 4.2 or higher roms.
Did you even read my post? I already said, I tried Skydragon and ARHD and I had bugs... and yes, I made a full wipe 3 times.
Click to expand...
Click to collapse
Stop being rude to someone trying to help you. Yes I did read your post obviously. You didn't state if you wiped your sd card. So what do you expect from the community if you figured it out all by yourself? If it's not the software it's the hardware, replace the battery.
Sent from my HTC One X using XDA Premium 4 mobile app
donkyshot said:
Stop being rude to someone trying to help you. Yes I did read your post obviously. You didn't state if you wiped your sd card. So what do you expect from the community if you figured it out all by yourself?
Click to expand...
Click to collapse
I didn't meant the part with the sd card, I meant the sentence were you said I should try a sense rom, which I already tried as I stated.
I'm sorry if you interpreted my post as an insult.
Edit: Ok I fixed the USB problem, I installed the newest HBoot and used lyapotas Kernel, now it works without problems. Now I'm going to fix all wakelocks and wait for my new battery.
I removed all wakelocks now and I got about one hour more since then, but at some times the drain is heavyer, I tried to backtrace the drain with GSAM and BBS (root) but there are no Problems with wakelocks. The battery drained from one minute to the other from 72 to 78, I don't know if the stats didn't refresh correctly, but I am now pretty sure it's the battery.
Okay, my battery arrived. I replaced it and besides I fixed my Wi-Fi with a piece of aluminium foil. The drain on the first start was heavy, but I think it has to undergo some full charges to calibrate.
But I have one more problem.. I'm on ARHD 33.1 with lyapotas LM kernel (XM beta didn't work very well), but I can't undervolt with SetCPU (paid for root version). Every time I want to save the undervolt settings SetCPU itself crashes and I don't really want to use TricksterMod for undervolting.
Is it because of lyapotas kernel?
I already reinstalled SetCPU two times..
Update: Wow, I never had 78% battery left after work! I guess it was my battery that was broken, so the thread can be closed.