Database Users

[DEV][WIP][KERNEL-PATCH][MSM7x30/8x55 GPU OVERCLOCKING][2d-core done][3d-core][v0.7]

Finally after someone pm'd me I looked back into GPU Overclocking.
New thread created issues with old thread OP permissions (people seem to be asking the same questions over and over again all information will be kept in OP & DO READ THE THREAD, repetitive questions will now be ignored)
Benefits:
Smoother UI
Handle 2d & 3d core GPU intensive applications & games
Currently only 2D core has been overclocked working on 3D core OC
2D-core original value - 192mhz OC to 245mhz DONE achieved 25% performance boost grp_2d_clk outputs 245760000hz
3D-core original value - 245mhz OC to 300+mhz WIP hoping to achieve 40-50% performance boost
2D-core OC only Download: Coming soon...
Download Links for other devices coming soon...
Works for all HTC Sense/Cm9/Cm10 kernels (Just ask a kernel developer for your device to implement the source code)
Note: Don't have internet on PC so providing 3 main files that need replaced for 2D-core OC to work
Download link to source code: http://d-h.st/wbH
3D-CORE OC TESTS Download: Coming soon...
Do check under sys/kernel/debug/htc_clock/clks/ look for file with all clocks & look for GRP_clks (Graphics clock)

OK so basically today I've been thinking and I've come to the conclusion that I will release the 2D-core OC patch As Soon As Possible, 3D-core Core OC is NOT Impossible but for now I'll give it a break, I will attempt 3D-core OC If/When I can get a hold of a msm7x30/msm8x55 device, as it will make it much easier for both me & users.
So for now you can enjoy the 50mhz increase/bump up, perf boost 25% in 2D-core (will increase performance in both 2D/3D intensive appications as 2D-core is used for 3D AFAIK and increase User Interface performance (Note: This will not take a hit on battery life)), I will also release a couple of fixes on patchas kernel that shouldnt be there/set etc.
(Theres a device available in my area for roughly £90, if anyone wants to contribute towards getting that device or can donate a device , more than welcome and shoot me a PM so I can list you here.)
(This isnt a promise of 3D-Overclock if you donate, if you donate please do so expecting nothing I will only attempt 3D-overclock)
Working device list - all kernel 3.0+ msm7x30/msm8x55 soc devices.
Main thread is in Desire HD Android Development section: http://forum.xda-developers.com/show....php?t=2368497

Thanks for your efforts.
I'm trying to follow the link to your Desire thread and it seems it's broken.
Nevermind, found it: LINK

I think a kernel dev from the droid incredible 2 has a 3d gpu overclock in a kernel but I didn't use it in mine because I worry about the heat output being overclocked combined with that.
Sent from my ADR6400L using Tapatalk 2

disconnecktie said:
I think a kernel dev from the droid incredible 2 has a 3d gpu overclock in a kernel but I didn't use it in mine because I worry about the heat output being overclocked combined with that.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2372291
you must be referring to this...
Someone already showed me the commits
no one has managed gpu overclocking at all on any msm7x30/msm8x55 platform/soc devices

I saw it someone's git when I was building my kernel. I couldn't find useful posts about kernel stuff so I just looked for git accounts that were from similar devices.
Sent from my ADR6400L using Tapatalk 2

Probably Kangaroo Kernel based off of Beast Mode.

Oh ya that's the one. Been a while since i looked.
Sent from my ADR6400L using Tapatalk 2

Shaky156 said:
OK so basically today I've been thinking and I've come to the conclusion that I will release the 2D-core OC patch As Soon As Possible, 3D-core Core OC is NOT Impossible but for now I'll give it a break, I will attempt 3D-core OC If/When I can get a hold of a msm7x30/msm8x55 device, as it will make it much easier for both me & users.
So for now you can enjoy the 50mhz increase/bump up, perf boost 25% in 2D-core (will increase performance in both 2D/3D intensive appications as 2D-core is used for 3D AFAIK and increase User Interface performance (Note: This will not take a hit on battery life)), I will also release a couple of fixes on patchas kernel that shouldnt be there/set etc.
(Theres a device available in my area for roughly £90, if anyone wants to contribute towards getting that device or can donate a device , more than welcome and shoot me a PM so I can list you here.)
(This isnt a promise of 3D-Overclock if you donate, if you donate please do so expecting nothing I will only attempt 3D-overclock)
Working device list - all kernel 3.0+ msm7x30/msm8x55 soc devices.
Main thread is in Desire HD Android Development section: http://forum.xda-developers.com/show....php?t=2368497
Click to expand...
Click to collapse
I have an Inc2 id be willing to test on if you'd like...
Sent from my Maserati using XDA Premium

Everyone has been modifying the kernel graphics software layer platform data with values that dont make sense and are impossible more above with values that dont exist within thw graphics table anywayx
3d oc is abit more difficult
Devs + testers join IRC will make life easier
Irc freenode #s1gpuoc

I wouldn't recommend replacing those files in any current kernel directly. Since there is no github to see what the actual changes are isolated from the file, it's hard to say if all the changes made are compatible. Some of them were unnecessary, and simply added credits to a line that was unchanged (most likely because it has been updated since the original writing of the files).
https://github.com/StarKissed/stark...mmit/dc381024f122a114b770076e2992cd5097f5c47c <- The specific changes required

twistedumbrella said:
Does this include a sysfs interface to throttle the overclock?
https://github.com/StarKissed/stark...mmit/618b9e076f7b2c0a8f9f0c5733f61d4ef27261c0
Click to expand...
Click to collapse
There isnt any need for a sys fs at the moment due to the way qualcomm have made their msm7x30

Shaky156 said:
There isnt any need for a sys fs at the moment due to the way qualcomm have made their msm7x30
Click to expand...
Click to collapse
Any time values that aren't stock are being forced, it's good to have the option to turn it off but in this case it's only forcing stock values to persist so it doesn't really matter.
Sent from my Galaxy Nexus using Tapatalk 2

Okay after looking @ GPU Overclock for 2 weeks, This is the news on GPU OC for MSM8x55/MSM7x30 socs.
My findings...
2D-core OC from 192mhz to 245mhz successful.
3D-core OC will not happen without me obtaining the datasheet (which is proprietary)
The clocks are protected, via Ownership/Permissions, and maybe an RCU/MPU
No Overclocking the CPU does NOT Overclock the GPU, thats the worst thing I've heard in my life lol.
The lowest the GPU can hit is 192mhz or lpxo freq
Bus is not overclockable, it always is 192mhz
EBI_2D_clk will and has always been 0mhz
Modifying kgsl platform data and/or the graphics table with random values or even calculated values from correct pll freqs will NOT OC the gpu
it's ashame the GPU clocks are protected.
IF anyone is looking to continuing this project and is on the right track you're more than welcome to get in contact with me, especially if you have the msm7x30 datasheet.
The QSD8x50 soc is more open than this soc, so I'm doing a few tests on the HD2

Kernel explanation

