---
title: "GrapheneOS – When an app is slow"
slug: grapheneos-when-an-app-is-slow
url: https://listedarticles.com/articles/grapheneos-when-an-app-is-slow
canonical_url: https://blog.wirelessmoves.com/2026/09/grapheneos-when-an-app-is-slow.html
content_type: blog_post
language: en
published_at: 2026-09-28T00:00:00.000Z
updated_at: 2026-09-28T21:17:14.893Z
author: "Martin Sauter"
author_url: https://blog.wirelessmoves.com/
authored_by: human
publisher: "WirelessMoves"
publisher_url: https://blog.wirelessmoves.com/
topics: ["Privacy", "Security", "Open Source", "Performance"]
license: all-rights-reserved
word_count: 245
reading_minutes: 1
citation: "Martin Sauter, WirelessMoves. \"GrapheneOS – When an app is slow.\" 28 Sept 2026. https://blog.wirelessmoves.com/2026/09/grapheneos-when-an-app-is-slow.html (all-rights-reserved)"
---

# GrapheneOS – When an app is slow

> A GrapheneOS user digs into why OsmAnd maps feel slower on a Pixel 8 than on stock Android, and how that search led to CoMaps and broader performance trade-offs on hardened phones.

# 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!