B b4auser1 Well-Known Member Licensed User Longtime User Mar 2, 2015 #1 AddReceiverText(svcSMSReceiver, <intent-filter androidriority="-1000"> <action android:name="android.provider.Telephony.SMS_RECEIVED" /> </intent-filter>) I have used Static SMS intent filter as it described in Tutorial, because: Static receivers always work. If the process is not running then it will be created. but if I kill my application thru applications in Android settings, then my service is not started automtically after SMS received. What is wrong ? P.S. Except the case with killing, service in my application receives and processes all the incoming SMS correctly.
AddReceiverText(svcSMSReceiver, <intent-filter androidriority="-1000"> <action android:name="android.provider.Telephony.SMS_RECEIVED" /> </intent-filter>) I have used Static SMS intent filter as it described in Tutorial, because: Static receivers always work. If the process is not running then it will be created. but if I kill my application thru applications in Android settings, then my service is not started automtically after SMS received. What is wrong ? P.S. Except the case with killing, service in my application receives and processes all the incoming SMS correctly.
Erel B4X founder Staff member Licensed User Longtime User Mar 2, 2015 #2 This is how Android works (starting from Android 4 I think). If the user explicitly kills your app it will not be started again until the user has explicitly started it. Upvote 0
This is how Android works (starting from Android 4 I think). If the user explicitly kills your app it will not be started again until the user has explicitly started it.
B b4auser1 Well-Known Member Licensed User Longtime User Mar 2, 2015 #3 Is there a workaround to force starting service after application being killed by user ? Upvote 0
Erel B4X founder Staff member Licensed User Longtime User Mar 2, 2015 #4 No. StartServiceAt will not work as well as it also uses an intent filter. Upvote 0
