yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] hrkfdn:
Wow, that is quite some testing you've done there :)

Why do the results bother you, though? Please remember that most of the patches are supposed to improve responsibility. Some might not make a difference at all in some cases. Also NEVER FORGET that benchmarks are not comparable to a real user experience. I, myself, am quite happy with the UI snappiness and battery performance.

I will probably readd the 120MHz then due to popular request :) After all, everyone is welcome to turn it off..
[Desire HD Android Development] McKebapp:
w00t?

no, the test don't bother me at all.

The opposite is the truth; I'm quite exited.

Barely no difference between both kernels at 245MHz and 368MHz.

460Mhz - 768Mhz aren't that comparable, but there is a nice intermediate speed at 768Mhz on your Kernel (maybe you can flush 576Mhz, as it isn't working well).

And on 806Mhz: Holy ****! That is a >20% advantage. :eek:

But, to be honest, I'm not sure if everything is right there.

I'm sure I did some failures in measurement.

I guess, wiping the caches wasn't a good idea.

With Buzz 1.1.4. I'm on >54MFlops again, after a few hours of running it.

I guess, I should re benchmark each Kernel after a day of usage, when both caches are build again.

On the other Hand: Why is there no performance gain beyond 806Mhz on sour Kernel? 1200Mhz is a plus of barley 50%, compared to 806Mhz. It _has_ to be noticeable at all.

I'll rerun my benchmarks on the weekend, incl. Linpack and Quadrant.

My conclusion atm.:

The Buzz Kernel is faster, due to the defective, higher performing, 460Mhz Step on Buzz and the (maybe) defective, lower performing, speed steps beyond 806Mhz on your Kernel.

I'm pretty sure your Kernel will get the fastest CM7 Kernel around, once these things are fixed.

And in average view: If speeds lie 1.51 Ghz and 100Mhz steps till 2.0Ghz would be added, it will blast everything from the road...

Just two, small negative things atm:

- The battery drain is still higher on your Kernel. Could you please post a voltage@frequency table, that is used on your Kernel?

- The UI is a little less snappy. I'm not sure if its, the missing average performance or som kind of glitch. Like slower frequency switching or something. In my subjective kind of view, Buzz feels a little "lighter". Mustn't be the truth; just saying :) .

Is there anything We / I can do?

I really appreciate your work.

Atm this is the only CM7 Kernel in development and I feel this can get something very big!
[Desire HD Android Development] hrkfdn:
Alright well, here is the current CPU/Voltage table: https://github.com/hrkfdn/linux-htc-ace/blob/master/arch/arm/mach-msm/acpuclock-7x30.c

If you have improvements, shoot! :)
[Desire HD Android Development] McKebapp:
Holy... :eek:

I barley get half of the stuff written there....

But I guess this is what I've searched:

{ 245760, PLL_3, 5, 2, 61440, 900, VDD_RAW(900) },
{ 368640, PLL_3, 5, 1, 122800, 900, VDD_RAW(900) },
{ 576000, PLL_3, 5, 1, 192000, 975, VDD_RAW(975) },
{ 768000, PLL_1, 2, 0, 153600, 1025, VDD_RAW(1025) },
{ 806400, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 960000, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 1024000, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1075) },
{ 1200000, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },

Afaik, this is apache14s, from his latest Sense Build:

