[HACK] Overclocking and tuning Adreno200 GPU & misc qsd8k development - Android Software/Hacking General [Developers Only]

[HACK] Overclocking and tuning Adreno200 GPU & misc qsd8k development - Android Software/Hacking General [Developers Only]

{
"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"
}
"Hey Dev! Make those Snapdragons fly!"
A little into:
Hello wonderful and amazing people! I'm Fera, ROM/Kernel developer from SonyXperia X10 forum. I'm 20 years old hungry student and I'd like to share a bit of my experience with you guys. Open Source rules! :highfive: Hacks listed here have to work despite kernel versions. I made this hacks specificly for qsd8k board, but you may try your luck on newer chipsets if you get the logic. Things are pretty similar on Snapdragon chipsets. I spent a lot of hard time figuring things out so if you like this stuff, hit 'Thanks' button, rate this thread, share it to let other people know, and feed me.
Now..enough for drama, have good music, tighten your belts, sit back and relax - we're going to fly at the speed of light..
GPU and CPU overclocking:
I will show an example by overclocking my Sony Ericsson Xperia X10 retired phone with QSD8x50 Snapdragon S1 board with Adreno200 rev1 GPU onboard. You may look at more complex details list of Adreno GPU HERE.
Let's start now. This hack requiers to recompile kernel for your device. It's quite simple actually. To keep things more clear, let's note what we have:
Code:
grp_clock = Graphics clock //128000000 by default for adreno200 rev1
ebi1_clock = External Bus Interface 1 clock //256000000 by default for qsd8k
imem_clock = Internal Graphics Memory clock //256000000 by default for qsd8k
We're going to deal with grp_clock of Adreno bus clock and CPU clock itself.
In kernel sources under arch/arm/mach-msm we have acpuclock-8x50.c file. This file (or any equivalent to your board) contains actual CPU freq. table and misc hw stuff related to clocks.
Default freq. table for qsd8k is:
PHP:
{ 0, 19200, ACPU_PLL_TCXO, 0, 0, 0, 0, 14000, 0, 0, 1000},
{ 0, 128000, ACPU_PLL_1, 1, 5, 0, 0, 14000, 2, 0, 1000},
{ 1, 245760, ACPU_PLL_0, 4, 0, 0, 0, 29000, 0, 0, 1000},
{ 1, 384000, ACPU_PLL_3, 0, 0, 0, 0, 58000, 1, 0xA, 1000},
{ 0, 422400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xB, 1000},
{ 0, 460800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xC, 1000},
{ 0, 499200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xD, 1025},
{ 0, 537600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xE, 1050},
{ 1, 576000, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xF, 1050},
{ 0, 614400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x10, 1075},
{ 0, 652800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x11, 1100},
{ 0, 691200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x12, 1125},
{ 0, 729600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x13, 1150},
{ 1, 768000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x14, 1150},
{ 0, 806400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x15, 1175},
{ 0, 844800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x16, 1200},
{ 0, 883200, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x17, 1225},
{ 0, 921600, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x18, 1275},
{ 0, 960000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x19, 1275},
{ 1, 998400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1A, 1300},
Little theory lesson:
Let's take last line and digest it..
1/0 - means that this clk ladder is enabled/disabled
998400 - Actual ladder freq. in Khz
ACPU_PLL_3, 0, 0, 0, 0 - AXI/PLL macros, adresses
128000 - AXI bus freq. in Khz
0/1/2 - Init adresses
0x1A - Step raw code for CPU
1300 - Voltage gained to corresponding freq. step in mV
We can see that we have 128000 freq. on top of the table set as 0 (disabled) for global access and reserved for PLL_1 which is adressed to 2. After hardcore testings I found out that this adresses to GPU AXI bus clock used by Adreno200. We simply change it to 192000Khz. Overclocking to higher values made my device very unstable, so don't bump high too much.
The ready line will be look as:
PHP:
{ 0, 192000, ACPU_PLL_1, 1, 5, 0, 0, 14000, 2, 0, 1000 },
But it's not all. Note that this may vary in your .c file so turn on your brain and search for axi defines. In my case it was in same .c file in this function :
Code:
unsigned long clk_get_max_axi_khz(void)
{
return 128000;
}
EXPORT_SYMBOL(clk_get_max_axi_khz);
Find something similar to this (if it realy exists) and set value to 192000.
Now we have to update all CPU freq table with overclocked axi bus values which could be stable.. At this point I spent monthes of testing and finally came up to stable things. I will just paste here my table which also includes CPU overclock and undervolt:
PHP:
{ 0, 19200, ACPU_PLL_TCXO, 0, 0, 0, 0, 14000, 0, 0, 1000 },
{ 0, 192000, ACPU_PLL_1, 1, 5, 0, 0, 14000, 2, 0, 1000 },
{ 1, 245760, ACPU_PLL_0, 4, 0, 0, 0, 29000, 0, 0, 1025 },
{ 1, 384000, ACPU_PLL_3, 0, 0, 0, 0, 58000, 1, 0xA, 1025 },
{ 0, 422400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xB, 1025 },
{ 1, 460800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xC, 1025 },
{ 0, 499200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xD, 1025 },
{ 0, 537600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xE, 1025 },
{ 1, 576000, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xF, 1025 },
{ 0, 614400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x10, 1050 },
{ 0, 652800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x11, 1075 },
{ 0, 691200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x12, 1100 },
{ 0, 729600, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x13, 1125 },
{ 1, 768000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x14, 1125 },
{ 0, 806400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x15, 1150 },
{ 0, 844800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x16, 1200 },
{ 0, 883200, ACPU_PLL_3, 0, 0, 0, 0, 160000, 1, 0x17, 1225 },
{ 0, 921600, ACPU_PLL_3, 0, 0, 0, 0, 160000, 1, 0x18, 1250 },
{ 0, 960000, ACPU_PLL_3, 0, 0, 0, 0, 160000, 1, 0x19, 1275 },
{ 1, 998400, ACPU_PLL_3, 0, 0, 0, 0, 192000, 1, 0x1A, 1300 },
{ 1, 1036800, ACPU_PLL_3, 0, 0, 0, 0, 192000, 1, 0x1B, 1325 },
{ 1, 1075200, ACPU_PLL_3, 0, 0, 0, 0, 192000, 1, 0x1C, 1325 },
{ 1, 1113600, ACPU_PLL_3, 0, 0, 0, 0, 192000, 1, 0x1D, 1325 },
{ 1, 1152000, ACPU_PLL_3, 0, 0, 0, 0, 192000, 1, 0x1E, 1350 },
{ 1, 1190400, ACPU_PLL_3, 0, 0, 0, 0, 192000, 1, 0x1F, 1350 },
{ 1, 1228800, ACPU_PLL_3, 0, 0, 0, 0, 192000, 1, 0x20, 1375 },
{ 1, 1267200, ACPU_PLL_3, 0, 0, 0, 0, 192000, 1, 0x21, 1425 },
{ 1, 1305600, ACPU_PLL_3, 0, 0, 0, 0, 192000, 1, 0x22, 1425 },
{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0},
This is how my table looks after GPU/CPU overclock/undervolt and hard testings. I find theese values solid stable and best at performance, exept last freq ladder. 1.3Ghz overclock is a bit overdose for my device (since it is max available freq. ladder for my cpu) but I save it in case there is a phone of mine with balls of steel (not all CPU chips are same and not all can handle overclocking). As you may notice, overclocked axi frequency is enabled on higher CPU clock steps. This means that axi overclock will be enabled when CPU runs on 1113Mhz and higher, so to enable all this things you have to use overclocked CPU table.
Since we overclocked our CPU we need to modify our .c file with all theese tables furter (acpuclock-8x50.c in my case) to match new changes. Search for:
Code:
case 0x00:
max_acpu_khz = 998400;
and set it to 1305600 (maximum available CPU freq.)
Then searching for this:
Code:
static struct cpufreq_frequency_table freq_table[20];
and changing the value in the ind to 28 since we have now 28 CPU freq. steps in total. That's all for CPU overclock. Continuing boosting our Adreno..
Open your board-****.c file.
If you use old KGSL drivers (Android 2.3 and older), search for struct kgsl_platform_data kgsl_pdata function. In function structure you will see this:
Code:
.high_axi_3d = 128000,
.max_grp3d_freq = 0,
.min_grp3d_freq = 0,
Set high_axi_3d value to 192000.
Set max_grp3d_freq value to 256*1000*1000.
Set min_grp3d_freq value to 192*1000*1000.
If you use new KGSL drivers (Android 4.0+) then search for struct kgsl_device_platform_data kgsl_3d0_pdata. You will see something like this:
PHP:
.pwrlevel = {
{
.gpu_freq = 0,
.bus_freq = 128000000,
},
Set gpu_freq value to 256000000.
Set bus_freq value to 192000000.
In the end we have undervolted and overclocked (1.3Ghz) CPU and overclocked GPU of my old phone. Saying again..Overclocking bus higher than 192Khz is realy bad idea for QSD8x50.
When you're done, build your kernel with enabled debugging (CONFIG_DEBUG_KERNEL=y) and then add this script to mount debug sysfs dir. in init.d or anywhere else on auostart:
Code:
#!/system/bin/sh
### FeraLab ###
mount -t debugfs debugfs /sys/kernel/debug
echo 0 > /sys/kernel/debug/msm_fb/0/vsync_enable
This script will also disable VSYNC to boost your 2D FPS. When system runs check out /sys/kernel/debug/clk_rate folder (If you can't see this folder the your init.d support is not working properly..put script somewhere else, in /etc/hw_config.sh for ex.). You will have to see reports:
gp_clk - 192000000
grp_3d_clk - 256000000
imem_clk - 256000000
And for CPU overclocking use any app you like from market. No-frill-CPU is a good one.
Bingo! :silly:
Now I can play such games like NFS MW or GTA Vice City on my retired but rocking phone.. (proof video)
If you like this - feed me :good:
Display panel overclocking:
Still not enough? Wow..you're d thirsty one..
Ok.. Let's overclock your LCD bus frequency then..
Install any app on you pc that could recursively search txt from kernel directory (I use double-cmd-gtk on ubuntu) or just search you git repo online. Fins this thing (It may vary on 3.x kernels. This is for 2.6 ones):
Code:
panel_info.clk_rate
This part of code will most probably be under /drivers/video/msm folder or directly in your board-xxx.c file which is just my case.
I have this values by default:
Code:
panel_data->panel_info.clk_rate = 192000000;
panel_data->panel_info.clk_min = 190000000;
panel_data->panel_info.clk_max = 200000000;
Simply change to
Code:
panel_data->panel_info.clk_rate = 235000000;
panel_data->panel_info.clk_min = 192000000;
panel_data->panel_info.clk_max = 256000000;
Done :good:
Updating KGSL drivers in kernel:
At first I though this is realy hard to do but I dealed with this and wanna show you a quick and easy way to do it. It is pretty same for most kernel versions. I will do an example using my 2.6 kernel.
Basicly, just get my sourcecode .zip, extract it somewhere. Go to your kernel's /drivers/gpu/msm (or drivers/char/msm) folder and delete it. Now go to my kernel/drivers/gpu/msm and copy that folder to your kernel. Not finished yet. Replace your file with mine from my kernel/include/linux/msm_kgsl.h. Done. Yeah. Soo simple. This are latest CAF gb_release KGSL drivers which improved my 3D performance around 30%. Don't forget to update ROM libs. (You may take them from my .zip too) Same thing is for newer android versions, but dont copy it from my kernel. My kernel is for GingerBread atm.
Tuning Adreno GPU:
This is more simple than previos guides and is already familiar, but I will stick it here again anyway.
It's about using Adreno config file. This will work only on GingerBread ROMs. To make it working place this part of code in your /system/etc/hw_config.sh:
Code:
if [ ! -h /data/local/tmp/adreno_config.txt ]; then
chmod 777 /system/etc/adreno_config.txt
ln -s /system/etc/adreno_config.txt /data/local/tmp/adreno_config.txt
fi
Now edit and put your adreno_config.txt in /system/etc/ and set all permissions for it (chmod 777). Also edit your build.prop, add:
Code:
debug.egl.hw=1
debug.egl.profiler=1
debug.performance.tuning=1
debug.sf.hw=1
This is how originnal version of adreno_config file looks like. It contains various explanations and I will put it here so you could refer to.
Now what parameters are realy cool to tune are:
Code:
forceAutoTextureCompression=1
triJuice=3
Theese configs have to greatly improve your 3D performance in cost of quality, but I think it doesnt matter anymore for old devices.
Juice it:
A simple trick to disable framebuffer swapping and flush all frames without filtering os to edit your build.prop and add/replace theese strings:
Code:
debug.sf.hw=1
debug.egl.hw=1
debug.egl.profiler=1
debug.performance.tuning=1
debug.gr.swapinterval=0
debug.egl.swapinterval=0
This will double your 2D FPS but you will get UI glithces instead. It's not because something've get slow - it's because it've get too fast . If you wish to use this trick for prolonged use, I suggest you do disable all animations in system settings.
Probably you may want have a look at another my thread for optimized apps & games HERE.
I think that's it for now. Have a nice day-time. Peace out! :fingers-crossed:

tuning adreno gpu
while i wanted to try this hack however i find it impossible as my phone htc hd2 has not got a hw_config.sh in it searched with es file explorer and root explorer and also in system etc and cant find the file. is there any other way to do this? cant do kernel hack as no nothing about kernels at all phone htc hd2 cm7 gingerbread rom http://forum.xda-developers.com/showthread.php?t=1867986 it is fast and very stable but would be nice to tweak it a bit. Oh and for juice it in my build prop only have debug.sf.hw=1 not the other debug lines do i just add them to build.prop. thank you

Well i ain't pro in kernel developing but is it work with adreno 205-8255 chipset-mogami board?

yamin8000 said:
Well i ain't pro in kernel developing but is it work with adreno 205-8255 chipset-mogami board?
Click to expand...
Click to collapse
Yes, adreno 205 has been overclocked before. See this commit: https://github.com/Evervolv/android...mmit/9d5bda971744f536125488a19043b0003bbbfd73

yamin8000 said:
Well i ain't pro in kernel developing but is it work with adreno 205-8255 chipset-mogami board?
Click to expand...
Click to collapse
npz said:
Yes, adreno 205 has been overclocked before. See this commit: https://github.com/Evervolv/android...mmit/9d5bda971744f536125488a19043b0003bbbfd73
Click to expand...
Click to collapse
I realy hope that that commit realy does overclock andreno205, because in adreno200, despite of setting various values for same kgsl-3d data function, grp_clk was still reporting same default value.. Thats why i digged deeper to find out how adrenos work.. I dont know how do new chips work but older ones frequencies are fully depended on cpu..

antutu benchmark score would be nice to compare the results before & after cpu and gpu OC each :3

Flaîm said:
antutu benchmark score would be nice to compare the results before & after cpu and gpu OC each :3
Click to expand...
Click to collapse
I will say about my kernel..that after all optimizations of my kernel..which are not only overclocking, comparing quadrant 3d scores..60% improvement was observed. Comparing cpu score on antutu.. 80% of improvement was observed. Not many dual core cpus can reach 1400 in antutu cpu.. I get it on my one core. Overall my kernel does roughly double higher score than stock firmware. I will attach screensjots later.

@FeraVolt Can you please help me to overclock my GPU on MSM7225A? The kernel source is here: https://github.com/rootdefyxt320/android_kernel_motorola_tinboost My kernel version is 2.6.38.6
EDIT: Okay, here is my acpuclock-7201.c:
Code:
/* 7x25a pll2 at 1200mhz with GSM capable modem */
static struct clkctl_acpu_speed pll0_960_pll1_245_pll2_1200_pll4_800_25a[] = {
{ 0, 19200, ACPU_PLL_TCXO, 0, 0, 2400, 3, 0, 30720 },
{ 0, 61440, ACPU_PLL_1, 1, 3, 7680, 3, 1, 61440 },
{ 1, 122880, ACPU_PLL_1, 1, 1, 15360, 3, 2, 61440 },
{ 1, 245760, ACPU_PLL_1, 1, 0, 30720, 3, 3, 61440 },
{ 0, 300000, ACPU_PLL_2, 2, 3, 37500, 3, 4, 150000 },
{ 1, 320000, ACPU_PLL_0, 4, 2, 40000, 3, 4, 122880 },
{ 0, 400000, ACPU_PLL_4, 6, 1, 50000, 3, 4, 122880 },
{ 1, 480000, ACPU_PLL_0, 4, 1, 60000, 3, 5, 122880 },
{ 1, 600000, ACPU_PLL_2, 2, 1, 75000, 3, 6, 200000 },
May you please help me to interpret it?

HTC HD2
Would this hack work on an old HTC HD2 , it has Adreno 200 (AMD Z430) with OpenGL ES 2.0 support GPU and a Snapdragon S1 QSD8250 chipset

EvilMegaDroid said:
Would this hack work on an old HTC HD2 , it has Adreno 200 (AMD Z430) with OpenGL ES 2.0 support GPU and a Snapdragon S1 QSD8250 chipset
Click to expand...
Click to collapse
Yes
Sent from my X10i using XDA Free mobile app

Can't find
I can't find the board-****.c file

Will this work on adreno 203...on arubaslim board on my Samsung galaxy core duos.snapdragon s4 play???

Thread updated with newer CPU freq table for qsd8k. True 1,3Ghz overclock...

Another update in OP. New CPU freq. table, and improved board-config fine-tuning.

So I'm guessing I cannot pull the kernel from my phone decompile edit some stuff and then recompile....bummer
Sent from my LT28i using XDA Free mobile app

You can compile kernel from source code only
Sent from my X10i using xda premium

Hi, how i change minimum and max CPU clock on i9515 stock ROM?

lorenzitto said:
Hi, how i change minimum and max CPU clock on i9515 stock ROM?
Click to expand...
Click to collapse
On new devices sysfs can be used for this reason. Otherwise kernel recompilation is required

How I can do it on the cyanogenmod 12.1 ported for i9515 ( s4 4g ) ?

It depends on your kernel

Related

msm7500 series overclocking

crazybyte said:
I suggest to the rom cookers, to check about Qualcomm 7201A overclock, because in another forum, someone overclocked it to 768 mhz, and it seems to be true, because it's the real speed of the output of PLL generator. Our devices has a divisor.
Here is the link:
http://www.nuerom.com/BlogEngine/post/2009/09/06/Touch-Pro-running-at-800MHZ.aspx
I think that all the problem resides in the file:
http://android.git.kernel.org/?p=ke...3;hb=ebea985a6ec461a59afb86f0068cc1d79d7c8bf1
We think that the first step it's enable cpufreq to scale to 768mhz, and testing it in this freq.The info about scalling are in the lines 227 and 228:
227 CONFIG_MSM_CPU_FREQ_ONDEMAND_MAX=384000
228 CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN=245760
Click to expand...
Click to collapse
i thought this might have better set up as its own thread.
edit
i have done some mild kernel work in winmo on a 7200 and do believe this is not only possible but a decent hack worth putting time into. also no2chem is to winmo as cyanogen is to android. so its from a good source

I posted in that thread too. I think the 65nm MSM7201A in the G1 could be easily pushed to 768MHz.
coolbho3000 said:
I was thinking about this but never could get any kernel to compile because I'm stupid. The other way would be to use PLL 2 to go all the way to 1056 (probably impossible ).
It's actually not that simple. This is the file you want to modify: http://android.git.kernel.org/?p=ke...13e3ef308591e8c0e5fe7ce0311d3f4d6b0b8;hb=HEAD
Add an entry for 768000 in static struct clkctl_acpu_speed acpu_freq_tbl[] for 768000.
{ 768000, ACPU_PLL_1, 1, 0, 128000, 5, VDD_7, 128000, 0, 5, -1 }
Those should be the correct values for 768MHz - all except for the last two 5 and -1. I don't know what those do, probably something to do with scaling.
Click to expand...
Click to collapse
Then add 768000 to static struct cpufreq_frequency_table freq_table[] and you should be able to echo those values into scaling_max_freq and scaling_min_freq

although this would kill the battery in 5 minuites it is great for hero and emulators as well

If someone could pull that off it would be killer.
Do you really think it would be that big of a drain on the battery if it was only climbing that high under heavy load situations rather than being set that high at all times?
I would be willing to take a hit in battery life to gain a performance increase of that type as long as the batter life doesn't end of 1/4 of what it was.

I've got an upgraded battery, so I don't care. Give me more speed!

One note please remember this was confirmed on 7500 not 7501a also it was a cdma phone not gsm but it could work with some work

If this makes a big different in performance, I'm willing to use the brick size battery I bought. It's been laying around unused since I bought it.

i am willing to try this but i dont know which file you edit. If someone can tell me ill give it a go

I don't think it'll be that easy though

You need to recompile the kernel with the added values in clkctl_acpu_speed acpu_freq_tbl[] in http://android.git.kernel.org...b0b8;hb=HEAD
I might give it a go if you want to try it out. I think we should determine if the last two 5 and -1 numbers are important first. Does look like scaling:
Code:
78 /* Index in acpu_freq_tbl[] for steppings. */
79 short down;
80 short up;
As far as I can tell the stepping values are used here:
Code:
332 while (cur_s != tgt_s) {
333 /*
334 * Always jump to target freq if within 256mhz, regulardless of
335 * PLL. If differnece is greater, use the predefinied
336 * steppings in the table.
337 */
338 int d = abs((int)(cur_s->a11clk_khz - tgt_s->a11clk_khz));
339 if (d > drv_state.max_speed_delta_khz) {
340 /* Step up or down depending on target vs current. */
341 int clk_index = tgt_s->a11clk_khz > cur_s->a11clk_khz ?
342 cur_s->up : cur_s->down;
343 if (clk_index < 0) { /* This should not happen. */
344 printk(KERN_ERR "cur:%u target: %u\n",
345 cur_s->a11clk_khz, tgt_s->a11clk_khz);
346 rc = -EINVAL;
347 goto out;
348 }
349 cur_s = &acpu_freq_tbl[clk_index];
350 } else {
351 cur_s = tgt_s;
352 }

daproy said:
You need to recompile the kernel with the added values in clkctl_acpu_speed acpu_freq_tbl[] in http://android.git.kernel.org...b0b8;hb=HEAD
I might give it a go if you want to try it out. I think we should determine if the last two 5 and -1 numbers are important first. Does look like scaling:
Code:
78 /* Index in acpu_freq_tbl[] for steppings. */
79 short down;
80 short up;
Click to expand...
Click to collapse
yep ill try it out if you compile it btw what is the worst hat could happen to my phone?

The code is optimized to stay on the same PLL so the last two numbers are the array index in the acpu_freq_tbl[] two go down to or up to from that entry. Since our new entry is ACPU_PLL_1 the next one down is entry 6 and there are none to step up to so it should be:
{ 768000, ACPU_PLL_1, 1, 0, 128000, 5, VDD_7, 128000, 0, 6, -1 }
The step up from 384000 should also be changed now that we're adding a higher frequency on the same PLL to:
{ 384000, ACPU_PLL_1, 1, 1, 128000, 2, VDD_6, 128000, 0, 2, 8 }
So the acpu_freq_tbl[] should be:
Code:
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 19200, ACPU_PLL_TCXO, 0, 0, 19200, 0, VDD_0, 30720, 0, 0, 4 },
{ 122880, ACPU_PLL_0, 4, 1, 61440, 1, VDD_3, 61440, 0, 0, 4 },
{ 128000, ACPU_PLL_1, 1, 5, 64000, 1, VDD_3, 61440, 0, 0, 6 },
{ 176000, ACPU_PLL_2, 2, 5, 88000, 1, VDD_3, 61440, 0, 0, 5 },
{ 245760, ACPU_PLL_0, 4, 0, 81920, 2, VDD_4, 61440, 0, 0, 5 },
{ 352000, ACPU_PLL_2, 2, 2, 88000, 3, VDD_5, 128000, 0, 3, 7 },
{ 384000, ACPU_PLL_1, 1, 1, 128000, 2, VDD_6, 128000, 0, 2, 8 },
{ 528000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },
{ 768000, ACPU_PLL_1, 1, 0, 128000, [B]5[/B], VDD_7, 128000, 0, 6, -1 }
{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 },
};
and
Code:
static struct cpufreq_frequency_table freq_table[] = {
{ 0, 19200 },
{ 1, 122880 },
{ 2, 128000 },
{ 3, 245760 },
{ 4, 384000 },
{ 5, 528000 },
{ 6, 768000 },
{ 7, CPUFREQ_TABLE_END },
};
coolbho3000, does this sound correct? You sure about the values for a11clk_src_div, ahbclk_khz, ahbclk_div at 768000? Sound like you've already started looking into this.
Is there a reason to change the AHB bus clock divider ahbclk_div to 5?

JJbdoggg, not sure what it'll do if it doesn't work. Probably freeze up the phone.

JJbdoggg said:
yep ill try it out if you compile it btw what is the worst hat could happen to my phone?
Click to expand...
Click to collapse
Your processor could get fried.

I'm 100% sure about a11clk_src_div (according to Qualcomm docs 0000 means you don't divide the PLL at all, leaving it at 768000, 0001 means you divide by 2, 0010 means you divide by 3, etc) but I'm not sure if ahbclk_khz is supposed to go above 132000 so I left it at 128000, making ahbclk_div 5 (768000/6 = 128000). Other possible values for the two might be 153600 and 4, and 192000 and 3. I'm digging through the Qualcomm documentation to see if I can find anything.

More info in a follow up from the original post:
http://www.nuerom.com/BlogEngine/post/2009/09/08/Yet-more-notes-on-overclocking.aspx

daproy said:
More info in a follow up from the original post:
http://www.nuerom.com/BlogEngine/post/2009/09/08/Yet-more-notes-on-overclocking.aspx
Click to expand...
Click to collapse
Seems unstable, but worth a shot. Seems like the worst that's happened to a WM user is a freeze.
3) There is a clock divider for the AHB that is separate from the ARM11 frequency. I’ve tried increasing the divider from the default of 0x4 to 0x5, with no real increase in stability.
It seems like multiple AHB clocks/dividers would work then, probably answering my above post... maybe best to try and see which is the most stable?

