Banking App Won't Open?
Crashing, stuck loading, or throwing a device error. Here's the fix, matched to what you're actually seeing.
Most Australian banking apps run fine on GrapheneOS with Sandboxed Google Play. When one doesn't, it's almost always one of a small number of known causes — not a sign the device is fundamentally incompatible with banking.
Find your symptom below for the fastest fix, or work through the general checklist further down if nothing matches exactly.
Match your symptom
App crashes immediately on launch
Likely cause: Most often GrapheneOS's hardened memory allocator (hardened_malloc) conflicting with how the app was built. This is the single most common cause of an instant crash.
Fix: Settings → Apps → [app name] → Exploit protection compatibility mode → On. Relaunch the app. This relaxes memory hardening for that one app only, leaving every other app on the device fully hardened.
"Device not supported" or "Rooted device detected"
Likely cause: The app's Play Integrity check is failing — usually because Sandboxed Google Play isn't fully set up, not because the device is actually rooted (GrapheneOS never roots the device).
Fix: Confirm all three components are installed in the profile: Google Play Services, Google Play Store, and Google Services Framework. Open Play Store once and let it finish its own setup. Then confirm Play Protect is enabled in Play Store settings.
Stuck on a loading spinner or blank screen after login
Likely cause: Often a stale sandboxed Play Services session, or the app failing to get a background network permission it expects silently.
Fix: Force-stop the app (Settings → Apps → [app name] → Force stop), then check its permissions include network access. Restart Sandboxed Google Play in the background: Settings → Apps → Google Play Services → Force stop, then reopen the banking app.
Push notifications for transactions aren't arriving
Likely cause: Google Play Services needs background network and battery-unrestricted permissions to maintain the notification channel — GrapheneOS's per-app controls mean these aren't automatically granted the way they are on stock Android.
Fix: Settings → Apps → Google Play Services → Permissions → confirm background network access is allowed. Also check battery optimisation isn't restricting it: Settings → Battery → Unrestricted for Google Play Services.
App installs but won't even open the login screen
Likely cause: Incomplete or corrupted install, frequently from installing before Play Store had finished its own first-time setup.
Fix: Uninstall the app entirely, restart the device, open Play Store and wait until it's idle (no pending updates), then reinstall the banking app fresh.
General checklist, in order
If your symptom didn't match anything above, or the fix didn't work, work through this list in order — most issues resolve by step two or three.
- 01
Confirm Sandboxed Google Play is fully installed
Open the GrapheneOS Apps repository and verify Google Play Services, Google Play Store, and Google Services Framework are all present and up to date. Missing even one of these causes most of the symptoms above.
- 02
Enable exploit protection compatibility mode for the specific app
Settings → Apps → [app name] → Exploit protection compatibility mode → On. This is the single highest-hit-rate fix and worth trying even if the symptom doesn't obviously look memory-related.
- 03
Check your Verified Boot status
Settings → About phone → Device identifiers → Verified boot state. It should read "Boot verified". If it shows anything else, the device's integrity attestation will fail for every banking app — this is rare but worth ruling out first if multiple apps are affected at once.
- 04
Check for a GrapheneOS update
Settings → System → System update. App compatibility issues sometimes trace back to a GrapheneOS patch that's already been released — updating resolves the issue without any further changes on your end.
- 05
Try the app in a separate user profile
If nothing above resolves it, install Sandboxed Google Play and the app fresh in a second user profile (Settings → System → Multiple users → Add user). This isolates the app completely from anything in your main profile that might be interfering, and often clears persistent issues outright.
- 06
Contact us
If you've worked through all of the above and the app still won't run, contact us. We actively test and track banking app compatibility issues, and if it's a known, unresolved issue on the bank's side, we'll tell you honestly rather than have you keep troubleshooting something that isn't fixable client-side.
Frequently asked questions
- Why did my banking app suddenly stop working after it was fine for months?
- The most common cause is an app update on the bank's side that changed its integrity checks or added a new permission requirement. Check for a GrapheneOS update first, then work through exploit protection compatibility mode — this covers the majority of sudden breakages.
- Is my device actually rooted if I see a 'rooted device detected' error?
- No. GrapheneOS never roots the device — root access is deliberately excluded from the entire project. This error message is almost always a Play Integrity check failing because Sandboxed Google Play isn't fully configured, not an actual root detection.
- Does reinstalling the banking app lose my saved data or settings?
- Uninstalling and reinstalling clears the app's local data, but your account itself lives with your bank — you'll simply log back in. Any local-only settings, like saved biometric login preferences, may need to be reconfigured after reinstalling.
- Will this happen again after I fix it?
- Occasionally — app updates on the bank's side can reintroduce compatibility issues. It's uncommon for the same app to break repeatedly for the same reason. If you're a SOVEREIGN customer and it becomes a recurring problem with a specific app, contact us — we track this and will tell you if it's a known pattern.
- Should I just avoid banking apps that don't work?
- Most Australian banking apps work correctly on GrapheneOS with Sandboxed Google Play — see our full compatibility guide for what's confirmed working. A single app having a transient issue doesn't indicate GrapheneOS is generally incompatible with banking.
Still stuck?
If you've worked through the checklist and it's still not resolved, contact us — or if the phone needs a clean reconfiguration, our reconfiguration service rebuilds it from scratch.
Last updated: July 2026. Compatibility and fixes may change with app updates on the bank's side. If you find outdated information, contact us and we'll correct it.