cellurl wrote: > I'm bummed. > So it seems widgets are only useful for once-a-day type info, no > exceptions?
I didn't say that. I said you can't fork threads from a BroadcastReceiver. App widgets are designed to change either on user input or after a period of time (preferably something nice and long, like 30 minutes, to save battery life). Based on your (non-working) code, you want to have an *app widget* be updated every time the device moves *a meter*. This would: -- require GPS to be on 24 hours a day, driving down battery life tremendously -- require some service of yours to be in memory all of the time, reducing the amount of memory available for other things -- update the home screen, thereby doing inter-process communication, on every change, further driving down battery life (and, since GPS can sometimes be twitchy, you might get these updates a whole lot) I recommend you watch Jeff Sharkey's "Coding for Life...Battery Life, That Is" presentation from the 2009 Google I/O conference: http://code.google.com/events/io/2009/sessions/CodingLifeBatteryLife.html You can create a service that will get woken up by an AlarmManager alarm periodically, register for location updates, update the app widget when a fix arrives, and shut down waiting for the next alarm. If you do this fairly infrequently, battery impact should be modest. However, I have no idea if this model will meet your needs, since "fairly infrequently" is a far cry from what your current implementation was trying to do. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
