yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] show-p1984:
you may want to edit the cpufreq.c section in that patch to this:

diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index e4a1842..57d28c8 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -681,6 +681,68 @@ static ssize_t show_bios_limit(struct cpufreq_policy *policy, char *buf)
return sprintf(buf, "%u\n", policy->cpuinfo.max_freq);
}

+#ifdef CONFIG_CPU_VOLTAGE_TABLE
+
+extern ssize_t acpuclk_get_vdd_levels_str(char *buf);
+extern void acpuclk_set_vdd(unsigned acpu_khz, int vdd);
+
+static ssize_t show_vdd_levels(struct kobject *a, struct attribute *b, char *buf) {
+	return acpuclk_get_vdd_levels_str(buf);
+}
+
+static ssize_t store_vdd_levels(struct kobject *a, struct attribute *b, const char *buf, size_t count) {
+
+	int i = 0, j;
+	int pair[2] = { 0, 0 };
+	int sign = 0;
+
+	if (count < 1)
+	return 0;
+
+	if (buf[0] == '-') {
+	sign = -1;
+	i++;
+	}
+	else if (buf[0] == '+') {
+	sign = 1;
+	i++;
+	}
+
+	for (j = 0; i < count; i++) {
+
+	char c = buf[i];
+
+	if ((c >= '0') && (c <= '9')) {
+	pair[j] *= 10;
+	pair[j] += (c - '0');
+	}
+	else if ((c == ' ') || (c == '\t')) {
+	if (pair[j] != 0) {
+	j++;
+
+	if ((sign != 0) || (j > 1))
+	break;
+	}
+	}
+	else
+	break;
+	}
+
+	if (sign != 0) {
+	if (pair[0] > 0)
+	acpuclk_set_vdd(0, sign * pair[0]);
+	}
+	else {
+	if ((pair[0] > 0) && (pair[1] > 0))
+	acpuclk_set_vdd((unsigned)pair[0], pair[1]);
+	else
+	return -EINVAL;
+	}
+	return count;
+}
+
+#endif	/* CONFIG_CPU_VOLTAGE_TABLE */
+
cpufreq_freq_attr_ro_perm(cpuinfo_cur_freq, 0400);
cpufreq_freq_attr_ro(cpuinfo_min_freq);
cpufreq_freq_attr_ro(cpuinfo_max_freq);
@@ -696,6 +758,10 @@ cpufreq_freq_attr_rw(scaling_max_freq);
cpufreq_freq_attr_rw(scaling_governor);
cpufreq_freq_attr_rw(scaling_setspeed);

+#ifdef CONFIG_CPU_VOLTAGE_TABLE
+define_one_global_rw(vdd_levels);
+#endif
+
static struct attribute *default_attrs[] = {
&cpuinfo_min_freq.attr,
&cpuinfo_max_freq.attr,
@@ -711,6 +777,18 @@ static struct attribute *default_attrs[] = {
NULL
};

+#ifdef CONFIG_CPU_VOLTAGE_TABLE
+static struct attribute *vddtbl_attrs[] = {
+	&vdd_levels.attr,
+	NULL
+};
+
+static struct attribute_group vddtbl_attr_group = {
+	.attrs = vddtbl_attrs,
+	.name = "vdd_table",
+};
+#endif	/* CONFIG_CPU_VOLTAGE_TABLE */
+
struct kobject *cpufreq_global_kobject;
EXPORT_SYMBOL(cpufreq_global_kobject);

@@ -2028,7 +2106,7 @@ EXPORT_SYMBOL_GPL(cpufreq_unregister_driver);

static int __init cpufreq_core_init(void)
{
-	int cpu;
+	int cpu, rc;

for_each_possible_cpu(cpu) {
per_cpu(cpufreq_policy_cpu, cpu) = -1;
@@ -2039,6 +2117,10 @@ static int __init cpufreq_core_init(void)
&cpu_sysdev_class.kset.kobj);
BUG_ON(!cpufreq_global_kobject);

+#ifdef CONFIG_CPU_VOLTAGE_TABLE
+ rc = sysfs_create_group(cpufreq_global_kobject, &vddtbl_attr_group);
+#else
+ rc = 0;
+#endif	/* CONFIG_CPU_VOLTAGE_TABLE */
+
return 0;
}
core_initcall(cpufreq_core_init);

This avoids a unused Variable warning when compiled without CONFIG_CPU_VOLTAGE_TABLE or it wouldn't make not much sense to include a choice, since most of the devs treat warnings as errors.

Just wanted to leave my two cents here ;)
[HTC Sensation] GabrielSousa:
GREAT APP !!!!

