Related
Hi everyone (and sorry for my bad english) !
Since some days my GSM Galaxy Nexus is anoying me with a problem I can't understand.
At random moments, my GN thinks he is charging but he isn't even plugged !
The indicator in the notification bar shows the battery is in charge and all the phone believes he is charging.
Other problème, the charging indicatore comes and goes again and again and again, so the scree goes on everytime the GN is "plugged in".
My battery goes down at the speed of light this way ...
I tried to wipe, uninstall potential apps that could cause the issue, changing rom, changing kernel ... It still happening but not every time. Often it comes when the battery is under 50% or arround. I also have battery drops when I reboot the phone, like if the battery wasn't correctly calibrate ...
If I reboot the phone, the problem still here, if i get the battery off and then put it back and reboot the phone it works normaly ... for a indeterminate time ...
This problem make me crazy, is anyone got a solution ?
Thanks for all.
Anyone can help please ?
I would definitely demand a replacement battery. For me it seems like the battery is broken, therefore it's a warranty issue. If the problem still exists, it must be the hardware of the phone itself. I don't think it's a software problem, since you wiped, changed rom and even the kernel.
So demand a replacement of the battery!
Thanks for your answer ! I'll try this but I don't think samsung customer support will send me a replacement battery like that, they will ask me to send back the phone I think.
I recently had the same issue... here's what fixed it for me. I took the battery out and left the phone plugged into the outlet. Let it sit. I then installed the battery and let it finish its charge while the phone was off. I then took the battery out, unplugged the charger from the phone, and reinserted battery. Power on, VOILA! Mine was back to normal. Hope this helps.
Thanks for helping ! I'll try this
I just saw that I'm not alone in this case : http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=23789
This issue is considerated as a medium priority, I hope for a fix !
I have the exact same problem, and have also commented on the issue at code.google.com. I have also tried "everything". Changed ROM, kernel, wiped battery stat, even let it fully charge while off. Still the same problem where it show as charging in notification bar when unplugged.. and when it have drained to below 50% or so, it start to flicked between charging and not-charging and drains even faster.
After checking CPU Spy it tells me that the phone never goes to sleep, this causes the battery to only last about 12-14 hours by itself..
I have also tryed to open the phone and clean the connector, but it did not fix it. One thing that is strange, is if I pry a toot stick or similar in the micro-usb-connector to press the connector plate (inside the micro-usb-connector) down with the phone faced up, it actually stops to flicker and stays not-charging.
---------- Post added 5th January 2012 at 12:18 AM ---------- Previous post was 4th January 2012 at 11:44 PM ----------
Same problem here: http://forum.xda-developers.com/showthread.php?t=1379478 and here: http://forum.xda-developers.com/showthread.php?p=21031287#post21031287
I have the same problem, and it make my crazy.
I bought the phone about month ago and this problem came in the second week.
I plugged my phone up to my car charger omw home for lunch and the stupid charging issue started to happen all over again... I had to do the whole thing over again. Remove otterbox, back shell, battery, and put it all back together. I'm really trying to avoid swapping the phone out with verizon. With the way it's looking, I'm about to call and hassle a VZW CSR and get me an instant swap in the morning. This is unacceptable SAMSUNG. Bad thing is, it must be common with Smsg phones, as I found 5 other devices of theirs that seemed to have the same problem Nexus S and Fascinate being two of them.
Same issue here as well, with the battery icon showing the charging bolt despite not being plugged in.
This will happen when the phone is not in use, and ill notice the screen flash on for a moment.
I tried the solution offered in this thread, only to have the symptom return just hours after powering the phone back on, and w/o being plugged back into another charger.
Same here, the solution didn't work for me but push the conector down with a toothpick seems to work for me ... for the moment.
So it seems to be a hardware problem of the device !
I have now ordered a new USB connector board to see if that fixes it: http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=150713366355
Will report back.
---------- Post added at 06:30 PM ---------- Previous post was at 06:01 PM ----------
When did you buy your phones? This could be a problem on early batches.
Could you see what part number you have on the actual USB connector?
I see that on this replacement board the number is 1H13D, while my number is 1J10F.
The replacement board with 1H13D written on it: http://www.globaldirectparts.com/v/vspfiles/photos/SMSNG6111630-6.jpg
Melhouse said:
I have now ordered a new USB connector board to see if that fixes it: http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=150713366355
Will report back.
---------- Post added at 06:30 PM ---------- Previous post was at 06:01 PM ----------
When did you buy your phones? This could be a problem on early batches.
Could you see what part number you have on the actual USB connector?
I see that on this replacement board the number is 1H13D, while my number is 1J10F.
The replacement board with 1H13D written on it: http://www.globaldirectparts.com/v/vspfiles/photos/SMSNG6111630-6.jpg
Click to expand...
Click to collapse
Hey, strong work! You might diagnose this thing before Google does. Keep us posted.
I'm experiencing this too, I did have it go away for about a week, but now it's back. I"m not looking forward to RMAing it, because I ordered it from the US and I'm in the Caribbean. I'm hoping the USB board replacement will work - waiting to see the results.
So glad I finally found this thread....
This started happening to me Friday night. First thing I noticed was while I was out the battery symbol had the lightning bolt in it as if it was charging, but it wasn't.
Long story short, nothing I do is able to charge the phone, both while the phone is on and while the phone is off) and it's REALLY pissing me off. The only response I can get from the phone is when it's off, it keeps looping over the two battery animations and acts like it's charging, but it's really not.
In all my playing around with it I somehow got it to charge to 40% yesterday. The only thing I can say for certain was that the phone was plugged in while I was trying to boot it up and when it shut off I didn't see the battery charging animations so I left it alone for a little bit before I checked it out and was surprised to see it charged a bit.
Today I was able to have it happen again and got the battery to 60%. This time I Started from the bootloader and again, when it turned off, I didn't see the battery animation.
I was able to reproduce this again just now by going into the bootloader and just choosing the option to power it off. Will report back in a little while to let you know if it charged past 60% after doing that.
Edit: powering off from the bootloader did not charge the phone. I accidentally pulled the battery and it went from 60% to 37% when I turned it back on. I think there is something screwy with my battery. Does anyone know if the regular Verizon battery fits in the GSM version?
I've got at least a similar issue, but managed to get a fix working (at least for now). I've had the phone for about 2.5 hours now. I got it with around 50% charge, after 1.5 hours, it was at 24% so I went to charge it. Tried the included USB cable to my Windows 7 PC, it tried to install drivers, the install failed. The battery was labeled as still discharging and the unlock screen told me to charge the battery.
I proceeded to try the samsung charging head thing with the original cable in one outlet, then in two more - same result, no charging indicated. Tried with a brand new micro USB cable and had no results. Tried the other cable with the PC. I read around on the issue a bit and found this thread, since people were saying it could be software related, I figured I would power down the device and try again.
I powered down the phone while it was disconnected from USB. I then plugged it into the USB cable connected to my computer. My PC then recognized the device and installed the drivers correctly, the bolt over the battery icon appeared on the Galaxy Nexus's screen. I let the screen turn off then woke it again, the battery charging animation was going. I booted the device while connected to USB. Now in the OS it says the battery is charging and it was charging from about 42% - so I think the actual battery power was not being properly reported before the reboot and when the charging problems were happening.
I'm hoping this has set it to work, but if something else happens, I'll post here again.
DaJMasta said:
I've got at least a similar issue, but managed to get a fix working (at least for now). I've had the phone for about 2.5 hours now. I got it with around 50% charge, after 1.5 hours, it was at 24% so I went to charge it. Tried the included USB cable to my Windows 7 PC, it tried to install drivers, the install failed. The battery was labeled as still discharging and the unlock screen told me to charge the battery.
I proceeded to try the samsung charging head thing with the original cable in one outlet, then in two more - same result, no charging indicated. Tried with a brand new micro USB cable and had no results. Tried the other cable with the PC. I read around on the issue a bit and found this thread, since people were saying it could be software related, I figured I would power down the device and try again.
I powered down the phone while it was disconnected from USB. I then plugged it into the USB cable connected to my computer. My PC then recognized the device and installed the drivers correctly, the bolt over the battery icon appeared on the Galaxy Nexus's screen. I let the screen turn off then woke it again, the battery charging animation was going. I booted the device while connected to USB. Now in the OS it says the battery is charging and it was charging from about 42% - so I think the actual battery power was not being properly reported before the reboot and when the charging problems were happening.
I'm hoping this has set it to work, but if something else happens, I'll post here again.
Click to expand...
Click to collapse
I've had the phone for over a month now and never had any issues. I've been trying to plug into a Mac so drivers aren't an issue (I know from previous phones that in Windows the phone wouldn't charge until the right drivers were installed).
There's definitely something very wrong w/ the phone and I fear it's likely a hardware issue, as even when the phone is off it won't charge (but acts kind of like it is).
Right now the only surefire way for me to charge my phone is let it die all the way down and keep trying to boot it up until it dies during a boot before the OS comes up (at which point it'll charge).
For what it's worth I fixed the phone on Monday. I stuck a wooden stir stick from work in the usb port and pushed down on the plate inside ever so slightly. I'd seen this suggestion from a few places online, but I was pretty skeptical. Well, much to my surprise it started charging!
I quickly got it back to it's stock state and re-locked the booloader in case I end up needing to send the phone back to Sammy if the problem happens again.
So far so good, but I've been very careful when plugging and unplugging the usb cord.
I think it's important to keep the OP's issue in mind, because I'm pretty sure there are two different issues here.
1)Many of us have an issue were the phone shows it's charging WHILE UNPLUGGED, causing the screen to flick on repeatedly. This may/may not be accompanied by a charging issues - in my case it isn't.
2)A second issue where owners have problems charging their phones (but never experience the charging while unplugged bug).
I think the intent of this thread is to track (1). I've never heard of the toothpick issue helping those experiencing (1).
How are people pushing the usb plate down, any pictures?
I have a strange issue that my Samsung Focus used to get when it was first released. The Focus was later fixed with a Firmware update.
When I plug in my power cord, SOMETIMES, the screen becomes unresponsive, or glitchy. Also, instead of charging my phone, it starts to drain the battery. I can watch the Diagnosis app (##634#), and it is pulling charge, instead of pushing it. If I unplug and restart my phone, then plug it back in, it starts charging it normally.
Also, when I power off my phone while it's plugged into power, it goes into a reboot loop showing battery empty, even though the battery is fully charged (or, sometimes, it locks up and I have to unplug to restart). I have to unplug the cord and restart, or it never powers back on.
I've already tried multiple Hard Resets, and still happening. I'll keep an eye on this, and see if anyone else is having the same problem. If not, I might exchange it. If others are, then I will expect Nokia to fix it shortly and I won't stress about it yet.
PS: Lumia 900 Black
I had this happen once
Sent from my Lumia 900 using Board Express
Which charger/cable are you using? I found that I had this problem with my e900 using a cheap third party charger. I'm having the same issue with my Lumia now, but on a different charger (that was working fine on the e900). Going to the first party charger or playing around with another one I had at home seemed to solve the issue.
genericasian said:
Which charger/cable are you using? I found that I had this problem with my e900 using a cheap third party charger. I'm having the same issue with my Lumia now, but on a different charger (that was working fine on the e900). Going to the first party charger or playing around with another one I had at home seemed to solve the issue.
Click to expand...
Click to collapse
Yes, I did notice it's mostly a third party charger. But it also does it on the PC USB port. Likely due to low amperage too. I understand the lumia has a large power requirement, but the PC USB port should not cause it. Its not like they will never be used on PC USB power.
Like I said above, my Focus had the same issue, and they fixed it with a firmware update. I'm sure Nokia will do the same.
Good luck. Keep us updated.
I had an issue just now while charging my Lumia 900. The battery was around 15% so I plugged it in for a charge. I went to look at something on the phone a few times while plugged in and the first few it was fine. Then on the third time I couldn't get any response at all from the phone. I unplugged it and had to hold the power button for a long time to get it to come back on. This is the first "issue" that I've experienced with this phone since getting it on Friday. I haven't had any data issues or anything else that some others are seeing. Not sure why it happened but I'm concerned it might not be an isolated incident.
At this point this has only happened once and while charging. Not sure if its related to being plugged in or if it could happen while under normal use yet.
my battery was critically low and the screen became unresponsive..it just froze on whatever I was doing and it wasn't responding to any of the commands..so I had to hold the power button for a long time and restart it..but upon restart it did it again..then I plugged in my charger and it was fine after that...does the lumia charge while off? or is the phone supposed to be on whilst charging?
Those are the exact symptoms my Samsung Focus had until they fixed it via Firmware.
Windows phones only charge while on. If the battery is exceptionally low, it will charge just enough to be able to power itself on, then it will finish charging while on. It's designed that way. I'm looking forward to firmware and software updates, which will only make this phone better. Or, if we get to upgrade to Apollo, woohoo!
Still love this phone though, even w the charging glitches.
Hi guys!
I bought my new HTC One X on contract with three UK about 10 days ago. Been working great and I've flashed several different roms on it, the latest being the AOKP jelly bean.
I was in the middle of setting up my Go Launcher last night, when the phone suddenly died. I thought it must have just crashed following some rom/kernel issue, so I tried to turn it back on, no luck. Also tried holding the power button down but to no avail.
I supposed that it might have run out of battery, as it was fairly low at the time, so I left it charging on USB (with the indicator light flashing) all through the night (around 9 hours) and this morning it still won't turn on.
The screen won't come up at all, and the phone doesn't vibrate or make any noise but if I connect it to my computer it will sometimes be detected and I can see the device in ADB.
"adb devices" first shows the device as offline, then if I run "adb kill-server" and try again then it shows the device as "HT23YW105462 recovery".
I've then tried running commands such as "adb reboot", "adb reboot-bootloader", "adb reboot -p" but no luck. The phone seems to recognize the command as it disconnects, but it doesn't turn back on.
Any theories guys? I hope my new toy hasn't been bricked somehow! If this happened to my Desire HD I'd just take the battery out to make sure it was fully off and try again... is this a good idea here?
Thanks in advance for any help you can give! Many cookies will be given as reward. (sorry for the long post )
- P.s. This is pretty urgent as I use this number for work!
:victory:
Ok, it seems to have been resolved at last... just for anybody who gets the same issue, here's what worked for me.
After doing some more searching I found someone mentioning this method: Leave the phone plugged in to your USB port for a while until the orange LED flashes. Leave it flashing for a few minutes, then quickly swap the lead from your USB port to a wall charger. If you leave it unplugged too long then it seems the LED stops flashing and it won't work, so do it quickly.
If successful the LED will keep flashing while plugged into the wall, and it will start to charge up. Give it a while (I left mine for about 25 minutes) then try and turn it on. This worked for me, but even after this period of time it had only charged up to 2%!
:S This is an odd phone indeed.
Very strange resolution IMHO.
This problems must be caused by discharging the battery more than it should (which I guess custom ROMs can cause)
/Croaton
Croaton said:
Very strange resolution IMHO.
This problems must be caused by discharging the battery more than it should (which I guess custom ROMs can cause)
/Croaton
Click to expand...
Click to collapse
Very strange indeed... I tried pretty much everything I could before this, but this was the only thing to get the phone to boot. Charging and working fine now :S. I'll have to make sure to never run it flat if I can help it, this would be a right pain if it it happened while I was out
Just saved from similar issue
My battery run out last night when I had the phone connected to the tv through USB>HDMI when i put it on the charger the charging light would not switch on. Phone wouldnt switch on either it was really dead!. Left it all night hooked up to charger and this morning still nothing, wouldnt switch on.
So I Hooked it up to the PC and after 10 minutes or so the light started to flash and I quickly inserted the usb charging cable and it started to charge.
Pretty sure I either discharged the battery to much (did update to 7.2.2 yesterday with 30% bat), OR something to do with having the USB>HDMI cable inserted when the battery run out.
Odd but brought it back to life (phew!)
silenttalker said:
My battery run out last night when I had the phone connected to the tv through USB>HDMI when i put it on the charger the charging light would not switch on. Phone wouldnt switch on either it was really dead!. Left it all night hooked up to charger and this morning still nothing, wouldnt switch on.
So I Hooked it up to the PC and after 10 minutes or so the light started to flash and I quickly inserted the usb charging cable and it started to charge.
Pretty sure I either discharged the battery to much (did update to 7.2.2 yesterday with 30% bat), OR something to do with having the USB>HDMI cable inserted when the battery run out.
Odd but brought it back to life (phew!)
Click to expand...
Click to collapse
Hmm, seems like a pretty common fault. Maybe an app that cuts power to the phone when it reaches a critical limit might be a good idea... I noticed that most phones seem to turn themselves off before fully dead, whereas ours now seem to completely flatten themselves. At least if it shut down at 1% you could still turn it back on when you found a charger, and it could tell you why your screen was about to go black rather than "poof, gone".
Anybody know such an app? Or should I make one (been wanting to get my hands dirty)
wont turn on
chrisoverson said:
Hmm, seems like a pretty common fault. Maybe an app that cuts power to the phone when it reaches a critical limit might be a good idea... I noticed that most phones seem to turn themselves off before fully dead, whereas ours now seem to completely flatten themselves. At least if it shut down at 1% you could still turn it back on when you found a charger, and it could tell you why your screen was about to go black rather than "poof, gone".
Anybody know such an app? Or should I make one (been wanting to get my hands dirty)
Click to expand...
Click to collapse
im unable to see led light i believe unsupported kernel fryed phone
My phone won't turn back on or charge anymore. The last thing i did was pause Google Music, then the phone just sat there. It wouldn't go to the home screen or anything, it froze. I pulled the battery and now it won't turn on or charge at all. Won't display the battery charging when i have it connected to the computer or wall. Can't enter fastboot either. I'm currently at work and the computers here wont recognize it when i connected via USB.
mhm motherboard sudden death..? it doesnt seems to be a brick.
fabulous69 said:
mhm motherboard sudden death..? it doesnt seems to be a brick.
Click to expand...
Click to collapse
idk but my own laptop won't recognize it either =/
Painkiller006 said:
My phone won't turn back on or charge anymore. The last thing i did was pause Google Music, then the phone just sat there. It wouldn't go to the home screen or anything, it froze. I pulled the battery and now it won't turn on or charge at all. Won't display the battery charging when i have it connected to the computer or wall. Can't enter fastboot either. I'm currently at work and the computers here wont recognize it when i connected via USB.
Click to expand...
Click to collapse
I doubt it's bricked. Will it start up into the bootloader?
Again, try pulling the battery for a few minutes. Then put everything back together but wait until you have access to a true USB charger, not a USB port on a computer. I've noticed with a few phones in the past (GNex included) that sometimes when I had a bad crash and the phone went unresponsive, that trying to get a hint of life while using a USB port didn't work as well as a charger. You'll probably have to leave it plugged in for a little bit, but after 15-30 minutes you should once again at least get the white battery charging icon to display front-and-center if you give the power button a single push. At that point, try booting into fastboot, then recovery and clean things up a bit before rebooting into android (Wipe Caches, Fix Permissions).
If not, seriously, do everything again, and wait with it charging overnight. I had a similar issue with my Nexus 10 after doing my first unroot and flashing on it. It took nearly an hour, but then I finally got the charging icon (in that case though, a battery pull wasn't feasible).
sporkette said:
I doubt it's bricked. Will it start up into the bootloader?
Click to expand...
Click to collapse
nope, won't start at all.
stefpap said:
Again, try pulling the battery for a few minutes. Then put everything back together but wait until you have access to a true USB charger, not a USB port on a computer. I've noticed with a few phones in the past (GNex included) that sometimes when I had a bad crash and the phone went unresponsive, that trying to get a hint of life while using a USB port didn't work as well as a charger. You'll probably have to leave it plugged in for a little bit, but after 15-30 minutes you should once again at least get the white battery charging icon to display front-and-center if you give the power button a single push. At that point, try booting into fastboot, then recovery and clean things up a bit before rebooting into android (Wipe Caches, Fix Permissions).
If not, seriously, do everything again, and wait with it charging overnight. I had a similar issue with my Nexus 10 after doing my first unroot and flashing on it. It took nearly an hour, but then I finally got the charging icon (in that case though, a battery pull wasn't feasible).
Click to expand...
Click to collapse
Yeah i tried all of that since 1 pm yesterday, that's when it just died on me. I have left the phone charging for over an hour and still don't get any sign of life, not even the white battery charging icon. Left the phone charging overnight, that didn't work also. I tried the OMAP fix but that also failed, it isn't recognized by my laptop.
That's a bummer. Once I had an Epic 4G that I also thought was bricked but the "leave it charge overnight" method worked even though the charging led wasn't on at all. I'm surprised that I now have seen an actual thread with a truly bricked device, not the usual "my phone is going into boot loops its bricked!" thread. Sorry to hear it man.
This may be irrelevant to you, but mine is on verizon and was having charging problems. I went into one of their stores and they had a replacement on the way in under 15 minutes of me coming in. Great service from them if that's who you're with carrier-wise.
crowmallet said:
That's a bummer. Once I had an Epic 4G that I also thought was bricked but the "leave it charge overnight" method worked even though the charging led wasn't on at all. I'm surprised that I now have seen an actual thread with a truly bricked device, not the usual "my phone is going into boot loops its bricked!" thread. Sorry to hear it man.
This may be irrelevant to you, but mine is on verizon and was having charging problems. I went into one of their stores and they had a replacement on the way in under 15 minutes of me coming in. Great service from them if that's who you're with carrier-wise.
Click to expand...
Click to collapse
Everything was working perfectly on mine, the battery was at 80%. I'm with T-Mobile and i know they don't carry the Galaxy Nexus. Would a Verizon store let me check if a new battery will be turn it back on? If not, guess i have no other choice but to call Samsung =/
Painkiller006 said:
Everything was working perfectly on mine, the battery was at 80%. I'm with T-Mobile and i know they don't carry the Galaxy Nexus. Would a Verizon store let me check if a new battery will be turn it back on? If not, guess i have no other choice but to call Samsung =/
Click to expand...
Click to collapse
The Verizon gNex uses a different batter than the GSM model.
3rdstring said:
The Verizon gNex uses a different batter than the GSM model.
Click to expand...
Click to collapse
Well that sucks Guess, it's time to call Samsung
I was rooted and running stock att, touchwiz for a while with no issues. It started to get slow and on my nerves (and I was thinking of all the empty promises about this phone like inductive charging, google wallet, JB4.2.2, faster than iphone etc.) so I decided to kick in the bucket and install CM10.1. Install went smoothly, I accidentally installed the wrong google apps, but realized it, reinstalled everything with the correct one, and all is well and dandy.
The entire time, the phone is sitting at 0% battery, so I am assuming I am barely charging enough for the phone to keep up with my usage, but it never actually dies so all is good. The icon says 'charging 0%'. I was messing around in the settings, and got to the LED color settings. Went to change the "low battery" one, and the current active one changes. I go to change the battery charging one, and nothing changes. I unplug the phone, and it immediately goes into shutdown mode due to low battery. I plug it back in and let it sit for like 5 minutes before actually booting it back up, and it boots up but battery is still at 0%.
Basically, battery drained its way down from fully charged to 0, and now won't go back up. The fact that the LED state thinks that it is "low battery" rather than "battery charging" leads me to think it is a bug. I checked the bugs thread that is stickied, and nothing comes up close to what I have. I am using the nightly build from 03-03-2013.
ph7ryan said:
I was rooted and running stock att, touchwiz for a while with no issues. It started to get slow and on my nerves (and I was thinking of all the empty promises about this phone like inductive charging, google wallet, JB4.2.2, faster than iphone etc.) so I decided to kick in the bucket and install CM10.1. Install went smoothly, I accidentally installed the wrong google apps, but realized it, reinstalled everything with the correct one, and all is well and dandy.
The entire time, the phone is sitting at 0% battery, so I am assuming I am barely charging enough for the phone to keep up with my usage, but it never actually dies so all is good. The icon says 'charging 0%'. I was messing around in the settings, and got to the LED color settings. Went to change the "low battery" one, and the current active one changes. I go to change the battery charging one, and nothing changes. I unplug the phone, and it immediately goes into shutdown mode due to low battery. I plug it back in and let it sit for like 5 minutes before actually booting it back up, and it boots up but battery is still at 0%.
Basically, battery drained its way down from fully charged to 0, and now won't go back up. The fact that the LED state thinks that it is "low battery" rather than "battery charging" leads me to think it is a bug. I checked the bugs thread that is stickied, and nothing comes up close to what I have. I am using the nightly build from 03-03-2013.
Click to expand...
Click to collapse
wipe cache/dalvik and reflash. if it does not clear the issue, full wipe and reflash. report back
Neither worked. I thought maybe I'm just playing around with the phone too much and not giving it a chance to charge, so I plugged it into a wall socket a couple rooms over so I wouldn't touch it. 15 minutes later, I turn it on and it is still at 0% charge. The phone is pretty hot at the charger port.
I'm starting to think this is a hardware issue, because it is also unresponsive when it goes into sleep/lock mode... Won't wake, and can't even call it. The only way to get it responsive again is a hard reset.
I should still have some time left on my at&t warranty, and I have a backup from when I was still on the original recovery. Where does CWM store the recovery files on CM10?
When I was using TW, they were just in a folder on the root called clockworkmod. They are actually still there, a couple "0's" down the line in the file structure... Not really sure what that does... Now the root has no clokworkmod folder, but it definitely is storing backups because I just backed up now, and restored to one when I originally installed CM10, and I can see them both when I select "restore" in the recovery menu. Is there any way that I can put one of my backups from my computer into that folder so that I can revert, unroot, and get this thing swapped out?
The battery has been giving me all kinds of issues since I bought it and all they offered last time I went was a new battery. Hopefully with it being unresponsive as well, they will just swap out the handset.
Update:
I was able to use odin to reflash the original rom, so I am back to the non rooted state. Battery seems to be working fine, and I haven't run into a hang on lock, so it is most likely software related. I am going to redownload all of my apps slowly and see if it is one of my apps causing the hang, but the battery issue seems to still be related only to CM10.1. After all that headache, I could care less if I go back to CM10, but I think maybe you guys would want me to troubleshoot this issue, so that you can possibly fix the bug?
Let me know.
ph7ryan said:
Update:
I was able to use odin to reflash the original rom, so I am back to the non rooted state. Battery seems to be working fine, and I haven't run into a hang on lock, so it is most likely software related. I am going to redownload all of my apps slowly and see if it is one of my apps causing the hang, but the battery issue seems to still be related only to CM10.1. After all that headache, I could care less if I go back to CM10, but I think maybe you guys would want me to troubleshoot this issue, so that you can possibly fix the bug?
Let me know.
Click to expand...
Click to collapse
Try AOKP next time
It seems to me...
It seems to me that the charging problem only happens when there are notifications waiting. As long as there are no notifications waiting, the red LED is on and the phone charges just fine. When a notification comes in and the blue LED starts flashing, charging stops or slows to a crawl or starts discharging. The longer this condition continues, the hotter the phone gets. After clearing the notifications, the red LED comes back on and the phone starts charging normally.
This seems to happen with Samsung chargers and off brand chargers.
Again, I don't know if this really happening. It just seems to all coincide.
therapyco said:
After clearing the notifications, the red LED comes back on and the phone starts charging normally.
This seems to happen with Samsung chargers and off brand chargers.
Again, I don't know if this really happening. It just seems to all coincide.
Click to expand...
Click to collapse
I have the same problem with at least 3 sammy based roms. If anybody has a solution please let us know. It is definitely related to the notifications.
how/what are you wiping before each flash?
Follow up...
It no longer seems to me that the flashing blue notification LED is the problem. I've identified two other issues with chargers.
The Samsung charger works well and fast, especially when plugged into the power outlet adapter and not computer's USB. I guess that's typical... something about only one pin being available for charging when the USB cable is connected to the port on the computer. The off brand charger (charger only, not USB/charger combo) was much slower and sometimes wouldn't charge at all.
The first I thing did was look at the tips. They are slightly different, but the thing I noticed is that two little "fangs" on the tips were more prominent/stiff on on the Samsung charger. I used a needle to pry/bend those fangs out on the off branded charger so that they pop out more. That resulted in a much more secure/tight connection to the phone and fixed the problem with the battery actually stopping charging or discharging while plugged into the off brand charger.
Next, I compared the power ratings on the two chargers. The off brand charger accepts 100-240VAC, 47-63Hz and 0.2A. Its output is 4.3-5.0V and a MAX of 0.8A.
The Samsung charger accepts 100-240VAC, 50-60Hz and 0.15A. Its output is 5V and 0.7A (seemingly a constant output no matter the input).
I hypothesize that the off brand charger's output is directly related to its input. So, the output at 120VAC input would be about 0.4A and the output at 240VAC input would be 0.8A. The Samsung charger, seems to have a constant output of 0.7A whatever the input is. So in the US with our approximate 120VAC, the off brand charger would put out maybe 0.4A and the Samsung charger would put out 0.7A or 75% more current than the off brand charger. This would explain the difference in charging rate between the two chargers.
I suppose I could get my multimeter out and verify this idea, but I'm too lazy and I'm satisfied with my hypothesis.
This happens to me once every 4-5 flashes. I usually get everything set up, reboot, then power down, remove battery for 30 seconds, power on (without charger), then plug in and it charges normally. If that doesn't work try enabling fast charge (if your kernel supports it).
Fast Charge FTW