Am Samstag, den 28.02.2009, 00:49 +1100 schrieb Carsten Haitzler: > > Feel free to disable the idlenotifier plugin in frameworkd.conf, it's a > > one liner. (Of course I will not remove the idlenotifier at all, since > > it's all we have, if X is not running) > > if u dont have x - you dont have a functional system...
That's a bit far fetched, don't impose your use pattern on others. There are tons of interesting single-purpose apps (think vertical market solutions) here that might not want to run X, but rather some UI they hooked on the framebuffer. They might even be fine with console mode, only giving input over a keyboard. frameworkd should be a nice companion as well for these kinds of patterns. > be it x or any > replacement (an fb based app) it will have the same ability as x does as it is > the one and only controller of the screen and input - so it can do the same. > > > You will then have to worry about the display being still dark when e.g. > > the PIN dialog opens, or a call arrives. Oh and please take care about > > applications that do not want autosuspend to trigger. > > apps should deactivate x screensaver as part of a toolkit call when such > actions happen. Good, lets spread the word to the application developers and have them disable the idlenotifier plugin. Screensaver also deals with suspend/resume yet? -- :M: _______________________________________________ smartphones-standards mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-standards
