Develop Bugs

Bugged when device is charging and off?

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.

Phone keeps crashing

When charging, my phone works fine, but when I unplug it, it crashes within a few seconds. If I turn it on without pluging it in first, it boots, and a few seconds after fully booting, it shuts off.
Phone is rooted and I'm using the IceColdSandwich ROM, always on the newest test build.
Help me please, this is really annoying
Sent from my Microwave using Tapatalk

Help, please.
Sent from my Microwave using Tapatalk

I have a similar problem - but its imho ROM independent. I left my phone in direct sun for about 30 minutes and the phone was afterwards wery hot and it crashed...
No I can run the phone only, when the charger is plugged in. Without charger attached the phone shut down in 5 - 20 seconds. I think, the extreme temperature demaged the battery. Unfortunetaly Im in Mexico right now and Im unable to buy another battery, to verify my hypothesis.
Its very likely battery related, bacause after every higher energy drain - flash light or similar it crashes even on charger...
Any ideas - suggestions or similar problem? Thx.

check for battery pins bent if they are ok try changing the rom like cyanogen as they are very stable if issue still there replace ur battery with a new one.

had the same...
i had the same problem and when I tried Ascension ICS, never had crashing issue since lastweek....but....it is starting to act weird this morning...not good

XoXFaby said:
When charging, my phone works fine, but when I unplug it, it crashes within a few seconds. If I turn it on without pluging it in first, it boots, and a few seconds after fully booting, it shuts off.
Phone is rooted and I'm using the IceColdSandwich ROM, always on the newest test build.
Help me please, this is really annoying
Sent from my Microwave using Tapatalk
Click to expand...
Click to collapse
Check the health of your battery. There are battery monitoring apps on the market that can do this.
Do you charge using a wall charger or USB port on your PC? The phone cannot run by itself using wall power or USB power and needs the battery to function.
I have a feeling it's the ROM. Can you try a ROM based off an official RUU? Or maybe revert to a stock ROM? Or you could full-wipe your phone and reflash Ice Cold Sandwich.

Hi guys, thx for replies.
In my case its 99% not ROM related - yesterday I tried around 5 custom ROMs (gingerbread and ICS), flashed another recomended radio and RIL and finaly reverted to stock... still the same problem - reboot after several seconds or minutes...
Unfortunetaly Im unable to replace the battery, to see if its battery-related or not.
Regard Pylorus

Problem Solved
After returning back home, I replaced the battery with a new one and the phone works flawlessly again... so voila, problem solved

pylorus said:
After returning back home, I replaced the battery with a new one and the phone works flawlessly again... so voila, problem solved
Click to expand...
Click to collapse
same here ^^

[Q] Energy ROM Battery Question

First, I'd like to thank the DEV for the Energy ROM. I've run the last two releases and it is truly spectacular. The latest version with Hashcode's Kernel makes it a completely functional daily user (not that the SOD's in the last one made it any less amazing). I understand the battery issues associated with it, and have read through the workarounds in the DEV forum, but this issue seems to be beyond those. On any given day, I leave the house for work with a full charge and, even if I'm not able to use it during the day, I get home and am hovering around the 50% level. Not a big deal, but the last two days I've taken it a step further and did a hard power off before I left (held power for the 20s). When I got back 10 hours later and tried to power it back on, it was completely dead. First day I thought, just a fluke, maybe the power button got bumped accidentally. But two days in a row, while the KF was secured in a hard case, got me concerned. Is anyone else running into this sort of issue? This is by far the best ROM i've run on the KF, and tomorrow I won't bother to shut it down, but I'm curious as to what could be the cause. I'm running at the standard 1200/600 clock speed, but with it shut down, to my understanding I shouldn't see any significant battery loss, right? I'm definitely a noob when it comes to android, so if this is an issue easily remedied, I apologize up front. Thanks in advance for any help offered, and thanks again to all that made this ROM possible!

It's a known issue for older kernels (not sure about the latest one) that if you force the shutdown, it may sometimes turn on at random a while later - this is probably what happened, it turned on a while after you left it off, and then just ate through the battery during the day until you got back home.
If you have flashed the latest kernel, using the "normal" Shutdown option should work (not sure if the ROM would need to be updated or not) fine, so far I've never had it turn back on after using it, but I'm using Hashcode's ROM instead.
Otherwise, just reboot into TWRP and press "Reboot" - "Power Off", which will make it stay off... hopefully.

