Related
Hi all. I really don't know what causes my problem, so I'll just describe it:
Epilogue:
My Legend came with some Vodafone ROM so as soon as I got it I flashed 2-3 ROMs found on XDA (all in the same day, all were 2.2) before I settled for BlaY0's. Everything was working properly. After 3-4 months I decided to try a new ROM so I flashed a 2.3.3 with HTC Sense (http://forum.xda-developers.com/showthread.php?t=987251) - didn't like it much; then I tried a Cyanogen, also 2.3 - didn't like it either. So I flashed back the BlaY0 2.2. (also, in one day)
This is when my problem started.
Usually my battery would last for a day and a half. But every evening I connect it to the charger (at about 50%). In the morning the little light turned from orange to green and the battery indicator showed 100%. This was before! Now, I connect the charger in the evening but in the morning the light is still orange and the battery indicator shows something between 70% and 85% (I don't know if this is important, but most of the times is 85%). Usually it took 2-3 to fully charge the battery.
After a while, I noticed that if I reboot the phone in the morning, after the reboot the indicator shows 95-98%.
First thing I did was to wipe the battery stats (http://forum.xda-developers.com/showthread.php?t=765656) but either I did it wrong or that was not the problem because it did'n solve anything.
Then I noticed something else. When I go to SETTINGS>ABOUT PHONE>BATTERY I can see the UP TIME and the AWAKE TIME. I'm guessing that the up time is the total time since last reboot but the awake time I'm not sure; is it the time the display was on or it is more about CPU activity? Anyways, it seems that after I connect the charger, it thinks that it is awake because in the morning I can read about 8-9 h of awake time (during the day it reaches at about 1-2 h). So it appears that something consumes the power at a higher rate messing with the charging process. If so, why does the battery indicator heals after reboot?
Thinking that an app was causing the problem I eliminated some of them: Advanced Task Killer, Llama, Watchdog. The problem persisted...
Now I'm out of ideas...so if someone has some I'd be grateful. It's not that I need to reboot in the morning, it's the not knowing that's killing me!
Absolutly same issue here.
I remember seeing a solution somewhere in the forum. Try using search. I think there're many threads revolving around this issue.
Sent from my Legend using XDA App
elk2210 said:
Absolutly same issue here.
Click to expand...
Click to collapse
I know that it's selfish but I'm glad I'm not alone
@Asovse1: I did a search before posting but I'll keep digging if you say there is a solution somewhere. Tks!
marginean.m said:
I know that it's selfish but I'm glad I'm not alone
@Asovse1: I did a search before posting but I'll keep digging if you say there is a solution somewhere. Tks!
Click to expand...
Click to collapse
There was a huge thread on this in General.
http://forum.xda-developers.com/showthread.php?t=1151450&highlight=charge
Unfortunate, until an alternate solution is found, it seems that replacing a piece of the hardware is the only way. Which sucks. I'm sorry.
When flashing a new ROM or switching between primary and secondary batteries in my wallet, I always make sure I calibrate it so the system doesn't misinterpret predefined untrue values regarding the highs and lows of the battery.
Actually, with my second battery, it takes an hour to charge from 2-60, then another one for 61-76, then the whole night til 100. It's quite horrible. The stock HTC battery excels at charging, but I digress.
It seems like a counter-solution to me, but maybe a temporary fix for you: Have you tried investing in a really cheap, secondary battery, perhaps on eBay? I bought two for around 2 dollars each, on separate occasions. My first I'm still using now, in my wallet, switches each month. My other one I bought recently, and the first time it dipped to 30%, it completely shut off. Needless to say, I threw it away, it was horrible.
@Asovse1
I read the thread...to be honest I never thought it would be a hardware issue. Anyways, replacing the motherboard isn't really a fix.
I guess your solution (having spare batteries) is the only one feasible. This kinda sucks!
Solution (see last sentence)
I have two HTC Legend phones here that both have this same problem.
I have read elsewhere that some people got the HTC Legend fully charged by charging it normally, like overnight, then powering it down and charging once more until the light turns green. Some repeated this procedure twice, i.e. pulled the charging cable, then plugged it in again.
I just tried charging with the phone powered down and got it to 100%.
But I'm still not sure whether this is just snake oil, because the indicated figure may not actually show the true charge.
Addendum: As I now know, it is snake oil. As far as I can tell, the phone charges normally. Only the indicator underreads. It does not reach 100%, it goes down rapidly, the phone keeps operating for hours with the indicator showing 3% or less.
And here is the solution.
I have a serious problem.
My battery is draining more charge when it is powered off than when it is on!
First off, yes, I am powering it off and not just putting it in sleep.
What happens is this; I power it off for the night, battery at 100, turn it on in morning, battery is at 70-50! Now get this, I reboot this morning, battery instantly drops another 10%!!!!
What on earth is going on here? Does anyone else's have similar problems? I did Google it, but can't find a solution, although it looks like I am not the only one with the problem!
Please help!
Edit: here is a screenshot of my battery use, if anyone wants (sorry, don't know how to post picture other than as attachment)
I had this situation once before. After I updated my firmware to 2.3.5 from 2.2, it never happened again. Hope this help.
Tim_Lau said:
I had this situation once before. After I updated my firmware to 2.3.5 from 2.2, it never happened again. Hope this help.
Click to expand...
Click to collapse
Mine is US version, comes with 2.3.5.
Use the original version 2.2 Froyo that came with it. I did not want to update because everything works fine. no bugs of any kind. I think I did the right thing, because I have read several bugs related to the update to 2.3.5.
Do not always update is really necessary. Unless something does not work well or update the device will really improve. But this is not always true.
In my case the battery has excellent durability. An exception to games but that's with any Android. Even with a 2500 MAH as the G70. Luckily, I'm not adept at games.
ADR USR said:
Use the original version 2.2 Froyo that came with it. I did not want to update because everything works fine. no bugs of any kind. I think I did the right thing, because I have read several bugs related to the update to 2.3.5.
Do not always update is really necessary. Unless something does not work well or update the device will really improve. But this is not always true.
In my case the battery has excellent durability. An exception to games but that's with any Android. Even with a 2500 MAH as the G70. Luckily, I'm not adept at games.
Click to expand...
Click to collapse
Please read my post above you;
U.S. version=2.3.5, not downgradable!
Hey man I had the same problem with mine several times now, last night I decided to disable my wifi and this morning I still have full battery, not sure if the two are connected but I thought I would post this anyway!
Sent from my DROID BIONIC using Tapatalk
Jeremiah_1988 said:
Hey man I had the same problem with mine several times now, last night I decided to disable my wifi and this morning I still have full battery, not sure if the two are connected but I thought I would post this anyway!
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I've notcied that my battery would drain faster when connected to wifi at home.
I have 5.0, 2.3.5 US version. I had a problem getting mine to charge to 100% (seemed to stop at 80%), but finally it hit 100%. Got to 80% in 3-4 hours, got to 100 in 6 hours extra!
Mine seems to drain "normally", at 65% after 23 hours. Not been doing a lot with it, just messing with apps (installing, rearranging). I always turn off wifi when not using it (especially if there's none around).
You might install "Power Tudor" and see what exactly is using that much power to drain yours that fast. Could be something stuck syncing (like if you have mail set to sync every 10 minutes).
Well, the thing is, it shouldn't be syncing or doing anything while powered off! Oh well, I have just gone to putting in airplane mode, then letting it sleep at night, doesn't burn any battery that way anyway!
Just curious, isn't "airplane mode" the same as just turning off wifi, since it has no cell radios?
I also question the time scale on the battery chart, never seems right to me. If your graph is 10 hours, and it was off at night, I would think it should register than 6-8 hours (or whatever your "night" was. Looks like it was only about an hour.
iJimaniac said:
Well, the thing is, it shouldn't be syncing or doing anything while powered off! Oh well, I have just gone to putting in airplane mode, then letting it sleep at night, doesn't burn any battery that way anyway!
Click to expand...
Click to collapse
airplane mode turns off all antennas (wifi,GPS,FM radio). Yeah the battery chart doesn't make Denver to me either, but whatever.
Just keep it plugged in at night, I guess.
iJimaniac said:
airplane mode turns off all antennas (wifi,GPS,FM radio). Yeah the battery chart doesn't make Denver to me either, but whatever.
Just keep it plugged in at night, I guess.
Click to expand...
Click to collapse
Either that's a joke I don't get or a really funny autocorrect
yup, that would be auto correct!
either was the word I'm looking for.
I have searched on here for the last 20 minutes so I hope I didn't just miss something.
Anyways, onto the problem I am having... I'm currently running UnNamed 1.3.1 and last night before I went to sleep the phone got really warm. I went to place it on the night stand and missed resulting in the phone taking a minor fall ~2ft. Everything was in working order so I placed in back on the stand and went to sleep.
At some point during the night the phone died on me causing me to miss work today. Now I'm trying to charge it but all it is doing is showing the depleted battery icon for about 2 seconds and then going to a black screen and repeating. Have any of you guys heard of this issue? Is it just a defunct battery?
Thanks for the help in advance.
jcarson112 said:
I have searched on here for the last 20 minutes so I hope I didn't just miss something.
Anyways, onto the problem I am having... I'm currently running UnNamed 1.3.1 and last night before I went to sleep the phone got really warm. I went to place it on the night stand and missed resulting in the phone taking a minor fall ~2ft. Everything was in working order so I placed in back on the stand and went to sleep.
At some point during the night the phone died on me causing me to miss work today. Now I'm trying to charge it but all it is doing is showing the depleted battery icon for about 2 seconds and then going to a black screen and repeating. Have any of you guys heard of this issue? Is it just a defunct battery?
Thanks for the help in advance.
Click to expand...
Click to collapse
This sometimes happens with a severely depleted battery - after a bunch of cycles like that it SHOULD eventually stay on I think.
Otherwise you may need to give the battery just a little "juice" with a standalone charger.
Thanks I'll keep trying, was having a minor crisis when I woke up 2 hours late to work today.
I had this same issue when my battery died severely. Woke up with the phone cycling, like you mentioned and it was extremely warm.
The problem you are having is that UnNamed is running a kernal that automatically boots up the phone if it is off when you plug it in. This, combined with the fact that android turns your phone off automatically when the battery is too low, is putting you into a battery bootloop.
I just went into the AT&T store, and they swapped out my battery for free. Just don't let your phone get too low before charging it.
Hope this helps.
It's finally started taking charge thank goodness.
Anyone gave an idea as to why my battery tanked so hard. I exited out of all apps and had it plugged in through the night.
jcarson112 said:
It's finally started taking charge thank goodness.
Anyone gave an idea as to why my battery tanked so hard. I exited out of all apps and had it plugged in through the night.
Click to expand...
Click to collapse
Rage from being dropped.
Hard to say. Unless you catch it as it's draining like crazy, a logcat or bbs will only comment on how it's currently running.
Sent from my páhhōniē
Lol i just put it into download mode and charged it haha. I made it stop rebooting......
Sent from my SAMSUNG-SGH-I777 using xda premium
Can't charge battery
o i think i am having the same issue. i dont have any other charging method. it is so dead i can't even get it to get into download mode.... any ideas. PLEASE HELP
Did you put a different kernel on it? I know certain kernels cause the phone to lock into 1200MHz while charging. At that rate the phone would die even plugged in, like you saw on that battery graph. Zedomax kernel did that to my phone. None of entropy512's did that to me, but if you used a different kernel than what gtg packed it with that might be it.
Look for BetterBatteryStats, it will tell you what apps are preventing your phone from going into deep sleep. If its an app causing that issue BBS will tell you which one. It costs money in the android market, but there is free version for xda members in the android app forum.
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?
I recently ordered two new OEM batteries for my Atrix 4G, equivalent to the battery I was replacing – at least they appear that way. When I installed the new battery, my battery indicator was showing that the phone was at 15% after only a few hours. I charged a couple of times with the same problem occurring, I tried the second battery. When the same thing happened, I decided just to let it die all the way and charge fully after. My battery level hit 1% and stayed that way for hours and hours of use. When I timed the battery life, it was actually very good and it appeared the battery meter was just reading wrong.
I tried several full discharge and recharge cycles and tried disconnecting the battery while the phone was plugged in until the ‘?’ battery appeared and reinstalled it. The same problem occurred again and again. Next, I rooted the phone and tried the battery recalibration app. Results were the same. I have followed this up with discharging and recharging the battery fully several times but the problem still remains.
I have now installed an app that reads the voltage on the battery. It reads ~4200mV when plugged in and fully charged. It will discharge to somewhere between 3200mV and 3300mV before the phone shuts off and it takes upwards of 30 hours for this to happen. This has proved to be a somewhat effective way to actually estimate my remaining battery but it is still driving me nuts that the meter is off. Is there anything I can do?
Thanks for your help!
try this http://forum.xda-developers.com/showthread.php?t=1832470
barry_ said:
try this http://forum.xda-developers.com/showthread.php?t=1832470
Click to expand...
Click to collapse
Thanks for the reply. I installed the app a couple of days ago. I have tried the first option "Run the Fix" a couple of times, once with the battery stating it was at 100% while plugged in and once in the middle of the day while not plugged in. It has not seemed to do anything from what I can tell.
I have not run the second option to Fix battd yet because I had to figure out how to install Busybox, which I have now done. I will try that option tonight and report back.
Thanks.
You should also read about the purpose of the app and how to use it. It is all in the OP of that thread. There is no point in running the fix just whenever you feel like it, it is meant to be run only right after the battery is done charging. Running it any other time will most likely just mess up the stats/percentage even more (not irreversibly though).
ravilov said:
You should also read about the purpose of the app and how to use it. It is all in the OP of that thread. There is no point in running the fix just whenever you feel like it, it is meant to be run only right after the battery is done charging. Running it any other time will most likely just mess up the stats/percentage even more (not irreversibly though).
Click to expand...
Click to collapse
I did "run the fix" when my battery was fully charged overnight and rebooted the phone. I used the phone for a couple of days and it did not improve the situation. Last night I charged to 100% again and did the "fix battd" option. Today, there has been no improvement in the meter. I will try charging to 100% again tonight and try the force calibration option with the "run the fix". Is there any other way I should try to run it?
It will always charge right up to 100% and 4200 mV, the problem is the percentage will drop rapidly once unplugged all the way down to 1%. Once it hits 1% it will stay there and I can keep using the phone through the rest of the day and even overnight and into the next day before it actually powers itself down.
Yeah, I've heard of a few other people having the same issue. Sadly the battery fix app isn't going to help in your case - I don't really know what will, I'm not sure if there is a fix. Try searching the forum, this has definitely been mentioned more than once.
Hi. I just started using the Atrix today. I flashed the official ICS leak. But strangely, my battery meter isn't going above 50%. Can i use the app (from the link given above) to solve the issue>?
thanks.
Dunno. Why don't you try and see for yourself?
BTW I don't think running the leaked ROM as a daily driver is a good idea at all, especially if you only just started using this phone...
ravilov said:
Dunno. Why don't you try and see for yourself?
BTW I don't think running the leaked ROM as a daily driver is a good idea at all, especially if you only just started using this phone...
Click to expand...
Click to collapse
Oh ok. I will try it for a couple of days and see. So far, it is amazing. Fast, responsive, very very little lag. Just this battery thing is a little weird. BTW, it did go ahead of 50%...i hope it doesnt fall really fast.
And I have a NeXus 4 as my main phone. My office gives me one phone, hence the Atrix.
ravilov said:
Yeah, I've heard of a few other people having the same issue. Sadly the battery fix app isn't going to help in your case - I don't really know what will, I'm not sure if there is a fix. Try searching the forum, this has definitely been mentioned more than once.
Click to expand...
Click to collapse
I have done some research and have found that this has been a common issue for users of the Droid X. There are two revisions of the BH6X battery, SNN5880A and SNN5893A. Many users of the Droid X purchasing the 5893 revision of the battery report having the exact same problem I am having. They have solved it by using the older 5880 revision. They suspected that the 5893 was made for the Atrix and the 5880 for the Droid.
The problem is, I have the newer 5893 revision on both new batteries which, according to that info, should work for my phone. I do not have my original battery that I was replacing with me at the moment but I can check that model number tomorrow night. I only found one other thread where a person had this issue with the Atrix here. There is no real answer on how to solve or work around the problem though and I am not having any luck finding others with this issue.
Is there any way to adjust the battery meter settings or simply hide the stock meter? I apologize if this is a dumb question.
Problem solved:
I tried the batteries in my girlfriend's Atrix and experienced the same problems. Convinced it was an issue with the battery itself, I contacted Motorola through live chat and explained the situation. After talking about (some of) the various troubleshooting steps I had taken, they told me they would send me a new battery. The battery came and has been working perfectly for the last week with the percentage showing accurately.
The two bad batteries I had were manufactured 04/08/11 and 04/12/11. The new one they sent was manufactured sometime in April 2012. Perhaps a bad batch of batteries was produced by Motorola. That would explain why Droid X owners believed that the battery was incompatible with their phones. The talk that the battery was incompatible started shortly after those batteries were produced (it looks like around August 2011), and mixed in there are reports of the SNN5893A working in the Droid X for some. Hopefully this info is helpful to others.
Thanks again to everyone who took the time to offer help.