Related
Been happy with my Nexus with Cyanogen Rom, but just having a problem with it sleeping:
Suddenly its stopped going into standby/sleep when I press the power/wake button on the top. Pressing and holding still allows me to shut down etc, so its not hardware.
The only thing I thought was I just installed RoboDefence Free Edtn and Android mentioned it will keep the phone awake in the "Program Controls" confirmation page. I've since uninstalled the app but still have the problem.
Anyone know if theres a global setting somewhere for this?
Thanks,
I am having the same problem with my recent Cyanogen
if you are on 5.0.5, i'd wait till tomorrow till 5.0.5.1 comes out and hope that fixes it.
check your end button behavior under spare parts. i changed mine to "sleep" on 5.0.5 and now the power button puts the phone to sleep
had this problem for a few days intermitantly then wouldnt let me power down at all....took my battery out and phone wouldnt turn on...! phoned HTC said they will collect and see for repair/replacement...
tip: back up your data now just in case it is the power button on its way to braking down. just in case!
very helpfull staff tho wen i called up quite pleased so far!
any update?
..im having the same issue, and was
considering calling in & sending it back,
but i'm wondering if they'll snoop around n'
find out that i've rooted & un-bootlocked..
i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
three threads above yours.
http://forum.xda-developers.com/showthread.php?t=681723
could be a hardware issue.
Mine does this every few days.. I am still on the stock 2.1 rom.
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
It happens to me as well, but very infrequently. Maybe every few days... so it doesn't bother me enough to worry about it.
I'm on stock ROM btw.
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Hmm, my problem's slightly different. Around half of the time, I have to press the power button twice to turn the screen on. Sometimes, pressing it the first time doesn't turn the screen on, had to press the power button firmly again.
This started only recently. On stock n1 and bought it during feb.
that means that your power button is dying, like many others' (including mine)
this is the first time, it takes 2 clicks to work....than it will increase.
Expect a repair soon...
Well i am having the issue other way around. i am not been able to put my phone in stand by mode by clicking on it and it is do a hard press then i get options to shut off the phone
any suggestions what might be causing it ?
I'm happy I haven't received this problem yet
-------------------------------------
i want my yogurt lol froyo time
negroplasty said:
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
Click to expand...
Click to collapse
I am having the same issue and i wonder if you were able to find the cause for it. I have the same rom as you do on your phone
negroplasty said:
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Click to expand...
Click to collapse
I have a similar problem. When I unplug the N1 from the charger, the screen comes on showing the lock screen, and I can't get it to turn off. If I unlock the phone, however, then the power button works normally. I don't think it was doing this until recently (I bought it in January the first day it was offered and am running the stock update1 ROM).
So here is my theory if the power button is a problem then it needs to act up both ways and not only one way. right now i can put the phone in sleep mode but i can wake it up. i will post the issues on the development forum and might be able to find an asnswer to it
So seems like the issues is because of Cyanogenmod 5.0.6 because since i have flashed another rom it is working just fine. i will be doing some more testing before i can be certain
Another problem I am experiencing is when I long press the power button, it pulls up the phone options menu but also turns off the screen. It's extremely frustrating as it does this quite frequently; right after I power on the screen again and unlock the device it works properly every time - so much so that I am convinced this is a software issue.
I am now running froyo, rooted with Cyan's minor root patch. I can also say for sure I experienced the same problem on CM 5.0.6, but it definitely occurred less frequently.
Am I alone here?
di2356 said:
i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
Click to expand...
Click to collapse
I just started having this problem after upgrading to 2.2.
I have this every so often. But sometimes wonder if it is flyscreen doing it
You guys should all just be running the app no lock to take the power autumn out of the equation.
Ahhhhh! I just need trackball wakeup!
I have a similar issue where my screen will turn on but will be unresponsive. When i turn it on and off, the backlight jut comes and goes. If it times out it won't turn back on for a bit(the backlight will come on still).
I just wiped my phone, hoping that'll fix it since it only started happening on a regular basis since I updated to Froyo
(moved from wrong forum to right one!)
Here's a silly question,
How do I tell if the N1 is off? Without turning it on?
There have been several times where I've turned it off for the night (force of habit), and later couldn't remember whether or not I had in fact turned it off...
Of course hitting the power button only turns it on if it was in fact off... meaning that I have to wait a whole boot cycle before shutting it down again.
From the thread in the other forum:
Hitting the volume keys doesn't seem to do anything when the phone is sleeping, i.e. it doesn't wake the screen up.
I like the idea of the trackball on wake thing except that it will probably wake the phone up a lot when it's in my back pocket.
any other tips?
v.
Trackballwake is the only way i can think. I used it on Cyanogenmod, and i didnt seem to have a problem constantly waking the phone in my pocket. Give it a shot, if it does cause a nuisance, back to square one.
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Svarto said:
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Click to expand...
Click to collapse
so the only way to escape this is by pulling the battery and rebooting? when you do reboot and dont go in standby, the touchscreen works fine?
You can check the issue using logcat and /proc/kmsg.
Also, you can read my threads on the subject, describing the same error with logs, and see if your logs are the same.
I'm currently trying to check if the error repeats itself after full wipe and starting from scratch. In the meantime it didn't show up until I applied a theme, and then after reflashing the ROM it's gone again - I'm still checking, only a day has passed.
Yes, the only solution is to pull out the battery and reboot. Then it works fine and I can go in and out of standby. I havent found a particular pattern to it happening so it is hard to reproduce.
I will have a look at that logcat and your other thread!
Just to guide you - when it happens to me, the phone gets stuck with mmc0 access that receives "CRC error" reply and doesn't go through. Pressing power button for a long time several times and playing with trackball / touching the screen between presses "releases" the "lock", and you'll be able to work with the phone again until you put it to sleep again. If you turn WiFi and BT off and then back on - the problem seems to disappear.
I need some help!! My nook color (with CM7 on an SD card) will not come back on after the screen turns off. Now this isnt everytime but it happens quite often. It happens whenever the screen automatically turns off or if I press the power button to turn off the screen. Then when I press the n button or the power button to turn the screen back on, it sometimes won't turn on. I press either button multiple times and it won't turn on. I have to hard reboot it. It's very annoying.
Is it going into some sort of sleep mode? Any help is appreciated.
Change the wifi sleep policy to turn the wifi off when the screen is off, you can accomplish this by going to the wifi settings, hitting the menu button and then advanced...
I'd also recommend for general usage to install to the emmc and use the latest nightly for best CM7 stability and performance.
I'm kinda new to this stuff. Can you tell me how to accomplish the general usage to the emmc? And also how do I update to the newest build? Would I have to rebuild my SD card from scratch?
To install to the emmc just follow this guide(http://forum.xda-developers.com/showthread.php?t=1030227)
You can get the latest nightly here(http://download.cyanogenmod.com/?device=encore)
If you just want to update your sd card install all you should have to do is place the latest nightly on the boot partition of your sd card and boot into recovery(start with the nook off, press and hold the "n" button and at the same time press and hold the power button for a good 3-4 seconds, while still holding the "n" button let go of the power button) and the build should update itself.
If I update the build will I lose all my apps and configurations?
tiray73 said:
If I update the build will I lose all my apps and configurations?
Click to expand...
Click to collapse
No, you wont.
After I install the newest nightly build, how can I verify it is the newest one?
settings>about tablet>mod version
This is Sleep of Death. To get rid of it forever set up two profiles in tasker one for wifi off with screen off and wifi on when screen is on.
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
koopakid08 said:
This is Sleep of Death. To get rid of it forever set up two profiles in tasker one for wifi off with screen off and wifi on when screen is on.
Click to expand...
Click to collapse
Love Tasker, and did this in Tasker for a while, but Green Power is actually better for this specific task, even if it is yet-another-service.... It'll open up wifi (if you want it to) every N minutes for M minutes to grab email or such, then back off. And it's pretty cheap if you don't already have Tasker.
In reality, I am sure I COULD have Tasker do this too... Set a var, have a every-15-minutes process look to see if the var is set, go online for M minutes, go back offline... But I sometimes find Tasker doing too many things at once makes it get behind.
khaytsus said:
Love Tasker, and did this in Tasker for a while, but Green Power is actually better for this specific task, even if it is yet-another-service.... It'll open up wifi (if you want it to) every N minutes for M minutes to grab email or such, then back off. And it's pretty cheap if you don't already have Tasker.
In reality, I am sure I COULD have Tasker do this too... Set a var, have a every-15-minutes process look to see if the var is set, go online for M minutes, go back offline... But I sometimes find Tasker doing too many things at once makes it get behind.
Click to expand...
Click to collapse
I tried green powder and still got SoD because of the constant wifi on and off in sleep. Tasker is the only complete solution I've found
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
True, for the NC, turning off completely makes sense.