I just realized something: this camera sequence must suck for perspective jump between main and tele. I presume their choice came from thermals.

Looks like the emulated system of the new Android terminal feature runs on different TTL than host system, so net hostility measures that discriminate traffic on the basis of origin start to mess with terminal user just like with hotspot. Termux wins again ☺️

So Xiaomi wants people to pay twice the Chinese price for their European phone units. Then by using extreme measures in China, it makes sure that midrange devices are no longer worthy of import.
So you overpay just like you're expected to by buying in your local official distribution, just to be met with stuff like this. If nothing changes next year, the reliability of paid gray market bootloader unlock will vastly surpass the official method, no matter how hard you try. It's already the case. For many people, this section of Xiaomi Community app is already completely useless.
If they fully lock down their devices, at least no one will live with illusion that they're unlockable for free.

Soooo...
It works without GMS, at least the version from AppGallery. I can't say anything about any potential hardware attestation requirement, but it seems increasingly likely that we end users have a skill issue. The checker inside the app is most likely mad about the indicators snitched directly by device (bootloader, TrustZone?) itself, humbly passed by the affected Android ROMs.

The irony is usual: it'll work on a rooted device with proper hiding or worst possible tasteless ROM, but won't work on the proud official distributions of most popular projects, as they choose not to spoof the state of device, letting app vendors weaponize their own honesty against them.

For reference, the test was conducted in work profile of bl locked Motorola S50 Neo, with Google Services disabled and the SPIC result confirming that.

For some example:
https://source.android.com/docs/security/features/verifiedboot/boot-flow#locked-devices-with-custom-root-of-trust

Your device will snitch by default that your AVB is yellow rather than green, if you're using Graphene with locked bootloader just like you were guided to.

Happy Holy Innocents' Day 😝

https://en.wikipedia.org/wiki/April_Fools%27_Day#28_December

Attention seeking chiteroman and all the gullible parts of Android community falling for it – vol. XX

As much as my recommendation is to purge any apps reliant on PIA from your life, I hope you'll remember to keep distance with any of his claims. Thanks.

(Context: yet another "final end of Play Integrity bypass")

TIL:
On Firebase Cloud Messaging (the most popular way of providing notifications to apps without keeping them up 24/7), the end-to-end encryption (the only one where notification content is invisible to Google) is optional and implementation-dependant. Telegram (and I presume most of the popular chat apps) seems to have done its homework, but literally nothing stops an app vendor handling your personal information to pass it carelessly in plaintext through Google servers.

If you're using Gmail... don't worry.

Update:
It doesn't look like it! I'm afraid that we're seeing something more nefarious – a check for custom ROMs specifically. I had no issue in orange state (even "riskier" than yellow, stands for unlocked bootloader) while on stock ROM. PIA was at basic integrity.

Take this, Fairphone! This is what I call commitment to recycling!

If you don't believe me, try your luck. And certainly do that before you buy.

Google is so scared of people flashing their Pixel 4a with builds that don't include their still unexplained battery blow-up prevention, that they removed downloads of every other build. They wouldn't do that even while Pixel 6 bootloader antirollback made flashing of Android 12 builds impossible.

Louis is a long talker, but if you need more reference, check his vid or P4a Reddit.
https://www.youtube.com/watch?v=Xboo6sV-cJU
https://www.reddit.com/r/Pixel4a/

Right..?