Linked by diegocg on Sun 22nd Jul 2012 19:09 UTC
Permalink for comment 527797
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2011-01-28
sb56637,
As I understand it, on a very general level they've added a new synchronisation lock in the kernel, which is accessed directly by userspace applications to block sleep states. Once no userspace applications hold a lock, the entire system immediately enters a sleep state. These transitions occur very frequently as one receives input.
The thing about the google G1 hardware was that it only supported a system-wide sleep state, not per-device, which is why google built that into android. But most hardware can put individual components to sleep and wake them up individually on demand, and I argue is better than a system wide sleep. Someone please correct me if I'm wrong, but I think if any android application is using one device with a wake lock, then all active yet idle devices on the system remain awake during that interval.