Adding a second data point to the LV1000 report above, with a control.
Pixel 8 Pro, 9 Nov 2026, current GrapheneOS, locked bootloader. myID from the Play Store in a secondary user profile with sandboxed Google Play.
- Set-up with the existing email and document checks: fine.
- Face check for Strong: LV1000 seven times out of seven. Glasses off, mobile data and Wi-Fi, full brightness, and with exploit protection compatibility mode on for the app. No change.
- Skipping the photo and finishing at Standard works, and login codes arrive within a minute. But if your identity was ever Strong, the ATO refuses a Standard sign-in, so for me that was a dead end.
From logcat during one failing attempt: the face check is the iProov liveness SDK. The camera opens, the SDK connects, capture runs to 99% ("Submitting your photo"), and the failure comes back about a second after upload with reason "Try again" and feedback code "unknown". So the refusal is made server-side after the capture is sent, not by an on-device check. I saw no Play Integrity or key attestation call in the log during the check, but I had no known-good capture to compare with, so treat that as unproven.
The control: next day I flashed the same phone back to stock Android 17. The face check passed first time and Strong was restored.
So on this phone the only variable was the OS. That matches the reports of iProov checks failing on GrapheneOS in other countries since mid-2026 (thread 37884). I have reported it to myID through their feedback form and asked them to document LV1000 and say whether GrapheneOS is blocked. That form is an anonymous survey and says they cannot respond, so I am not expecting an answer. I will post here if anything changes.