infinityger.blogg.se

However, we recommend to keep the notification In coming releases, we might add a setting inside the app to turn it off for pre-Android-O devices.

And still users can disable this notification from Android settings If we work as a foreground service, Android system will less likely kill our process

Google is right, better to be transparent to all users So when we implemented these changes, we thought about it and apply for all versions, because: I assume, now there might be questions like "but my device is not Android O?". So by this way, an application provide some functionality (in our case real-time protection), while being transparent to user (with a notification). And when you have foreground service, your service is considered by Android system and it is not killed. If you have a foreground service, you can do things (without having UI), but a foreground service should be transparent to user, so you have to show the notification. So what's a foreground service and what does it do? So to be complaint with new SDK (API 26), we needed to work in a foreground service. Our real-time protection is a background process too. Especially when they are doing background operations. With Android O, Google wants to all applications to be more transparent to user. I can explain a little more about that notification icon