[Q] KF2 battery problem after CM10 install

[docnougat]

Hi, new here but I've been lurking for a while.

I followed Powerpoint's guide to instal CM10 on my KF2
http://forum.xda-developers.com/showthread.php?t=2105077

Everything was running great and has been since I first loaded version 3 a few weeks ago, and last week i went to version 4 of powerpoint's rom with no problems. Then a couple days ago after i had been browsing the internet on it for maybe 30 minutes, I set it down and when i came back the screen was off and wouldn't turn back on. so i figured the battery was just dead, so i plugged it in to the wall charger. At first the charge/power light wouldn't come on at all. Then after several plugs and unplugs the orange light started to come on but would only stay illuminated for 30 seconds-ish. So I tried it on my phone charger and the orange light came on and stayed on, so i decided to let it charge overnight. The next morning the light was still glowing orange so I unplugged it and tried turning it on, but still nothing happens. But when I plugged it back in afterwards the light came on green. now it has been plugged in for almost a day with the green light on but it still wont turn on.

Anyone else have this problem? Any ideas what i can try? for obvious reasons i can't exactly ship it back to amazon lol

p.s. I have a final on friday and the text book for that class is on the kindle. So urgent responses will be greatly appreciated.

 

[docnougat]

Nevermind guys, I figured it out. Power button for 20 and it booted right up

Sent from my EVO using xda app-developers app

 

[chronicfathead]

Nevermind guys, I figured it out. Power button for 20 and it booted right up

Sent from my EVO using xda app-developers app

I've had this a couple of times on both 10.1 ROMs. As you stated the only way I got it working was to hold the power button for 20 secs, then power on normally.

Sent from my Amazon Kindle Fire2 using Tapatalk HD

 

[docnougat]

It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?

on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?

 

[iytrix]

It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?

on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?

Wow, for once I can completely and knowledgeably help with almost no guess work!

The issue is Sleep of Death.

The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.

It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.


TO FIX

You guys were right on fixing it mostly.

If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.

I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.

I would say....in a few weeks with the device, I've had the issue around 5-6 times.

I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.

 

[docnougat]

agreed, if it was happening while i was trying to do stuff it would be problem. As it is though, I just consider it a minor inconvenience. Glad to know I'm not the only one experiencing this though.

 

[fmkilo]

Wow, for once I can completely and knowledgeably help with almost no guess work!

The issue is Sleep of Death.

The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.

It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.


TO FIX

You guys were right on fixing it mostly.

If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.

I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.

I would say....in a few weeks with the device, I've had the issue around 5-6 times.

I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.

I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..

 

[chronicfathead]

I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..

I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.

Sent from my Amazon Kindle Fire2 using Tapatalk HD

 

[fmkilo]

I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.

Sent from my Amazon Kindle Fire2 using Tapatalk HD

or you could have kmsg being written to a file during it...
the hard reset (power button for 20s) clears memory