GrapheneOS – When an app is slow

aucisson_masque•1 minute ago

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.

negative_zero•about 2 hours ago

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

BlackRabbit1•about 2 hours ago

CoMaps behaves very very weirdly on GrapheneOS. Same with OrganicMaps.

Osmand and GMaps are working fine.

Waze is almost melting the poor thing. Beside of that working fine.

subscribed•28 minutes ago

Osmand and OrganicMaps work flawlessly for me. Waze on 6 (not pro), works better than on my 9 Pro.

broodbucket•about 1 hour ago

Waze works perfectly fine for me

DuncanCoffee•about 1 hour ago

Anyone writing about apps compatibility should specify if it's with or without the play services

ThePowerOfFuet•about 1 hour ago

I use Comaps daily on GrapheneOS on a Pixel 8 Pro and it works great.

Groxx•about 2 hours ago

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

WalterGR•about 2 hours ago

https://news.ycombinator.com/item?id=45358216

Groxx•25 minutes ago

I mean OsmAnd - other mapping apps don't slow down anywhere near this much.

OSM-rendering apps are a fair bit more computationally-expensive than many apps, so I do expect them to show the allocator's cost more, but OsmAnd stands out quite starkly against every other app on my phone.

hadi77ir•about 2 hours ago

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?

pjmlp•about 3 hours ago

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

izacus•about 3 hours ago

Or maybe there's a reason why the mainline Android OEMs don't ship that allocator by default.

Groxx•about 2 hours ago

The fairly obvious answer here is "OEMs don't care about security because very few people will pay for it, either with $ or time". Benchmaxxing sells better.

izacus•about 2 hours ago

That's trivially provable as false.

pjmlp•about 2 hours ago

Because they cut costs on hardware and not all ship MTE enabled ARMs.

palata•about 1 hour ago

Maybe... legacy?

mohamedkoubaa•about 3 hours ago

There needs to be a wall of shame for apps that abuse hardware owned by users

yjftsjthsd-h•about 3 hours ago

How's it abusing anything? It's an Android app that works fine with the default Android memory allocator.

pjmlp•about 2 hours ago

The AOSP memory allocator is seldom the one used by OEMs.

perching_aix•about 2 hours ago

That doesn't necessarily mean it isn't being abusive, just that said allocator tolerates it okay.

RKearney•41 minutes ago

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

perching_aix•about 3 hours ago

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?

himata4113•about 3 hours ago

Seems unlikely, it's java so this is likely related to loading large amounts of objects and having the GC thrashing.

someonebaggy•7 minutes ago

C++ memory allocator choice probably wouldn't affect Java code, which has its own heap algorithms.

RedComet•about 2 hours ago

The core is C++ afaik.

GrapheneOS – When an app is slow

⚡ Community Insights

Discussion (34 Comments)Read Original on HackerNews