In my opinion this is the most tricky/hard part of a mainstream/average Android development. For instance on BlackBerry this is IN TIMES easier. Definitely you need to use a Service. AsyncTask does not suit, because it is tightly “bound” to your Activity via a Context handle (otherwise you would not be able to update UI … Read more
Service is a base class of service implementation. Service runs on the application’s main thread which may reduce the application performance. Thus, IntentService, which is a direct subclass of Service is available to make things easier. The IntentService is used to perform a certain task in the background. Once done, the instance of IntentService terminates … Read more
In your concrete implementation you have to declare a default constructor which calls the public IntentService (String name) super constructor of the abstract IntentService class you extend: public MyService () { super(“MyServerOrWhatever”); } You do not need to overwrite onStartCommand if the super implementation fits for you (what I expect). In your current case you … Read more
Tejas Lagvankar wrote a nice post about this subject. Below are some key differences between Service and IntentService. When to use? The Service can be used in tasks with no UI, but shouldn’t be too long. If you need to perform long tasks, you must use threads within Service. The IntentService can be used in … Read more