Is Ingress Prime working on /e/OS 3.3 for other people?

[narium]

Hello, I’m new here, I hope this is the right place to ask

I’m testing a Fairphone 6 with /e/OS 3.3 with all options in microG allowed. I could install Ingress Prime with App Lounge and I can login (with a gmail account…) but then I get the message “Ingress is not supported on this device configuration“.

I could find some old posts about ingress compatibility, but not much recent ones. And Ingress is missing from the list [LIST] Apps that work or do not work with microG . The only recent post I could find (November 2025) suggests that Ingress worked with some version of /e/OS < 3.2 (the post doesn’t tell the exact version) but stopped working with 3.2: Feedback for v3.2 - #219 by Batsylph

So I’m curious if other people (agents as they are called in Ingress) have gotten Ingress working, and what measures/hacks/workarounds were needed.

I have other banking apps and other games working, but Ingress is known to be picky, probably to avoid GPS spoofing.

Thx!

[tcecyk]

I looked at a provided logcat a year+ ago. if Auth Result not handled: GooglePlayNotReady still comes up in a current log that is Unity complaining about its environment it runs in

Using Ingress Prime on /e/ phone

there’s a few auth related failures, not sure which one does bring it all to a halt in the end - to get a fitting report in microGs bugtracker is looking for some of the error messages or common libraries (as Unity). You could put the logcat up at Can't log in to Ingress Prime with Google · Issue #990 · microg/GmsCore · GitHub as the last log is from 2019 I think the lines preceding any “<pid> <pid> E Unity ..” helps categorizing Auth Result not handled: GooglePlayNotReady

[Batsylph]

Hello, it’s Batsylph, my ingress app is working fine now. I dont know what happened in november. For me, it didn’t work for about 4 days… after that all went fine.

My phone is a Fairphone 5, working (now) on /e/ OS 3.3-a15-20251210556408-official-FP5.