I don't know if the answer to my question is somewhere hidden between the thousands of threats but I did try to find it before(including Google and YouTube) and would be more than happy to get a reply.
I'm using custom Kernels since the Note 2 but was never able to put more time and afford in to understand how they actually work and always used the default settings.
Now I'm trying to get some knowledge on Kernel settings and what is safe to change and what not. I'm very interested on how a Kernel works and how I can boost both battery life and/or performance as well as the basic knowledge of the Kernel settings.
At the moment I'm trying to explore with trickster mod to kinda learn by doing but I always get really bad results in testing or no big changes when I change the governor. Also I'm a little afraid in messing up my phone and therefor don't change the settings much. What I know is that the same Kernel can have different outcomes on different Note 3's so please do not post just your Kernel and settings without explanation cause I would like to find the most suited Kernel and settings for my Note.
Sooo...Some help and explanations would be more than appreciated.

4aces said:
I don't know if the answer to my question is somewhere hidden between the thousands of threats but I did try to find it before(including Google and YouTube) and would be more than happy to get a reply.
I'm using custom Kernels since the Note 2 but was never able to put more time and afford in to understand how they actually work and always used the default settings.
Now I'm trying to get some knowledge on Kernel settings and what is safe to change and what not. I'm very interested on how a Kernel works and how I can boost both battery life and/or performance as well as the basic knowledge of the Kernel settings.
At the moment I'm trying to explore with trickster mod to kinda learn by doing but I always get really bad results in testing or no big changes when I change the governor. Also I'm a little afraid in messing up my phone and therefor don't change the settings much. What I know is that the same Kernel can have different outcomes on different Note 3's so please do not post just your Kernel and settings without explanation cause I would like to find the most suited Kernel and settings for my Note.
Sooo...Some help and explanations would be more than appreciated.
Click to expand...
Click to collapse
I can give you a brief (easy) explanation with comparisons to try to get you to understand what a kernel is.
A kernel is your phone's driver (like a car) where it adjusts settings of the hardware and controls how each individual part interacts with each other.
There is a reason you take a car to get tuned up, and that is because a car can go berserk as there is no "maintaining force" - YOU or the person who tunes your car makes changes to the car to make sure it does not overheat, use less power per mile travelled, control how much windshield fluid is being released or how much torque force required to ensure the car does not snap XXXXXX when going at a speed of YYYYYY.
These options are beyond the manufacturer's decisions, and therefore when people flash a kernel you immediately trip KNOX (N9005). You can give your phone less power to process, more power to process (not recommended), speed up the CPU/limit the CPU, control governors on how the disk I/O (input/output) is being handled and/or control how much the phone will swap to it's virtual memory when it reaches no memory.
People think use a custom kernel! It saves you a ton of battery life!. This statement is partially wrong. You have to understand how a kernel reacts to your phone. Even though I know that lite kernels like Wootever's Custom N3 has the best battery life, this is because it has less tweaks and features that may boggle the user, and may allow for subsequent battery life extension compared to CivZ's SneakyKat or Imoseyon's LeanKernel. By inserting new tweaks into the kernel, you allow to have more "useful" features that may add to the "driver's knowledge" - Color tweaking, Fast charge over USB, CIFS support, all are extras that the kernel supports. To save power, developers remove the junk that the manufacturers added and added their own settings to make sure they get the result they would like, then they would share it to the public. However, people recommend custom kernels as they get more options when they flash it, as well as ridding of a lot of the stock settings that manufacturers love setting (default governors, lowest CPU frequency, etc)
CPU governors work by controlling how much speed is used at a given time, a good description of what each governor does is listed here: http://forum.xda-developers.com/showthread.php?t=1736168
I/O governors (simply speaking) control how files and requests are being handled by the system, a good description of what each governors is listed here: http://forum.xda-developers.com/showpost.php?p=23616564&postcount=4. Good way to understand this is if you learnt programming and you learnt the Stack/Queue ADTs in a programming language, it describes things better when looking at the descriptions in the link above.
Adjusting Synapse/Trickster would not get you anywhere to getting the best battery/best performance out of the phone. You will have to experiment and check which kernel is best with your phone, according to your SOC_PVS value. SOC_PVS value is how Qualcomm decides your processor's manufacturing "rank" and if you compare a low rank to a high rank, you will see that you can use less power to operate a high ranked chip compared to a low ranked counterpart. As most governors rely heavily on how the code is handled by the system, you should always go for the kernel that fits your system, and setting configurations depending on your system's likings. By following other people's configurations you risk sporadic reboots and incompatibilities, as not all phones are built the same way.
Things you should not touch if you are afraid of destroying your phone: Overvolting and Overclocking, as these may fry your device if you don't know what you are doing.
Any questions - click reply to this, or else I won't see it!

nicholaschum said:
I can give you a brief (easy) explanation with comparisons to try to get you to understand what a kernel is.
A kernel is your phone's driver (like a car) where it adjusts settings of the hardware and controls how each individual part interacts with each other.
There is a reason you take a car to get tuned up, and that is because a car can go berserk as there is no "maintaining force" - YOU or the person who tunes your car makes changes to the car to make sure it does not overheat, use less power per mile travelled, control how much windshield fluid is being released or how much torque force required to ensure the car does not snap XXXXXX when going at a speed of YYYYYY.
These options are beyond the manufacturer's decisions, and therefore when people flash a kernel you immediately trip KNOX (N9005). You can give your phone less power to process, more power to process (not recommended), speed up the CPU/limit the CPU, control governors on how the disk I/O (input/output) is being handled and/or control how much the phone will swap to it's virtual memory when it reaches no memory.
People think use a custom kernel! It saves you a ton of battery life!. This statement is partially wrong. You have to understand how a kernel reacts to your phone. Even though I know that lite kernels like Wootever's Custom N3 has the best battery life, this is because it has less tweaks and features that may boggle the user, and may allow for subsequent battery life extension compared to CivZ's SneakyKat or Imoseyon's LeanKernel. By inserting new tweaks into the kernel, you allow to have more "useful" features that may add to the "driver's knowledge" - Color tweaking, Fast charge over USB, CIFS support, all are extras that the kernel supports. To save power, developers remove the junk that the manufacturers added and added their own settings to make sure they get the result they would like, then they would share it to the public. However, people recommend custom kernels as they get more options when they flash it, as well as ridding of a lot of the stock settings that manufacturers love setting (default governors, lowest CPU frequency, etc)
CPU governors work by controlling how much speed is used at a given time, a good description of what each governor does is listed here: http://forum.xda-developers.com/showthread.php?t=1736168
I/O governors (simply speaking) control how files and requests are being handled by the system, a good description of what each governors is listed here: http://forum.xda-developers.com/showpost.php?p=23616564&postcount=4. Good way to understand this is if you learnt programming and you learnt the Stack/Queue ADTs in a programming language, it describes things better when looking at the descriptions in the link above.
Adjusting Synapse/Trickster would not get you anywhere to getting the best battery/best performance out of the phone. You will have to experiment and check which kernel is best with your phone, according to your SOC_PVS value. SOC_PVS value is how Qualcomm decides your processor's manufacturing "rank" and if you compare a low rank to a high rank, you will see that you can use less power to operate a high ranked chip compared to a low ranked counterpart. As most governors rely heavily on how the code is handled by the system, you should always go for the kernel that fits your system, and setting configurations depending on your system's likings. By following other people's configurations you risk sporadic reboots and incompatibilities, as not all phones are built the same way.
Things you should not touch if you are afraid of destroying your phone: Overvolting and Overclocking, as these may fry your device if you don't know what you are doing.
Any questions - click reply to this, or else I won't see it!
Click to expand...
Click to collapse
First of all thank u very much for the detailed response. That was exactly what I was looking for. I will get back to you after going through the awesome links you were posting with some more knowledge
One thing which came straight in my mind was how do I know if I have a low or high rank from the soc_pvs_value and where do I find it?
Thanks again!

