security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

clarify foreground service notification priority

Browse Source
This commit is contained in:
Daniel Micay 2022-08-11 11:06:33 -04:00
parent 5884da2ddb
commit 81c87b6691
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
static/faq.html
View File

@ -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.