I am developing a simple GPS logger that runs as a service, getting fixes in short intervals. As I've read documentation and posts in this forum, I realize I need a WakeLock to keep the service running and logging points. Right now, without a WakeLock, my service runs fine for many hours, even when I am not using the phone that entire period. This is because I have other apps installed (task automation, etc.) that are using WakeLocks.
So, a couple of questions. Are there any issues running multiple apps that all use WakeLocks? Aren't they all just redundant? Wouldn't it be smarter to have one WakeLock app installed (at least one exists in the market) that allows the user to decide how and when to let the CPU/screen sleep and wake? In that way, WakeLock support doesn't need to be added to multiple applications. I'm not trying avoid implementing WakeLock, just want to make sure it's the best solution. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
