Hi!
Over a month ago, I installed Cyanogenmod 11 on my Samsung Galaxy S III because I did not like Samsung's OS. I thought everything would be the same, however, I noticed that my battery now has a few problems.
1. My battery won't charge to 100%.
Sometimes it gets stuck at 83%, sometimes at 96%, but it won't charge fully. Worst, sometimes it will say my phone is charged completely, but when I shut down my phone, it says it is only charged at about 40%.
2. My battery has a huge drain.
I have a 4300mAh Extended Battery in my phone, but it will only last 8-9 hours max.
I looked at a bunch of forums to find a solution. I did a lot of battery calibrations, I wiped Dalvik cache, reboot my phone, etc.
Nothing seems to work.
Can someone help me?
hawaiicinqzero said:
Hi!
Over a month ago, I installed Cyanogenmod 11 on my Samsung Galaxy S III because I did not like Samsung's OS. I thought everything would be the same, however, I noticed that my battery now has a few problems.
1. My battery won't charge to 100%.
Sometimes it gets stuck at 83%, sometimes at 96%, but it won't charge fully. Worst, sometimes it will say my phone is charged completely, but when I shut down my phone, it says it is only charged at about 40%.
2. My battery has a huge drain.
I have a 4300mAh Extended Battery in my phone, but it will only last 8-9 hours max.
I looked at a bunch of forums to find a solution. I did a lot of battery calibrations, I wiped Dalvik cache, reboot my phone, etc.
Nothing seems to work.
Can someone help me?
Click to expand...
Click to collapse
Try buying a new cable. Worked for me since I used to have the same problem as you did, even if I was just on stock.
You can try to Replacement a plug.I don't know whether or not it work for you,but it useful for me.
Ler Gies said:
You can try to Replacement a plug.I don't know whether or not it work for you,but it useful for me.
Click to expand...
Click to collapse
I bought a new cable, a new battery. Does not work...
Well, a couple of things could be up, probably rooted in the fact that you have an after-market, non-standard battery, and CM might not be fully equipped to deal with that somehow. Just a theory though.
Also, you can try and get some more info on the problem by installing Boeffla kernel (instead of CM default one). The Boeffla-Config app will give you info on charge-rate, for example. There's probably some apps out there that will offer this and more info on the battery.
Related
Hi everyone, I really don't know where locate this "thing" is happening to my hero but it is definitely related to ROMs.
I recently post my battery problem in the battery's thread in this forum but seems like a battery calibration was not the solution.
I used to have Floyo on my hero and it worked perfect, also battery life was pretty good. Since I changed it to try another one, I can not have any 2.2 ROM in my hero cause battery drains almost 15-20%/hour with wifi off, sync off, screen minimum, 2G network, just the necessary to receive calls.
I've tried all 2.2 ROMs with different kernels, always wiping everything and none of them works property. I decided to install a 2.1 ROM and voila, more than 2 days of battery. Does anyone have any idea of the problem?
Other thing is driving me crazy is why I have to use toggle set (because of handset problem->always is on even when is not plugged) but only with VillainROM 12 I don't have this problem, I thought it was a hardware problem.
For all of this, my hero is understandable, any light to see what's going on? Thank you all
BEfore flashing a 2.2 ROM, wipe EVERYTHING, including battery stats. Let then the battery drain to 0, and charge the phone with the wall charger for 6-7 hours, then turn it on while it's still plugged and leave it like that for 1-2 hrs. Then unplug it and there will be no more drain.
Maybe this could also help you, when you set up your 2.2 rom for the first time,
have you ever disable google backup?
I have been told that drain battery like hell....
yukinok25 said:
Maybe this could also help you, when you set up your 2.2 rom for the first time,
have you ever disable google backup?
I have been told that drain battery like hell....
Click to expand...
Click to collapse
Yes I did, actually I don't have now any data plan in my mobile cause I'm living abroad so I don't use internet/data at all. Thanks
adritati said:
Yes I did, actually I don't have now any data plan in my mobile cause I'm living abroad so I don't use internet/data at all. Thanks
Click to expand...
Click to collapse
You welcome, worth of giving a try..
RaduG said:
BEfore flashing a 2.2 ROM, wipe EVERYTHING, including battery stats. Let then the battery drain to 0, and charge the phone with the wall charger for 6-7 hours, then turn it on while it's still plugged and leave it like that for 1-2 hrs. Then unplug it and there will be no more drain.
Click to expand...
Click to collapse
Thanks, I'll try next time doing it in this way and I'll see the results thought I think it won't change cause even if it's not fully charged I wipe battery stats also when i flash
Batteries die with time, so if you keep having a problem, you can consider investing $20 in a Mugen Power extended battery (1550 mAh) which doesn't need the back cover to be changed.
I greatly recommend it.
Hello all,
I bought the Atrix around 6 months ago and I have always had the same problem I'm about to describe. First I should mention that I used to have a stock rom and stock radio (77.15) until a couple of weeks ago when I flashed Cyanogenmod and radio 77.30p, yet the problem is present in both configurations.
My problem is as follows: my battery life is mediocre. Without using the phone very heavly, I get around 7-8 hours until it shuts off. Since day one I've tried many different fixes to see if the battery improved without success. Now here's the fishy part: for whatever reason, every time I make a full wipe (when I was using stock I did it from the "reset to factory defaults" option, now I do a full wipe on recovery) the battery lasts an insanely amount of time, something like 24 hours or more.
Here's how it usually works for me: I do the wipe, I boot my phone and configure my accounts, the phone syncs and installs the apps I usually use. Like I said, that day the battery will last forever, last time I've tried this I reached around 31 hours before I plugged the phone back on, and it was around 17% still. Now, the next day, without installing any new app or using the phone for nothing different, I go right back to the mediocre battery life. For example, it just went from full charge to 88% for just 10 minutes of browsing the net on wifi, not even using 3G.
Like I said, this happened with stock ROM and now with Cyanogenmod regardless of the radio I'm using. I have calibrated the battery a million times, I've tried with Watchdog which didn't show nothing, the same with Better Battery Stats. I really need some suggestions on what to try because it irritates me that the battery is dropping so much with such a light use.
Thanks!
I'm getting also quite short battery life with CM7. I'm wondering what the reason could be. It gets down with 15% for just 5 hours without any phone calls. I have just whatsapp and email checking every hour. No other resource hungry applications. With the stock ROM and the same usage I'm getting around three days ~ 72 hours.
Well in my case it's the same but with both stock and others roms. I suspect it's a software problem because I get normal battery life when I do a full wipe.
Did you try to revert back to unlocked bootloader.
What I found strange is that somehow the indicator doesn't show the ratio mAhercentage. On 85% battery the calibration battery shows charge 4030 mAh which is not 15% less than the full charge of 4200 mAh.
Well actually this problem has existed from before I unlocked the bootloader so I don't think that's the problem. And in my case the mah percentage is correct. It's like if somethings draining the battery that I can't find. Maybe is a problem with my carrier?
If the coverage is poor where you live then it is possible to get lower battery life than expected. Another solution is to revisit the application you use, try also to do a full wipe including formatting the internal memory card.
Go through this process: http://forum.xda-developers.com/showthread.php?t=1198333
You'll be good to go after that. Check also BetterBatteryStats here in xda, will show you what processes eat the battery.
Thanks but I've tried that when using the stock rom and it didn't help me. I think that solution is for a different problem as it's mainly to display the correct mah percentage, which is not exactly my problem. Also, CM7 already includes juggernaut fix.
Radiobuzz said:
Thanks but I've tried that when using the stock rom and it didn't help me. I think that solution is for a different problem as it's mainly to display the correct mah percentage, which is not exactly my problem. Also, CM7 already includes juggernaut fix.
Click to expand...
Click to collapse
Have you tried a different radio?
Yeah, like I said I had 77.15 at first and now I'm using 77.30
There's more radio's, check in General.
Ok, I flashed 77.36p and there was an improvement, I've unplugged the phone around 13 hours ago and I'm at 25%. Would you consider a good battery life for a light use? It's getting better but I saw many people crossing the 24 hour mark on their phones. Are there any other radio to try other than 77.15, .30 and .36 that would be worth it?
Do a full wipe in Fastboot & install Nottach's DarkSide and leave it with the stock kernel. I'm at 77% with 1hr 40 minutes screen time & 17,5 hrs standby..
P. S. I'm using the N_01.100.00R radio. Am in Germany, though on an at&t phone. Best radio so far.
Anywhere from 13-20 hours is fine but keep in mind it's all dependent on what's on your phone. If u have a bunch of apps pulling data from the internet or something ....I mean its all dependent on your phone setup.
Sent from my MB860 using xda premium
Vangelis13 said:
Do a full wipe in Fastboot & install Nottach's DarkSide and leave it with the stock kernel. I'm at 77% with 1hr 40 minutes screen time & 17,5 hrs standby..
P. S. I'm using the N_01.100.00R radio. Am in Germany, though on an at&t phone. Best radio so far.
Click to expand...
Click to collapse
Well, for now I'll stick with Cyanogenmod for a while because I really like it, but I have flashed the radio you've mentioned, we'll see how it behaves. Thanks!
Hello all,
I purchased a Galaxy S2 at the end of July, I live in the US, so it was from Amazon. The phone has been phenomenal, an amazing piece of technology.
I rooted the phone and flashed Lite'ning Rom 6.1 XXKH3. Still worked great, with no problems at all.
However, starting about a week ago, I am getting an extremely fast battery drain. Since then, I have spent hours looking at threads trying to figure out what was going on. I updated the rom to UltraToxic Rom v8.0 XWKK5, still no change.
I used Titanium Backup to freeze many widgets and app processes, still no change. I am currently using better battery stats to monitor wake locks, however after managing the wake locks, still no change.
I then bought a replacement battery thinking that the battery may have been bad, sadly, there was no change.
I have been trying to find a solution to this and had tried many other suggestions in other threads to no avail. As of now I have come to the conclusion that the device might have some type of malfunction that is causing this.
Am I going crazy or am I missing something obvious? Any help would be greatly appreciated.
Thanks
I have also re-calibrated the battery, still no positive changes.
Seeing the battery graph, you have your screen on a lot of time. Screen sucks battery a lot, so there might be one of the causes of battery draing.
Also you seem to have all day enabled 3G/WiFi, that also sucks some battery with it.
You can try JuiceDefender and see if it can help you extend a little your battery.
change kernel
Try flashing hardcore's "SpeedMod Kernel" and you will never complain about your battery life.....
After flashing this kernel my worse battery life was 1day and 12h with 3.5h screen on and wifi 85% ON.
http://forum.xda-developers.com/showthread.php?t=1182498&highlight=speedmod+kernel
AzureusPT said:
Seeing the battery graph, you have your screen on a lot of time. Screen sucks battery a lot, so there might be one of the causes of battery draing.
Also you seem to have all day enabled 3G/WiFi, that also sucks some battery with it.
You can try JuiceDefender and see if it can help you extend a little your battery.
Click to expand...
Click to collapse
Lol.... It's obvious he has some kind of battery problem, he is not using the phone much, and galaxy S 2 should have at least 5-6 hours screen on time and the phone lasted 3 hours.
Sent from my GT-I9000 using xda premium
Since I had all data on the phone backed up, I did a factory reset. I also flashed the UltraToxic Rom v8.0 XWKK5 as well as the suggested SpeedMod Kernel. When the battery was at 100%, I calibrated the battery. I tried to leave the phone idle as much as possible, I did use the internet for about 10 minutes to check e-mail, news, etc. So now the phone is essentially "empty" in terms of apps downloaded, I got rid of all widgets on all home screens.
There was still no positive change, I do really like the SpeedMod Kernel though, I do notice faster responsiveness from the phone.
I am beginning to think that the problem may be the hardware and not the software or battery.
I've got similar problems here. I am suspecting a hardware problem (I damn well hope it isn't coz i got mine from hong kong) because my phone never goes into deep sleep mode for more than 50% while the screen is off. I've tried at least half a dozen different kernels and roms and nothing helps, this is even in airplane mode i.e. with pretty much everything turned off. I've tested wakelocks and dont get anything more than a couple of seconds. I had my battery charged to full at 6:30am this morning, went to work and got home and it was dead after just under 12 hours with being idle 75% of the time. This is worrying as most people's battery lasts at least a whole day.
So I know it can't be the kernel, I know it cant be wakelocks, I know it cant be wifi or 3g data or anything of that nature so the only thing it comes down to now is hardware...
Funnily enough I've had exactly the same issue since about a week ago. Even when I take it off charge it's almost immediately down to around 80%. It's lasting around 4-5 hours, even when I'm not using the phone much, plus it gets really hot.
A couple of times Social Hub has appeared high up on the list of battery draining apps, although I don't use it. It doesn't always show up though. I switched to the CF-Root kernel and started using GO Launcher EX recently and wondered if that (or one of it's addon widgets) could be the cause.
It's really bugging me now!
SOLVED!
After days and days of trying to fix the issue of the phone not sleeping (and therefore draining excess battery whilst idling) I have finally fixed it!!!!!
First i noticed that along with the sleep problems, I was getting the problems with car mode popping up randomly, the phone going into mtp connection mode, and thinking its charging when it was unplugged. After looking into these issues (and i thought it was a longshot) I decided to do what people were saying and CLEAN THE MICRO USB PORT.
Now you're probably thinking I am a crazy man, but now im just crazy happy that I don't have to send my phone back to Hong Kong!
Instructions:
1. Get a clean, dry, soft-bristled toothbrush.
2. Take any case you have off the phone.
3. Gently insert the bristles into the port and "flick" it out softly.
4. Repeat this about 10-15 times
No matter what ROM, what kernel, what modem i tried flashing, my phone was always sitting on no more than 50% deep sleep mode when idle and had no wakelocks or "rogue apps".
I am now getting 90% - 98% DEEP SLEEP MODE!
I obviously can't guarantee that it will work for everyone, heck how it solved the issue is a mystery to me, one which probably an electronically-minded/computer systems person could answer. What I can say though is I searched high and low online for about a week. I tried different kernels, I tried different ROMs, I tried "re-calibrating" the battery, I used BBS to check for partial wakelocks. If you too have tried all this and have had no success please PLEASE try this and see if you have success!!
Thanks for reading!
....
Or if you didnt...
TL;DR: If you're having battery drain problems clean the micro USB port with a soft toothbrush.
The phone never sleeps when charging, the CPU idles at 200 MHz, whatever was in your USB port was probably making contact with the pins that tells the phone it is connected to a charger when it actually is not, so it was idling at 200 MHz and was not receiving power, that's the only explanation I could fathom
Do two things:
Install CPU spy and show us what the deep sleep percentages are,
and try disabling wifi. Also, what is the router?
I have a battery drain issue; but its kind of screwey as i will reboot my phone and lose about 20% of the phones charge. If i turn it off and leave it off for an hour the charge comes back. Its random as well; only happens once a week. I have had this problem on different roms. You might have a similar problem to me. Possible the hardware that detects battery state is knackered.
Sent from my GT-I9100 using Tapatalk
try to reduce screen brightness it might help, and when on wifi turn off data plan might help too
kamazaki said:
try to reduce screen brightness it might help, and when on wifi turn off data plan might help too
Click to expand...
Click to collapse
Since you didn't seem to realize, I thought I'd tell you. This thread was 5 months old before you posted in it...
lol
Hey guys.
It seems like almost everyone with battery drain issues has Android OS at the top of their battery stats.
I just want to share my experiences with this particular Bug.
Maybe it will help anyone. Please share if it also helped with your problem.
I had the Android OS bug since I dropped my phone a few months ago and had the screen replaced. The guy who replaced it (official Vodafone shop employee) said that they didn't just replace the screen and that something else was also damaged (they didn't say what) so they also replaced the rest. Well, that's when the Android OS problems started. I tried many ROMs and many Kernels. Sometimes the problem went away for an hour or so, but it always came back.
Then I finally decided to use BetterBatteryStats two days ago (I really should have done this earlier, I know...). I came to the conclusion that I had some sort of the well-known "fuel_alerted" bug, since fuel_alerted was the service that kept my phone from going into Deep Sleep.
This bug should have been fixed long ago but for me it somehow still persists, even on stock JB.
It didn't only drain a lot of battery (I had 8-10h maximum without doing much), it also used up a lot of CPU time, effectively slowing down the whole system to the point that I wasn't able to use Spotify on my phone without severe stuttering.
Well. I found a solution to the fuel_alerted bug.
The procedure is: turning airplane mode on, shutting phone off, taking out battery, putting it back in after a few minutes, turning phone back on.
This solved the problem. No more Android OS draining the power. Phone goes into Deep Sleep again. Only 2% drain after an hour. Spotify runs smoothly again. Yeah!
BUT well... It seems like the problem comes back randomly for me, today I had to replace the battery 5 times...
Now I am trying to strictly follow another "rule" to keep the problem from coming back: Always waking and unlocking the phone before plugging it in or out of power. I never did this before so it could have been the cause of the bug. Now let's see how long it stays bug-free.
If it still doesn't help, I guess I have to conclude it's some kind of hardware problem, which could only be solved by Samsung...
EDIT: Nope. Problem still there. So not really a fix, but maybe still helpful for somebody.
Okay, what ROM are you on?
Sent from the little guy
gastonw said:
Okay, what ROM are you on?
Sent from the little guy
Click to expand...
Click to collapse
It's the up-to-date stock Samsung ROM I guess. See attachment for infos.
Damn, it seems like the problem just came back without me doing much. I only checked BetterBatteryStats every 30 minutes or so and recieved 1 SMS just a minute ago. Seems like the bug started 20 minutes ago, when battery was around 78%. Now it's draining battery like hell again, Spotify stutters, Deep Sleep won't work...
Guess I'll have to pull the battery again.
Since I'm pretty new to all this: What kind of information would be useful to narrow down the source of the problem?
I can provide my BetterBatteryStats screenshots and logcat/dmesg files as well as my Android Battery Stats screenshots.
Is there anything else I could post?
Yeah, screen shots of partial and kernel wakelocks.
Sent from the little guy
I just rebooted the phone, waited for a few minutes and took screenshots.
Here they are.
Okay, this is what you need to do now, drain it empty, charge it (while phone off) till 100 %. Remove the battery, wait for 90 sec or so, put it back and power on.
It's a placebo, but it might work.
Sent from the little guy
Okay, I will try and do the charging overnight. Thanks!
derSchmiddi said:
Okay, I will try and do the charging overnight. Thanks!
Click to expand...
Click to collapse
Good luck man.
Sent from the little guy
I don't know much about kernel and ROM stuff, but I was just wondering...
As far as I understand, the fuel_alerted thing turns on if the battery charge goes below a certain threshold. The old bug with it was that, when recharging, the fuel_alerted thing would sometimes still stay on, even if battery charge is no longer critical.
Could it somehow be possible that this threshold is not set to 15% for me, but something around 80% due to some horrible bug?
This would explain why it suddenly turned on at around 80% when everything was fine before.
We're trying to adjust your fuel gauge and sort of calibrating your battery.
Sent from the little guy
Okay, I did exactly what you recommended.
Everything went well for about 2.5 hours.
Then the fuel_alerted process began again, but this time only for a short while apparently.
It took about 5 minutes kernel wakelock time in a 30 minutes measurement.
Way less than usual and when I check now, it's no longer active.
So. The problem might still be there, or it might not.
Do you recommend going through a few more recharge cycles to get the gauge set properly or do you think this won't make it better?
By the way, thanks for your quick responses!
derSchmiddi said:
Okay, I did exactly what you recommended.
Everything went well for about 2.5 hours.
Then the fuel_alerted process began again, but this time only for a short while apparently.
It took about 5 minutes kernel wakelock time in a 30 minutes measurement.
Way less than usual and when I check now, it's no longer active.
So. The problem might still be there, or it might not.
Do you recommend going through a few more recharge cycles to get the gauge set properly or do you think this won't make it better?
By the way, thanks for your quick responses!
Click to expand...
Click to collapse
Not really.
Now, when it gets to 15% or so plug it in (while phone ON), get battery calibration from play store.
Run the app, when it gets to 100 % hit calibrate. Plug off the device. Turn off.
Take out the battery for 90 sec again, reinsert it and power it on.
That calibration app is another placebo but as I said before, placebos sometimes work.
Sent from the little guy
Since the battery calibration app requires Root access, I flashed a Dorimanx kernel a few hours ago. Then I did a factory reset and the battery-removal thing. 5 hours have passed now without the bug, 3h of which were without wireless access (maybe it correlates with that).
I'll now let the battery (slowly) drain below 15% and then recharge it with phone on overnight. I will use the battery calibration tomorrow and will inform you about the results later.
Thanks man!
Good to know
Sent from the little guy
I did the battery calibration. Bug is still there, no changes
Post you battery details and a couple of BBS screens.
Sent from the little guy
Okay, here are some screenshots.
From the graph you can clearly see when the bug started.
Is it normal to have >26 kworker processes running?
Something else that concerns me: >2h without or with unknown signal. The whole day I was in an inner city area where the signal should be good...
Can you conclude anything from the screenshots?
I will now try something which I also should have tried earlier
I have a spare battery (not original samsung, less capacity) which I just put into the phone.
I'll let it fully charge with phone off and then I will try if the problem persists even with the other battery.
If it doesn't, the problem might come from the battery itself...
Is this a good idea?
No it's not.
You gotta post detailed info there, we can only guess what's draining your battery.
Sent from the little guy
Okay... I posted the screenshots you asked for...
What more should I post?
Hey all, I'm a frequent noob to this site always asking for help because I always seem to mess up my phone in some way... So my phone was fine, then I started to notice the battery was always displaying the wrong charge. I would put the phone to charge and it would charge too 100% and when I disconnect it then it would display 60% or 90% that was just the beginning of my troubles. Now the phone sometimes has 30%+ more or less and the screen starts to flicker and lose lighting, then the phone gets really slow and ends up freezing. I go to turn my phone on and it doesn't even turn on... I leave it charging about an hour to see if that helps and when I turn it back on it says it is at 10% or so and then the same thing happens minuets later. Also at times it wouldn't even let me charge the phone it would say battery disconnected, this is the main reason why I did a fresh and clean install of a new ROM. I know it isn't my cable because I tried 4 different cables I have a few of my friends. I am running 4.1.2 with Siyah 6.0 I recent did a clean wipe of the phone to try to fix the issue and I had some issues with the new ROM. It kept saying com.android.phone has stopped blah blah blah so I downloaded a new ROM and it went fine I guess, then I uses Titanium Backup to restore all my apps and system data, then the com.android.phone message started popping up again... So I do a fresh clean install ONCE AGAIN and it works fine, I install just the apps+data no system data this time and it is still working fine. Also I moved all my apps to my SD card, when I reboot my phone it starts really slow and says loading instead of the name of the apps, also it takes about 5 minuets for the phone to work normally, at the start it is really slow and barely does anything, is that normal? I am using Lookout Security as my anti-virus. Also I use GO Launcher, is that fine or could that be an issue? ALSO I use ZDbox for an applock a cache cleaner and to kill tasks when I want to save battery life. I'm a real idiot when it comes to these things any help at all would be great, thanks.
P.S. As I am typing this my phone froze at 30% and when I reset it the number showed 14% and it has been charging ever since and is at 17% so the charging seems to be working fine for now, but not always and it loses battery life FAST, thanks for anyone who can help and give tips / answers.
Here are my phone details:
Model number
GT-I9100
Android version
4.1.2
Baseband version
I9100UHMS1
Kernel version
3.0.31 -Siyah-s2-v6.0b5+
[email protected] #177
SMP PREEMPT Mon Feb 18 16:38:28
PST 2013
Build number
JZO54K.I9100UHMS8
No need for your life story. Might be a battery issue, might be the USB port/board. Try one, then t'other.
I had exactly the same problem. Literally, exactly the same.
I bought a new battery. Problem solved.
Sent from my Nexus 7 using Tapatalk 4
For the battery issue, you can try to charge your phone completely when it reaches 15-20% (just think to shut it down before) to 100% (and let it charge 1 or 2 hours after 100%). Try this several times to recalibrate your battery. If it doesn't work I think you could buy a new battery.
How long have you got this battery? Just to let you know, a battery can be "dying" after roughly 500 charging.
Brahktor said:
For the battery issue, you can try to charge your phone completely when it reaches 15-20% (just think to shut it down before) to 100% (and let it charge 1 or 2 hours after 100%). Try this several times to recalibrate your battery. If it doesn't work I think you could buy a new battery.
How long have you got this battery? Just to let you know, a battery can be "dying" after roughly 500 charging.
Click to expand...
Click to collapse
I'm pretty sure it is the battery then because it is 2 years old LOL I have the same battery from when I bought it back in 2011, also I have 2 anker batteries which are a little over a year old so I'll buy a new one when I get a chance, probably a huge extended battery, I've always wanted one of those that last 3 days LOL thanks for the help guys.