Ok so I searching the immediate forum section and discovered that I have an issue that is slightly different from the rest.
When I flash any custom ROM's that have any AOSP components, my phone stops charging when turned on, even with a stock kernel.
This includes Project AOSP, which is a TW based ROM that then replaces a lot of the stock apps with the AOSP counterparts. I have done a significant amount of testing and the puzzler is it's only with AOSP based or with AOSP components on top of TW.
I then have to pull the battery, let the phone sit for up to an hour, and try it. If that doesn't work, I have an external charger I toss the battery onto to get it kickstarted so to speak and then after awhile of that it will charge, but sometimes it doesn't work either.
It's not the cable as I have several different ones and I've tried this at home, at work (using standard Samsung AC adapter), in the car, and on my computers. I'm confused as to why this is happening, and it has been going on for several months as I've been trying to get an AOSP ROM on my Note 2.
I've heard about this IC Charging issue, and I'm not sure what that entails as the information is varied. I'm not on Sprint technically, I have Ting as my carrier but it is an L900.
Looking for advice on what I can try to do to solve this issue. I was running Synergy ROM for several months until it became an almost daily issue. I then reverted back to MC2 rooted that I pulled from rwilco12's site. I have TWRP installed. Also I had it locking up after flashing MC2 and reflashing TWRP. In TWRP it would freeze requiring a battery pull.
I'm really not looking forward to having to replace this phone as this would be my second Samsung phone within a 1 year period (first was an S3 that went bad on me) so anything I can do to alleviate or completely fix this would be awesome.
Final ultimate goal: get a working AOSP ROM on my phone. Alternative goal: get my phone to reliably charge on a daily basis at home instead of me needing to go to work to charge it.
Edit: More information. I downloaded the charger checking app for the Galaxy devices and on a different charger it had radically different numbers. So I was able to charge using that charger for a couple of days without any problems. I loaded Project AOSP and it too was working just fine. As of last night however it now refuses to charge at all and when turned off recognizes the cables and shows the battery icon, then it stops and turns the screen off.
Sigh. Going to keep at it.
Ok well the update I do have is this: The charging issue only happens when using anything AOSP related, including Project AOSP (which is Touchwiz based, but looks/feels like AOSP).
But when I use my external charger for 3-4 Days and my spare battery, it then decides it will charge via the phone and it works for a few days then it sometimes won't start charging right away will take awhile to kick in. Then usually the day after it stops charging again.
So I think what I'm going to do is look into getting a new phone, probably a Nexus 5 this time around and see if the Note 2 works when totally stock, no rooting or anything. If it does, then I will sell it and put that money towards a tablet. Otherwise I'll just hang onto it and find a use for it somehow, or keep it as a spare.
Related
Ok here's the rundown:
Found out about the fast charging feature of Franco's kernel.
Flashed Winner's build onto my phone.
Flashed Franco's Milestone 2 build
Purchased/played around with multiple fast charge togglers. Decided to just let Tasker do it when the phone went into car mode.
Tasker did a good job of turning on fast charge but was sloppy in turning it off.
Several days later while playing GTA I had to plug it into my computer, fast charge was on. Shortly afterwords my niece and daughter get into a fight and I put my phone down, break up the fight and take my daughter outside to calm her down (She's 14 months) forgetting about the phone.
Phone sits on the computer's USB for about an hour maybe hour and a half.
Come back, it's at about 86% realize fast charge is on and turn it off.
That night the phone won't charge.
Now, here's what I have figured out.
Phone will charge in a powered-off state.
Phone will usually charge after a battery pull.
Phone will not connect to Windows 7 machines or XP machines except to charge when off or after a battery pull. (Device not recognized, latest Samsung drivers installed)
Phone will not connect in recovery mode.
When the phone does not charge it does maintain the current battery level unless I'm using up more battery than it can replenish.
Flashing multiple roms doesn't work.
Re-flashing Franco's kernel doesn't work.
Manually entering fast-charge commands doesn't work.
Oh and when I say it doesn't charge that is on either AC or USB.
I'd send this thing back to Verizon but I can't stock and lock it.
I would guess there are at least 20 threads here with this exact issue.
Yea, sorry about that. I did look around but besides 1 or 2 threads of people doing the usual rom swapping and just going out to get a new phone. I just wanted to start a thread for real diagnostics of this problem.
Oh yea, I also found the phone while plugged in will maintain the charge on the battery but will not actually charge the battery. Next time I'm in the car I'm going to see if the charge script will enable fast charge (Maintain) off of a USB connection.
This is the real thread: http://forum.xda-developers.com/showthread.php?t=1427539
I did read that thread, I don't think that is the same problem I'm having. I actually had that issue before (Shorted contacts) and had my previous Gnex warrantied.
To tell you the truth this will be the last samasung phone I'm ever going to get. Samsung is great on glitz but short on substance. My previous i760 was the same story. Fantastic out of the box but once it was 4 months old it was a royal pile of junk. It's pretty bad when you send the things into warranty enough to where the call center people get to know you by your voice. We currently have 4 of these things in the enterprise I have had to call in on them 6 times already.
Edit: well **** on a stick, it is related. Good I can continue ranting on the absence of the 3 pin dock(s) with more vigor than before. Now off to Ebay to find a replacement charge board.
I know, Samsung has not handled this problem well. I have read threads where they claim water damage on this exact issue, and refuse to fix the problem under warranty. After so many issues with it, they REALLY should have fixed it under warranty.
After having this issue twice, and after replacing my USB charging board twice I know that you have the same issue in the sense that it is the USB charging board that it failing.
You really should star/comment here if you have not: http://code.google.com/p/android/issues/detail?id=23789
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
Been coming here a while.. forums are nothing new to meh.. we'll skip the fact I just made this account and immediately made a thread ^^;
We'll get right to the details:
Had her since Autumn last year. Best phone I've ever used. No problems besides freezes I know I caused, etc.. never an issue. Til about October this year. Seen similar issues, looked for two months and found nothing close besides a Nexus 7 that physically needed its battery pulled for it to power on again. Anywho, here's how the moment went down: In the span of an hour or so, my GNex had crashed on me about three times... normally it'll do that maybe three times a day to three a week, depending how hotplugx on leankernel felt that day (having only one core on 90% of the time was pretty sweet). Was running the PA 3.99 based "Built With Love" ROM- the first build to incorporate any Saber stuff afaik- and the flat out 8.0 version of leankernel. Now.. the laast time she froze, the battery was already near dead, so when I popped it back in I plugged it up to the charger. All going as normal, right? Done this plenty from tinkering with kernels and seeing which android ROMs & versions I could hop back and forth to without wiping (had the current said setup for a month straight, surprisingly) Nope. It brings up the charging logo with the lighting bolt in the middle of the battery... and freezes there. Pulled out the cord, waited a bit and everything. Nada. Freaked out, I popped the battery. Went to put the battery back in and power it.. nothing. Okay, maybe that just killed the charge. Nope. Power cord fails to bring up any kind of light or charging animation. No screen activity. Will not boot into odin, recovery, or anything.
The ONLY signs of life still coming from this phone, are heat when it's on the charger, heat after 'USB jumping' the phone -after disconnecting the cord as well, and for at least two hours it continues producing heat- (had to do that when I first got it from Google) , and if I plug her into the laptop via USB WITHOUT a battery, it'll show as "OMAP 4440" for a split second in device manager.
Any more details will come from answering questions. As this happened over two months ago, I'm a little fuzzy on outright recalling details.
Cannot find this problem elsewhere at all. Either it's rare or I suck at looking around.
So I'm coming to you guys. Is she bricked? Stuck in charging.. idk what. Toolkits won't detect a device either, even after the USB jump when I know the battery is discharging and the phone is -technically- powered on.
If you guys could help me out for Christmas, even if it's to tell me she's busted, it would be so indescribably appreciated... <3
[Edit] Nabbed this really quick (attachment). Holding the button combo for download/odin mode has Windows searching this.
No battery inserted, as the dialog disappears and the taskbar pops with a bubble saying "device not recognized" etc. when the battery is put back in or is simply in it when plugged into the laptop.
Also to note: a third party battery yields the same results as the stock one. What kills me is Windows can see it, but aside from that and the heat production, it's essentially dead. What gives? :c
Shameful bump. Need to know if it's completely bricked, or possibly a hardware issue that's repairable or not.
Had to save up for over a year for this phone. Really need to figure out if it's gone or not. If it is, then I'll need to start saving for an N5, which I consider a downgrade ._. Can't beat the community support though, and that extra screen space :3
Aside from irrelevant blabble.. any answer would be appreciated. I can provide any additional information if need be, as well.
Have not seen this issue anywhere.
Bump..? :c
There's almost nothing on charge animation freezes. And what there is, the owner was able to boot their device with some simple workarounds.
If there's anyone who knows what's going on, even to tell me I'm a retard who bricked his phone, please do. Please.
Can't even afford glue to put my shoes back together. Saving up for another phone is impractical this year and probably next as well :\
Would I need the OMAP 4440 driver and some other stuff? If there's some way to push a boot.img to /boot while the phone is in this state, that would fix it..
I'm somewhat sure, at least. Since the kernel's in charge of that from what I understand.. any ideas?
Search for OMAP flash. I think your phone can be revived. i can't search right now but i believe there are some tutorial about OMAP flash of galaxy nexus. Good luck
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.
I'm having issues with this POS phone that I can't understand. If I use any charger at all, including the provided charger and cable, it used to say something about slow charging and that I should use the stock charger. Now it doesn't even bother warning me 99% of the time, it doesn't even give me a time til complete on the lock screen.
I'm at stock everything and fully updated on the t-mobile version of the One M9.
If I factory reset the phone it charges for a couple weeks but does the exact same thing. I've already had this phone replaced once for the same issue, the replacement behaves exactly the same way. I've used custom roms, deleted apps like facebook, and tried keeping the screen brightness all the way down. Absolutely nothing has helped for more than a couple weeks. Right now it's on extreme battery saver and has been sitting at 27% for 30 minutes. I've also looked into the battery optimization option in the settings and that literally does nothing at all. If I enable it it'll just sits there doing nothing. If I exit and come back it's switched back to disabled.
These are just a couple of the more pressing issues right now, I've had nothing but problems with this horrible phone since I bought it. And I used to love HTC. I've had 5 HTCs, a bunch of Samsungs, an LG, and a few generic Android devices. None have been as bad as this thing. Worst camera I've used since 2009. Slowest boot time, except for the generic tablets. App install times are easily three times longer than any device I've ever used. Oh, god, and updating is always at least an hour long process. I just don't understand how their quality dropped so far in just a few years. Anybody have any tips or ideas as to what might be happening or should I just cut my losses and get another Galaxy?