Battery will not charge while phone is plugged in

cyanozen

New member
Dec 29, 2012
2
0
0
Visit site
Long time reader, first time poster here. I bought the Samsung Galaxy S3 directly from Sprint on Black Friday (11/24). The first thing I did with my SPH-L710 is install cyanogenmod10. I had cyanogenmod9 running on both epic 4gs I had, no issues ever.

On December 23rd, I decided to experiment with a nightly build of cyanogenmod10 for my phone. I downloaded and installed, disliked just about everything because it was buggy and such. Decided to flash back to the backup rom. Ever since then I have run into some major problems with the battery. It will not charge while plugged in. Sprint will not look at my phone until I restore back to the stock rom and unroot my phone so that's the last resort. I bought a second battery and external charger to help my cause while I figure this out.

I've wiped everything, including battery stats via clockworkmod recovery. I've factory reset/wiped data, wiped cache, wiped dalvik cache, etc. Tried different chargers (5), usb cords (5), mixed and matched, different wall sockets. It seems when I plug it in, the charging light goes on but then immediately switches to not charging. And a lightening bolt overlays the battery symbol. So I don't think it's a hardware issue. It connects as a media device to my computer and everything. However, I see that the battery is overheating from several different battery monitors. Is there something internal that stops the battery from charging if it's too hot? That might be my problem. If it is my problem, what can I do with the battery to stop it from overheating? Can something else cause the battery to overheat, say the cellular radio?

Does anyone have any ideas? Screen shots with information:

screenshot2012122917451.png

screenshot2012122917261.png

screenshot2012122917434.png

screenshot2012122917441.png


From last night:

screenshot2012122821190.png
 

Skunkape60

Well-known member
Oct 9, 2010
4,460
344
0
Visit site
Long time reader, first time poster here. I bought the Samsung Galaxy S3 directly from Sprint on Black Friday (11/24). The first thing I did with my SPH-L710 is install cyanogenmod10. I had cyanogenmod9 running on both epic 4gs I had, no issues ever.

On December 23rd, I decided to experiment with a nightly build of cyanogenmod10 for my phone. I downloaded and installed, disliked just about everything because it was buggy and such. Decided to flash back to the backup rom. Ever since then I have run into some major problems with the battery. It will not charge while plugged in. Sprint will not look at my phone until I restore back to the stock rom and unroot my phone so that's the last resort. I bought a second battery and external charger to help my cause while I figure this out.

I've wiped everything, including battery stats via clockworkmod recovery. I've factory reset/wiped data, wiped cache, wiped dalvik cache, etc. Tried different chargers (5), usb cords (5), mixed and matched, different wall sockets. It seems when I plug it in, the charging light goes on but then immediately switches to not charging. And a lightening bolt overlays the battery symbol. So I don't think it's a hardware issue. It connects as a media device to my computer and everything. However, I see that the battery is overheating from several different battery monitors. Is there something internal that stops the battery from charging if it's too hot? That might be my problem. If it is my problem, what can I do with the battery to stop it from overheating? Can something else cause the battery to overheat, say the cellular radio?

Does anyone have any ideas? Screen shots with information:

http://imageshack.us/a/img17/4230/screenshot2012122917451.png
http://imageshack.us/a/img837/5510/screenshot2012122917261.png
http://imageshack.us/a/img405/7375/screenshot2012122917434.png
http://imageshack.us/a/img69/8163/screenshot2012122917441.png

From last night:

http://imageshack.us/a/img87/6942/screenshot2012122821190.png

Did the Rom you flashed have the fast charge mod? If so a return to stock might fix it.
 

cyanozen

New member
Dec 29, 2012
2
0
0
Visit site
I believe after double checking both the kernel version and the fast charge app that it does not support fast charge. But some of the milder symptoms of fast charge match what is going on. Nothing has melted yet thank god!
 

Latest posts

Trending Posts

Forum statistics

Threads
942,406
Messages
6,913,939
Members
3,158,399
Latest member
pauloxcavalcante