Android Question StartServiceAt on Gingerbread not starting the service after the app is killed by os

GeeKay

Member
Licensed User
Longtime User
Hi! I'm working on an app (service) which provides some notification to user based on the app data. I used StartServiceAt with rescheduling every time the service is started. It worked perfectly on ICS and above and on Gingerbread too. Until I tried to clear RAM by task manager (clear memory). On Gingerbread this causes, that the scheduled service does not start anymore. Is there any workaround how to protect the scheduled service from being removed by the os? On ICS and above it works like a charm! I don't want to use sticky or foreground service - I need to run it once a day...
 

coslad

Well-Known Member
Licensed User
Longtime User
You must use Stickyservice, i think there aren't other solution.
 
Last edited:
Upvote 0

GeeKay

Member
Licensed User
Longtime User
Thanks Erel. It looks like a good and probably the only possible solution with the intent filter. I'll try.
The behavior I described in previous post I observed on Samsung Galaxy S Advanced with the BUILD-IN task manager..

To: coslad
I used the stickyservice before but I think the StartServiceAt is a much better and more elegant solution. I want to use it if there is at least a little chance.
 
Upvote 0
Cookies are required to use this site. You must accept them to continue using the site. Learn more…