InstallerXRevived-UI [PackageInstaller] Module v3.0
Replace the stock PackageInstaller / GooglePackageInstaller with the modern InstallerX Revived UI on AOSP-based ROMs.
Replace the stock PackageInstaller / GooglePackageInstaller with the modern InstallerX Revived UI on AOSP-based ROMs.
ā¤17
InstallerXRevived-UI v3.0 [Magisk+AP+KSU].zip
4.1 MB
InstallerXRevived-UI v3.0 [Magisk+AP+KSU].zip
š„14ā¤4š2
Blur Effects Enabler Module v2.0 [Magisk+KSU].zip
23.5 KB
Blur Effects Enabler Module v2.0 [Magisk+KSU].zip
š9ā¤6
KernelSU Next - New Manager Look
& Support Cloud Modules
& Support Cloud Modules
ā¤23š¤3
KernelSU_Next_v3.0.1-20-g95c2d228_32987-release.apk
9.4 MB
KernelSU_Next_v3.0.1-20-g95c2d228_32987-release.apk
š8š„°4
Plumpy Signal Icons v1.0 Android 16 Only [Magisk+KSU].zip
96.6 KB
Plumpy Signal Icons v1.0 Android 16 Only [Magisk+KSU].zip
ā¤18
Quick question for anyone tracking Android 16 QPR builds.
As far as I understand, the mapping looks like this:
BP2A ā QPR0
BP3A ā QPR1
BD3A ā QPR1
BP4A ā QPR2
Does this look right to you, or am I mixing up some of the build prefixes here?
Iām familiar with the general build naming pattern, just got a bit unsure because of the overlap around QPR1 and wanted to double-check.
As far as I understand, the mapping looks like this:
BP2A ā QPR0
BP3A ā QPR1
BD3A ā QPR1
BP4A ā QPR2
Does this look right to you, or am I mixing up some of the build prefixes here?
Iām familiar with the general build naming pattern, just got a bit unsure because of the overlap around QPR1 and wanted to double-check.
š27ā¤20š„3šÆ1