[Magisk] pndwal:
Yeah, sure... but you said you were "not happy with Google for continuing to "enhance" Android as time goes on"... And that's where we differ...

I think their intention in implementing the innovations and OEM requirements that also require modding Devs to adapt, innovate and re-invent, is ultimately to advantage all of us... I mentioned the advantages of some such changes.

And it's not their fault that while their Devs push milestones destined for AOSP with every new flagship Google device, the likes of TeamWin have only a base team of four + device maintainers and have difficulty keeping up/adapting in a timely fashion... They've got a business to run!

... But that's quite another thing, and again depends on perspective.

Google is not actually blocking root or mods on Android at all!

... Unless you regard (half-heartedly) opting out of allowing their own proprietary Pay/Wallet app from running in a modded / AVB unverified (uncertified) code execution environment and providing the means for other institutions to similarly opt out if they wish as root-blocking and mod-blocking... Patently, that's a means of blocking proprietary code from running, NOT blocking root or mods however!

So Google provides a mobile OS for all; Banks use it as do bank customers and modders...

You seem to think that banks etc should be made to allow their code to run on devices without the assurances of AVB verifications and other security features for the convenience of modders...

Google thinks they should be allowed to choose, otherwise what's the point of having Green, Yellow and Orange state Android, military grade cryptography/encryption, password and pattern locks etc, etc.

IOS simply locks down their OS for modders and offers no attestation to a 'verified' execution environment for banks etc AFAIK because there is just no need... No need and no choices...

Since we've jumped onto this horse, I'm actually baffled as to why we're still playing cat-and-mouse years after John thought/said "The fun's over"...

For me, it's a fun game while it lasts...

Regarding Google, in their SafetyNet and Play Integrity APIs they themselves have (surprisingly) managed to keep this game (and the mice) alive for much longer than any of us imagined!... The simple inclusion of a strong attestation to the keymaster version a device has (which exists in key extension data already) or similar in the integrity APIs would have allowed PI strongIntegrity etc to be enforced on devices that have the requisite keymaster 3+ without impacting users of older devices at least showing various levels of 'basic' attestation to verified Green (device locked with OS signed with OEM set, not custom, keys) AVB state, and, as such, a strongIntegrity verdict would have been enforced by banks as soon as it was proffered!... Ie, Google could easily have ushered in the end-game, at least for all Android 8+ devices, but didn't...

My point again is that Google isn't really to blame; After all they could easily have handed out mouse traps, but instead just gave us the cheese and a largely unusable integrity attestation trap/system for the banks...

Of course ultimately that game will surely end with the mice the loosers... But unless there is some Quantum change in the Google mobile OS / AOSP model, moddable and rootable Android will remain unaffected...

Only those who equate root and modding with the ability to falsify (spoof) expected security signals will disagree. 😬 😜 PW