My phone refuses to charge! What should I do?
Can you flash a different rom and radio? When I used the bamf rom, my charging light never came on but it was still charging.
Sent from my ThunderBolt using XDA App
Apparently turning off fast boot works, but I'm trying to figure out how to do that...
It's in settings>power. Uncheck fastboot, reboot and you should be charging just fine.
I rebooted while plugged in and it was good to go....had the same issue
Change kernel, mine is charging fine.
Alright I turned off fastboot. What kernel are you guys using?
I cleared the battery stats/data and rebooted and my thunderbolt recharged fine. Didn't uncheck fast boot option
I still can't get it to charge. It says its charging but it's actually losing power
What Kernel are you using? I'm using the modded Test 7 that Adrenelyn listed in the BAMF thread. I think Imo has a link up in his kernel thread as well. I haven't had any charging issues using this kernel.
2.5.3 test 7
metstang said:
What Kernel are you using? I'm using the modded Test 7 that Adrenelyn listed in the BAMF thread. I think Imo has a link up in his kernel thread as well. I haven't had any charging issues using this kernel.
Click to expand...
Click to collapse
I had plenty of charging issues using this kernel. My phone would take forever to charge. However the one that says "test4" is working fine for me.
Well after further usage I have to retract my last statement, Test4 acts the same as test7. I tried the suggestions mentioned here, (turning off fastboot and clearing battery stats and rebooting) and now all seems well. My feeling is that you can leave fastboot on but you have to clear the battery stats and reboot to solve the slow charging problem. Only thing I don't know is if we have to do it everytime we charge. Maybe someone who has tested more than myself can better answer this.
Related
Just curious if anyone else here experienced this...I plug my charger in (AC or through my computer) and what shows up it's charging, isn't it's actual total.
IE, it shows it's charging and it's at 85%...but if you unplug it, it'll show up it's really a different level, sometimes less, sometimes more. Heck, one night it sat on "charging 37%" for 8 hours while I slept and was still like that when I woke up...but when I unplugged it, it was really fully charged.
TMO is sending me out a replacement device, so I'm really not worried about it. Just curious if anyone else had this happen to them?
bballcat03 said:
Just curious if anyone else here experienced this...I plug my charger in (AC or through my computer) and what shows up it's charging, isn't it's actual total.
IE, it shows it's charging and it's at 85%...but if you unplug it, it'll show up it's really a different level, sometimes less, sometimes more. Heck, one night it sat on "charging 37%" for 8 hours while I slept and was still like that when I woke up...but when I unplugged it, it was really fully charged.
TMO is sending me out a replacement device, so I'm really not worried about it. Just curious if anyone else had this happen to them?
Click to expand...
Click to collapse
Maybe you can share what ROM and kernel you use.
Sent from my Calculator with Android.
CM7 RC1 w/ faux's kernel
Sent from my LG-P999 using XDA App
bballcat03 said:
CM7 RC1 w/ faux's kernel
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
If you use the DS driver version of faux's kernal, it's well documented that the battery readings will be wonky...but your phone should run cooler. The CM driver version has more accurate readings, but is reported to run hotter.
edit: Waiting for next post: "Which one is better?"
Nope, it won't be "which one is better"...it'll be...how do I know which of those I'm running?
Also, that's just what I'm currently running. I've flashed nightly files, EB, etc...all with the same.
As I said, TMO has shipped me out a new device, so I'm not worried about it. Just curious if anyone else had this problem (which you say it is wonky with certain driver).
discuss. as far as i can tell its related to the battery driver and only occurs while charging on AC. have not experienced it on USB charging off pc/other. baseband update failed to correct the issue. change of cm7 nightlys does not solve the issue. changing kernals "faux made it sod and overheat like hell" trinity is untested. alternate roms are so far untested "most are based off cm7 anyhow so i dont see trial and error for other roms being worthwhile. some claim keep awake while charging solves the issue since the phone will not sleep during charge. believe cm7 has this removed unfortunately.
Solace50 said:
discuss. as far as i can tell its related to the battery driver and only occurs while charging on AC. have not experienced it on USB charging off pc/other. baseband update failed to correct the issue. change of cm7 nightlys does not solve the issue. changing kernals "faux made it sod and overheat like hell" trinity is untested. alternate roms are so far untested "most are based off cm7 anyhow so i dont see trial and error for other roms being worthwhile. some claim keep awake while charging solves the issue since the phone will not sleep during charge. believe cm7 has this removed unfortunately.
Click to expand...
Click to collapse
I was getting the SOD whenever my phone would go into standby... Never when it was charging
Sent from my LG-P999 using xda premium
I had a lot of reboots when charging on AC too.
Sent from my LG-P999 using XDA Premium App
i had a similar issue as well with the phone would just shut off. making the assumption its related to the 15% shut off bugg since when i turned it on "not a sod" it showed not 100% battery despite it was on the charger. this only happend if it was left on charger for a long time. random reboots in cm7 nightlys was solved a while ago opposed to SOD/random shut offs. that or the baseband update solved it
Solace50 said:
i had a similar issue as well with the phone would just shut off. making the assumption its related to the 15% shut off bugg since when i turned it on "not a sod" it showed not 100% battery despite it was on the charger. this only happend if it was left on charger for a long time. random reboots in cm7 nightlys was solved a while ago opposed to SOD/random shut offs. that or the baseband update solved it
Click to expand...
Click to collapse
The baseband has nothing to do with reboots or SOD's.
Sent from my LG-P999 using xda premium
I have 2 G2x, both afflicted with "get hot near camera with SOD with significant battery drain" issue. Rebooting once a day fixed it for both phones. Our SODs would happen randomly - always with screen off, usually NOT on the charger. I charge on USB, she charges on A/C adapter. My wife doesn't always reboot, so I installed setCpu to limit screen off cpu usage, and also installed watchdog lite. So far watchdog lite has had only one hit - from "Linux Process' using 51% cpu - but no SOD.
The only reason I am on this forum is due to SOD - my wife is on-call, and NEEDS a phone, not a brick. the G2x ROCKS, except when it is a brick - then it SUCKS!
My goal is to either
A) find the SOD problem
B) have the SOD problem GO AWAY.
I am interested in any input or organized testing to fix this problem.
SOD? Sleep of death? Sorry, been away from xda for a bit.
My current issue (with 2 phones, and the replacement unit has this after 3 days.) is sometimes that it refuses to charge until I do a battery pull. Once my first g2x (the second i've owned. 3 total) got so low it wouldn't boot or charge and no battery pull would work for a couple days. Got a new one mailed to me, same problem.
I'm really considering demanding an upgrade, maybe to Sensation. Sorry if off topic, but don't want to go posting duplicate topics.
Sent from my LG-P999 using XDA App
My phone keeps shutting off all the sudden like the battery is suddenly dieing. It doesn't matter what the battery percentage is. I'll manage to reboot it after a few tries and every time the battery percentage jumps around. I'll boot up into recovery and can play around in there all day without the phone shutting off but once I leave recovery it keeps happening randomly. The only time it won't reboot is when I have it plugged in (this is how I narrowed it down to a battery issue).
I've tried charging it all the way up but it still happens. I've wiped battery stats and have done a full wipe and fresh install. It happens with custom kernels AMD the stock kernel.
Is my battery fried or is there something else I can do?
Sorry for any typos I'm on my phone now.
I had similar problems. By chance, do u use juice defender? I was troubleshooting my issues and when I stopped using JD my shutoff problems disappeared.
Sent from my HTC Sensation 4G with Beats Audio using XDA
droy.cms said:
I had similar problems. By chance, do u use juice defender? I was troubleshooting my issues and when I stopped using JD my shutoff problems disappeared.
Sent from my HTC Sensation 4G with Beats Audio using XDA
Click to expand...
Click to collapse
Nope no apps for the battery or cpu. The only "tweaking" app I use is sd booster. I don't see how that could do anything though.
Try reseting battery data in recovery
Sent from my Sensation 4G using xda premium
Have same issue, didnt managed to fix it so far
ImHuge07 said:
My phone keeps shutting off all the sudden like the battery is suddenly dieing. It doesn't matter what the battery percentage is. I'll manage to reboot it after a few tries and every time the battery percentage jumps around. I'll boot up into recovery and can play around in there all day without the phone shutting off but once I leave recovery it keeps happening randomly. The only time it won't reboot is when I have it plugged in (this is how I narrowed it down to a battery issue).
I've tried charging it all the way up but it still happens. I've wiped battery stats and have done a full wipe and fresh install. It happens with custom kernels AMD the stock kernel.
Is my battery fried or is there something else I can do?
Sorry for any typos I'm on my phone now.
Click to expand...
Click to collapse
i had the same issue two days ago and i fix it with this changing back firmware from 3.32 to 3.12 read post here
http://forum.xda-developers.com/showthread.php?t=1610232
& try it if u like for two days i had no issue
IT Manager Musa
my NS4G with MIUI 2.6.1 and Matrix 20.0 Kernal goes to 98% as soon as i pull off the charger. if i use it for 45 minutes unplugged its dead. if i use it while its plugged in, it will die!
should i get a new battery?
Yeah that doesn't happen to me... I would try a full wipe and reflash the same ROM (or a different one) and reflash kernel.
If that doesn't work then I would try another battery because that drain seems abnormal
I just wanted to say that I have been having similar battery problems. Using the exact same ROM and Kernel as the OP, today my phone died within 6 hours of use, with the screen having been on for no more than 50 minutes. I also turned off data, and sync during this time, and had my screen's brightness at the minimum.
I've wiped and flashed AOKP b-38 today, and the consumption seems to be much better.
Any thing to help?
thought i was the only one.
is it the kernal?
or is it because its time for a new battery?
How could I test to find out which it is...
Swap kernels. Probably easiest way to test.
Very possible its just an old worn out battery.
Sent by pocket technology.
hoping its just an old battery.
ive switched to CM9 / TouchWiz mod thinking it might be the ROM
im going to use the stock kernal from CM9 for a day to see if i could tell a difference.
ordered a new battery anyways.
saw on a forum somewhere a guy complaining about this problem since he switched to ICS ROMs .. hopefully thats not the case because i LOVE 4.0.X
mathkid95 said:
Yeah that doesn't happen to me... I would try a full wipe and reflash the same ROM (or a different one) and reflash kernel.
If that doesn't work then I would try another battery because that drain seems abnormal
Click to expand...
Click to collapse
same problem, switched from MIUI to CM9 ... still using Matrix 20.0
Try wiping battery stats
Sent from my Nexus S using xda premium
If it were processes/functionality causing your battery drain, that quick, the phone would be piping hot at the same time!
superng888 said:
Try wiping battery stats
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No. Why would that have any effect on anything?
Sent by pocket technology.
JiminyCricket64 said:
If it were processes/functionality causing your battery drain, that quick, the phone would be piping hot at the same time!
Click to expand...
Click to collapse
yes, the screen also gets EXTREMELY hot!
Well in that case, what have you got installed? If you have apps constantly syncing, that could be part of the problem. What are your battery stats saying is using the most battery? My phone gets warm, but as expected since its being used. If its not being used,it could be a rogue app or the phone could be constantly searching for a good signal.
Sent by pocket technology.
i have barely any apps.
i only have facebook, xda, sportscenter and instagram installed besides GApps.
i have the problem even before i download apps as i just flashed CM9
also its so bad, that if i start using my battery when its @ 10% PLUGGED IN, it will eventually die on me. even though its charging..
Hi I have now had my OPO for one year now. 3 months ago however I ruined my display due to water going in the phone, rest of phone was working fine. I brought in a new display and fixed it just yesterday. Phone's fine however I've run into one problem.
Phone charges really slowly. 5 hours for a full charge. It wasn't like that before. It used to take 5 hours only if I was using a 1A charger. But now even with OPO charger and a Sony 1.5A charger it takes the same. Previously it only took 60-90 minutes with the OPO charger.
I used the OPO Charging Current app and I'm only getting on average 300 mA while charging. Shouldn't I be getting around 2000?
help needed
Edit: I forgot to add, I was in CyanideL ROM before, thought it was a software issue, and instaleld BlissPop latest, but same on both
Guys help?
Bump for help :/
naeem76 said:
Hi I have now had my OPO for one year now. 3 months ago however I ruined my display due to water going in the phone, rest of phone was working fine. I brought in a new display and fixed it just yesterday. Phone's fine however I've run into one problem.
Phone charges really slowly. 5 hours for a full charge. It wasn't like that before. It used to take 5 hours only if I was using a 1A charger. But now even with OPO charger and a Sony 1.5A charger it takes the same. Previously it only took 60-90 minutes with the OPO charger.
I used the OPO Charging Current app and I'm only getting on average 300 mA while charging. Shouldn't I be getting around 2000?
help needed
Edit: I forgot to add, I was in CyanideL ROM before, thought it was a software issue, and instaleld BlissPop latest, but same on both
Click to expand...
Click to collapse
Same problem with me in each and every ROM. Never found any workarounds. So I just flashed AK kernel and increased AC Charging current to 2100mA using Synapse. Now it works alright but whenever I plug into charging I must check what current I am getting because sometimes even if I have increased it to 2100 it charges with 50-100mA. Simply reconnecting the chrger does the trick though. Also IF you dont prefer AK Kernel, latest Resurrected Kernel also has the feature, but you'll have to increase the currently manually at each boot using Terminal.
SaurabhMumbaiOneS said:
Same problem with me in each and every ROM. Never found any workarounds. So I just flashed AK kernel and increased AC Charging current to 2100mA using Synapse. Now it works alright but whenever I plug into charging I must check what current I am getting because sometimes even if I have increased it to 2100 it charges with 50-100mA. Simply reconnecting the chrger does the trick though. Also IF you dont prefer AK Kernel, latest Resurrected Kernel also has the feature, but you'll have to increase the currently manually at each boot using Terminal.
Click to expand...
Click to collapse
Met I'm already using AK kernel but setting that does nothing for me, maybe its a hardware problem for me