summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2022-08-11 11:06:33 -0400
committerDaniel Micay <danielmicay@gmail.com>2022-08-25 23:15:08 -0400
commit81c87b669135b886f2a6f9704e0ea5ae69c91648 (patch)
treecc32f8acc749b1a9d0fcbeeb6bc65d666dbb1dab
parent5884da2ddb5873b70fdb1f2209092b32b5e4eb7f (diff)
clarify foreground service notification priority
-rw-r--r--static/faq.html13
1 files changed, 8 insertions, 5 deletions
diff --git a/static/faq.html b/static/faq.html
index 8d992d0e..4216394c 100644
--- a/static/faq.html
+++ b/static/faq.html
@@ -1247,11 +1247,14 @@
<p>In order to properly implement either push messaging or frequent polling
themselves, an app needs to run a foreground service. This is displayed as a
persistent notification. It will normally be marked as a silent notification
- with the lowest possible priority, so it will be collapsed at the bottom and
- won't show up as an icon in the status bar or on the lockscreen. 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>
+ with the lowest possible default importance for a foreground service
+ (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>
<p>FairEmail and Signal are examples of apps using the proper approach of a
foreground service combined with an optional battery optimization exception.