Funky Behavior When Shutting Down ICS ROM's - Kindle Fire General

I've tried two ICS ROM's. CM9 Reloaded and CM9 Kang. When I shut down the screen goes blank but not completely black. It's slightly dimmed. In this dimmed state if I hit the power button once more it will turn completely off. The real issue is when I try to turn the KF back on, it won't power on. The only way I can get it to power up is to do the 20 second long press on the power button. Any thoughts? I am afraid one of these times it's not going to turn on.

I had the same problem thats why I went back to Modacos rom. I think its a kernal issue

Abbens said:
I had the same problem thats why I went back to Modacos rom. I think its a kernal issue
Click to expand...
Click to collapse
I have the same problems with most ICS rooms and would agree it's probably kernel related. I am hoping it will be resolved with hashcode's new 3.0 kernel
Sent from my Amazon Kindle Fire using XDA

Related

[Q] MT4G won't sleep with Sense

Hi
I have a rooted stock ROM/Theme MT4G which I noticed last week that it stopped going to sleep. If I set the timeout to 15 seconds (or anything) then right after the timeout is reached the screen sleeps and then within a second immediately comes back on (to the lock screen). It keeps doing that no matter what settings I try. This of course kills the battery life with my screen being nearly 100% of use.
I thought it was related to an app update so I removed nearly everything I could to no avail. Thinking that it was something related to the ROM I decided to try a different ROM. I installed CM7RC2 and low and behold the same problem persisted. I had to disable trackball wake for this problem to go away. I then tried several other ROMs and the problem still remained. I've attempted the various Royal* ROMs and the same problem persisted. Any Sense based ROM was problematic since I had no way of disabling Trackball Wake so I'm now running CM7 (nighties).
The other snag I'm having is that I too have the problematic power button but in my case I have to REALLY press hard to operate the power button which of course is annoying.
Anyone have any suggestions or experience with this sort of problem?
Thanks.
Did you check out the Cyanogen mod 7 in settings ?
I did. That's what I'm running now.what exactly are you suggesting? Thanks.
Sent from my HTC Glacier using XDA App
I have the same exact issue, ive been trying to get some devs to add the disable trackpad wake option in sense roms but so far nothing so right now i use either royalginger or royalmiui im on miui but i really miss sense :/
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Nicgraner said:
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah ive tried that be4 with no luck
Nicgraner said:
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Click to expand...
Click to collapse
I must have done that a bunch of times already but nothing worked except CM7 because I can disable the trackpad wake function. I wish Sense based ROMs allows for disabling the trackpad...that would be greatly appreciated. An even more helpful feature is the ability to remap the buttons.
Is it possible your trackpad is defective? DO you notice other odd behavior that could be related to it?
If your using google voice its the application doing that you can fix this on cm 7 by moving the application to the Sd card.
Sent from my HTC Glacier using XDA Premium App
I believe this is a real hardware issue... It seemed that the optical sensor in the trackpad is broken and it's always sending signal to the kernel telling that it detected activity but in reality nothing was going on, so the kernel can never go into power saving mode.
Sense UI is a CLOSED SOURCE software, there's nothing you can do to patch it.
Since ALL MT4G are still under the 1 year Manufacturer's warranty, you should call T-Mobile/HTC to get it fixed or just get a replacement....
Ok I found a solution for us mt4g owners with the messed up trackpads, you are gonna have to flash virtuous unity rom v. 2.39 and then apply this patch:
http://dl.dropbox.com/u/28766802/Virtuous/trackpad_disabled.zip
This patch was made by one of the developers of the rom chrisch1974 specially for this issue, so good luck =D
Same problem, but found work-around
My phone (MT4G) has the same issue but I know why it happened. I got caught in the rain and although I had the phone in my pocket, it got wet. Everything works except that. I left in a bag of rice overnight to no avail.
Anyway, when I press the power button to send it to sleep mode, it just comes back to the lock screen. If I let it time out, it goes out but comes right back to the lock screen. Sounds familiar?
What works for me is holding the home button (the one with the sensor) and, while still holding the home button, pressing the power button once. It is then that I let go of the home button.
Works, but sometimes I have to repeat this charade a couple of times before it sticks. Usually have to repeat it when I don't fully press the home button.
Anyway, hopefully this will help someone that is stuck with this phone and is unable to get a replacement.

Does your screen flash when you turn it off?

