flawedworld
flawedworld
It sounds like the code path within AOSP for under display fingerprint is checking for biometric unlocking support in an odd way.
We want to completely replace Seedvault with our own backup app. That will likely be taken care of there.
>b) There seems to be no seedvault backup of the clock app "com.android.deskclock". --> Please include the settings of this standard app in the backup list. We could look into...
This is due to Google shipping a proprietary fork of PermissionController [com.google.android.permissioncontroller] and AOSP uses [com.android.permissioncontroller]
Quad9 Quad9 ECS OpenDNS CleanBrowsing
Hi @ao-anssi we would be interested to evaluate this and adapt your changes. Please link the app/changes here when possible.
@loryeam ye
Is this still an issue?
Please check if this is still an issue on the 2022042000 release
So it's only broken in secondary profiles, not the Owner profile now?