Dumdum I'm using the legacy apps not the beta ones.
Thread for discussing app compatibility with the new exploit protection toggles.
- Edited
Here's the list of my applications I had to authorize because of a crash and a request.
DLC via memory :
-BoursoBank
-Google Play services
-Google Play Store
-Google Services Framework
-WhatsApp
DLC via storage :
-Android Auto
-Microsoft Authentificator
-Bandcamp
-BoursoBank
-Gboard
-Google play services
-Google Play Store
-Images Toolbox
-Google Maps
-Waze
-WhatsApp
Require DCL via memory :
- BanquePostale (French bank),
- BoursoBank (French bank) ==> seems to work in certain situations (?)
Notesnook.
fid02 WebView JIT or something else?
- Edited
Xtreix WhatsApp works without DCL via memory for me. Only needed DCL via storage
- Edited
DLC via memory :
BoursoBank (French bank)
CityMapper
FotMob
Google Play services
Spotify
Tor Borwser (Rather surprised)
Vanadium
Whatsapp
I've had no problems with Bitwarden, Google Play Store and Google Services Framework
How do these problems manifest themselves?
Stewart Browsers need DCL via memory to work from what I can see.
Stewart How do these problems manifest themselves?
Which problems? The ones regarding the apps you listed? If so,
Stewart Bitwarden
Legacy app requires DCL via memory to function. If you are using the new beta apps, then this is not needed.
Stewart Google Play Store and Google Services Framework
These apps require DCL via Storage if I understand correctly to load Dynamite Modules (something Google is planning on depreciating).
DCL VIA MEMORY RESTRICTED
Accrescent - works
Aegis - works
AppVerifier - works
Brave - crashes
Breezy Weather - works
Cheogram - doesn't crash, haven't tested receiving messages
Duo Mobile: works
Magic Earth: works
Obtainium: works
Orbot: works
Proton Calendar: works
Proton Drive: works
Proton Pass: works
Proton VPN: works
Signal: works
SimpleX: works
Spotify: crashes
Vanadium: works
Cryptee as Vanadium PWA: works
WhatsApp: A message displays that it tries to use DCL via memory, but works fine
DCL VIA STORAGE RESTRICTED
Accrescent: works
Aegis: works
AppVerifier: works
Brave: works
Breezy Weather: works
Cheogram: doesn't crash, haven't tested receiving messages
Duo Mobile: crashes
Magic Earth: works
Obtainium: works
Orbot: works
Proton Calendar: works
Proton Drive: works
Proton Pass: works
Proton VPN: works
Signal: works
SimpleX: works
Spotify: works
Vanadium: works
Cryptee as Vanadium PWA: works
WhatsApp: crashes
WEBVIEW JIT DISABLED
Accrescent: works
Aegist: works
AppVerifier: works
Brave: works
Breezy Weather: works
Cheogram: doesn't crash, haven't tested receiving messages
Duo Mobile: works
Magic Earth: works
Obtainium: works
Orbot: works
Proton Calendar: works
Proton Drive: works
Proton Pass: works
Proton VPN: works
Signal: works
SimpleX: works
Spotify: works
Vanadium: works
Cryptee as Vanadium PWA: works
WhatsApp: works
- Edited
Stewart Strange that Vanadium doesn't work for you. Vanadium (and a PWA through it) works fine for me with all the new settings toggled off.
For someone like myself who is not familiar with DCL, what is it and is it a privacy issue?
Cheers!
- Edited
Cold_Beer Read this: https://discuss.grapheneos.org/d/15395-grapheneos-version-2024083100-released
as well as towards the bottom of https://grapheneos.org/features#exploit-mitigations
ErnestThornhill Thank you.
SimpleX isn't working with DCL via storage restricted. Its crashes often.
kebab_definite
And Brave doesn't work without DCL via memory Allowed.
- Edited
kebab_definite Just like OP, SimpleX Chat runs fine for me.
ErnestThornhill interesting. There is also a github issue on simplex.
https://github.com/simplex-chat/simplex-chat/issues/4810
And a similar post like this treat on:
https://discuss.privacyguides.net/t/graphene-os-has-strengthened-its-security-many-day-to-day-programs-affected/20546
What did you do for DCL via storage? Did you restrict DCL on all apps and authorize it when the notification requested activation?