I was looking through /system with root explorer to see what I notice that it new from the EVO 4G and I stubbled across a file called adreno_config.txt. I opened it and read through parts of it and it has a lot of values that can be changed. I changed binning from software to hardware and noticed a very slight jump in benchmark scores using antutu benchmark. Mainly I noticed smoother scrolling on homescreens and webpages with a lot of flash content. I was hoping maybe a dev or someone who knows alittle more about these things than I do could look thru this file and see if we could get a performance boost from anything in this file. The exact path to the file is /system/etc/adreno_config.txt. thanks and hopefully something good could come of this. One of the big things I noticed was antialiasing settings that were all turned off by default. If this has already been looked at then I am sorry for the double post and don't mind being told I'm wrong.
I will upload the file if needed, but I figure that anyone who would know anything about this should already have root and s-off so it is really pointless.
Clay333 said:
I was looking through /system with root explorer to see what I notice that it new from the EVO 4G and I stubbled across a file called adreno_config.txt. I opened it and read through parts of it and it has a lot of values that can be changed. I changed binning from software to hardware and noticed a very slight jump in benchmark scores using antutu benchmark. Mainly I noticed smoother scrolling on homescreens and webpages with a lot of flash content. I was hoping maybe a dev or someone who knows alittle more about these things than I do could look thru this file and see if we could get a performance boost from anything in this file. The exact path to the file is /system/etc/adreno_config.txt. thanks and hopefully something good could come of this. One of the big things I noticed was antialiasing settings that were all turned off by default. If this has already been looked at then I am sorry for the double post and don't mind being told I'm wrong.
I will upload the file if needed, but I figure that anyone who would know anything about this should already have root and s-off so it is really pointless.
Click to expand...
Click to collapse
seems like an AWESOME find. subscribed
Don't apologize, sounds like you found something thar we can tinker with. Good post.
did a little bit of searching about this config file..it seems it got monkeyed around with while they were trying to achieve s-off, but I cant find anything showing any performance differnces from changing the values, so hopefully were on to something good
Success100 said:
did a little bit of searching about this config file..it seems it got monkeyed around with while they were trying to achieve s-off, but I cant find anything showing any performance differnces from changing the values, so hopefully were on to something good
Click to expand...
Click to collapse
Could you post it? I'll take a look to see if the file can improve performance.
DDiaz007 said:
Could you post it? I'll take a look to see if the file can improve performance.
Click to expand...
Click to collapse
just use root explorer to go in and grab it from your phone. i would definetely make a backup of it on your sd card and nandroid before messing around with it. I dont have s-off just yet (computer is down) or Id mess with it myself
here it is
Thanks I'll take a look to see what he's talking about exactly.
From what it looks, it looks like it is the Adreno 220 graphics configuration settings. It seems it can be tweaked, but I do not know entirely since this is a phone.
Take a look at these lines...
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Specify the allocation strategy for multisampling antialiasing buffers.
; Valid values:
; on_demand - allocate MSAA buffer on demand. This is the default value.
; always - always allocate MSAA buffer.
; never - never allocate an MSAA buffer.
;
;MSAABufferAllocation=on_demand
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Force the MSAA antialiasing mode to the value in MSAAMode.
; Valid values:
; 0 - (default) do not force the MSAA antialiasing mode.
; 1 - force the MSAA antialiasing mode to the values in MSAAMode and MSAASmoothing.
;
;forceMSAAMode=0
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Specifiy the antialiasing mode to use if forceMSAAMode is enabled.
; Valid values:
; 0 - (default) do not antialias.
; 1 - use 2x antialiasing.
; 2 - use 4x antialiasing.
;
;MSAAMode=0
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Now I don't know if this will fully improve performance, but I do know that when I am tweaking files like this for a PC video card, it'll make all the difference in the world for running games. But these files are within the games directory so this seems to be some sort of universal settings. I don't know entirely since this is a phone. Someone with knowledge in regards to this please chime in.
Yup this has to do with the configuration settings, it is universal. I can see an FPS cap option. Our evos aren't capped by FPS, if anyone would want to know that.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Cap value for frames per second. Do not cap if value < 0 or value > 1000.
; Valid values:
; 0 - (default) do not cap.
; Int - (integer) cap to this number of frames per second if N 1000.
;
;FPSCap=0
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
I'll probably tweak this file to see if it really does anything, but I don't have the time to fiddle with it right now. Anyone who has knowledge in regards to phones, I don't mind if you chime in and educate.
good ****..
i just sent viper a pm and well see what he says about it.
He's one of the more popular devs in the dev section
I pm'ed two Devs... I know files like this are used always in computers for adjusting configurations precisely rather than using presets. I'm just not entirely sure for a phone lol
to get full benefit of these tweaks, you must use chainfire 3D PRO, and enable EGL beta driver when you install CF3D driver. Also, since you have pro, go ahead and hide CF3Ds announce ID. good luck, have fun.
I assume this is what joelZ9614 might have used to "force GPU UI rendering" mentioned in his Shooter Rewind ROM changelog
phatmanxxl said:
I assume this is what joelZ9614 might have used to "force GPU UI rendering" mentioned in his Shooter Rewind ROM changelog
Click to expand...
Click to collapse
I don't believe so, there is another way to do it.
Tilde88 said:
to get full benefit of these tweaks, you must use chainfire 3D PRO, and enable EGL beta driver when you install CF3D driver. Also, since you have pro, go ahead and hide CF3Ds announce ID. good luck, have fun.
Click to expand...
Click to collapse
gotcha. well viper says he's gonna f around with it tonight and report back. so tilde your saying this is only going to benefit gamplay and not system operations?
edit: and here comes viper lol. right on time
phatmanxxl said:
I assume this is what joelZ9614 might have used to "force GPU UI rendering" mentioned in his Shooter Rewind ROM changelog
Click to expand...
Click to collapse
I always wonder what that meant. If anyone uses his ROM, is there a noticeable difference using it?
Success100 said:
gotcha. well viper says he's gonna f around with it tonight and report back. so tilde your saying this is only going to benefit gamplay and not system operations?
Click to expand...
Click to collapse
Most likely gameplay only.
DDiaz007 said:
I always wonder what that meant. If anyone uses his ROM, is there a noticeable difference using it?
Click to expand...
Click to collapse
I've enabled it in my ROM (in my test build) and it seems a little smoother, not amazingly different, but every little bit helps
Joel just told me he's seen the file but hasn't bothered looking into it at first.. he said he's going to though.
Related
INFO:
Let me save you the time of reading all this. In it's current form, this is impossible. An inside connect at Qualcomm has told us we can't change the GPU clock from userland or kernel. That mean's we're screwed basically. Here is the post by Jack_R1:
Checked, as promised. Bad news. If I sum it up in one sentence - GPU overclock w/o touching the rest of the system is plain impossible, and GPU overclock while trying to play with the whole system is most probably still impossible (pending further deeper check), and it's definitely impossible for anyone that doesn't have the clock diagram, which is NDA, thus won't be available. The reason isn't software, and don't ask, what it is - I won't give direct explanations.
I've written a long post with some explanations of clock networks, to educate those that want to learn and prevent some of big mistakes that I've seen along this thread, and it's pending approval, since I don't want to accidentally spill more than I can share. I hope it gets approved and I'll post it. It should give some more insight.
The only good news is - global overclocking that affects 1GHz CPU clock will affect GPU too.
Click to expand...
Click to collapse
I'm sure we all heard about being able to overclock the GPU on some of the old MSM devices, but the Snapdragon handles the graphics chip in a different way. The goal of this thread is to try and overclock the GPU on Snapdragon devices as well.
There is nothing GPU related in acpuclock-scorpion.c at least for setting clock speed as far as I can tell.
In board-mahimahi.c there is some kgsl init code, but so far as I can tell it isn't setting the clock there, instead it seems to be pointing to PWR_RAIL_GRP_CLK to set the clock. It defines the variable in board-mahimahi.c but I'm not sure where that variable is set, since it doesn't seem to be in any of the other board files as far as I can tell. I could be completely off here too though.
In drivers/video/msm/gpu/kgsl/kgsl.c there is a method called kgsl_clk_enable that seems to be called whenever the GPU is enabled. It looks like this:
Code:
/* the hw and clk enable/disable funcs must be either called from softirq or
* with mutex held */
static void kgsl_clk_enable(void)
{
//clk_set_rate(kgsl_driver.ebi1_clk, 128000000);
clk_set_rate(kgsl_driver.ebi1_clk, 245000000);
clk_enable(kgsl_driver.imem_clk);
clk_enable(kgsl_driver.grp_clk);
}
The line that's been commented out is the original value, I replaced it with my value on the line below it in a failed attempt to overclock it. Probably a stupid effort on my part, I doubt it's that simple, but it was worth a shot.
According to the clk.h files in the standard linux kernel, clk_set_rate is obviously a method to set the clock rate. The first variable is a struct that tells it which clock to set, and the second variable is a long value that is the rate you want it set at. Is it setting the right clock there for Snapdragon chips? Or is it only the clock for older chips? Actually I've looked again, the kgsl files are ONLY for the newer Qualcomm chips, the QSD8x50 Snapdragons & the midrange MSM7x27 series that replaced the old MSM7x00a chips like in the Dream & Magic. At least thats the way it seems to me judging from what Qualcomm & AMD have written in the source.
I'm in way over my head with this source, I'm but a lowly Java dev , but I really wanna solve this. Can anyone with a little more experience than me throw in a little more info? Sorry if it doesn't make much sense, if it isn't clear just ask me & I'll try to explain a little more.
Regards,
Jesse C
EDIT: Okay I did a little more digging and those kgsl settings should work for QSD8x50 chips. In the config file, under Drivers, Graphics Support, it allows you to enable 3D accelleration for QSD8x50 & MSM7x27 chips. The tag for that is CONFIG_MSM_KGSL_MMU. If you check in kgsl.c it checks to see if that is enabled in the config, and if it is then it compiles and uses kgsl.c & all of the kgsl code. That tells me that the clock is either not being set, or the wrong clock is being set. I'm adding some debug code right now so I can see in dmesg what code is actually being run.
EDIT 2: Another status update. Adding the debug code showed that it is setting the clock at my level whenever the kgsl initializes. Also, as IntersectRaven pointed out, clocks.h in arch/arm/mach-msm nicely lays out what each clock is:
Code:
grp_clock = Graphics clock
ebi1_clock = External Bus Interface 1 clock
imem_clock = Internal Graphics Memory clock
If you want to add your own debug code to it, calling the method "pr_info" and passing it a string with the message you want will output it to the kernel logs you can view with dmesg. An example would be "pr_info("kgsl: clock set at 245mhz\n");"
EDIT 3: I now know the values for all the GPU related clocks.
Code:
<6>[ 70.681793] kgsl: grp_clock= 256000000
<6>[ 70.682464] kgsl: imem_clock= 256000000
<6>[ 70.683441] kgsl: ebi1_clock= 128000000
If you want to get these values yourself, the following code in the kgsl_clk_enable method will output them to the kernel log:
Code:
int clkg = clk_get_rate(kgsl_driver.grp_clk);
int clki = clk_get_rate(kgsl_driver.imem_clk);
int clke = clk_get_rate(kgsl_driver.ebi1_clk);
// this will get the clock rate & print it in the kernel log
pr_info("kgsl: grp_clock = %d", clkg);
pr_info("kgsl: imem_clock = %d", clki);
pr_info("kgsl: ebi1_clock = %d", clke);
Just add that into the function I mentioned and it will output it to the kernel log, quite often in fact, so I wouldn't leave it in there except to see the values
EDIT 4: 7-2-2010
Qualcomm has now released a new driver. It looks a lot better for our purposes. I'm looking through it today but I have other stuff I need to do. I will look at it, but I can't promise I can devote much time to it until at least Sunday.
EDIT 7-7-2010:
I've collaborate with storm99999 over GTalk and things aren't looking good. Here's what it comes down to:
If we try and lock it with any of the clk_set_rate methods, there is no effect. Not matter how we change it, it just stays at the original value. This either means it's set in the radio (impossible for us to change) or that it's set one time on boot and never changes, but we just don't know where it's actually set (more likely, but I'm not sure either way)
If we try and change it with msm_proc_comm, which is a direct interface to the hardware, it causes the kernel not to boot at all. This is really really strange. We can monitor the clock with pr_info as before, and if we read the data1 argument, it prints to the kernel fine, but if we try and read the data2 arg passed to msm_proc_comm, it also freezes on boot.
We seem to be out of ideas here. We're open to any reasonable suggestions, so if you have any, PLEASE let us know in this thread or PM one of us. Or you can email me at [email protected]
This is a great idea for sure. I will certainly lend a hand where I can.
That being said don't know if it is possible to OC the GPU. I remember discussing this with kmobs in the past and he didn't think so. Perhaps tweaking Open GL might prove more fruitful. All of this is definitely worth thinking about.
jlevy73 said:
This is a great idea for sure. I will certainly lend a hand where I can.
That being said don't know if it is possible to OC the GPU. I remember discussing this with kmobs in the past and he didn't think so. Perhaps tweaking Open GL might prove more fruitful. All of this is definitely worth thinking about.
Click to expand...
Click to collapse
Hmm well that may be kind of a downer...
I know it sets the values somewhere, but I can't seem to find anywhere it could be setting them other than the kgsl stuff, and that doesn't have any effect on performance at all. Unless it could be set in hardware?
I don't really care about harming my Nexus at this point, now that I've upgraded to an Evo, so I'm willing to try dangerous kernels on my Nexus (read: any kernel changes I make ).
If someone could give me any more ideas about where to look, I'd be greatful. I've gone through everything I can think of and it doesn't seem to be getting me anywhere closer.
P.S. I love your avatar jlevy! Simpsons FTW!
This is definitely for the kernel masters like Cyanogen, pershoot and kmobs to weigh in on. In the meantime I am going to rip through the code to see what I can find (if anything). To bad you are moving on to the EVO. We'll miss all of the great ideas/solutions you provide (well N1 user will)
jlevy73 said:
This is definitely for the kernel masters like Cyanogen, pershoot and kmobs to weigh in on. In the meantime I am going to rip through the code to see what I can find (if anything). To bad you are moving on to the EVO. We'll miss all of the great ideas/solutions you provide (well N1 user will)
Click to expand...
Click to collapse
Thanks! I'll still be hanging around the N1 forums, since so much of the code is interchangeable with them both having the QSD chips and all. If you're looking through source, can you get with me on GTalk or Wave & we can work together on it. Also I've updated the first post with a little more info.
Geniusdog254 said:
Thanks! I'll still be hanging around the N1 forums, since so much of the code is interchangeable with them both having the QSD chips and all. If you're looking through source, can you get with me on GTalk or Wave & we can work together on it. Also I've updated the first post with a little more info.
Click to expand...
Click to collapse
Sounds good, I will PM you my gtalk address.
So I added the debug code. It shows that it is calling my code every time the GPU is initialized. This means it is setting the EBI1 clock to 245mhz instead of the original 128mhz. However I guess that is the wrong clock. it also defines 2 other clocks along with the EBI1 clock, however EBI1 is the only one that it sets a value for, the other 2 it just turns on (hardware values?).
After looking at the code, the clocks seem to be initialized at kgsl_platform_probe by clk_get. (correct me if I'm wrong since I'm a newbie at tracing through the GPU... )
*Nope...wrong analysis...that was the clock SOURCE instead of clock RATE...
**After looking through a bigger part of everything, I think you can't specifically overclock it. The way I see it, the clock source used by kgsl is unified with different clocks being set elsewhere. This is why you're not getting it to work. When it calls the kgsl part you modified, it sets to the modified clock BUT the moment it exits, some other part which uses the same clock source will reset it to 128Mhz. If you want to modify that, you'll pretty much have to modify everything which uses the same clock source. (again, correct me if I'm wrong but I think that pretty much describes what I'm seeing with the code...)
Geniusdog254 said:
So I added the debug code. It shows that it is calling my code every time the GPU is initialized. This means it is setting the EBI1 clock to 245mhz instead of the original 128mhz. However I guess that is the wrong clock. it also defines 2 other clocks along with the EBI1 clock, however EBI1 is the only one that it sets a value for, the other 2 it just turns on (hardware values?).
Click to expand...
Click to collapse
Yeah, I think the other two value are hardware related. To find the right clock...
intersectRaven said:
After looking at the code, the clocks seem to be initialized at kgsl_platform_probe by clk_get. (correct me if I'm wrong since I'm a newbie at tracing through the GPU... )
*Nope...wrong analysis...that was the clock SOURCE instead of clock RATE...
**After looking through a bigger part of everything, I think you can't specifically overclock it. The way I see it, the clock source used by kgsl is unified with different clocks being set elsewhere. This is why you're not getting it to work. When it calls the kgsl part you modified, it sets to the modified clock BUT the moment it exits, some other part which uses the same clock source will reset it to 128Mhz. If you want to modify that, you'll pretty much have to modify everything which uses the same clock source. (again, correct me if I'm wrong but I think that pretty much describes what I'm seeing with the code...)
Click to expand...
Click to collapse
I think you are reading it correctly and that one would have to manipulate all the other values to ensure it won't reset to 128mhz. However, even if you do modify all that, there could be a master over-ride that controls the clock set at a pre-set value.
One interesting thing I did come across is one can write their own Open GL code. http://android-developers.blogspot.com/search/label/OpenGL ES
So if one could manipulate the values for Open GL, it would almost be equivalent to OC the GPU. Just a thought.
jlevy73 said:
Yeah, I think the other two value are hardware related. To find the right clock...
Click to expand...
Click to collapse
I know for sure 2 of the 3 are set in the kernel. The EBI1 clock of course is the one I'm trying to modify now, it has no effect. Then there is the "imem" clock which I haven't seen any code to set it, and then there is the "grp" clock.
If you see my first post, in board-mahimahi.c it defines PWR_RAIL_GRP_CLK which is the GRP clock. It is set at 8 as I just discovered. Here is that code:
Code:
#define PWR_RAIL_GRP_CLK 8
static int mahimahi_kgsl_power_rail_mode(int follow_clk)
{
int mode = follow_clk ? 0 : 1;
int rail_id = PWR_RAIL_GRP_CLK;
return msm_proc_comm(PCOM_CLKCTL_RPC_RAIL_CONTROL, &rail_id, &mode);
}
The only thing that leaves is the imem clock which may be a memory clock? I haven't found it set anywhere, but it could be in the kgsl_sharedmem.c & .h files. I haven't checked there yet. That covers 2 of the 3 clocks. I don't know what the 8 value on the grp clock means, or even what the grp clock is. But so far, those 2 are for sure set in the kernel...
I forget his username, but maybe the guy who got use all the mem hacks would be of great service? I think it's c00l something
Who got us* damnit I hate these typos. I'm going to bed. Too tired, and tapatalk has no flipping edit button lol
dictionary said:
I forget his username, but maybe the guy who got use all the mem hacks would be of great service? I think it's c00l something
Click to expand...
Click to collapse
Coolbho3000. He posted in the original thread or the MSM7500 chip about how it was handled differently on Snapdragon chips and that we may be able to change it, but that's all he said.
Yup him. I see. I'll have my bro look over this and see if he can find anything relevant, or help in any way
I'm not so advanced with my dev
Geniusdog254 said:
I know for sure 2 of the 3 are set in the kernel. The EBI1 clock of course is the one I'm trying to modify now, it has no effect. Then there is the "imem" clock which I haven't seen any code to set it, and then there is the "grp" clock.
If you see my first post, in board-mahimahi.c it defines PWR_RAIL_GRP_CLK which is the GRP clock. It is set at 8 as I just discovered. Here is that code:
Code:
#define PWR_RAIL_GRP_CLK 8
static int mahimahi_kgsl_power_rail_mode(int follow_clk)
{
int mode = follow_clk ? 0 : 1;
int rail_id = PWR_RAIL_GRP_CLK;
return msm_proc_comm(PCOM_CLKCTL_RPC_RAIL_CONTROL, &rail_id, &mode);
}
The only thing that leaves is the imem clock which may be a memory clock? I haven't found it set anywhere, but it could be in the kgsl_sharedmem.c & .h files. I haven't checked there yet. That covers 2 of the 3 clocks. I don't know what the 8 value on the grp clock means, or even what the grp clock is. But so far, those 2 are for sure set in the kernel...
Click to expand...
Click to collapse
According to clock.h, imem_clk is the clock source for the internal graphics memory so that seems right.
intersectRaven said:
According to clock.h, imem_clk is the clock source for the internal graphics memory so that seems right.
Click to expand...
Click to collapse
Hey look at that! It just nicely lays out what all those clocks are!
grp_clock = Graphics clock
ebi1_clock = External Bus Interface 1 clock
imem_clock = Internal Graphics Memory clock
Not sure what the ebi1_clock is linked to, but kgsl sure sees it as important enough to set it every time it runs. It's the only one set in a recognizable format (hz).
I'm not sure where the imem_clock is set or if it even is. Intersect, did you happen to see it set anywhere? It may be important to change though, it would allow more memory throughput and we could increase the graphic memory size in the board file and that may boost performance.
The grp_clock seems to be actually the real GPU clock according to clock.h. It's set 8 in board-mahimahi.c but I'm not sure what the 8 means. But then it may be that PWR_RAIL_GRP_CLK is setting a voltage or other power level to the graphics bus? Maybe the clock is set somewhere else. That'll take some more digging.
Geniusdog254 said:
Hey look at that! It just nicely lays out what all those clocks are!
grp_clock = Graphics clock
ebi1_clock = External Bus Interface 1 clock
imem_clock = Internal Graphics Memory clock
Not sure what the ebi1_clock is linked to, but kgsl sure sees it as important enough to set it every time it runs. It's the only one set in a recognizable format (hz).
I'm not sure where the imem_clock is set or if it even is. Intersect, did you happen to see it set anywhere? It may be important to change though, it would allow more memory throughput and we could increase the graphic memory size in the board file and that may boost performance.
The grp_clock sleeps to be actually the real GPU clock according to clock.h. It's set 8 in board-mahimahi.c but I'm not sure what the 8 means. But then it may be that PWR_RAIL_GRP_CLK is setting a voltage or other power level to the graphics bus? Maybe the clock is set somewhere else. That'll take some more digging.
Click to expand...
Click to collapse
The EBI clock is the external bus interface clock so I don't think we should mess with it. Anyways, it's set I think to ensure that it's working when the GPU is rendering something. If you'll look at the things that set it, it's usually set to 0 when entering suspend or sleep. Anyways, the variables in clock.h are used as sort of pointers to where the system will actually try to set the clock. (from what I can read at least) As for the imem_clk, I didn't find it set anywhere so it may be that it's on the radio or hardcoded. As for the graphics memory size, I think coolbho3k already knows more about resizing it since he's studied the N1's memory layout in further detail. (he did create that mod which increased the size of the available memory AND also figured out how to get charansingh's camera more memory) Anyways, I'll take a look further.
Interesting, but can we activate hardware acceleration in the device? i think if you can think of a way to do that you will be able to overclock the GPU just like on a PC and easily access the clocking just like the CPU.
I'm no expert on overclocking Phones only PC's.
intersectRaven said:
The EBI clock is the external bus interface clock so I don't think we should mess with it. Anyways, it's set I think to ensure that it's working when the GPU is rendering something. If you'll look at the things that set it, it's usually set to 0 when entering suspend or sleep. Anyways, the variables in clock.h are used as sort of pointers to where the system will actually try to set the clock. (from what I can read at least) As for the imem_clk, I didn't find it set anywhere so it may be that it's on the radio or hardcoded. As for the graphics memory size, I think coolbho3k already knows more about resizing it since he's studied the N1's memory layout in further detail. (he did create that mod which increased the size of the available memory AND also figured out how to get charansingh's camera more memory) Anyways, I'll take a look further.
Click to expand...
Click to collapse
I just woke back up. I guess I will remove the EBI1 overclock since I'm not sure what it does. I'm also not sure what increasing the GPU memory will do, but it's worth a shot.
I had noticed EBI1 is being set to 0 whenever it's diabled, and then setting it back at the time it's enabled. I'm gunna go back through and try to find another setting for the grp clock & a setting for the imem clock.
Hi everyone! We're back at it again with another DIY guide and this time it's everyone's favorite: Dual Cores.
This guide will assume you don't use any other software that will affect this, such as but not limited to: SetCPU, Virtuous OC.
I'm not sure how Virtuous OC works, as I've never used it, but I included in there just in case. SetCPU has been tested by me to render this useless, as it resets the permissions on the second core.
There are a number of ways to go about doing this:
ramdisk
init.d
init.post_boot.sh
But, the easiest fastest way to get this accomplished is to either upload and post your init.post_boot.sh file, which is located in /system/etc/, OR edit it manually yourself.
There are other ways but this file already exists, and has most of what you need in it and it gets executed at boot anyway.
Take note of the permissions set for this file, because they will need to be set back if you choose to edit outside of Android. You can also edit the file with Android's file editor if you use Root Explorer.
If you choose to edit it yourself and outside of Android, you will need to open the file with Notepad++ (Or whatever qualified editor you use) and add this in anywhere before the line "chown system /sys/devices/system/cpu/cpu0/online"
echo "1" > /sys/devices/system/cpu/cpu1/online
chmod 0444 /sys/devices/system/cpu/cpu1/online
echo "ondemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
chmod 0644 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
What this does is set the second core's online state to 1 (enabled) and the second line sets this value as read-only, so that the system can't disable its online state when it feels the second core is no longer needed. The third line sets the governor, and I assume you can use any governor that's available in the kernel. However, I'm not sure if both cores can have separate governors. Changing one may change the other. I haven't tested this myself, but sampling frequency and up-threshold works like this, so I assume governors may as well. The last line, if it has anything in common with the third, sets the governor so that you may infact change it with CPU Tuner (since it has the ability to control the second core as well as the first). This line may be obsolete and was only added in as a fail safe.
While you're in there, you can tune your cores even more (assuming you don't use anything like virtuous OC, CPU Tuner, ETC) and set the min and max values by adding this (there should already be something like this for the first core so you can go ahead and add this below that):
echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 192000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 594000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
As a way to conserve battery life, I set the second core to run at half its max (stock kernel), This works fantastically for CPU Master, which only controls the first core, as you can have all your profiles set, without messing with the second core. (I've found that you can run the first core at 192MHz with the screen off/low battery while still maintaining minimal lag by setting the second core's max to 594MHz!)
Once you've edited the file, you can go ahead and push it back to your device (assuming you've edited it outside of android) and set the permissions back to what they were and reboot.
As always, if any of this is overwhelming, I'll be happy to edit the file for you.
The other methods mentioned above work in pretty much the same fashion (adding those lines in), and if you prefer to use one of those methods, then that's fine as well.
To check whether or not your edits were successful, you can navigate with root explorer to /sys/devices/system/cpu1 and look for "online" which should have permissions of r--r--r-- You can view the file and see if "1" is in there, indicating that the second core is active. You can also use SystemPanel to check your CPU activity, which should show both cores active. As a legend, a grey pie chart means the second core isn't active, but they should both be green and actively being used.
Good luck!
Nice. What sort of difference in user experience have you noticed?
system panel shows second core 100% idle after editing file, also the /sys/devices/system/cpu/cpu1/online file show 0 in view as text instead of 1 any suggestions?
cabbieBot said:
Nice. What sort of difference in user experience have you noticed?
Click to expand...
Click to collapse
much smoother with no lag at all on my end.
rontonomo said:
system panel shows second core 100% idle after editing file, also the /sys/devices/system/cpu/cpu1/online file show 0 in view as text instead of 1 any suggestions?
Click to expand...
Click to collapse
did you reboot after editing? Did you verify that the online file's permissions are r--r--r--? And finally, are you using any cpu controlling software? Setcpu?
what do you recommend besides setcpu to overclock?
cabbieBot said:
what do you recommend besides setcpu to overclock?
Click to expand...
Click to collapse
cpu master or cpu tuner
got it to work by taking out the quotes around the 1
I'm using your latest modified stock kernel. Can you post an additive to add this?
Via My HTC Evo 3D On The Now Network From Sprint.
Rydah805 said:
I'm using your latest modified stock kernel. Can you post an additive to add this?
Via My HTC Evo 3D On The Now Network From Sprint.
Click to expand...
Click to collapse
if you're on the dual core version then this is identical to what's already there. No need to apply.
freeza said:
if you're on the dual core version then this is identical to what's already there. No need to apply.
Click to expand...
Click to collapse
Ahh, just saw it again, dual cores are alive.!!! LOL
Via My HTC Evo 3D On The Now Network From Sprint.
So in theory wouldn't this make ur phone faster? Because after doing some quad testing it seems that my phone is slower. It feels faster but at times the scrolling lags a bit. Anyway to fix the lag? That's if anyone else is having the issue. And I know quads don't mean sh*t but I was curious as to why they would drop.
Sent from my Beastly EVO.. And did I mention it has 3D?
What were the original permission for init.post_boot.sh. I think they were:
RW - R - R
Can someone please confirm?
ericwgarza1 said:
What were the original permission for init.post_boot.sh. I think they were:
RW - R - R
Can someone please confirm?
Click to expand...
Click to collapse
confirmed
youngpro83 said:
So in theory wouldn't this make ur phone faster? Because after doing some quad testing it seems that my phone is slower. It feels faster but at times the scrolling lags a bit. Anyway to fix the lag? That's if anyone else is having the issue. And I know quads don't mean sh*t but I was curious as to why they would drop.
Sent from my Beastly EVO.. And did I mention it has 3D?
Click to expand...
Click to collapse
the reason why there is lag is because your system switches the governor back to userspace after a while... don't know what triggers this, just know that it happens. i have performed this same modification on my phone numerous times and with no success. the phone is smoother managing itself.
i was actually going to ask freeza if he knows of a way to permanently set both cores to ondemand, and permanently have cpu1 online...
that would make it fast. it will stick momentarily, but as soon as that governor is switched back to userspace, you will see lag and a huge performance drop.
---------- Post added at 11:48 AM ---------- Previous post was at 11:36 AM ----------
or maybe i misunderstood the post... and maybe freeze can help me understand here...
so you are saying the lag comes from both cores running at high frequencies? and that if you throttle down the second core, but always have it running, it will improve performance without the lag?
hottubtimemachine said:
the reason why there is lag is because your system switches the governor back to userspace after a while... don't know what triggers this, just know that it happens. i have performed this same modification on my phone numerous times and with no success. the phone is smoother managing itself.
i was actually going to ask freeza if he knows of a way to permanently set both cores to ondemand, and permanently have cpu1 online...
that would make it fast. it will stick momentarily, but as soon as that governor is switched back to userspace, you will see lag and a huge performance drop.
---------- Post added at 11:48 AM ---------- Previous post was at 11:36 AM ----------
or maybe i misunderstood the post... and maybe freeze can help me understand here...
so you are saying the lag comes from both cores running at high frequencies? and that if you throttle down the second core, but always have it running, it will improve performance without the lag?
Click to expand...
Click to collapse
I've set my scaling_governor to read-only and so far "ondemand" has stuck since boot yesterday.
hmmm... i wonder what is causing it to switch back and forth me...
I keep triing this but its not working or maybe I'm doing it wrong, so if I post my file could someone edit it for me? THANKS
Sent from my PG86100 using Tapatalk
MPD CPU1 Governor Control
Treve's MPD CPU1 Governor Control
http://forum.xda-developers.com/showpost.php?p=17456447&postcount=7630
working well with this
Freeza, Good stuff man, thanks for posting this! We appreciate you sharing your knowledge!
kr1m3boss said:
I keep triing this but its not working or maybe I'm doing it wrong, so if I post my file could someone edit it for me? THANKS
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Hi, sorry for the late response. Have been really busy the past few days.
Did you ever get this working?
has anyone ever bothered to go into developer options in settings and turn off transition animations scale or windows animation? to see if things are speeded up even more so. I noticed with windows animation off, the setting screens just pop onto the screen vs. a more gradual appearance of it. I'm trying it with those off to see if any noticeable increase in UI speed. although my UI was fast n lag free before, I'm just curious to see if speed increased even more. Someone brought up a point before that one reason IOS UI is fast because they don't have fancy transition animations n such like android. so cutting those off "should" theoretically improve ICS UI.
I just use the app "spare parts" to speed up the window and transition animations.
krispy521 said:
I just use the app "spare parts" to speed up the window and transition animations.
Click to expand...
Click to collapse
I have that app also. but instead of just speeding them up, you can completely shut them off. things do move alot faster as far as ui goes. if you put the transitions to 10x you get this cool slow mo fading effect when switching to certain tasks or apps. but going into developer options and cutting off windows animation and transition animation does speed things up. they pop on the screen that much faster.
I might try out the spare parts thing to see how that fares. reminds me of an app I had on Ipad, jailbreak needed, that was like a fake gpu accelerator. all it did was speed up window animation and transition animation. it worked well so ill take a look at this. I'd still think completely shutting them off is the fastest method vs. speeding them up.
edit update: I just tried out spare parts like you said. Do you know what speeding up the windows n transitions animations really does in that app? lol all it does is change the developer animation settings. I compared it. OK for example stock developer settings has windows and transition set at 1X by default. now if you go into spare parts app and put those animations to fast, all it did was change developer options animations to .5x speed. so really that spare parts app is not even needed for that. you can go straight into developer options and change this without needing that app. I did it a few times and looked back n forth at spare parts settings then developer options and all it does is change developer option speed. which I can do within Asus settings itself. even in the app description it says cutting them off brings fastest device performance.
I still wish we could find out a more technical answer on if Forcing GPU rendering helps or not. and if it does, is there extra battery drain? only seen mixed answers. nothing concrete yet. I have noticed in the developers section there's a custom rom calles WSG rom. one of his features is that he basically cut off CPU rendering and forced GPU rendering full-time. been hearing good things about how fast it is. I wonder if its the same as going into developer options and forcing gpu rendering. Anyone has any technical insight into this?
I think I was the one who mentioned the screen transition in a thread where someone was calling the TFP laggy.
I have mine set to none. I don't see why anybody would use screen transitions. Isn't instant screen changes what everyone wants?
theandies said:
I think I was the one who mentioned the screen transition in a thread where someone was calling the TFP laggy.
I have mine set to none. I don't see why anybody would use screen transitions. Isn't instant screen changes what everyone wants?
Click to expand...
Click to collapse
cutting off those animations does bring instant screen changes. I think I will leave them off. UI is even faster than before with them off. everything, as far as UI. launching apps, etc..is instant.
here is technical info on what happens when you Force GPU rendering. I asked the developer MasterZen about it in his thread. He isbthe Creator of WSG Rom, where he added the feature of removing software(CPU) rendering and forcing GPU rendering full-time. here's his quote:
" FULL GPU rendering puts our tablets into a state where all the rendering steps, both rasterization and scene composition, are handled by the GPU. The rasterization step in the rendering phase takes all the display list objects, either vectors and bitmaps, and creates textures to be rendered. Then the textures are copied on to the buffer. Thus freeing up our CPU for more excessive task"
demandarin said:
here is technical info on what happens when you Force GPU rendering. I asked the developer MasterZen about it in his thread. He isbthe Creator of WSG Rom, where he added the feature of removing software(CPU) rendering and forcing GPU rendering full-time. here's his quote:
" FULL GPU rendering puts our tablets into a state where all the rendering steps, both rasterization and scene composition, are handled by the GPU. The rasterization step in the rendering phase takes all the display list objects, either vectors and bitmaps, and creates textures to be rendered. Then the textures are copied on to the buffer. Thus freeing up our CPU for more excessive task"
Click to expand...
Click to collapse
Is this how iOS does it? Are there any drawbacks to full GPU rendering, more crashes..ect?
demandarin said:
here is technical info on what happens when you Force GPU rendering. I asked the developer MasterZen about it in his thread. He isbthe Creator of WSG Rom, where he added the feature of removing software(CPU) rendering and forcing GPU rendering full-time. here's his quote:
" FULL GPU rendering puts our tablets into a state where all the rendering steps, both rasterization and scene composition, are handled by the GPU. The rasterization step in the rendering phase takes all the display list objects, either vectors and bitmaps, and creates textures to be rendered. Then the textures are copied on to the buffer. Thus freeing up our CPU for more excessive task"
Click to expand...
Click to collapse
That's how apple does it! I am telling you guys why do you think they use extensive amounts of VRAM and also why they leave their CPU clocked so god damn low!
We should start forcing that in all roms and send a letter to Andy Rubin if we find it helps a bunch!
Sent from my PG86100 using Tapatalk
aypanthony said:
Is this how iOS does it? Are there any drawbacks to full GPU rendering, more crashes..ect?
Click to expand...
Click to collapse
I'm not noticing any drawbacks at the moment on full gpu rendering. MasterZen said in his thread that he will put together a beta team to see if it has any drawbacks or improvements to battery performance.
Wordlywisewiz said:
That's how apple does it! I am telling you guys why do you think they use extensive amounts of VRAM and also why they leave their CPU clocked so god damn low!
We should start forcing that in all roms and send a letter to Andy Rubin if we find it helps a bunch!
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
good idea. plus people should definitely go into developer options and cut off the windows and transition animations, tablet is Wahhabi more snappier now. add force gpu rendering and UI n everything becomes really fast. mines was already great before but cutting off those animations took it to another level. I'm forcing gpu rendering also to see how that fares also. we might be on to something
Wow... i just changed the Windows and transition animation setting to 0.5 instead of 1.0 and enabled the force gpu option. There is a Noticeable improvement in GUI speed for the interface. I like the eye candy so didn't want to completely turn them off.
Thanks for the tip!
Def a speed boost when turning off animations.
MadmanJay said:
Wow... i just changed the Windows and transition animation setting to 0.5 instead of 1.0 and enabled the force gpu option. There is a Noticeable improvement in GUI speed for the interface. I like the eye candy so didn't want to completely turn them off.
Thanks for the tip!
Click to expand...
Click to collapse
no problem
demandarin said:
good idea. plus people should definitely go into developer options and cut off the windows and transition animations, tablet is Wahhabi more snappier now. add force gpu rendering and UI n everything becomes really fast. mines was already great before but cutting off those animations took it to another level. I'm forcing gpu rendering also to see how that fares also. we might be on to something
Click to expand...
Click to collapse
Benchmark it like that!
Sent from my PG86100 using Tapatalk
Wordlywisewiz said:
Benchmark it like that!
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
OK. ill do it tonight. I doubt the animations would affect anything but forcing GPU rendering could have dramatic effect for the positive in the benchmarks. as far as gpu side of things goes.
Hello everybody, here is a mod that should give you better performance by forcing cpu1 (second core) to run more, depending on the zip you flash below. The system will handle how it scales and the dcmhelper script will modify some parameters if you choose that zip. Some people on the EVO 3D felt that it gave them better battery life, some didn't. Some thought the performance was much better, some didn't. This is just something else for you guys to play with and see what works best for you Please note: If you are on viperROM, please choose one of the viperROM .zips! There are no memory optimization .zips for viperROM since that is already done in the ROM! Here are the details:
=============== How was this done? ===============
It was pretty easy, instead of modifying the kernel itself, I just modified /system/etc/init.qcom.post_boot.sh. It already sets extra parameters for the CPU and system shortly after boot. Here are the lines that I added:
Code:
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
What this does is it tells cpu1 to come online and then changes the permissions so user read-only so that it can't be overridden. This will be applied on every boot.
You can also verify this is working by any number of apps, but I find SystemPanel to be the best. They have a free lite version. Just download and tap on the top right where the CPU info is. You will the the CPUs changing, when it goes grey it's offline (which you won't see when using the Dual Core Mod).
aLogcat will also show you everything DCM is doing. Just apply a filter in aLogcat called DCM and it will tell you in detail what is going on.
If you want a little bit less info or want to use adb, just type su and then dcmlog and you will see what the 2nd core is doing exactly. This is updated every 1/4 second for extremely accurate results.
Click to expand...
Click to collapse
=============== Requirements ===============
HTCdev Unlock (Choose "All Other Supported Models" and follow all the directions, including driver install)
Custom recovery - I would recommend TWRP since it doesn't have the /misc issue anymore
Click to expand...
Click to collapse
=============== How to Flash ===============
Download the mod below and place on your internal_sdcard or sdcard (doesn't matter, just remember where you put it!)
Go into Settings > Power > Fast Boot and uncheck that.
Turn the phone off. Once off, press and hold the Volume Down + Power Button until you reach the white bootloader screen
Choose "RECOVERY" (volume down and up to move, power to select)
Choose "Install" and locate the mod wherever you put it. NOTE: If you don't see it, make sure that either internal_sdcard or sdcard is mounted. This can be done via the "Mount" button at the main menu of TWRP. Be sure that either internal_sdcard or sdcard is checked!
Wait until the install is finished and then tap "Reboot to System"
Click to expand...
Click to collapse
=============== Dual Core Mod v2.1 (flash over any existing version) ===============Updated dcmhelper
Fixed issues with cpu1 turning off when screen on
Fixed issues with cpu1 turning on when screen off
Added double check for cpu1 off when screen off
Added logging to logcat
Updated init.qcomm.post_boot.sh
Set perms of 444 on hotplug file, regardless of dcmhelper present or not
Other
Added /system/bin/dcmlog (type su then dcmlog from terminal or adb) - Tells you current cpu1 status [0 = off, 1 = on]
=============== Dual Core Mod v2 (flash over v1) ===============
MANY new options!
Added "Screen Profiles" and "Auto Tweak" script option (all located in one configurable file - /system/bin/dcmhelper) - see 2nd post for more info
Added "Memory Optimization" option - see 2nd post for more info
Support AT&T HTC One X
Support T-Mobile One S
"All-in-One" .zips - all devices supported via 1 .zip file (thanks to a very smart updater-script I wrote )
=============== Dual Core Mod v1 ===============
Initial release
Click to expand...
Click to collapse
=============== Explanation of Mods===============
All DCMs have memory optimizations!
Dual Core Mod - Full time cpu1 on
Dual Core Mod Plus - cpu1 on when screen on, cpu1 off when screen off
Dual Core Mod Ultimate - Same as Plus but governor is tweaked for more performance when screen on, more battery life when screen off.
Click to expand...
Click to collapse
=============== Downloads ===============
Dual Core Mod v2.1
Dual Core Mod v2.1 Plus
Dual Core Mod v2.1 Ultimate
Dual Core Mod Back to Stock
=======================================
Dual Core Mod v2.1 for viperROM
Dual Core Mod v2.1 Plus for viperROM
Dual Core Mod v2.1 Ultimate for viperROM
Dual Core Mod Back to Stock viperROM
Click to expand...
Click to collapse
=============== Credits ===============
Freeza for doing this on the EVO 3D where I got the idea from
rohandhruva, remedy1419, and ewalk4866 for EXTENSIVE testing to fix issues and make DCM better
Click to expand...
Click to collapse
It has been asked to make it easier to donate for people using Tapatalk, so here are the links...
Donate to -viperboy-
http://bit.ly/n7sB9g
More Info
=============== How are all supported phones in 1 zip per file? ===============I wrote a custom updater-script that will identify your device and automatically give you the right file needed. Just like magic
Click to expand...
Click to collapse
=============== How can I monitor the 2nd core? ===============You can also verify this is working by any number of apps, but I find SystemPanel to be the best. They have a free lite version. Just download and tap on the top right where the CPU info is. You will the the CPUs changing, when it goes grey it's offline (which you won't see when using the Dual Core Mod).
aLogcat will also show you everything DCM is doing. Just apply a filter in aLogcat called DCM and it will tell you in detail what is going on.
If you want a little bit less info or want to use adb, just type su and then dcmlog and you will see what the 2nd core is doing exactly. This is updated every 1/4 second for extremely accurate results.
Click to expand...
Click to collapse
=============== What are the "Memory Optimizations?" ===============The optimizations I made are the same that I have made in viperROM. They are as follows:
echo "0,4,6,8,14,15" > /sys/module/lowmemorykiller/parameters/adj
echo "2560,4096,6144,7680,8704,10240" > /sys/module/lowmemorykiller/parameters/minfree
Click to expand...
Click to collapse
This will allow better multitasking and should eliminate any issues with apps being killed off very easily.
Click to expand...
Click to collapse
=============== What are the "Screen Profiles?" ===============The screen profiles are part of a custom script, located in /system/bin/dcmhelper. Once flashed, this .zip runs in the background to monitor screen state (uses hardly any power). When you choose a .zip with this in it, the phone won't just leave the second core always running - it will turn it off when the screen is off and on when the screen is on. This is done via this code here:
while : ; do
awake=`cat /sys/power/wait_for_fb_wake`
if [ $awake = "awake" ]; then
echo 1 > /sys/devices/system/cpu/cpu1/online
awake=
fi
sleep=`cat /sys/power/wait_for_fb_wake`
if [ $sleep= "sleeping" ]; then
echo 0 > /sys/devices/system/cpu/cpu1/online
sleep=
fi
Click to expand...
Click to collapse
Pretty simple and straightforward
Click to expand...
Click to collapse
=============== What is the "Auto Tweaking Script?" ===============The auto tweaking script is the second part of a /system/bin/dcmhelper. This part of the script will set certain governor settings based on the screen being off or on. In the viperROM version, the screen on settings are the same as in the ROM. In the other versions, the screen on settings are more set for performance. I intentionally kept the same settings in the viperROM version to make sure you get as close to the same battery life as unmodified viperROM. Here is a code snipit (from the non-viperROM version) that shows what the settings are:
ondemand_sampling_rate_awake=40000
ondemand_up_threshold_awake=80
ondemand_down_differential_awake=12
ondemand_sampling_down_factor_awake=3
ondemand_sampling_rate_sleep=80000
ondemand_up_threshold_sleep=95
ondemand_down_differential_sleep=5
ondemand_sampling_down_factor_sleep=1
Click to expand...
Click to collapse
Long story short, when awake, it will check if the CPU needs to increase speed faster and in bigger steps. When asleep, it will wait longer before polling the CPU to scale up and it will take a more gradual approach to scaling up. However, you shouldn't experience any lockscreen lag.
Click to expand...
Click to collapse
=============== Long Term Goals for Dual Core Mod ===============
Config file and script for users to set their own settings
Profiles for battery
Set max freq when screen off (will affect virtuous_oc daemon in viperROM, still working on that)
Click to expand...
Click to collapse
you rocking man
gonna give it a guinea pig test
Thinning this now. Seems pretty smooth. Played a couple games real quick and everything worked well. I'll report on battery life.
Tapatalked from my shiny new HTC Evo LTE
Trying it out now. It sounds like a good idea, so I figure why not?
+1, flashing now. Time to start seeing what these can do.
Swyped from my eVo
Can you guys do this, and run quadrant I remember the evo3d would go from 2700 --> 3100 just from doing this mod.
supers2k said:
Can you guys do this, and run quadrant I remember the evo3d would go from 2700 --> 3100 just from doing this mod.
Click to expand...
Click to collapse
If someone posts Quadrant (or other benchmarks) before and afters, I will post them up here, even though I don't believe in benchmarks...
-viperboy- said:
If someone posts Quadrant (or other benchmarks) before and afters, I will post them up here, even though I don't believe in benchmarks...
Click to expand...
Click to collapse
I will hold on
Edit- yay not worth posting, only a 100 better
My quadrants were not dramatically different but the performance increase is insane. Dont see how this won't drain battery thought
Sent from my EVO using Tapatalk 2
my quadrant was lower
lets see if it actually saves battery
Mine was just about the same
Sent from my EVO using xda premium
one thing i notice so far is the phone sleeps phenomenally well
1hr and 45minutes off the charger with little to no use
and the battery is still at 100 ^_^
edit:
i got a 1% drop in 2 hours and 8 minutes of very light usage
not bad at all
Nor really sure how to take this. Quadrants are 5200, roughly the same, but some 3d is smoother. I not sure yet whether to keep DC or not, but this will really make more of a difference when heavily o/c'd. Can't wait to push this to hopefully 2GHz.
Swyped from my eVo
will this affect battery life, both how long the charge lasts, as well as the physical life of the battery?
Does the phone get any hotter since both cores are running?
If this enables the second core to be run but scales its use, how is this different than the stock way? Does the stock way not scale the use of the second core as well? or is the second core completely disabled?
94tbird said:
will this affect battery life, both how long the charge lasts, as well as the physical life of the battery?
Does the phone get any hotter since both cores are running?
If this enables the second core to be run but scales its use, how is this different than the stock way? Does the stock way not scale the use of the second core as well? or is the second core completely disabled?
Click to expand...
Click to collapse
I've seen maybe a slight increase in drain when the screen is on however this mod caused zero extra heat for me. I'm keeping it for now
Sent from my EVO using Tapatalk 2
Kidromulous said:
I've seen maybe a slight increase in drain when the screen is on however this mod caused zero extra heat for me. I'm keeping it for now
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
It hasnt been out long enough for the LTE folks really to make an actual difference. I was hoping to hear from maybe Evo 3d people who switched to lte and see their thoughts on it if they used it on the 3d.
94tbird said:
It hasnt been out long enough for the LTE folks really to make an actual difference. I was hoping to hear from maybe Evo 3d people who switched to lte and see their thoughts on it if they used it on the 3d.
Click to expand...
Click to collapse
I am one of the people who used it on the 3d. It doesn't cause the phone to heat up i put the phone through its paces etc. The performance increase was almost immediately noticeable for me just like with the 3d.
Sent from my EVO using Tapatalk 2
So awesome to see Viperboy has the EVO LTE. Happily running Redline on my 3vo, can't wait to see what he churns out on the LTE.
If I wanted to do this to my One X, can I just add those two lines in manually? Does anything need to be removed from the script? Is there a specific location that I need to add them or can I just toss them in as the last lines in the file? TIA.
Friends, I got this k3 note with chipset MT6752. I have to modify its thermal configuration.
It is throttling the CPU so early when playing games, so it goes from 1.69Ghz to 1.4Ghz. This causes framedrop.
In snapdragon devices there will be a file /etc/thermal*.conf which is not present in mediatek phones.
Please help on where to change that config, can't seem to find anywhere... I also dont like setting min/max frequency
thanks
dude_creative said:
Friends, I got this k3 note with chipset MT6752. I have to modify its thermal configuration.
It is throttling the CPU so early when playing games, so it goes from 1.69Ghz to 1.4Ghz. This causes framedrop.
In snapdragon devices there will be a file /etc/thermal*.conf which is not present in mediatek phones.
Please help on where to change that config, can't seem to find anywhere... I also dont like setting min/max frequency
thanks
Click to expand...
Click to collapse
Not sure if you can edit it, but it's at /system/etc/.tp/
Also if you edit build.prop so that the ROM reports as a test build rather than user, you can get into the thermal settings in MTK EngineeringMode
HypoTurtle said:
Not sure if you can edit it, but it's at /system/etc/.tp/
Also if you edit build.prop so that the ROM reports as a test build rather than user, you can get into the thermal settings in MTK EngineeringMode
Click to expand...
Click to collapse
Thanks, I changed the build.type=eng and thermal settings are accessible now. I changed to 120deg celcius settings and no throttling anymore at least.
Now games are playable with low settings. I also did GL tools fake GPU Mali T628.
Full HD screen is a double edge sword.
dude_creative said:
Thanks, I changed the build.type=eng and thermal settings are accessible now. I changed to 120deg celcius settings and no throttling anymore at least.
Now games are playable with low settings. I also did GL tools fake GPU Mali T628.
Full HD screen is a double edge sword.
Click to expand...
Click to collapse
Is there a quantitative way to check the throttling? Or is it just experience (qualitative)?
Might as well check mine with/without the temp cap.
HypoTurtle said:
Is there a quantitative way to check the throttling? Or is it just experience (qualitative)?
Might as well check mine with/without the temp cap.
Click to expand...
Click to collapse
CPU spy Plus now shows 1.69Ghz (max) always when I am playing asphalt, earlier it dropped to 1.4ghz after sometime. I reset timers of CPU spy and measured it.
Also found that we can rename the thermal.conf to something else (idea from a coolpad forum), and now no throttling in build type=User mode also .. :good:
I also had to do, in GLTools Fake GPU Mali-T628 works the best with 0.5x texture and Medium inside asphalt 8 .
So much tweaks just to play a game. 1080p gaming is not the league of MT6752 i think .
dude_creative said:
CPU spy Plus now shows 1.69Ghz (max) always when I am playing asphalt, earlier it dropped to 1.4ghz after sometime. I reset timers of CPU spy and measured it.
Also found that we can rename the thermal.conf to something else (idea from a coolpad forum), and now no throttling in build type=User mode also .. :good:
I also had to do, in GLTools Fake GPU Mali-T628 works the best with 0.5x texture and Medium inside asphalt 8 .
So much tweaks just to play a game. 1080p gaming is not the league of MT6752 i think .
Click to expand...
Click to collapse
Yep i have the same issue with my jiayu s3. I can't believe i have this issue since on video reviews on this product the gaming experience was amazing.
Sadly in my hands its not the same, don't know if its a fault with the device i have received or they just give them a better device for reviews.
I might attempt to teardown the device and do a cooling hack.
Okay upon further testing I have found that it works best at setting it to "thermal protection only" within the mtk engineering mode.
No need to set it to 120c and no need to rename the thermal config. Setting it to high 120c was extremely hot while testing it with wwe immortals game.
Now the lag has gone within that game and the temps are quite good. Even scored higher in benchmarks now.
Thermal.conf file not in readable form
dude_creative said:
Thanks, I changed the build.type=eng and thermal settings are accessible now. I changed to 120deg celcius settings and no throttling anymore at least.
Now games are playable with low settings. I also did GL tools fake GPU Mali T628.
Full HD screen is a double edge sword.
Click to expand...
Click to collapse
Thanks,I changed the build.type =eng but thermal.conf file is not in readable format.Could you tell me how did you read from this file ?
shri3415 said:
Thanks,I changed the build.type =eng but thermal.conf file is not in readable format.Could you tell me how did you read from this file ?
Click to expand...
Click to collapse
You have to change above line in the /system/build.prop file .. thermal.conf is still not readable. Only mtk guys will know
dude_creative said:
You have to change above line in the /system/build.prop file .. thermal.conf is still not readable. Only mtk guys will know
Click to expand...
Click to collapse
Hi,
I changed the build.type=eng in /system/build.prop file. But still thermal.conf is not in readable format, it looks like encrypted.
As you mentioned in previous comments, you'r able to change the 120d c settings.
I want to know the thermal cutoff of devices.
Kindly help me to figure out the way to read this file properly. I will be very grateful.
Thanks a lot.
shri3415 said:
Hi,
I changed the build.type=eng in /system/build.prop file. But still thermal.conf is not in readable format, it looks like encrypted.
As you mentioned in previous comments, you'r able to change the 120d c settings.
I want to know the thermal cutoff of devices.
Kindly help me to figure out the way to read this file properly. I will be very grateful.
Thanks a lot.
Click to expand...
Click to collapse
Rename it to theremal.conf.bak , thats enough
Can anyone please tell me how to change the build.type into Eng I found the file system/build.prop in the recovery mod but I can't edit it thanks in advance.
Dors renaming the thermal.conf file or removing it have a damage on the long term ?
on miui 9 change ro.buid.type=eng doesnt unlock the thermal config in mtk engineering, anyone can solve this?
dude_creative said:
CPU spy Plus now shows 1.69Ghz (max) always when I am playing asphalt, earlier it dropped to 1.4ghz after sometime. I reset timers of CPU spy and measured it.
Also found that we can rename the thermal.conf to something else (idea from a coolpad forum), and now no throttling in build type=User mode also .. :good:
I also had to do, in GLTools Fake GPU Mali-T628 works the best with 0.5x texture and Medium inside asphalt 8 .
So much tweaks just to play a game. 1080p gaming is not the league of MT6752 i think .
Click to expand...
Click to collapse
Initially I found this thread
http://en.miui.com/forum.php?mod=viewthread&tid=1136161&page=1#pid18973837
Based on my findings
You could also enable the test build, but when I did this for MT6592 & MT6753 the temps were 15-20 degrees higher than user mode, so not recommended at all
- for MT6753 (android 5.1) there are 4 files
thermal_manager /etc/.tp/thermal.conf >>> 66 degC throttling
thermal_manager /etc/.tp/thermal.off.conf >>> 85 degC throttling
thermal_manager /etc/.tp/.ht120.mtc >>> 117 degC throttling
.thermal_policy_00 did not figure it out, don't care actually
So easiest way is to enable a script in kernel adiutor to run when phone starts and add
su
thermal_manager /etc/.tp/.ht120.mtc
When I tried to rename the thermal.conf, I got 75 degC throttling, so maybe this is linked to .thermal_policy_00 ???
- for MT6592 (android 4.4) there are 3 files, except the .thermal_policy_00
renaming the thermal.conf I managed to get above 85 degC, but also su thermal_manager works
So easiest way for me is kernel adiutor with Init.d with
su
thermal_manager "file-path"
Look here: https://github.com/wszqkzqk/mtk-thermal-config-tool-windows
Disable throttling
Hi, I just delete thermal.conf in system/etc .tp try to copy edited thermal.conf to that folder but couldn't able to do it error showing , unable to create any folder on that directory . someone please help me out. How to regain thermal.conf ..
My mobile is tecno id5a mt6761
---------- Post added at 06:33 PM ---------- Previous post was at 06:19 PM ----------
I just run on terminal su thermal manager/etc/.to/thermal.conf but its showing thermal manager not found , do I need to install thermal manager apk or what may I go wrong?