| |||||||||||||
From wakelocks to a real solutionFrom wakelocks to a real solutionPosted Feb 19, 2009 8:01 UTC (Thu) by i3839 (guest, #31386)Parent article: From wakelocks to a real solution
> What has been proposed instead is that the user-space "inhibit suspend"
> policy be encapsulated into a separate daemon which would make the > decisions on when to keep the system awake.
A daemon like that could also implement the timeout behaviour, solving the problem described here:
> User-space applications may simply screw up and forget to allow the
Simple kernel interface + user space daemon seems like a working solution.
(Log in to post comments)
From wakelocks to a real solution Posted Feb 19, 2009 8:24 UTC (Thu) by alonz (subscriber, #815) [Link] Such a daemon could also allow some applications to hold the phone active for a longer time—for example, media players or games.It could even use the Android permissions model to decide which applications get this preferential treatment.
|
|||||||||||||