// HACKER NEWS — CYBERSECURITY
GrapheneOS – When an app is slow
I’ve been using GrapheneOS for about a year now and overall, I am very happy with the security and privacy features. There is one app, however, that runs noticeably slower on my Pixel 8 with GrapheneOS than on other Android devices: OpenstreetMap for Android (Osmand). The good side of this is that it has made me look for other map applications on Android, and I’ve found CoMaps that meets almost all of my needs. But still, I’d like use Osmand every now and then as well. So after looking around a bit, I found the reason behind why it is so slow on GrapheneOS and how to ‘fix it’.
The reason behind it is the hardened memory allocator, which seems to create a significant overhead for Osmand. That might be because scrolling a map requires constant loading and discarding of data. The good news: The hardening can be deactivated on a per-app basis! And once switched it off, Osmand runs as fast again as ever.!This comes with a security drawback, however, but since Osmand is not loading anything from the Internet apart from the occasional maps update, the security vs. speed equation works for me.
To disable the hardened memory allocated, long-tap on the program icon, select ‘info’ and then scroll down to ‘Exploit protection’. Leave the protection on in general, just disable the ‘hardened memory allocator’. And that’s it! After restarting Osmand, it is much faster again!
Well finding this is timely. Waze was killing the battery on my Pixel 10a with GOS on it. I was using it through Android Auto, and the charger I was using in the car could barely keep up. And the phone got quite warm. I should disable memory hardening to see if that improves things.
This is also a good reminder to experiment with CoMaps and Omsand. I typically only install Waze when I’m on a road trip, so it slips my mind.