GrapheneOS – 当应用运行缓慢时
GrapheneOS – When an app is slow

原始链接: https://blog.wirelessmoves.com/2026/09/grapheneos-when-an-app-is-slow.html

在使用 GrapheneOS 一年后,作者发现由于该操作系统采用了“强化内存分配器”(hardened memory allocator),OsmAnd 地图应用运行速度明显慢于其他安卓设备。这一安全功能因不断加载和丢弃地图数据而产生了额外开销。 为解决此性能问题,作者建议针对 OsmAnd 单独禁用该保护功能。具体操作为:长按应用图标,选择“应用信息”,进入“漏洞保护”,然后关闭“强化内存分配器”。 尽管这会带来轻微的安全权衡,但作者认为对于几乎不联网的地图应用来说,这是可以接受的。按照上述步骤操作后,OsmAnd 的运行速度即可恢复正常。

这个 Hacker News 帖子讨论了地图应用 OsmAnd 在 GrapheneOS 上运行时的性能问题。许多用户报告了显著的卡顿,并将其归因于 GrapheneOS 的强化内存分配器。 虽然一些用户建议禁用此安全功能以提高性能,但另一些用户则争论该问题究竟是源于 OsmAnd 的代码(特别是其内存分配习惯),还是使用安全强化操作系统的固有权衡。这场讨论突显了 GrapheneOS 的严苛安全标准与主流应用实际兼容性需求之间更广泛的矛盾。 参与者还探讨了在没有 Google Play 服务的情况下运行某些应用的困难、Waze 和 OrganicMaps 等导航应用在该平台上的性能差异,以及主流 OEM 厂商与注重隐私的操作系统之间优先级的不同。最终,大家的共识是:用户必须在 GrapheneOS 的安全优势与现实情况之间取得平衡,因为某些应用(尤其是计算密集型应用)可能会受到该平台“安全至上”设计选择的影响。
相关文章

原文

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!

联系我们 contact @ memedata.com