When I hit the power button to shut the screen off, it flashes brightly before it goes off.
Wondering if this is a Nook Color thing in general, or just a CM7 thing. Is this related to the fact that the screen animation doesn't work on CM7 when using the current kernel? I heard that Dalingrin had the screen animation working in the early test kernel and wondered if this got rid of the screen flash as well.
FWIW, mine flashes also. I haven't researched the cause, though.
CM7.0.2 from SD, when I tap the power button, it fades over about half a second. No flash, although occasionally there's a flicker in the middle of the fade. Power on happens much quicker, but there is a bit of fade-in.
I did enable on and off animations, even though I didn't think they were supposed to work yet.
this is a CM7 thing. its a power off and on animation. if you dont like it you can turn it off in settings. personally i like it. it reminds me of the old CRT screens.
boxcar8028 said:
this is a CM7 thing. its a power off and on animation. if you dont like it you can turn it off in settings. personally i like it. it reminds me of the old CRT screens.
Click to expand...
Click to collapse
More specifically it's a 2.3 thing - but I think the problem is that it doesn't work the same as on other standard resolution screens so it just ends up 'flashing' rather than doing a fancy animation. Your solution is correct though.
Interesting. The on/off animations are off by default in the Encore build. I enabled them in the settings and still had the flash (as one would expect). However, once I disabled them again everything was fine. I wonder if this is another persistence bug, similar to airplane mode?
My screen flashes whether the screen animations are on or off, though to be fair it doesn't flash every time, definitely more often than not though.
Mine is more of a quick blink rather than an obvious flash. And it isn't consistent.
My screen flashes as well. It just started doing this yesterday and I've been running cm7 off my sd card for about a week with no other problems. Worse, sometimes the screen turns green and stays that way until I hit the N button. Any idea what this means and possibly how to fix it? Any input would be greatly appreciated. Thanks.
FairJuno said:
My screen flashes as well. It just started doing this yesterday and I've been running cm7 off my sd card for about a week with no other problems. Worse, sometimes the screen turns green and stays that way until I hit the N button. Any idea what this means and possibly how to fix it? Any input would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Which version of CM7 are you running? I haven't seen the flash or the green screen since I switched from 7.0.2 to nightly 86. Maybe it's coincidence, but it looks like the flash issue has been fixed.
(The power button does sometimes turn off the screen briefly then turn it right back on again -- hitting the power button a second time always turns it off.)
akaCat said:
Which version of CM7 are you running? I haven't seen the flash or the green screen since I switched from 7.0.2 to nightly 86. Maybe it's coincidence, but it looks like the flash issue has been fixed.
(The power button does sometimes turn off the screen briefly then turn it right back on again -- hitting the power button a second time always turns it off.)
Click to expand...
Click to collapse
It's the CM7.0.3 stable version. Maybe I should do an update. I wasn't sure if that was the problem since it had just started doing this. Are you saying you've seen the green screen? Just curious because I can't find anything about it anywhere. Thank you for your response. I'm going to try out the nightly and see if that fixes the problem.
Mine does more of a quick flicker,i think its the screen off/on animation issue on the nook because the animation works fine on my droid incredible cm7
GreenXSniper said:
Mine does more of a quick flicker,i think its the screen off/on animation issue on the nook because the animation works fine on my droid incredible cm7
Click to expand...
Click to collapse
Actually, that's what mine does too. Sometimes there's a flash, but most of the time it's a quick flicker. If it's just the animation then I probably don't need to worry about it. It's just the green screen that worried me...though that only occurred when I kept messing with it. I haven't messed with it the past couple of days so I haven't seen the green screen. Maybe I was causing some kind of error.
FairJuno said:
It's the CM7.0.3 stable version. Maybe I should do an update. I wasn't sure if that was the problem since it had just started doing this. Are you saying you've seen the green screen? Just curious because I can't find anything about it anywhere. Thank you for your response. I'm going to try out the nightly and see if that fixes the problem.
Click to expand...
Click to collapse
Yup, I've seen the green screen. I don't remember what build I was on at the time because I looked at a bunch over a couple of days. It could have been 7.0.3.
Or maybe I messed up something on my nook, and flashing another build corrected it? Either way, I haven't seen it in a few weeks.
akaCat said:
Yup, I've seen the green screen. I don't remember what build I was on at the time because I looked at a bunch over a couple of days. It could have been 7.0.3.
Or maybe I messed up something on my nook, and flashing another build corrected it? Either way, I haven't seen it in a few weeks.
Click to expand...
Click to collapse
That's good that you haven't seen it in a while. And not that I want anyone else to suffer, but I'm glad I wasn't the only one. LOL. Hopefully that means I'll have an easy fix. I haven't seen it in a few days myself, so I'm just going to wait and see what happens. Most likely I'll update to a nightly. Thanks for the responses. Now I'm not worried about it anymore.