that would end getting really hot, if it is usable and perfected, hell yeah would i love to have some power like that out of my g1, i got 2 batteries

Well I played around with this a bit. Pulled cyanogen's latest kernel code with BFS from github. Patched acpuclock.c (patchfile attached). Compiled with the android toolchain.
First off there is definitely something wrong with the kernel i compiled because it was horrible slow to boot. I did use the .config from cyanogen 4.1.6 without edits so I'm not sure why. I can't imagine it was due to the patch since with default min and max scaling it should be running the same as the kernel compiled by cyanogen.
Regardless, I was able to try to overclocking:
Code:
# echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
# echo 768000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# cat /proc/cpuinfo
Processor : ARMv6-compatible processor rev 2 (v6l)
BogoMIPS : 527.15
Features : swp half thumb fastmult edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x1
CPU part : 0xb36
CPU revision : 2
Hardware : trout
Revision : 0080
Serial : 0000000000000000
# echo 768000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
# cat /proc/cpuinfo
Processor : ARMv6-compatible processor rev 2 (v6l)
BogoMIPS : 766.77
Features : swp half thumb fastmult edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x1
CPU part : 0xb36
CPU revision : 2
Hardware : trout
Revision : 0080
Serial : 0000000000000000
It reboot immediately following the cpuinfo but looks like it did scale up to 768000
Phone is fine after the reboot and back to default min max freq.
Before trying to toy around with different AHB clock dividers I should probably work out getting a good kernel to compile first, unless cyanogen has some spare time and feels like taking a look at this. I know I won't have any spare time in the next few days.

