[Magisk] pndwal:
I think this may be fairly unique to builds for this device, and maintainer doesn't know why either:

https://xdaforums.com/t/lineageos-18-1-r-11-unofficial-mi-pad-4-plus-clover.4178757/post-84664747

I think LOS's purpose was to pick up from where CM left off after a falling out among the team led to that project's abandonment...

The point of CM was certainly not to be free of Google Proprietary Apps however. In fact it bundled these in ROM until Google hit Steve Kondik (Cyanogenmod) with a cease-and-desist order for including these.

He thought (and posted) that CM was dead and almost ditched the project, but Google seemed to realise they were SHOOTING THEMSELVES IN THE FOOT and clarified that they would still allow GApps to be sideloaded by end custom ROM users (but not packaged with custom ROMs) in short order.

Steve breathed a sigh of relief and got on with the job, Google shut their mouths, and others got OpenGapps.org established to make sideloading GApps simple for custom users, and those users were elated that they could still have their cake and eat it too... 😁

In fairness to Google, since that debacle, they have made a number of concessions to custom AOSP devs and users.

For example, while fighting unscrupulous OEMs and resellers who have tried to bundle Google's proprietary apps with uncertified devices (Chinese etc), and later, provided guides for sideloading the same, they have established a white list expressly to allow GApps to be run on these same devices as long as a Custom ROM is installed (although it seems to work also for stock 😉) by registering device by submitting Google Services Framework Android ID. (Without this, GApps can often be set up, but users are prevented from registering a Google account to use them).

https://www.google.com/android/uncertified/

Need for this, CDD & CTS and companies ignoring these are discussed here, and alternatives to GApps (still use minimal Google services) are touched on at the end of the article:

https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/

Nb. While such whitelisting is not generally needed for custom ROM or Magisk users employing spoofing techniques (certified fingerprint, etc), I'm guessing that this whitelist will likely be essential for many users wishing to to use GApps after final/full Hardware Keystore Attestation rollout.

At that time, SafetyNet pass as well as the use of a number of security centric apps will in all probability be impossible, and users whose Google Services Framework Android ID doesn't indicate a certified device (devices supplied with China stock ROMs especially) will suddenly need to register to use GApps at all. At least, that's my educated guess! 😬

Perhaps, but I think mileage may vary considerably between various ROMs and devices.

All best to you!

Don't we all... But that's the cost of progress!

"Everything's gonna run on a paying basis.

Out with the spiritual mumbo-jumbo and the backward ways.

We're gonna see a brave new world where they hook us all up to a grid.

Yes, a veritable age of reason.

Like the one they had in France. Not a moment too soon.

Not a moment too soon."

O Brother Where Art Thou

😜 PW