Improve FetchPushForegroundService's reliability (#6757)
* Improve `FetchPushForegroundService`'s reliability - Don't use DI, we can just create the notification channel. This should speed up the creation of the service and reduce the number of `ForegroundServiceDidNotStartInTimeException` received. Also use `MainScope` instead of the app's coroutine scope. - Move the wakelock releasing mechanism to `onDestroy` so it's always used. Previously, this would only happen when `stopService` was called, which would only happen when `stopSelf()` is called, but not when the OS or the service manager stops the service. * Add fallback value for the notification channel title * Replace the wrong string for the notification/channel title --------- Co-authored-by: Benoit Marty <benoitm@element.io>
This commit is contained in:
parent
11476c73cf
commit
77b444581d
22 changed files with 60 additions and 62 deletions
|
|
@ -197,7 +197,6 @@
|
|||
<string name="common_advanced_settings">"高度な設定"</string>
|
||||
<string name="common_an_image">"画像"</string>
|
||||
<string name="common_analytics">"分析"</string>
|
||||
<string name="common_android_fetching_notifications_title">"通知を同期中…"</string>
|
||||
<string name="common_android_shortcuts_remove_reason_left_room">"あなたがルームを退出"</string>
|
||||
<string name="common_android_shortcuts_remove_reason_session_logged_out">"セッションからログアウトされました"</string>
|
||||
<string name="common_appearance">"テーマ"</string>
|
||||
|
|
@ -243,6 +242,7 @@
|
|||
<string name="common_failed">"失敗"</string>
|
||||
<string name="common_favourite">"お気に入り"</string>
|
||||
<string name="common_favourited">"お気に入り"</string>
|
||||
<string name="common_fetching_notifications_title_android">"通知を同期中…"</string>
|
||||
<string name="common_file">"ファイル"</string>
|
||||
<string name="common_file_deleted">"ファイルを削除しました"</string>
|
||||
<string name="common_file_saved">"ファイルを保存しました"</string>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue