your service will want to spawn its own thread or asynctask to do your
heavy work or else you will get a forceclose.
On Jun 13, 8:46 am, tarek.attia tarek.m.at...@gmail.com wrote:
Hi all,
I have a question what to Use ,Service Or Thread,as both run in the
background
--
You received this
On Jun 13, 11:46 am, tarek.attia tarek.m.at...@gmail.com wrote:
Hi all,
I have a question what to Use ,Service Or Thread,as both run in the
background
no, services run in the UI thread
pskink
--
You received this message because you are subscribed to the Google
Groups Android Developers
Services obviously don't run on the UI thread. It runs in the
background. However, Services have their own lifecycle, and can be
easily managed by applications. You can think of Services as an
extension of threads, in the sense that both of them do not run on the
UI thread.
Thanks and Regards,
Kumar Bibek wrote:
Services obviously don't run on the UI thread. It runs in the
background. However, Services have their own lifecycle, and can be
easily managed by applications. You can think of Services as an
extension of threads, in the sense that both of them do not run on the
UI
Services Run in the background as stated here
*Services*A *service* doesn't have a visual user interface, but rather runs
in the background for an indefinite period of time
http://developer.android.com/guide/topics/fundamentals.html
So my question is when to use Services and When to Use threads
5 matches
Mail list logo
