@MetropleX [GrapheneOS] ⚡🟣 @Vitor Pamplona
Just ran into a weird issue the past couple of days. I suddenly couldn't get Amethyst to connect with my Start9 relay using Orbot. It finally took turning on Exploit Protection Compatibility Mode in GrapheneOS to fix it. I switched EPCM back off and it's still connecting just fine. Haven't had an issue since. I have no idea WTF would've caused any of that, but knowledge is power, so now you know.
Very keep me appraised if you notice this regularly. If this fix is repeatable it usually speaks to a memory related issue. Is this using Orbot within Amethyst or standalone?
Orbot is installed alongside Amethyst, then connected within the app. I tried switching EPCM on Amethyst rather than Orbot because things like SimpleX were still working fine. It seemed confined to Amethyst. So far switching that on and off has fixed it. I almost literally just jiggled the handle.
hum... What's EPCM?
@MetropleX [GrapheneOS] ⚡🟣 would have to give you the fine details. I believe the point is to protect you from attacks involving memory. This is what it looks like in settings. GrapheneOS only, as far as I know.
https://i.nostr.build/eLEm.png
Exploit Protection Compatibility Mode is designed to allow apps that have memory related issues picked up by our hardening to run:
The exploit protection compatibility mode toggle will:
Switch from hardened_malloc to Android's standard allocator (Scudo
)
Reduce address space size from 48 bit to Android's standard 39 bit
Disable memory tagging, unless the app has opted-in to it (only on compatible devices)
Allow native debugging (ptrace) access
All of these changes apply only to the selected app and can be toggled separately.
I just had this issue again. I still can't isolate what's causing it, but we did have intermittent data service around the same time. I seem to remember that happening before as well. Might be something, might be nothing.
Oddbean new post about login | logout 