PDA

View Full Version : Resume from Standby with Laptop



DWAnderson
September 27th, 2004, 02:50 AM
I'm trying to use ny USB-UIRT to wake my laptop from standby using a remote. I am able to do so using the instructions in other threads, but the LCD display won't turn on (and Girder won't respond to commands) until the physical mouse or keyboard on the laptop is used.

Any idea how I can solve/work around this problem?

Promixis
September 27th, 2004, 09:54 AM
Hi,

What plugins are you using?

Does the laptop start up with the UIRT?

You might want to try having Girder move the mouse using the OnResumeSuspend event and see if that turns on the screen.

DWAnderson
September 27th, 2004, 11:00 AM
Hi,

What plugins are you using?

Does the laptop start up with the UIRT?

You might want to try having Girder move the mouse using the OnResumeSuspend event and see if that turns on the screen.

I'm using the USB-UIRT plugin.

The laptop does startup with the UIRT after going into standby (I know because I hear the HD start and the appropriate indicator lights come on), but the screen won't come on AND Girder won't respond (or maybe the system isn't sending the events) to either the On ResumeSuspend, a command to turn on the screen on a remote button press, or any other event until I physically hit a key or make a motion on the touchpad.

Any ideas of what I can do to address/work around this issue?

Promixis
September 27th, 2004, 12:29 PM
Download the logger plugin. Enable it and go through a standby resume sequence. Cut and paste the logger output here.

DWAnderson
September 27th, 2004, 11:21 PM
Here is the logger output:

This reflects pressing one button to stand by and another to wake from standby (only the screen doesn't come on until I physically hit a key or the touchpad):

22:00:48.338 Monday, September 27, 2004 EVENT: Dev: 18 OnResumeSuspend
22:00:29.593 Monday, September 27, 2004 EVENT: Dev: 18 OnSuspend
22:00:29.252 Monday, September 27, 2004 EVENT: Dev: 18 OnQuerySuspend
22:00:29.242 Monday, September 27, 2004 EVENT: Dev: 75 8029DDA836CA

This reflects pressing one button to stand by and another to wake from standby and then another key on the remote five times (one mapped in Girder to turn the screen on). Again, the screen doesn't come on until I physically hit a key or the touchpad:

22:16:27.038 Monday, September 27, 2004 EVENT: Dev: 18 OnResumeSuspend
22:16:24.454 Monday, September 27, 2004 EVENT: Dev: 75 80A9DD8836EA
22:16:23.813 Monday, September 27, 2004 EVENT: Dev: 75 80A9DD8836EA
22:16:23.112 Monday, September 27, 2004 EVENT: Dev: 75 80A9DD8836EA
22:16:22.451 Monday, September 27, 2004 EVENT: Dev: 75 80A9DD8836EA
22:16:21.760 Monday, September 27, 2004 EVENT: Dev: 75 80A9DD8836EA
22:16:08.416 Monday, September 27, 2004 EVENT: Dev: 18 OnSuspend
22:16:08.055 Monday, September 27, 2004 EVENT: Dev: 18 OnQuerySuspend
22:16:08.045 Monday, September 27, 2004 EVENT: Dev: 75 8029DDA836CA

Thanks for your help.

Promixis
September 28th, 2004, 07:12 AM
Well, you are getting the right events.

You can try having Girder move the mouse when the laptop resumes but I am thinking there might something about the laptop hardware that won't turn on the lcd unless a key is pressed.

jon_rhees
September 28th, 2004, 07:09 PM
You can thank Microsoft for this one...

This is Window's behavior for some wake-on devices, such as Lan and Modem (saw this issue several years back when developing modems). Microsoft's thinking was that since you were firing up your laptop remotely, no user was present and therefore the screen didn't need to be turned on (to save energy).

I don't know what you can do as a workaround, unfortunately. You might want to play with the general power settings and see if you can get it to behave more like a desktop.

-Jon

DWAnderson
September 28th, 2004, 09:30 PM
You can thank Microsoft for this one...

This is Window's behavior for some wake-on devices, such as Lan and Modem (saw this issue several years back when developing modems). Microsoft's thinking was that since you were firing up your laptop remotely, no user was present and therefore the screen didn't need to be turned on (to save energy).

I don't know what you can do as a workaround, unfortunately. You might want to play with the general power settings and see if you can get it to behave more like a desktop.

-Jon

Thanks for the insight. I'm at least glad I'm not crazy. :)

I had looked at the general power settings in Windows and in the BIOS. This is a Dell 2650 so the BIOS settings are too basic to have ANY power settings. I also tried playing around with Windows power settings, but nothing seemed to work.

Any idea if this behavior occurs on all laptops?