Related
For Sapphire EBI1/32A users
All credits goes to Wesgarner and the people who his works based on.. (cyanogen etc.)
Original Thread: http://forum.xda-developers.com/showthread.php?t=592466
Now, the real stuffs-
EBI1 CFS Kernel (01/01/10): Here
EBI1 BFS Kernel (02/01/10): Here
Instructions
Nandroid BACKUP!
Wipe/Clear
Install WG Build Y R1 (thread link above)
Install EBI1 Port (link above)
Boot and wait~
Enjoy, folks!
Thanks your work
downloading the rom now.....great and thanks , mate!!
arctu said:
For Sapphire EBI1/32A users
All credits goes to Wesgarner and the people who his works based on.. (cyanogen etc.)
Original Thread: http://forum.xda-developers.com/showthread.php?t=592466
Now, the real stuffs-
EBI1 CFS Kernel (01/01/10): Here
EBI1 BFS Kernel (02/01/10): Here
Instructions
Nandroid BACKUP!
Wipe/Clear
Install WG Build Y R1 (thread link above)
Install EBI1 Port (link above)
Boot and wait~
Enjoy, folks!
Click to expand...
Click to collapse
Good work man, I'll try it!!
imho, it's one of the featured smoothest rom besides CM. try it with BFS kernel.
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Thanks a lot for the hard work. Will try it out mate
no many issues so far, everything seems to work well.
arctu said:
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Click to expand...
Click to collapse
Thank you. this is just what I was looking for. I was using bcrook's CM port in earlier versions and was doing ok(only some FCs in the first boot).
and since build Y I can't user bcrook's port with app2sd and swap..maybe something to do with the new kernel.
I did post in that thread if there is a 32A port prior the release, but guess too many people are just too excited for the new release and overlooked my post..anyway
please don't discontinue it, I am sure many people will like to run WG build on their 32A Sapphire.
just wondering, I saw your other thread MAGIC Port, can we use that with ANY dream/32B ROM? and more importantly, is is stable? (I saw an big red ALPHA..)
if so, can we also use that with WG-Build?
so you can take a rest now, then?
arctu said:
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Click to expand...
Click to collapse
Thanks for porting, this rom seems sexy. Lol. Aniwae, pls continue! Since it would be great to have this rom widely used on 32A radios.
@haozheng91
MAGIC Port is stable actually.
But no, for WG Build and few other roms, even though it ports properly, it doesn't do a full port. For Cyanogen Mod, WG Build Y, Enomether etc. they use custom kernels. When you use my magic port, well, it does work, but it's not using the intended kernel which the ROM creator compiled.
But anyway, your problem was you're using CM Port over WG Build Y.. that's incorrect because of the different ramdisk (the rom init script). Hence the A2SD failed.
---
the rom is stable so far for me. i'm loving it and the smoothness.
so far, no FC. though, BFS does drain battery.
What's the difference between CFS & BFS?
multitouch
wipe
flash WG-Build Y.R1 - CFS with RAM Hack
flash wgbuildy_ebi1_signed.zip - CFS kernel
everything is going well, but multitouch doesnt work ...
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Naturally, smoother UI but drains a little more battery.
@coltcha:
CFS somehow doesn't work. Try BFS. I'll recompile the kernel once wesgarner release another version.
Does this ROM include the radio image that will brick a 32A magic?
BFS drains more battery.. that's good to know.
if Cyanogen Mod and WG Build use different kernel, then what are some ROMs we can use your magic port? Cyanogen Mod is one of the most popular ROMs there..
what about any of the Eclair ROMs?
I have heard that BFS is supposed to be a little faster..but WG recommands CFS as BFS is not as stable or something.. as for the battery, I always have to recharge everyday, so can't really tell the difference between different ROM or kernel...
hikki2000 said:
Does this ROM include the radio image that will brick a 32A magic?
Click to expand...
Click to collapse
it doesnt.
@haozheng91
like i said, it'll work on any 32B roms.
it's just not a full port for cases of roms with custom kernel. so... if you go on to the dream forums, if the ROM dev say he compiled his own kernel... you will just not benefit from the custom kernel enhancement. that's all.
though, most of the time, the custom kernel isn't much of a benefit as they're usually just variants of existing kernels with different build configs. you'll also see that most devs tend to us CM kernel... especially eugene eclair roms and some senseui roms.
arctu said:
it doesnt.
Click to expand...
Click to collapse
So it is safe for me to flash the ROM and then apply your port file, with my current SPL and Radio? Thanks.
yes. it should be. but then again, flash at your own risk, i or the rom dev aren't responsible if you brick your phone.
arctu said:
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Click to expand...
Click to collapse
No No, buddy, please keep up your good work, we are glad to see the diversities.
this is my 2.6.27 source for eclair builds of android. this has been a long time project with lots of help from some great friends. i consider this a community kernel so all are welcomed to it, to use in their builds or what not. all thats asked is for all who use it, to give credit for using this source. just as u would for using anyone elses work. thats just to be fair to those who help maintain this kernel.
thanx:
maejrep
flipz
quietblongs
phhusson
MrPippy
tmzt
bzo
and if i forgot u ill add u later
current commits:
-msm_hw3d support for Donut and Eclair builds (ported patches made by phhusson and MrPippy)
-synaptics touch driver (backported from .29)
-msm_camera (backported from .29 by maejrep)not yet working
-compcache sources
-overclocking and the ability to scale all current freqs (major thanx to phhuddson, bzo, and maejrep for all the help)
-backported ext4 support
-fixed freq tables to show correct clock speeds
-backported BFS (Brain **** Scheduler) version 316
new commits and patches are welcomed. please submit them for review.
http://github.com/toastcfh/htc-2.6.27-heroc
Enjoy
reserved
...........................................
Good job Hopefully these fixes make it into all the awesome ROMs out there (yours included)
So this is the much anticipated OpenGL and Multitouch?
I actually grabbed the source from github /jhansche/htc-2.6.27-heroc last night. Got it compiled and running and I have to say it works nicely. Loving the OpenGL, but especially the multi-touch!
You guys are awesome. Thank you for all your hard work!
PRGUY85 said:
So this is the much anticipated OpenGL and Multitouch?
Click to expand...
Click to collapse
Sure is. This is the code base that got me the highest-on-Hero-so-far 29.9fps bench on neocore that I posted a screenshot of in his thread.
Amazing work guys
damn it I really need to get a linux setup so I can compile the kernels. I WANT THIS!!!!!! AAAAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGG!
Hope this gets incorporated soon into the latest 2.0.1/2.1 AOSP ROMs...also is this compatible with Gumbo's Kernel?
PRGUY85 said:
Hope this gets incorporated soon into the latest 2.0.1/2.1 AOSP ROMs...also is this compatible with Gumbo's Kernel?
Click to expand...
Click to collapse
this is a kernel it is not a rom.
PRGUY85 said:
Hope this gets incorporated soon into the latest 2.0.1/2.1 AOSP ROMs...also is this compatible with Gumbo's Kernel?
Click to expand...
Click to collapse
i'm pretty sure that this is a kernel, so your question's a bit confusing. maybe i'm just delirious?
I know its a kernel dude....still it can get incorporated into those ROMs builds like everyone has been waiting to do so...
What I'm saying is that with this now the ROM makers can get OpenGL and Multitouch on their ROM releases, something everyone has been waiting for.
soooo who wants to be so nice as to compile this to zip so people can flash it
PRGUY85 said:
I know its a kernel dude....still it can get incorporated into those ROMs builds like everyone has been waiting to do so...
What I'm saying is that with this now the ROM makers can get OpenGL and Multitouch on their ROM releases, something everyone has been waiting for.
Click to expand...
Click to collapse
yes that is true but you also asked if it was compatable with gbhils kernel that is why it was a little confusing.
Avalaunchmods said:
soooo who wants to be so nice as to compile this to zip so people can flash it
Click to expand...
Click to collapse
lol I wanst going to be the one to ask but I was kinda hoping someone would.
PRGUY85 said:
I know its a kernel dude....still it can get incorporated into those ROMs builds like everyone has been waiting to do so...
What I'm saying is that with this now the ROM makers can get OpenGL and Multitouch on their ROM releases, something everyone has been waiting for.
Click to expand...
Click to collapse
Yes, this codebase (the last few days' commits at least) will enable hw3d and multitouch, and can be applied to any .27 kernel that is based on the htc-heroc-2.6.27 code that HTC released (which I should hope is all of them )
And yes, any kernel can be integrated into a ROM, as long as the ROM doesn't rely on custom kernel changes (e.g., squashfs is not enabled in this codebase, but if the developer already has squashfs in his own kernel codebase, he can apply these latest commits to his code, and compile a new kernel with both squashfs and gl+multutouch support, if that's what his ROM requires)
wtphoto said:
yes that is true but you also asked if it was compatable with gbhils kernel that is why it was a little confusing.
Click to expand...
Click to collapse
Yea I'm no tech guy/developer...just asking if on a ROM a dev could include this as well as the ability to setcpu which is available by way of Gumbo's kernel.
wtphoto said:
lol I wanst going to be the one to ask but I was kinda hoping someone would.
Click to expand...
Click to collapse
im excited so i had to go for it
wtphoto said:
lol I wanst going to be the one to ask but I was kinda hoping someone would.
Click to expand...
Click to collapse
You can't add just a kernel to an update.zip and flash it -- kernel gets combined into the boot.img, which is included in the update.zip for every ROM. boot.img also has the stuff that goes into / (like init.rc scripts), and so not every ROM will be compatible with the same boot.img, and you can't just flash a boot.img by itself via zip (you can via flash_image in recovery, but still, some ROMs require the boot.img that it was designed for, due to init ramdisk )
So, this is more something for the ROM developers and the not-so-faint of heart. In reality, it's not that hard to build the boot.img, and you can actually unzip your favorite ROM's zip, unpack the boot.img, then rebuild a new boot.img using that ROM's initrd and your own custom kernel, then flash just the boot.img using flash_image, and it won't even require a wipe. That's again assuming the ROM doesn't rely on anything custom in the kernel it was released with.
PRGUY85 said:
Yea I'm no tech guy/developer...just asking if on a ROM a dev could include this as well as the ability to setcpu which is available by way of Gumbo's kernel.
Click to expand...
Click to collapse
ok I see what you where asking now majrep already answered most of it but yeah I belive that they could get the setcpu thing going in this kernel.
For
32A Magic on any Sense update based ROM
6.35 radio
Tested on CursorSense 1.2.6
AnyKernel version for any 1.5 Sense ROM 2.6.27.6 kernel
710 MHz is stable for 32A. It's well proven. Now.
If you are flashing this kernel over Cyanogenmod 5, I don't know what's wrong with you. The .27 kernel isn't meant for Donut, nevermind Eclair. Unless you know how to resolve some of the weird crap that will inevitably happen by you doing something like that, don't do it.
v3 Version works even when you setup setcpu profiles. enabled range from 176 MHz to 710 MHz. If you know how to customize setcpu, it is enabled to allow up to 768 MHz. included setcpu.txt that goes into /system/sd. Does not autodetect.
You can enable 729.6, 748.8 and 768 MHz by manually editing setcpu.txt.
ondemand governor seems to be buggy (exists also with Hero oc kernel, confirmed tests by than33). Try msm7k or performance instead.
Undervolted at lower speeds (245 MHz and down).
v2 Version is not setcpu compatible but does not require setcpu to scale properly. Does not display cpu frequencies. Possible dead on standby bug on some ROMs. SetCPU wont work because this kernel has perflock configured.
BOGOMIPS will still display 528 MHz but it is actually running at 710 MHz whenever 528 MHz is shown. Run a benchmark to see if it is actually faster.
Credits
phhusson and toastcfh for oc patch
cyanogen in general
cursordroid's kernel source
Teknologist original hero kernel
maxisma's edit to acpuclock.c
koush's anykernel
Notes
Kanged from various places
2.6.27.6 kernel
Using http://github.com/maxisma/Hero-OC-kernel edit plus cursordroid's HTC-CCR kernel 2.6.27
Linpack goes to 3.x
Bluetooth, GPS wifi all still work on my phone
If your phone wont boot, revert boot.img and wlan.ko by reflashing those files or reflashing your ROM entirely.
I deleted the kernel source off my computer for this. What you see is what you get
Can I just flash this over an existing cursorsense ROM then?
Yes, that's what i just did.
My score in linpack went from 2.32 (average) up to 3.13. And the phone looks stable and responsive.
shayne122 said:
Can I just flash this over an existing cursorsense ROM then?
Click to expand...
Click to collapse
That's the point
Haha sorry for that it was early and I'm a bit of a noob - anyway, definitely stable as hell so far, with only a bit more battery drain. Dolphin browser is noticeably smoother.
I was having issues a few weeks ago using any other kernel other than cursors, but this one is working fine (for the obvious reasons). Problem was yellowing and interlacing issues on the screen. I would be curious to try another ROM and flash this kernel to see if it would help those with the newer Rogers magics.
EDIT: don't do this. wouldn't boot past blank screen. wooooo ADB!
This is running on my 32A Magic right now. Everything seems okay actually.
Battery life doesn't seem much worse neither. This patch just bumps the frequency up without changing voltage.
WHat's about test with app Benchmark?
http://www.cyrket.com/p/android/softweg.hw.performance/
Before? After?
Real overclock or placebo?
If you still think this patch is placebo you have not been around for the last couple weeks
does it work on 2.1 Sense UI ROM (e.g. Smoki, CapySlide)?
Flashed on top of Capymod's ROM based on Sanpei's Legend 0.4 (Eris). Phone no longer boots.
6.35 Radio
1.76.2007 SPL
HTC Magic 32A (Rogers)
Reverted to pre-patched system.img and it's fine again though.
Do you think this is dangerous for the phone? I mean, I know there's always a certain risk, but is it high?
csjfong said:
does it work on 2.1 Sense UI ROM (e.g. Smoki, CapySlide)?
Click to expand...
Click to collapse
tried smoki, wouldn't boot. had to revert to nandroid backup.
I said this is for 1.5 Sense roms. Why are you guys even trying this for 2.1 roms?
Deviser said:
Do you think this is dangerous for the phone? I mean, I know there's always a certain risk, but is it high?
Click to expand...
Click to collapse
I know in computer OC'ing, the danger is heat, hence the advent of things like water cooling and fans the size of a hubcap.. If the same rings true, I don't think we have too much to worry about as the upping of the frequency hasn't put out any noticeable heat increase during gaming, calls, and regular usage. At least on my phone.
xaueious said:
I said this is for 1.5 Sense roms. Why are you guys even trying this for 2.1 roms?
Click to expand...
Click to collapse
Because we suck at reading.
Looks like Sense 2.1 roms won't work with this. Thanks anyway!
Strangely enough Linpack reports no apparent improvement after flashing the update over, still in the 2.2-2.3s. Using CursorSense 1.2.6.1, 6.35 radio, on top of 32A. Any ideas?
d3vi said:
Strangely enough Linpack reports no apparent improvement after flashing the update over, still in the 2.2-2.3s. Using CursorSense 1.2.6.1, 6.35 radio, on top of 32A. Any ideas?
Click to expand...
Click to collapse
I have the same setup and my results in Linpack went up to 3.1....Sorry, but I don't know how to help you any further.
xaueious said:
I said this is for 1.5 Sense roms. Why are you guys even trying this for 2.1 roms?
Click to expand...
Click to collapse
omnikai said:
Looks like Sense 2.1 roms won't work with this. Thanks anyway!
Click to expand...
Click to collapse
noobs, gota love em... haha
xaueious said:
If you still think this patch is placebo you have not been around for the last couple weeks
Click to expand...
Click to collapse
Ok. I'm testing, but...
I installed CursorSense 1.2.4 fresh after full wipe, then 1.2.6 and got problem with superuser, then installed 1.2.6.1 - problems with superuser were gone
Installed Linpack 1.1.2, tested without patch...
Then installed patch via recovery, started, tested with Linpack again
No 3.xxx points, same 2.390-2.410 points
Why?
I explore patch - it contain 08dalviklink script. After installing patch - script can be found in /system/etc/init.d. SO patch installed successfully, but why Linpack results are same???
p.s. In build version: Cursorsense32A-1.2.6 + Dalvik-Cachemod by xau. What's wrong?
p.p.s.
Turned wifi off. Results are same
Disconnect from computer. Results are same.
Second try
Wiped everything
Installed 1.2.4, then 1.2.6.1, then patch
Tested by Linpack - got 2.41
Disappointment...
Here's the GSM Hero devs discussion: http://forum.xda-developers.com/showthread.php?t=685489
Github:
http://github.com/toastcfh/CdMa-HeRoC-2.6.29
toastcfh has the kernel up for 2.6.29, and is supposed to work for GSM Hero. I am no dev, but if I remember correctly this is the kernel source we are missing for 2.1 to happen for the 32A Magic.
The only difference between the GSM Hero and the 32A Sense UI 2.6.27 kernel that I saw was FB_MSM_LOGO, which did nothing except display a rgb565 logo. Didn't the same config compiled on the GSM Hero kernel work 32A before on the same kernel? Will it just work this time then for 32A Magic?
Here's the Cursordroid 32A Magic kernel: http://github.com/cursordroid/HTC-CCR-Kernel/blob/master/kernel-2.6.27
Or we could add the 'FB_MSM_LOGO' config option, but I don't think it really does anything important. I only see it under: http://github.com/cursordroid/HTC-CCR-Kernel/blob/master/kernel-2.6.27/drivers/video/Kconfig
Code:
config FB_MSM_LOGO
depends on FB_MSM
bool "MSM Frame Buffer Logo"
help
Show /logo.rle during boot.
One possible way to test this is to compile a kernel same as compile for GSM Hero (those settings might need to be confirmed by toastcfh, who seems to know his way around this kernel). Then pack a boot.img for Cyanogenmod 5 and see how that runs.
My cousin uses the 32A Magic so it's not exactly free for development at the moment. But it's worth a shot I think. Or am I being stupid?
xaueious said:
http://github.com/toastcfh/CdMa-HeRoC-2.6.29
toastcfh has the kernel up for 2.6.29, and is supposed to work for GSM Hero. I am no dev, but if I remember correctly this is the kernel source we are missing for 2.1 to happen for the 32A Magic.
The only difference between the GSM Hero and the 32A Sense UI 2.6.27 kernel that I saw was FB_MSM_LOGO, which did nothing except display a rgb565 logo. Didn't the same config compiled on the GSM Hero kernel work 32A before on the same kernel? Will it just work this time then for 32A Magic?
Here's the Cursordroid 32A Magic kernel: http://github.com/cursordroid/HTC-CCR-Kernel/blob/master/kernel-2.6.27
Or we could add the 'FB_MSM_LOGO' config option, but I don't think it really does anything important. I only see it under: http://github.com/cursordroid/HTC-CCR-Kernel/blob/master/kernel-2.6.27/drivers/video/Kconfig
Code:
config FB_MSM_LOGO
depends on FB_MSM
bool "MSM Frame Buffer Logo"
help
Show /logo.rle during boot.
Click to expand...
Click to collapse
im willing to test it
its open source kernel we have been waiting for new radio!!
I think this may have a chance to work with our device as CCR kernel by cursordroid is just a modified teknologist kernel
if someone could compile it we could try
would be lovely if it works
then we could really get something done
Maybe I am being an idiot, but if the radio and SPL are identical would someone try flashing a Hero ROM to your 32A?
This one is built on the new toastcfh kernel I think.
[ROM] 20 May 2010- Cronos Droid (2.1 Release full 2.6.29)
http://forum.xda-developers.com/showthread.php?t=684654
Cursordroid tested a Hero ROM before on his 32A Magic before:
http://forum.xda-developers.com/showthread.php?t=594712
If this doesn't work, maybe the extra config option does need to be added. But I don't think it is even necessary.
Things may break, but this 2.1 Sense UI Hero ROM will boot on 32A Magic I think.
After seeing how 32A overclocking results have been IDENTICAL to the GSM Hero, I keep thinking of how similar our devices might be.
I can take that boot.img apart. It will be missing the sapphire boot file in there.
xaueious said:
Maybe I am being an idiot, but if the radio and SPL are identical would someone try flashing a Hero ROM to your 32A?
This one is built on the new toastcfh kernel I think.
[ROM] 20 May 2010- Cronos Droid (2.1 Release full 2.6.29)
http://forum.xda-developers.com/showthread.php?t=684654
Cursordroid tested a Hero ROM before on his 32A Magic before:
http://forum.xda-developers.com/showthread.php?t=594712
If this doesn't work, maybe the extra config option does need to be added. But I don't think it is even necessary.
Things may break, but this 2.1 Sense UI Hero ROM will boot on 32A Magic I think.
After seeing how 32A overclocking results have been IDENTICAL to the GSM Hero, I keep thinking of how similar our devices might be.
I can take that boot.img apart. It will be missing the sapphire boot file in there.
Click to expand...
Click to collapse
i'll try now
ploish
lol wrong thread
boot.img will be missing init.sapphire.rc
Other files include:
/system/build.sapphire.prop
What else?
I have never ported a ROM from a different phone before. What other files need to be fixed?
xaueious said:
Maybe I am being an idiot, but if the radio and SPL are identical would someone try flashing a Hero ROM to your 32A?
This one is built on the new toastcfh kernel I think.
[ROM] 20 May 2010- Cronos Droid (2.1 Release full 2.6.29)
http://forum.xda-developers.com/showthread.php?t=684654
Cursordroid tested a Hero ROM before on his 32A Magic before:
http://forum.xda-developers.com/showthread.php?t=594712
If this doesn't work, maybe the extra config option does need to be added. But I don't think it is even necessary.
Things may break, but this 2.1 Sense UI Hero ROM will boot on 32A Magic I think.
After seeing how 32A overclocking results have been IDENTICAL to the GSM Hero, I keep thinking of how similar our devices might be.
I can take that boot.img apart. It will be missing the sapphire boot file in there.
Click to expand...
Click to collapse
You are right on the money, these are the kernels ive been playing with and running cm on for a couple weeks now, this source has no sapphire board files, I added them and am compiling now to test.
carz12 said:
You are right on the money, these are the kernels ive been playing with and running cm on for a couple weeks now, this source has no sapphire board files, I added them and am compiling now to test.
Click to expand...
Click to collapse
good job! that means we can get CM and overclocks for new radio hopefully
If you compile an update.zip, can you use Koush's Anykernel format? That way we can just try it across different ROMs. Just the zImage and wlan.ko should be enough for most ROM ports in this forum.
By the way Cursorsense has always rom on 32A Heros:
http://forum.xda-developers.com/showthread.php?t=620243
And I've attached the init.sapphire.rc and init.hero.rc from Cursorsense
Also attached the build.*.prop files from CM5 test 5 that should get other things going.
They seem quite different though.
Doesn't seem any compilation needs to be done though. Just download the 2.1 Sense ROM, unpack boot.img, and repack it. The same wlan.ko should work fine.
I use something like this, based on CM Wiki's kernel port guide:
unpack-H.pl boot.img
mkdir ramdisk
cd ramdisk
gunzip -c ../boot.img-ramdisk.gz | cpio -i
cd ..
Click to expand...
Click to collapse
Now slip in the init.sapphire.rc and modify whatever you need to the ramdisk
repack-H.pl ~/cm-kernel/arch/arm/boot/zImage ramdisk boot.img
mv boot.img /media/win_share/boot.img
Click to expand...
Click to collapse
If everything plays nicely, we should be seeing 2.1 ports by the bucketload this weekend.
I'd like to see the HTC Legend port updated for this If not it's a matter of AnyKerneling it.
dum di dum, hopefully someone does it soon cannot do crap on the windows box
what we need is just a kernel image,and the rest is kroush's Anykernel script——I successfully port CM 5.0.7 test1~5 to new radio by using sanpei's kernel image(not boot.img but the kernel ),it works well~
Can someone look at this? I tried putting together a .config for Cyanogemod 5: http://pastebin.com/cKkBNtKJ
This compiles
Just following up on this, I talked to toastcfh a little and he has updated a .config for the sapphire on github. But it still does not boot the Magic. It gets stuck on splash1 and does not respond to any adb commands.
I will add in some of the missing stuff when I wake up tomorrow. Or someone else can give it a shot.
keeping a very close eye on this one, very interesting. wish i could contribute to this somehow
You can.
Follow this: http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port_for_CM5
There's also this in case anything goes wrong with the more updated method for CM5:
http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
do a git clone on the toastcfh kernel source instead (change the url)
Everything else is like the same
Sanpei has good news about kernel source for new radio.
AnyKernel zips will only replace the kernel in your boot.img.
To define a boot.img:
Kernel(zImage) + ramdisk(root file system + init scripts) = boot.img
Where AnyKernel came from:
While searching for different kernels for my Motorola Droid I stumbled on a great idea implemented by Koush. Basically it will split the boot.img from recovery while your phone is running then replace the kernel and make a new boot.img and flash it along with the correct modules for the kernel.
I figured I would implement it on the CDMA Hero and it worked out.
This will work on any rooted rom with a custom recovery running Sense UI including the stock rom.
------------------------------------------------------------------------------------------------------------------------------------------------------------
Here are the undervolted and overclocked kernels for Sense ROMS
These kernels are built from the HTC heroc-2.6.29-bc0d2ccf source with toasts overclock patch modified by darchstar/Decad3nce to include undervolt.
The git repo for this is @ http://github.com/zenulator/htc-heroc-2.6.29-bc0d2cff
The GPL license can be read @ http://www.gnu.org/licenses/gpl.html
ZenKernel-HTC-08122010 no perf lock
It has perf lock disabled to allow full overclocking with out the need use setcpu to disable perf lock. The clock speeds will stay at what ever the target rom uses unless you running a rom with no overclock built in. If so it will scale from 19mhz to 768mhz.
Download
ZenKernel-HTC-08122010 perf lock
Same as above but with perf lock enabled. It will run at stock values on any sense Rom until you use setcpu. To overclock it you will need to set setcpu to autodetect and then disable perf lock inside setcpu.
Download
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
StockVoltage Overclocked Kernel:
This kernel is built from the same source as the rest except the voltages were changed to stock values. It will max out at 691 and the governor is set to performance.
Download
Setcpu is free for xda memebers and can be found here:
http://forum.xda-developers.com/showpost.php?p=3638937&postcount=1
Instructions:
Download the update and copy it to the root of your sdcard.
Reboot into recovery.
Nandroid (just in case you want to go back)
Flash the update
Reboot
Check Settings > About phone > Software information > Kernel version
_____________________________________________________________________________
If you wish to modify this with another kernel just extract the update and replace the zImage in the kernel directory with the one you want and replace the corresponding modules. Then rezip and resign and flash. It will work on any 2.1 sense rom regardless of boot.img.
Damn good work zenulator I am downloading it now and will test thoroughly tomorrow and see how it go's.
Thanks for the hard work.
Works great, using it with your beta ROM. Lock screen lag is gone
I got used to it so I barely noticed it... but now it seems a lot faster
I know you just started this and it says for sense. But I gotta ask is there anyway that this will work with froyo? I'm not a fan of overclock roms because of the lag when you push the menu key till when you screen is actually ready to go. And this gives me hope
of having a kernel that doesn't do that
thatguythatdid said:
I know you just started this and it says for sense. But I gotta ask is there anyway that this will work with froyo? I'm not a fan of overclock roms because of the lag when you push the menu key till when you screen is actually ready to go. And this gives me hope
of having a kernel that doesn't do that
Click to expand...
Click to collapse
Yes it will work for froyo if you modify it and put in the correct zImage (kernel). It won't work with the update I posted since it's made for Sense roms and uses HTC's Synaptics driver which isn't compatible with AOSP 2.2 Froyo/Cyanogenmod.
If you want a AOSP kernel with no overclock and no ability to overclock at all then I can do that but not for a couple days. If you ask darch he might be able to do it quicker since he already has everything set up and most likely only two files will need to be changed before a compile.
zenulator said:
Yes it will work for froyo if you modify it and put in the correct zImage (kernel). It won't work with the update I posted since it's made for Sense roms and uses HTC's Synaptics driver which isn't compatible with AOSP 2.2 Froyo/Cyanogenmod.
If you want a AOSP kernel with no overclock and no ability to overclock at all then I can do that but not for a couple days. If you ask darch he might be able to do it quicker since he already has everything set up and most likely only two files will need to be changed before a compile.
Click to expand...
Click to collapse
Thanks for the reply I'm gonna give the new kernel a chance to see how it does
Excuse my ignorance but how is this different from Standard DarchKernel vUV2 691 MHz found here http://forum.xda-developers.com/showthread.php?t=705074 ?
That's what I'm using and it already says
Kernel version
2.6.29-cyanogenmod
[email protected] #6
Thanks for this zen works great
this is undervolted correct? does this really help the battery life?
c00ller said:
Excuse my ignorance but how is this different from Standard DarchKernel vUV2 691 MHz found here http://forum.xda-developers.com/showthread.php?t=705074 ?
That's what I'm using and it already says
Kernel version
2.6.29-cyanogenmod
[email protected] #6
Click to expand...
Click to collapse
Uhh. I'm going to give a brief explanation.
AnyKernel is a tool created by Koushik Dutta found here on github.
The beauty of it is that it can flash/add a kernel to any boot.img regardless of ramdisk. It literally does the unpacking of the boot.img, extracting of the ramdisk, deletion of the original kernel and repacking of the boot.img together with the kernel of your choice.
The difference with this is probably changes in base address/cmd line and possible how it's extracted(haven't looked at it). Very awesome tool nonetheless, and is a lot more efficient that going through the process of coupling the kernel with each specific ramdisk before releasing a boot.img.
That's how it's different from your quoted "kernel".
Decad3nce said:
Uhh. I'm going to give a brief explanation.
AnyKernel is a tool created by Koushik Dutta found here on github.
The beauty of it is that it can flash/add a kernel to any boot.img regardless of ramdisk. It literally does the unpacking of the boot.img, extracting of the ramdisk, deletion of the original kernel and repacking of the boot.img together with the kernel of your choice.
The difference with this is probably changes in base address/cmd line and possible how it's extracted(haven't looked at it). Very awesome tool nonetheless, and is a lot more efficient that going through the process of coupling the kernel with each specific ramdisk before releasing a boot.img.
That's how it's different from your quoted "kernel".
Click to expand...
Click to collapse
I understand the explanation but have to ask what rge different change. I know this will just change the kernal from the boot imiage which is great and it has the HTC synaptic drivers in the kernal but that kernal with the HTC drivers has already been implemented into the latest boot.imgs. its a cool concept and would make it easier to change just the kernal for a one shot stop when a newer kernal comes out but as of right now that's the same kernal most of the sense based roms have already implemented into them at this time. If im wrong I'm sorry.
Now with the HTC Synaptics driver included, the swipe action once the screen is on is no longer lagged. However, I notice that there is still lag from the time the power button is hit to the time the screen comes on as compared to stock where there is almost no lag. Is there some other driver or something that causes this?
Well just an update but it has been very smooth so far, 8 hours as still smooth . Great job. Screen rotation and scroll seem quicker also .
Sent from my HERO200 using XDA App
Papa Smurf151 said:
I understand the explanation but have to ask what rge different change. I know this will just change the kernal from the boot imiage which is great and it has the HTC synaptic drivers in the kernal but that kernal with the HTC drivers has already been implemented into the latest boot.imgs. its a cool concept and would make it easier to change just the kernal for a one shot stop when a newer kernal comes out but as of right now that's the same kernal most of the sense based roms have already implemented into them at this time. If im wrong I'm sorry.
Click to expand...
Click to collapse
This will just make it a lot easier instead of having multiple boot.img for different roms like in the other thread. Plus this will work on other roms not supported in the other thread. I know the kernel brings nothing new but for instance if someone wants to overclock my old ZenHero they can now do that. Or if someone just rooted their phone and installed RA or some other recovery this is all they need to over clock and still keep their stock system.
So when someone makes a new kernel they can use this and have it work on any Rom instead of just a specific Rom.
Sent from my HERO200 using XDA App
zer0vette said:
Now with the HTC Synaptics driver included, the swipe action once the screen is one is no longer lagged. However, I notice that there is still lag from the time the power button is hit to the time the screen comes on as compared to stock where there is almost no lag. Is there some other driver or something that causes this?
Click to expand...
Click to collapse
I've always wondered about this delay with the OC kernels as well.
Sent from my HERO200 using XDA App
zenulator said:
This will just make it a lot easier instead of having multiple boot.img for different roms like in the other thread. Plus this will work on other roms not supported in the other thread. I know the kernel brings nothing new but for instance if someone wants to overclock my old ZenHero they can now do that. Or if someone just rooted their phone and installed RA or some other recovery this is all they need to over clock and still keep their stock system.
So when someone makes a new kernel they can use this and have it work on any Rom instead of just a specific Rom.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Makes sense. I thought about it actually and it will make things easier. I used it earlier today on a boot.img I flashed first that had the ramdisk mod for battery tweak but I think was missing the HTC synaptic driver. Lag is all gone and it worked great.
Papa Smurf151 said:
Makes sense. I thought about it actually and it will make things easier. I used it earlier today on a boot.img I flashed first that had the ramdisk mod for battery tweak but I think was missing the HTC synaptic driver. Lag is all gone and it worked great.
Click to expand...
Click to collapse
It's definitely going to make it easier for me at least since I plan on doing a bunch of new kernels based on toasts and darchstars work. As well as the official HTC kernel with toasts overclock.
Sent from my HERO200 using XDA App
zenulator said:
It's definitely going to make it easier for me at least since I plan on doing a bunch of new kernels based on toasts and darchstars work. As well as the official HTC kernel with toasts overclock.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Now this is what I'm talking about
I was looking for something like this. Darchstar is one helluva dev, but it seems like the only kernels in use these days are Toasts (base) then modded toast kerenels by Darchstar (which are great as well). But I'd like to see a couple of tweaks fixed in the most recent Kernel #6 such as the typo that Uroshiol mentioned that is located in the actual zImage in the DArchstar uv2 kernel 710 with freememkiller
Nice nice work ya'llz and great stuff Zen... makes the addition of new kernels a breeeeze
Wait...so there is an under volted, oc kernel available for nfinite's .6 stock rom that eliminates the menu button wake lag?? i dont like the lag but deal with it. although if there is a way to eliminate the lag, please share!!
Zen, you're definitely an unsung hero (no pun intended I swear) around these parts and I for one definitely appreciate your work. Cheers!