My app has 2 services (actually 3, if you count the starter also)
The first service is running in the foreground, with a notification displayed.
This should assure it won’t get killed under SDK 26 rules.
The second service is running alongside the first, it is actually started in Service_Start of the first one, and should have the same lifecycle of the first, i.e. always running.
Does having the first service running in foreground, also shields the second one from being killed by the OS, or should I start also the second one in foreground, displaying a second notification icon, that will be redundant and may confuse the user?
The first service is running in the foreground, with a notification displayed.
This should assure it won’t get killed under SDK 26 rules.
The second service is running alongside the first, it is actually started in Service_Start of the first one, and should have the same lifecycle of the first, i.e. always running.
Does having the first service running in foreground, also shields the second one from being killed by the OS, or should I start also the second one in foreground, displaying a second notification icon, that will be redundant and may confuse the user?