[FSO 5.1] Preventing screen blanking

Nicola Mfb nicola.mfb at gmail.com
Wed Apr 8 16:29:56 CEST 2009

2009/4/8 Johny Tenfinger <seba.dos1 at gmail.com>

> Hem? Toggle for preventing screen from being blanked (and another for
> suspend) is for few mounths in shr-settings. And guess who implemented
> it :P (answer: that was me :p)
That's  fine, as the user has to be able to choose it's power management
profile, however in a real scenario, you are in a car and want to start your
navigation software, it's better you stop driving and park (this is in
general good :)) as you have to launch srh-settings (it's slow, but it may
depend on the fact I have a slow glamo clock for avoiding some problems with
my sd card), and click some button, switch to illume, start your navigation
application, when finished you switch back to shr-settings and reclick
Suppose now that tangoGPS or navit, or other gps tools may do simply a
couple of call to org.freesmartphone.Usage.RequestResource at startup, when
the application exits the fso daemon automagically releases the resources:
you obtain a
on-click-and-do-not-suspend-dim-navigation-system-restoring-all-at-exit :))

I do not understand why this is so hard to implement! It may be that
upstream developers does not want to add that snippet of code as their
project is not distro-targeted, but distro mantainers may write a simple
patch do add to the SRH/FSO recipes epository?

It's only a consideration, when I'll begin to use GPS on my FR it may be
I'll write those damned patches :)

A question about shr-settings, do they interact with illume too to avoid
illume blanking?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/support/attachments/20090408/2e8d2c68/attachment.htm 

More information about the support mailing list