Related
My device shut itself off last night while charging. I had to do a battery pull to get it to turn back on. Anyone else experience this? My first droid, is this normal? I'm withing the 14 day grace period on my THIRD device.
No it's not normal. It is however a bug that some are experiencing and is usually fixed by doing a factory data reset and making sure you font skip over the Google setup when your device turns on for the first time after doing your reset. There is about 50 threads regarding this issue in this forum so your best bet would be searching for them and see what ers are doing to eleviate the situation. Worst comes to worst just exchange it for another.
Sent from my LG-P999 using XDA App
I think this problem was associated to the first few build batches of the device. After replacing for a new batch I have not seen this problem.
Update: Was told it's an issue with the battery. T-Mobile is overnighting a replacement battery free of charge. Was told if it does it again to replace through warranty as I am tired of taking up my time going to the store to replace.
I dunno. I think it is more drivers. Some people reported the phone turning off while stock during a charging session. They've rooted and moved on to the leaked Gingerbread or CM7 and haven't had any issues.
Me, I haven't had any issues with Stock 2.2 or CM, but the leaked Gingerbread does the same thing as described. It locks up and turns off while charging over night but also will just randomly do it throughout the day.
I don't think it is a hardware issue at all. I think it is some kind of driver/kernel issue.
Some reports state that the phone won't do this while charging over a PC-USB connection but does on a standard wall charger.
One thing to think about is which wall adapter are you using? The included on or another USB charger? I'm using my Nexus One wall plug, which some said could be the issue. I also use a wall plug from a MS Zune I found somewhere.
It could be the charging methods but that doesn't explain how it still does it while just being in my pocket. Now this is ONLY with the leaked Gingerbread/variants (EaglesBlood). Stock 2.2 and CM based roms I have no issues with. When I flashed the leaked build I found it powered off 3 times that night (after 5pm) by just laying around, and powered off in the morning just laying there on a charge.
The phone was at 100% when I turned it on. So maybe it is charging to 100% and turning off to prevent it from "over-charging"? I dunno but it still doesn't explain why it died 3 times without being connected to anything.
I say it is software. Try the latest CM7 #11 and report back. I think there is something fishy with the stock roms.
I am going to wait for the gingerbread update then move on to CM7. I will let you guys know if the new battery helps.
I rooted to cm7 and 2.3.3 update and this still happens... it definitely happens when charging towards full charge...
With that I also think the battery was bad since it happened 90% at charging ...
Im going to get a new one soon and see what happens..
Sucks for me though since I bought this phone from CL
Try CM7. There aren't any reports of the lockups. I'm actually running one of the later KANGs right now, which is a nightly created at a different time of the day.
CM7 #11 is available too. It isn't perfect but between the Theme app, Battery%, and Notification menu toggles... it is easy to deal with.
My problem with it now is the Sound will go out randomly and requires a reboot, but at least I'm not missing calls and notifications because it was off.
I have an non rotted G2x that I bought directly from A Tmobile store April 20th. I had random rebooted and almost daily my phone would lock up over night while charging. I was lucky I woke by myslef or I might have been very late for work. Amway... I was using my Nexus Ones charger, so I swapped it out and used the one that came from LG with the G2x. And I did not get anymore lockups after full charges overnight.
The other thing I did was every morning...I turn my phone off and then back on again.... right after I take it off the charger. And since I started doing that I got no more ghost restarts. Maybe it is coincidental....but it works for me. So far so good...watch as soon as I am done with this post....blame...reboot LOL. Anyway...try what I did. I thought I saw a reference tonight to rebooting the phone daily as a possible fix....in another post somewhere.
WTH my post disappeared.
I was coming back to edit it to say CM has a new #13 nightly:
http://download.cyanogenmod.com/?device=p999
My original post said to try CM7 before doing anything dramatic. CM uses their own Kernels which is what I suspect the problem is with the stock roms.
The official Gingerbread update should come with a new kernel update, as it did with other phones.
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
I guess the issue is with the battery itself. Try getting a new battery. I heard some guys experiencing the same and sorting things out replacing the battery....
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it
If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries
i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium
spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha
I agree. It still sounds like a battery issue.
I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.
I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App
Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.
If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!
The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.
I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..
Qhastic said:
I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..
Click to expand...
Click to collapse
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.
1BadWolf said:
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Sorry, meant clockwork mod, not cyanogen. I haven't flashed any ROMs on this phone yet.
Do you think the battery issue arose as a result of rooting/installing clockwork mod?
No no..Many phones these days fail to charge when drained because they use software to detect the charger and then allow current to flow.. This is unlike the older nokia phones or current HTC phones.. what you can do is as suggested above.. use a 9V battery or something that ought to do it.
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
minirx7 said:
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
Click to expand...
Click to collapse
Never flash anything or make major changes to your phone with a low battery (below 70%).
I may be the member he was talking about. I had a thread on this. Only difference was my phone wouldn't charge at all. When I plugged it in when it was off it would boot loop the charge screen. It was rooted and I had some bloat frozen, but the issue started after I installed Sugarsync. I had the same configuration for a few days with no problems, and my battery was about 50 percent when I tried to charge.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just trying to help. I freaked yesterday because no matter what i did, it wasnt charging. But once i fully powered off, it started chargin!!
scott14719 said:
Never flash anything or make major changes to your phone with a low battery (below 70%).
Click to expand...
Click to collapse
I just flashed a ROM with 56%. I like to live dangerously.
AdePower said:
I just flashed a ROM with 56%. I like to live dangerously.
Click to expand...
Click to collapse
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
scott14719 said:
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
Click to expand...
Click to collapse
I bricked a S2 like that. Flashed a rom adn the battery drained in the process, causing it not flash properly. phone was dead, no download mode or anything.
Hello everyone.
I own a Samsung Galaxy Tab 2 7.0 (GT-P3100) running a cm13 official. Before, it was running so well to my device but when my original charger broke it didn't.
I immediately bought a cheap charger from a Shop with no warranties. After I went home, I charged it immediately. It wasn't charged for like 12 hours so it was showing the charging icon when turned off charging. When I booted it up (note that the charger was still plugged in) it shows the booting anim. and then freezes.
Thinking that my tab was bricked or something, I wiped it, flashed the same ROM and gapps but still when booting up whil e charging, it'll froze on the boot animation.
I then changed my ROM to aokp, not minding the bug and it was running so well. (Freezing didn't occur on this ROM)But the thing is I noticed something odd about the charger. When I play DQ (Dungeon Quest) or a video on the internet, when the charger is plugged in or out, it suddenly closes the app.
Well I didn't mind about that but the time came that I got bored with AoKp and went back to Cm13 (Partially thinking that the bug is fixed) it booted up and froze on the boot anim. So I unplugged the charger and booted it up it worked like magic and I plugged it back after the animation has ended but unfortunately it freezes around 5-10 mins.
Anyone else experiencing this problem? Does anyone know some solution? Please let me know.
I don't wanna ditch this charger, there might be another solution than that.
Update:
I've just flashed another ROM called OrionOS which is currently on android 6.0.1 and the problem still exist, same as CM13.
It seems like this problem occur on Marshmallow Roms. Well I can't really say that but
I'm going to try other ROMS out.