clarify background data usage restriction + FCM
This commit is contained in:
parent
ebdb522e61
commit
a4fd0bc923
@ -568,7 +568,7 @@
|
||||
<li>Sandboxed Google Play compatibility layer: allow Android Auto foreground services to have while-in-use permissions when wired and/or wireless Android Auto special permissions are granted by the user to fix voice commands in some cases</li>
|
||||
<li>Sandboxed Google Play compatibility layer: make Google text-to-speech app queryable by other apps in the same profile by default as it is on the stock OS since libraries using it don't declare the query explicitly (note apps and their libraries can declare any queries they want including for any app with a launcher activity and there's no approval along with there being other ways to detect apps)</li>
|
||||
<li>Sandboxed Google Play compatibility layer: show the notification for Play services not having Unrestricted battery usage enabled one more time for existing users since not having it now causes more severe delays FCM push messaging including notifications or more urgent events such as incoming calls to an app like Signal which uses FCM for this when available</li>
|
||||
<li>Sandboxed Google Play compatibility layer: add notification about Play services having background data usage restricted which will break FCM</li>
|
||||
<li>Sandboxed Google Play compatibility layer: add notification about Play services having background data usage restricted which will break FCM when only mobile data is available (no Wi-Fi access)</li>
|
||||
<li>Sandboxed Google Play compatibility layer: don't show battery usage notification for Play services when it has the Network toggle revoked since the user clearly doesn't want the functionality depending on Unrestricted background power usage</li>
|
||||
<li>Settings: opt-out of Android 15 edge-to-edge for the developer options app picker activity since it's not properly supported yet (upstream bug)</li>
|
||||
<li>Setup Wizard: avoid incredibly rare edge case crash (uncaught exception) when trying to disable OEM unlocking when it's already disabled and not allowed to be disabled by the carrier</li>
|
||||
|
Loading…
x
Reference in New Issue
Block a user