diff options
| author | Daniel Micay <danielmicay@gmail.com> | 2022-08-11 17:38:40 -0400 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2022-08-25 23:15:08 -0400 |
| commit | 5b9ca99537c32cb3c0da08800ec630ed4efd056f (patch) | |
| tree | dd55d950e45351140b515661490b9d69d91605b6 /static | |
| parent | d39543eeb6e0ccad0c8163a3685122043bef7f4e (diff) | |
further clarification for foreground service push
Diffstat (limited to 'static')
| -rw-r--r-- | static/faq.html | 9 |
1 files 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.</p> + 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.</p> <p>FairEmail and Signal are examples of apps using the proper approach of a foreground service combined with an optional battery optimization exception. |