surprisingly early suspend

John Watlington wad at
Sun Mar 7 22:00:35 EST 2010

Suspend happens after fifteen seconds of no UI interaction
(there are other criteria as well).

We are trying to ensure that this suspend is transparent to
the user.

Currently, screen dimming is "wrongly" tied to suspend (not sleep)
timing.   This has recently been a subject of vigorous debate, and
should change in a upcoming release.

We are also looking into supporting wakeup on USB.  It is unclear
how well this will work (as it didn't work very well on XO-1, even
with sideband signals available for wakeups).  The XO-1.5 hardware
theoretically supports this, but I don't know if any USB keyboards
will properly support this.

I would love to see the UI idle time before suspend be 1-2 sec. !


On Mar 5, 2010, at 11:44 PM, Mikus Grinbergs wrote:

> Disclaimer:  I am not asking for help;  I am reporting my experiences.
> XO-1.5.  Was installing a new build.  I got distracted, then noticed
> that the boot-up process had gotten as far as asking for the name  
> to be
> typed in.  Plugged in the external keyboard - was surprised that me
> pressing keys did not show up on the screen.  Pressed keys on  
> native XO
> keyboard -- they did not show up on screen either.  Then the screen
> brightened, and I realized that the XO-1,5 had gone into suspend  
> because
> I had not "soon enough" entered the name when boot-up was asking  
> for it.
> mikus
> _______________________________________________
> Devel mailing list
> Devel at

More information about the Devel mailing list