https://github.com/xzr467706992/KonaBess/releases/tag/v0.14 is the app that allows us to play with frequency clocks, regulators, etc.
I wrote a post in another thread - How to Guide Redmi K40 Pro ROOT Tools. This is just the instructions so you can get right to it. Make sure you have the fastboot ROM installed (the way Xiaomi.eu is packaged or the MIUI source you used on your phone), or you can export in the KonaBess app to the root SD card and transfer back to your PC. I highly recommend using the most updated FastBoot and ADB tools found here, the guy is religious so go pray to your deity of choosing, or to the earth, wind, fire, whatever the heck you believe in I don't care. https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/ thanks bro for that tool.
****** SO HERE ARE THE INSTRUCTIONS SO YOU CAN GET MODDING!!!! *******
Just FYI, most people don't know what I'm talking about when I say "voltage regulators for the GPU." The goal here is to use the first one on the top of the list (top is lowest voltage, bottom is highest) that can support the frequency your GPU Mhz are defined at. As you go up a regulator, the voltage increases, which leads to more power usage and hotter temperatures. Note that I played with it a little bit, and it DOES NOT seem to allow large changes in frequencies (higher that is, without upping the regulator*** you may not be able to use the higher regulators because of a commit I found in KonaBess (noted later). So it's usefulness may be not as great as I had hoped on the OC side, the throttling side, yes this could be invaluable.
If it doesn't boot, ensure you have your fastboot ROM downloaded somewhere (or use the program, it will extract vendor_boot.img to the root directory for you, save off to your PC where fastboot is located as you'll have to use PWR+Volume Down to go to fastboot, then reinstall the original vendor_boot.img (the new format saves this info in this new partition) by typing:
fastboot flash vendor_boot vendor_boot.img
fastboot reboot
Now this tool looks great for underclocking. I booted at 295mhz low and 825mhz high without changing the voltage regulators. But note the program seems a bit buggy - it will (sometimes) drop the max clock when you change it, so you MAY need a kernel manager like SmartPack to set on boot the max clock speed. At least until the code is fixed. I was able to boot on a lower regulator at 150mhz BTW [LEVEL_LOW_SVS_D1], and I didn't notice any performance difference! Just watch out for dropped frames, which can happen if your spacing is too far apart, or your frequency clock not giving enough juice. This can be done just viewing the screen - set it how you like it - power hungry or power friendly or mix and match.
These are the GPU Voltage Regulator Names (extracted from Linux 5.6.41 K40 Pro Plus / Mi11i source, codenamed haydn), listed from lowest voltage to highest. You have 10 choices I believe (regulator 0 is always the max frequency, regulator 9 is the lowest frequency):
LEVEL_RETENTION (so low it may not display anything)
LEVEL_MIN_SVS
LEVEL_LOW_SVS_D1 (note: I got it to boot at 150mhz on this regulator)
LEVEL_LOW_SVS default for 315000000 (315mhz) [REGULATOR 9 STOCK]
LEVEL_LOW_SVS_L1 default for 379000000 (379mhz)
LEVEL_LOW_SVS_L2
LEVEL_SVS default for 443000000 (443mhz)
LEVEL_SVS_L0 default for 491000000 (490mhz)
LEVEL_SVS_L1 default for 540000000 (540mhz)
LEVEL_SVS_L2 default for 608000000 (608mhz)
LEVEL_NOM default for 676000000 (676mhz)
LEVEL_NOM_L1 default for 738000000 (738mhz)
LEVEL_NOM_L2
LEVEL_TURBO default for 778000000 (778mhz)
**LEVEL_TUBRO_L0 -> added by KonaBess, not sure you can actually use it as it would require a kernel modification
LEVEL_TURBO_L1 default for 840000000 (840mhz) [REGULATOR 0 STOCK]
The levels below are turned off by KonaBess on "old 888 firmware" in commit https://github.com/xzr467706992/KonaBess/commit/e12afa47c7255e5ce1d33d97700479f67449ff89 - I presume the K40 Pro Plus supports it as it has an 888+ qcom,speed-bin = <1> defined at 900mhz on the LEVEL_TURBO_L2 regulator in the file lahaina-gpu-v2.dtsi, while Mi11 code does not have this regulator defined in the file: qcom,rpmh-regulator-levels.h) NOTE: get fastboot up on your PC before you mess with any of these regulators, you'll need it! You'll be fastboot flashing vendor_boot.img a lot. The device is already super OC'd by Qualcomm stock. That's why 888's throttle so much. Now that may be GPU or CPU related, we don't know yet. This will give us some idea. Watch temps wisely:
LEVEL_TURBO_L2
LEVEL_SUPER_TURBO
LEVEL_SUPER_TURBO_NO_CPR (okay this regulator sounds scary - CPR is used to bring someone's heart back to life after it stops beating... use with EXTREME CAUTION. My guess is it turns off all overheating protection)
My K40 Pro Plus is packed up for resale, start a conversation with me if interested ($620 USD basically Mint condition + S&H, extra rugged case + cam lens tempered glass, no markup @ China price, Xiaomi.EU stable 12.5.3 rooted with Magisk Stable and has Vanced (YouTube and Music no ads), Netflix L1, Amazon US, AdAway, all Google Services and apps like Calendar, Contacts, Messages, Chome, Discovery, Lens, GPay always worked when I used the phone before, etc. just login to your Google account and everything will auto-setup). A guy said he'd buy it from me this Friday if I hold it for $700, we'll see about that. I know it works on T-mobile USA alright LTE (N41 5G IF deployed to your area, its not in Houston, TX yet for me to test) and many EU countries frequency coverage is even better. Start of conversation with me if interested I have loads of pics on other websites. Selling because I can only build so many kernels and I have way too many phones. **I'll delete this portion once sold, not sure if the XDA rules allow me to post it (sorry moderators if I violated a rule, just trying to give a great deal to someone who is looking for an 888, I'm not making ANY money).
Back to the topic at hand. I would begin starting at the 840mhz and switch it to one lower regulator, i.e. switch to TURBO instead, and likely drop the mhz too if it fails to boot. Then repeat the rest the same way (1 level down) but only modify 1 at a time, test, then it's fastboot time if it doesn't support it OR you succeeded (write down the numbers). Then run 3DBench 1 test run first. If that works fine, you can run the stress test for 20m after you're happy with all your new frequencies and see if it runs well (no fragments, no lag, etc). If so, keep it there. You should be able to see any FREQUENCY changes in SmartPack Kernel Manager (free on the Playstore or Github, under GPU menu). You can make up your own clock speeds too. I tried dropping the max clock to 825mhz from 840mhz and it booted fine; the AnTuTu v9.0.5-OB graphics segment was lag free. This is silicon lottery customization BTW, some chips will run better at different frequencies and regulators than others.
I hope you find this post useful, took me A VERY LONG TIME to put it together to simplify the GPU adjustments using KonaBess app. It's easiest to make small changes, remember OC'ing an already OC'd device (straight from QCOM, yes they OC'd it) is not likely to work work well - any OC attempts should be like +5000mhz or +10000 at a time. All 888 phones throttle on the default config when pushed hard enough (i.e. like during a bench / stress test session). Since you are mostly testing graphics, I suggest the 3DMark 20 minute stress test for stability verification. If you underclock the GPU enough, you can probably eliminate throttling while still getting a good bench result, while adding to your screen on time (SOT). Throttle free and fast, with decent battery, and you have a winner.
Although if you want to play with the often randomly changing AnTuTu benchmark, you can do that that a little bit faster. I just think that is used by OEMs to sell phones after using it for so many years, I noticed the version #s started to increment a lot faster as more 888 phones were released. From AnTuTu v9.0.1-OB to v9.0.5-OB scores just randomly seemed to change. Companies like RealMe and Nubia (RedMagic) cheat the bench anyway to give you higher scores that don't mean anything in actual use. 3DMark seems like a more consistent bench. Anyway, regardless of which bench you chooose, mark the first runs at the current settings. Let the phone cool down and close all open apps before benching (5 minutes is a good rule of thumb for all apps to load). For more consistency, turn on airplane mode and turn off bluetooth / nfc / etc. Try to run your benches at the same battery % (have that charger ready).
Please post your findings here and notate your device, the mhz you chose, the regulator you chose, etc. so people can work from your values. As I mentioned, you are testing your silicon lotto ticket here - most chips will differ between one another. Your 888 only has to pass a minimum spec to make it to production. Some are all stars and some barely make the cutoff. That's life, it's okay, they are all fast anyway. Even the worst chip will still be fast.
Feel free to like this post if it helped you out!
mslezak said:
https://github.com/xzr467706992/KonaBess/releases/tag/v0.14 is the app that allows us to play with frequency clocks, regulators, etc.
I wrote a post in another thread - How to Guide Redmi K40 Pro ROOT Tools. This is just the instructions so you can get right to it. Make sure you have the fastboot ROM installed (the way Xiaomi.eu is packaged or the MIUI source you used on your phone), or you can export in the KonaBess app to the root SD card and transfer back to your PC. I highly recommend using the most updated FastBoot and ADB tools found here, the guy is religious so go pray to your deity of choosing, or to the earth, wind, fire, whatever the heck you believe in I don't care. https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/ thanks bro for that tool.
****** SO HERE ARE THE INSTRUCTIONS SO YOU CAN GET MODDING!!!! *******
Just FYI, most people don't know what I'm talking about when I say "voltage regulators for the GPU." The goal here is to use the first one on the top of the list (top is lowest voltage, bottom is highest) that can support the frequency your GPU Mhz are defined at. As you go up a regulator, the voltage increases, which leads to more power usage and hotter temperatures. Note that I played with it a little bit, and it DOES NOT seem to allow large changes in frequencies (higher that is, without upping the regulator*** you may not be able to use the higher regulators because of a commit I found in KonaBess (noted later). So it's usefulness may be not as great as I had hoped on the OC side, the throttling side, yes this could be invaluable.
If it doesn't boot, ensure you have your fastboot ROM downloaded somewhere (or use the program, it will extract vendor_boot.img to the root directory for you, save off to your PC where fastboot is located as you'll have to use PWR+Volume Down to go to fastboot, then reinstall the original vendor_boot.img (the new format saves this info in this new partition) by typing:
fastboot flash vendor_boot vendor_boot.img
fastboot reboot
Now this tool looks great for underclocking. I booted at 295mhz low and 825mhz high without changing the voltage regulators. But note the program seems a bit buggy - it will (sometimes) drop the max clock when you change it, so you MAY need a kernel manager like SmartPack to set on boot the max clock speed. At least until the code is fixed. I was able to boot on a lower regulator at 150mhz BTW [LEVEL_LOW_SVS_D1], and I didn't notice any performance difference! Just watch out for dropped frames, which can happen if your spacing is too far apart, or your frequency clock not giving enough juice. This can be done just viewing the screen - set it how you like it - power hungry or power friendly or mix and match.
These are the GPU Voltage Regulator Names (extracted from Linux 5.6.41 K40 Pro Plus / Mi11i source, codenamed haydn), listed from lowest voltage to highest. You have 10 choices I believe (regulator 0 is always the max frequency, regulator 9 is the lowest frequency):
LEVEL_RETENTION (so low it may not display anything)
LEVEL_MIN_SVS
LEVEL_LOW_SVS_D1 (note: I got it to boot at 150mhz on this regulator)
LEVEL_LOW_SVS default for 315000000 (315mhz) [REGULATOR 9 STOCK]
LEVEL_LOW_SVS_L1 default for 379000000 (379mhz)
LEVEL_LOW_SVS_L2
LEVEL_SVS default for 443000000 (443mhz)
LEVEL_SVS_L0 default for 491000000 (490mhz)
LEVEL_SVS_L1 default for 540000000 (540mhz)
LEVEL_SVS_L2 default for 608000000 (608mhz)
LEVEL_NOM default for 676000000 (676mhz)
LEVEL_NOM_L1 default for 738000000 (738mhz)
LEVEL_NOM_L2
LEVEL_TURBO default for 778000000 (778mhz)
**LEVEL_TUBRO_L0 -> added by KonaBess, not sure you can actually use it as it would require a kernel modification
LEVEL_TURBO_L1 default for 840000000 (840mhz) [REGULATOR 0 STOCK]
The levels below are turned off by KonaBess on "old 888 firmware" in commit https://github.com/xzr467706992/KonaBess/commit/e12afa47c7255e5ce1d33d97700479f67449ff89 - I presume the K40 Pro Plus supports it as it has an 888+ qcom,speed-bin = <1> defined at 900mhz on the LEVEL_TURBO_L2 regulator in the file lahaina-gpu-v2.dtsi, while Mi11 code does not have this regulator defined in the file: qcom,rpmh-regulator-levels.h) NOTE: get fastboot up on your PC before you mess with any of these regulators, you'll need it! You'll be fastboot flashing vendor_boot.img a lot. The device is already super OC'd by Qualcomm stock. That's why 888's throttle so much. Now that may be GPU or CPU related, we don't know yet. This will give us some idea. Watch temps wisely:
LEVEL_TURBO_L2
LEVEL_SUPER_TURBO
LEVEL_SUPER_TURBO_NO_CPR (okay this regulator sounds scary - CPR is used to bring someone's heart back to life after it stops beating... use with EXTREME CAUTION. My guess is it turns off all overheating protection)
My K40 Pro Plus is packed up for resale, start a conversation with me if interested ($620 USD basically Mint condition + S&H, extra rugged case + cam lens tempered glass, no markup @ China price, Xiaomi.EU stable 12.5.3 rooted with Magisk Stable and has Vanced (YouTube and Music no ads), Netflix L1, Amazon US, AdAway, all Google Services and apps like Calendar, Contacts, Messages, Chome, Discovery, Lens, GPay always worked when I used the phone before, etc. just login to your Google account and everything will auto-setup). A guy said he'd buy it from me this Friday if I hold it for $700, we'll see about that. I know it works on T-mobile USA alright LTE (N41 5G IF deployed to your area, its not in Houston, TX yet for me to test) and many EU countries frequency coverage is even better. Start of conversation with me if interested I have loads of pics on other websites. Selling because I can only build so many kernels and I have way too many phones. **I'll delete this portion once sold, not sure if the XDA rules allow me to post it (sorry moderators if I violated a rule, just trying to give a great deal to someone who is looking for an 888, I'm not making ANY money).
Back to the topic at hand. I would begin starting at the 840mhz and switch it to one lower regulator, i.e. switch to TURBO instead, and likely drop the mhz too if it fails to boot. Then repeat the rest the same way (1 level down) but only modify 1 at a time, test, then it's fastboot time if it doesn't support it OR you succeeded (write down the numbers). Then run 3DBench 1 test run first. If that works fine, you can run the stress test for 20m after you're happy with all your new frequencies and see if it runs well (no fragments, no lag, etc). If so, keep it there. You should be able to see any FREQUENCY changes in SmartPack Kernel Manager (free on the Playstore or Github, under GPU menu). You can make up your own clock speeds too. I tried dropping the max clock to 825mhz from 840mhz and it booted fine; the AnTuTu v9.0.5-OB graphics segment was lag free. This is silicon lottery customization BTW, some chips will run better at different frequencies and regulators than others.
I hope you find this post useful, took me A VERY LONG TIME to put it together to simplify the GPU adjustments using KonaBess app. It's easiest to make small changes, remember OC'ing an already OC'd device (straight from QCOM, yes they OC'd it) is not likely to work work well - any OC attempts should be like +5000mhz or +10000 at a time. All 888 phones throttle on the default config when pushed hard enough (i.e. like during a bench / stress test session). Since you are mostly testing graphics, I suggest the 3DMark 20 minute stress test for stability verification. If you underclock the GPU enough, you can probably eliminate throttling while still getting a good bench result, while adding to your screen on time (SOT). Throttle free and fast, with decent battery, and you have a winner.
Although if you want to play with the often randomly changing AnTuTu benchmark, you can do that that a little bit faster. I just think that is used by OEMs to sell phones after using it for so many years, I noticed the version #s started to increment a lot faster as more 888 phones were released. From AnTuTu v9.0.1-OB to v9.0.5-OB scores just randomly seemed to change. Companies like RealMe and Nubia (RedMagic) cheat the bench anyway to give you higher scores that don't mean anything in actual use. 3DMark seems like a more consistent bench. Anyway, regardless of which bench you chooose, mark the first runs at the current settings. Let the phone cool down and close all open apps before benching (5 minutes is a good rule of thumb for all apps to load). For more consistency, turn on airplane mode and turn off bluetooth / nfc / etc. Try to run your benches at the same battery % (have that charger ready).
Please post your findings here and notate your device, the mhz you chose, the regulator you chose, etc. so people can work from your values. As I mentioned, you are testing your silicon lotto ticket here - most chips will differ between one another. Your 888 only has to pass a minimum spec to make it to production. Some are all stars and some barely make the cutoff. That's life, it's okay, they are all fast anyway. Even the worst chip will still be fast.
Feel free to like this post if it helped you out!
Click to expand...
Click to collapse
Many thanks for your contribute. Hope that this community will grow and we'll have TWRP and custom ROM son
It will take some time, but someone in China is likely working on it since Venus (Mi11) TWRP just came out.
mslezak said:
It will take some time, but someone in China is likely working on it since Venus (Mi11) TWRP just came out.
Click to expand...
Click to collapse
BTW it could be out there already if you search Chinese websites, someone just "found" the Mi11 TWRP in Chinese, we have no idea who made it. I'd search for haydn TWRP or K40 Pro TWRP and see where it gets you ...
mslezak said:
BTW it could be out there already if you search Chinese websites, someone just "found" the Mi11 TWRP in Chinese, we have no idea who made it. I'd search for haydn TWRP or K40 Pro TWRP and see where it gets you ...
Click to expand...
Click to collapse
Wow, really looking forward to this. I'll keep an eye out. As far as i know there're a TWRP for alioth. Soon be haydn.
Can you port ROM for this devices. I'm trying to learn but there're no up to day document for me to start
makiothekid said:
Wow, really looking forward to this. I'll keep an eye out. As far as i know there're a TWRP for alioth. Soon be haydn.
Can you port ROM for this devices. I'm trying to learn but there're no up to day document for me to start
Click to expand...
Click to collapse
Someone needs to make the kernel first, AOSP, which will be a challenge. I have never done it.
awesome - thanks very much for your efforts!
I have set 840MHz to Turbo and 768 on Nom_L3.
The phone is booting fine.
So is there any way to know if the settings are applied?
Kernel manager shows power level 9.
And clock reaches 840 fine during tests.
I applied with the flash option in konaBess.
11x pro
Going to try this now!
I also started to undervolting the Snapdragon 888 GPU. I'm on xiaomi.eu weekly ROM.
I cannot use any Benchmark/stresstest app because of the Xiaomi block. Can someone help me please, how to use 3DMark or something like that on a xiaomi.eu ROM?
Since a week I'm using the following values. It seems to be stable including gaming.
Kernel manager shows power level 10 (because of adding custom freq?) and i need to set max. freq to 840 MHz on boot in kernel manager.
Here are my first results:
Voltage LevelDefault Frequency (MHz)UV Frequency (MHz)NotesLEVEL_RETENTION--not available on haydnLEVEL_MIN_SVS--LEVEL_LOW_SVS_D1-150added 1 of max. 1 custom FrequencyLEVEL_LOW_SVS315315LEVEL_LOW_SVS_L1379379LEVEL_LOW_SVS_L2-443LEVEL_SVS443491LEVEL_SVS_L0491540LEVEL_SVS_L1540608LEVEL_SVS_L2608676LEVEL_NOM676738LEVEL_NOM_L1738-LEVEL_NOM_L2-778LEVEL_NOM_L3--not mentioned in the first postLEVEL_TURBO778800LEVEL_TUBRO_L0--not tried, see note in first postLEVEL_TURBO_L1840-
mslezak said:
https://github.com/xzr467706992/KonaBess/releases/tag/v0.14 is the app that allows us to play with frequency clocks, regulators, etc.
I wrote a post in another thread - How to Guide Redmi K40 Pro ROOT Tools. This is just the instructions so you can get right to it. Make sure you have the fastboot ROM installed (the way Xiaomi.eu is packaged or the MIUI source you used on your phone), or you can export in the KonaBess app to the root SD card and transfer back to your PC. I highly recommend using the most updated FastBoot and ADB tools found here, the guy is religious so go pray to your deity of choosing, or to the earth, wind, fire, whatever the heck you believe in I don't care. https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/ thanks bro for that tool.
****** SO HERE ARE THE INSTRUCTIONS SO YOU CAN GET MODDING!!!! *******
Just FYI, most people don't know what I'm talking about when I say "voltage regulators for the GPU." The goal here is to use the first one on the top of the list (top is lowest voltage, bottom is highest) that can support the frequency your GPU Mhz are defined at. As you go up a regulator, the voltage increases, which leads to more power usage and hotter temperatures. Note that I played with it a little bit, and it DOES NOT seem to allow large changes in frequencies (higher that is, without upping the regulator*** you may not be able to use the higher regulators because of a commit I found in KonaBess (noted later). So it's usefulness may be not as great as I had hoped on the OC side, the throttling side, yes this could be invaluable.
If it doesn't boot, ensure you have your fastboot ROM downloaded somewhere (or use the program, it will extract vendor_boot.img to the root directory for you, save off to your PC where fastboot is located as you'll have to use PWR+Volume Down to go to fastboot, then reinstall the original vendor_boot.img (the new format saves this info in this new partition) by typing:
fastboot flash vendor_boot vendor_boot.img
fastboot reboot
Now this tool looks great for underclocking. I booted at 295mhz low and 825mhz high without changing the voltage regulators. But note the program seems a bit buggy - it will (sometimes) drop the max clock when you change it, so you MAY need a kernel manager like SmartPack to set on boot the max clock speed. At least until the code is fixed. I was able to boot on a lower regulator at 150mhz BTW [LEVEL_LOW_SVS_D1], and I didn't notice any performance difference! Just watch out for dropped frames, which can happen if your spacing is too far apart, or your frequency clock not giving enough juice. This can be done just viewing the screen - set it how you like it - power hungry or power friendly or mix and match.
These are the GPU Voltage Regulator Names (extracted from Linux 5.6.41 K40 Pro Plus / Mi11i source, codenamed haydn), listed from lowest voltage to highest. You have 10 choices I believe (regulator 0 is always the max frequency, regulator 9 is the lowest frequency):
LEVEL_RETENTION (so low it may not display anything)
LEVEL_MIN_SVS
LEVEL_LOW_SVS_D1 (note: I got it to boot at 150mhz on this regulator)
LEVEL_LOW_SVS default for 315000000 (315mhz) [REGULATOR 9 STOCK]
LEVEL_LOW_SVS_L1 default for 379000000 (379mhz)
LEVEL_LOW_SVS_L2
LEVEL_SVS default for 443000000 (443mhz)
LEVEL_SVS_L0 default for 491000000 (490mhz)
LEVEL_SVS_L1 default for 540000000 (540mhz)
LEVEL_SVS_L2 default for 608000000 (608mhz)
LEVEL_NOM default for 676000000 (676mhz)
LEVEL_NOM_L1 default for 738000000 (738mhz)
LEVEL_NOM_L2
LEVEL_TURBO default for 778000000 (778mhz)
**LEVEL_TUBRO_L0 -> added by KonaBess, not sure you can actually use it as it would require a kernel modification
LEVEL_TURBO_L1 default for 840000000 (840mhz) [REGULATOR 0 STOCK]
The levels below are turned off by KonaBess on "old 888 firmware" in commit https://github.com/xzr467706992/KonaBess/commit/e12afa47c7255e5ce1d33d97700479f67449ff89 - I presume the K40 Pro Plus supports it as it has an 888+ qcom,speed-bin = <1> defined at 900mhz on the LEVEL_TURBO_L2 regulator in the file lahaina-gpu-v2.dtsi, while Mi11 code does not have this regulator defined in the file: qcom,rpmh-regulator-levels.h) NOTE: get fastboot up on your PC before you mess with any of these regulators, you'll need it! You'll be fastboot flashing vendor_boot.img a lot. The device is already super OC'd by Qualcomm stock. That's why 888's throttle so much. Now that may be GPU or CPU related, we don't know yet. This will give us some idea. Watch temps wisely:
LEVEL_TURBO_L2
LEVEL_SUPER_TURBO
LEVEL_SUPER_TURBO_NO_CPR (okay this regulator sounds scary - CPR is used to bring someone's heart back to life after it stops beating... use with EXTREME CAUTION. My guess is it turns off all overheating protection)
My K40 Pro Plus is packed up for resale, start a conversation with me if interested ($620 USD basically Mint condition + S&H, extra rugged case + cam lens tempered glass, no markup @ China price, Xiaomi.EU stable 12.5.3 rooted with Magisk Stable and has Vanced (YouTube and Music no ads), Netflix L1, Amazon US, AdAway, all Google Services and apps like Calendar, Contacts, Messages, Chome, Discovery, Lens, GPay always worked when I used the phone before, etc. just login to your Google account and everything will auto-setup). A guy said he'd buy it from me this Friday if I hold it for $700, we'll see about that. I know it works on T-mobile USA alright LTE (N41 5G IF deployed to your area, its not in Houston, TX yet for me to test) and many EU countries frequency coverage is even better. Start of conversation with me if interested I have loads of pics on other websites. Selling because I can only build so many kernels and I have way too many phones. **I'll delete this portion once sold, not sure if the XDA rules allow me to post it (sorry moderators if I violated a rule, just trying to give a great deal to someone who is looking for an 888, I'm not making ANY money).
Back to the topic at hand. I would begin starting at the 840mhz and switch it to one lower regulator, i.e. switch to TURBO instead, and likely drop the mhz too if it fails to boot. Then repeat the rest the same way (1 level down) but only modify 1 at a time, test, then it's fastboot time if it doesn't support it OR you succeeded (write down the numbers). Then run 3DBench 1 test run first. If that works fine, you can run the stress test for 20m after you're happy with all your new frequencies and see if it runs well (no fragments, no lag, etc). If so, keep it there. You should be able to see any FREQUENCY changes in SmartPack Kernel Manager (free on the Playstore or Github, under GPU menu). You can make up your own clock speeds too. I tried dropping the max clock to 825mhz from 840mhz and it booted fine; the AnTuTu v9.0.5-OB graphics segment was lag free. This is silicon lottery customization BTW, some chips will run better at different frequencies and regulators than others.
I hope you find this post useful, took me A VERY LONG TIME to put it together to simplify the GPU adjustments using KonaBess app. It's easiest to make small changes, remember OC'ing an already OC'd device (straight from QCOM, yes they OC'd it) is not likely to work work well - any OC attempts should be like +5000mhz or +10000 at a time. All 888 phones throttle on the default config when pushed hard enough (i.e. like during a bench / stress test session). Since you are mostly testing graphics, I suggest the 3DMark 20 minute stress test for stability verification. If you underclock the GPU enough, you can probably eliminate throttling while still getting a good bench result, while adding to your screen on time (SOT). Throttle free and fast, with decent battery, and you have a winner.
Although if you want to play with the often randomly changing AnTuTu benchmark, you can do that that a little bit faster. I just think that is used by OEMs to sell phones after using it for so many years, I noticed the version #s started to increment a lot faster as more 888 phones were released. From AnTuTu v9.0.1-OB to v9.0.5-OB scores just randomly seemed to change. Companies like RealMe and Nubia (RedMagic) cheat the bench anyway to give you higher scores that don't mean anything in actual use. 3DMark seems like a more consistent bench. Anyway, regardless of which bench you chooose, mark the first runs at the current settings. Let the phone cool down and close all open apps before benching (5 minutes is a good rule of thumb for all apps to load). For more consistency, turn on airplane mode and turn off bluetooth / nfc / etc. Try to run your benches at the same battery % (have that charger ready).
Please post your findings here and notate your device, the mhz you chose, the regulator you chose, etc. so people can work from your values. As I mentioned, you are testing your silicon lotto ticket here - most chips will differ between one another. Your 888 only has to pass a minimum spec to make it to production. Some are all stars and some barely make the cutoff. That's life, it's okay, they are all fast anyway. Even the worst chip will still be fast.
Feel free to like this post if it helped you out!
Click to expand...
Click to collapse
How do I extract vendor_boot.img directly from the phone? I have op9pro and can't find the rom version I have installed, and konabess seems to extract boot.img
Unfortunately, this doesn't work for the Mi 11X Pro. Doesn't it support phones with the Snapdragon 888 chipset?
Related
Ok so how in the world are these people getting such a high overclock? I've been doing some research and I just cant figure it out.
Check this link: http://www.greenecomputing.com/apps/linpack/linpack-by-device/ and scroll down to the eris section. There is one guy in there who actually pulled off a 864MHz Overclock. I know thats a hard thing to do because the highest I've ever got was 760MHz and that lasted like 30 seconds before my Eris just gave up. I've accedintly put my phone in the 800MHz range and it just froze instantly. So far the highest stable range has been 748MHz.
Does anybody now something I dont? Is there a trick to getting that high of an overclock with the Eris?
From what I understand, there's a range in the stable clock cycle range that any chip/processor can run at. When the Eris was built, the "sweet spot" (stable) speed was apparently 528MHz (although this certainly could have been selected for marketing purposes too).
Most, but not all, Erii can run safely at 710MHz and be stable. However, we have seen instances where folks have installed ROMs that were overclocked to 710MHz as a default and their phones would not complete booting-up.
Others have indeed "pushed the envelope" by running in the high 700s and even in the high- to mid-800s as you've reported. However, there is usually a cost associated with doing this in terms of decreased life-span of your CPU. That being said, there are some members that have reported having a stable phone running 800MHz or higher. Your mileage will vary, as you have seen -- it really depends on your phone.
Cheers!
I can run 806 just fine, but most of the time I just choose to run at 767 or even 748, mainly because I don't need *that* much speed versus the larger battery drain at such high speeds.
Flashing GB has recently given me the ability to OC to 806, haven't tried any further.
Well, there are two things going on.
The first is that your phone hardware is like any other macroscopic object in the universe - they have variable characteristics. Go to the store and look carefully at the apples they have for sale - pick a given variety, and you'll notice that every one of them is just slightly different from the next.
If you were to zoom in and have a look with a good microscope at the transistors in your processor chip - you would first notice that: (a) there are millions of them!, and (b) they all look very similar, but are not exactly identical. That's just the nature of things - the manufacturing processes have some amount of (hopefully well controlled) variations.
But, when it comes to computer chips executing software instructions, we definitely want them to all behave identically. So, what to do? The answer is, run them all at a sufficiently low enough speed (and a large enough voltage) that the small natural variations from transistor to transistor never make a difference in how the outputs from those transistors are interpreted.
You've heard the expression "timing is everything", yes? Nowhere does this expression apply better than in computer chip design. I'll use a stupid analogy to illustrate how this works.
Suppose you had a marching band ... not like the ordinary kind, but instead, a band full of morons. So stupid, in fact, that you teach them to play songs like this:
"You nearest two neighbors will hand you a note just before each beat of the kettle drum, and you will decide based on those notes what note to play yourself after you hear the next kettle drum beat - and then you will hand that note to your neighbor".
In this analogy, each (transistor) logic gate in the chip is a moron band member, and the kettle drum is like the system clock.
Well, each moron (transistor logic gate) in the band will need to take some time to decide what note to play next. And it is plainly obvious, that if the moron's neighbors (other morons/gates) don't hand their notes off by the time the kettle drum beats, the wrong decision will be made. Chip designers call this "setup time".
Also, since we presume that the band members are morons, they actually need to some amount of time to stare at the notes from their neighbors to make up their mind - sometimes so slowly that the beat of the kettle drum has already been heard some time ago before they make up their mind. If the neighbor moron band members were to "yank their notes away too quickly", the receiving moron band member (logic gate) might again make the wrong decision. Chip designers call second sort of timing measurement "hold time".
So, this is a very simplistic view of chip design: the designer needs to make sure that the inputs (notes) to every gate (moron band members) arrives well enough ahead of the clock (kettle drum beat), and stay stable for a short period of time after the clock (kettle drum) beat. And they also have to consider how slowly each gate (moron) can "make up his mind" - because of course, that introduces delay in passing off information to other gates (morons) at the next beat of the clock (drum).
If you followed this analogy closely, the question might have also occurred to you, "what happens if the morons in the band don't all hear the kettle drum beat at precisely the same time?" In the analogy to chip design, this is the problem of clock distribution - because at each moron (gate), the decisions are made when they individually hear the kettle drum (clock) beat. So, there could be some major trouble if a moron (gate) was supposed to receive notes (signals) from other morons (gates) that were hearing the kettle drum (clock) either much to early, or much too late, compared to their neighbors.
Now, marching bands are only a little bit like this, especially since we said in our example that only nearby neighbor morons (gates) were involved; but in chip design, both clocks and signals may need to be passed great distances away, not just to nearest neighbors.
A major part of chip design revolves around exactly these concepts: trying to compute exactly what the "setup", "hold", and "delay" time min/max values are for millions and millions of gate and signal paths in the chip, and also knowing exactly how long it will take for the signals and clocks to travel from their source to destination(s).
If only a single one of the millions of morons (gates) gets this wrong, the whole song is ruined.
So, it should be clear that if you run the system clock really, really slowly, you generally won't bump in to any setup or delay hazards (hold is a little trickier, but we can ignore that). The clock beats so slowly that signals have plenty of time to reach their destinations, and also the amount of delay through each gate is negligible compared to the long amounts of time that using a slow clock grants you.
But as you increase the clock faster and faster, you start shaving away available time for signals to get to their destinations, and come closer and closer to one of these hazards - a "setup" or "hold" violation. Not only that, but the delays across the chip - which are negligible for a slow clock - start to become really important.
Now, I spent a lot of words up there to illustrate something: the timing problem only very weakly depends what software is running on the phone, it is a function of the hardware alone. You can't "install some software" to make this problem go away. Your microprocessor will run flawlessly up until a certain clock speed, and then disaster!.
And that disaster could be the fault of a single transistor out of tens of millions - generally, a transistor which for some reason, is "weaker" than most of it's neighbors - or it has to push a signal through a line which is oddly more resistive than it should be - and therefore slower.
The second thing to be aware of is that these benchmarks are being run on a multitasking operating system - if you run them 5 times in a row, you will see that you get a different benchmark value each time you run them - because other activities on the phone and the kernel's scheduler conspired to give your benchmark app slightly less or slightly more total attention during the elapsed (wall) clock time of the benchmark.
So, since that website records the "best of the best" - make sure you run your benchmark twenty to fifty times, see if you can diddle the oom_adj value of your process while it is running, and delete all other applications from your phone so that it is the only thing running.
To illustrate that there's no "magic" going on here, I'll give you a concrete example. Two days ago I ran that Linpack app on my Eris. Here's what I did:
OS: GSB v1.2
min cpu = 748 Mhz
max cpu = 748 Mhz
governor = performance
JIT on
killed off most idle apps
And I got linpack scores that varied from 4.8 to 5.1 over two or three runs.
Now, let's compare (the best of) those results to the ones reported in the Benchmark results, but scaled to a different frequency:
(844 Mhz / 748 Mhz) * 5.1 = 5.75
Note that this is plenty close the the value reported at 844 Mhz.
If you want to convince yourself that your phone is fine, set the cpu speed min=max = whatever. Then run the benchmark a couple of times, and compare your result
(844 Mhz / whatever ) * your_best_result
And you will see that your phone is no "different" than the best Eris out there - except that it can't run at 844 Mhz. That latter part is just the luck of the draw.
bftb0
Not all CPUs are created equal. Some are stable at higher frequencies than others. This because many of the steps in CPU production rely on chemical processes. Doping, silicon wafer growth, electroplating, etc. Manufacturers use a technique called CPU binning to help them sort out the better chips.
Where I learned this:
http://www.tomshardware.com/picturestory/514-intel-cpu-processor-core-i7.html
@bftb0...that was beautiful...
If you're going to try higher rates, leave logcat running and watch for errors.
I love that analogy. Mostly because it's fun to make fun of morons, and the more the better!
bftb0, could I have your permission to repost that (up through "and therefore slower.") on FaceBook? I will note before the quote that this applies to any kind of computing device, but I wouldn't change anything you said. I would, of course, also give a linked credit to you, this thread, and XDA.
I was going to ask you in a PM, so I didn't put you on the spot in public, but you must have used to get way too many PMs since you disabled that.
I won't be offended if you say no, just thought I'd ask.
Actually most of those are faked.
There used to be 1ghz scores for the eris. They're quite easy to fake. While some phones can get quite high due to the way CPUs are processed... the linpack website is incredibly easy to fool.
roirraW "edor" ehT said:
could I have your permission to repost that (up through "and therefore slower.") on FaceBook? I will note before the quote that this applies to any kind of computing device, but I wouldn't change anything you said. I would, of course, also give a linked credit to you, this thread, and XDA.
Click to expand...
Click to collapse
Sure.
+10char
bftb0 said:
Sure.
+10char
Click to expand...
Click to collapse
bftb0, I never took the time back then to say thank you for your explanation. I'd like to do that now. Thank you. Obviously I know more about Android and the phones its installed on now. I have a better understanding of this subject and others you have helped with.
Also I haven't seen you around lately. I certainty hope your ok and hope to see you around again.
DINC|CM7|INCREDIKERNEL
I see him all the time. Well I don't actually see him but I do benefit a lot from his advise and insites. Also I've been able to run my Eris at 787mhz without issues but as a norm run at 710mhz.
I stumbled upon these apps by dumb luck and decided to post this for anyone that doesn't know they exist. The dev is Chinese I am guessing based on a lot of his apps being in Chinese. He soes have these 3 apps in full English though and I am glad he does! For anyone that is looking for a SetCPU alternative, look no further. I will be the first to admit that I am not crazy about SetCPU. The app and I don't get along because of stability issues. CPU Master can do everything SetCPU can do but with better stability. I have been using it on both of my Vibrants. I have one Vibrant with the MIUI Rom (1.7.29) with the Bali 1.1.1 kernel and the other Vibrant is running CM7 Trigger Redux #17 with the Bali 1.1.1 kernel. I have had ZERO issues with the phones. Set on boot work flawlessly and overclocking is a breeze. The will give you every scaler that is included with the kernel you are running along with whatever overclock speed is set in the kernel. The Bali kernel supports up to 1.4Ghz and thats what the slider is maxed at. I loaded the Glitch kernel that supports 1.7Ghz overclock to see if the slider adjusts to that speed and as expected, I got 1.7. The only difference between the Free version and the paid version is that you can set and edit profiles in the paid version. For 1.99, its well worth the investment!
The Benchmark app ties directly into CPU Master. It tests everything that Quadrant Advanced (paid version) does PLUS it tests the speed of your SD cards! All of this and it's Free. If you are playing with overclocking speeds on your phone to see where the threshold is on your device, this benchmark will tell you. Through its rigorous testing you will see right away if your phones CPU can handle the speed you are testing. If you lock up during the test, its time to slow it down! On my MIUI Vibrant, I can only go up to 1.3Ghz and beyond that it freaks out. On my CM7 Trigger Vibrant, I can run 1.4Ghz with no problems.
Smart Profiles Free is a great app for people who spend part of their day in places where being quite is important. You can create all kinds of different profiles throughout your day to keep your phone running like the way YOU want it and not worry about turing on and off features. Just make your profiles and you are done! For example, from Monday to Friday I am at work 8 - 4:30 and I want my phone on Vibrate only. During those times I also want my WiFi on to use the company's internet and not my data plan and I also want my GPS off. As you can see you have A LOT of control of the various functions of your phone!
These apps are definitely worth the time to take a look at and try out. For any end user that wants even more control of their phone, they are certainly a fantastic addition!!
Free Apps:
CPU Master (Free): https://market.android.com/details?id=com.antutu.CpuMasterFree
AnTuTu Benchmark: https://market.android.com/details?id=com.antutu.ABenchMark
Smart Profiles (Free): https://market.android.com/details?id=com.antutu.phoneprofilefree
Paid App:
CPU Master for ROOT Users: https://market.android.com/details?id=com.antutu.CpuMaster
Excellent over / underclocking utility!
Yes, sure Antutu CPU Master is really a very good and powerful utility. I bought the pro version and it is worth the money. I am using it in my Samsung Infuse 4G, this allow the device to be underclocked till 100 MHz and overclock up to 1800 MHz, of course with the required Kernel and root access. It can be configured by the readymade profiles that can automatically change the clock settings based on conditions.
The widget which is just two column wide and 1 row height shows CPU Speed, Battery Status and Temperature.It has profiles, default, Charging, Screen off, In Call, Low battery, Temperature over-heat.
For stable clock setting set the minimum to 800 MHz as below this the device goes unresponsive particularly when the screen is off. I am using the range between 800 - 1800 and so far no issues, and it works great!
As mentioned, the benchmark, CPU setting and profile are great features of Antutu collection of software. Thanks to them!
I'm curious about the state of fine tuned overclocking on the note.
Of course, we have Da G's OC Kernel, and a couple roms.
But i've never been so unlucky when it comes to receiving some free performance via overclocking.
I've been blessed with a solid piece of silicon on my transformer and my desktop setups.
I find that even at 1.72ghz, i FC every 20-25 minutes or so. Just enough to make me want to avoid OCing it.
At 1.78 it's worse, and although i've heard that the majority of users have no issues at 1.83 ghz, i crash hard at that settings--within a quarter-minute of applying it.
I've tried different governors, and had more luck with smartassv2. I have a feeling that i just received a mediocre piece of silicon.
I only have a couple options-- i've had other issues with my note--namely the buttons; soft keys, as well as hard, and display brightness--unfortunately im just past my 30 days to return the note, so i'd have to replace it through Black-Tie Protection....i have no idea how this even works.
The other option is to bump up the voltages, but in SetCPU, there are no options, and CPU Master is the same. The only app I've found that even lists voltage options is System Tuner Pro, and while i'm not fond of the UI, i could deal with it.
Edit:
It turns out, bumping up the voltages @ 1.83ghz to 1375mV seems like it buys me a few seconds more before i crash and burn, but this could be a placebo affect.
So, the pupose of this thread is two-fold:
A: Find out if voltage adjustment is a function of the app, and a logic board component.
B: Find out if voltage adjustment must be supported at the kenel and/or ROM level in order to function, and the settings i'm changing are just dummy settings without said support.
2.
A: Find out how much variation on overclocking yield is standard.
B: Poll and share the results.
it is non sense having a poll for that because although we have the same device, still they are not the same if u know what i mean. stop overclocking if it crashes unless you want your phone to die, or just get it replaced with another one and see if it works fine. 1 question, why you need to oc?
This thread is for discussing overclocking methods, settings, support, and to answer my questions about the above listed specificity.
The poll is meant to survey our (us @ the LTE Galaxy Note forums on XDA) sample (albeit, a small one) to find out where our numbers fall. Unless we have a volunteer to read the thread every day, and report back on how many users are stable @ the clock speeds listed above, a poll is the most efficient, concise, objective, and standardized method to gather such information via forum.
Us non-cyborgs (organic humans) just don't do well when it comes to looking at a ton of numbers and extrapolating 411 from 'em over, and over, and over again.
Hello. I have been running CyanogenMod 10.1-10.2 since I got my device back in July, everything has been working great. Bugfixes have been lovely and all that good stuff; however one thing continues to annoy me. I cannot underclock my device properly. Let's say I go into the normal CyanogenMod Performance settings. Then I put my CPU to something like 1024MHz, then I see how the results went over with PerfMon from Chainfire, it will underclock only on Core 0, the rest of the cores still run up to the standard limit, 1890MHz. The only way I can somewhat successfully underclock is by setting my CPU to 594MHz or lower, at which point it will disable all cores except Core 0.
This has been annoying me for a while, I am running the standard CyanogenMod kernel, and recently I tried the Elite Kernel. The only thing the Elite Kernel did was remove the ability to disable the other 3 cores when below 594MHz. (And add the ability to go up to 2.2GHz, but who wants to overclock the Galaxy S4 yet?)
It may be worth mentioning if I try to tweak individual core settings with Tasker, on Core 0 it will let me set a CPU frequency, then if I go in and try to set something on Core 1, it won't have any of the default values for anything, and I enter them manually, then it will give me some errors about not finding the governor I said and stuff like that.
Anyone who knows any way to fix this (Custom kernels, different ROMs (Only for curiosity, I would stick to CyanogenMod anyway), etc) would be greatly appreciated.
Anyone who questions my motives for underclocking, question away. I don't like how my battery life is next to junk when I'm not even touching my phone all day, and the GS4 hardly needs the CPU it has, so I plan to use Tasker to set up a bunch of power saving mechanisms.
I suppose I do have one other question. Will underclocking even benefit me if I can't modify the voltage settings? Are they modified automatically when you're running at lower frequencies? (You would hope so, considering it's kinda a mobile device with a power source that isn't infinite). But if it won't help me without lowering my voltage (and if it isn't modified automatically) is there any good way to do that with a Tasker based setup, so it can be switched instantly whenever I do something? For example, launching a music player. All 4 cores shoot up to 1890MHz (I know they eventually settle down to lower frequencies, but for example's sake), I would rather have it so when I launched the app, Tasker would come in and set my CPU to ~800MHz with only a single core. Everything might slightly lag, but it would work and I would potentially get better battery life while listening to music.
Also, I never tested this on TouchWiz, as I didn't stay on it for more than 30 minutes after I got my device.
I am running the latest CyanogenMod nightly in case it matters (20131002, and it'll be 20131003 tomorrow unless it breaks something)
Thanks in advance to anyone who can possibly help with this. I'm sorry if the post is unorganized, but I hope it's understandable.
[bump]
Forgive me for my ignorance since I'm on ME7 and unable to flash CM10.x yet, but couldn't you just try different governors instead? On my old phone I was using lulzactive and it gave me great battery life, and you could tweak all the values any way you want for more performance or battery life.
I also remember when I experimented with undervolting and much to my dismay it turns out it made my battery life WORSE because of all the error correcting it was doing.
I get at least a days worth of moderate/heavy use on mine and with how fast it charges I don't really care about battery life but I'm curious how much actual gain you'll get for your efforts
It's now in its final version but I'll still update as I see needed
[Donate here]
* IMPORTANT *
Read ENTIRE OP for compatibility and install instructions as I will not respond to a question that is answered in the op
OP has been updated with the new instructions
OK Here's the New CTTMod for marshmallow ROMs Working to improve performance eliminate lag along with lowering the core temps allowing your phone to continue to run smoothly after long or heavy periods of use. Now with faster charging times
Any developers feel free to use the mod in your ROMs just please give proper credit thanks
Please Read The Entire OP before installing
I Am Not Responsible For Anything You Do To Your Device.
How to determine if your G3 set up is compatible with this mod and INSTRUCTIONS and DOWNLOADS are in the 2ND post
Everyone I need your feedback with certain details which I list below in the 2nd post to be able to create an accurate list of which devices are compatible and which devices I'm currently working to make a compatible version for..
Remember always make a full nandroid backup before doing anything
I've decided to go into a little more detail in this thread to give people a better understanding of how and what this mod does, mostly by detailing how the thermal controls work and what I changed within in them. I also went into detail about governors because they go hand in hand controlling the CPU's frequency in different ways. which I'll go into more detail below in hopes of helping you understand when and how the CTTMod will improve your performance
______________________________________________
Governors and thermal control How & why they effect your phones performance
First here are a quick summaries of what a governor does and what the thermals do then I'll get into more detail below
Note I tried to write and explain everything as simple as possible in the hopes of helping even the newcomers to android to be able to understand and gain little knowledge and insight.
Also I hope this helps everyone also understand why and when this mod starts doing it's thing and why sometimes it might feel like it's not working and other times feel like it's working great.
There are a lot of variables and different criteria that has to be met for each process to be enacted.
The kernels governor manages the CPU's frequency mainly by the amount of load the cpu is under and other preset values.
Thermal control which determines the frequency by the temperature of the CPU and is told by preset values set in thermal files when it (cpu),should lower its frequency depending on temperature
Both play big rolls in how well your phone performs but in opposite ways the governor basically start out by trying to keep your phone running smoothly by increasing the clock speed to match the load on the cpu, whereas thermal control does the opposite where it kicks in after the cpu reaches a preset limit and starts lowering the clock speed in an attempt the cool down the CPU to keep the phone running smoothly
Now the governor bases what the clock speed is set to and determines the point the kernel will increase the CPU's frequency by the load value set in the governor which is preset by the OEM or dev. With a rooted phones most of these values can be changed. The load values based on numbers with 0 being the phone just sitting idle not under any load so the governor will have the cpu frequency set to the preset minimum allowed frequency set by the kernel. And as the work load increases the governor raises the frequency in steps also preset by the governor until the CPU reaches a frequency that handles the increase in work load and continues to raise the clockspeed as the load increases. Now once the CPU's load reaches the preset target load value it will be running at the maximum allowed frequency set in the kernel. Different governors have a different numbers of load and other settings some can be changed and some can't depending on the governor and what features were added by the builder
For example the conservative governor sets it's target load values high usually around 95 and a step value of say 14 (step value being the amount of frequencies it will go thru to reach the maximum set frequency. Which helps improve battery life but you sacrafice performance. As say the interactive governor with the target load value set at 70 (Target load value being the highest amount of work load on the CPU before bumping it up to the maximum allowed CPU frequency set in RJ kernel and a step value of 7 will have better performance that the conservative .
All but one governor (performance) which is set to run at the maximum CPU frequency all the time) has parameters that can be tuned to your liking with one of the many CPU/kernel control apps out. But not all kernels and the governors come with the same settings. The builder/OEM/dev. of the kernel can pick and choose what features and governors to put in the kernel and also what settings are allowed to be changed. Also not all particular governors come with the same allowed settings. One developer might only put in the interactive governor and only put a few settings that can be changed whereas a kernel from another developer will add in every setting there is for the interactive governor.
Here's a great page explaining just about everything you should know about governors it's a must read.
http://forum.xda-developers.com/gene...ors-o-t3048957
OK now thermal control works by throttling the CPU down to preset frequencies at preset temperatures and is also done in a preset # of steps. Thermals also monitor and play parts in controlling other components like the GPU, battery and a couple of other things.
First let me be clear about one thing
The CTTMod does not turn off thermal throttling. Now the trick of going into the hidden menu and turning thermal mitigation and thermal control on. That does turn off all thermal monitoring and control and I highly advise against ever doing it. You take a huge risk of frying your phone.
Now let me explain a little what gets changed by installing this mod, and how and when the thermal control do there thing.
What i did is changed the first 3 bump downs (steps). I did this raising the preset frequency in the phones thermal file that tells the CPU to slow it's clockspeed down when the cpu reaches a preset temperture. Now in reality the thermal just sits and monitors the temperature of different components. It doesn't affect the CPU at all until it reaches a preset temperature.
Now there are 6 steps 5 of which throttle your cpu down. The first one being you CPUs max frequency and as long as the cpus actual temperature is below the one predefined in the file the CPU is allowed to scale as high as it needs to in order to complete the task in an efficient and speedy manner. So until it reaches that temperature it's the kernels governor that is deciding what the CPUs frequency needs to be by the load that the CPU is under at any given time. Now each different governor has its own way of how and at what load points it'll tell the cpu it can scale up or down by the values set in parameter settings of the governor and also tells the CPU how many steps ( scaling frequencies) to go thru and how long to stay at each step before moving on. So in short but not the entire story is that the governor controls when to speed up the cpu by the load it's under and the thermal controls tell the cpu when to step down to certain frequencies that corresponds with temperature points that are set in the thermal file in an effort to keep the temperature of the CPU down to try and keep the phone running smoothly and within an efficient operating temperature
Now what I have done is raised the first 3 points at which the thermal tells the cpu to be at. But left the last two and the shut off values at their stock values so it doesn't let the phone get hot enough to burn up. That's why you might notice with this mod after a long period of time using your phone under heavy load and the cpu reaches that forth step down temp. that when you'll notice a dramatic slow down. The thermals also control a what i would consider a fail safe temp setting that will automatically shut your phone down. Which is set at 120°c and won't let you turn your phone back on until the temp lowers to 115°c which I also left at the factory settings.
Now hopefully after reading this you have an understanding of what the mod does and how it affects the performance of your phone. And how the settings in whichever governor you are using also affects the performance of the phone. So if your governor is not tuned to your usage. You will not see a difference after flashing the CTTMod.
Now I'll explain what changes I made to the first bump down to. I changed the first frequency bump down to 2.26 and raised the tempurture it has to reach to 70°c Stock was set to drop the cpu down to 1.5 GHz at 60°c
Now at stock they scale your clockspeed by almost half of the processors actual top speed of 2.45 ghz which is why the g3 has such bad lag when after a short time of moderate to heavy use. So as a result of increasing the first set frequency to 2.26 GHz and raising the temperature limit will allow you turn operate you phone for a much longer period of time before you start to notice the phone slowing down .
Also in the LP versions I was able to tweak some of the battery values to keep the phones temperature down which I had discovered by accident and for most people they say there battery now stays cooler compared to stock. And tweaked the GPU. The second version that is now up implements the cpu throttling and battery improvements and I hope to hand the GPU tweaked and working in the next version.
I Hope this has helped you have a little more insight on what this mod does and how you devices improvement might not be noticeable compared to someone else who show a great improvement in performance. It all depends things we do to our phones to customize them .ie different ROMs kernels, settings and mods we add to them.
Let me know how the mod works for you and what carrier version and ROM and kernel you are on and governor being used
Thanks Rob
Also with the vs985 MM firmware the thermal file in system/etc is thermal-engine-8974.conf
So check to see what thermal file/s you have. If they're different send me a link to your thermal files and I'll take a look and see what I can do modifying them
Instructions and Downloads for G3 Marshmallow
Instructions
#1 - DO A FULL BACK UP BEFORE YOU DO ANYTHING
And since I only have access to the vs985's 46a stock firmware (MM) That is the only variant I can actually test myself . So far haven't found a device that's not compatible
Any g3 variants that have different files the just the one I name below I will need you guys to post me the information and file/s that I have listed at the end of the instructions
First you have to determine if your phone and ROM are compatible.
Check your Roms thread op and see if it's already included in the ROM as many Roms have now included the CTTMod
So before anything, you'll have to see in you have the file named
thermal-engine-8974.conf.
To do so navigate to /system/etc and look to see if you have the file with the same name as I just stated above. If you see that you have only one thermal file and the names match,
Then follow the New Instructions- First still follow the instructions in op to see if your variant or ROM is compatible then proceed
1- reboot into recovery
2- flash mod
3- wipe the cache important no need to wipe dalvic, but you must wipe the cache for the mod to take into affect.
Then in your kernel control app. In thermal make sure it's set to core control.
Now this is optional but under cpu hotplug turn mp decision/intelliplug to off. With hotplug off it will throttle less or on to throttle faster but both ways it'll only throttle to 2.26ghz on the first bump down instead of 1.5 or 1.7. You can read more about mp decision and intelliplug and how they affect the mod HERE
If you decide to leave feedback, good or bad you must include the details about your phone I have listed here
starting with your G3 model # The type of ROM (ie stock, aosp or cm, whether you on a stock or custom kernel, and the governor you are using.. Also please leave any results you have based on one of the two ways below on how to evaluate whether or not the mod works as it's intended too and just how much of an improvement you notice
First and easiest way is your actual user experience. Use your phone like you would on any given day and try to remember things you been doing on you phone that caused your phone to feel slow , laggy , not as responsive, or made your phone get hot to the touch. . Then install the mod and try to repeat what you did before and feel the difference.
If you'd like to take it a step further for some real evidence on if it's working or not. You can do some real testing by
First you'll need an app like CPUtemp to see the CPU frequency, load it's under and the temp of the cpu in real time .
With your phone fully charged use it moderately like going on Facebook and making a call have 2 or 3 apps going at once and doing something on the phone. For around thirty minutes. You want to put the cpu under at least 50%: load logging the temp and frequency every couple minutes for about twenty to thirty minutes. Then do the same again but this time you'll want to put the cpu under a heavy load 100% really work it.(running alot of apps, playing a resource hogging game, running a benchmark or stability test I think you get the idea)
Log the temps and CPU frequency again every couple minutes for 20 to 30 minutes or as long as it takes to reach full load
Then repeat the process after you install the mod.
You should perform the tests once before you install the mod logging the results and then try to duplicate what you did the first time after you install the mod and log the results. It's important to do some testing before you install the mod to give a baseline to compare with. Then you will be able to see what did or didn't gain any improvement compared to stock. And if an something got worse I'll know where to look to fix it.
Thank you as the more people willing to do the testing and share the results will help me greatly on improving, perfecting and to trying to make it compatible with as many variants and ROMs possible.
DOWNLOADS (Alternate download links bottom of this post)
G3-CTTMOD-MM_final:
Yes this is the same mod I had posted in post 52 I've just now made it official after having tested it for a while now.
As stated before I will still be updating as I see fit
CTTMod-MM+FC-v2
Change log: increased the charging voltage by 50mv on the second and third bump downs. Left the first and forth and fifth stock. Goal is to to speed up charging times. I only increased it slightly to start so there might not be much of a noticeable difference. Will increase more once some testing has been done on this one. Please leave feedback thanks
CTTMod-fc-V-2.1 - changes - increased the second and third charge by another 50mv and still left first, forth and fifth stock the same as v-2
CTTMod-MM+gpu-v3-beta
Change log: added slight increase in GPU
CTTMod+fc+gpu-V.3.1- change log- goal better GPU performance along with the faster charging from v2.1
Back to stock zip
( I haven't personally tested this but I don't see any reason why it wouldn't work)
Test versions
I'm going to work on posting all my test versions here as I have many improvements I'm trying to make but can only do and test one at a time to make sure the changes are doing what I want them to do. So please if you decide try a test version please message me with your findings and how you tested
Remember any of the mods posted here are experimental and have not been tested as with anything you flash this at completely your own risk
Here's the first test version for better gaming
CTTMod-fc-gpu-v4
Please lane feedback
Download link doesn't work for me....
D855
RUNNING: N&N 1.9 STOCK MM
+1
cultofluna said:
Download link doesn't work for me....
D855
RUNNING: N&N 1.9 STOCK MM
Click to expand...
Click to collapse
Requires login
cultofluna said:
Download link doesn't work for me....
D855
RUNNING: N&N 1.9 STOCK MM
Click to expand...
Click to collapse
Had to reload should will be up shortly
Can't download because AFH require sign in.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-F400S using Tapatalk
Robshr said:
Had to reload should will be up shortly
Click to expand...
Click to collapse
Thanks for the MOD,but why we have to log in to download?.....
D855
RUNNING: N&N 1.9 STOCK MM
cultofluna said:
Thanks for the MOD,but why we have to log in to download?.....
D855
RUNNING: N&N 1.9 STOCK MM
Click to expand...
Click to collapse
You don't have to register to download
Here's am alternate download link to the new G3 thermal mod for MM- https://mega.nz/#!q1B3wYxS!jfyhwQnXa8c0rYAA2JcDVpiqeEDc4IlbvQ6DfSvZyIs
Robshr said:
I don't know maybe it's something new with android file host just click on the bars in the upper right corner and register is free and they Smit send you a ton of junk it's what all the dev use
Click to expand...
Click to collapse
No thanks.......
D855
RUNNING: N&N 1.9 STOCK MM
cultofluna said:
No thanks.......
D855
RUNNING: N&N 1.9 STOCK MM
Click to expand...
Click to collapse
I just posted an alternate download link in the op
chuyennho184 said:
Can't download because AFH require sign in.
Sent from my LG-F400S using Tapatalk
Click to expand...
Click to collapse
Alternate download link is up
Robshr said:
I just posted an alternate download link in the op
Click to expand...
Click to collapse
Thanks Dev, download it....
D855
RUNNING: N&N 1.9 STOCK MM
Robshr said:
Alternate download link is up
Click to expand...
Click to collapse
check your file/folder permission though, this is what I got even I am logged in
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.
PS: Also, the link should be www.androidfilehost.com/?fid=xxxxxxxxx (17 digits ) , but yours is androidfilehost.com/user/?w=settings-dev-files&flid=49846
Robshr said:
Instructions
First thing since I only have access to the vs985's 46a stock firmware (MM) and won't flash an asop MM ROM until I have this just have I want it and it all backed up to my computer.
So before anything go to /system/etc and find any files with thermal or thermald in it. Hope you only have 1. Named thermal-engine-8974.conf if that's the only file you have you can just flash the zip wipe the both caches reboot and give it about a day to settle in before starting to test or give any opinions
Now if you have different files then the one I name above send all the details about what's running on your phone and upload a copy of whatever files you have and send the link along with you phone info
Link to downloads-
https://www.androidfilehost.com/?fid=24415232478675537
Alienate download link: https://mega.nz/#!q1B3wYxS!jfyhwQnXa8c0rYAA2JcDVpiqeEDc4IlbvQ6DfSvZyIs
Please remember this is a WIP so please be patient thanks
If interested here are my interactive governor settings see attachment
Click to expand...
Click to collapse
abced123 said:
check your file/folder permission though, this is what I got even I am logged in
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.
PS: Also, the link should be www.androidfilehost.com/?fid=xxxxxxxxx (17 digits ) , but yours is androidfilehost.com/user/?w=settings-dev-files&flid=49846
Click to expand...
Click to collapse
I got it fixed I had copied the link to the folder with contained the file and not the link to the file itself. Anyway it's all good now
I'm on fulmics 3.5 with solid kernel (d850). I don't see any thermal file in my system\etc folder. Can I still flash the mod?
sociojeje said:
I'm on fulmics 3.5 with solid kernel (d850). I don't see any thermal file in my system\etc folder. Can I still flash the mod?
Click to expand...
Click to collapse
EDIT SORRY MISREAD you're right in the /system/etc/ there and definitely a thermal file in there
near the bottom
File is. .config or you might been on a romv with a thermal. XML file or similar
Dump question but you're using a root file browser
Second version on the way
I started on the second version last night in hopes of keeping the phone cooler at high loads compared to stock ) like I did with previous versions). So after my initial real feel testing for the first few hours after flashing the the new mod I was happy to feel that the phone felt cooler and didn't lag at all and just felt very smooth even after am hour of moderate to heavy use. I was happy enough to say f-it and go against my own rule of testing and just waited a few hours to let the phone get back to normal temps and than I started an all it assault on the CPU for about thirty minutes straight I kept the CPU under 100% load or as close as possible for the entire 30 minutes. Well the results were better than I hoped for. The highest temp the CPU reached was right around 80° c and was there for only a few seconds and throttled down the CPU just that time and cooled down enough to throttle back up in less than a minute. Now compared to stock. And doing pretty much the same tests for the same amount of time stock went as high as 100°c and throttled down to 1.2ghz within the first ten minutes then down to 1.19 after 15 minutes and stayed between 996 and 1.2 the rest of the time occasionally dropping lower. By a little over halfway testing it stock without the mod the phone was at a crawl and by the end I thought for sure it was going to shut down.
Now with the mod installed it only throttled down once maybe twice but never lagged and ran smooth as silk the whole time. So I think I'm happy enough to try and release it tomorrow as version 2 experimental just in case I find a bug or something in the next few days if i don't then I'll post it in the op. continue testing it and start on the next version which hopefully I can make it as good as possible and achieving what I wanted to do with this mod, but there's always room for improvement. Well below I posted a screenshot of cputemp which was taken at around the 28 minute mark into the test and it shows the load the CPU is under, the frequency it's running at, and its temperature . now it doesn't really refect the average temp or average clockspeed which was closer to 70°c and 2.26 ghz because it bounces up and down quickly. That's why you need to check the reading alot because of how fast and how much all the different readings change every few seconds. So to get a more accurate average of the readings you need to log them as often as possible with whatever app you're using to see the temps and frequency.. Like in the picture I caught it at a much lower frequency than the average which was around the 2.26 mark and spending almost the same amount of time at the top speed of 2.45 ghz . one other bonus I noticed is how low the battery temp stayed. I don't think it ever went above 36°c and remember I had the on charge the entire time.
And these results should improve over the next few days as the mod has a chance to settle in. Hopefully users will get similar results and post them to confirm my results.
I'll perform the tests again in a few days and post them hopefully they improve
Robshr said:
I started on the second version last night in hopes of keeping the phone cooler at high loads compared to stock ) like I did with previous versions). So after my initial real feel testing for the first few hours after flashing the the new mod I was happy to feel that the phone felt cooler and didn't lag at all and just felt very smooth even after am hour of moderate to heavy use. I was happy enough to say f-it and go against my own rule of testing and just waited a few hours to let the phone get back to normal temps and than I started an all it assault on the CPU for about thirty minutes straight I kept the CPU under 100% load or as close as possible for the entire 30 minutes. Well the results were better than I hoped for. The highest temp the CPU reached was right around 80° c and was there for only a few seconds and throttled down the CPU just that time and cooled down enough to throttle back up in less than a minute. Now compared to stock. And doing pretty much the same tests for the same amount of time stock went as high as 100°c and throttled down to 1.2ghz within the first ten minutes then down to 1.19 after 15 minutes and stayed between 996 and 1.2 the rest of the time occasionally dropping lower. By a little over halfway testing it stock without the mod the phone was at a crawl and by the end I thought for sure it was going to shut down.
Now with the mod installed it only throttled down once maybe twice but never lagged and ran smooth as silk the whole time. So I think I'm happy enough to try and release it tomorrow as version 2 experimental just in case I find a bug or something in the next few days if i don't then I'll post it in the op. continue testing it and start on the next version which hopefully I can make it as good as possible and achieving what I wanted to do with this mod, but there's always room for improvement. Well below I posted a screenshot of cputemp which was taken at around the 28 minute mark into the test and it shows the load the CPU is under, the frequency it's running at, and its temperature . now it doesn't really refect the average temp or average clockspeed which was closer to 70°c and 2.26 ghz because it bounces up and down quickly. That's why you need to check the reading alot because of how fast and how much all the different readings change every few seconds. So to get a more accurate average of the readings you need to log them as often as possible with whatever app you're using to see the temps and frequency.. Like in the picture I caught it at a much lower frequency than the average which was around the 2.26 mark and spending almost the same amount of time at the top speed of 2.45 ghz . one other bonus I noticed is how low the battery temp stayed. I don't think it ever went above 36°c and remember I had the on charge the entire time.
And these results should improve over the next few days as the mod has a chance to settle in. Hopefully users will get similar results and post them to confirm my results.
I'll perform the tests again in a few days and post them hopefully they improve
Click to expand...
Click to collapse
Thank you for your amazing contribution for our G3 community.
All the download links are working fine
No more login prompt?
Uploading v2 now link will be posted later on in the op