YY
S G
Use hyper kernel
Unfortunately it's not overclockable
Size: a a a
2020 May 02
SG
Yy Yellow
Unfortunately it's not overclockable
What tasks you do on this device that needs overclocking
YY
Btw sorry @Sairam60 sir
YY
Whatever
S
Yy Yellow
Btw sorry @Sairam60 sir
Not needed
S
Yy Yellow
Unfortunately it's not overclockable
Starting with the 845 generation, Qualcomm introduced a hardware clock manager dubbed OSM (Operating State Manager). Early during the SoC's development, the kernel was responsible for initializing OSM and the in-kernel OSM driver was much more sophisticated as it held the sole responsibility of configuring OSM for all the CPUs as well as the shared L3 system cache.
In July of 2017, Qualcomm decided to prevent the kernel from modifying these values and designated OSM initialization to the TrustZone secure world instead. Here's the kernel commit marking the change. Reverting that commit will NOT unlock it as the change was made to the secure world's firmware. The commit mentions being locked out from the HLOS, which stands for High-Level OS — Linux in this case.
After that change, the kernel simply reads the frequency table out of the few OSM registers it is allowed to access and exposes them to the
Here is proof that the overclock is fake, since the CPU can't possibly run at 10 GHz with no issues.
In July of 2017, Qualcomm decided to prevent the kernel from modifying these values and designated OSM initialization to the TrustZone secure world instead. Here's the kernel commit marking the change. Reverting that commit will NOT unlock it as the change was made to the secure world's firmware. The commit mentions being locked out from the HLOS, which stands for High-Level OS — Linux in this case.
After that change, the kernel simply reads the frequency table out of the few OSM registers it is allowed to access and exposes them to the
clk framework as well as cpufreq for the rest of the kernel to use. To initiate a frequency switch, the kernel writes the index of the desired frequency to a special OSM register in memory and then TrustZone/OSM handles the rest based on the table programmed into it. TrustZone reads the tables from the QFPROM, which cannot be mutated by the kernel.Here is proof that the overclock is fake, since the CPU can't possibly run at 10 GHz with no issues.
YY
Starting with the 845 generation, Qualcomm introduced a hardware clock manager dubbed OSM (Operating State Manager). Early during the SoC's development, the kernel was responsible for initializing OSM and the in-kernel OSM driver was much more sophisticated as it held the sole responsibility of configuring OSM for all the CPUs as well as the shared L3 system cache.
In July of 2017, Qualcomm decided to prevent the kernel from modifying these values and designated OSM initialization to the TrustZone secure world instead. Here's the kernel commit marking the change. Reverting that commit will NOT unlock it as the change was made to the secure world's firmware. The commit mentions being locked out from the HLOS, which stands for High-Level OS — Linux in this case.
After that change, the kernel simply reads the frequency table out of the few OSM registers it is allowed to access and exposes them to the
Here is proof that the overclock is fake, since the CPU can't possibly run at 10 GHz with no issues.
In July of 2017, Qualcomm decided to prevent the kernel from modifying these values and designated OSM initialization to the TrustZone secure world instead. Here's the kernel commit marking the change. Reverting that commit will NOT unlock it as the change was made to the secure world's firmware. The commit mentions being locked out from the HLOS, which stands for High-Level OS — Linux in this case.
After that change, the kernel simply reads the frequency table out of the few OSM registers it is allowed to access and exposes them to the
clk framework as well as cpufreq for the rest of the kernel to use. To initiate a frequency switch, the kernel writes the index of the desired frequency to a special OSM register in memory and then TrustZone/OSM handles the rest based on the table programmed into it. TrustZone reads the tables from the QFPROM, which cannot be mutated by the kernel.Here is proof that the overclock is fake, since the CPU can't possibly run at 10 GHz with no issues.
Thanks
R
/notes
List of notes in Redmi 3S-3X XDA/4PDA/OT Discussions [Global]:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
You can retrieve these notes by using
-
adb-
adfree-
bestgcam-
bestrom-
chimera-
cleanflash-
ctsfix-
decrypt-
deepsleep-
dirtyflash-
encryption-
eng-
fast-thermal-
firmware-
flashtreble-
fontfix-
fp-
gcam-
gcamnight-
gcampie-
gcamset-
gcamtitbackup-
gms-
goodixbane-
gpsfix-
idledrainfix-
jasperk-
kcal-
lf-
los-
macaroni-
macaroni_recipe-
magisk18-
manualefsbackup-
marshmallow-
miuistablefw-
notificationfix-
oreo-
pie-
pkmkb-
pround-
rcube-
reddit-
root-
spotify-dl-
statusbar-
stop_spam-
substratum_q-
todo-
tool-
toolv2-
triggered-
twrp-
xda-
xdalabs-
xposed-
yukakernelYou can retrieve these notes by using
/get notename, or #notenameK
#fast-thermal
R
#fast-thermal
KM
#statusbar
R
Kanaya Marteen
#statusbar
Open terminal
Type "
Enter
Type "
Enter.
Type "
su"Enter
Type "
settings put secure sysui_rounded_content_padding 0"Enter.
S
T#
Starting with the 845 generation, Qualcomm introduced a hardware clock manager dubbed OSM (Operating State Manager). Early during the SoC's development, the kernel was responsible for initializing OSM and the in-kernel OSM driver was much more sophisticated as it held the sole responsibility of configuring OSM for all the CPUs as well as the shared L3 system cache.
In July of 2017, Qualcomm decided to prevent the kernel from modifying these values and designated OSM initialization to the TrustZone secure world instead. Here's the kernel commit marking the change. Reverting that commit will NOT unlock it as the change was made to the secure world's firmware. The commit mentions being locked out from the HLOS, which stands for High-Level OS — Linux in this case.
After that change, the kernel simply reads the frequency table out of the few OSM registers it is allowed to access and exposes them to the
Here is proof that the overclock is fake, since the CPU can't possibly run at 10 GHz with no issues.
In July of 2017, Qualcomm decided to prevent the kernel from modifying these values and designated OSM initialization to the TrustZone secure world instead. Here's the kernel commit marking the change. Reverting that commit will NOT unlock it as the change was made to the secure world's firmware. The commit mentions being locked out from the HLOS, which stands for High-Level OS — Linux in this case.
After that change, the kernel simply reads the frequency table out of the few OSM registers it is allowed to access and exposes them to the
clk framework as well as cpufreq for the rest of the kernel to use. To initiate a frequency switch, the kernel writes the index of the desired frequency to a special OSM register in memory and then TrustZone/OSM handles the rest based on the table programmed into it. TrustZone reads the tables from the QFPROM, which cannot be mutated by the kernel.Here is proof that the overclock is fake, since the CPU can't possibly run at 10 GHz with no issues.
such pro ... respec ++++
CK
Starting with the 845 generation, Qualcomm introduced a hardware clock manager dubbed OSM (Operating State Manager). Early during the SoC's development, the kernel was responsible for initializing OSM and the in-kernel OSM driver was much more sophisticated as it held the sole responsibility of configuring OSM for all the CPUs as well as the shared L3 system cache.
In July of 2017, Qualcomm decided to prevent the kernel from modifying these values and designated OSM initialization to the TrustZone secure world instead. Here's the kernel commit marking the change. Reverting that commit will NOT unlock it as the change was made to the secure world's firmware. The commit mentions being locked out from the HLOS, which stands for High-Level OS — Linux in this case.
After that change, the kernel simply reads the frequency table out of the few OSM registers it is allowed to access and exposes them to the
Here is proof that the overclock is fake, since the CPU can't possibly run at 10 GHz with no issues.
In July of 2017, Qualcomm decided to prevent the kernel from modifying these values and designated OSM initialization to the TrustZone secure world instead. Here's the kernel commit marking the change. Reverting that commit will NOT unlock it as the change was made to the secure world's firmware. The commit mentions being locked out from the HLOS, which stands for High-Level OS — Linux in this case.
After that change, the kernel simply reads the frequency table out of the few OSM registers it is allowed to access and exposes them to the
clk framework as well as cpufreq for the rest of the kernel to use. To initiate a frequency switch, the kernel writes the index of the desired frequency to a special OSM register in memory and then TrustZone/OSM handles the rest based on the table programmed into it. TrustZone reads the tables from the QFPROM, which cannot be mutated by the kernel.Here is proof that the overclock is fake, since the CPU can't possibly run at 10 GHz with no issues.
So overclocking not possible on new devices ??
AM
what is this for?
2020 May 03
S
such pro ... respec ++++
S
So overclocking not possible on new devices ??