android-service

In previous versions of Android, I used this method to find if a service from another app was up and running. It worked reliably for me: ActivityManager manager = (ActivityManager)getSystemService(Context.ACTIVITY_SERVICE); List<RunningServiceInfo> services = manager.getRunningServices(Integer.MAX_VALUE); However, with Android O this is now deprecated and will only return information about the calling apps services. I've looked into other solutions, but I don't want to ask the user for more permissions, (UsageStatsManager, NotificationManager, etc). Is there an alternate solution for obtaining

From my little android knowledge I understand that android OS can kill my service under extreme memory conditions. I have created a service that returns START_STICKY . The service is meant to run in background. If android is about to kill my service, will it call onDestroy ? And when it restarts it would it call onCreate ? See here, the dev guide. http://developer.android.com/reference/android/app/Service.html#ProcessLifecycle onCreate() is only called when the process starts, which can either be the first time the service is running, or if it was killed on restarted, essentially this is

Following the Google developer instructions on implementing Firebase in my app , I notice that android lint complains. The idea is that we have to implement two services which inherit from Firebase services: public class MyFirebaseInstanceIDService extends FirebaseInstanceIdService { ... } public class MyFirebaseMessagingService extends FirebaseMessagingService { ... } and then register those services in the manifest. But, it's not quite perfect. In particular, these two recommended AndroidManifest.xml service entries do not contain any special permissions: <service android:name="

I have a setup that looks something like this: class MyFragment implements SomeEventListener { Application mAppContext; boolean mBound; boolean mDidCallUnbind; MyIBinder mBinder; ServiceConnection mConnection = new ServiceConnection() { @Override public void onServiceConnected(ComponentName name, IBinder service) { mBound = true; mBinder = (MyIBinder) service; mBinder.getThings();... } @Override public void onServiceDisconnected(ComponentName name) { mDidCallUnbind = false; mBound = false; mBinder = null; } }; ... @Override public void onSomeEvent() { mAppContext.bindService(...); } void

I have an app which is basically a service that runs all the time and alarms the user when something happens. When the service creates the alarm, it needs to give it his context so that the alarm can do callbacks to the service when something happens. For example: public MyService extends Service{ private SomeAlarm alarm; @Override public void onCreate() { super.onCreate(); alarm = new SomeAlarm(MyService.this); } } How can I inject the SomeAlarm class into the service, and give the SomeAlarm the service context as a variable? I wrote the code from the top of my head, so there could be a typo

My basic task is to create a native service in android and then write a simple native program to test it. lets say i want to write a simple service which return me sum of 2 integers. I have to use binders to talk to it from the program, I have tried to google around but i cant find a precise example. I need to know how to create a native service and find it in the program and if needed in Java also. If you're creating a normal Android application using the NDK, you can't use Binder because it's not part of the NDK APIs. Look in the NDK docs/STABLE-APIS.html for the full list of stable APIs,

I was looking at a scheduling tutorial by Vogella . It mentions the Job Scheduler API that was introduced in API 21 of Android. My question is can it be implemented in APIs lower than 21 (Lollipop) but not less than Android version 3 (Honeycomb)? from now on (after I/O 2015), you can also use new GcmNetworkManager. How to use it and how it works is described here - https://developers.google.com/cloud-messaging/network-manager It does a lot cool stuff like it persists your tasks trough reboots. On Lolipop it uses JobScheduler, on pre-Lolipop it uses it's own implementation. EDIT: An example