android-service

We have developed an Android Application which involves a service in the background. To implement this background service we have used IntentService . We want the application to poll the server every 60 seconds . So in the IntentService , the server is polled in a while loop. At the end of the while loop we have used Thread.sleep(60000) so that the next iteration starts only after 60 seconds. But in the Logcat , I see that sometimes it takes the application more than 5 minutes to wake up (come out of that sleep and start the next iteration). It is never 1 minute as we want it to be. What is

I've just been reading about adding a service to my application, and since 7/8 there are now service restrictions to improve phone performance. I've seen that the recommended approach is to use a job scheduler, but will that not just periodically start a new listener if I did that? Basically I update my database, and using a snapshot listener I want to update my user in real time. When the app is closed, I'd like to send a notification. My issues (if I'm correct) are that constantly making a new Firestore request will eat through my request allowance. Also, if its a job scheduler it won't

There are few questions similar to this on StackOverFlow but none of the solutions are working for me Problem The problem is with only few devices like OnePlus and MI ,The service is getting killed as soon as the user swipes away app from recent app. I read that these OEM'S use some aggressive strategies to kill services . I just want to know is there any way to keep service running or start it as soon as it gets killed . What I want I need to run a service which will give location continuously (24/7) in background (This app is only for specific people so no worries about battery life) .

I am developing an app where I start a service if a particular feature (in my app) is enabled by user. I want to keep running this service even after user quits my app. How can I do this? plz help EGHDK Right from developer.android.com A service is a component that runs in the background to perform long-running operations or to perform work for remote processes. A service does not provide a user interface. For example, a service might play music in the background while the user is in a different application, or it might fetch data over the network without blocking user interaction with an

We are currently developing an Android app that is a fitness-tracker application. It runs constantly in the background, and it works fine on most devices, but we've been having issues with the application dying completely on some Samsung devices. After some investigation, it seems like some Samsung devices has a completely custom "App Optimisation" feature ( http://forums.androidcentral.com/samsung-galaxy-s6/599408-app-optimisation-after-updating.html ), which is basically a (very) primitive version of the Doze feature that exists in later versions of Android which basically just murders apps

How can I make sure that only one instance of Service is created? I have checked some functions with logging (WeatherService is the class who extends Service): Log.i(TAG, "Start Id:" + WeatherService.this.hashCode()); Log.i(TAG, "End Id:" + WeatherService.this.hashCode()); It gives different hash codes even when I am sure that the same function is running twice (downloading): 09-12 01:00:55.195: INFO/WeatherService(7222): Start Id:1137653208 09-12 01:00:57.235: INFO/WeatherService(7222): Start Id:1137654296 09-12 01:00:59.035: INFO/WeatherService(7222): Start Id:1138806536 09-12 01:01:39.085:

Is there any other reason that the Intent that is passed to onStartCommand(Intent, int, int) would be NULL besides the system restarting the service via a flag such as START_STICKY ? Also, when the service is restarted by the system the Intent.getAction() method returns NULL... sometimes. Intent is not NULL just getAction() I asked here too but haven't received an answer just yet. UPDATE : After chatting with Mark Murphy, he suggested that I return START_REDELIVER_INTENT in the onStartCommand() callback in my service instead of START_STICKY so that the entire intent is sent following a restart