@ArtSalt: No.
@Sir Alex: Aha! I knew it
. Great find! We can't easily muck with the framework ourselves, though, so it's unlikely this could get fixed via a hack, but it's nice to know more details about that nonetheless
.
@Pushka: Not that I know of, it's basically the same fonts than those installed by default by the hack, and I used those for about two days without any issues... What happened exactly after putting the fonts & doing a framework restart?
@choclit: ~disableScreensaver works. (kinda). The only downside (AFAICT, never tried it myself) is that it disables the sleep mode (suspend) altogether... There was a way to change the sleep timeout on FW 2.x, but I haven't taken a look at that yet on FW 3.X.
We discussed this a bit a while ago, so, to answer isotherm's idea:
lipc-set-prop com.lab126.powerd touchScreenSaverTimeout 1
only resets the timeout to the max (ie. 600s).
(Didn't test preventScreenSaver, suspendGrace & deferSuspend though).