TL;DR
Get the latest gadgets delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
A September 2026 blog post reports that OsmAnd ran slowly on its author’s Pixel 8 with GrapheneOS and became faster after the author disabled the hardened memory allocator for that app. The post describes a per-app setting and acknowledges a security trade-off; it does not establish that the allocator causes slow performance for other users or devices.
The account, published by Wireless Moves, is based on the author’s experience using GrapheneOS for about a year. The author reported that OsmAnd, an Android mapping app, performed more slowly on a Pixel 8 running GrapheneOS than on other Android devices. After looking into the issue, the author attributed the slowdown to the operating system’s hardened memory allocator, which they said imposed significant overhead for OsmAnd.
The post proposes a possible explanation: map scrolling repeatedly loads and discards data, which may interact with the allocator’s protections. That explanation is the author’s hypothesis; the post does not include technical measurements or an independent investigation. The author reports that turning off the hardened memory allocator for OsmAnd and restarting the app made it run “much faster again.”
The described setting is under the app’s information screen, in Exploit protection. The author says to leave protection enabled generally and disable only the hardened memory allocator for OsmAnd. This is a user’s account of a setting and its result, not a GrapheneOS recommendation or a verified fix for every slow app.
A Per-App Speed and Security Trade-Off
The report highlights a choice users may face when troubleshooting an app that appears slow on a security-focused operating system: a setting intended to add protection may, in some circumstances, carry a performance cost. In this user’s case, the reported improvement followed disabling one protection for one app, while leaving the setting enabled elsewhere.
The change also has a security cost. The author acknowledges that disabling the hardened memory allocator reduces protection for OsmAnd, and says the trade-off was acceptable for their use because the app does not load internet content apart from occasional map updates. That is the author’s assessment, not a guarantee that the app is risk-free or that the same decision suits other users. Readers considering the setting should weigh the performance they observe against the protection they give up.
The Report Comes From One Pixel 8
The author says they had used GrapheneOS for about a year and were happy overall with its security and privacy features. The performance issue they describe was specific to OsmAnd on their Pixel 8; they compared its speed with the app on other Android devices but did not identify those devices or provide test conditions.
The search for an alternative led the author to CoMaps, which they said met almost all their needs. They still wanted to use OsmAnd occasionally, prompting further troubleshooting. The post presents the allocator setting as the explanation they found, but does not say whether the finding was confirmed by GrapheneOS developers or OsmAnd’s maintainers.
Cause and Wider Effects Unverified
The post does not include timing measurements, diagnostic logs, or tests isolating the allocator from other possible causes of the slowdown. Its proposed link between map data handling and allocator overhead remains an explanation offered by the author, not an independently established cause.
It is also unclear whether other GrapheneOS users, Pixel models, or versions of OsmAnd would show the same behavior. The source does not specify the software versions tested or report input from GrapheneOS or OsmAnd developers. The security impact of changing this setting is acknowledged in general terms, but the post does not quantify it or assess the app’s exposure in detail.
Users Can Compare App Performance
The account offers a setting readers can inspect if OsmAnd is slow on their own device, while making clear that the change reduces a protection for that app. Users can compare performance before and after restarting the app, but one person’s result does not establish a general fix.
No developer response, formal investigation, or planned software change is described in the source. Whether the reported overhead can be reproduced or addressed without disabling the allocator remains unknown.
Key Questions
What made OsmAnd slow in the report?
The author attributed the slowdown on a Pixel 8 running GrapheneOS to the hardened memory allocator. The post offers map data loading and discarding as a possible reason for the overhead, but does not provide measurements confirming that explanation.
What change did the author make?
The author disabled the hardened memory allocator for OsmAnd in the app’s Exploit protection settings, then restarted the app. They reported that it felt much faster afterward.
Does disabling the setting reduce security?
Yes. The author explicitly describes a security drawback from turning off the allocator for the app. The post does not quantify the risk, and the author’s personal assessment should not be treated as a guarantee of safety.
Is this a confirmed fix for all GrapheneOS users?
No. The report describes one user’s experience with OsmAnd on a Pixel 8. It provides no benchmark, independent confirmation, or evidence that other devices and app versions will behave the same way.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