Amazing!!
Nice to see 766 in cpuinfo What do you think, was the reboot caused by cpu failure or "something wrong" in kernel?
If I understand well, we must modify kernel, and we cant easily install app to overclock..

[Q] Editing CPU Freq tables - any info?

I am looking into modifying the kernel on the Incredible S (as HTC kindly dropped the sources) and I was wondering about changing the CPU Freq table. I can find lots of people who have done it, but very little info on how to go about it.
First of all there are two acpuclock files - one for the qsd8x5 and one for the 7x30. The phone has an 8255 so I presume the first is correct, but the buildprop is actually setup as if it contains a 7x30 so I am not sure which of the two files it is using.
Secondly, if there any reference as to what freq /voltages can be used for this chipset? Is it safe to just nick the table from a phone that already has this chip & an overclocked kernel? I have pasted the table from the 8x50 in case it is any help.
Code:
struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 19200, CCTL(CLK_TCXO, 1), SRC_RAW, 0, 0, 1050 },
{ 128000, CCTL(CLK_TCXO, 1), SRC_AXI, 0, 0, 1050 },
{ 245000, CCTL(CLK_MODEM_PLL, 1), SRC_RAW, 0, 0, 1050 },
{ 256000, CCTL(CLK_GLOBAL_PLL, 3), SRC_RAW, 0, 0, 1050 },
{ 384000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0A, 0, 1050 },
{ 422400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0B, 0, 1050 },
{ 460800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0C, 0, 1050 },
{ 499200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0D, 0, 1075 },
{ 537600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0E, 0, 1100 },
{ 576000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0F, 0, 1100 },
{ 614400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x10, 0, 1125 },
{ 652800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x11, 0, 1150 },
{ 691200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x12, 0, 1175 },
{ 729600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x13, 0, 1200 },
{ 768000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x14, 0, 1200 },
{ 806400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x15, 0, 1225 },
{ 844800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x16, 0, 1250 },
{ 883200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x17, 0, 1275 },
{ 921600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x18, 0, 1275 },
{ 960000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x19, 0, 1275 },
{ 998400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1A, 0, 1275 },
{ 0 },
};
Edit: I looked in the config and it looks like it's setup to use the 7x30 scropion chip which is very strange, but the cpu table does reveal some interesting info:
Code:
/* Use negative numbers for sources that can't be enabled/disabled */
#define SRC_LPXO (-2)
#define SRC_AXI (-1)
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 24576, SRC_LPXO, 0, 0, 30720, 1000, VDD_RAW(1000) },
{ 61440, PLL_3, 5, 11, 61440, 1000, VDD_RAW(1000) },
{ 122880, PLL_3, 5, 5, 61440, 1000, VDD_RAW(1000) },
{ 184320, PLL_3, 5, 4, 61440, 1000, VDD_RAW(1000) },
{ MAX_AXI_KHZ, SRC_AXI, 1, 0, 61440, 1000, VDD_RAW(1000) },
{ 245760, PLL_3, 5, 2, 61440, 1000, VDD_RAW(1000) },
{ 368640, PLL_3, 5, 1, 122800, 1050, VDD_RAW(1050) },
{ 768000, PLL_1, 2, 0, 153600, 1100, VDD_RAW(1100) },
#ifndef CONFIG_ACPUCLOCK_LIMIT_768MHZ
/* ACPU >= 806.4MHz requires MSMC1 @ 1.2V. Voting for
* AXI @ 192MHz accomplishes this implicitly. 806.4MHz
* is updated to 1024MHz at runtime for QSD8x55. */
{ 806400, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
#endif
{ 0 }
};
Anyone know where this would be updated at runtime?

