Well, I hope this doesn't turn out to be an irrelevant distraction, but did you really have to move the code from onCreate and onStart? Not every IntentService can implement only onHandleIntent the way Google's sample does in http://developer.android.com/guide/topics/fundamentals/services.html#ExtendingIntentService
The same doc does, after all, specifically address this need in "If you decide to also override other callback methods, such as onCreate(), onStartCommand(), or onDestroy(), be sure to call the super implementation, so that the IntentService can properly handle the life of the worker thread." But in what you described, what was happening only when the Service was created is now happening every time you get an Intent. Maybe for your Service it makes no difference, but in general, that is quite a change. On Feb 23, 2:54 pm, Jake Colman <[email protected]> wrote: > >>>>> "KV" == Kostya Vasilyev <[email protected]> writes: > > KV> Based on your code - is your service class in a different package from > the > KV> widget class? > > No. Everything is in the same package. Everything about this package > was working and I was able to update the widget. The only change I made > was recode ZMUpdateService to extend IntentService instead of Service > and to move code from the onCreate and onStart methods to the > onHandleIntent method. That's why am I asking all these questions about > differences between using a Service and an IntentService - although > based on all the answers there isn't any! > > -- > Jake Colman -- Android Tinkerer -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