4aces said:
First of all thank u very much for the detailed response. That was exactly what I was looking for. I will get back to you after going through the awesome links you were posting with some more knowledge
One thing which came straight in my mind was how do I know if I have a low or high rank from the soc_pvs_value and where do I find it?
Thanks again!
Click to expand...
Click to collapse
Anytime
You can either install Synapse (If your Kernel supports it, and click on the button under CPU), or check here:
Code:
/sys/devices/system/soc/soc0/soc_pvs
The higher your number, the better.

nicholaschum said:
Anytime
You can either install Synapse (If your Kernel supports it, and click on the button under CPU), or check here:
Code:
/sys/devices/system/soc/soc0/soc_pvs
The higher your number, the better.
Click to expand...
Click to collapse
I ran out of "thanks" so u get it tomorrow. But thanks again. One more thing:
How do I know if I have a high number/between which numbers does the value wary? My soc_pvs is 3.

4aces said:
I ran out of "thanks" so u get it tomorrow. But thanks again. One more thing:
How do I know if I have a high number/between which numbers does the value wary? My soc_pvs is 3.
Click to expand...
Click to collapse
You got a rather good number.
The lowest is 0, and the highest is 6. I have 2 but I don't undervolt so this is not an issue

nicholaschum said:
You got a rather good number.
The lowest is 0, and the highest is 6. I have 2 but I don't undervolt so this is not an issue
Click to expand...
Click to collapse
Can't thank u enough!!! Now I will be off to some reading and testing

nicholaschum said:
You got a rather good number.
The lowest is 0, and the highest is 6. I have 2 but I don't undervolt so this is not an issue
Click to expand...
Click to collapse
Aaand one more question.
What is the difference in tcp congestion control (cubic/reno) and what does it change?

4aces said:
Aaand one more question.
What is the difference in tcp congestion control (cubic/reno) and what does it change?
Click to expand...
Click to collapse
That seems more of a Trickster Mod specific tweak.
It is more of a network speed tweak which you can read here: http://en.m.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm
In simple words, you have to understand what Network Congestion is, and how queues affect how much data is being transmitted. When too much data is being carried in a link or a node, the quality of service would deteriorate. To do Congestion control, it affects how much data is being transmitted through each node systematically. This is rather complicated to explain using simple terms as this is a mathematical formula which processes how much data is being transmitted.
Cubic is used by many default linux kernels. Like CPU governors, these are data transmission governors, and it is best if you use the one better for your TCP/IP connection (Carrier or Wifi)

nicholaschum said:
That seems more of a Trickster Mod specific tweak.
It is more of a network speed tweak which you can read here: http://en.m.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm
In simple words, you have to understand what Network Congestion is, and how queues affect how much data is being transmitted. When too much data is being carried in a link or a node, the quality of service would deteriorate. To do Congestion control, it affects how much data is being transmitted through each node systematically. This is rather complicated to explain using simple terms as this is a mathematical formula which processes how much data is being transmitted.
Cubic is used by many default linux kernels. Like CPU governors, these are data transmission governors, and it is best if you use the one better for your TCP/IP connection (Carrier or Wifi)
Click to expand...
Click to collapse
Just read the answer in the link u posted. Stupid me.
Sorry for taking up your time.

nicholaschum said:
That seems more of a Trickster Mod specific tweak.
It is more of a network speed tweak which you can read here: http://en.m.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm
In simple words, you have to understand what Network Congestion is, and how queues affect how much data is being transmitted. When too much data is being carried in a link or a node, the quality of service would deteriorate. To do Congestion control, it affects how much data is being transmitted through each node systematically. This is rather complicated to explain using simple terms as this is a mathematical formula which processes how much data is being transmitted.
Cubic is used by many default linux kernels. Like CPU governors, these are data transmission governors, and it is best if you use the one better for your TCP/IP connection (Carrier or Wifi)
Click to expand...
Click to collapse
I have another question. If I want to oc or uv is there any script I have to use or can I just apply/test right away?

4aces said:
I have another question. If I want to oc or uv is there any script I have to use or can I just apply/test right away?
Click to expand...
Click to collapse
Just use the main interface of either Trickster or Synapse. I use Synapse personally as my kernel provides the best interface on Synapse.

nicholaschum said:
Just use the main interface of either Trickster or Synapse. I use Synapse personally as my kernel provides the best interface on Synapse.
Click to expand...
Click to collapse
What I found out so far is that the device runs smoother on performance based governors with cfq or sio scheduler. The best results I had so far was on lean kernel and ael kernel. I'm using the last at the moment cause it has a lot of settings to play with
But it seems that I'm still miles away from finding the best settings.

4aces said:
What I found out so far is that my device reacts not good on performance based governors & schedulers. The best results I had so far was on lean kernel and ael kernel. I'm using the last at the moment cause it has a lot of settings to play with
But it seems that I'm still miles away from finding the best settings.
Click to expand...
Click to collapse
I could give you some recommendations that would work well decently with 2-3 PVS valued processors.
Interactive Governor
No OC, No UV.
I/O schedulers Internal: cfq 512kb
I/O schedulers External: cfq 512kb
Dynamic Fsync Enabled
PowerSuspend driver enabled
Mdnie enabled, 0.39%
FastCharge Enabled
GPU Governor: Simple Ondemand 450MHz
I use CivZ's SneakyKat but Wootever's Custom N3 has the best battery life. If you want features you should play with CivZ's, if you like 6h screen on then you should play with Wootever.
You don't have to follow these values, but I spent days restarting my phone finding the best "average" configuration for devices ranging in my state. I found that Intellidemand didn't do so well and Interactive prevented any sporadic reboots that I got while on Intellidemand. Also read aheads of above 512kb doesn't show much speed enhancements. Synapse is great as it tells you whether your boot is successful or not, and now all my boots get Completed.
Notice: Do not soft reboot when configuring Kernels, Kernels don't get loaded properly/doesn't get reset properly so use Full reboot when configuring

cpu lock
I tried gaming with different kernels and governors and encountered a strange issue. Especially in candy crush after playing for a while the cpu locks (sometimes on 14k sometimes 12k). Reboot fixes it but I'm still curious why it locks. 
 @nicholaschum any idea?
Btw. my favorite settings so far are intellidemand with deadline gr8 performance and battery life is OK.

