View Single Post
Old 10-25-2013, 08:08 AM   #3
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299993
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
This is nice.

How would you solve the additional puzzle of the "screensaver time issue."

When people choose to run an app with this configuration of "tap-out" escape, the default screensaver timeout time of 600 seconds comes back into play.

as you yourself have noted, some applications don't like being "backgrounded" by the Screensaver layer and will in fact end up irretrievably hidden...

There is a way to touch the screensaver timeout and set it back to another ten minutes, perhaps that could be part of the solution.

Code:
lipc-set-prop com.lab126.powerd -i touchScreenSaverTimeout 1


One final question, I wonder if the lipc-wait-event construct would be worth demonstrating too...

Last edited by twobob; 10-25-2013 at 08:24 AM.
twobob is offline   Reply With Quote