Thanks, I'll give it a try through TWRP and see what happens. FYI I'm running release #8 of the 3.0 kernel if that sheds any light on the problem
Sent from my Amazon Kindle Fire using XDA

I too had battery issues with EnergyROM... things seem stagnant there so I flashed gedeROM last night and so far so good.

psudeke said:
FYI I'm running release #8 of the 3.0 kernel if that sheds any light on the problem A
Click to expand...
Click to collapse
It'd be for the best if, at the very least, you flash kernel #10, as it allows for "normal" shutdown (ie, no need to go through TWRP or to force the shutdown by holding the power button 10-20s), though I'd recommend switching to Hashcode's ROM (better support, plus a few more ROM only features) instead, at least until everything slows down a bit.

Thanks for the advice. I'll take a look at his ROM as well. I thought about just flashing the #10 kernel, but i understand you lose some of the functionality of the kernel since the ROM isn't designed to take full advantage of it.
Sent from my Amazon Kindle Fire using XDA

[Q] Sleep of Death

I've read XDA for some time now but I'm not sure I've posted all that much since I can't post to the dev forms. Anyway, I just acquired a Kindle Fire and decided to put a ROM on it:
http://forum.xda-developers.com/showthread.php?t=1591850&page=213
I tried one from August and it worked well but the charge indicator didn't react to plugging it in so I found the 12/02 one and it was better but then I ran into the Sleep of Death problem. I decided to try a different one so now I'm back to 11/27-1605. I did a full wipe and used it all day with no issues. I left it for a few hours tonight, came home to it being dead. I did more searching and found something about CPU settings and the like so I've change that but I was wondering if there was a specific thread that I wasn't able to find directed at the Kindle Fire CM10 builds and this issue.
Any pointers for a KF noob?
thanks peterb

It sounds like the battery is dead. Try plugging it in, booting into recovery, and trying mounting the fire onto you computer as a flash drive. Then you can move a ROM like Jandycane over to it and flash it. Make sure you do a system wipe first.
Also, it might be a good idea to charge the kindle to 100% before copying over the ROM and trying to flash it.

jji7skyline said:
It sounds like the battery is dead. Try plugging it in, booting into recovery, and trying mounting the fire onto you computer as a flash drive. Then you can move a ROM like Jandycane over to it and flash it. Make sure you do a system wipe first.
Also, it might be a good idea to charge the kindle to 100% before copying over the ROM and trying to flash it.
Click to expand...
Click to collapse
It's not the battery because I can hold the button for about 10-15 seconds, release and then power it back up. Based on what I've read, it's the sleep of death issue. More reading lead me to mess with the CPU governor (setting it to performance) which seems to have helped out the snappiness of the device which is cool but it still got the sleep of death. More reading led me to SoftLocker Free. So far that seems to have taken car of things but will know more with time. I was hoping to find some feedback from folks who've run into this on the Fire and been able to fix it. I'll report back if this latest addition does indeed take care of it.
You mention the Jandycane ROM, is there a place to go to see the various ROMs are available? So far I like the ROM I've got as it's pretty standard Jellybean which makes it a lot like the N7's that my two kids have which is cool. I'd be interested in seeing what the other ROM's have to offer but so far my preference has always been for as vanilla a ROM or image as I can find.
thanks peterb

The sleep of death thing seems to be in the 4.1 kernel that Hashcode has been working on. He is the one that is working on getting us on CM 10. I believe Jandycane and SGT7 are both based on his CM10. That is why the sleep of death occurs on these roms. Once Hashcode gets more time, I'm sure he'll try to fix it. But until then... it is usually just a minor annoyance, at least for me. It is random, but does not usually occur all the time.
You could also try some of the CM 9 based roms, I believe there is also a MIUI rom based on CM9.
I am on the CM10 11/16 build. And it is usable most of the time. There are still a few quirks here and there.
Hope this helps.

With the softlocker free app installed the fire slept all night and woke up this morning as soon as the power button was pressed. So that seems to be the solution for me for now. If hash code gets it fixed that would be great but if this keeps working it's fine with me. BTW, thanks hashcode . The fire is great with this ROM.
Peterb

[Q] Anyone experiencing powering off and troubles switching it back on (charged)?

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: