GrapheneOS Upstate1618 DCL storage restrictions are not enabled by default and show a clear notification when code loading is prevented. Play services dynamite modules are partially incompatible with DCL restrictions until they fully move them to split APKs. That's a known incompatibility. You should not enable exploit protection compatibility mode to work around this but rather don't enable the DCL storage restrictions for apps requiring it. You shouldn't disable the standard memory exploit protections.
other8026 I thought that the log viewer was around for longer than it has been, apparently. You can get logs by following these instructions: https://developer.android.com/studio/debug/bug-report#bugreportdevice
the0815 matchboxbananasynergy will the release that contains this fix also come to devices with legacy extended support (like 4a, 4XL) that multiple people reported the problem on in this thread?
matchboxbananasynergy the0815 Almost certainly not. Those devices are in legacy extended support and are very much on their way out. We've been at the point where people on these devices need to update to a support model for quite a while now.
bla Good news : My 4a just updated to TQ3A.230805.001.S1.2024092100 And built in maps seems to work ! - for now... Thank you to all grapheneos team!