On Fri, 6 Aug 2010, Brian Swetland wrote: > On Fri, Aug 6, 2010 at 4:59 PM, <david@xxxxxxx> wrote: >> >> now, android is betting that the apps are all developed specifically for the >> android from scratch, so having a different API is acceptable, even if it >> cuts them off from the rest of the *nix applications. For a phone this is >> not neccessarily an unreasonable stance, but as Android moves into the >> spaces where normal applications are in use (netbooks and tablets), this >> becomes a much shakier stance to take. > > "Normal" apps work reasonably well -- they get halted when the screen > turns off, just like they do when my laptop suspends. > > Wakelocks are useful for mobile-centric apps that you want to keep > running in the background, wake up and do work when the device is > "asleep", etc. that description sounds far more like normal sleep power management that suspending. especially since they want to set timers to wake the system up and the defining characteristic of suspend (according to this thread) is that timers don't fire while suspended. as I am seeing it, there are two reasons why this don't "just work" 1. sleeping can't currently save as much power as suspending 2. the current logic for deciding to sleep can't ignore the other apps on the system. David Lang _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