download the source and compiled.

the voltage dont change anything
[HTC Sensation] Romanbb:
Thanks, I'll have another look at it later tonight
[HTC Sensation] GabrielSousa:
ops.... i need glasses, the voltage prefs, works ;)
[HTC Sensation] zimphishmonger:
Yup, however, currently the CPU clock only limits cpu0, CPU1 still can clock to max. Roman's working on it ;)
[HTC Sensation] GabrielSousa:
i think is a kernel problem,

in faux123 and Bricked-Kernel, neither setcpu neither cpumaster, neither system tuner can clock cpu1 :(
[HTC Sensation] zimphishmonger:
No its not, none of those apps listed (except system tuner, he's working on it) has been updated for a true async dual core chip, which is why it can't properly clock the second core. Romannbb is working on an all to modify Voltage and clock speed for both cores. Bug the devs of those apps to update based on fauxs latest findings regarding our cpu, it's entirely different than previously used methods of oc/uv

If u want an example, I have both cores limited to 1.29ghz and it sticks using virtuous oc daemon. Cpu never steps above that ;) working like a charm
[HTC Sensation] BrokenWall:
I have not had issues with CPU1 clocking and holding proper min/max clocks in v010 or v012, im currently on cm7 using v012 so.

I have done plenty of testing on this...

I have just double checked it on my end with the CM7 kernel and I guess somewhere in the updates the clocks stopped holding true. I know for sure this was not an issue with v006
[HTC Sensation] faux123:
I will look into this tonight... ugh.. so tired from work :(
[HTC Sensation] zimphishmonger:
I think my post was misunderstood. setcpu , cpumaster, nofrill don't properly clock Cpu1 but it is possible cause it works (keeps cpu1 max clocking at what I want) using virtuous daemon. I am using v13 1.5ghz version atm.

Thanks for ur hard work and research, faux! It's a shame the snapdragon isn't adequately documented for developers
[HTC Sensation] Lucky Thirteen:
Logcat bootloop

Hi Folks!

First of all thanks for your hard work to provide us a such wonderful and promising piece of software!

I did once in a while have random crashes followed by infinite bootloops with my Sensation (details of ROM & Kernel versions in the provided screenshots). If you guys want some logcat of this issue, I can provide them. I did collect one when the phone tried to reboot.

I did follow attentively the instructions when I flash a new ROM. I did use TB to backup my apps, but I never restore data, only apps. I always SuperWipe when things go wrong before re-installing a clean ROM.

I would be glad if I can contribute to help you understand, if not, well I'll understand ! :D

Long live to you!

Cheers!
[HTC Sensation] 3c:
Actually you can use System Tuner, it copes with CPU1 pretty well and can also use or disable the OC/deamon for you! :D It has been deved/tested on Faux v0.1.4 actually.

12.5mV steps works out ok, just look at the voltage table, you'll see 12.5mV differences in some original frequencies.
[HTC Sensation] GabrielSousa:
what i'm saying is.

with faux123 1.7ghz and if you clock to 1.5.

only cpu0 goes to 1.5ghz, cpu1 stays on 1.7

i tried all cpu managers and virtuous daemon too.

this happens on Bricked too.
[HTC Sensation] show-p1984:
echo 1 > /sys/devices/system/cpu/cpu1/online

echo 1782000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

then look if it is overclocked, which it should be now, at least if you use bricked .55 ;)

That should stick until the next reboot.

It's not a kernel, it's an app issue ;)

The app can't oc a cpu thats offline (which it will be with aSMP systems), so the cpu1 will not get overclocked.
[HTC Sensation] 3c:
If I may add a little to the discussion...

On non-aSMP kernels (SMP?) setting CPU0 will automatically set CPU1 the same way, probably because they're symetrical... I remember a dev bulding a kernel to get the same feature, which made it easy for everyone and was also more intuitive!

