android-service

The life cycle diagram of an Activity on an android does not guarantee that onDestroy() would be called, but that the process may be killed and the Activity is removed abruptly. The life cycle diagram of a Service on an android does guarantee that onDestroy() would be called. So I have two questions relating to this difference. Firstly, if the Service is part of the same process as the Activity, is the Service onDestroy() called, though the Activity onDestroy() is not called? I would think not, as "killing a process" suggest that the operating system is stopping its threads and releasing its

I'd like to be able to do some stuff when the SIM state change, i.e. play a sound when SIM PIN is required, but I think there are no Broadcast events that can be intercepted by a broadcast receiver for this... registering for android.intent.action .PHONE_STATE does only tell you when the CALL-STATE changes.. An alternative can be starting a service that registers a PhoneStateListener and reacts upon a LISTEN_SERVICE_STATE (when the state is OUT-OF-STATE it can get the SIM state from the TelephonyManager and look if the state is SIM_STATE_PIN_REQUIRED). So, my questions are: 1) Is there any

I am starting a service (or re-starting the running service) when an activity is launched, using : Intent intent = new Intent(this, MyService.class); startService(intent); Later on based on certain actions, the same activity binds to the service using bindService(new Intent(this, MyService.class), mConnection, Context.BIND_AUTO_CREATE); And when the activity is destroyed, I call unbindService(mConnection); Earlier, the service used to restart when I killed the same activity/application from the application tray and showed the "message 1 process 1 service running" under running apps. Now, the

How to continue background service in android Oreo without showing notification dot? i continues my background service using notification but i don't want to show notification for running service. Abdur Rahman This isn't possible in this API version (26) and higher. Android OS automatically close your service if you run it without showing a notification to the user. If you are targeting API >= 26 the system will impose a restriction on your service to run in background unless your activity in foreground. As soon as your activity goes to background, the service will be terminates when system

Usually when I create an Android service I implement the onCreate method, but in my last project this does not work. I tried implementing onStartCommand , and this seems to work. The question is: when I have to implement a service which method is required? Which methods I have to implement? onCreate , onStartCommand , or both? And what is the role of each? onCreate() is called when the Service object is instantiated (ie: when the service is created ). You should do things in this method that you need to do only once (ie: initialize some variables, etc.). onCreate() will only ever be called