View Single Post
Old 08-24-2013, 03:45 PM   #10
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@zxczxc: IIRC, there's a lipc call to reset the timeout. Never tried it myself, and you will still need to periodically launch this command, so that's not terribly awesome, but it might work.

EDIT:
Code:
lipc-set-prop com.lab126.powerd -i touchScreenSaverTimeout 1
Works, the default tier 1 timeout is 600s.

May also want to investigate what the hell defer_suspend & suspend_grace do, but I suspect, as the name implies, that they're mostly for the tier 2 timeout (suspend).

Last edited by NiLuJe; 11-30-2013 at 05:44 PM.
NiLuJe is offline   Reply With Quote