← All Guides

App Compatibility Fixes

Most apps work on GrapheneOS without any modification. When an app does not behave as expected, there is usually a specific, identifiable reason — and a targeted fix. This guide provides a disciplined troubleshooting sequence. The fundamental rule: make one change at a time, test, then proceed. Changing multiple things simultaneously makes it impossible to determine what actually resolved the issue and risks introducing new problems.

Why it matters

App compatibility is the most common concern for people transitioning to GrapheneOS. The instinct when something breaks is to start disabling security features or granting broad permissions. That approach trades your security posture for convenience — often unnecessarily. In most cases, the fix is far more specific: an update, a single permission, a cache clear, or a targeted exploit protection toggle for one app. A methodical approach preserves your device's security while getting the app working.

The troubleshooting sequence

Follow these steps in exact order. Do not skip steps, and do not combine them. Each step addresses a different potential cause. Stop as soon as the problem is resolved.

1. Update GrapheneOS to the latest version. Go to Settings > System > System update. Check for and install any available update, then reboot. Compatibility improvements and bug fixes are included in regular releases. Running an older version means you may be troubleshooting a problem that has already been solved.
2. Update the problem app to the latest version. Open the app store you installed it from (Google Play Store, F-Droid, Aurora Store, or the developer's website) and check for updates. App developers frequently release fixes for compatibility issues. If you sideloaded the APK, download the latest version from the official source.
3. Check whether the app requires sandboxed Google Play. Many apps depend on Google Play services for push notifications, in-app purchases, location services, or authentication. If Google Play services are not installed — or are installed in a different profile — the app may crash, fail silently, or behave unpredictably. Install sandboxed Google Play in the same profile where the problem app runs. Go to Apps > Google Play Store (if available) or install via the GrapheneOS App Store.
4. Review app permissions. Some apps crash or refuse to function when denied permissions they expect to have — even if those permissions are not strictly necessary. Go to Settings > Apps > [app name] > Permissions. Review which permissions are denied. Grant only those that are clearly relevant to the app's function. For example, a messaging app may need notification and contacts permissions to function properly but should not need camera access unless you use its camera feature.
5. Clear the app cache. Go to Settings > Apps > [app name] > Storage > Clear cache. This removes temporary files that may have become corrupted. It does not delete your account data, login state, or settings. This is a safe, non-destructive step.
6. Clear app data. Go to Settings > Apps > [app name] > Storage > Clear storage. Warning: this resets the app to a fresh-install state. You will need to log in again and reconfigure settings. Use this step when the app's stored data appears to be the problem — for example, if the app crashes immediately on launch but worked previously.
7. Check exploit protection compatibility settings. Go to Settings > Apps > [app name] > Exploit protection. GrapheneOS applies several hardening features on a per-app basis, including memory tagging, native code hardening, and other exploit mitigations. Some apps — particularly those using older or non-standard code — may crash when certain protections are active. If the app is crashing, try toggling individual exploit protection settings for that specific app. Change one toggle at a time and test the app after each change. When the app works, you have identified the specific protection that conflicts. Critical: exploit protection toggles are per-app. Changing them for one app does not affect any other app on the device. Never seek out a way to disable these protections globally.
8. Check community reports. The GrapheneOS community maintains discussion forums and compatibility information. Search the GrapheneOS discussion forum (discuss.grapheneos.org) for the specific app name. Others may have encountered and solved the same issue. Documented workarounds save time.
9. Try the app in a different profile. GrapheneOS supports multiple user profiles, each with independent app installations and configurations. Create a new profile, install the app there — with or without Google Play services, depending on what you are testing — and see if the behaviour changes. This isolates whether the problem is profile-specific or device-wide.
10. Accept that some apps will not work. A small number of apps perform device integrity checks, require proprietary system-level access, or use techniques that are incompatible with GrapheneOS by design. Some banking apps, corporate MDM apps, and DRM-heavy media apps may fall into this category. When an app fails after exhausting every step in this guide, the limitation is on the app vendor's side. Check if the vendor offers a web-based alternative.

Best practices

• Always test after each individual change. This is the single most important habit for effective troubleshooting.
• Document what you change. If you toggle an exploit protection setting or grant a permission, note it. If you later need support help, this record is valuable.
• Prefer apps from F-Droid or direct APK downloads from developers when possible. These versions often have fewer dependencies on Google Play services.
• Keep a minimal Google Play footprint. Install sandboxed Google Play only in profiles where apps require it. There is no need to install it everywhere.
• Before granting a permission, ask whether the app genuinely needs it for the function you use. A navigation app needs location. A note-taking app does not.

Common mistakes

• Disabling all security features to make one app work. This is disproportionate. If an app requires you to strip your device's security, the app is the problem — not the device. Use targeted, per-app adjustments only.
• Installing Google Play services in every profile. Each installation of sandboxed Google Play adds background processes and network activity. Install it only where needed.
• Not checking community resources. The GrapheneOS community is active and well-documented. A five-minute search often surfaces an exact solution.
• Giving up too early. Steps 1 through 6 resolve the vast majority of compatibility issues. If you stop at Step 2 and conclude the app is broken, you may miss a simple fix.
• Making too many changes at once. If you clear data, change three permissions, toggle two exploit protections, and reinstall Google Play simultaneously, and the app then works — you have no idea which action was relevant. Next time the issue recurs, you are back to guessing.

Reality check

GrapheneOS is compatible with the vast majority of Android apps. The sandboxed Google Play implementation provides access to apps that depend on Google services without granting those services the privileged system access they receive on stock Android. However, compatibility is not absolute. Apps that perform attestation checks expecting a stock operating system, or that require system-level integrations GrapheneOS intentionally restricts, may not function. This is a conscious trade-off in favour of user security and control. In most cases, a web-based version of the service is available as an alternative.

App compatibility troubleshooting on GrapheneOS is methodical, not mysterious. Follow the sequence, make one change at a time, and let each test result guide your next step. Most issues resolve within the first six steps. When they do not, exploit protection toggles and community resources cover the remaining cases. The goal is always the same: get the app working with the minimum necessary change to your security configuration.