4aces said:
I tried gaming with different kernels and governors and encountered a strange issue. Especially in candy crush after playing for a while the cpu locks (sometimes on 14k sometimes 12k). Reboot fixes it but I'm still curious why it locks.
@nicholaschum any idea?
Btw. my favorite settings so far are intellidemand with deadline gr8 performance and battery life is OK.
Click to expand...
Click to collapse
That's a bit weird, did you have powersaving turned on? But I assume it's off.
I think you should disable your kernel mod application in Application Manager and test it out, if it's a problem with Synapse/Trickster then one setting is a bit problematic.

nicholaschum said:
That's a bit weird, did you have powersaving turned on? But I assume it's off.
I think you should disable your kernel mod application in Application Manager and test it out, if it's a problem with Synapse/Trickster then one setting is a bit problematic.
Click to expand...
Click to collapse
Nope that's why it's strange. Even got it after clean flash without setting/installing any Kernel related apps.
Tested other games and they work fine so I deleted candy crush and so far no cpu lock. No idea why, that's why I was curious

4aces said:
Nope that's why it's strange. Even got it after clean flash without setting/installing any Kernel related apps.
Tested other games and they work fine so I deleted candy crush and so far no cpu lock. No idea why, that's why I was curious
Click to expand...
Click to collapse
I don't play Candy Crush so I wouldn't know..haha

nicholaschum said:
I don't play Candy Crush so I wouldn't know..haha
Click to expand...
Click to collapse
Lol. Me neither from now on... (my kids will be sad though) Still can't really belive the game caused it

[kernel][3.0.31] Mk kernel - based on CoCafe kernel Refresh r10

