Develop Bugs

[Q] Phone stopped charging

So all of a sudden today my phone just stopped charging. It worked last night when I was asleep, I got up and it was at it's normal 100% or whatever. Came to work after it draining like crazy down to like 66% in an hour span. It worked for a second at work, then it just stopped. I checked the port on my PC that I use, no issues with the port. Tried another one, doesn't charge. Turned off Fast_Charge, doesn't charge. Tried it in another computer, same deal. Tried another cord... same deal. So I thought: Could be software! Turned it off and it shows me the charging animation but I don't think it's working. I'm going to let it sit for a while as I saw in: http://forum.xda-developers.com/showthread.php?t=1411761 to see if this works. But I looked at the port and saw nothing obstructing it. I've taken the battery out and tried to power it on without the battery and that's a no-go. I'm thinking it's the actual port, which sucks cause I bought this phone out right.
Any more ideas?

Which ROM? I know cm9 had a problem with charging when phone is turned off.
The charging works as it should, but if you try to turn it on while plugged in the phone would freeze and battery pull was only option.
Swyped on my CM9 Galaxy Nexus

Whatever the latest AOKP is.
EDiT: I just tried to re-install everything and it's the same deal. I'm bout to lose my mind over here.

HTC One X Suddenly won't turn on!

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

[Q] Problems charging/holding a charge/can't boot

Having massive issues right now. Last night I left my phone plugged in AC to charge and ran a sleep tracker app. Woke up this morning and found the phone dead. I tried unplugging and plugging again multiple times and managed to get the Red LED blinking then it went steady indicating it was charging. Turned the phone on but as if it wasn't charging anymore, it powered off within minutes. I managed to get recovery running and factory reset (running CM10). Same issue still there. I even tried leaving the phone in hboot and recovery to charge but after 10 mins the battery went flat again. Now I've just left the phone off and plugged into AC. The blinking LED came on again then went steady - but after 15 mins the LED light disappears. I just left it like that, now the phone tries to boot up but gets stuck at HTC logo. Also it is incredibly hot.
Any ideas? Really need help here.
Additional info, installed NFS: Most Wanted yesterday, tried playing but phone really overheated big time. Could that have cause the motherboard to fry? Just seems odd though cause it boots up fine, just won't stay on - can't even get past the initial setup wizard.
Also I would take it back to Vodafone AU but since I can't get the phone up long enough to restore to stock, they might find out I've rooted and thus voiding my warranty.

I had the same problem. I installed NFS MW and it drained my battery like help and when i tried recharging it it wouldnt charge
at all. Even when i pluged the phone on it wouldnt charge. Tried a different cable. For all it could be a adapter/cable problem.
That was what it was for me. I tried a different charger and it worked. If you are using a different charger, use something with 1A output.

If the led is blinking, it means that the battery is verryy low.
once your phone turns on, turn the airplane mode ON and display OFF and wait a few minutes before using the phone.

no luck
xzallent said:
I had the same problem. I installed NFS MW and it drained my battery like help and when i tried recharging it it wouldnt charge
at all. Even when i pluged the phone on it wouldnt charge. Tried a different cable. For all it could be a adapter/cable problem.
That was what it was for me. I tried a different charger and it worked. If you are using a different charger, use something with 1A output.
Click to expand...
Click to collapse
Yea, I tried using a different cable, even tried using my old iPod USB to wall adapter. No luck there, but I think I'm on to something now. Thanks anyway

getting there
Vcek said:
If the led is blinking, it means that the battery is verryy low.
once your phone turns on, turn the airplane mode ON and display OFF and wait a few minutes before using the phone.
Click to expand...
Click to collapse
Hey, yea I figured that much from searching around. Too bad it's such a big flaw. I couldn't sustain a charge at all when I was still on CM10. Couldn't even finish booting up and it would just die. Voltage was super low was my guess. Tried using the fastboot charging script (http://forum.xda-developers.com/showthread.php?t=1658084&page=5) and managed to get battery up enough to flash stock boot.img, did a nandroid restore to Stock ROM then flashed stock recovery. Seems to be stable now, in airplane mode and display off. Started up phone at 4% and now it's at 6% so fingers crossed :fingers-crossed: Thanks for the reply though - needing all the tips I can get!

[Q] Galaxy S3 not actually charging after CM10.1 install

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

Charging Problems Please Help Have Had This Problem for Months and Still Do!!!

I have had this problem for about 2 months now, and it seems like everything I do, never fixes the problem. When I was rooted, I was having fun tweaking, flashing roms, and mods, but then one day my battery percentage was low so I plug my phone in the charger with the stock charger and cable that came with my GS3. I wait, 5 minutes goes by and I check my GS3 again, and it has the same exact battery percentage it had when I was going to plug it in to charge. Never even increased one single bit. So I thought to myself, that's strange. I wait another 5 minutes, and it only goes up by 1 percent. I was thinking to myself what the *beep*! Now I left it that night to charge, and I wake up... HOORAY! 100% fully charged! I take it out of the charger and BOOM! it drains all the way down, to a low percentage, which I'm pretty sure was the same percentage I had when I went to charge it last night. Now I was pissed man, phew, I got so mad! I read all over XDA and Android forums, and it seems like I'm not the only person who has this problem. There was one thread with like 10 pages and counting. There were answers like, "just wipe battery stats", I wiped battery stats, the problem still persists. It still takes a very long time to charge and, once I immediately take it out of my charger it drains, to a very low percentage. So then people were saying "it's the cable, just use a different cable" I use a cable from a Pantech charger and I wait. It charged my GS3 just like the way it is supposed too. I'm thinking to myself, great it's back to normal charging state! Then another day I plug it in the Pantech charger and my GS3 doesn't even recognize, that it is charging, no lightning symbol on the battery pic thing on the status bar. I wait and there has been no increase, but actually a decrease of battery. Again I was like what the *beep*! So I use various different chargers and my GS3 doesn't even recognize any of them that they are charging, EXCEPT for the stock Samsung charger that came with the GS3 which takes a very long time to charge and once it's fully charged and I take it out, it immediately drains to a low percentage. So I switched batteries with a friend of mine who had a high percentage, and I booted into CWM, and I wiped data/factory reset I wiped dalvik cache, and cache partition, and I reflashed my ROM. No fix. Same Problem. So I try many different ROMS, and every ROM I try. No fix. Same Problem. Even the very stable ones which supposedly have not many problems. I thought unrooting and going back to stock firmware would work. That's exactly what I did and... No fix. Same Problem. I downgraded to ICS and... No Fix. Same Problem. I have tried everything that people on XDA and other forums have said would fix the problem, and the problem is still there and it seems like it's not going anywhere.
SORRY FOR THIS LONG THREAD.
PLEASE PRIVATE MESSAGE ME ANYTHING THAT WOULD FIX THE PROBLEMS OR ANSWER IN THIS THREAD.
ANY HELP IS GREATLY APPRECIATED!