google disabled legacy play integrity, now i got this

Btw, now stock ROM + Locked BL will only give Device now
https://www.tgoop.com/trrflexgroup/178232

A lot of people have questions that I'm going to try to clarify here:

- Google already warned about this, and you all should have been prepared.
- No, you can't create your own keybox, so stop sending weird scripts in the chat because none of them will work for you. All keyboxes are created by Google (as they are the only ones with the private key to generate them) and distributed to the various OEMs.
- PlayIntegrityFix is 50% "obsolete"; it's still "working," but it needs another workaround to get the Device verdict (e.g., TrickyStore).
- No, I'm not going to share any keyboxes. There are already many channels dedicated to this, and all they'll accomplish is getting all those keyboxes revoked. Then come the regrets...

I'm not sure whether to continue with the module... Google keeps putting up more and more obstacles, and it's quite exhausting having to search for solutions that will end up being useless in a few months... 😭

The End Of The STRIX Chronicles

ReSTRIX 20250512 EOL For MIUI (KSUN only)
STRIX-Revived 20250520 EOL For AOSP (NoSU only)

Changelogs:
ReSRTIX-MIUI: Fixed the heating issues (if I remember correctly) of the previously leaked 20250510 build and other changes I forgot
STRIX-Revived-AOSP: Same as 20250323 but with the new bpf changes to boot A16 QPR1.

I am done with STRIX base now and I don't wanna mess or deal with it anymore. I'd like to move on and do something I'd wanted to do for a long time. ReSTRIX is a failed experiment to me and is not what I wanted to do.
I don't care about the fate of STRIX now.

Stay tuned for whatever next now if you care

Wanna enable bypass charging on kernels that have it implemented (including the last 2 (0510 and 0512) ReSTRIX builds 👀) but don't wanna install RvKernel Manager just exclusively for bypass charging?
Well, here's a alternative to that you can setup via FKM:

Open FKM > Burger Menu > Kernel Settings > Custom Tunables >Add a new tunable > Enter file path
Enter (or copy and paste) the following path:
/sys/class/power_supply/battery/input_suspend
And then simply, when you want to enable bypass charging, change the value from 0 into 1

Source (as well as including another path to try if the one in this message is not found)

Btw, LN8000 really REALLY hates bypass charging
Like it works when enabled, but the moment you disable bypass charging, whilst still connected to charger, expect slow charging and/or disconnect and reconnect spam until you unplug and replug the cable (This behavior could differ between kernels)

There ya have it folks!
Even stock ROM + locked BL on A12 won't give you strong integrity
Google REALLY wants you to upgrade more than Xiaomi does kek

Just a survey (and yeah, channel discussion is temporarily back for this)

Do you enjoy the kernel rain going on in sweet channels? And how do you feel about their quality/performance/bugs/etc?

everyone, find the cat!

I've decided to discontinue the PIF project.

Google is increasingly putting up more obstacles, and I no longer have as much time to dedicate to this as I used to. It's been a very interesting journey, and I've learned a lot. I thank everyone who has accompanied me and contributed to the project.

But things seem to be getting worse, and Google is going to make it even harder to use its services (GMS) on devices with an unlocked bootloader.

As an alternative, you can use PlayIntegrityFork.

Farewell.

Android used to be a playground for power users. Now it’s a locked-down joke. Unlock the bootloader and apps break, features vanish, and you're treated like malware. No one’s getting hacked because of this it’s just bad engineering and anti-user policy.
UX gets worse every year. Bloat, ads, broken updates and no way to fix it.
Rooting? Bootloader unlock? Penalized.
We’re not users just revenue streams trapped in locked hardware.
OEMs can’t ship working software, and they’ve stopped pretending to care.

AOSP is not going away

Seang Chau, VP and GM, Android Platform has posted on X saying that AOSP is not going anywhere, and that it was built on a foundation of "being an open platform for device implementations, SoC vendors, and instruction set architectures."

However, he has not said anything about why Pixel device trees have not been released.

🔗 @seangchau
🧑‍💻 @agamtechtricks

Get Android source (for Pixel)
Starting from Android 16, Google stopped making Pixel device trees public. Instead, there is a portal made available for developers (at least that's what they have left as an option).

You will be required to fill in a form and they will decide whether to distribute the code or not, plus there might be a processing fee. Additionally, they mentioned you can only apply for devices that you received within three years or devices that still receive customer support for code licensed under the GPL-3.

More info: AOSP
#Android #Pixel @PixelHubUpdates