What is the point of this hardening feature if you got to disable it ?

You can tweak Android as much as you want, the OS was not made to be private nor secure. App developers will never check if it breaks the grapheneos memory allocating feature (amongst others) so by default you disable it.

Anyway it also requires the app to be able to even run on a rom that doesn’t respect play integrity.

Odd. Google Pixel 7 with GrapheneOS here. OsmAnd works perfectly fine for me without disabling any exploit protection options.

Huh. Yeah, it is noticeably faster on my 9a with that disabled. I wonder what they're doing differently...

I wonder if a website using leaflet.js has better or worse performance in the said case. If it does better, then maybe the problem is on OsmAnd's side?

Maybe the actual solution is to improve, replace the application.

"Before installing, please turn off all anti-virus and firewall software."

If you have two apps, both maps...

> 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.

... is this really the right hunch, over e.g. the OpenStreetMaps app lacking in discipline with its heap allocations?

[flagged]