I think we can use logcat and analyze it’s output. In all similar programs I have found this permission : android.permission.READ_LOGS It means all of them use it but it seems the program starts and after that our program (app protector) will start and bring front. Use below code : try { Process mLogcatProc = … Read more
The root of your problem is located here: unregisterReceiver(batteryNotifyReceiver); If the receiver was already unregistered (probably in the code that you didn’t include in this post) or was not registered, then call to unregisterReceiver throws IllegalArgumentException. In your case you need to just put special try/catch for this exception and ignore it (assuming you can’t … Read more
Does BroadcastReceiver.onReceive always run in the UI thread? Yes.
Well here is a complete example of an AutoStart Application AndroidManifest file <?xml version=”1.0″ encoding=”utf-8″?> <manifest xmlns:android=”http://schemas.android.com/apk/res/android” package=”pack.saltriver” android:versionCode=”1″ android:versionName=”1.0″> <uses-permission android:name=”android.permission.RECEIVE_BOOT_COMPLETED” /> <application android:icon=”@drawable/icon” android:label=”@string/app_name”> <receiver android:name=”.autostart”> <intent-filter> <action android:name=”android.intent.action.BOOT_COMPLETED” /> </intent-filter> </receiver> <activity android:name=”.hello”></activity> <service android:enabled=”true” android:name=”.service” /> </application> </manifest> autostart.java public class autostart extends BroadcastReceiver { public void onReceive(Context context, Intent arg1) … Read more
I had the exact same problem you describe above (Galaxy Nexus on t-mobile USA) it is because mobile data is turned off. In Jelly Bean it is: Settings > Data Usage > mobile data Note that I have to have mobile data turned on PRIOR to sending an MMS OR receiving one. If I receive … Read more
instead, you may provide two different intent filters: filter for refresh only IntentFilter filterRefresh = new IntentFilter(Params.INTENT_REFRESH); filter for refresh and update IntentFilter filterRefreshUpdate = new IntentFilter(); filterRefreshUpdate.addAction(Params.INTENT_REFRESH); filterRefreshUpdate.addAction(Params.INTENT_UPDATE); now you may switch between intent filters by registering and un-registering the desired one but your receiver’s implementation would be same
In your onCreate method you can register a receiver like this: private BroadcastReceiver receiver; @Override public void onCreate(Bundle savedInstanceState){ // your oncreate code should be IntentFilter filter = new IntentFilter(); filter.addAction(“SOME_ACTION”); filter.addAction(“SOME_OTHER_ACTION”); receiver = new BroadcastReceiver() { @Override public void onReceive(Context context, Intent intent) { //do something based on the intent’s action } }; registerReceiver(receiver, … Read more
First, you need the permission in your AndroidManifest.xml: <uses-permission android:name=”android.permission.RECEIVE_BOOT_COMPLETED” /> Also, in yourAndroidManifest.xml, define your service and listen for the BOOT_COMPLETED action: <service android:name=”.MyService” android:label=”My Service”> <intent-filter> <action android:name=”com.myapp.MyService” /> </intent-filter> </service> <receiver android:name=”.receiver.StartMyServiceAtBootReceiver” android:label=”StartMyServiceAtBootReceiver”> <intent-filter> <action android:name=”android.intent.action.BOOT_COMPLETED” /> </intent-filter> </receiver> Then you need to define the receiver that will get the BOOT_COMPLETED action … Read more
Answer to your first question: Your broadcast receiver is being called two times because You have added two <intent-filter> Change in network connection : <action android:name=”android.net.conn.CONNECTIVITY_CHANGE” /> Change in WiFi state: <action android:name=”android.net.wifi.WIFI_STATE_CHANGED” /> Just use one: <action android:name=”android.net.conn.CONNECTIVITY_CHANGE” />. It will respond to only one action instead of two. See here for more information. … Read more
There is no API function to check if a receiver is registered. The workaround is to put your code in a try catch block as done below. try { //Register or UnRegister your broadcast receiver here } catch(IllegalArgumentException e) { e.printStackTrace(); }