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
This media is not supported in your browser
VIEW IN TELEGRAM
I have been suffering from high energy consumption for a while, which makes the phone heat up and drain the battery. Is this consumption normal? Literally like this always without using anything, what might be the reason?
ā¤16š6ā¤āš„2š2
QPR Mapping
This mapping is originally based on Pixel devices, so it also applies to custom ROMs built on AOSP.
It usually does NOT apply to OEM stock ROMs (such as MIUI, HyperOS, OxygenOS, ColorOS, etc.), since manufacturers often modify the Build ID format.
Q1 ā QPR1
Q2 ā QPR2
Q3 ā QPR3
R1 ā QPR1
R2 ā QPR2
R3 ā QPR3
S1 ā QPR1
S2 ā QPR2
S3 ā QPR3 (12L)
T1 ā QPR1
T2 ā QPR2
T3 ā QPR3
U1 ā QPR1
A1 ā QPR2
A2 ā QPR3
A3 ā QPR1
A4 ā QPR2
B1 ā QPR3
B2 ā QPR0
B3 ā QPR1
B4 ā QPR2
C1 ā QPR3
Example:
Build ID: TQ3A.230805.001
First letter: T
First number after it: 3
š Key = T3 (used to detect QPR)
This mapping is originally based on Pixel devices, so it also applies to custom ROMs built on AOSP.
It usually does NOT apply to OEM stock ROMs (such as MIUI, HyperOS, OxygenOS, ColorOS, etc.), since manufacturers often modify the Build ID format.
Android 10
Q1 ā QPR1
Q2 ā QPR2
Q3 ā QPR3
Android 11
R1 ā QPR1
R2 ā QPR2
R3 ā QPR3
Android 12
S1 ā QPR1
S2 ā QPR2
S3 ā QPR3 (12L)
Android 13
T1 ā QPR1
T2 ā QPR2
T3 ā QPR3
Android 14
U1 ā QPR1
A1 ā QPR2
A2 ā QPR3
Android 15
A3 ā QPR1
A4 ā QPR2
B1 ā QPR3
Android 16
B2 ā QPR0
B3 ā QPR1
B4 ā QPR2
C1 ā QPR3
Example:
Build ID: TQ3A.230805.001
First letter: T
First number after it: 3
š Key = T3 (used to detect QPR)
š„47ā¤33ā¤āš„3
KernelSU_Next_v3.0.1-23-g314fbc5a_32990-release.apk
9.4 MB
KernelSU_Next_v3.0.1-23-g314fbc5a_32990-release.apk
š20ā¤5š„°2
If your phone is using the stock / OEM launcher (not a third-party one), such as:
⢠Xiaomi (MIUI / HyperOS)
⢠Samsung (One UI)
⢠OPPO (ColorOS)
⢠vivo / iQOO
⢠Motorola
⢠Realme
⢠Infinix
⢠ASUS
⢠Sony
⢠Huawei
⢠or any other OEM
Launcher package name
Example:
Xiaomi ā MIUI Launcher
com.miui.home
⢠Xiaomi (MIUI / HyperOS)
⢠Samsung (One UI)
⢠OPPO (ColorOS)
⢠vivo / iQOO
⢠Motorola
⢠Realme
⢠Infinix
⢠ASUS
⢠Sony
⢠Huawei
⢠or any other OEM
Please comment with:
Launcher package name
Example:
Xiaomi ā MIUI Launcher
com.miui.home
This will be used to enable running custom ROM launchers based on Launcher3 on OEM stock ROMs. We will skip the old replacement method based on system paths for each launcher, and instead perform the replacement using the launcher package name.
ā¤59š10š„9