Problem: Can't unlock Phone (Random issue)

Hi, i got a problem with my S2. Sometimes, when locked, the phone can't be unlocked. The screen stays black and nothing happens. I thought it had shutdown and tried to boot it, but no answer from any button. Only thing that works is keep the ON button pressed for 10 seconds forcing the reboot, or remove the battery and put it again.
I'm using Criskelo V15 and T39 Speedmod Kernel. Other users in another forum are expierencing the same issue with different roms. I'm also using Green Power that i just uninstalled to see if it has any effect.
Any idea? Could be hardware related? It only happens when the phone is locked.
Thanks for any advice.
The processor in your phone might not work well with speedmod. Could be too low of a downclock in sleep mode or something. I'm not familiar with what speedmod specs are but I would try a different kernel. All CPU's have different reactions to speeds lower or higher than stock. I had an old HTC Hero that would have wake issues on certain kernels/clock settings.
PhoenixG said:
Hi, i got a problem with my S2. Sometimes, when locked, the phone can't be unlocked. The screen stays black and nothing happens. I thought it had shutdown and tried to boot it, but no answer from any button. Only thing that works is keep the ON button pressed for 10 seconds forcing the reboot, or remove the battery and put it again.
I'm using Criskelo V15 and T39 Speedmod Kernel. Other users in another forum are expierencing the same issue with different roms. I'm also using Green Power that i just uninstalled to see if it has any effect.
Any idea? Could be hardware related? It only happens when the phone is locked.
Thanks for any advice.
Click to expand...
Click to collapse
best thing to do is go back to stock rom and see if the problem persists..if it does then uh oh!
Still covered by warranty?
I'm covered by warranty. I've uninstalled Green Power to see if the problem persists. If so, i'll comme back to a stock ROM and see. But i'm reading in other forums that it may be Hard related.

Nook Color Won't Turn On

So I got my Nook Color a couple of days ago. I've been using CM7 off the SD card, but when I just went to turn it on nothing happens. I took the SD card out, still a no go. I even tried using a cwm from sd card thing, nada. The Nook doesn't turn on at all. any ideas?
Try plugging in the nook and leaving it for a little while. Sometimes that helps it reset itself.
Try holding down both the power and the nook button simultaneously for awhile untill it reboots sounds like the sod (sleep of death) hit you. Google it!
Sent from my NookColor using Tapatalk
Have you tried rebooting your Nook? Hold the power button for 10 seconds or so, then release it and hold it again for a couple of seconds until the screen flashes white.
I just left it alone for a while and when I picked it up a few hours later it came on. It happened again today, I turned off the screen for a minute, went to turn it back on a and nothing happened. Just a black screen. Interestingly, it was still running though, because when I hit the volume keys the tone sounded. I just held down the power button till it turned off and then turned it back on and it booted right up. Any ideas what could be causing this?
Edit: I forgot to mention I'm now running CM7 from internal memory, so its not just instability from running it from SD
JustisLewis said:
I just left it alone for a while and when I picked it up a few hours later it came on. It happened again today, I turned off the screen for a minute, went to turn it back on a and nothing happened. Just a black screen. Interestingly, it was still running though, because when I hit the volume keys the tone sounded. I just held down the power button till it turned off and then turned it back on and it booted right up. Any ideas what could be causing this?
Edit: I forgot to mention I'm now running CM7 from internal memory, so its not just instability from running it from SD
Click to expand...
Click to collapse
Read the other posts its called Sleep of Death
Sent from my NookColor using Tapatalk
koopakid08 said:
Read the other posts its called Sleep of Death
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I was under the impression that in sleep of death the nook is inoperable, ie the volume keys wouldn't work. Is that inaccurate?
JustisLewis said:
I was under the impression that in sleep of death the nook is inoperable, ie the volume keys wouldn't work. Is that inaccurate?
Click to expand...
Click to collapse
No, for some odd reason sometimes you can hear sound and the volume keys will work. Nothing else will.
To fix SoD: set up two profiles in tasker. One for wifi off when screen is off and one for wifi on with screen on.
Sent from my LG Optimus V using Tapatalk
tasker fix, good to know, had this happen the other day to my nook
Glad I came across this thread. I updated my ROM to CM7.1 earlier this week and have been enjoying it. Came home today and couldn't get my nook color to turn on. Was starting to panic that it had died. Thankfully it was the SoD and I got it back on.
Thanks for the quick tips on how to get it back up and running.

