foreground-service

I read many questions here about doze mode like Android doze mode , Android N Doze mode - how to keep background download and processing? , Wakelock and doze mode and many others. But in many replies, opinions is different. I can't test it by myself (emulator does not support my processor, and my only test device is android 5.1). I would like to know the next situation. I have an activity, which controls the media player. On devices with android 6.0 and higher it wouldn't work as expected cause of doze mode. As many solutions says to prevent doze mode it should start a service in separate

My foreground service doesn't show a notification when it works on Android Oreo. It works perfectly on Android versions from 15 to 25. When I do targetSdkVersion from 26 to 25 this issue disappears. But this solution seems not good. I prepared test project with this issue. What should I do for fixing it on Android Oreo with targetSdkVersion 26 ? My foreground service, SoundService.java( full source ): public class SoundService extends Service implements MediaPlayer.OnErrorListener, MediaPlayer.OnPreparedListener, MediaPlayer.OnBufferingUpdateListener { private final static String TAG =

I have a problem sometimes with my GCM service which is closed when RAM of my smartphone is automatically cleared (read this if you need more details). As far as I understand if I set my service to run in foreground it should help the system to to delete it with RAM. The method of Service.class onStartCommand() is usually used to run startForeground() method. But with the latest version of GCM implementation it is impossible since the onStartCommand() method of the parent GCMListenerService.class is defined as final and I cannot override it. So how can I set my gcm receiver to rum in

My app will call startForegroundService(intent) in the onCreate of the MainActivity . And I put startForeground(ON_SERVICE_CONNECTION_NID, notification) in both the onCreate and the startCommand of the Service . But I'm still receiving this error occasionally. Exception android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground() android.app.ActivityThread$H.handleMessage (ActivityThread.java:1775) android.os.Handler.dispatchMessage (Handler.java:105) android.os.Looper.loop (Looper.java:164) android.app.ActivityThread.main (ActivityThread

I am trying to stop a service which is running as foreground service. The current issue is that when I call stopService() the notification still stays. So in my solution I have added a receiver which I am registering to inside the onCreate() Inside the onReceive() method I call stopforeground(true) and it hides the notification. And then stopself() to stop the service. Inside the onDestroy() I unregistered the receiver. Is there a more proper way to handle this? because stopService() simply doesn't work. @Override public void onDestroy(){ unregisterReceiver(receiver); super.onDestroy(); } Ilya