Next update System Tuner will actually put CPU1 online before setting it's OC settings, then back to its previous state!

Ah! definitely an app issue anyway!
[HTC Sensation] show-p1984:
Was that a hidden feature wish?
[HTC Sensation] GabrielSousa:
it works,

now we all know is app thing,

lets wait for the new version, to clock the cpu1 right ;)
[HTC Sensation] 3c:
Obviously not everyone knows that... hence the question above.

Anyway, if you want to clock CPU1 right, you can still force CPU1 online all the time, it will be clocked fine, even on boot.

My bad, it was the fact that CPU1 was not retaining its settings after going offline...
[HTC Sensation] zimphishmonger:
Exactly, that seems the be the remaining issue
[HTC Sensation] 3c:
No really remaining, I said it was an issue, as in 'it used to be a problem, not anymore'...

Both tested 0.1.4 and now Briicked-Kernel 0.5.5, not any issue as far as I can tell.

Just checked again to be certain, looks very much ok now. Or am I too tired already? :D
[HTC Sensation] zimphishmonger:
Ill update\retest ur app after work and see how it works on CPU1.. I know Roman was having issues controlling CPU1 in his app as well,
[HTC Sensation] lemassykoi:
same problem here, twice : one time yesterday and one time today. The only thing I can do is to pull out battery. After that, it's OK.

My ROM is Bulletproof 0.9, with kernel 0.1.2 1,56 sync L2

going to flash new kernel 0.1.4 1.56 sync L2
[HTC Sensation] zimphishmonger:
Are you doing ANY uving or OCing (besides what's stock in the kernel)? If so, your chip might not be able to handle it.
[HTC Sensation] Masrawy:
@Faux123

I wonder if it's possible to make the next kernel with the same libs as v0.1.0? It was the only version of kernel I didn't had issues with games like Cordy and Fruit Ninja I believe

Also, why there's 2 versions of the kernel? why isn't it possible to have 1.78ghz with L2 sync?

thanks!
[HTC Sensation] faux123:
The new baseline is 2.3.4 which is NOT compatible with the older libs from 0.1.0. HTC broke their GL/FrameBuffer code in their 2.3.4 release. I am still looking for the fix for it (no guarantee that I would find it).

The L2 cache is slower than CPU and more difficult to run at the same speed as the CPU (think of desktop PCs, same situation). Memory architecture still a bit behind the CPU innovations. L2 start to become unstable beyond 1.566 GHz, so not possible to run synchronous to CPU @ 1.782 GHz.
[HTC Sensation] Masrawy:
thanks for your precise answers! and good job BTW, your kernel rocks!
[HTC Sensation] jlevy73:
Been testing 0.1.5 with the new Stock Beats Rom and it's been pretty smooth. The Faux Clock app is not working properly with the test kernel. It's all over the place relative to what adb says. Linpack and CF-Benches are very low compared to 0.1.4. Linpack scored a lofty 10.115 :)
[HTC Sensation] zimphishmonger:
Been testing v15. Lower cf bench score but minor gfx glitches on some widgets i had occasionally haven't reoccurred. Ui responsiveness is still very smooth, even at 1.08ghz. Fantastic battery life, I think I see some improvement but I need more time to test for accuracy
[HTC Sensation] omar302:
Would anyone please share the link for v0.1.5?

I couldn't find it on XDA or on the other forum.
[HTC Sensation] GabrielSousa:
where is version 0.1.5 ?
[HTC Sensation] LittleH79:
Faux, could you help me with sth plz??

Why o why is version 0.1.0 perfectly smooth for me and all native 2.3.4 kernels (0.1.2 and up) are all giving me big time stuttering?

I'm really lost here :(

Already flashed 1.45 RUU so started from scratch but result stays the same..
[HTC Sensation] faux123:
010 was based on 2.3.3 where as all later versions were based on official 2.3.4 source from HTC. HTC broke something for 2.3.4 and introduced a few bugs along the way.
[HTC Sensation] zimphishmonger:
Sorry, I cant..... Im sure Faux will release soon
[HTC Sensation] jlevy73:
Battery life is exactly the same for me as 0.1.4 was. IMHO I still think 0.1.3 is the best kernel thus far. I started noticing excessive cpu heating with 0.1.4 which carried to 0.1.5. Graphics also felt a bit smoother on 0.1.3 then on 0.1.5 on games like asphalt6, heavy gunner3d, etc.
[HTC Sensation] i900frenchaddict:
I also think 0.1.3 was above 0.1.4