[Q] CM7 on Nook Color has blackout issue

I have been running CM7 on my Nook Color successfully for about 6 months now, but there is an ongoing issue that drives me nuts. Any help is appreciated. The problem is that, occasionally (about 4-5 times a week), the Nook will go to screen timeout and then not be able to come back out with any combination of buttons. The "n" button, power button, volume buttons, etc. all have absolutely no effect whether you press and release or hold down. The only way to get things back is to hold down the power button for 8-10 seconds and release...then hold the power button down again until the screen flashes and the green Cyanogen logo comes up. This, to me, is forcing it to shut down and then rebooting, though I can't see what's going on onscreen until the reboot. Then it will boot normally and work like normal......until the next blackout.
This happens even if the battery meter is fully charged, mid-way, or getting low...makes no difference. It will also happen no matter what the screen was when it timed out (home screen, app screen, etc.). Any ideas?
emopdx34 said:
I have been running CM7 on my Nook Color successfully for about 6 months now, but there is an ongoing issue that drives me nuts. Any help is appreciated. The problem is that, occasionally (about 4-5 times a week), the Nook will go to screen timeout and then not be able to come back out with any combination of buttons. The "n" button, power button, volume buttons, etc. all have absolutely no effect whether you press and release or hold down. The only way to get things back is to hold down the power button for 8-10 seconds and release...then hold the power button down again until the screen flashes and the green Cyanogen logo comes up. This, to me, is forcing it to shut down and then rebooting, though I can't see what's going on onscreen until the reboot. Then it will boot normally and work like normal......until the next blackout.
This happens even if the battery meter is fully charged, mid-way, or getting low...makes no difference. It will also happen no matter what the screen was when it timed out (home screen, app screen, etc.). Any ideas?
Click to expand...
Click to collapse
This is Sleep of Death (SOD). Well known issue. It happens when you have wifi set to stay on all the time. When the screen turns off and the nook goes into deep sleep, sometimes wifi and deep sleep get tangled up and you can't turn the screen back on. Only solution is to change your wifi setting or get a patched wifi module and flash that to your system. If you want a link to that patched file just ask and I will post it.
Edit: here it is:
http://d01.megashares.com/dl/8VPCE7N/wifi_SOD_patch.zip
Sent from my NookColor running ICS and Tapatalk
Thanks for the solution
I guess I wasn't using the magic keywords to find the problem online. Thank you so much for the solution and link.
@leapinlar: Do we know if that fix will work with mrg666's new kernel?
It still reports 2.6.32.9 in about tablet but I was under the impression that was because he was too tired to change it that night.
In my case I'm just happy to set wifi to turn off when the screen turns off, (I hate, hate, double hate, loath entirely when a device I've put to sleep trys to get my attention).
MISRy said:
@leapinlar: Do we know if that fix will work with mrg666's new kernel?
It still reports 2.6.32.9 in about tablet but I was under the impression that was because he was too tired to change it that night.
In my case I'm just happy to set wifi to turn off when the screen turns off, (I hate, hate, double hate, loath entirely when a device I've put to sleep trys to get my attention).
Click to expand...
Click to collapse
The patch only works on 2.6.32.9 kernels. I don't know anything about his new kernel. Just backup your existing twlan_drv.ko in /system/lib/module by renaming it .bak before flashing, and if it does not work restore your backup.
leapinlar said:
The patch only works on 2.6.32.9 kernels. I don't know anything about his new kernel. Just backup your existing twlan_drv.ko in /system/lib/module by renaming it .bak before flashing, and if it does not work restore your backup.
Click to expand...
Click to collapse
Yeah, I did that last night and didn't get an SOD but that really doesn't tell us much. I'll try to remember to take this over to his thread.
MISRy said:
Yeah, I did that last night and didn't get an SOD but that really doesn't tell us much. I'll try to remember to take this over to his thread.
Click to expand...
Click to collapse
Well, if you flashed it and wifi still works, it is compatible. On the CM9 kernel, it worked on .9 kernel until they updated to .59 and then if you used the patch, wifi quit working.

Categories

Resources