Hi,
there is no easy solution. The Android OS might kill a service (here the NewsRob sync service) at any time. That is not a problem, but the service is not notified about it about to be killed.
Now, at the begin of a sync I set a notification and at the end of a sync I remove the notification. The problem is when the sync is killed in between. As my service is just killed without prior warning I can't remove the notification and so the notification stays around.
And this happens much more frequently than you would expect. When your phone gets under memory pressure, it starts killing processes. Did you ever wonder why you had new articles, but they weren't downloaded yet even though the sync service is not running anymore? That's why. The service got killed, but will resume its work when it is scheduled the next time or you hit refresh.
I am trying to figure out what the best way is to deal with it, but recently Dianne Hackborn, an Android Dev from Google
answered [1], and this didn't give me any confidence that I will be able to solve this one quickly.
If you can live with this issue that the notification might hang around until the next sync, even though it is "finished" already, you can add the following line to a file called "newsrob.debug" that need to be placed in the sdcard's root:
enableSyncInProgressNotification=1
You can follow along the mentioned discussion if you're interested. I will reply to her answer soonish.
Cheers,
Mariano