I hate bumping my own thread, but I am really tearing my hair out over this one, does no one know?

You have any luck on this one?

According to specs it has a 1GHz cpu so it cannot use the freq table that only goes to 800MHz. So it has to be the first one.
Looks similar to the Desire freq table to try this one.
Code:
struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 19200, CCTL(CLK_TCXO, 1), SRC_RAW, 0, 0, 1050 },
{ 128000, CCTL(CLK_TCXO, 1), SRC_AXI, 0, 0, 1050 },
{ 245000, CCTL(CLK_MODEM_PLL, 1), SRC_RAW, 0, 0, 1050 },
{ 256000, CCTL(CLK_GLOBAL_PLL, 3), SRC_RAW, 0, 0, 1050 },
{ 384000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0A, 0, 1050 },
{ 422400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0B, 0, 1050 },
{ 460800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0C, 0, 1050 },
{ 499200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0D, 0, 1075 },
{ 537600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0E, 0, 1100 },
{ 576000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0F, 0, 1100 },
{ 614400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x10, 0, 1125 },
{ 652800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x11, 0, 1150 },
{ 691200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x12, 0, 1175 },
{ 729600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x13, 0, 1200 },
{ 768000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x14, 0, 1200 },
{ 806400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x15, 0, 1225 },
{ 844800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x16, 0, 1250 },
{ 883200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x17, 0, 1275 },
{ 921600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x18, 0, 1275 },
{ 960000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x19, 0, 1275 },
{ 998400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1A, 0, 1275 },
{ 1036800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1B, 0, 1275 },
{ 1075200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1C, 0, 1275 },
{ 1113600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1D, 0, 1275 },
{ 0 },
};
Here's some inspiration: https://github.com/thalamus/kernel/blob/2.6.35.14-bravo/arch/arm/mach-msm/acpuclock-qsd8x50.c

