So I've run into an bizarre problem today, one that I've never seen before.
My mum's S2 was having problems charging last night with the screen not showing the charge animation. So we decided to charge my S2's battery in my phone, then put it into her phone. It worked, but the battery was draining really quickly. I turned off the phone, decided to charge her battery in MY phone. Then I put her original battery back into her phone. But even though I haven't turned the phone on, it starts heating up within minutes! So anyway, I've tried plugging her phone into the charger again, but it seems like something is taking up the battery to quickly to charge it - even while the phone is completely off! I've even checked the processes running when the phone was on, but there seems to be nothing there causing the drain.
So anyway the next thing I'm going to try is a factory reset (this is currently running on the stock ROM), and then attempting the flash another ROM to see if that will work.
Also another thing to note - while i was backing up her phone, I had it plugged in to my computer and after leaving it for a bit to do some other stuff, I hear this high pitched beep coming from the phone saying something like "Battery temperature too high. Charging stopped." Really really strange.
Anyway, if anyone has run into this problem before or has any other ideas, it would be much appreciated. Thanks.
Related
Hey guys,
I'm having an interesting issue here, basically I've noticed my vibrant isn't charging the phone battery,
instead it says "discharging" when plugging it in. When i go to the 'about phone - status area'.
When I unplug the charger it says "not charging" and when I plug it in it says Discharging.
Has anyone seen this behavior on their phones? I'm not sure if there is something wrong with my phone
or if Samsung tries to regulate the battery reconditioning it?.
I would like to avoid having to return my phone if this is some sort of strange issue with the vibrant.
I have had the vibrant for over a week now, have not done any changes to it other then simply rooting it,
no flashing done otherwise. I just happened to notice this tonight before going to bed.
Also note that I do not have wifi turned on, and I wasn't running anything at the time either that should be
draining it more then a charger should put out. I have also tried charging it using the charger that came with
the vibrant and a second charger I bought.
I have only seen one post related to this on Google.
http://forum.androidcentral.com/t-mobile-vibrant/33383-battery-discharging-error.html
Update: I can tell you that my % has gone down, from 30% to now 20%, still discharging..
Also Screen Brightness is set to lowest, WiFi Off, and not running any applications in the background,
on original vibrant rom.
Video Or it Didn't Happen, Posted.
Here I took a video of it too if for some reason you can't see what i'm saying, or think i'm crazy.
Weird Camera is angle is cause the phone number just happens to be right under the battery status.
http://www.youtube.com/watch?v=Nk_JHdlMVbg
what charger are you using? and do you have another that you can test? Also if you're charging VIA usb port on your laptop have you installed the samsung drivers, if not install the samsung USB drivers, if you have then try a different USB port.
its doubtful its the phone, far more likely the USB port, charger or cable
I have charged it with 3 different chargers, and cables from different computers and usb ports, as well as in wall charger,
the samsung usb drivers are installed and i'm able to access adb.
My computer also has 3 powered usb hubs.
The battery kept draining, till the phone shut off and restarted on its own
after receiving a charge from the charger, so i'm wondering if maybe some
other people might be able to notice this behavior at all.
When it restarted on its own it said it had 60% battery from 0% right before charging,
so I am wondering if perhaps some people's phones are doing this in the middle of the night.
After restarting the phone charges normally starting at a really high %.
Could this be caused by software problems on the phone.
that is crazy... you certainly have ruled out a charger problem.
Was this just a one time thing and after the restart it's charging normally?
if it's still acting up you could try flashing the original rom via odin or to be safe take it back and exchange it.
People might not be realizing theres a discharging problem
Yeah has only happened once that I've caught so far, so thats why i'm trying to raise a little bit of awareness,
seeing that other post on androidcentral it seems like some people got to be having this problem.
Maybe they just don't realize it. Its not something you'd notice plugging the phone in before bed.
For now it seems fine after a restart, its possible that its a problem that occurs after the phone has been on for so many hours,
and perhaps a memory leak occurs of some sort. It could even be Samsung's poor attempt trying to recondition the battery somehow.
I have had some odd occurrences where I have grabbed my phone off the charger first thing in the morning and found it around 30%. Rebooted it and it charged normally. I think this has happened twice now. I didnt notice anything while I had it plugged in so I can't say if it said discharging or not.
Maybe what you could do is go to the phone settings, scroll to the about section and check out the battery status next time that happens.
On the larger scale of things, this could be a fairly common issue that noone
is taking a look at.
It could be related to why some people are having very poor battery life
and why the battery meter can be really inaccurate.
If your phone discharges itself completely, reboots thinking its at 60% battery life,
I can see that causing many problems that you just wouldn't see since people
just plug their phone in and go to bed.
Bump cause I'm having the same issues. Was a solution ever found for this?
I had this problem before but it happened to me with an after market battery, once I changed batterys the problem went away. so basically your battery is bad..
Yes! I have this problem all the time. A restart will fix it but often I will plug it into a wall charger or car charger and my Battery Indicator Pro will say "failure". Battery life is also horrible.
Sent from my SGH-T959 using XDA App
This is caused by running 2.2.1 roms I think. Only got it once and was on such a rom. A restart will fix it. Its possible you didn't flash good as I have never gotten it since. Its a rom issue though.
Sent from my GT-I9000 using XDA App
}{Alienz}{ said:
This is caused by running 2.2.1 roms I think. Only got it once and was on such a rom. A restart will fix it. Its possible you didn't flash good as I have never gotten it since. Its a rom issue though.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Op was running stock rom.
You need to delete your battery stats, but to do this you need to be rooted.Looks like your phone is not charging at all .... plug the charger in and take out the battery and see if it starts charging.... hope this helps ....
this is happening to me, right now. i've had it happen once before, i shut down, pulled the battery, replaced it and booted. it charged fine afterwards. but i don't want that as an answer.
mine is at 84 hours uptime, i don't remember what it was last time i had this issue. whats weird is i was just charging at work not 30 minutes before i got home and plugged it in to charge. worked fine half an hour ago. but not now.
i've got a stock vibrant on 2.2. wonder what's causing this.
This happened to me and i could only get it to charge by rebooting it. I eventually had to replace my phone because it also was doing soft reboots too but discharging also.
I think I found a solution. Is anyone still having this issue tho? If so ill post it.
elsolo00 said:
I think I found a solution. Is anyone still having this issue tho? If so ill post it.
Click to expand...
Click to collapse
I have this problem and have been for a while. Will you post the solution please?
Thanks in advance.
here too... but with a htc wildfire (aka buzz)
it discharges while in charge
very strange!
I tried almost everything, also replaced battery with another one original of course... nothing changes, also replaced AC charger... nothing!! my mobile become a fix line
unluckily I don't have a rooted phone so it's not possible for me to recalibrate trough SW
ive had a battery issue similar to this. my battery never discharged while plugged in, but after flashing a 2.2.1 rom(bi-winning) and then installing "battery left" and reconditioning my battery, the "battery left" app had a roughly 18% difference in battery charged then the system...as the syatem read the battery as being lower then the app showed i had. it would shut off with "low battery" when the app said i had about18% left. after flashing again and reconditioning my battery again the problem went away...could be some software setting somewhere!
So, I recently received my dad's old Galaxy S2. Stock JB, unrooted. My dad used to charge the phone in his car and during office time, whereas I've always been an "overnight" charger (keep this in mind as it's important). So, here's what happened -
1. I woke up really late the next day and realised that the alarm clock hadn't rung. checked out the phone beside me to see that it was really hot. The phone had shut down by itself. I turned it on and it functioned normally. That day I rooted the phone using PhilZ (mainly for the adfree app)
2. I didn't do an overnight charge for the next night cause my dad told me that "it ruins the battery". And the phone was fine the next morning. I changed to dorimanx's kernel for all the wonderful extra features.
3. That night, I decided to try overnight charging once again. Woke up the next day to a shock. It was 10am! No alarm, hot phone. I thought the phone had just shut down again, so i tried to switch it on. It showed the samsung boot screen and then the pretty "dorimanx" screen, but then.. stuck. the device wasn't starting, but recovery was working. I removed the battery, I wiped the cache, I installed another kernel (siyah)... nothing worked. FInally, I decided to try flashing a new rom. Downloaded SlimKat and flashed it through CWM. The device then booted up and has been working quite normally now. And I like SlimKat much more than stock! But that's not the point. The point is, I'm scared of charging overnight again.
None of my previous phones have faced this problem. I'm just a noob, but I have a theory. I noticed that the phone, once it reaches 100%, doesn't give any indication that it has stopped charging (like most phones do). The charging icon on the battery still shows. Does this mean that the phone is still trying to charge even after the full battery, which is causing the overheating and shutdown of the phone? I'm still confused regarding why it refused to boot up.
Is this a battery/device problem, or was this merely due to some fault in the stock rom?
You were actually stock in a boot loop (which has happened to me before(hated it). Be glad that it didntt freeze at the Samsung logo. Because then you couldn't get into the CWM.
I am not entirely sure what is wrong with your phones battery, because I have never had this problem myself, so I am sorry I can help you with that. Try going to settings/battery and see if you can turn sound on for the battery from there. :thumbup:
Sent from my SGH-T959V
Given the age of the battery it's likely to be the battery, so replace that first. Could also be the USB board, but cross that bridge when you come to it (try the easier option first).
Your old man is wrong about charging - constant charging/discharging like he did for however long is far more likely to reduce a battery's useful life than a simple use the phone during the day charge once overnight arrangement.
Hi XDA, wondering if anyone can help me out with an annoying problem.
I have a Galaxy Note Edge. Within about 8 months I've been experiencing random shut-downs.
Thinking it was battery related, I started there. The problem persisted. Thinking it was perhaps a wake-lock issue, I did a factory reset including cache clear, still have the problem.
Basically when I'm using the device it will randomly shut down. I could be checking my email or taking a pic, out of nowhere poof, off it goes. Battery will still say an arbitrary amount, today it was at 64%. But when I plugged it in, with the device off it said 0%.
I notice this happens often. If I charge my phone overnight it will stop charging at maybe 70%. Poor/wrong calibration?
Here's the thing though, even if the phone says 0% after shutting down, if I try to turn it on it will go into a boot loop for..well infinitely. Hours. So there's clearly still power. If I try to use my battery bank to charge it, it still won't get past the boot loop until I connect it to at least a 2.1amp charger.
I'm at a loss. There doesn't seem to be any obvious hardware issues. I've been scraping the interwebs for a good year but nothing has helped and I just live with it.
Running Android 5.1.1, stock, no dumb unoptimized apps. Someone please save my sanity? Cheers! E>
Hello guys, so, a friend of mine gave me his old RAZR xt910 after some begging, he was going to throw it away. This phone came to me with a dead battery and a shattered screen. First, the phone wasn't turning on, but would turn on and stuck on bootlogo only - with the charger (ac). I managed to hard reset it and load Android throu BP TOOLS (vol up down + charger), after taking the battery away, Running on charger only, - this was a new "gold" 3030mah aftermarket battery that was put in there by my friend one year ago. I was pretty impressed since it turned on without battery, like, wtf!. I tried to install CyanogenMod but could get to safestrap since it was asking for a battery ((?) image when on charger). Recently he brought me the old original battery - the one he tried to swap for the new one. It was all good, I put it back in and booted with 99%, but it depleted quickly. The phone refuses to charge it, wherever it is on or off, ((? Image when it's off, again)… it says OVERHEATING when it's on and then enters a cool down phase in which I can only do emergency calls, nothing else. On cpu-z it shows battery as Overheat at 80c (doesn't show variation). It also shows Overheat when without battery so I'm guessing this is preventing charge, but the energy flows well through the phone. Cyanogens turn the phone immediately off after optimizing apps on first boot (I guess it's because the wrong temperature data). I'm afraid... should i spend 15 dollars to try the luck on a new battery?, is the temperature sensor installed on the battery or the phone? Anyone booting from CHARGER ONLY, NO BATTERY INSTALLED getting "Overheat" status on cpu-z temperature readings? I would like to fix this phone to keep it... I like collecting phones.
After the battery depleted I managed to recharge it alone on a.universal charger, manually. I can't say its a comfortable way to charge it, but still the only way. Unfortunately I threw the "new battery" away so I can't say if it would say "Overheat " too to determine if it's a phones problem. Big fault
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
--yep mine too. I'm thinking it has to do with the heaying problem. Mine crashes and dies when there are many apps running/ wifi on with downloads while watching youtube., etc. another is when I recprd videos at 4k pr 720p for about 8-10 mins. My phone heats up real hard. I'll try resetting it and hopefully this fixes it. ps. Haven't done anything to my z5c yet. no unlocked bootloader, no root.,etc.
Same problem
I had the same problem
Device have charge (50,60,70 or more), show 0% and turn off.
Hardware problem maybe ???
any solution found?
hi,
I know it's been a long time you posted this but I'm currently facing that exact same problem.
Could you find any solution in the end?
Thanks
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
It looks like your battery is just dying. This was a common issue with Nexus 6p and other phones.
Resetting batterystats won't help... it doesen't have anything to do with it