I've beeb trying ARHD 3.5.0XE with the 0.1.5 kernel, and indeed, CF bench scores were low and overall 3D performances and games were less fast.

Wondering if it was the ROM or the Kernel, I flashed v 0.1.3, then 0.1.0 (my favourite one for gaming :p ) and I got again very good CFbench scores, and I think the fastest 3D scenes in Quadrant I've ever seen, even if the final score is under what I have with 0.1.3

Faux123, is it the 0.1.5 kernel that is not completly ready in his definitive version, or is it simply less fast for 3D, or could it be the association with Android Revolution HD 3.5.0 that leads to low 3D performances?
[HTC Sensation] faux123:
015 was a beta version, I didn't intend to release it, but now Mike already included in his ROM so I will release it later after work. 015 has many framebuffer patches and enhancements I modified from CAF. It was an attempt to fix the graphic glitches seen in games such as Cordy and Ninja Jump but as a bonus, it also added more bug fixes and enhancements that the released HTC kernel did not include. I will continue to apply enhancements, bug fixes from CAF from time to time. 015 pretty much has all them all.

Oh, 1 more thing, Check your PM ;)
[HTC Sensation] Whiskey103:
Hai Mate,, released it in the betaROM,, not xda edition. ;)

Still not published.. your work, your release :)

ow,, and it seems to runs smooth,, thanks for it :)
[HTC Sensation] i900frenchaddict:
right, not released, that's true, we knew it was a beta thing

I've just flashed what I got in my inbox, trying right now, will edit !

EDIT: so far, it's indeed better than 0.1.5 It remains slower than 0.1.0 at same speed, but it seems than when it...hmmm..."scales up" (meaning speed increases sometimes quite suddenly after a few milliseconds slower), it goes as fast as 0.1.3

I think I should do a full wipe, I've flashed too much tonight to be sure of my results (falshed ARHD then at least 6 of your kernels ^^)

Thanks for your work, I'll continue testing everything you release for sure!
[HTC Sensation] jlevy73:
V0.1.6 is better than 015 but I'm still getting some gpu lag especially in certain games. It's pretty noticeable in heavygunner3d where earlier versions of the kernel resulted in smooth play. As an aside, benchmarks are still all over the place. CF-Bench is very low. Neither setcpu, faux clock, oc deamon play nice with this kernel. Will keep testing
[HTC Sensation] vabeach454:
Any more Kernal testing needed, count me in. I have been Flashing faux123 kernals since the start MT4G. I have always thought they were the best and if you ever noticed his is the most Kernal in everyone else's ROM's. ;)
[HTC Sensation] faux123:
I have nearly opposite of your experience. Very strange indeed.
[HTC Sensation] jlevy73:
Yes it is, hmm.
[HTC Sensation] zimphishmonger:
v16 is a lot smoother than v15, in terms of responsiveness. Benchmarks are all over the place as well. No issues w/ slowdown in 3d games. OC Daemon does work for me, although it seems sorta finicky. I did have one kernel panic earlier, which in turn corrupted my boot animation file (I dont know WTF happened, I just managed to track it down via logcat errors).
[HTC Sensation] 3c:
Hello Faux123,

Tested the last beta you sent, no particular issues for me, didn't noticed much differences either, sorry. I'm an average user most of the time, no particular 3D games, just phone usage, a few simple games and app testing.

Anyway, I've recently moved to Lee's ROM+Kernel, and noticed the thermals are now managed by the kernel, no more thermald, and it just works great!

So, any chance of getting the following in the next kernel:

- Integrated thermal management