[KERNEL][Sep18]-=UNITY V9=-[2.6.35.14][OC/UV][CIFS/TUN][SLQB][NOOP][2WCR]

{
"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"
}
Features:
Based on Official GB kernel source code from HTC
Patched to .14
2-way call records - https://market.android.com/details?id=com.skvalex.callrecorder
OC up to 2016MHz (Default 245 - 1075MHz @ Ondemand)
VDD sysfs interface
Tweaked Interactive governor
Additional Virtuous/SmartAss/SavagedZen/Scary governors
Audio Boosts (20%)
CIFS
TUN
CFS
SLQB
NOOP I/O scheduler
TINY PREEMPT RCU
Full EXT4 Support
and more...
Click to expand...
Click to collapse
Compatible with:
All Sense ROM's based on Android 2.3.4 - 2.3.5 >
Click to expand...
Click to collapse
Issues:
- you tell me
Click to expand...
Click to collapse
Install:
- Flash via CWM
Click to expand...
Click to collapse
Download UNITY V9:
http://www.multiupload.com/VPFKEN5RAM
For correct work 2wcr function use CallRecorder app https://market.android.com/details?id=com.skvalex.callrecorder
Click to expand...
Click to collapse
Enjoy
Click to expand...
Click to collapse
More info & GPL:
Virtuous Home: http://www.virtuousrom.com
Virtuous Forum: http://forums.virtuousrom.com/index.php
HTC: http://www.htc.com/
Kernel GIT: https://github.com/mdeejay/msm7x30-gb-kernel
Thanks: Markinus (for teach), avs234 & skvalex (for 2WCR), Flemmard, seo and other Virtuous team, LordClockaN, LeeDroid, etc

Changelog:
Code:
UNITY V9:
- OC up to 2.0GHz
- Tweak all governors
- New Virtuous governor
- XZ compressing
- PREEMPT_TINY_RCU
- lots minor fixes & tweaks
UNITY V8:
- Fixed VDD
- OC up to 1804MHz
UNITY V7:
- Added VDD sysfs interface
UNITY V6:
- Enabled AMR format support for CallRecorder
- Fixed support apps like "Voice Commander"
UNITY V5:
- Fixed USB for Android 2.3.4
- "Fast USB charging" hack
UNITY V4:
- Added new module for 2wcr
---- Fixed hardware amr recordings
---- Fixed stereo recordings
---- Fixed missing call recordings
- Added SavagedZen governor
- Added Scary governor
- Some minor cleanups
UNITY V3:
- New OC method with 50 steps
- New acpu table
- Fixed kernel info
- Some cleanups
UNITY V2:
- Reverted new audio drivers
- Added 2WCR patch for new audio drivers
- Added Wi-Fi Calling support for T-Mobile users (Kineto GAN)
- Disabled BFQ / Enabled Deadline
- Disabled btrfs & ext2 support
UNITY V1:
- Added support HTC Desire Z & HTC My Touch 4G
- Tweaked video drivers
- CIFS/TUN/UTF set as modules
[SIZE="2"]v.23:
- Back to old video drivers (from official HTC source)
- ACPU edits
v.22:
- Improved SmartAss works with >=1600Mhz
v.21:
- new acpu table
- tweaked governors
- some cleanups
- max OC 1708MHz
v.20:
- not released
v.19:
- Updated video drivers from CodeAurora
- Added BFQ v.2-r1
- Tweak SmartAss (XBOCT)
- Increase GPU & Camera memory allocation (Lee)
- Disable write cache support
- Correct LCD panel size
- Added 1612MHz to acpu table
v.18:
- Added 2 steps in acpu table
- New universal updater script for both filesystems
- Prevent memory leak on hotplug
v.17:
- Added 2-way call records
v.16:
- Based on official GB kernel source code from HTC
- Enabled OC (1516MHz MAX)
- Removed 2-way call records patch
- Added Smartass governor
- Added interactive governor
- Added Conservative governor
- Added audio boost
- Added default V(R) I/O Scheduler
- Added default SLQB Memory allocator[/SIZE]
ACPU Table:
Code:
{ 122000, PLL_3, 5, 2, 61440, 875, VDD_RAW(875) },
{ 245000, PLL_3, 5, 1, 192000, 875, VDD_RAW(875) },
{ 307200, PLL_3, 5, 1, 192000, 900, VDD_RAW(900) },
{ 384000, PLL_1, 2, 0, 192000, 900, VDD_RAW(900) },
{ 460800, PLL_3, 5, 1, 192000, 925, VDD_RAW(925) },
{ 537600, PLL_2, 3, 0, 192000, 950, VDD_RAW(950) },
{ 614400, PLL_2, 3, 0, 192000, 950, VDD_RAW(950) },
{ 691200, PLL_2, 3, 0, 192000, 975, VDD_RAW(975) },
{ 768000, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 844800, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 921600, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 998400, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 1075200, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 1152000, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1228800, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
{ 1305600, PLL_2, 3, 0, 192000, 1125, VDD_RAW(1125) },
{ 1382400, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1150) },
{ 1459200, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1536000, PLL_2, 3, 0, 192000, 1275, VDD_RAW(1275) },
{ 1612800, PLL_2, 3, 0, 199680, 1325, VDD_RAW(1325) },
{ 1689600, PLL_2, 3, 0, 199680, 1375, VDD_RAW(1375) },
{ 1766400, PLL_2, 3, 0, 199680, 1425, VDD_RAW(1425) },
{ 1843200, PLL_2, 3, 0, 199680, 1450, VDD_RAW(1450) },
{ 1920000, PLL_2, 3, 0, 199680, 1475, VDD_RAW(1475) },
{ 1996800, PLL_2, 3, 0, 199680, 1500, VDD_RAW(1500) },
{ 2016000, PLL_2, 3, 0, 201600, 1500, VDD_RAW(1500) },

Beta versions:
Code:
Download:

Woow!
It's uv? Which governator??
Can you give us more details?
Thanks!
Sent from future

NICE!!
So you succeded!!
Congrats!!

