[4/03/16] CTT mod for marshmallow #1 mod for the g3(new ver. up for faster charging) - G3 Android Development

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

Related

Noob Question: How do I use SetCPU?

So I'm interested in undervolting using the stock CPU freq's, and I'm going to be using setCPU (obvi).
So, first question: Even if I want to use the stock frequencies, do I have to be using the OC kernel (0.2.1/1.45ghz at the time)? And then adjust the max to 1000mhz?
Second, I started up SetCPU and whenever I go to the voltage tab it forcecloses. This happens with both the stock enhanced & OC kernel, and I've tried fixing permissions to no avail.
All I really understand so far is that the end result is a table of CPU frequencies and linked voltages. I've OCed the hell out of desktops, but I'm lost here.
I'd just like to know how to get from starting up setcpu to ultimately popping out that new voltage/freq table.
I do apologize if this seems kinda stupid, I'm just trying to exercise caution lest I demolish my phone's innards. I've done it with many an intel.
If you just want stock frequencies, then there's no need for a custom kernel. I guess in that case, you could just use SetCPU for undervolting & profiles.
However, if you want overclock, you'll need a custom kernel.
If you're going to be using a overclocked kernel (i.e. the new Faux 1.45 GHz), then you will need to set the max to 1.45 GHz, and make sure SetCPU is set to start on boot; other wise it will stay at the stock clock speed of 1 GHz... So i guess if you only wanted the OC at certain times, you could set the max speed manually, only when you want to, and not select to start on boot.
I haven't really had any success with undervolting yet... always crashes on me & reboots. The best thing to do is make sure "set to boot" is not selected, when testing your undervolting, other wise you could get stuck in a loop, with the phone crashing every time it boots and tries to apply you undervolting values. I'd start at -25 for each and work from there... stress testing each choice with a benchmark app to make sure you wont reboot... if it reboots, then you know your undervolt was to much. Also remember that you can not undervolt more than -100 between each frequency, otherwise the undervolting will not make any difference.
I really like the profile options in SetCPU... you can set the screen off frequencies to the lowest two, that way for whatever reason your phone isn't running at full strength while your not using it. Also, you can set frequency speeds at custom defined battery levels.
Hope this helps somewhat.
It's unclear to me why it force closes. This may be a rom incompatibility or a SuperUser issue? I assume you've tried uninstalling it and reinstalling it? Updating your SU app? Try flashing to the latest Aura rom?
A few quick words about SetCPU:
1. When you first get started, do not set to "Set on Boot" in case you've undervolted too much and it crashes when applied. You can always check it later once you know the voltages are stable.
2. Between each frequency step there is a maximum of 100mV step off. Anything greater than that it defaults to native voltage. I think this is a Tegra2 issue.
With that said, undervolting is simple: simply slide the little slider on SetCPU to negative values. How much you can under-volt largely depends on your particular hardware and it is inconsistent across all Atrix's. My voltage table is as belows:
1000mhz: -50
912: -50
750: -50
608: -75
456: -75
312: -100
216: -100
I, however, did not test the limits of my phone. Many people will slowly increment the voltage lower until they start to get resets, and then they'll move it back to find the lowest stable point.
It has, however, been well established that minor undervolting improves battery life and diminishes heat generation. Excessive undervolting may actually hurt battery life. You can look around on this forum regarding the data. However, reasonable undervolting will improve battery life.
Thanks fellas, this helps A LOT.
I was so afraid I'd get 17 responses of "You're such a noob. Stop cluttering the forums" etc etc
At this point, I think that the problem is, for whatever reason, the FC when I tap the voltages tab.
I'm on the newest Aura (1.2.2.1) newest enhanced stock kernel from Faux123 (0.2.1) and the newest SetCPU (2.4). I'll try updating my SU (though I believe I did that right after I flashed.
I'll reintall SetCPU and report back.
Until then, THANKS BUCKETS fellas. I really appreciate the info and advice.
UPDATE: May have found the problem. When it first boots up it prompts to autodetect freq's or choose them manually (or something like that). I was afraid this would actually alter my CPU clocks right then and there and so I hit manual detect, saw something that said Tegra2 etc and clicked it. I just now hit 'menu' and set it to autodetect, tried the voltages tab, and no FC, so I think that's solved.
Thanks again for all the info guys! I'll start experimenting and let you know HOW LOW I CAN GO (ha).
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
AdiNova said:
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
Click to expand...
Click to collapse
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
xyrovice said:
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
Click to expand...
Click to collapse
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Swiftks said:
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
xyrovice said:
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
Click to expand...
Click to collapse
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
ghost_og said:
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
Click to expand...
Click to collapse
That makes perfect sense- limiting the max during the stress test. Thanks for the tip bro I really appreciate it.

[Kernel]Unsecured, OverClocked, SmartAssV2, and Voltage Control[New Links 01.27.12]

Okay, I looked at what ziggy and cron247 did over on XDA and tried to make it better.
This kernel is unsecured, meaning adb connects with root.
It OverClock's up to 1.836MHz.
It has the SmartAss V2 governor.
It uses my ramdisk, not the one you have. I cannot forsee this being an issue. If it becomes one, let me know.
Updates:
Version 1.1.3 changes the version of lagfree, the old one was having issues. Also removes forcing the second CPU to be online which was causing choppiness.
Version 1.1.2 adds increased read ahead, writeback tweaks, decreased dirty ratio settings, simple I/O scheduler, and the lagfree governor.
Version 1.0.5 adds mpdecision fix by Mr X, thank you whoever you are, if you removed mpdecision, put it back. Also added voltage control for you UV lovers.
The only control program I have tested to work is AnTuTu CPU Master (Free), I have had issues with SetCPU and a few others. This one does speed, governor, and voltage all very well.
Get it here: AnTuTu CPU Master (Free)
The following problems seem to be fixed at this point: governor and speed settings not sticking, smartass staying at top speed, random reboots or bootloops overnight.
READ THE INSTRUCTIONS, THIS IS A SINGLE FILE
To install this kernel:
Copy the file to the root of your SDcard.
Reboot into recovery (CWR or AmonRa).
Flash the file from the SDcard.
At the end of the flash the phone will reboot to fastboot.
Once fastboot loads, tap PWR to get to HBOOT.
HBOOT will find the update and ask you to install.
Tap Vol Up to begin the install.
When it finishes it will say tap PWR to reboot. Do it.
After the phone boots remove the PH98IMG.zip file from your SDcard.
Use AnTuTu CPU Master (Free) to set min/max/gov/voltage.
Enjoy!
Thanks to ziggy and con247 for getting us started and having stuff out there for me to get ideas from.
Download:
Link: dsb9938 Kernel 1.1.3
MD5: a2558e70f9af572f43e258c9aedb4b40
Source on GitHub.
My favorite Rezound kernel so far. Haven't had one crash, even at max OC. Thanks so much guys at BAMF!
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
dccoh said:
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
Click to expand...
Click to collapse
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Argent36 said:
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Click to expand...
Click to collapse
It's kernel related; I'm running rezrom and had the same exact issue with my alarm running this kernel.
Do you think ziggys is more stable?.. or do I just need to find the right overclock/underclock settings?
I seem to recall seeing them have that problem on ziggy's - but I never had that problem on earlier versions of dsb's - so maybe it's just something that is fixable for the next release
*wanders off to test it again*
This is no doubt me doing things wrong that led to this, but I downloaded the kernel through the phone browser, then flashed it from the download directory on the internal SD. When I flashed Incredikernel from there it copied the PH98 to the sdcard, but no dice on this kernel until I copied it to the sdcard then flashed it.
I probably should have copied it to the sd card myself first anyway, but I figured I would let you know!
Well this morning - my alarm clock went off - I was able to snooze it - and then a few minutes later the phone went in to boot loops - had been running stable all weekend - once I pulled the battery the phone booted back up just fine.
we'll see if it repeats this behavior tomorrow morning or not...
Call recording support in the kernel?
timp123 said:
Call recording support in the kernel?
Click to expand...
Click to collapse
Nope, only Ziggy's kernel currently supports this.
I only set one alarm at a time usually, but I have one set to go off every morning at 7:30 & it has worked perfectly everyday for a few weeks now.
~John
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
sandman_nyc_316 said:
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
Click to expand...
Click to collapse
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
hgoldner said:
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
Click to expand...
Click to collapse
Thanks! How's your battery life been with those settings?
sandman_nyc_316 said:
Thanks! How's your battery life been with those settings?
Click to expand...
Click to collapse
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
hgoldner said:
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
Click to expand...
Click to collapse
Appreciate it. Gonna see what happens. Will update with my results. Thanks again!
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
zetsumeikuro said:
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
Click to expand...
Click to collapse
Good question. I haven't had a single bootloop since flashing this kernel after coming from Ziggy's. Been running this 192min/183max and UV'd -75 across the board and running great.
Hopefully I don't jinx myself.
Guys with bootloops/lockups...are you running any profiles?
Make sure you do a dalvik cache wipe....
Ziggy's would always lock up on me (multiple times per day) so I gave up on it. The only problem I have with this on (and this was a problem with Ziggy's too) is the min jumping to max.
My frequencies bounce on this kernel. It spends about equal time between the highest setting, and lowest setting. It works great other than that. My question is this bad for my CPU? I get great battery life, and performance, just scared the bouncing could be bad for the processor. Any help would be great.....
Sent from my ADR6425LVW using Tapatalk

