Thanks for responding!! Well!! I am working with emulator currently and the behaviour is same. I have confirmed from the logs that the service is not crashing. All I could observe from the logs that System is killing the service(and hence the process) as its not a system service.
>your service is not using a background thread Well my service is a multi-threaded application but not sure what you mean here. Its a Android application/process with only one service and nothing more than it.Do you mean I should start a thread for running the service? I thought of utilizing the process as its only one service in the process. Thanks in advance Ash On Nov 20, 1:52 pm, Ash <ashutoshkagra...@gmail.com> wrote: > Hi!!, > > I am running a background Android Service as VoIP Framework which > provides different VoIP services to different Android applications, > (VoIP call, Video Call, etc). The service establishes a network > connection with the Server(Service Provider) and does some initial > handshake before it can start providing service to the Android > applications, that’s why though of starting the service on > BOOT_COMPLETED event. > > The problem is when the service gets started on BOOT_COMPLETED event, > before even it finishes the initial network connection with server and > handshaking, it gets killed by the system. > > I have tried using setForeground which improves the behavior a bit but > still gets killed mid-way. I am working with old version 1.5 r3 of SDK > and hence, cannot use "startForeground". > > Is there a way out or another alternative available with SDK 1.5 r3? > > Thanks in advance, > Ash -- 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
