Timeline for How to deal with (orphaned) WakeLocks?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 10, 2013 at 2:24 | comment | added | Izzy | Thanks a lot! I was hoping for an easy solution to the "What if it is the Android System itself?" part. Seems there isn't such a thing -- but if it's possible, it might be a good idea to integrate with WLD :) | |
| Mar 10, 2013 at 2:04 | comment | added | UzumApps | The answer for your question is 'no' because wakelock detector groups wakelocks that belong to the same app packagename. As Location Service belongs to android os, the solution would be checking User permissions of app | |
| Mar 9, 2013 at 19:35 | comment | added | Izzy | Thank you for the details! I merged them into your answer, I hope you don't mind :) Question of understanding: Say an app queries the location using an interval of "0 seconds". This would cause the LocationService to wakelock the device. Would Wake Lock Detector show the responsible app then as the real cause -- or the LocationService, as it's not a part of that apps package? | |
| Mar 9, 2013 at 19:31 | history | edited | Izzy | CC BY-SA 3.0 |
included details from the comments
|
| Mar 8, 2013 at 10:32 | history | edited | Izzy | CC BY-SA 3.0 |
added 574 characters in body
|
| Mar 8, 2013 at 10:23 | comment | added | Izzy | Thank you! That's a valuable information indeed. Would you mind to add some more details to your answer, e.g. what makes it so special? I would add some screenshots then. Until that's done: Here's the Playstore link to the app... | |
| S Mar 8, 2013 at 9:45 | review | Low quality posts | |||
| Mar 8, 2013 at 10:00 | |||||
| S Mar 8, 2013 at 9:45 | review | Late answers | |||
| Mar 8, 2013 at 10:37 | |||||
| Mar 8, 2013 at 9:30 | history | answered | UzumApps | CC BY-SA 3.0 |