About a week ago, I flashed to the Beanstalk 4.2 JB rom. And found that while running the rom, I began suffering from real odd battery patterns.
I had two wall chargers and a USB cable to my computer, when I connected my phone to them, it would say that it was charging, but instead, it'd just drain the battery.
Using my 4.1 AOKP rom simply a few days ago, I never had a problem as weird as this. All my chargers worked on my phone, including the USB.
The only time I could charge my battery properly was to have to phone completely off.
So after a week, a few days ago, I flashed the SlimBean Rom in hopes I'd get a different experience from 4.2.
Now things got really weird. The phone would start repeatedly flashing that it was charging and not charging. Battery would still drain, what's worse is after calibration yesterday, I tried charging my phone while it was off. The battery during this charging process, said it was full. So I turned on the phone, and found my battery at 15%.
But this weird behavior isn't all the time, just now I plugged in my phone while on, using my wall charger. And right now it's acting fine. The question is, when and why is it doing something weird?
I'm not sure why this is happening. Everything was fine until 4.2 a week and a half ago, now my phone is acting like there isn't a consistent way to charge the battery, it's pretty much randomnly taking power and using it while it's connected to a charger.
Does anybody have similar problems with their phone after a flashing? Again, everything was fine when I was using 4.1.
patach said:
About a week ago, I flashed to the Beanstalk 4.2 JB rom. And found that while running the rom, I began suffering from real odd battery patterns.
I had two wall chargers and a USB cable to my computer, when I connected my phone to them, it would say that it was charging, but instead, it'd just drain the battery.
Using my 4.1 AOKP rom simply a few days ago, I never had a problem as weird as this. All my chargers worked on my phone, including the USB.
The only time I could charge my battery properly was to have to phone completely off.
So after a week, a few days ago, I flashed the SlimBean Rom in hopes I'd get a different experience from 4.2.
Now things got really weird. The phone would start repeatedly flashing that it was charging and not charging. Battery would still drain, what's worse is after calibration yesterday, I tried charging my phone while it was off. The battery during this charging process, said it was full. So I turned on the phone, and found my battery at 15%.
But this weird behavior isn't all the time, just now I plugged in my phone while on, using my wall charger. And right now it's acting fine. The question is, when and why is it doing something weird?
I'm not sure why this is happening. Everything was fine until 4.2 a week and a half ago, now my phone is acting like there isn't a consistent way to charge the battery, it's pretty much randomnly taking power and using it while it's connected to a charger.
Does anybody have similar problems with their phone after a flashing? Again, everything was fine when I was using 4.1.
Click to expand...
Click to collapse
Time for a new battery. Take it out and see if it spins. If it does, your battery is bad. If not, you may have a bad flash or rogue app; try clean flashing your 4.2 ROM and manually installing apps from the play store.
Sent from my SPH-D710 using XDA
Adreaver said:
Time for a new battery. Take it out and see if it spins. If it does, your battery is bad. If not, you may have a bad flash or rogue app; try clean flashing your 4.2 ROM and manually installing apps from the play store.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
What do you mean by "see if it spins?" Do you mean spin it flat on a table?
Also, I have factory reset and flashed both roms each time. Is that a clean flashing?
patach said:
What do you mean by "see if it spins?" Do you mean spin it flat on a table?
Also, I have factory reset and flashed both roms each time. Is that a clean flashing?
Click to expand...
Click to collapse
yes, spin it on a flat surface. if it spins like a top, its bad. if it doesn't spin, its probably okay.
clean flash (for AOSP) means:
Reboot to recovery
Make a nandroid
Wipe data/Factory Reset
Wipe /cache
Advanced > Wipe /dalvik-cache
Flash ROM
Flash Gapps
Reboot.
I have a new related question:
Is it possible that flashing a rom could damage hardware? Like the battery or something else?
The battery sometimes will not recharge EVEN when the phone's turned off ever since I switched to 4.2. It's become a phone that is insanely unpredictable.
Battery doesn't spin, it's still fairly heavy. I'm a little worried something darker might be effecting my phone now.
patach said:
I have a new related question:
Is it possible that flashing a rom could damage hardware? Like the battery or something else?
The battery sometimes will not recharge EVEN when the phone's turned off ever since I switched to 4.2. It's become a phone that is insanely unpredictable.
Battery doesn't spin, it's still fairly heavy. I'm a little worried something darker might be effecting my phone now.
Click to expand...
Click to collapse
Not a ROM issue. I recommend using triangle away to reset the binary counter, then Odin back to stock unrooted fl24 or gb27 and seek warranty replacement.
Sent from my SPH-D710 using XDA
Flashes Liquid Smooth 4.2.2 on my wife's E4GT about a week ago. She has been having the same charging problems, no issues on 4.1.2. I have flashed many 4.2.2 ROMs with no charging problems. I will restore 4.1.2 on her phone tomorrow and see if that fixes things
Sent from my SPH-D710 using xda premium
Same Problem
I am having the same problem with my phone. im running ReVolt JB 4.2.2 6/2/13 ...same weird flashing when connected to charger, battery only charges when its turned all the way off and plugged into a wall charger. Battery is still good doesn't spin...for me its only this rom that gives me trouble.
Everyone's has the 3.0 kernel on 4.2.2 or the 3.4 kernel on 4.2.2?
I've never had any issues on Slim Bean, Liquid Smooth, ChaOS, SuperNexus, Carbon Rom, CM10 WFTN.
On top of that, make sure you're using the original charger and usb cable too because using different types of cables
with the same type of usb port can also be the issue. ( Short, Long, MTP or PTP type for PC's only etc )
Also is your FAST CHARGE ( If supported by the kernel ) on?
Or is your usb cable / plug not connected all the way on both charger and wall port.
It could be a ton of different issues.
My friends wife had a problem when she was using 4.2.2 AOKP.
Turns out her original PLUG was the problem and she was using her husbands Note II plug just to charge the battery but
she still is using the original E4GT usb cable.
Spark91 said:
Everyone's has the 3.0 kernel on 4.2.2 or the 3.4 kernel on 4.2.2?
I've never had any issues on Slim Bean, Liquid Smooth, ChaOS, SuperNexus, Carbon Rom, CM10 WFTN.
On top of that, make sure you're using the original charger and usb cable too because using different types of cables
with the same type of usb port can also be the issue. ( Short, Long, MTP or PTP type for PC's only etc )
Also is your FAST CHARGE ( If supported by the kernel ) on?
Or is your usb cable / plug not connected all the way on both charger and wall port.
It could be a ton of different issues.
My friends wife had a problem when she was using 4.2.2 AOKP.
Turns out her original PLUG was the problem and she was using her husbands Note II plug just to charge the battery but
she still is using the original E4GT usb cable.
Click to expand...
Click to collapse
The cable shouldn't make a difference in how long it takes to charge unless it's an inferior cable. Note 2 and Epic 4G Touch are both Samsung cables, I can't imagine that they would make the Note's cable inferior to ours
Also, search through these forums and you'll find that the recommended cable for this device, actually is a Blackberry cable.
I had to get a replacement phone because my charging port was fried luckily I had insurance so the replacement phone was free. Initially my charging port was lose and the tech support at sprint tightened it up but it was all down hill from there...just an update to my previous post .... It was a hardware issue not a ROM issue.
Sent from my SPH-D710 using Tapatalk 4 Beta
Related
I have a strange issue and I am trying to recall if it happened well on srf 1.0 but I can't recall I think it did. When I plug my phone into charge during the day sometimes and i stress sometimes the charging icon starts to blink red and starts to discharge this happens with none standard usb cable into different computers or with the standard plug wall charger. I am on srf 1.1.1 with extended battery. I have fully charged ran battery calibrate apk and fully drained. I am thinking my extended battery might be defective but not sure. But a reboot fixes the issue for at least one attempt at charging. Any ideas?
I was using a HTC usb cable and I was loosing more battery it would never go above 75%. Changed cables and now it works better, but I did see the discharge icon also...
maxertx said:
I was using a HTC usb cable and I was loosing more battery it would never go above 75%. Changed cables and now it works better, but I did see the discharge icon also...
Click to expand...
Click to collapse
this happens with 2 different cables. I am going to test with stock battery to see if it happens. think it might be a bad extended battery or something with the rom that doesn't like the extended battery. Not sure that last part makes an sense but that is what it almost seems like.
When I got to work today, I grabbed another Epic from our device locker and that battery went to 100% and then I calib'd it and it seems to be working fine.. weird
Ihave charging probems with cheap thin cable chargers. But I got a usb cable for a droid x and it works better then any charger or cable I've tried
silver03wrx said:
Ihave charging probems with cheap thin cable chargers. But I got a usb cable for a droid x and it works better then any charger or cable I've tried
Click to expand...
Click to collapse
I have a good store bought cable that happens with as well. I am going to use the factory battery today n see what happens.
Sent from my SPH-D700 using XDA Premium App
So far unable to duplicate with stock battery. This should be fun trying to get a replacement extended battery. Or could this be a ROM issue with the extended battery? I know the only way to test is go back to stock to see. Now with that said I am will to test next week but I do have a question. I have a nanbackup when I reconvert to ext4 with cwm 3.0.2.5 I should be able to recover that right? Me switching back and forth from ext to rfs and changing cwm version shouldn't do anything?
I think I found out what part of my problem is. I think most of it had to do with EE03 modem and/or twilight kernel. I restored from my nanbackup installed Vision kernal and flashed back to ec05 and have had no problems. The nanbackup was created after the fresh install of SRF 1.1.1 w/twilight so I went back to my stock setup with no tweaks. Also found out about the DRM and SNS stuff draining battery life so I froze those in Titanium all is good now!
When my Galaxy Nexus GSM is not plugged in, the battery shows itself as "discharging". Previously this used to be "not charging". I have tried multiple (Jelly Bean) ROMs, different cables, wall and USB chargers. Same problem. The larger issue: my PC no longer recognizes my phone and I have resorted to using AirDroid to transfer files.
Can anyone shed light on this issue?
I have done full wipes, including wiping battery stats.
Mine was always discharging...
And make sure that you got fast charge off if you have that on. That disables MTP capability.
I have exactly the same problem...see my thread...its recent!
Sent from my GT-P1000 using xda app-developers app
I had a similar issue, and then not long after the phone refused to charge. I had to take it to get serviced, and the ended up giving me a refurb instead.
I think it has to do with the temp of the battery, if its too hot and you have it plugged in it will say discharging.
SEALBoy said:
When my Galaxy Nexus GSM is not plugged in, the battery shows itself as "discharging". Previously this used to be "not charging". I have tried multiple (Jelly Bean) ROMs, different cables, wall and USB chargers. Same problem. The larger issue: my PC no longer recognizes my phone and I have resorted to using AirDroid to transfer files.
Can anyone shed light on this issue?
I have done full wipes, including wiping battery stats.
Click to expand...
Click to collapse
First, don't use a charger other than the original. The different volts mess with the NFC chip and antenna. Try disabling NFC and rebooting. Leave NFC off and try to charge. If that doesn't do it I have another option that might work but I'm CDMA so you would have an extra step to change lines in file.
Thanks for the suggestions, guys. I tried disabling NFC but it had no effect. My phone is the international version (the box was in Polish) which is not warrantied through Samsung USA, so I guess I'm out of luck there as well. I'm just gonna hang in there until the next Nexus phone, I guess.
JediNinjafication said:
First, don't use a charger other than the original. The different volts mess with the NFC chip and antenna. Try disabling NFC and rebooting. Leave NFC off and try to charge. If that doesn't do it I have another option that might work but I'm CDMA so you would have an extra step to change lines in file.
Click to expand...
Click to collapse
When will people realize that the difference in voltage won't cause any problems with the phone as long as they're within safe range.
I've been using the charger that came with my G2 (htc) on my nexus for months and have no problems. I would've continued using the original one that came with the nexus but it had an annoying whine to it.
biscuitownz said:
When will people realize that the difference in voltage won't cause any problems with the phone as long as they're within safe range.
I've been using the charger that came with my G2 (htc) on my nexus for months and have no problems. I would've continued using the original one that came with the nexus but it had an annoying whine to it.
Click to expand...
Click to collapse
Really because it sure seemed to be my problem a while back and anytime i use a different one. Guess samsung and google must not know what theyre talking about.
Chargers are rarely the problem, however different usb cables might be the problem instead.
New glitch spotted when phone is of and in the charger it wil chrage for like 2 seconds and then the animation saays the phone is full!but 2seconda later its charging again so on and so on... sort of chargingloop..
But it never charges
Sent from my GT-P1000 using xda app-developers app
Sent from my GT-P1000 using xda app-developers app
Am using samr original charger and cord. Works fine
I have this same issue
My Galaxy Nexus from Verizon has worked flawlessly for several months now. It updated about 4 days ago to JellyBean 4.1.1 and I have been charging the same two wall chargers, car charger, and USB cables every day since I got the phone. I even was using the USB charger to deploy and debug a simple application I am building around noon today. This evening at about 8 PM while on the wall charger I noticed the charging stopped. No lightening bolt icon, status says Discharging, and I noticed one time that it said Not Charging. Neither of the wall chargers work, nor is it recognized by the laptop using the USB cable. It is at 65% charge and is dropping fast. It seems that no one has a fix for this other than replace the phone.
Very difficult for me to believe that the USB port just went bad using the same chargers every day. Hard to blame JellyBean that has run at least 4 days with no issue even though several sites point to a possible charging issue. I even dialed *#*#4636#*#* and checked the battery status, and it's health was good. I have not rooted or placed anything on this phone that is obscure beyond my simple near "hello world" development apps. I have rebooted, and performed a battery pull with no such luck. With the number of posts pointing to a JellyBean issue, and users experiencing the same issue after the upgrade to 4.1.1 I am leaning towards this being a software issue, but it is interesting at the number of posts saying that the their only fix is a refurb phone replacement from the carrier.
Pretty odd occurrence, and extremely frustrating. As I said the phone worked fine all day today. This just started a few hours ago for me.
Update
enviux said:
... No lightening bolt icon, status says Discharging, and I noticed one time that it said Not Charging. Neither of the wall chargers work, nor is it recognized by the laptop using the USB cable. It is at 65% charge and is dropping fast. It seems that no one has a fix for this other than replace the phone...
Click to expand...
Click to collapse
OK I have fixed my issue. and it does appear to have been hardware related. I will preface this with you must be very careful not to break your phone with the solution below. I read several posts about using contact cleaner on the USB port, so I looked at the port on the phone and noticed that the "toungue" inside the reciever USB port appeared to be slightly bent down. With the phone off and battery removed I used a needle to wedge under the toungue and bend it up ever so slightly making sure I would not break it. Pluged in the phone and it still did not charge. (That was last night) this morning with the phone at 55% and thinking it was going to need to go back to Verizion I did it again phone off and battery removed only this time a bit more forcefully out of desperation. I definitely moved the "toungue" up and even had a bit of difficulty getting the USB cord to slide back into the connector. But when it did the Phone is charging again. Appearantly I must of jammed the plug into the phone upside down last night when getting into my car and bent the "tongue" in the USB port. Lesson learned, and hope this helps others.
Means the battery has been recharged and discharged to the point were it holds less of the charge. Basically its an older battery, or its been tappered with with, probably a rom using to much ram or pussing the device a bit too far nightly and ported roms could be the cause I say stick to stock kernal unless you really now what to do
Scrap that wrong fourm I think
I flashed my Galaxy s2 with AOKP JB5 rom last week. worked fine over the weekend. Last night it stopped charging. It wouldnt drain while it was plugged in but it wouldnt charge either. Now it is just dead and just a non-charging paper weight. i cant flash or reset because i have no charge. I have tried cleaning the usb port... using both wall/laptop to charge. It shows the aokp charging icon and but will not charge.
Maybe your battery is shot? Not sure as I've never experienced something like this but it sounds like the battery isn't holding a charge.
I know my phone just vibrates if I plug in the charger when the battery isn't in it.
Yeah it doesn't sound like a rom problem to me could be either your USB port or battery
Sent from my SGH-T989 using xda premium
I've had this issue multiple times, still have yet to get a new battery. First time had it on the charger for a full day, it would constantly boot show 0% and shut off then boot back up. Randomly started charging again.
And again just this morning, it was still discharging while on the charger. Unplugged it a couple times now charging again, but slowly... Either way not exactly sure what it is either :-\
Sent from my SGH-T989 using xda app-developers app
I am having same problem my phone ran dead and wouldn't turn on even with the charger and wont go into download or recovery mode when connected to the computer. I was running rootbox rom I figure it could be a problem with the rom or something so I am going to try a friends battery into my phone and try install in recovery the latest update or see if that helps.
Hope my phone turns on and I will see if it will charge if not I can get one of those microusb port for galaxy s2 on ebay for about £10 and attempt to repair my usb port.
Your options:
1) Get a new battery.
2) Get charging port repaired.
3) Get a new battery and a wall charger for that battery.
[ NEXUS⁴ / VANILLA ROOTBOX / APEX PRO / TAPATALK ]
well just to update you my friend has a galaxy s2 aswell and I swapped his battery into mine and mine into his and my phone booted. My battery when put into his phone came up a yellow triangle for a while and then started charging again so maybe the problem lies with the yellow triangle thing? After I charged my battery a little bit in his phone put it back in mine and it works and charges so it wasnt the port a software problem maybe.
Updated the rom and all is working OK and my phone has died and it still charges so it baffles me why it done this.
It's the JB ROM
It's the JB roms. I've conducted tests with this ROM and some other NON-JB roms. The JB ROMS will allow for a device to be fully discharged, therefore killing the battery pack and requiring it be charged from an alternate source, if one is available.
Do NOT allow the ROM to reach below 2%, as you're about to have a rather difficult time recharging the battery if it goes completely dead. As I said, I can reproduce this, but I don't know WHY it's only with JB roms. I have successfully killed 13 PowerSkins to the point of no return with this test, and 28 batteries (17 OEM and 11 aftermarket), it's the ROM.
Has anyone had this problem before?
My phone says its charging but it discharges (sometimes stays at the same level and sometimes charges VERY slowly). I let it sit on the charger without playing with it and sometimes I have to let it charge while turned off. I have tried many different chargers/usb cables but cannot find a solution.
I have tried wiping the phone twice + I have used an ipad charging block some of the time (higher voltage and amperage I believe).
It works for a little while after a wipe but the problem always comes back. I am running the latest Task 650 rom with stock kernel...
Any suggestions? My last resort is to return it to stock and try getting a warranty exchange.
I have this problem charging in the car on a really long cheap USB cable. Are you using the stock battery and stock charger / cable?
the green man said:
Has anyone had this problem before?
My phone says its charging but it discharges (sometimes stays at the same level and sometimes charges VERY slowly). I let it sit on the charger without playing with it and sometimes I have to let it charge while turned off. I have tried many different chargers/usb cables but cannot find a solution.
I have tried wiping the phone twice + I have used an ipad charging block some of the time (higher voltage and amperage I believe).
It works for a little while after a wipe but the problem always comes back. I am running the latest Task 650 rom with stock kernel...
Any suggestions? My last resort is to return it to stock and try getting a warranty exchange.
Click to expand...
Click to collapse
Have you tried using BetterBatteryStats to see what's draining your battery so much? If nothing seems odd or over the top. It could be a hardware problem (battery, usb, etc).
BWolf56 said:
Have you tried using BetterBatteryStats to see what's draining your battery so much? If nothing seems odd or over the top. It could be a hardware problem (battery, usb, etc).
Click to expand...
Click to collapse
Well my battery is draining at the normal rate but it is not charging at the normal rate (most of the time it doesn't charge at all)
I have tried the stock usb cable and charging block, I also utilize the stock battery.
the green man said:
Well my battery is draining at the normal rate but it is not charging at the normal rate (most of the time it doesn't charge at all)
I have tried the stock usb cable and charging block, I also utilize the stock battery.
Click to expand...
Click to collapse
Have you tried plugging it in other wall outlets?
Also, did you try charging it through your PC? (can't use Fast Charge without another kernel than Task's)
BWolf56 said:
Have you tried plugging it in other wall outlets?
Also, did you try charging it through your PC? (can't use Fast Charge without another kernel than Task's)
Click to expand...
Click to collapse
Yes I have tried different outlets and through the PC. I have had this problem using both 4.1.2 (12/2) and 4.2.2 (2/15)
the green man said:
Yes I have tried different outlets and through the PC. I have had this problem using both 4.1.2 (12/2) and 4.2.2 (2/15)
Click to expand...
Click to collapse
Do you get this issue on stock or other ROMs?
Btw, there's 2/20 now.
BWolf56 said:
Do you get this issue on stock or other ROMs?
Btw, there's 2/20 now.
Click to expand...
Click to collapse
I don't know, haven't reverted to stock yet. I was running 12/2 for about 2 months with no issues though..
the green man said:
I don't know, haven't reverted to stock yet. I was running 12/2 for about 2 months with no issues though..
Click to expand...
Click to collapse
Try updating, if it doesn't work, try stock. if it still doesn't work, send it for warranty.
Try another cable or reverting back to stock. I've got 4 different Galaxy S variant phones and some of the provided cords have just given up the ghost and wouldn't charge quickly anymore. Some will work with another another and some won't. Revert to out of the box stock and see if that helps.
Mine was doing similar deal. I did the *#*#4636#*#* went to battery and found out when I plugged in stock charger and cable it said usb charging instead of ac charging. When I plugged in htc charger went right to ac charging. So I tried using a different cable with stock charger and it went ac charger and seam to fix the problem. In fact if I plugged in just the stock cable not hooked to computer or charger it would switch to usb when there was no power going thru it. Hope this helps.
Sent from my SAMSUNG-SGH-I747 using xda premium
I've been seeing the following problem on my Note II (L900): I plug it into the micro USB wall charger and the phone will not register that it is charging (no vibration, no change in battery icon, battery stats list "Discharging"). Sometimes this will change in a few seconds, other times it will take a minute or more. If I unplug it, the phone will tell me it's charging. It remains in this state a few seconds or more. Plugging in a second time will sometimes result in a quicker charging response (other times, not).
The problem first cropped up on a stock rooted MC2 build. It also appears on digiblur. CM builds seem to be immune as do some MK4 custom ROMs (no issue on Synergy or STS). It's frustrating because MC2 based ROMs seem to run best on the phone: great battery life, smooth performance and a lack of the nanny-ware that Samsung has added to the MK4 builds (I'm looking at you, high volume warning!).
Has anyone else seen this problem? I know that some of you are going to be quick to tell me that some part of my hardware is screwed up and it might be, but it seems strange that the problem is somewhat ROM-dependent.
I'd appreciate the help. Mainly, my goal is to get digiblur to work. If I could get it to charge it would be more top choice of ROM. That is, unless there is a way of keeping CM10 or 11 from ripping through my battery. Not an exaggeration, BTW, I get half the life on CM.
I'm relatively new to posting on XDA, but I'm not new to flashing ROMs. I had a OG EVO that ran CM7 until I upgraded. I'm a novice but a quick study.
Enderend said:
I've been seeing the following problem on my Note II (L900): I plug it into the micro USB wall charger and the phone will not register that it is charging (no vibration, no change in battery icon, battery stats list "Discharging"). Sometimes this will change in a few seconds, other times it will take a minute or more. If I unplug it, the phone will tell me it's charging. It remains in this state a few seconds or more. Plugging in a second time will sometimes result in a quicker charging response (other times, not).
The problem first cropped up on a stock rooted MC2 build. It also appears on digiblur. CM builds seem to be immune as do some MK4 custom ROMs (no issue on Synergy or STS). It's frustrating because MC2 based ROMs seem to run best on the phone: great battery life, smooth performance and a lack of the nanny-ware that Samsung has added to the MK4 builds (I'm looking at you, high volume warning!).
Has anyone else seen this problem? I know that some of you are going to be quick to tell me that some part of my hardware is screwed up and it might be, but it seems strange that the problem is somewhat ROM-dependent.
I'd appreciate the help. Mainly, my goal is to get digiblur to work. If I could get it to charge it would be more top choice of ROM. That is, unless there is a way of keeping CM10 or 11 from ripping through my battery. Not an exaggeration, BTW, I get half the life on CM.
I'm relatively new to posting on XDA, but I'm not new to flashing ROMs. I had a OG EVO that ran CM7 until I upgraded. I'm a novice but a quick study.
Click to expand...
Click to collapse
Battery doctor has worked wonders for quickly/efficiently charging my zerolemon 9400mha as well as giving me options to save battery life and showing me the saving in minutes gained.
usb
my biggest issue is that when connected to a computer through usb it will lose connection randomly... then it will reconnect 1 second later and pop up on my computer as an "unrecognized" device
Enderend said:
I've been seeing the following problem on my Note II (L900): I plug it into the micro USB wall charger and the phone will not register that it is charging (no vibration, no change in battery icon, battery stats list "Discharging"). Sometimes this will change in a few seconds, other times it will take a minute or more. If I unplug it, the phone will tell me it's charging. It remains in this state a few seconds or more. Plugging in a second time will sometimes result in a quicker charging response (other times, not).
The problem first cropped up on a stock rooted MC2 build. It also appears on digiblur. CM builds seem to be immune as do some MK4 custom ROMs (no issue on Synergy or STS). It's frustrating because MC2 based ROMs seem to run best on the phone: great battery life, smooth performance and a lack of the nanny-ware that Samsung has added to the MK4 builds (I'm looking at you, high volume warning!).
Has anyone else seen this problem? I know that some of you are going to be quick to tell me that some part of my hardware is screwed up and it might be, but it seems strange that the problem is somewhat ROM-dependent.
I'd appreciate the help. Mainly, my goal is to get digiblur to work. If I could get it to charge it would be more top choice of ROM. That is, unless there is a way of keeping CM10 or 11 from ripping through my battery. Not an exaggeration, BTW, I get half the life on CM.
I'm relatively new to posting on XDA, but I'm not new to flashing ROMs. I had a OG EVO that ran CM7 until I upgraded. I'm a novice but a quick study.
Click to expand...
Click to collapse
Update: I may have found the source of the problem. I had a Titanium Backup nightly schedule that backed up all System and User apps. I switched to just User apps. My theory was that some system process wasn't being restarted properly after the backup completed. Perhaps related to the charge full notification? No idea. Turns out that my problem has seemed to disappeared since I made the change.
Very interesting that this issue seems to have be software and not hardware dependent. I'd love to hear a dev perspective.
Sent from a Huge Phone on @tingFTW
Enderend said:
Update: I may have found the source of the problem. I had a Titanium Backup nightly schedule that backed up all System and User apps. I switched to just User apps. My theory was that some system process wasn't being restarted properly after the backup completed. Perhaps related to the charge full notification? No idea. Turns out that my problem has seemed to disappeared since I made the change.
Very interesting that this issue seems to have be software and not hardware dependent. I'd love to hear a dev perspective.
Sent from a Huge Phone on @tingFTW
Click to expand...
Click to collapse
Okay, the problem is back. It is very infuriating. Here's another data point. When I am in TWRP, I can see that the device is charging ("Battery: 64%+), but not in the OS. Again, I would love to hear a DEV opinion on this issue.
troubleshooting
First things first. You need to positively identify the source of the problem as to either hardware or software. Try a couple different charge cables and chargers and note the results. I'm willing to bet it's your USB cable. I've had the same symptoms with what I thought was a mint condition SAMSUNG USB cable. Turns out they lose continuity inside the cable over time due to bending, pulling, etc. Test with a confirmed good Samsung charger & cable if possible. After you confirm your USB cable & charger troubleshooting then move on to the micro USB port itself. That's not easy to do but chances are it's one or the other. Being that you've flashed a few different ROM with same charging issue, I'm confident it's the usb cable or the port or both.
tx_dbs_tx said:
First things first. You need to positively identify the source of the problem as to either hardware or software. Try a couple different charge cables and chargers and note the results. I'm willing to bet it's your USB cable. I've had the same symptoms with what I thought was a mint condition SAMSUNG USB cable. Turns out they lose continuity inside the cable over time due to bending, pulling, etc. Test with a confirmed good Samsung charger & cable if possible. After you confirm your USB cable & charger troubleshooting then move on to the micro USB port itself. That's not easy to do but chances are it's one or the other. Being that you've flashed a few different ROM with same charging issue, I'm confident it's the usb cable or the port or both.
Click to expand...
Click to collapse
Thanks. I ended up replacing the USB board. It was cheap and surprisingly easy to do. So far so good. It's been really solid so far.
me either
same problem, after I unplug my usb wall charge, still battery icon has volt
and the status is charging.
cm12.1 rom, does the rom changes my harware?
how to solve this? please. tell me.