View Single Post
Old 08-24-2013, 09:07 PM   #13
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: See lipc-set-probe usage, -i is to set a property exposed as an int, which touchScreenSaverTimeout is, according to lipc-probe.

I happen to know the tier1 default timeout value because it hasn't changed since the K2, and I still remember it ;p (also, it's shown in the output of the status property of powerd).

Why 1? Because I guessed that it was actually more like a boolean value, so 1 for true effectively triggers it, and resets the countdown . I haven't checked if we could make the countdown larger than the default t1 with a different value.

The tier2 timeout used to be 60s after t1, but I don't know if it's still the same value on FW 5.x.

Last edited by NiLuJe; 08-24-2013 at 09:10 PM.
NiLuJe is offline   Reply With Quote