Update
All the changes I made were merged into CoCore-refresh kernel (3.0.31) and 3.0.101 by TeamCanjica, so they will hit 'mainstream' in some time when they release another build.
This thread is over
/Update
Hi,
I've been working on this kernel for some time with improving undervolting in mind. It's based on CoCore Refresh r10 by CoCafe and of course the credit goes to him where it's due.
Main changes:
- rewritten liveOPP internals.
It improved stability a lot - it now allows to use 300/500/700/900 MHz frequencies with no problem and it allows to undervolt low frequencies even more. Freqs >1GHz are now stable at varm=0x32 (at least on my phone), which also saves a lot of power.
Freqs <=400 MHz now use 0x12 (0.925V) voltage by default - It's the original voltage for 400MHz and you can go even lower when undervolting
- rewritten Mali booster algorithm.
It's far from perfect yet, but it eliminated instability due to the fact, that CoCafe's mali booster and "original" booster (switching between APE 50/100 OPP) were working independently and could cause a crash when the original algorithm switched to APE_50_OPP while mali boost was active. APE_50_OPP voltage is 1V by default (0x18), so when clock is boosted to i.e. 700MHz and it switched to 50 OPP, the result was 350MHz @ 1V, which mihgt be too low.
- allow to set APE and DDR OPP with liveOPP
echo apeopp=25/50/100 > arm_stepXX and echo ddropp=...
before the kernel would set ape/ddr opp to 100 for freqs above 400MHz
- allow changing ape_50_opp voltage
echo 0xXX > /sys/kernel/mali/mali_gpu_vape_50_opp
- make wlan/mmc boost tunables available through sysfs in /sys/kernel/performance/*
- Memory split changed to 2G/2G and switch highmem off - it's not needed with this split
- removed some unnecessary drivers and moved others to modules to reduce kernel size
- changed kernel compression to LZO
- 631MB available memory
- 7800ms kernel boot time
Download & install:
Mediafire
That's partition image - flash it with dd:
Code:
dd if=kernel.mk-r1-release.img of=/dev/block/mmcblk0p15
It's also good to create a symlink from /system/lib/modules to /lib/modules - it'll allow modules to autoload, enable modprobe to work and also you can use KoControl app to manage module loading.
Source:
GitHub
TODO:
- create a package for flashing with recovery and place modules (7MB) in /system/lib/modules instead of a ramdisk
- touchbooster has a bug that causes it to limit max freq to 1000MHz on boost.
- figure out how to enable setting of minimal cpu freq - now touchboost always resets it to 100MHz
- add interactive gov from Zwliew kernel
- create more power optimized, auto tuning 'foreground' governor (long story)
My voltage settings
(default kernel voltages are more conservative - set those from init scripts and test them for stability!):
100 - 0x0f
200 - 0x10
300 - 0x11
400 - 0x12
500 - 0x14
600 - 0x18
700 - 0x1d
800 - 0x24
900 - 0x28
1000 - 0x2f
1050..1250 - 0x32
Mali gpu voltage
Default voltage from CoCafe is way too high - idx0 vape could be just 1V since that's the voltage, when mali is running at 1/2 speed (200MHz by default).
My settings (for safety they are 3 steps higher than the lowest working voltage for given freq).
#0 - 0x17
#5 - 0x1c
#9 - 0x23
I don't overclock the gpu - my low index is set to 0 (200MHz), and hi (boosted) to 5(400MHz), which is the original mali freq. That gives mi 100MHz when working at half speed. I don't use any fancy UI effects, so it's enough - when not plaing a game, mali is only working at 100/200MHz and only boosts when loaded. Params:
boost_low idx=0
boost_low threshold=30
boost_delay 2000
boost_high idx=5
boost_high threshold=220
Default kernel settings are left unchanged - set those manually from init scripts.
I place the thread here because I'm not allowed to post in developer forums (<10 messages limit).
MK

Wow. Thanks for your work, mate!
Most people are using CM or CM/AOSP based ROMs nowadays, but there are only a few people (like me) who still use Jellybean. So, I'll try your kernel very soon and I'll post a review after using it.
You joined XDA on 2010 and yet, this is your first post. That just doesn't feel right.. Anyways, keep up the good work, mate. :good:

Good to see another kernel developer for our phone! I'm on stock rom now, I will try it out

Sami Kabir;5571pro. [B said:
Wow. Thanks for your work, mate! [/B]
Most people are using CM or CM/AOSP based ROMs nowadays, but there are only a few people (like me) who still use Jellybean. So, I'll try your kernel very soon and I'll post a review after( using it.
Click to expand...
Click to collapse
The code is on github and there's no problem with merging it with some cm kernel. When I'll try my with some 4.4 again (so far each one had something broken and didn't suit me), I'll probably do it
You joined XDA on 2010 and yet, this is your first post. That just doesn't feel right.. Anyways, keep up the good work, mate. :good:
Click to expand...
Click to collapse
To keep it short let just say that I'm not a sociable type of guy... but when I have something of value, I try to share...
One more thing (most probably know it, but for those who don't) - 99% of "user experience" depends on the settings of governor, mali and touch booster - if you screw this up, no kernel will work smoothly. I had this problem with my first vanilla jb - it sucked as hell(ondemand), but when I set sampling_down_factor to 3-4 suddenly it was very smooth. Default gov params aren't always the best. Thats one of the reasons I'll try to write a governor that tunes itself and adjusts itself to the app currently in foreground - but that's just an idea and it'll take me some time to refresh all the math needed for it...
Anyway - enjoy the kernel.

Hmm I really wanna test this kernel, but I'm currently on Vanir
I definitely gonna follow your thread, it's good to know Janice is still alive and kicking

Reinkaos said:
Hmm I really wanna test this kernel, but I'm currently on Vanir
I definitely gonna follow your thread, it's good to know Janice is still alive and kicking
Click to expand...
Click to collapse
You can always ask rom's devs to merge my changes - it's just a few commits.
And how is that rom working for you? At the time I was checking up 4.4 roms each one of them sucked in a different way. Carbon was the closest (in fact it was the only one acceptable) to being useful (feature- and ui-wise), but it had some process spinning in the background and It was draining my batt (it was unkillable because it was a part of lock screen I think - the bug was known, but no fix available at that time).
If it's similar to carbon I might give it a try...

mkaluza said:
You can always ask rom's devs to merge my changes - it's just a few commits.
And how is that rom working for you? At the time I was checking up 4.4 roms each one of them sucked in a different way. Carbon was the closest (in fact it was the only one acceptable) to being useful (feature- and ui-wise), but it had some process spinning in the background and It was draining my batt (it was unkillable because it was a part of lock screen I think - the bug was known, but no fix available at that time).
If it's similar to carbon I might give it a try...
Click to expand...
Click to collapse
Well I use to be a Carbon die-hard fan before, but since the dev have got himself another device, so I just had to change rom.
And then I try Vanir. Surprisingly it's pretty stable, and we have official support by the Vanir team too.
Feature-wise its just as good as Carbon, but I kinda miss the pie, since Vanir doesn't have it.
And I think Vanir have a bit more features than Carbon do.
Anyway can you go lower than those cpu voltage on your OP? Or is it really not stable?
Mine's 1000 is at 0x2c, 800 at 0x20, and that's the lowest I can go.
And thanks for the gpu voltage :good: , I actually use that value now :laugh:

aioreu the
Reinkaos said:
Well I use to be a Carbon die-hard fan before, but since the dev have got himself another device, so I just had to change rom.
Click to expand...
Click to collapse
It's a pity... but I understand that's only the S Advance branch of Carbon thats dead - the rom itself is being developed further?
And then I try Vanir. Surprisingly it's pretty stable, and we have official support by the Vanir team too.
Feature-wise its just as good as Carbon, but I kinda miss the pie, since Vanir doesn't have it.
And I think Vanir have a bit more features than Carbon do.
Click to expand...
Click to collapse
I didn't like the pie ;P But if you say it's ok, I'll give it a try when I'm in the mood to reinstall everything on the phone...
Anyway can you go lower than those cpu voltage on your OP? Or is it really not stable?
Mine's 1000 is at 0x2c, 800 at 0x20, and that's the lowest I can go.
Click to expand...
Click to collapse
Actually I didn't recheck those two and focused on lower freqs - these were the limits with older LiveOPP, but now I can go to 0x22 and 0x2c.
In fact, 0x24 and 0x2f are already undervolted values - original are 0x28 and 0x32. But every bit counts, especially on higher freqs.
Thanks for the tip
But what's more interesting - 900MHz works at 0x23 (didn't test that before - just took a voltage halfway between 800 and 1000)... there's something wrong with this ARM_100_OPP, but I don't know what yet... Will test the rest again later and post my results.
And thanks for the gpu voltage :good: , I actually use that value now :laugh:
Click to expand...
Click to collapse
Your welcome
When I have time, I'll try to write how to quickly check undervolting limits for both cpu and gpu.
Mk

mkaluza said:
It's a pity... but I understand that's only the S Advance branch of Carbon thats dead - the rom itself is being developed further?
Click to expand...
Click to collapse
Yes, only for our device. It's not really dead yet.
The dev has been kind enough compiling new one once in a while.
I didn't like the pie ;P But if you say it's ok, I'll give it a try when I'm in the mood to reinstall everything on the phone...
Click to expand...
Click to collapse
Yeah, I could understand that. Too much of a hassle. Got to reinstall everything back again.
But you know, I always do clean flash, even with nightlies. Imagine backing up, factory reset and restoring everything in every 3-4 days.
But now I get really used to it
Actually I didn't recheck those two and focused on lower freqs - these were the limits with older LiveOPP, but now I can go to 0x22 and 0x2c.
In fact, 0x24 and 0x2f are already undervolted values - original are 0x28 and 0x32. But every bit counts, especially on higher freqs.
Thanks for the tip
But what's more interesting - 900MHz works at 0x23 (didn't test that before - just took a voltage halfway between 800 and 1000)... there's something wrong with this ARM_100_OPP, but I don't know what yet... Will test the rest again later and post my results.
Click to expand...
Click to collapse
No problem man, thought that information would be useful to you.
Yeah, it would be really nice to go lower, especially on 1000 and 800.
I'm gonna test the rest, and later I would let you know the lowest working voltage that I can go.
And honestly, I have no idea about kernel stuffs :silly: The least that I can do is to play around with it
Your welcome
When I have time, I'll try to write how to quickly check undervolting limits for both cpu and gpu.
Mk
Click to expand...
Click to collapse
Yes, please do. I would really appreciate that :fingers-crossed:

Reinkaos said:
Yes, only for our device. It's not really dead yet.
The dev has been kind enough compiling new one once in a while.
Click to expand...
Click to collapse
He also left a repo with build scripts and manual, so I'll try to build the rom.
Yeah, I could understand that. Too much of a hassle. Got to reinstall everything back again.
But you know, I always do clean flash, even with nightlies. Imagine backing up, factory reset and restoring everything in every 3-4 days.
But now I get really used to it
Click to expand...
Click to collapse
That's hardcore ;P I have patience to do it 1-2 times a year
Yeah, it would be really nice to go lower, especially on 1000 and 800.
I'm gonna test the rest, and later I would let you know the lowest working voltage that I can go.
Click to expand...
Click to collapse
mine crashed at 1000MHz/0x2c - I'm on 0x2d now and it seems ok
And honestly, I have no idea about kernel stuffs :silly: The least that I can do is to play around with it
Click to expand...
Click to collapse
You could always learn It's fun, all the info is there to read for free... all it takes is will and time
Yes, please do. I would really appreciate that :fingers-crossed:
Click to expand...
Click to collapse
I still cant post links, so you need to go to my github (mkaluza), open the i9070_kernel_CoCore-E repo and go to wiki on the right - there is a page "Undervolting janice". Hope this helps.
Mk

mkaluza said:
He also left a repo with build scripts and manual, so I'll try to build the rom.
Click to expand...
Click to collapse
Well that's a good news :good:
That's hardcore ;P I have patience to do it 1-2 times a year
Click to expand...
Click to collapse
LOL yeah
mine crashed at 1000MHz/0x2c - I'm on 0x2d now and it seems ok
Click to expand...
Click to collapse
I'm not sure if mine is really stable, gonna test it with your guide on github
You could always learn It's fun, all the info is there to read for free... all it takes is will and time
Click to expand...
Click to collapse
Yeah, I am learning right now
I still cant post links, so you need to go to my github (mkaluza), open the i9070_kernel_CoCore-E repo and go to wiki on the right - there is a page "Undervolting janice". Hope this helps.
Mk
Click to expand...
Click to collapse
So there are scripts that will provide me with some infos when doing UV-ing
And I'm not familiar with registers though, I only do it via liveopp, but still I'll try this
Thanks for the guide
Anyway I got a question about gpu, lets say my mali low_boost is 400 and high_boost is 480,
does it use the two freq only or it use the other freq in between 400 and 480 too?
P.S. hey you could just spam in OT threads to get 10 posts

Reinkaos said:
I'm not sure if mine is really stable, gonna test it with your guide on github
Click to expand...
Click to collapse
If you don't get random reboots/crashes than it is - when following my guide, the resulting voltage should be stable, but it isn't always so... I'ts just a starting point that can save you some initial crashes or the other way around - if it doesn't pass freq_jump test, then it isn't stable for sure
Anyway I got a question about gpu, lets say my mali low_boost is 400 and high_boost is 480,
does it use the two freq only or it use the other freq in between 400 and 480 too?
Click to expand...
Click to collapse
Only those two - three actually - also 200MHz (that is low_boost/2), but with ape_50_opp voltage, not the one from dvfs_config. There's not much point in doing any smarter gov because gpu intensive apps usually load it at 100% no matter how much power it has - they just have more fps then.
.P.S. hey you could just spam in OT threads to get 10 posts
Click to expand...
Click to collapse
Yeah, maybe, but if those are the rules, then I try to respect them - because I respect the community. (not because I'm some kind of by-the-book guy ;P I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).

mkaluza said:
I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
Click to expand...
Click to collapse
You like adrenaline, heh
PS: Sorry for OT

mkaluza said:
If you don't get random reboots/crashes than it is - when following my guide, the resulting voltage should be stable, but it isn't always so... I'ts just a starting point that can save you some initial crashes or the other way around - if it doesn't pass freq_jump test, then it isn't stable for sure
Click to expand...
Click to collapse
Hey, just letting you know, about opptop script, we don't have prcmu-qos folder in /debug. I thought maybe it have a different name, but I couldn't find ape_requirements and ddr_requirements. The others are working fine
Only those two - three actually - also 200MHz (that is low_boost/2), but with ape_50_opp voltage, not the one from dvfs_config. There's not much point in doing any smarter gov because gpu intensive apps usually load it at 100% no matter how much power it has - they just have more fps then.
Click to expand...
Click to collapse
Thanks for the infos :good:
Yeah, maybe, but if those are the rules, then I try to respect them - because I respect the community. (not because I'm some kind of by-the-book guy ;P I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
Click to expand...
Click to collapse
LOL, I'm curious though, what bike do yo own? Must be a real badass one

Force said:
You like adrenaline, heh
PS: Sorry for OT
Click to expand...
Click to collapse
I'ts more about freedom and versatility, but yeah sometimes I like to push it too
Reinkaos said:
Hey, just letting you know, about opptop script, we don't have prcmu-qos folder in /debug. I thought maybe it have a different name, but I couldn't find ape_requirements and ddr_requirements. The others are working fine
Click to expand...
Click to collapse
I forgot... this feature was written by me, so it's available only on my kernel for the moment. But it's not really that important - it was more for debugging purposes for me, now I left it as informative.
I'm trying to build Carbon rom for out phone since last night... when/if I'm done, I'll patch the kernel with my stuff and push it somewhere. What is your kernel version? I think that both carbon and vanir use the same, or at least similar one.
LOL, I'm curious though, what bike do yo own? Must be a real badass one
Click to expand...
Click to collapse
Not really I't an old BMW F650 - only 48 ponies (of which some might have already died of old age ;P). But in reality you can do most of the fun stuff with as little as 125cc Anything bigger is usefull for longer trips/highways/trips with passenger/etc... I mostly ride small country roads and light offroad, so I rarely go over 100km/h, so no badass machine is needed something like 350cc would be best I think. Actually - it's not the bike you ride, but how you ride it... and on narrow roads with many turns a bigger bike is event sometimes harder to ride...

mkaluza said:
I forgot... this feature was written by me, so it's available only on my kernel for the moment. But it's not really that important - it was more for debugging purposes for me, now I left it as informative.
I'm trying to build Carbon rom for out phone since last night... when/if I'm done, I'll patch the kernel with my stuff and push it somewhere. What is your kernel version? I think that both carbon and vanir use the same, or at least similar one.
Click to expand...
Click to collapse
Well ok then. Vanir got a 3.0.101 kernel. It's the same I think? I'll flash and test it when you're done, definitely.
Not really I't an old BMW F650 - only 48 ponies (of which some might have already died of old age ;P). But in reality you can do most of the fun stuff with as little as 125cc Anything bigger is usefull for longer trips/highways/trips with passenger/etc... I mostly ride small country roads and light offroad, so I rarely go over 100km/h, so no badass machine is needed something like 350cc would be best I think. Actually - it's not the bike you ride, but how you ride it... and on narrow roads with many turns a bigger bike is event sometimes harder to ride...
Click to expand...
Click to collapse
lol the biggest one I ever been on is about 130 cc. It's small, enough that you could squeeze through traffics
I don't know much about bike, but AFAIK those superbike need different kind of handling too.

Let's speak just about this kernel as for this is meant this thread

Please anyone tell me how to find the kernel link . I`m a noob at this part :silly: Thanks

pictorul20 said:
Please anyone tell me how to find the kernel link . I`m a noob at this part :silly: Thanks
Click to expand...
Click to collapse
Go here and see download link at top of page: https://github.com/mkaluza/i9070_kernel_CoCore-E
Download link : http://goo.gl/FvqPlg
Then check OP to see how to install it.

Force said:
Go here and see download link at top of page: https://github.com/mkaluza/i9070_kernel_CoCore-E
Download link : http://goo.gl/FvqPlg
Then check OP to see how to install it.
Click to expand...
Click to collapse
Many Thanks.

ROMs and Kernels, which are you running and why?

What's YOUR Set-Up?
Hello everyone, like most people here on XDA, I enjoy switching between ROMs and Kernels while keeping an eye out for a daily driver that I like best. If you have any other ROM/Kernel combinations that you enjoy and think others might also enjoy, please feel free to share them here and explain why it's awesome!
:laugh: :good: ​
This thread is for the Nexus 6P only
Currently I'm running:
Device: Nexus 6P - 32 GB - Aluminum (If you're curious )
ROM: Chroma (11/22) latest with SElinux Enforcing
Kernel: ElementalX (0.08) latest [SElinux Enforcing option ticked.]
Small Cluster - 1555 MHz (stock)
Large Cluster - 2054 MHz (Max)
Govenor - ElementalX
Min. CPU Frequency - 600 MHz
Max. CPU Frequency - 1824 MHz
GPU: Max = 600 MHz / Min = 180 MHz / Governor = msm-adreno-tz <------------- Anyone recommend a different governor? One for performance and the other interactive?
Color Setting Recommendations? (ElementalX App Only)
I/O Scheduler - FiOPS <----------------------- Anyone recommend a different I/O? BatterySaver/Performance/Interactive?
I'm also curious about the color fixes that Kernels purport to solve (washed out blacks? other issues?) and how to apply these fixes if someone can point me in the right direction or provide their own instructions and values for the color options (Everywhere I look just says tune to your liking but I need somewhere to start, and frankly, I don't know where to start)
I'm really enjoying this ROM/Kernel combo but I am having Battery Drain to the likes I've never seen before, which is probably my fault.
I'll attach logs from BetteryBatteryStats as well as the Battery Stats from Stock 6 or so hours after the posting of this thread (for accuracy).
Any 'Standard' or 'Conventional' logs needed to convey insightful information? for BBS or for anything else? Let me know.
Please let me know if you need any other information and perhaps how I can retrieve it for you (kinda noobish, but not extremely bad lol)
I'm certain it's a user issue but I don't know how to find and correct the issues myself, so any help would be greatly appreciated.
I'm running Chroma ROM for some of the simple customizations and its speed (I don't care about Layers [probably cuz I don't know how to use them]).
I'm running ElementalX simply for the Overclock/Underclock CPU options and the advanced color control (once I learn how to use it) but I don't care about any of the gestures, sweep2sleep,
NTFS r/w and exFAT support (no clue what this is), and Option to disable fsync (don't know what this is/does)
Lastly, what I'm looking for out of a ROM/Kernel combo is great battery life and great performance, with some fun features but definitely minimal. So if feel your setup matches these wants, and you don't mind sharing it here with me, as well as others who may be looking for a similar setup, please do so!
I, as well as most others on this forum, would also be happy to help troubleshoot any problems you may be experiencing with your ROM/Kernel combo to the best of our abilities but we cannot guarantee that we will be able to fix your phone and the responsibility of the device lies with you, the user.

Stock rooted rocks for the first 3 months until development picks up, kernel developers make enough changes and rom developers fully implement most features into their roms.

Enjoying Stock Rooted smoothness... for now!

No need to create multiple threads on exact same thing.
http://forum.xda-developers.com/nexus-6p/general/roms-kernels-running-t3257280/post64009263
Please stick to one thread.
Thanks! Thread closed.
Darth
Forum Moderator

Abandoned

abandoned.

Can this apply on mi 11?

huycoixvb said:
Can this apply on mi 11?
Click to expand...
Click to collapse
Not exactly.
This chart is for the sd865.
Mi11 has a sd888, so the voltage levels will be different.
The basic idea is the same. But it requires testing and proofing.

Do you have source of konabess app? If possibility, send me pls :3

Thanks really useful

Great guide, this post definitely deserves more views. Got one question: if my goal frequency is (let's say) 660MHz, isn't it better to set ddr7 and ddr8 max values to 11? Would it squeeze out more performance at max load, in your opinion?

Keppo2911 said:
Great guide, this post definitely deserves more views. Got one question: if my goal frequency is (let's say) 660MHz, isn't it better to set ddr7 and ddr8 max values to 11? Would it squeeze out more performance at max load, in your opinion?
Click to expand...
Click to collapse
Not really. The ddr timings are not really set for balanced performance.
Trottling happens alot, so finding a balance give overall better performance than burst performance thatxthen gives lower results due tocthe time to cool being longer than the time to heat up.
I was able to get a higher antutu score than stock at 670, with timings between 4-9
But its all based on user preference and work loads. These settings work excellently well for me.
The big difference though is the voltage table. Less electricity going in creates less heat.
The ram timings are just a minor tweak to add a bit more to the clock. Its the voltage that really changed big time for me. Lower volts, less heat, longer time at high clocks.

Patrick Morgan said:
Not really. The ddr timings are not really set for balanced performance.
Trottling happens alot, so finding a balance give overall better performance than burst performance thatxthen gives lower results due tocthe time to cool being longer than the time to heat up.
I was able to get a higher antutu score than stock at 670, with timings between 4-9
But its all based on user preference and work loads. These settings work excellently well for me.
The big difference though is the voltage table. Less electricity going in creates less heat.
The ram timings are just a minor tweak to add a bit more to the clock. Its the voltage that really changed big time for me. Lower volts, less heat, longer time at high clocks.
Click to expand...
Click to collapse
Loud n' clear, thanks alot!

How can I edit Votages is volts table ?

Can l do this in xiaomi mi 10t pro?

yeh with any smartphone with snapdragon from 855. Just root and install konabess from GitHub and overclock and undervolt

Patrick Morgan said:
abandoned.
Click to expand...
Click to collapse
Hi Patrick, sorry to ask but you abandoned for some reason?
I have a OnePlus 9R (SNAP 870) and it's hot, I'm looking for an undervolt on it but I can't find anything, could you give me some direction?

Use this table from this post in this video.
Max freq on Poco F3 is 683Mhz you have to try if can be overclock higher but Undervolt is still possible as all phones.
I recommend new version 0.15 on two lower freq retention and min_svs or low svs on third and do like in this table so 670 voltage SVS_L2.
I don't think that Snapdragon 870 is good choice for gaming better is to buy 865 and overclock to 950Mhz or 1ghz giving snapdragon 888 performance with lower temps than 870 and 888.
If you do root try to underclock CPU to 865+ 3ghz or 2.9ghz to lower temps performance difference isn't noticable.

vinyimp said:
Hi Patrick, sorry to ask but you abandoned for some reason?
I have a OnePlus 9R (SNAP 870) and it's hot, I'm looking for an undervolt on it but I can't find anything, could you give me some direction?
Click to expand...
Click to collapse
things just update faster than I have time to test.
my charts became old, even the one Dr.Brown is using on his video, its quite old missing voltage steps and have not been tested on the newer versions of Konabess.
my original thread here took about 3 months of my time testing every possible setting to make sure other users didnt brick or toast their devices.
I took everything down when I seen alot of new rom updates, and konabess updates were causing bugs in the settings I had here for many users.
I didn't have time to retest everything and update my charts, I also had to deal with people stealing my charts and claiming the work for them selves. which I had to open youtube reports, contact google with proof of my work contact admins here and a few other sites too, etc all because some people didn't want to add a credit of where they found my charts.
so after a good week of emailing and chatting on the phone with google fraud control i decided to not continue posting my work, that may actually cause damage if used wrongly was too much work to deal with.
I'm still just too busy. my phone is stock android non rooted now because some apps I use can't be hidden.
so, I have no time to update this thread. I have no desire to leave the information for others to brick their devices.
the chart on dr.browns video is older than my most up to date chart, but still even that is months behind the current app and rom version changes.
my best advice is, if your phone works the way you want it, dont mess with any of the clock speeds. just undervolt some steps that are commonly used and test those.
too many people have tried to overclock their phones GPUs above 900 and lost functionality (permanently) or just hard bricked the phone (where an unbrick tool wont recover it.)
many will say its harmless, but its about usage. if you game alot and want to game alot, overclocking will create more heat, even if you undervolt. the result will be a paperweight.
those many people are not you, and not your phone. so anything can happen.
be mindful and careful of the settings you use. and install a temperature monitor for CPU and GPU.
going over 70'c will risk the loss of your unit.

Patrick Morgan said:
things just update faster than I have time to test.
my charts became old, even the one Dr.Brown is using on his video, its quite old missing voltage steps and have not been tested on the newer versions of Konabess.
my original thread here took about 3 months of my time testing every possible setting to make sure other users didnt brick or toast their devices.
I took everything down when I seen alot of new rom updates, and konabess updates were causing bugs in the settings I had here for many users.
I didn't have time to retest everything and update my charts, I also had to deal with people stealing my charts and claiming the work for them selves. which I had to open youtube reports, contact google with proof of my work contact admins here and a few other sites too, etc all because some people didn't want to add a credit of where they found my charts.
so after a good week of emailing and chatting on the phone with google fraud control i decided to not continue posting my work, that may actually cause damage if used wrongly was too much work to deal with.
I'm still just too busy. my phone is stock android non rooted now because some apps I use can't be hidden.
so, I have no time to update this thread. I have no desire to leave the information for others to brick their devices.
the chart on dr.browns video is older than my most up to date chart, but still even that is months behind the current app and rom version changes.
my best advice is, if your phone works the way you want it, dont mess with any of the clock speeds. just undervolt some steps that are commonly used and test those.
too many people have tried to overclock their phones GPUs above 900 and lost functionality (permanently) or just hard bricked the phone (where an unbrick tool wont recover it.)
many will say its harmless, but its about usage. if you game alot and want to game alot, overclocking will create more heat, even if you undervolt. the result will be a paperweight.
those many people are not you, and not your phone. so anything can happen.
be mindful and careful of the settings you use. and install a temperature monitor for CPU and GPU.
going over 70'c will risk the loss of your unit.
Click to expand...
Click to collapse
Perfect understood Patrick, it's a shame all this happened, unfortunately people don't give value/recognition to people who help for free!
I'll enjoy and tell you my experience, my 9R is on OOS 11.2.6.6 (Stock) and with Kernel Stock as well (since there isn't much customization yet)
They ended up recommending the Dr. Brown video and I decided to do some tests, if the person copies the Overclock that he does in that video (905MHz) the device will not start, it will be necessary to flash the previous boot.img
This happened to me and I was able to reverse the situation (probably because the KERNEL does not support such clocks that would even be unnecessary)
But on his channel there is a more recent video teaching how to Underclock and so I took the clock's as a base and started to make my fine adjustments
Clocks follow this pattern; 512 - 490 - 455 - 445 - 305 - 295 - 195
Voltages as per your chart; SVS_L2 - SVS_L1 _ SVS_L0 - SVS_L0 - LOW_SVS - LOW_SVS - LOW_SVS
And the BUS frequencies I left original, so I found SWEET SPOT, the device is much cooler, stable, in games despite the Underclock holding well (80 FPS+ with graphics at maximum)
Hopefully there will soon be some app/kernel that can undervolt the CPU too, maybe just remove -25mv/-50mv and do some testing as most of the heat comes from it.
I'm quite satisfied and I'm grateful to you because without your charts in Dr. Brown's video, wouldn't know how to do!
I wish you all the best, success!

vinyimp said:
Perfect understood Patrick, it's a shame all this happened, unfortunately people don't give value/recognition to people who help for free!
I'll enjoy and tell you my experience, my 9R is on OOS 11.2.6.6 (Stock) and with Kernel Stock as well (since there isn't much customization yet)
They ended up recommending the Dr. Brown video and I decided to do some tests, if the person copies the Overclock that he does in that video (905MHz) the device will not start, it will be necessary to flash the previous boot.img
This happened to me and I was able to reverse the situation (probably because the KERNEL does not support such clocks that would even be unnecessary)
But on his channel there is a more recent video teaching how to Underclock and so I took the clock's as a base and started to make my fine adjustments
Clocks follow this pattern; 512 - 490 - 455 - 445 - 305 - 295 - 195
Voltages as per your chart; SVS_L2 - SVS_L1 _ SVS_L0 - SVS_L0 - LOW_SVS - LOW_SVS - LOW_SVS
And the BUS frequencies I left original, so I found SWEET SPOT, the device is much cooler, stable, in games despite the Underclock holding well (80 FPS+ with graphics at maximum)
Hopefully there will soon be some app/kernel that can undervolt the CPU too, maybe just remove -25mv/-50mv and do some testing as most of the heat comes from it.
I'm quite satisfied and I'm grateful to you because without your charts in Dr. Brown's video, wouldn't know how to do!
I wish you all the best, success!
Click to expand...
Click to collapse
I recommend Overclocking by your self to higher freq.
This config from video don't boot on any sn865 devices even Apollo but I can overclock to 940 MHz stable.
I know that Poco F3 has lock freq to 683 MHz after that doesn't boot.
I think your UV is too high 512 can get as low as SVS_L1 or SVS_L0

astronomy2021 said:
I recommend Overclocking by your self to higher freq.
This config from video don't boot on any sn865 devices even Apollo but I can overclock to 940 MHz stable.
I know that Poco F3 has lock freq to 683 MHz after that doesn't boot.
I think your UV is too high 512 can get as low as SVS_L1 or SVS_L0
Click to expand...
Click to collapse
Unfortunately on the OnePlus 9R (all stock) any clock higher than the original (670 MHz) the system doesn't boot (I don't know why, maybe some ROM limitation or KERNEL doesn't support it)
I ended up Underclocking to have a cooler device and in fact it is cooler without loss of performance in normal use and holding up well in games at maximum graphics
No artifacts, crashing or instability
As for the voltage on 512, it could really go with SVS_L1 - it goes between SVS_L2 and L1 on Patrick's Chart (525 - 512 - 490 MHz) I intend to do a test soon, for now it's stable and in games it doesn't get too hot!

vinyimp said:
Unfortunately on the OnePlus 9R (all stock) any clock higher than the original (670 MHz) the system doesn't boot (I don't know why, maybe some ROM limitation or KERNEL doesn't support it)
I ended up Underclocking to have a cooler device and in fact it is cooler without loss of performance in normal use and holding up well in games at maximum graphics
No artifacts, crashing or instability
As for the voltage on 512, it could really go with SVS_L1 - it goes between SVS_L2 and L1 on Patrick's Chart (525 - 512 - 490 MHz) I intend to do a test soon, for now it's stable and in games it doesn't get too hot!
Click to expand...
Click to collapse
No it is lock by Qualcomm to that freq so of doesn't boot it like 855+/860.
That why I buy Mi 10T with 865 and can be overclock to even 2ghz by someone.

astronomy2021 said:
No it is lock by Qualcomm to that freq so of doesn't boot it like 855+/860.
That why I buy Mi 10T with 865 and can be overclock to even 2ghz by someone.
Click to expand...
Click to collapse
Understood, a custom KERNEL doesn't unlock this lock by Qualcomm?
I had a OnePlus 8 with 865, today I just miss it

vinyimp said:
Understood, a custom KERNEL doesn't unlock this lock by Qualcomm?
I had a OnePlus 8 with 865, today I just miss it
Click to expand...
Click to collapse
Maybe can by i case of 855+ was lock on all phones from manufacturer process.
But early builds of F3 has unlock freq but after that they are block that why buying 865 is better if you want performance for gaming or emulation like switch. I now play Zelda breath of the wild on my Mi 10 t and after 168days will be Overclocking to 940Mhz giving me performance of 888.