{ 245000, PLL_3, 5, 2, 122500, 900, VDD_RAW(900) },
{ 422400, PLL_3, 5, 1, 192000, 925, VDD_RAW(925) },
{ 460800, PLL_3, 5, 1, 192000, 950, VDD_RAW(950) },
{ 499200, PLL_1, 2, 0, 192000, 950, VDD_RAW(950) },
{ 537600, PLL_3, 5, 1, 192000, 975, VDD_RAW(975) },
{ 576000, PLL_3, 5, 1, 192000, 975, VDD_RAW(975) },
{ 614400, PLL_2, 3, 0, 192000, 975, VDD_RAW(975) },
{ 652800, PLL_2, 3, 0, 192000, 1000, VDD_RAW(975) },
{ 691200, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 729600, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 768000, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 806400, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 844800, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 883200, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 921600, 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(1050) },
{ 1075200, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1050) },
{ 1113600, PLL_2, 3, 0, 192000, 1075, VDD_RAW(1050) },
{ 1152000, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1075) },
{ 1190400, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1075) },
{ 1228800, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
{ 1267200, PLL_2, 3, 0, 192000, 1125, VDD_RAW(1125) },
{ 1305600, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1175) },
{ 1344000, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1175) },
{ 1382400, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1420800, PLL_2, 3, 0, 192000, 1225, VDD_RAW(1225) },
{ 1459200, PLL_2, 3, 0, 192000, 1225, VDD_RAW(1225) },
{ 1497600, PLL_2, 3, 0, 192000, 1250, VDD_RAW(1250) },
{ 1516800, PLL_2, 3, 0, 192000, 1250, VDD_RAW(1250) },

According to that tables, your Voltage is similar.

So it must be the missing Smartass Governor and the missing Speeds...

Is there a chance to put his https://github.com/BuzzBumbleBee/htc-kernel-ace/blob/master/arch/arm/mach-msm/acpuclock-7x30.c to your kernel?

Just for beta testing / benchmarking on my phone?

Or do they not match?
[Desire HD Android Development] hrkfdn:
Governor really shouldn't make a difference for benchmarking. If you set it to performance, it'll use the max speed all the time. I could copy the table and PM you a zImage, if that's okay with you.
[Desire HD Android Development] McKebapp:
Oh pardon, I was talking about the energy savings, when I mentioned smartass.

Yeah, I'm really looking forward for that zImage.

I'll write a long conclusion on Sunday, when I tested/benched the Kernel :)
[Desire HD Android Development] Rey-619:
please make an new release with it :> because its a tiny little bit more UVed than yours...

BTW: i asked before... what about HAVS on the Desire HD?
[Desire HD Android Development] hrkfdn:
alright, someone please test this build. it uses the latest buzzz voltages and frequencies up to 1.2GHz.
[Desire HD Android Development] igor.tonky:
whoops, 1190400/interactive froze the phone :)

no, wait, it's not the frequency, setcpu main menu seem to be freezing my phone, interesting.

yeah, it just hangs randomly after boot and setcpu start. what info(logcat?) can help you debug this?
[Desire HD Android Development] McKebapp:
Downloading right now.

What did you change exactly?

Did you copy the file and removed the frequencies >1.2Ghz?

Or did you overwrite your voltages?

Or..?
[Desire HD Android Development] hrkfdn:
i don't think that's a kernel issue.

try this in adb shell:

rm /data/data/com.mhuang.overclocking/shared_prefs/setcpu.xml

it's now using the whole buzz voltages and frequencies. i replaced the tables.
[Desire HD Android Development] McKebapp:
Already saw that.

No freezes over here, everything fine.

40,5mflops average @ 1.22Ghz.

11mA at idle (2G, WiFi on).

The dozens of frequencies look and feel very good.

Phones GUI is as snappy as Buzz 1.1.4 is.

I guess it will gain a little speed within the next hours.

I hoped you'd keep the higher frequencies as well, so that I'd could have made a 1-vs-1 Bechmarathon like yesterday. ;)

Very good one so far :-)
[Desire HD Android Development] McKebapp:
Sorry for the double post. I didn't like to edit my last post for a fifth time :-D

Something is wrong, like in the b31 release.

From 245Mhz - 576Mhz I'm reaching common mflops from 11mflops - 17.5mflops.

And from 652Mhz - 1228Mhz EACH score is at 40,5mflops average.

This can't be correct... :(
[Desire HD Android Development] hrkfdn:
i see. what about this one?
[Desire HD Android Development] McKebapp:
Still stuck at a max of 1.22Ghz :p .