Is this the first costume kernel for a gingerbread Desire HD? If so, can it be flashed to another 2.3.3 ROM (Capy's rom)?
ALso, m-deejay, can you post the RUU which this is based on.

Well I don't believe it. Well done good sir. Well done!

That's really nice News!!

Oh! Great news. U did that. U proved your self as MDJ once again. Thank you!
Just download, trying it now. Report u back!
I feel its better to do a nand back up first
Sent from my Desire HD

may be some issues in kernel. need more tests

Has the source been released then? I thought this wasn't possible until HTC released the gingerbread source?
Well done anyway. I used your kernals and roms when I had my HD2 so will give this a go.

dowlinr said:
Has the source been released then? I thought this wasn't possible until HTC released the gingerbread source?
Well done anyway. I used your kernals and roms when I had my HD2 so will give this a go.
Click to expand...
Click to collapse
HTC Incredible S source

The first 2.3.3 sense cusomize kernel!Thanks for the great work...Hopefully it can have improve the battery life..

m-deejay said:
Changelog:
Code:
v.1:
- Initial Release
Click to expand...
Click to collapse
Thank you so much, been waiting for this all day
Sent from my Desire HD using Tapatalk

And you get the bragging rights of having the first custom kernel for 2.3 sense.
Sense kernels, Sense ROM's, CM ROM's, is there anything you can't do? Got yourself a fan for life here.

work with coredroid thanks 5.4

man, you are awsome
6 stars
it works with Spike_M's DS port v1

to all
please test all functions of your phone with kernel

m-deejay said:
to all
please test all functions of your phone with kernel
Click to expand...
Click to collapse
Just flashed on CoreDroid5.4
Seems everything working. Quadrant score was 1950 @ 1401mhz with interactive governor and 1810 with performance. Confused..!
Feels good so far..
Edit: Bluetooth isn't working properly. Not detecting my SE Bluetooth stereo headset, even its already paired. Hope u can check this. No issues with WiFi
Sorry to say, need to look at Mobile data too.
Sent from my Desire HD

There seems to be a problem playing video...from the gallery and also YouTube.
I was checking YT and a few videos i`d taken earlier and they worked before flashing the kernel.
Running CD 5.4

[SCRIPT][Tool] Flashable Daemon Settings MIN/MAX Wake/Sleep Freqs

I will post here CWM Flashable Freq,s for the new Daemon OC .
It will only work on these ROMS so far:
1. Virtuos Unity ROM
2. Android Revolution 5.1.10 and higher
3. TB Fusion3D
DOWNLOADS
Buzz Kernels
DaemonSet_BuzzOC+_1612_384_230.zip
DaemonSet_BuzzOCUV_1228_384_230.zip
DaemonSet_BuzzOCUV_1075_384_230.zip
DaemonSet_BuzzOCUV_768_384_230.zip battery saver
DaemonSet_BuzzOC+_1305_384_230.zip
DaemonSet_BuzzOC+_1536_460_230.zip
DaemonSet_Buzz_ARHD_Stock_1228_691_230.zip
DaemonSet_Buzz_ARHD_Stock_998_537_230.zip
DaemonSet_Buzz_ARHD_Stock_1228_460_230.zip
DaemonSet_BuzzOC+_1075_460_230.zip
DaemonSet_BuzzOC+_1536_537_230.zip
DaemonSet_BuzzOC+_1459_460_230.zip
RCMIX_ARHD_ED 1.3_CIFS_TUN_NLS_EXT4 Used in Android Revolution HD , HONEY3D , Etc
DaemonSet_RCMIX_ARHD_ED_768_384_122.zip battery saver
DaemonSet_RCMIX_ARHD_ED_998_384_122.zip
DaemonSet_RCMIX_ARHD_ED_1152_384_122 Used in Android Revolution HD
DaemonSet_RCMIX_ARHD_ED_1228_384_122.zip
DaemonSet_RCMIX_ARHD_ED_1305_384_230
DaemonSet_RCMIX_ARHD_ED_1459_384_122.zip
DaemonSet_RCMIX_ARHD_ED_1612_384_122.zip
DaemonSet_RCMIX_ARHD_ED_1843_384_122.zip
DaemonSet_RCMIX_ARHD_ED_1382_384_122.zip
New ARHD Settings. Min Sleep
DaemonSet_RCMIX_ARHD_ED_768_384_230
DaemonSet_RCMIX_ARHD_ED_998_384_230
DaemonSet_RCMIX_ARHD_ED_1152_384_230
DaemonSet_RCMIX_ARHD_ED_1228_384_230
DaemonSet_RCMIX_ARHD_ED_1305_384_230
DaemonSet_RCMIX_ARHD_ED_1382_384_230
DaemonSet_RCMIX_ARHD_ED_1459_384_230
DaemonSet_RCMIX_ARHD_ED_1612_384_230
MDJ Unity V4 DHD and Incredible S compatible
DaemonSet_MDJ_Unity_1708_368_245.zip
DaemonSet_MDJ_Unity_1401_368_245.zip
DaemonSet_MDJ_Unity_1017_368_245.zip
DaemonSet_MDJ_Unity_1113_368_245.zip
DaemonSet_MDJ_Unity_1286_368_245.zip
DaemonSet_MDJ_Unity_1516_768_245.zip
DaemonSet_MDJ_Unity_1708_768_245.zip
DaemonSet_MDJ_Unity_806_368_245.zip battery saver
Leedroid Kernels
DaemonSet_Leedroid_1497_499_254.zip
DaemonSet_Leedroid_1344_499_245.zip
DaemonSet_Leedroid_1651_499_254.zip
DaemonSet_Leedroid_1113_499_245.zip
DaemonSet_Leedroid_1267_499_245.zip
DaemonSet_Leedroid_1804_499_254.zip
DaemonSet_Leedroid_729_499_245.zip battery saver
Be Aware : Flash Kernel and Flash Daemonset in CWM the same time !!
Flash Kernel
Flash DaemonSet
Reboot !!
Don,t forget to remove SetCPU ,No-frills or other cpu scaling apps !!
Click to expand...
Click to collapse
If video is not working on Android Revolution,, use this fix
Fix_for_other_kernels.zip
preacher65 said:
You can use Notepad++ to edit the files, or any editor that works with Linux or Unix text files. Notepad2 is good as well, it's small and fast.
http://notepad-plus-plus.org/
http://www.flos-freeware.ch/notepad2.html
Normal Windows Notepad doesn't work correctly - the "end of line" code for a Linux text file is different to the one for a Windows text file, so standard Notepad messes up the formatting.
Click to expand...
Click to collapse
or on DHD you can use ES FileExplore in r/w hiApk mode
if you have sugestions,, or requests,, i will try to customize it
Also new kernels.. keep me posted
Thanks Apache14/Bumble_Bee, MDJ/m-deejay and LeeDroid for the kernels,, i just provide daemon table,s for it.
If I forgot someone.. please pm me.
Also special thanks to Patrics83 and Mike1986 for supporting me.
And thanks for the guys from Unity/rmk.
The Daemon they made is just awsome
Links:
Introduction to the new Overclocking Daemon
http://forum.xda-developers.com/showpost.php?p=14529333&postcount=5
all credits and thanks to Diamondback2010/rmk
Mike1986
http://forum.xda-developers.com/showpost.php?p=14638641&postcount=34279
Click to expand...
Click to collapse

Freq Table
Buzz (1.22 GHz) for HTC Desire HD / Inspire 4G
| 230400 | 307200 | 384000 | 460800 | 537600 | 614400 | 691200 | 768000 | 844800 | 921600 | 998400 | 1075200 | 1152000 | 1228800 |
Buzz OC+ kernel (1.61 GHz) for HTC Desire HD / Inspire 4G
| 230400 | 307200 | 384000 | 460800 | 537600 | 614400 | 691200 | 768000 | 844800 | 921600 | 998400 | 1075200 | 1152000 | 1228800 | 1305600 | 1382400 | 1459200 | 1536000 |
1612800 |
Code:
{ 230400, PLL_3, 5, 1, 192000, 900, VDD_RAW(900) },
{ 307200, PLL_3, 5, 1, 192000, 900, VDD_RAW(900) },
{ 384000, PLL_1, 2, 0, 192000, 925, VDD_RAW(925) },
{ 460800, PLL_3, 5, 1, 192000, 950, VDD_RAW(950) },
{ 537600, PLL_2, 3, 0, 192000, 975, VDD_RAW(975) },
{ 614400, PLL_2, 3, 0, 192000, 975, VDD_RAW(975) },
{ 691200, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 768000, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 844800, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 921600, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 998400, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 1075200, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1152000, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1228800, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
OC+
{ 1305600, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1175) },
{ 1382400, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1459200, PLL_2, 3, 0, 192000, 1225, VDD_RAW(1225) },
{ 1536000, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1300) },
{ 1612800, PLL_2, 3, 0, 192000, 1350, VDD_RAW(1350) },
UNITY_V4_2.6.35.13_OC1708_UV900_SLQB_CIFS_TUN_VR_EXT4_2WCR
Code:
{ 245760, PLL_3, 5, 2, 61440, 1000, VDD_RAW(900) },
{ 368640, PLL_3, 5, 1, 122800, 1000, VDD_RAW(950) },
{ 768000, PLL_1, 2, 0, 153600, 1025, VDD_RAW(1000) },
{ 806400, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 825600, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 844800, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 864000, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 883200, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 902400, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 921600, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 940800, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 960000, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 979200, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 998400, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 1017600, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1036800, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1056000, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1075200, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1094400, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1113600, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1132800, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1152000, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1171200, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
{ 1190400, PLL_2, 3, 0, 192000, 1125, VDD_RAW(1125) },
{ 1209600, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1150) },
{ 1228800, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1150) },
{ 1248000, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1150) },
{ 1267200, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1150) },
{ 1286400, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1175) },
{ 1305600, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1175) },
{ 1324800, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1175) },
{ 1344000, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1175) },
{ 1363200, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1382400, PLL_2, 3, 0, 192000, 1225, VDD_RAW(1225) },
{ 1401600, PLL_2, 3, 0, 192000, 1250, VDD_RAW(1250) },
{ 1420800, PLL_2, 3, 0, 192000, 1250, VDD_RAW(1250) },
{ 1440000, PLL_2, 3, 0, 192000, 1250, VDD_RAW(1250) },
{ 1459200, PLL_2, 3, 0, 192000, 1250, VDD_RAW(1250) },
{ 1478400, PLL_2, 3, 0, 192000, 1275, VDD_RAW(1275) },
{ 1497600, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1300) },
{ 1516800, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1300) },
{ 1536000, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1300) },
{ 1555200, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1325) },
{ 1574400, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1325) },
{ 1593600, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1350) },
{ 1612800, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1350) },
{ 1632000, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1350) },
{ 1651200, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1350) },
{ 1670400, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1375) },
{ 1689600, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1375) },
{ 1708800, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1400) },
LeeDrOiD-Ace-GB-V3.2.0-KERNEL-2.6.35.13-CFS
LeeDrOiD-Ace-GB-V3.2.0-KERNEL-2.6.35.13-BFS
| 245000 | 422400 | 499200 | 576000 | 652800 | 729600 | 806400 | 883200 | 960000 | 1036800 | 1113600 | 1190400 | 1267200 | 1344000 | 1420800 | 1497600 | 1574400 | 1651200 | 1728000 | 1804800 |
Code:
{ 245000, 900, VDD_RAW(900) }, ------ | ----- { 245760, 1000, VDD_RAW(1000) },
{ 422400, 925, VDD_RAW(925) }, ------ | ----- { 368640, 1050, VDD_RAW(1050) },
{ 499200, 950, VDD_RAW(950) },
{ 576000, 975, VDD_RAW(975) },
{ 652800, 1000, VDD_RAW(1000) },
{ 729600, 1000, VDD_RAW(1050) },
{ 806400, 1025, VDD_RAW(1050) }, ---- | ----- { 806400, 1100, VDD_RAW(1100) },
{ 883200, 1050, VDD_RAW(1075) },
{ 960000, 1050, VDD_RAW(1075) },
{ 1036800, 1075, VDD_RAW(1125) }, ---- | ---- { 1024600, 1200, VDD_RAW(1200) },
{ 1113600, 1100, VDD_RAW(1125) },
{ 1190400, 1125, VDD_RAW(1150) },
RCMIX_ARHD_ED_1.3_OC_1.6_CIFS_TUN_NLS_EXT4
Code:
{ 122000, PLL_3, 5, 2, 61440, 875, VDD_RAW(875) },
{ 230400, PLL_3, 5, 1, 192000, 900, VDD_RAW(900) },
{ 307200, PLL_3, 5, 1, 192000, 900, VDD_RAW(900) },
{ 384000, PLL_1, 2, 0, 192000, 925, VDD_RAW(925) },
{ 460800, PLL_3, 5, 1, 192000, 950, VDD_RAW(950) },
{ 537600, PLL_2, 3, 0, 192000, 975, VDD_RAW(975) },
{ 614400, PLL_2, 3, 0, 192000, 975, VDD_RAW(975) },
{ 691200, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 768000, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 844800, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 921600, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 998400, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 1075200, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1152000, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1228800, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1100) },
{ 1305600, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1175) },
{ 1382400, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1459200, PLL_2, 3, 0, 192000, 1225, VDD_RAW(1225) },
{ 1536000, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1300) },
{ 1612800, PLL_2, 3, 0, 192000, 1350, VDD_RAW(1350) },
{ 1689600, PLL_2, 3, 0, 192000, 1400, VDD_RAW(1400) },
{ 1766400, PLL_2, 3, 0, 192000, 1425, VDD_RAW(1425) },
{ 1843200, PLL_2, 3, 0, 192000, 1450, VDD_RAW(1450) },
{ 1920000, PLL_2, 3, 0, 192000, 1475, VDD_RAW(1475) },

nice idea whisky, cheers

Hi!
How about for Lees Kernel?
Its the only1 I can get over 1.5ghz with stable
I get 1.8 daily runer with it.

OMG! You are working fast mate!
This is a GREAT thing to have if you want to change kernel or CPU tables

Very good idea for such tables.

del

Thanks so much mr Whiskey
Eagerly awaiting the release of 5.1.10

Will this daemon work on every rom? Or it is only for Unity?

anko184 said:
Will this daemon work on every rom? Or it is only for Unity?
Click to expand...
Click to collapse
Only for Unity and Android Revolution HD atm

mike1986. said:
Only for Unity and Android Revolution HD atm
Click to expand...
Click to collapse
It will work on the New incoming Android_Revolution_HD 5.1.10
Sent from my Desire HD using Smoke Signals, Morse Code and Pigeon Post.

Thanks for this Whiskey103
Which do you think is going to be the best kernel for the upcoming 5.1.10 of ARHD?

This has great potential but the way that the daemon changes settings is troublesome, I mean if you have to reboot everytime you change frequency or another setting you eliminate the battery improvements. Rebooting is a battery drainer, I will wait until this gets a GUI or change settings on the fly.

Can I ask sorry what this is please in Lehman's terms
Sent from my HTC Desire HD using XDA App

Spyr0s said:
This has great potential but the way that the daemon changes settings is troublesome, I mean if you have to reboot everytime you change frequency or another setting you eliminate the battery improvements. Rebooting is a battery drainer, I will wait until this gets a GUI or change settings on the fly.
Click to expand...
Click to collapse
No disrespect man, but how often do you change frequencies to call reboot battery drainer? You set it one time, and you are good to go. Cheers mate

Spyr0s said:
This has great potential but the way that the daemon changes settings is troublesome, I mean if you have to reboot everytime you change frequency or another setting you eliminate the battery improvements. Rebooting is a battery drainer, I will wait until this gets a GUI or change settings on the fly.
Click to expand...
Click to collapse
Yeah,, but for now,, it needs a reboot. I don,t think a GUI will change that btw.
And ofcourse,, you only need to set it one time..

Spyr0s said:
This has great potential but the way that the daemon changes settings is troublesome, I mean if you have to reboot everytime you change frequency or another setting you eliminate the battery improvements. Rebooting is a battery drainer, I will wait until this gets a GUI or change settings on the fly.
Click to expand...
Click to collapse
But why would you want to change frequencies that often? Frequencies are change by governor, the only thing you can change is min and max value. Once set I see no point in changing it very often...

What if you want to run a benchmark? What if you set the overclocking too high and your CPU can't handle it? You will stuck into an unbootable phone until you flash another setting. What about charging, low battery etc profiles

Spyr0s said:
What if you want to run a benchmark? What if you set the overclocking too high and your CPU can't handle it? You will stuck into an unbootable phone until you flash another setting. What about charging, low battery etc profiles
Click to expand...
Click to collapse
Well, you have your right but what I think is:
1. First of all - if you don't want to use O/C Daemon then just install SetCPU and O/C Daemon will be deactivated.
2. How many times a day a regular user do benchmarks?
3. Our tests proved that new O/C Daemon can handle much higher O/C then previous method with SetCPU. F.g. with SetCPU one of our devices was unstable on 1.6 GHz while with new O/C Daemon it's very stable with 1.6 GHz.
4. Yes, you can't use profiles like "charging" but as I said in point nr 1 - you can install SetCPU if you prefer it for some reasons.
So basically new O/C Daemon is not stripping any previous functionality. You can still use SetCPU if you want. It just gives extra possibility for users searching for better performance and those who don't want control CPU manually.

Whiskey, just a quick one. Is this deamon for the new one MDJ+ Unity V1?

[Kernel] Neok AceDroid V1.1 OC/UV/2012-Feb-06 | Amazing Smooth, Super Battery

This kernel is base on LeeDroid Kernel source
Neok AceDroid Kernel for Sense ROMS
Amazing Smooth Working!!! and Amazing battery efficiency
Changelog
- CFS Kernel
- Add TINY_PREEMPT_RCU
- Add RCU Booster
- Apply RCU Optimization
- Add SIO I/O Scheduler with SIO tweak
- 2.6.36 kernel Ondemand CPU Governor
- Add SmartasV2 CPU Governor
- Apply Smooth and higher battery efficiency tweak for SmartasV2
- Optimize CPU Clock table
- CFS tweak
- Disabled Sched-GENTLE_FAIR_SLEEPERS
- Apply AXI (Good for battery)
- improve SDHC card stability
- Compiled by Linaro GCC4.5.4 (2011.08)
- Apply compile optimze FLAG
- Update MSM3.0 kernel's Wlan driver by LorDClockaN
Changlog as 1.0 to 1.1 Version
- Remove popping noise sound by LorDClockaN
- Fix CPUFreq table fix
- min CPUFreq change 122 -> 230
- Fixed ext4 disk write performance regression
- Add genlock and msm related changes by LorDClokaN
- msm: cpufreq: Improve initial frequency selection - CodeAurora
- change compile optimization flag
Default kernel cpu setting
CPU Governor - SmartassV2
Max clock -1036Mhz
Min clock -230Mhz
Compile optimze FLAG
-mtune=cortex-a8 -march=armv7-a -mfpu=neon -mfloat-abi=hard \
-fsingle-precision-constant -ftree-vectorize -funswitch-loops \
-fforce-addr -fprofile-correction -falign-loops \
-fpredictive-commoning -fgcse-after-reload -pipe
Kernel CPU Clock table
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 24576, SRC_LPXO, 0, 0, 30720, 900, VDD_RAW(900) },
{ 61440, PLL_3, 5, 11, 61440, 900, VDD_RAW(900) },
{ 122880, PLL_3, 5, 5, 61440, 900, VDD_RAW(900) },
{ 184320, PLL_3, 5, 4, 61440, 900, VDD_RAW(900) },
{ MAX_AXI_KHZ, SRC_AXI, 1, 0, 61440, 900, VDD_RAW(900) },
{ 122000, PLL_3, 5, 2, 61440, 875, VDD_RAW(875) },
{ 230400, PLL_3, 5, 1, 192000, 900, VDD_RAW(900) },
{ 307200, PLL_3, 5, 1, 192000, 900, VDD_RAW(900) },
{ 422400, PLL_3, 5, 1, 192000, 925, VDD_RAW(925) },
{ 499200, PLL_1, 2, 0, 192000, 950, VDD_RAW(950) },
{ 652800, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 729600, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 806400, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 883200, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 960000, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 998400, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 1036800, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1113600, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
{ 1190400, PLL_2, 3, 0, 192000, 1125, VDD_RAW(1125) },
{ 1267200, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1150) },
{ 1344000, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1175) },
{ 1420800, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1497600, PLL_2, 3, 0, 192000, 1275, VDD_RAW(1275) },
{ 1536000, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1300) },
{ 1612800, PLL_2, 3, 0, 192000, 1350, VDD_RAW(1350) },
{ 1689600, PLL_2, 3, 0, 192000, 1375, VDD_RAW(1375) },
{ 1766400, PLL_2, 3, 0, 192000, 1425, VDD_RAW(1425) },
{ 1843200, PLL_2, 3, 0, 192000, 1450, VDD_RAW(1450) },
Kernel Source - https://github.com/kgp700/
Thanks to LeeDroid and LorD ClockaN

Is this for Sense Rom?

Yes, its for sense roms
Sent from my Desire HD using XDA App

inzaghi75 said:
Is this for Sense Rom?
Click to expand...
Click to collapse
yes for sense roms

kgp700 said:
yes for sense roms
Click to expand...
Click to collapse
will try this beast

Has it uv? Is the Best to use daemon or setcpu?
Inviato dal mio Desire HD usando Tapatalk

Currently running the v1.0 on the ER3BUSXL3.5 and it's pretty smooth working till now. Thanks for the work

USB D/C
What about USB D/C when the top bar is pulled down or WiFi is on/off operated?

Just flash on ER3BUSXL3.6
Ty

devilrex said:
Just flash on ER3BUSXL3.6
Ty
Click to expand...
Click to collapse
Very helpful post. This means two things:
1) Kernel is sense designed (which Op already stated);
2) You learned how to flash a kernel.

whiperhack said:
Very helpful post. This means two things:
1) Kernel is sense designed (which Op already stated);
2) You learned how to flash a kernel.
Click to expand...
Click to collapse
And you learned how to write a post

thanks for your new kernel .good work ...
Hum with smartassV2 my phone freez with 1.5GHz lol but with lord or rcmix kernel i can put 1.7GHz or 1.68GHz in Ondemand

hi!
hello kernel another kernel dev!
looking at your changelog all I can say it's the same as mine sense kernel but with little less features

mattiadj said:
Has it uv? Is the Best to use daemon or setcpu?
Inviato dal mio Desire HD usando Tapatalk
Click to expand...
Click to collapse
yes it support undervolt
i like setcpu
unhallowedone said:
Currently running the v1.0 on the ER3BUSXL3.5 and it's pretty smooth working till now. Thanks for the work
Click to expand...
Click to collapse
thanks
whiperhack said:
What about USB D/C when the top bar is pulled down or WiFi is on/off operated?
Click to expand...
Click to collapse
no problem
devilrex said:
Just flash on ER3BUSXL3.6
Ty
Click to expand...
Click to collapse
thanks

kgp700 said:
Strongly Recommand Wipe dalvik cache after kernel update!!!
Click to expand...
Click to collapse
In fact, dalvik cache has nothing to do with kernel, so wiping it isn't really necessary

brolee93 said:
thanks for your new kernel .good work ...
Hum with smartassV2 my phone freez with 1.5GHz lol but with lord or rcmix kernel i can put 1.7GHz or 1.68GHz in Ondemand
Click to expand...
Click to collapse
i'm tested about that
no problem on 1.5Ghz, SmartassV2
But have freeze on 1.6Ghz or higher clock with smartassv2
no problem on 1.7Ghz, ondemand governor
if you want use high cpu clock, i recommand ondemand governor
but not recommand high cpu overclock
LorD ClockaN said:
hi!
hello kernel another kernel dev!
looking at your changelog all I can say it's the same as mine sense kernel but with little less features
Click to expand...
Click to collapse
hi
thanks for reply
and thanks kernel source
yes less features than your kernel
i need some study for kernel
if you possible,
use my kernel, then please assessment about my kernel
(sorry my bad english)
sigurd_LU said:
In fact, dalvik cache has nothing to do with kernel, so wiping it isn't really necessary
Click to expand...
Click to collapse
ok thanks

ths guy，
i try the kernel，
and found there is A little noise when play music。

As latest RCMiX kernel there is a little background noise after any sound...

framir said:
As latest RCMiX kernel there is a little background noise after any sound...
Click to expand...
Click to collapse
+1
yes，all kernel have noise except LorDmoD kernel。

abaochen said:
+1
yes，all kernel have noise except LorDmoD kernel。
Click to expand...
Click to collapse
Please remove this fastidious noise!

Database Info

welcome