My device cannot stay in sleep mode, because have GSM issues. No rom actualization for it. Its Gigabyte G-Smart. So how i can mapp power button to turn screen off only, without suspend mode and lock device in the same time when i turn screen off? Like S2U2???
How to configure button power for only turn screen off, dont suspend???? Because my device have issues with GSM when in suspend mode.
.................
..........................
Aren't you confusing something?
* On: The user is interacting with the device. Everything is on.
* BacklightOff: There has been a brief period of user inactivity (no one has pressed any buttons or touched a touchscreen). The backlight has been turned off, but everything else is on. When you set the backlight timeout values in the control panel, you're setting how long the system should wait before going into this state. (Note that this state is new for WM 5.)
* UserIdle: There has been a longer period of user inactivity. Both the backlight and LCD have been turned off. When you set the screen timeout value on a Smartphone control panel, you're setting how long the system should wait before going into this state. This state is generally not used on PocketPC. There's no reason to turn the screen off when the device is about to go to sleep (sleeping turns the screen off). However, if/when PocketPCs go to the "Always On" model, they'll start using this state.
* ScreenOff: You go into this state when someone specifically says to turn the screen (and backlight) off. For instance, in Media Player you can assign a button to turn the screen off. When you press it, we go into this state. This state is different than UserIdle, though. This state says, "The user wants the screen off and doesn't want it to turn back on." UserIdle says, "The user hasn't touched any buttons in a while, so we might as well turn the screen off to save power." In ScreenOff, pressing a button (other than the power button) doesn't turn the screen back on. In UserIdle, pressing a button does turn the screen back on. Both PocketPC and Smartphone use this state.
* Unattended: This is a confusing state in which the screen, the backlight, and the audio are off. I won't go into too many details, other than to say that this is a PocketPC-only state that is used by applications which need to do things without alerting the user. While the PocketPC is in this state, the user thinks the device is asleep. For instance, ActiveSync when it syncs every 5 minutes. It's waking up, syncing, and going back to sleep, but the user can't tell.
* Resuming: This is the state the PocketPC goes into when it wakes up from sleep. In this state, the screen is off, and there is a very short (15 second) timer before it goes back to sleep. The only way to keep the device from going back to sleep is to have something put it into one of the other states. This is really for dealing with spurious wakeups and for giving the system a way to get into Unattended without letting the user know about it.
* Suspended: This is the PocketPC "Sleep" state. Everything is off, and the system isn't going to wake back up until some piece of hardware wakes it up. It's not actually an official Power Manager state, the way the other six are, but I'm including it for completeness.
Click to expand...
Click to collapse
from here: http://blogs.msdn.com/windowsmobile/archive/2005/08/10/450186.aspx
When you hit power button once, you go to Screen Off (Sleep). Suspended is when your device 'completely' off.
Ok guys.
I have a seriously annoying problem that has been here since CM6, at least since I started running it in late January, and is still
in CM7. Whenever you're listening to music, and have a screen lock delay (mine is set to 1 minute) whenever you press one of the
volume keys to adjust the volume the screen turns on. Yes, I have volume rocker wake unchecked in settings. This only happens during
the 1 minute time though, after it locks then the screen doesn't turn on. So if I had screen lock delay set at 5 minutes the volume
keys would continue to turn on the screen for 5 minutes until the lock activated. This happens if you have a lock delay, if you don't
then they never turn on the screen (unless you have it enabled in settings or you press one immediately after the screen turns off.)
If you have no lock/protection then this doesn't happen either, but if you have a delay it does. Please help, this wastes battery
life and is very annoying.
I have encountered some strange issues with Galaxy R during the past few days. The first issue is when I plug in my headphones when the phone is idle (i.e. screen off) the menu key often fails to wake it up. Only the power button wakes it up. Sometimes, it wakes up but after a greater than normal delay This happens only when earbuds are inserted when screen is off.
Secondly, sometimes my touch screen and capacitive buttons loose their sensitivity for a couple of seconds (say about 10 seconds) and then come back to normal. The menu and power button works fine but the touch controls are lost.
Has any of you encountered the same? Please comment. Thank you!
Mine Galaxy R doesn't have any of this. I'm on 2.3.4 and you? I think its a defect. And where you wrote this:
The first issue is when I plug in my headphones when the phone is idle (i.e. screen off) the menu key often fails to wake it up. Only the power button wakes it up.
I think that is normal because you cant unlock the phone by using the back or menu button.
I've noticed twice now within the last three weeks that my display will not respond to the power/volume buttons or gesture actions (double tap or track skip to start music). It will connect to my PC via USB and be discoverable and I can browse it, it'll also ring for phone calls (but I can't answer them). I used the security app Cerberus to take a picture and that works as well, but the command display message doesn't wwake the screen.
Kinda ironic that the display isn't waking just hours after I fixed my wakelock issues (just changed kernels btw). I have to long press the power button to reboot the phone to get the display back on.