[Q] Galaxy S4 CPU Control (Or lack of)

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

[TIPS] This setup will make your beloved Mi3 run like a champ!

Hello folks!
This thread is intended for sharing, please be kind. Any suggestions would be appreciated
A few days ago I was tired of having my Mi3 running on stock global dev MIUI 8, it was inefficient system with really bad memory management. On my experience, the MIUI tend to run out of memory. In some case, after a few hours of usage the system cannot reclaim the occupied RAM, thus making the system lags a lot and generate excessive heat!
Yes, MIUI is a feature-rich ROM, and the Mi ecosystem is a pretty mature ecosystem. However, those all greatness needs a lot of power to run on our 3 year old device. After a few research I decided to switch to CM13 ROM.
With efficiency in mind, I do my research and tinkering with my device to get the best setup possible without losing performance. The results are AMAZING! I can use my phone for a whole day without recharge in the mid day. All of this with huge improvement on performance, Real Racing 3 highest graphic setting without any noticeable lag! CPU and battery temperature are now significantly lower (43-47C idle / light tasks, 55-57C heavy gaming). Now that I've found the best setup, I want to share it with you folks! Here we go:
Mi3W 64GB
CM13 ROM snapshot build
CM kernel (automatically flashed while flashing CM13 zip through TWRP)
Screen resolution changed to 720x1280 use this guide
Modded interactive CPU governor (see screenshot below)
Undervolt (see screenshot below, this one really helps reduce CPU working temperature)
Noop I/O scheduler
Reduce aggresiveness of LMK (see screenshot below)
Thats all folks, hope this guide will get our Mi3 having another year of flagship-grade experience! Cheers! :highfive:
How did u undervolt
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
Yes, it depends on the kernel used. Some kernel support undervolting while others don't. You need to flash kernel that support undervolt.
solazz said:
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
Click to expand...
Click to collapse
While testing CPU voltage value, don't tick "apply on boot" option until you find the most stable voltage without causing system reboot or crashes. Every CPU has different limit on how far you can undervolt, but you can use the values on my screenshot as guidance (Snapdragon 801 / MSM8974-AB only)
Wow!! Thanks a lot bro. I'll fiddle now with my phone.
miui8polska,i cant root it .can you give me a supersu.zip?
Sent from my MI 4LTE using XDA Labs
Random reboot after setting undervolt just likes yours
z1d4n21 said:
Random reboot after setting undervolt just likes yours
Click to expand...
Click to collapse
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
rxl.noir said:
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
Click to expand...
Click to collapse
Ok thanks i will test it later

How To Guide Underclock or overclock your 888's GPU NOW with ROOT and KonaBess app!

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?

Categories

Resources