I would guess you are doing long-running work on the main thread of the service.
And any particular reason you are running it in a separate process? There is very rarely a need to do so. (Actually doing this probably hid the problem with blocking the main thread, since there is much less going on in that process, so much less chance for the system to detect a problem.) On Thu, Jul 16, 2009 at 8:15 AM, nuno <nba...@gmail.com> wrote: > > Hi all, > > I am starting a service from a broadcast receiver, using > android:process=":remote", which from what I understand means unbind. > That BR dies. > The service is runs some TTS (text2speach) in a cycle until a second > broadcast receiver comes into action and executes stopService. > > I am using action names to start and stop the service. > > The problem I am having is that after the stopService is executed the > service is still alive for a good 20 seconds when finally dies from > timeout. The other think I notice is that onDestroy() is never > called. > > Am I doing something silly (I know the answer is yes!) :) > > Thanks for the help. > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
