android-service

Suppose I have an android Activity / Service that is using system services such as PowerManager, WifiManager, etc... Is it beneficial to have private members for keeping reference to those services once in the constructor or onCreate method instead of getting those service managers each and every time they are needed by calling getSystemService(...)`? If so, are those members safe to use in case one of those system services crash and restart? If they aren't safe, what is the right approach for handling such cases of service death? s it beneficial to have private members for keeping reference

I am building an SDK. The Scenario From the app, the developer passes the JsonObject and URL in a method and inside the SDK. I add those values in SQLite database and start a JobScheduler. The Jobscheduler takes the request at 0 indexes out of the database executes it. When I get the response, I delete that request from the database and now the request at 1 index comes to the 0 index and again I execute the same code where 0th index request is fired. The Problem When I get the response from a server inside the SDK, I need to send it to the developer using a callback. I can take the callback as

According to the background execution limits introduced in Android Oreo, calling startService when the app is in background should throw an IllegalArgumentException . Check this question: Android 8.0: java.lang.IllegalStateException: Not allowed to start service Intent . I created a sample app targetting Android Oreo that does the following: @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); new Handler().postDelayed(new Runnable() { @Override public void run() { startService(new Intent(MainActivity.this,

In my application, I am starting the VIBRATOR_SERVICE through the following code long[] pattern = {50,100,1000} Vibrator vibe=(Vibrator) context.getSystemService(Context.VIBRATOR_SERVICE); vibe.vibrate(pattern, 0); I want the vibration continue till I call vibe.cancel(); The Code is working fine, but the vibration getting off when the screen goes to sleep mode. I want the vibration continue even after the screen goes to sleep mode. Is there any ways to do this? Please help me. Thanks in advance. :) Anu The correct answer to the question is as follows Before doing this, don't forget to add the

My app will access a webservice to access data (even if the application is not in foreground), every 10 minutes. What is the best way to do that? First do I need to start my service in seaparate thread? And how to make it get update from server every 10 minutes? Some people said handler.postdelayed and some using Alarm Manager. which one is better and do we have some examples. If the updates will occur while your application is running, you can use a Timer, as suggested in other answers, or the newer ScheduledThreadPoolExecutor . If your application will update even when it is not running, you

In my Android project, I have a Service : public class MyService extends Service{ //I defined a explicite contructor public MyService(){ //NullPointerException here, why? File dir = getDir("my_dir", Context.MODE_PRIVATE); } @Override public void onCreate(){ super.onCreate(); ... } @Override public int onStartCommand(Intent intent, int flags, int startId) { super.onStartCommand(intent, flags, startId); ... } } I know normally, I shouldn't explicitly define a constructor for Android Service . But in my case, I want to use the constructor to create a directory in my internal storage. When I try

I have sources of a remote service which is using AIDL. Also I have my own app that connects to that service. I debug two apps simultaneously, but inside the remote service I can hit breakpoints only in generated AIDL file (stub and proxy), but I can't hit the real methods of the remote service. What can be the reason? Maybe I'm doing something wrong? Thanks! It's a while since I tried this, but from memory I think what I did was : I set the breakpoints in the source, started the app which used the remote service, then went to the DDMS perspective and selected the process corresponding to the

I know this question has been asked before, but I've been over all of the answers I could find and still haven't been able to solve the problem. The issue is that when by BroadcastReceiver starts the IntentService onHandleIntent() isn't called. Weirdly enough the constructor does run (as I can see by the Log output). This is my code: NoLiSeA.class (This class contains the BroadcastReceiver that starts my service) public void toProcess(StatusBarNotification sbn) { LocalBroadcastManager.getInstance(this).registerReceiver(notificationForwarder, new IntentFilter("to_forward")); Intent intent = new