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 noticeably slower on one Pixel 8 running GrapheneOS and improved after the user disabled the hardened memory allocator for that app. The report describes a single-device experience; it does not establish how widespread the slowdown is or independently measure the performance and security effects.
A GrapheneOS user reports that the OsmAnd mapping app ran noticeably slower on their Pixel 8 than on other Android devices, and that disabling the app’s hardened memory allocator made it run faster again. The report describes a per-app setting and a trade-off: turning off this protection may reduce security for OsmAnd.
The account, published by WirelessMoves in September 2026, is based on the writer’s experience after using GrapheneOS for about a year. The writer says OsmAnd was the one app that felt noticeably slower on their Pixel 8 than on other Android devices. They suspected repeated loading and discarding of map data during scrolling could contribute to the slowdown, but did not present measurements or confirm that explanation.
The writer says they found the hardened memory allocator was responsible for the performance problem on their device. They report that switching it off for OsmAnd and restarting the app made it “much faster again.” GrapheneOS allows this protection to be changed for an individual app through its app information and Exploit protection settings, according to the post.
The change does not disable the protection across the phone: the writer advises leaving it on generally and turning it off only for OsmAnd. They acknowledge a security drawback, and say the trade-off suits their use because OsmAnd does not load internet content apart from occasional map updates. That rationale is the writer’s assessment, not an independently verified security evaluation.
Speed Comes With a Security Trade-Off
The report illustrates a practical choice for GrapheneOS users when a specific app performs poorly: the operating system provides a way to adjust an exploit protection for that app rather than changing the setting system-wide. In this case, the writer says the adjustment improved map use on one phone.
Disabling a memory protection can also reduce defenses against some forms of exploitation. The post does not specify which threats would be affected in this particular configuration, nor does it assess OsmAnd’s exposure. Users considering the setting have to weigh their own use of the app and the security cost; the report is not evidence that the change is risk-free or appropriate for every user.
One Phone, One Mapping App
The writer says they had used GrapheneOS for roughly a year and remained happy overall with its security and privacy features. The slowdown described concerns OsmAnd, an Android mapping app, on a Pixel 8 running GrapheneOS; it is not presented as a general performance finding about the operating system or all mapping apps.
The experience also led the writer to try other Android map applications. They say CoMaps met almost all of their needs, while they still wanted to use OsmAnd occasionally. The post offers this as personal context rather than a comparative review of the two apps.
“After restarting Osmand, it is much faster again!”
— WirelessMoves blog author
How Broad Is the Slowdown?
The report covers one user’s Pixel 8 and does not say whether other GrapheneOS users, devices, or OsmAnd versions show the same slowdown. It gives no timing benchmarks, controlled comparisons, or details of the device configuration beyond the operating system and phone model.
The proposed link between the allocator and the slowdown is presented as the author’s finding, while the explanation involving map-data loading is framed as a possibility. The post does not include an independent technical analysis, quantify the security reduction, or establish whether an OsmAnd update or GrapheneOS change could address the performance issue without disabling the protection.
Further Testing Would Clarify the Cause
The account does not announce a planned investigation or a response from GrapheneOS or OsmAnd developers. To establish whether the issue is widespread, further reports or reproducible tests across devices and software versions would be needed. Such comparisons could also help distinguish the allocator’s effect from other causes of app performance.
For now, the only next step described is restarting OsmAnd after changing its per-app setting. The author advises keeping exploit protection enabled generally, but the report does not provide official guidance on the security consequences. Users seeking a definitive recommendation will need information from the project developers or a more detailed security assessment.
Key Questions
What slowdown did the report describe?
The WirelessMoves author said OsmAnd felt noticeably slower on their Pixel 8 running GrapheneOS than on other Android devices. The post provides no benchmark results.
What change did the author say improved performance?
The author disabled OsmAnd’s hardened memory allocator in the app’s Exploit protection settings and restarted the app. They reported that it then ran much faster.
Does the report show that all GrapheneOS users have this problem?
No. It describes one user’s experience on one Pixel 8. The post does not establish how often the slowdown occurs on other devices or software versions.
What is the trade-off?
Disabling the hardened memory allocator removes that protection for the selected app, which may reduce its defenses against exploitation. The post does not quantify the change in risk or establish that it is safe for every user’s circumstances.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
