Quote:
Originally Posted by NiLuJe
Where (meaning in which app/context)?
There's a known (mysterious) issue like that mentioned on github with KOReader, FWIW (buttons going kaput after a suspend session).
Other than that, that'd be news to me, but then I don't have a Voyage  . |
Well, then that sort of makes it certain then that it is a Lab126 error.
Those buttons need a Lab126 kernel driver and they messed up the 'entering suspend' and 'exiting suspend' cases in the driver.
Hmm....
I see to recall seeing warnings in the dmesg file about some of their drivers "taking an excess amount of time" to suspend and wake-up.
(kernel 3.x versions just spit out a warning and do the process anyway - screw the hardware if it isn't ready)
= = = = =
And if the O.P. has the screensaver 'last' option set, they would not get any indication that the device had gone to sleep.