From 5b9ca99537c32cb3c0da08800ec630ed4efd056f Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Thu, 11 Aug 2022 17:38:40 -0400 Subject: [PATCH] further clarification for foreground service push --- static/faq.html | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/static/faq.html b/static/faq.html index 4216394c..65e72191 100644 --- a/static/faq.html +++ b/static/faq.html @@ -1251,10 +1251,11 @@ (IMPORTANCE_LOW). It can be reduced to the lowest importance (IMPORTANCE_MIN) by the user if they set the notification channel to be collapsed which will collapse it in the notification tray and it won't show up as an icon in the - status bar or on the lockscreen anymore. A battery optimization exception is - also needed for the app to bypass device idle states and run while the device - is idle. If you can tolerate delays while the device is idle, then the battery - optimization exception isn't mandatory.

+ status bar or on the lockscreen anymore. Users can also disable the + notification and the foreground service will continue working. A battery + optimization exception is also needed for the app to bypass device idle states + and run while the device is idle. If you can tolerate delays while the device + is idle, then the battery optimization exception isn't mandatory.

FairEmail and Signal are examples of apps using the proper approach of a foreground service combined with an optional battery optimization exception.