- CPU temperature in sysfs (value is obviously available, so it shouldn't be so hard)

- Standard UV table, including default values as with all other implementations we can find on XDA?

Sorry I keep asking those, it will allow me to provide a better user-experience in my app, though I'm sure it will benefit other apps and your users too.

Do you have the thermald source code by any-chance, maybe I can use it to read CPU temp somehow? I'm sure it must already be available somewhere, somehow?
[HTC Sensation] i900frenchaddict:
After some more testing, I have to agree with what is said above. Faux123, when you look at the 3D scenes of quadrant, the one with the planet, haven't you seen fps starting at 38 or 40, then suddenly go to 60 and remain at 60?

It seems it happens in some games too, kind of a latency, it starts slow then speed increases, like if the GPU (or CPU itself?) was waiting to scale up (Zelda Ocarina of time on N64oid shows this "unconsistancy")

Benchmarks are better than using 0.1.5, not as stunning as with 0.1.3, but most of the time I run my bench at 1.78ghz so I can't be really objective here.
[HTC Sensation] faux123:
Yeah this is due to gpu scaling. In any scaling governor design there would have this slight latency. On one hand, the scaler saves more battery, when gpu is not used but as you mentioned added some latency.

So for you hard core gaming fans would you like to see a constant clock instead at cost of battery life or live with some slight lag at the start but with better battery life?
[HTC Sensation] zhang yixi:
```

hi man..i like your kernel very much..and i want test it..where is the 0.16?:rolleyes::rolleyes:
[HTC Sensation] mike1986.:
I appreciate your work and I really never saw such good kernels developer :)

And I believe developer can buy another developer beer as well ;)

1EP07711HT020683R
[HTC Sensation] BigBoppa:
It would be nice if we can select it by romans fauxclock for example...:)
[HTC Sensation] faux123:
http://twitter.com/#!/faux123/status/114740667544117249 ;) Enjoy!
[HTC Sensation] miniterror:
1.6 extreme edition running fine on my coredroid 2.5 rc2.

Extreme edition is like mega undervolted right?
[HTC Sensation] i900frenchaddict:
Well, it depends on the time it takes you, you're already doing a huge work!

there's an extreme edition (I'm currently downloading it!!!), why not a "gamer edition" with constant clock, the flair of 0.1.0 with the fixes of 0.1.6 would be a gamer dream of course, but once more, only if you have time :)

EDIT: when you mean constant clock, you mean for the GPU, right? ^^
[HTC Sensation] zimphishmonger:
Althugh Im not a Hardcore gamer, IO felt I should weigh in. I cant see an issue w/ a slight GPU latency, as once it clocks up, it should stay up, correct? Once your playing a 3d game, it should keep the GPU scaling consistent (w/ consistent performance to match), but I dont see a reason to disable GPU scaling at the cost of battery.
[HTC Sensation] affliction_emrah:
Very nice move imo:)
[HTC Sensation] faux123:
Kernel 016 has a camera crash bug. I am at work right now, I will fix it tonight when I get home. Meanwhile use 014 if you need cameras.
[HTC Sensation] i900frenchaddict:
On some (rare, that's for sure!) or on emulators, it is as if the GPU clocks up because the scene is hard to render (example: a landscape in Zelda Ocarina of time), then your character turns toward a wall, so less power is required, then turns to the landscape again, and here it there can be kind of a latency.

But really, it's for rare games, 99% of games run perfectly with the kernels we've had since 0.1.0, maybe a little slower on 0.1.4 and mainly 0.1.5, very good for 1.1.3. This experience and opinion may greatly vary, depending on the games you play I guess,and you're right, no way battery life should be exchanged for a constant clock, it concerns too few users like me :p

The few ones using the extreme 1.7ghz kernel I guess lol

Maybe, as clocking at 1.7ghz is completly useless for daily use, and is only for hardcore gamers or benchmark addicts, this particular version could be made even more extreme with a constant GPU clock, I mean, using 1.7ghz kills the battery anyway ^^

Just my two cents, as I'm already more than happy using Faux123 kernels !
[HTC Sensation] khakiman:
This kernel is sick! !
[HTC Sensation] khakiman:
Actually this version broke game loft games for me cab anyone verify this fir me
[HTC Sensation] faux123:
Fixed 2 derps :p
[HTC Sensation] NYCguy2020:
Thanks.downloading now.

EDIT:Which version is recommended for power users??!
[HTC Sensation] faux123:
Extreme edition if you phone can run it.
[HTC Sensation] NYCguy2020:
Thanks for the quick response.will test and report back.
[HTC Sensation] anbinhv:
Hi faux, You should fix this guide in the 1st Post:

"echo 1 > /sys/devices/system/cpu/cpu1/online"

:D
[HTC Sensation] faux123:
ooops copy and paste error, thanks :o
[HTC Sensation] jerrylzy:
Hi,faux! Does your 0.1.7 kernel include JHash 3,gpu scalling and wifi_pm=fast?Thanks!
[HTC Sensation] anbinhv:
I use the method in the first post to undervolt and underclock (xbroadermod with your cm7 kernel)

When I reboot, all values back to default.(I used rootexplorer to check)
[HTC Sensation] v11lemans:
Governor

Hi Faux

i am using your kernel with InsetCoin 2.2.5 SSE and it is working perfectly.

I have only one question about the default governor.

Even if it is not reccomended i have used the CPU master only to check which governor is used by default and the only one present is ondemand and performance while my understanding is that the smartassv2 should be the default.

Is that correct or i have misunderstood something?

Thanks
[HTC Sensation] B-Man2005:
1.echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

2.echo 1188000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

3.echo 1 > /sys/devices/system/cpu/cpu1/online

4.echo 192000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

5.echo 1188000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

hi i want to set the default min freq to 384000 ... works with command 1

do i need to set min clock freq for cpu1 too ??

the 4th command didnt work ? :(
[HTC Sensation] meteor999:
I completely agree, battery life is the most important, I think most people would agree, except maybe the few hardcore gamers.

I having been using this kernal for a long time now, and battery life has always been good for me with the right settings in OC D, hopefully it will remain this way.

Keep up the great work Faux!!
[HTC Sensation] immunityx:
Is. 17 coming to cm7 kernal?
[HTC Sensation] khakiman:
Thanks .17 fixed games (chain fire drivers are not compatible
[HTC Sensation] atticus182:
04D40545TG481623T

Enjoy your cup of coffee! You really deserve it, your kernel is awesome!
[HTC Sensation] aaronpoweruser:
Faux i know your super busy bout would you consider making a evo 3d cdma kernal we are lacking kernal devs at the moment, from what i understand the basses aren't that different as they are both 8x60, carnayb uses a universal bass and builds for all devices from there maybe you could do a diff to make it easy
[HTC Sensation] Whiskey103:
4RJ78383KU218352X enjoy mate, and thanks for your great work !
[HTC Sensation] jlevy73:
Yes, yes, hardcore gaming edition would be much appreciated. It's a long flight from LA to China ;)
[HTC Sensation] jlevy73:
Version 17 is smoother than a baby's bottom
[HTC Sensation] i900frenchaddict:
Faux123, I know it's not related to your kernel, but if you have a hint....I've been looking for a workaround for 2 days, with B-man, but we have a big problem:

We use Android Revolution HD with your (so great!) kernels

Since Mike made its new 3.5.X (so 3.5.0, 3.5.1 and the fresh 3.5.2) base, whatever the kernel, I can't get good performances at all. I've tried many of your kernels, with super wipe and fresh ROM install, no backup to be sure: v 0.1.3, 0.1.6 0.1.7 and even 0.1.0

Only 0.1.0 could give me "reasonnable" performances, not as good as with previous ROM builds, but at least 7000 overall at CF-bench at 1.7ghz.

Even with 1.1.7 kernel at 1.7ghz, with or without Faux Clock, my scores are low (as low as 5400 CF benc or 42 Linpack), my 3D games lag, even some 2D openGL games can lag sometimes :eek:

I've seen that CPU1 tends not to stay online even when it's supposed to be really stressed.

Also, I have same performances at 1.3 or 1.7 ghz, best performances seem to be at 1.5ghz

I've tried many fixes, nothing works. B-man tried a lot of things too, same results as me.

If you have any idea of what in the new ROM base can prevent you kernel to work as it should, I would be really happy (or I'll have to revert back to an older rom to see the real potential of your 1.1.7 kernel! I haven't seen it yet )
[HTC Sensation] ajay83:
Thanks Faux for a great kernal.

Just wondered, could some one tell me which app is recommeded to use to downclock cpu speed to 1.62Ghz from the 1.78Ghz please

Im hearing : Cpu master/Set CPU/System Tuner/ Faux clock by Romann?

Thanks guys =)