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.
Related
I can't turn on the device while its plugged in and charging while its turned off. I would have to take out the batteries everytime. Is this a bug or is it suppose to be like this?
Sent from my Galaxy Nexus using Tapatalk
i have the same problem with all coocked rom but no with stock
i can turn it on... just hold the power button for a few seconds.
melterx12 said:
i can turn it on... just hold the power button for a few seconds.
Click to expand...
Click to collapse
Tried holding it for 2 minutes yet nothing happens. Don't think it is rom problem?
Sent from my Galaxy Nexus using Tapatalk
Good thing I read through this q n a, I'm going crazy too. When I power off (to reboot after installing tons of apps, to refresh etc.) I get the battery charged icon and freezes there. Only battery pull works. I'm on Android Revolution 2.1.0 unlocked and rooted. I guess bug? Annoying, feel like I'm going to tear the cover every time and damage the screen
This happened to me too, and the battery charging icon caused burn-in. Fortunately, it went away after a day or so.
Same bug here. We'll have to hold tight and wait for a fix or run stock.
On my Fascinate you could hold the vol up and power button to get soft boot the phone, but the GNex does not seem to have this feature. I hate pulling the battery.
Same issue for me ... I think we have to open a bug tracking. This is a very annoying problem.
Android 4.0.2
Kernel 3.0.8-gaaa2611
Since my phone is new to me I wanted to power down and get a full charge.. but I can report this bug as well. /cry
Did any of you use a different rom prior to ARHD? I wonder if its something in the kernel or the OS. What allows the phone to show that animation when turned off? That could hint at what modification breaks offline charging.
I have this problem too running a revolution rom. The phone charges fine but I have to pull the battery to boot up. It's a strange one!
does this happen to stock rom? the one shipped with the phone?
zeke1988 said:
does this happen to stock rom? the one shipped with the phone?
Click to expand...
Click to collapse
No!
The bug happens with custom roms. Infact I went back to the stock rom and (even if rooted) I can charge the phone when it's turned off without having problems.
I am certain the phone still charges to 100% but it appears to be frozen. The only way to boot back up is a battery pull.
Any more info on this from anyone? I saw a 4.0.3 rom yesterday that claims to fix the issue so maybe that's the way forward.
Same here, on bigxie's ROM, if I try to boot with phone plugged in from being dead, freezes right at battery charging icon, have to battery pull. Very annoying.
just4747 said:
Very annoying.
Click to expand...
Click to collapse
I agree.... infact I will not use custom roms until the bug will be closed!
This seems to be more prevalent in 4.0.3 roms. I have a deodexed 4.0.2 rom from bigxie which charges just fine when powered off. However any 4.0.3 rom will not let me charge while off.
Not sure if it's an unintented bug but we'll have to see when the full update hits gnex officially.
ihyln said:
This seems to be more prevalent in 4.0.3 roms.
Click to expand...
Click to collapse
I don't think so. I had the bug in a 4.0.2 custom rom
Fixed in 4.0.3 ROM/Kernel.
RMatt1992 said:
Fixed in 4.0.3 ROM/Kernel.
Click to expand...
Click to collapse
what and where? GSM usually doesn't apply to us CDMA/LTE users especially if it's a rom/kernel issue.
Might be related to a custom recovery. Do you guys all have ClockworkMod in common? I have a stock recovery and don't have such problems.
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.
So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?
I agree with your assessments.
I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app
what's your setup as of right now?
Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%
It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki
Hello guys,
I tried to search for a similar issues but I couldn't find anything similar so please bear with me.
My KF sometimes shuts down overnight. In the morning then I have troubles to switching it on again (clicking the power button, holding it for longer periods of time...). It usually helps for the tablet being connected to the charger, but it takes a few tries to turn it on. After I managed to turn it on again, for example yesterday, it had 80% of battery left.
I am using CM nighties and this is happening already for some time.
I am also using juice defender, I am not sure if that is relevant.
Do you have any suggestion, what could be the cause of this? Maybe a suggested alternative rom? Or some logs I can check? I think the powering on troubles bother me more than the shutting off overnight since I always think it won't come back on anymore.
Also, not sure if relevant. If I try to turn it on and it doesn't, sometimes the button flashes orange. After a few tries it turns green and powers on. Not sure if I am now not only confusing times, when it was simply out of juice.
P.S. On a different note, just curious, does anyone know how if there is a rom with working mic already?
Thanks in advance.
jkb
Yes, I sometimes have the same issue with the power button - in fact it happened to me this morning where I went from about 60% charge to 16% with a sudden power drop.
Not sure why this happens. I thought it was a bad battery so I changed it but am still getting the problem every now and then.
Sent from my Nexus 7 using xda premium
the only thing that i can think of is that during the middle of the night a soft-reboot happens and it cant boot back up into the system. this would cause it to sit there and continually try to boot up. this would use a lot of cpu and a lot of power. as for why that drains battery while being plugged in, well i cant help you on that.
Thanks for the input. I've wiped dalvik, cache and the system and installed hashcodes AOSP Jelly Bean (http://forum.xda-developers.com/showthread.php?t=2041694) and at least it survived this night without shutting down so maybe this helped. If I come across the same issue, I will update this thread with new info.
Thanks again,
jkb
Check this out:
amazon.com/gp/help/customer/forums/kindleqna/ref=cm_cd_pg_pg139?ie=UTF8&cdForum=Fx1GLDPZMNR1X53&cdPage=139&cdThread=Tx2JSJNEOWHGOIT
Sounds like a hardware issue, and Amazon has been replacing those of customers who buy new from them.
Mine has this issue too. I KNOW it has battery power, and is still on, but the screen won't turn on. Only solution is to plug in power, then hold down the power button until it shuts down hard. Then turn back on.
I'm returning mine because of it.
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
jokob.sk said:
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
Click to expand...
Click to collapse
Try going to the WiFi settings and selecting 'never' for keeping WiFi on during sleep. This seemed to work for me.... So far it hasn't happened again.
Sent from my Nexus 7 using xda premium
I think this is the bug I am experiencing:
Shutdown bug stalls out the shutdown. Looks like the device is off, but it's still powered draining battery. Currently requires long power button press to fully shutdown after the screen is black (about 15-20 seconds).
from the 3.4 kernel thread (http://forum.xda-developers.com/showthread.php?t=2264563). I am not sure if cm 10.1 nighties contain this kernel, but the description is pretty much spot on.I couldn't test the fix (holding the button for 15-20 seconds), since I already changed roms, but if someone experiences the issue again, he can post if this works and which rom and kernel they are using.
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
pwrdbykimchi said:
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
Click to expand...
Click to collapse
Yes, it happened again to me with the same ROM, but it happens less often. I will try the updated kernel once it is finished.
On May 27, 2013, Hashcode listed the known issues of the current kernel on his website:
Sound / MIC debugging
Deep sleep issues with “omapdss_dpi” device
SmartReflex shutdown loop fix.
Charging driver / OTG improvrments
Click to expand...
Click to collapse
Looks like they've been identified and are being resolved. :good:
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.