Hi,
I've searched for this and couldn't find anything so I'm making my first post. I'm familiar with flashing roms since my captivate. I flashed slim bean 2.7 onto my sgs3 from Rogers using cwm. Everything runs perfectly and I haven't experienced any bugs except this one. When my phone is powered off and I plug in the ac adapter, an empty battery icon flashes but never stays. I can't tell if it is charging or not as this icon will never update or come up again. While its plugged in, the phone will not boot at all. Once I unplug it, it boots up fine, sometimes going through 2 boots before launching into slim bean. Its not a big deal and i can live with it, its more of a concern if my phone battery ever dies. I was just wondering if this was a known bug or if I'm the only one noticing this.
Related
This only seems to be the case when I have the phone plugged in and charging: if I turn the phone off, naturally I get the battery charging icon in the center of a black screen. After this, the power button does nothing, even if I pull the charger from the phone. Further, the charging icon does not go away once the charger is pulled. At that point, I have to pull the battery from the back and put it back in to restart.
Anyone else experiencing this?
same thing is happening to me as well. are you using francisco's kernel running on stock? if no one else is experiencing this, it may be a specific app or kernel thats not playing well with our devices
I believe there are a few people are also having the same problem, so I don't think you are alone.
There is a new update being tested at the moment, apparently a major update and should hopefully address some problems (called 4.1.X). So let's hope that this problem is fixed with the update! (I have no clue what the actual update includes so I am only guessing here)
this seems to be a bug in the os, I had to do a battery pull when this happened to me
Sent from my Galaxy Nexus using Tapatalk
I have this exact same issue when I had Android Revolution HD rom installed with the modified kernel. After restoring back to stock the issue went away. But, I installed a maguro_ITL41F_rooted_deodexed.zip using CWM yesterday and this problem has reappeared. I'm pretty sure the zip included the stock kernel though so this may be an ICS problem.
I installed JB on my GN. Everything is running fine. But I notice some small problems :
1. When the phone turned off and I plug in the charger, it freezes at the battery icon [The icon with lightning, not the one flashing] , and I can't turn it on unless I take the battery out.
2. Sometimes the battery does not clear history after charge.
Is there any solution ?
UP!
How to fix it ? It really annoys me.
Sounds like something is not right with the upgrade, maybe odin back to stock ics and let the jb ota come through again
Sent from a phone...
Does anyone else's phone refuse to boot while charging? Whether I press power or hold it until it vibrates, no matter what my phone returns to the charging indicator and will not boot while plugged in.
johnnycs said:
Does anyone else's phone refuse to boot while charging? Whether I press power or hold it until it vibrates, no matter what my phone returns to the charging indicator and will not boot while plugged in.
Click to expand...
Click to collapse
true story, doesnt work for me either. thought my phone broke the other day because of this, until i tried booting the phone not plugged in.
Mine boots fine. Could be a ROM issue, that happened before with a specific ROM I was using but went away when I switched.
Sent from my SGH-T999 using Tapatalk 2
I think it's a Touch Wiz thing.
Sent from my SGH-T999 using xda premium
Battery Loop
Hello, This happen to me last night.
I've been using the CM10 nightlies, no problems...
I pulled the battery last night (was in the middle of an event and wanted to make sure it wouldnt suddenly ring).
Never woke back up. Plugging it into the charger just vibrates, shows the battery with the spinner for a split second and then again, and again and again in a loop.
Every now and again through removing USB charger/plugging in at the right timing (or resetting from download mode) I get the samsung logo, and a brief flash of the SIII logo...
I've flashed stock with ODIN, same deal.
Is my battery borked?
The SG I used to function with no battery plugged in.
Any advice?
elrojo said:
Hello, This happen to me last night.
I've been using the CM10 nightlies, no problems...
I pulled the battery last night (was in the middle of an event and wanted to make sure it wouldnt suddenly ring).
Never woke back up. Plugging it into the charger just vibrates, shows the battery with the spinner for a split second and then again, and again and again in a loop.
Every now and again through removing USB charger/plugging in at the right timing (or resetting from download mode) I get the samsung logo, and a brief flash of the SIII logo...
I've flashed stock with ODIN, same deal.
Is my battery borked?
The SG I used to function with no battery plugged in.
Any advice?
Click to expand...
Click to collapse
mine doesnt either. if i used to reboot it would stay on charging screen....NOW it reboots but if its off and i turn it on while charging it wont boot unless i disconnect it then wait a second for boot then plug it back in......I got the ability for it not to get stuck in the charging mode via reboot after using TRINITY's new kernel....so i wonder if its kernel based?
I now this is an old thread but...............
I have a Sprint Galaxy S3 and searched XDA for the problem I'm having which appears to be the same thing. Whenever I try to charge my phone with the battery off, I get the battery icon with the spinning thing and that's it. I never see the percentage, the LED doesn't light up, and I can't boot the phone unless I pull the battery. It's not a deal breaker although I could probably get another phone from Sprint.........or maybe even a new battery. Did anyone find the cause or fix for this? Like I said, I'm on Sprint and running Free GS3 with ktoon's kernel. Definitely doesn't seem to be carrier, ROM, or kernel based.
I was on wicked JB rom and ktoonez kernel and i noticed the issue. Odin backed to stock ICS H2 and it went away.
I'm using a T-Mobile Samsung Note 2 w/ Gummy Nightlies installed currently
Gummy: M3.0-09-02-14-NIGHTLY-t0ltetmo
The problem I'm running into happens consistently but not at predictable intervals. When the phone powers on, every so often while I'm using the phone, whether it be using the internet, browsing through Instagram or Twitter, or just scrolling through the apps my phone will perform a soft reboot.
I've tried multiple ROMs, stable releases, ROMs that aren't CM11 based, nothing seems to fix this issue.
Can anyone shed some light on what might the problem be and possibly a fix?
I'm not sure what else to include that might help anyone with diagnosing the problem, but if there is something that I forgot, I could definitely get you that information.
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Coug76 said:
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Click to expand...
Click to collapse
It hadn't happened on TouchWiz ROMs, but this just started happening about 2-3 weeks ago. I havent used a TouchWiz ROM in months. I've gone from OmniROM to LiquidSmooth to PacMan, to the most recent Gummy. From what I can remember its happened on the two latter ROMs.
It's strange because, I've called T-Mobile to have them send out a replacement battery, I figured that was the issue. I've had no issues with soft reboots while the phone was plugged into the charger, only when unplugged.
T-Mobile decided to just send me a new phone, so I reflashed to stock and im using my phone to send this message with no issues. So maybe AOSP problems?
What can I do to fix this?
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Coug76 said:
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Click to expand...
Click to collapse
The funniest thing just happened, it did it on the stock Firmware. My best guess would still be the battery. Good thing T-Mo sent the phone via Priority Next Day Air. I'll have it some time tomorrow
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
_lolzack said:
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
Click to expand...
Click to collapse
Did the new battery work?
I've got a similar issue ...
I was running Liquid Smooth 3.2 (4.4.4) with TWRP v2.7.0.1 and up until about a month ago, my 2 OEM batteries worked fine.
I was going to head out for the night, so I swapped to battery #2, it went into a boot-loop.
I thought it was a ROM issue, so I reflashed the ROM and still had the boot-loop, even after charging the battery to 100%
It wasn't until the next morning that I re-installed battery #1 and the phone booted fine.
Every time I swap to battery #2, the phone goes into a boot loop.
I ordered another OEM battery from Amazon and the phone goes into a boot loop as well.
The battery contacts on the back of the phone look fine.
I used the following procedure to delete the battery stats and it didn't help:
http://forum.xda-developers.com/showpost.php?p=38500258&postcount=8
I also switched to the JEDI Open Source Project (4.4.4) ROM and only battery #1 works.
I just removed battery #1 from the phone with it plugged into a charger and it remained powered up. I then installed battery #3 and it worked fine. When I rebooted the phone it went into a boot-loop again.
So, hello, guys. As the title says, my S2 keeps shutting down upon boot. When I turn the phone on, it goes to the splash screen, then to the boot screen, the screen darkens, then my phone abruptly shuts off with no warning. It never loads the home screen or the lock screen.
When I power my phone on while it is plugged in to the wall charger, it goes through the process perfectly. I am able to access everything perfectly. After I plug it out, then my phone will work fine for approximately 2 to 4 mins, then abruptly cut off despite what I am doing. This does not occur if I put the phone to sleep; only while the screen is on.
Can anyone give me any assistance? I've tried switching roms, from the stock rooted VM jelly bean 4.1.2 rom, to the Not Now V3 rom, to Slim Bean v7/v8 4.2.2 rom, Commotio B64, Vanir: the problem persists. Even now, I'm running CM11 (Feb 8th nightly), and I've even formatted my data and sdcard0 through CWM, nothing is working. Can anyone lend a helping hand, please?
Sounds like a bad battery.