1,22Ghz = 46mflops average

1,03Ghz = 41mflops av.

0,80Ghz = 34mflops av.

0,61Ghz = 27mflops av.

0,46Ghz = 17mflops av.

0,25Ghz = 12mflops av.

Scaling seems to be fine, now. :D
[Desire HD Android Development] zantekk:
1GHz would be enough for me :D

I just want you to add smartass gov pls because it doesn't need sreen-off profile.

:)

Would be nice if you could do this^^ ;)
[Desire HD Android Development] MrYuiM:
This all interests me, so I'm now installing linux, reading how to compile the kernel and looking through the files :) Might attempt adding the 1.5 Ghz to this kernel and testing it out. Would anyone have a guide or something on how to add smartass? Just for learning purposes, I'm in no way intending to take over your development hrkfdn :)

Ok, I've given up :/ So confusing. gaaah
[Desire HD Android Development] hrkfdn:
Well that was a rather quick adventure. Either way, do what you want with it. It's open-source after all :)
[Desire HD Android Development] McKebapp:
Just a little statement regarding latest Testkernel.

I've gained about 10% battery lifetime.

According to the PowerTime Widget, my "lifetime" is now at 30hrs, coming from 27hrs :-)
[Desire HD Android Development] MrYuiM:
Haha, I've decided to persevere after finding an ultra noob friendly guide :) I'm just a copy paste sorta guy :/ So ima just start with the frequency tables, then look around for stuff like smartass and others, then I'll just try and comprehend the code :) I have next to no knowledge of coding but I understand it by sight fairly easily :D Any progress made will be reported back :)

Ok. So far, I'm downloading the google source, kernel sources and everything. Ima open every single file in the Buzz Kernel Source, look for text that says smartass as I think that for the governor to be displayer in SetCPU you have to have the name for it and what it does, I think. Then Ima do the OC tables and test out 1.5 Ghz on your kernel, post some benchmarks, test for a week or two, if its stable then I'll upload it somewhere and PM you and leave you to do your magic :D But maaaaaan, this source is taking an age to download!
[Desire HD Android Development] igor.tonky:
okay, this is what i'm running for some time, seems to work fine to me :)

i removed two frequencies and undervolted everything else. my phone can't go lower than these voltages, though.

for the interested - i attached the kernel.

if system hangs on you:

1. reinsert the battery

2. plug phone into computer, it autoboots into recovery

3. do steps 2-4 below, but with #31 zImage file.

how to try it:

1. make sure you have your kernel backed up(or have #31 around)

2. download zImage.7z and unpack it

2. adb reboot bootloader

3. fastboot flash zimage zImage

4. fastboot reboot

@hrkfdn: would be nice if you could remove the minimum of 900, maybe our phones would handle, like, 850 on lower frequencies?

static struct cpufreq_frequency_table freq_table[] = {
{ 0, 122880 },
{ 1, 245760 },
{ 2, 368640 },
{ 3, 768000 },
{ 4, 806400 },
{ 6, 1024000 },
{ 7, 1228800 },
{ 8, CPUFREQ_TABLE_END },
};

/* 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, 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) },
{ 245760, PLL_3, 5, 2, 61440, 900, VDD_RAW(900) },
{ 368640, PLL_3, 5, 1, 122800, 900, VDD_RAW(900) },
{ 768000, PLL_1, 2, 0, 153600, 925, VDD_RAW(925) },
{ 806400, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 1024000, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 1228800, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 0 }
};
[Desire HD Android Development] McKebapp:
Sweet. but this is based on Kernel #26 .

Could you do that too, to the latest TestKernel?

Maybe incl. accidentally adding some OC frequencies? :D
[Desire HD Android Development] Rey-619:
sry for the question:

is an version for miui in progress? i want to use it in my Rom, because, since testbuild 2 it is realy nice in overhaul performance and battery life!
[Desire HD Android Development] hrkfdn:
try pulling the latest git tree and see whether it applies voltages below 900.

yes, i've messed around with it a bit. could you please try this build? i'm trying to make a hybrid kernel working on miui and cm6/cm7. would be cool if you could test both..
[Desire HD Android Development] Rey-619:
thx!! testing it in a few moments :)

is the voltage table from testbuild 2 integrated? ore only the commits of b31?
[Desire HD Android Development] hrkfdn:
It comes with the voltages of the second testbuild. :)
[Desire HD Android Development] Rey-619:
your my man!!! :)
[Desire HD Android Development] Rey-619:
sry for double posting... :)

wifi works now with miui!! Yeah man!! ^^
[Desire HD Android Development] hrkfdn:
It's a pretty messy fix. Can anyone confirm whether the MIUI build also works on CM6 and CM7? I'm not at home at the moment.
[Desire HD Android Development] McKebapp:
Works fine on CM7 - pnk-crispy duck. :)

I'm ready for low voltages and OC (I'll keep being enduring on this :D :p )
[Desire HD Android Development] Rey-619:
Mounting SD does not work on miui,

but i will test it on another PC, could be a problem of this machine here.
[Desire HD Android Development] Rey-619:
sry for my dobble posting again but i have news:

Miui kernel:

- mounting sd does not work

- data connection and mobile network dissapears when screen gets locked <<<<< !!!!

- battery consuption is higher than with the normal kernel (18-24mA on Standby), but acceptable

sry but for the moment i have to switch back ;)

looking forward to see more builds!
[Desire HD Android Development] McKebapp:
Does the "USB-Connection" Button simply not show in the upper bar?

Maybe you are able to mount it with the App "Dual Mount SD".

Had that "issue" with apache14s Buzz Kernel, too

Maybe just the screen-off rule?
[Desire HD Android Development] McKebapp:
I've benched the latest Testkernel.

Holy Sh**, that was a lot of frequencies.... :D

Here we go:

http://goo.gl/dzJbx

Some frequencies seem to be broken/useless again.

Overall Performance gained a little, due to the vast number of faster, and one cheating, frequencies. :)

Single speed dropped sometimes a little... :(

But I'll keep it due to loyalty issues :D
[Desire HD Android Development] MrYuiM:
I've just about given hope :( I'm using Linux in VirtualBox as wifi wasn't working when I installed it into a partition, but adb isn't recognized and nothing works properly :(
[Desire HD Android Development] hrkfdn:
Alright guys. Build 38:

BUILD 38:
- Readd 122MHz @ 850mV
- Improve voltages/frequencies
- Minor bugfixes
- Fix USB tethering
- Preliminary support for CM6/MIUI
[Desire HD Android Development] philask:
Looks good so far!
[Desire HD Android Development] Rey-619:
About mounting, im not sure at the moment.

Screen off were disabled at this time.

I try the new build and give feedback later
[Desire HD Android Development] starbase64:
Hi,

here is build 38 as exe file: ace-2.6.32.21-ck2-hrkfdn-b38.exe

with friendly greet

starbase64
[Desire HD Android Development] Frustu:
Works on cyanogenmod 6.1.3?
[Desire HD Android Development] Rey-619:
Test with b38 MIUI:

- sd mounting is still not working / showing no new device in device manager

- still loosing data and network connection when locking screen :/ / unusable sry

- battery life seems ok
[Desire HD Android Development] phunkycow:
While using the kernel, do this:

1. Download http://postkreative.eu/libhtc_ril.so

Connect your phone to your computer (just plug the usb cable, NO usb mounting) and do:

adb remount
adb push libhtc_ril.so /system/lib/
adb reboot

Tell us if you're still losing connection after locking the phone.

Edit: make sure you backup the original libhtc_ril.so first though (but you can find it in the miui zip @ system/lib folder anyway if something goes wrong.
[Desire HD Android Development] Rey-619:
i pushed the file before i instaled the kernel, because is cant use adb ore sd mounting with it ^^

data works now :) thank you very much!!

testing now usb again (deinstalling drivers and installing them and such things xD)

[EDIT] PC does not recognize my device (i deinstalled all drivers and plugged in)

Also: i have some little wakeup issue it takes sometimes 2 ore 3 seconds till wake up on 245 min/max powersave
[Desire HD Android Development] zantekk:
What does currentwidget show in stand-by on cm7 with build #38 ?
[Desire HD Android Development] McKebapp:
The lowest value I saw, yet, was 14mA (2G, WiFi on, screen-off).

Here is the latest Benching:

http://goo.gl/j8Fh9

My I'm missing something around 25mflops as intermediate step. :confused:

What do you guys think about the frequency steps?

Kind Regards,

McK
[Desire HD Android Development] Rey-619:
thx for comparing :)

i would say the frequencie steps are ok...

more steps, more calculating, more battery usage

The steps are included, are a very nice middle path.

[EDIT] i took a look again...

the step from 576Mhz (17.51mflops) up to 768Mhz (32.10mflops) seems a little bit high, could this be true?

if it is true so we could add another step between this two. 652Mhz could be the right one :)
[Desire HD Android Development] McKebapp:
Think so, too.

I'd say:

- 576Mhz can be flushed --> 368Mhz does barely the same job.

- 614Mhz would be nice again, if it's around 25mflops

- maybe 806Mhz out?

- maybe 1024Mhz out --> new entry of 1152Mhz or 1190Mhz @ approx 42 / 43 / 44 mflops

(- adding 1516, 16xx, 17xx, 18xx, 19xx and 20xx for nerds ^^)

@Henrik: Can you post the actual voltage table, please?
[Desire HD Android Development] Rey-619:
could be better, your right.
[Desire HD Android Development] hrkfdn:
Guys. Please check your SetCPU settings. The lowest I'm getting is 10mA with nothing turned off though. The 122MHz frequency has been undervolted to 850mV. Should definitely make a difference.

Current table is, as always, here:

https://github.com/hrkfdn/linux-htc-ace/blob/master/arch/arm/mach-msm/acpuclock-7x30.c

I was having stability problems with the voltages of the test build. My phone would crash sometimes. Unacceptable! I prefer stability over anything..

About MIUI. I'd say it's going to prove rather difficult, if the interfaces are that different.

The results @ 1228MHz in the benchmarks just prove once again that bigger fluctuations can be possible..
[Desire HD Android Development] igor.tonky:
btw, i'm runing 122880/750, and 245000/750 ^_^

strangely enough - i can't undervolt anything over 960000 on the latest kernel sources.

i'll see the usage today and post observation(maybe along with modified kernel) tomorrow.
[Desire HD Android Development] McKebapp:
Different ROM, Radio, Apps, Sync Services and so on = Different Standby.

So nothing uncommon. I'm very happy with 14mA.

K, sorry I didn't remember that there is a link. My grey cells aren't working anymore that good at barley 30yrs of age :D

For sure. Unluckily you seem to have a a little more sensitive CPU.

Over here, everything was fine.

No crashes, no fc'ing; worked like a charm.

If you'd add KaMa Kernels ability to make it possible for users to set the frequencies / voltages by them self, I'd determine the best/stable/linear frequency steps from 122Mhz - 1228Mhz for you. (I guess for your CPU it'd be +50mV each step, added to my findings).

Could you please explain that a little? I didn't get it, sorry :-(
[Desire HD Android Development] hrkfdn:
Exactly!

Yea, that was kind of weird anyway. It was working from day on I made the testbuild. Then yesterday it was crashing randomly which confused me. Reflashing the stock kernel (which was all I could do because I was outside) fixed it.

Do you see the fluctuations between my builds? They might seem quite signifcant, yet no code portion related to that has been changed.
[Desire HD Android Development] McKebapp:
O.k., got it. In that case, my testing isn't transparent enough.

One thing: Since the Testbuilds I didn't flush the caches anymore. Maybe there is a speedup after the rebuilt.

Any idea how I can make my comparings more reliable?

I guess I have to flash a nude/new CM7 build + the kernel I bench each time, huh?

What would be a good base? It should also be always the same CM7 build. Maybe PNK29?

@phunkycow: What about a pure kernel-benching ROM?

Nothing that could influence the speed inside, just SetCPU an LinPack / Quadrant / AnTutu?
[Desire HD Android Development] Rey-619:
WoW that was too much information for my bad english löl

So what did you say about miui? xD

im now nearly happy with your build on miui, since phunkycow posted the right lib file :)

all I missing is usb storage

BTW again: Thanks for your creat work :)
[Desire HD Android Development] kshting:
Just flashed the latest build to CM7. Played with my phone for a few minutes before I realized I need to charge it.

Upon charging, phone screen wouldn't wake up and red LED wouldn't light up when it should before flashing the kernel. Only when I pressed the power button, the above mentioned become normal again.

Does that mean the phone is not charging until I pressed the power button? Anything to do with the 122mHz frequency?

Guys, some input would be appreciated.

Edit: Yup, with my phone screen on, I plugged the phone to the charger and it would not start charging....
[Desire HD Android Development] Walker Street:
Swype does not work with b31 and b38 (works with stock CM kernel)

I'm using CM7. I noticed that Swype did not work once I started using b31 of hrkfdn's kernel. It doesn't read the gestures (i.e. no text appears).

I flashed CM7 again (with the stock kernel). Swype worked again.

Then after b38 came out today, I tried hrkfdn's kernel again. Swype was not working again. I think Swype was working on previous hrkfdn builds (not sure which ones).

This is a massive deal-breaker for me.

I can't live without Swype .... so it's back to the stock kernel for me. :(
[Desire HD Android Development] hrkfdn:
Can't really confirm that. swype is working fine here. In fact, I'm using it right now. Shouldn't be kernel related anyway.

About the battery bug: this is due to some changes I made. Looking to fix it as we speak.
[Desire HD Android Development] McKebapp:
I can also confirm this: No Problems with Swype, SlideIT and Thickbuttons.

No Charging or connectivity (in any way) problems either.
[Desire HD Android Development] hrkfdn:
Could you please try the latest build and see if the problem persists?
[Desire HD Android Development] Rey-619:
i realised another thing on miui

i said that the device needs 2-3 sec to wake up.. sry i'm wrong

device wakes up instantly but the screen keeps dark for 2-3 sec.

this means: i can unlock the device blind xD and than the screen wakes up instantly
[Desire HD Android Development] McKebapp:
This is known before as a bug/feature of the 122Mhz frequency.

Set the min speed a little higher and the screen will come up faster.

Or leave it an live with it, like I do :D
[Desire HD Android Development] Rey-619:
i thought so too... but it makes no diffrence! I also can set it higher and have the same problem ;)

now i can unlock it blind, so its not realy a problem. I just noticed this
[Desire HD Android Development] cattleprod:
swype has a really bad bug were it will just stop swyping lol an you have select another input method, use it and then switch back to swype an it will work again.
[Desire HD Android Development] hrkfdn:
I am currently using a profile for screen-off. Minimum is 122MHz, maximum 576MHz. Governor ondemand. No screen lags anymore..
[Desire HD Android Development] zantekk:
Gonna test #41 now and will report about battery life ;)
[Desire HD Android Development] starbase64:
Hi,

here is the flasher for #41: ace-2.6.32.21-ck2-hrkfdn-b41.exe

with friendly greet

starbase64
[Desire HD Android Development] Rey-619:
@hrkfdn can you link this in the first post?
[Desire HD Android Development] hrkfdn:
Your wish is my command.
[Desire HD Android Development] vatranxxx:
hey can somebody tell me why this kernel (#41) is much slower than the stock @768mhz? :(

But it seems that this kernel improved the battery life a little...

i´m using PNKCD Rom and LauncherPro.

thxx!!