On a number of apps I download when I try to activate them, I am informed I need to grant accessibility permission. I then get the same warning - “If you turn on app name, your device won’t use your screen lock to enhance data encryption”
What enhanced data encryption will I lose, and is there any way around this for me, or can the app developer do anything?
Do all apps that require accessibility affect screen lock encryption, if not, is there anyway to see which apps are affecting it?
as some accessibility services aren’t started for the early-boot fulldisk encryption (“fde”) pin-entry, the pin gets removed out of consideration for people needing to interface at all times e.g. with a bluetooth connected device. This info is already a few years old: you can re-enable the pin/password-enhanced disk encryption again through the settings.
I guess for file based encryption (“fbe”) this limitation no longer applies. See the bottom of the issue at google - Google Issue Tracker
For users who don’t need the accessibility services at boot, the steps in this comment worked for me: Google Issue Tracker. Just temporarilly accept the decreased security when enabling a new accessiblity service, then immediately go to reset your pin. Even if you’re setting it to the exact same pin you were already using, you’ll be prompted to reenable the enhanced encryption.
So the pin request shows lock screen encryption is working fine?
I don’t understand your question clearly - if you go to the pin-settings and it says already set, then the Warning by the app is moot and can be ignored
I see. It would appear then that e/OS is lagging behind Android, in not offering File-based encryption. So I think you should not use my app (or any other app using accessibility services) if you want to keep encryption. Or maybe you can inquire with the makers of e/OS why this message still appears in e/OS, but not in Android 10 and up (for which the app is designed)
