Timeline for How to deal with (orphaned) WakeLocks?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:18 | history | edited | CommunityBot |
replaced http://android.stackexchange.com/ with https://android.stackexchange.com/
|
|
| May 28, 2013 at 13:52 | history | edited | Izzy | CC BY-SA 3.0 |
added 239 characters in body
|
| Mar 8, 2013 at 10:48 | history | edited | Izzy | CC BY-SA 3.0 |
added some more details
|
| Dec 16, 2012 at 1:02 | vote | accept | Izzy | ||
| Dec 7, 2012 at 22:33 | comment | added | Izzy | Please do! And report your findings! I just had that described issue with the "orphaned" WakeLocks. Poking around for an hour, I didn't get further than seeing it was the LocationManagerService. Registered for updates all 0sec (sic!) was the Android Settings (=:-0). I exited it, stopped it, killed it at the command line... no way to get rid of the locks. WTF did Settings do there? A reboot solved it, of course -- but is this a WindowsPhone we have to reboot twice a day? | |
| Dec 7, 2012 at 22:25 | comment | added | t0mm13b | If I have time this weekend, I will poke around under the hood to see if there's a mechanism to get the kernel to boot out orphaned wakelocks.... ;) | |
| Dec 7, 2012 at 22:15 | comment | added | Izzy | Sure -- but see my question: I'm explicitly NOT asking about the developer side, but from a users perspective. Maybe I need to make that more obvious ;) | |
| Dec 7, 2012 at 22:09 | comment | added | t0mm13b | Better education to developers to say... "Release wakelocks when you are done with them and clean up after yourself"? | |
| Dec 7, 2012 at 22:08 | history | answered | Izzy | CC BY-SA 3.0 |