S Scantech Well-Known Member Licensed User Longtime User Aug 17, 2019 #1 I am trying to understand the StartServiceAt behavior. I call StartServiceAt in Service Start at 30 minutes (testing at 1 minute) and when i Force Close the App the StartServiceAt is useless. It will not start the Service. So far, I know force close will not allow the Service to Restart and what about app crashing? Do we have a workaround for this?
I am trying to understand the StartServiceAt behavior. I call StartServiceAt in Service Start at 30 minutes (testing at 1 minute) and when i Force Close the App the StartServiceAt is useless. It will not start the Service. So far, I know force close will not allow the Service to Restart and what about app crashing? Do we have a workaround for this?
S Scantech Well-Known Member Licensed User Longtime User Aug 17, 2019 #2 As per Erel 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. Click to expand... Old thread and i am assuming it still stands as what it says? Upvote 0
As per Erel 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. Click to expand... Old thread and i am assuming it still stands as what it says?
Erel B4X founder Staff member Licensed User Longtime User Aug 18, 2019 #3 Yes. Note that swiping the app from the recent apps list doesn't put the app in the STOPPED state (on most devices). This is different then closing it from the settings. An app in the STOPPED state cannot be started without the user explicitly starting it. Upvote 0
Yes. Note that swiping the app from the recent apps list doesn't put the app in the STOPPED state (on most devices). This is different then closing it from the settings. An app in the STOPPED state cannot be started without the user explicitly starting it.
