Android Service.startForeground does NOT respect notification id uniqueness

Question

Service.startForeground() vs NotificationManager.notify(), give different behaviors.

When using notify with two different notification ids, 2 notifi

Answer 1

Well, it's not the best solution, but you can always just "reassign" a notification to a dismissed notification ID. For example, say you start Process 1 (foreground) and then Process 2 (using NotificationManager). When Process 1 ends, dismiss the notification for Process 2 and update the foreground notification for Process 1 to actually now show the progress for Process 2.

That way you don't have to call stopForeground() and startForeground(), which may allow the service to be killed in between (haven't actually checked that's true, though).