Database Info

[PORT][EBI1/32A]WG-Build Y.R1 - 02/01/10

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.

[devs] toastcfh 2.6.29 kernel source GSM Hero - NOW BOOTS AHERO (BUGGY)

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.

[KERNEL][7/22/10]Darchstar's Overclocked Undervolted kernel for senseUI roms vUV 2

***Explaination***:
I, as many of us have, been using Toasts #89 Overclocked kernel since it's inception. I have been thrilled with it's performance, and that our community has produced kernel source code before one was avaliable to us from HTC. Thats quite impressive
The only cons with this kernel that I have found are:
1: Would occasionally (20% of the time?) get a Force Close when a phone call is coming in, resulting in the phone being borked, and me having to reboot the phone.
As many of you have noticed, toast incorporated a script into the kernel that makes it more likely to do this on reception of a call from your lover. Yes, this is a proven fact and can easily cause problems![/sarcasm]
2: The Application "WiFi Tether for Root Users" would start properly, and would share the internet connection over wifi as intended, but would hardlock the phone when you tried to stop the tether, requiring a battery pull to get the phone going again.
So in comes DarchDroid. I tried out darchdroid 2.6.4, and even tough it was an overclocked rom, I experienced NO force closes on phone calls, and a flawlessly working WiFi Tether.
I felt that both the problems above must be caused by the kernels, because I had never experienced them when using stock HTC kernel. So I thought it might be possible to use Darch's Kernel from 2.6.4(2.6.5 broke WiFi Tether), in a Sense rom. At the time I was using IceHoneyBun(from androincentral), after trying to make a update.zip myself using parts from darchs rom and getting nothing but boot loops, PMs back and forth with Darchstar, and Beezy(cooker of HoneyBun roms), Beezy posted a flashable zip to successfully use Darch's Kernel on HoneyBun. It worked! No phone FC, and working Wifi tether. Many people who use Toasts #89 experience the FC on incoming call, and everyone using it experiences hardlock on wifi tether end. So we thought we should share the fix, and make zips for Fresh and Damage based roms as well.
Enough jibber jabber, on the the good stuff!!!!
IMPORTANT READ THIS
Due to the folder structure for the .ko modules being different between the stock, the v4, vUV, and vUV2, you MUST run this remover to erase /system/lib/modules/* . Some of the zips below create a folder inside /modules to put the ramzswap.ko. If you flash the newest vUV 2 it puts it directly in /modules, and will not override the /modules/*/ramzswaps.ko, leaving you with 2 ramzswaps.ko. To avoid any conflicts or bugs, I am going to suggest running the remover zip before flashing ANY of the zips below. Simply put the zip on your SDcard, flash it, then flash the kernel of your choice.
http://www.4shared.com/file/mvUNHgqJ/ModuleRemover.html
DO NOT FLASH WITHOUT READING INSTRUCTIONS
Code:
INSTRUCTIONS:
1. Place zip kernel zip file and module remover zip file on root of SDcard
2. Boot into recovery
3. Perform Nandroid+EXT backup
[size=3][B]4. Flash ModuleRemover.zip[/B][/size]
5. Flash your kernel of choice
AS ALWAYS NANDROID FIRST, AND POST IF YOU HAVE PROBLEMS!
Code:
[B][size=4]vUV2 Kernel[/b][/size] 1.2v
HTC Synaptics driver! (thank you Darchstar!)
CPU is undervolted.
All versions overclockable using an app to 768.
Uses 2.6.29-cyanogenmod - [email protected] #6 kernel
With custom ramdisk for each rom/mod
[B][COLOR="blue"]Standard
Uses stock 2.27.651.6 RUU Ramdisk with apps2sd support added
Compatible with: Nfinitefx45's 2.27.651.6, ZenHeroFX, Fresh Rom 2.1.1/2.1.2/2.3.3[/COLOR][/B]
[URL="http://www.4shared.com/file/PgbKNp_0/Standard_vUV2_691.html"]Darchkernel vUV2 691mhz for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/Ojlxi-lD/Standard_vUV2_710.html"]Darchkernel vUV2 710mhz for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/rlOXyLcr/Standard_vUV2_768.html"]Darchkernel vUV2 768mhz for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/tcpFg_TS/Standard_vUV2_691_M.html"]Darchkernel vUV2 691mhz with freememkiller tweak for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/t5-qeBkS/Standard_vUV2_710_M.html"]Darchkernel vUV2 710mhz with freememkiller tweak for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/6mfmPmzf/Standard_vUV2_768_M.html"]Darchkernel vUV2 768mhz with freememkiller tweak for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[B][COLOR="blue"]HoneyBun[/COLOR][/B]
[URL="http://www.4shared.com/file/31GuJx7Z/Honeybun_vUV2_691.html"]Darchkernel vUV2 691mhz for Honeybun[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/YbYt2lR4/Honeybun_vUV2_710.html"]Darchkernel vUV2 710mhz for Honeybun[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/CeIa3x24/Honeybun_vUV2_768.html"]Darchkernel vUV2 768mhz for Honeybun[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[B][COLOR="blue"]Damage Control[/COLOR][/B](has ramdisk from 2.09,will work in 2.08 and 2.09)
[URL="http://www.4shared.com/file/pW0_QiMf/Damage_vUV2_691.html"]Darchkernel vUV2 691mhz for damagecontrol based roms[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/UkiGynor/Damage_vUV2_710.html"]Darchkernel vUV2 710mhz for damagecontrol based roms[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/Y4EceZgS/Damage_vUV2_768.html"]Darchkernel vUV2 768mhz for damagecontrol based roms[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
KNOW ISSUES WITH UV v2 KERNEL
*FREEMEMKILLER BUG IN ZIMAGE, MAY EXPERIENCE MEMORY LEAK, INTERMITTEN LAG, AND LOCKUPS.
*Audio pop can be head through headphones when music/sound first starts
*You can select 787mhz using an OC app, but this frequency setting is broken,
768 is the highest frequency that works.
Code:
[B][size=4]v4 Kernel[/b][/size] 1.325v
HTC Synaptics Driver, Standard CPU Voltage.
All versions overclockable using an app to 768.
Uses Darchstar 2.6.34-GoDmOdE-Darchshizz-OC
[email protected]#4 kernel
With custom ramdisk for each rom/mod
**BUGS FOUND IN FREE MEMORY TWEAK VERSION OF V4, RECOMMEND YOU USE vUV KERNEL INSTEAD**
[B][COLOR="blue"]Fresh 2.0d[/COLOR][/B]
[URL="http://www.4shared.com/file/OSUauZsW/Fresh20b_v4_768_M.html"]DarchKernelv4 768mhz with Free Memory Tweak For Fresh 2.0d[/URL] [COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[URL="http://www.4shared.com/file/0QiLL5Ru/Fresh20b_v4_710_M.html"]DarchKernelv4 710mhz with Free Memory Tweak For Fresh 2.0d[/URL][COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[B][COLOR="blue"]Infinitefx45's 2.27.651.6[/COLOR][/B]
[URL="http://www.4shared.com/file/tTFeHUJJ/Infinitefx_v4_768_M.html"]DarchKernelv4 768mhz with Free Memory Tweak For Nfinitefx45[/URL][COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[URL="http://www.4shared.com/file/Pman261O/Infinitefx_v4_710_M.html"]DarchKernelv4 710mhz with Free Memory Tweak For Nfinitefx45[/URL][COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[URL="http://www.4shared.com/file/snpFERGY/Nfinitefx45_v4_691.html"]DarchKernelv4 691mhz For Nfinitefx45[/URL][COLOR="SeaGreen"][B]**WORKING**[/COLOR][/b]
[URL="http://www.4shared.com/file/P3TciJjT/Nfinitefx45_v4_691_M.html"]DarchKernelv4 691mhz with Free Memory Tweak For Nfinitefx45[/URL][COLOR="seagreen"][B]**WORKING FREEMEMKILLER TWEAK**[/COLOR][/B]
[B][COLOR="blue"]HoneyBun[/COLOR][/B]
[URL="http://www.4shared.com/file/4N0ggqZ8/HoneyBun_v4_768.html"]DarchKernelv4 768mhz for Honeybun[/URL][COLOR="SeaGreen"][B]**TESTED**[/COLOR][/B]
[URL="http://www.4shared.com/file/2vcrF2fJ/HoneyBun_v4_710.html"]DarchKernelv4 710mhz for Honeybun[/URL][COLOR="SeaGreen"][B]**TESTED**[/COLOR][/B]
[B][COLOR="blue"]Fresh 2.1.1/2.1.2/2.3.3[/COLOR][/B]
[URL="http://www.4shared.com/file/yOuAlojE/Fresh21_v4_768_M.html"]DarchKernelv4 768mhz with Free Memory Tweak For Fresh 2.1.1/2.1.2/2.3.3[/URL] [COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[URL="http://www.4shared.com/file/z5TRFGnd/Fresh21_v4_710_M.html"]DarchKernelv4 710mhz with Free Memory Tweak For Fresh 2.1.1/2.1.2/2.3.3[/URL] [COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[B][COLOR="blue"]Damage Control[/COLOR][/B](has ramdisk from 2.09,will work in 2.08 and 2.09)
[URL="http://www.4shared.com/file/AzNynVNU/Damage_v4_768.html"]DarchKernelv4 768mhz for DamageControl[/URL] [COLOR="SeaGreen"][B]**TESTED**[/COLOR][/B]
[URL="http://www.4shared.com/file/hiYH5bQz/Damage_v4_710.html"]DarchKernelv4 710mhz for DamageControl[/URL] [COLOR="SeaGreen"][B]**TESTED**[/COLOR][/B]
KNOW ISSUES WITH UV v2 KERNEL
*Audio pop can be head through headphones when music/sound first starts
*Freememkiller versions may be buggy due to a typo that was copy/pasted into all v4 kernels,need to redo when I get an hour or so. I should note that I haven't actually seen this problem manifest in the real world, though I think it could.
Camera Fix(thanks infinitefx45!)
Camera/Media Fix**Should work on most De-Odexed roms that DO NOT use friendstream, PM me if this boot loops your phone, and I'll edit the zip for your rom. NANDROID FIRST**, **This will revert your htcdialer to an unthemed version if you are running a theme or a themed rom, you have been warned!**
Code:
[B][size=4]CHANGE LOG[/size][/b]
[b]vUV 2[/b]
*Build from newer kernel source.
*Added HTC synaptics driver (Thank you Darchstar)
*Consolidated Nfinitefx45's 2.27.651.6 stock, ZenheroFX, and Fresh into one category. Not 100% sure if it will work on fresh, if not I'll add in the fresh rom category again.
[b]vUV[/b]
*Undervolted CPU
*Fixed my incorrect settings in ramdisks that sometimes caused CPU to drop to 19mhz.
Bug is present in all V4 kernels.(use SETCPU/Oc widget and
manually set the frequency in the V4 kernels to avoid this!!)
*Fixed a mistake I made when performing freemem tweak on the V4 kernels,
those who used the V4 kernels with freemem killer tweak that experienced
lag/slowness/stuff closing when it shouldn't/, should have no problems with
the vUV kernels with freemem killer tweak.
[b]v4[/b]
*Added 710mhz default, and 768 mhz default versions(both clockable to 768 using an OC app)
*Added separate update.zips for Fresh, Damage, Honeybun, and Infinitefx
in an attempt to solve problems with failed boots on infinitefx rom, and to
allow for lowmem tweaks in fresh roms without effecting damage roms!
*Tweaked lowmemkiller settings for Fresh and Infinitefx roms
(Honeybun is already using a tweak; gumbo.sh. and
Damage control has lowmemkiller settings accessible in Dconfig)
*A Fresh 2.0b version, just for fun!(I was testing with Fresh 2.0d and had
problems trying to use the ramdisk from fresh 2.1.2
[b]v3[/b]
*Fixed Wifi, was broken in v2!
[b]v2[/b]
*Fixed for touchscreen lag
*Fixed improper auto detect maximum frequency
(reporting as 787 while actually only being 768)
[b]v1[/b]
*Initial release
________________________________________________________________
****Many thanks to Darchstar for compiling the kernel, Toastcfh for his kernel source, Beezy420(from android central) and Jus10o for creating the flashable ZIPS with the proper ramdisks, and everyone envolved in testing, or who gave any input!!****
________________________________________________________________
Links:
Original Thread at AndroidCentral
DarchDroid, the rom the kernel was pulled from
Excellent guide on Kernel Compiling
Toast's Kernel Source =D

urushiol said:
I just realized I don't have time to finish this post atm, I'll have to do it when I get off work, but this makes for a great teaser!
so I'll just say.......
COMING SOON(tonight)
****Many thanks to Darchstar for compiling the kernel, Toast for his kernel source, Beezy420 from android central for creating the flashable ZIPS with the proper ramdisks to work with fresh and damage!****
Click to expand...
Click to collapse
So it's just Darch's kernel for Darchdroid coupled with the ramdisk for Fresh/Dama(which are the same)?
At least that's what I interpreted from the thread at Android Central
.....
Zen also moved away from #89 and BFS because of the onslaught of problems that hampered his ROM with it. He's back at #65 too.
I think we're better off either waiting for Toast to fix up the kernel source (and using #65 in the mean time) or fixing it ourselves. But if this is Darch's kernel that you're coupling the Ramdisks with, you might end up with more problems than what you're trying to fix(but who knows, good luck).

Decad3nce said:
So it's just Darch's kernel for Darchdroid coupled with the ramdisk for Fresh/Dama(which are the same)?
At least that's what I interpreted from the thread at Android Central
.....
Zen also moved away from #89 and BFS because of the onslaught of problems that hampered his ROM with it. He's back at #65 too.
I think we're better off either waiting for Toast to fix up the kernel source (and using #65 in the mean time) or fixing it ourselves. But if this is Darch's kernel that you're coupling the Ramdisks with, you might end up with more problems than what you're trying to fix(but who knows, good luck).
Click to expand...
Click to collapse
So far so good. Its only untested on DamageControl.
**UPDATED FIRST POST WITH LINKS TO DOWNLOAD AND INFORMATION**

Can I flash this over the DC2.09 with #89 already on it? or will I have to wipe? I want to test it
Also is there a way to remove the original OC flash or someway to leave me back to stock speeds?

overthinkingme said:
Can I flash this over the DC2.09 with #89 already on it? or will I have to wipe? I want to test it
Also is there a way to remove the original OC flash or someway to leave me back to stock speeds?
Click to expand...
Click to collapse
Simply Nandroid first (incase the **** hits the fan), and flash the zip posted above for damage roms =D. No need to wipe.
Someone could build you an Update.zip using damages rom zip to restore the original kernel, if you wanted to go back to that.
Good luck, and let me know how it goes =D.

I'm using the rom posted by nfinitefx45 with DB-F-OC-Boot(fresh), testing with good results

does this also fix the GPS not locking on?
or is that just me?
i've tried 4 different OC roms and each of them i can't lock onto my position on GPS *closest is within 1000m*
on non OC roms it locks on to even what room i'm in in my house.

151jcolon said:
I'm using the rom posted by nfinitefx45 with DB-F-OC-Boot(fresh), testing with good results
Click to expand...
Click to collapse
Excellent!
gonzoangel said:
does this also fix the GPS not locking on?
or is that just me?
i've tried 4 different OC roms and each of them i can't lock onto my position on GPS *closest is within 1000m*
on non OC roms it locks on to even what room i'm in in my house.
Click to expand...
Click to collapse
I know this was common on early DarchDroid Builds, but has since been resolved, I never knew of the issue on sense based roms. But on a side note, I can say the GPS works great for me on honeybun+this kernel as well as fresh 2.1.2+this kernel.
what OC roms have you tried gonzoangel?

[FIX][Overclocking Kernel]FIXED force Close on phonecall and lock on wifi tether stop
Flashed the DC one and so far so good
Also using 2.08 based rom for the testing
-------------------------------------
Sent via the XDA Tapatalk App

Flashed over Toast's, tested like crazy trying to provoke FC, and couldn't do it. AMAZING job!!!

Decad3nce said:
So it's just Darch's kernel for Darchdroid coupled with the ramdisk for Fresh/Dama(which are the same)?
Click to expand...
Click to collapse
Its my kernel, but not the same found in darchdroid. I compiled specifically for this purpose as the OP requested it. It'll only work with sensui roms as it uses the htc touch synaptics source.

darchstar said:
Its my kernel, but not the same found in darchdroid. I compiled specifically for this purpose as the OP requested it. It'll only work with sensui roms as it uses the htc touch synaptics source.
Click to expand...
Click to collapse
Ah nvm then. I posted just based on the thread at Android Central(before the explanation). Was wondering about the synaptic drivers but wasn't sure who did the edits. Good stuff!

Just flashed and tested on DamageControl 2.09 - works great! TetherWiFi stops without causing my phone to hang - not sure about the phone call problem, as it only happened twice to me. Other than that, great job!

Decad3nce said:
Ah nvm then. I posted just based on the thread at Android Central(before the explanation). Was wondering about the synaptic drivers but wasn't sure who did the edits. Good stuff!
Click to expand...
Click to collapse
Lol, the explanation over at android central was terrible. That post was just like "here u go, a kernel. it may seem like i did all the work. lets just leave it at that"

I needed this! Thank you

darchstar said:
Lol, the explanation over at android central was terrible. That post was just like "here u go, a kernel. it may seem like i did all the work. lets just leave it at that"
Click to expand...
Click to collapse
Ha yeah. I tried my best to interpret it but was completely lost when I tried to piece everything together with my past knowledge about the differences between your kernel and toasts(notice the 15 edits on my first post LOL). So can we safely blame BFS(or at least its implementation)?

Called my phone more than 20 times in various states with no issues. Sick work!

Does this do anything for the occasional loss of a data connection issue?
http://androidforums.com/sprint-htc-hero/101113-losing-data-connection-2-1-update.html
thx.

very nice work.

ronnienyc said:
Does this do anything for the occasional loss of a data connection issue?
http://androidforums.com/sprint-htc-hero/101113-losing-data-connection-2-1-update.html
thx.
Click to expand...
Click to collapse
I can't comment on this issue, because I have not experienced data connection drops with the sprint kernel, toasts kernel #89, or this kernel.
Be sure your on the newest PRL, and have updated your profile. Do you have mobile data always on enabled or disabled?

[REQ] superFroyo for 32a

superFroyo v2.8.2 guys please port these rom for 32a device

we hope they will and i believe they will

Did you bother asking the developer?

gonna take some time for this to happen lol

Binary100100 said:
Did you bother asking the developer?
Click to expand...
Click to collapse
I asked one giant_rider is testing with some kernel function of this rom. But I wish some developer patches (as bcrook) created a patch for old radios

flash the Rom
flash port

davidcal said:
flash the Rom
flash port
Click to expand...
Click to collapse
work ??????

fonsigno said:
work ??????
Click to expand...
Click to collapse
Perfectly well

Well I don't think anybody should do any special port for any G1/32B roms.
I you wish to flash any of the roms in g1 section, the only thing you need to do is flash one of pershoot/bcrook/dumfuq 32A kernels on top of it and it will work just fine. Just make sure you flash the correct kernel version according to the rom base CM version.

In my opinion there is not a significant benefit to porting SuperFroyo since we now have other Froyo roms (without sense ui) that....
(1) Run on 32a 3.22 and 6.35 radios
(2) Have JIT working
(3) Have overclock kernels available up to ~700+ MHz
(4) Have Spareparts, CyanogenMod Settings and SetCPU for tweaking rom performance
These roms can now easily get 4.0-5.0 in Linpack and are stable.
Out of curiousity, I ported SuperFroyo a few days ago. The performance tweaks in SupSetup were not capatible with the .32 Sanpei kernel that was available for the 32a 6.35 radio at the time I did the port. We recently have the .34 kernel for the 32a 6.35 radio (thanks to carz12 and Switch33). I will update the ported SuperFroyo with the .34 kernel for the 32a 6.35 radio tonight or tomorrow hopefully. I don't think the result will be better than the other Froyo roms we have now, but I am happy to post a link if people want it.

thank you brother giant_rider for your hard work to give us the happiness
thanks you again giant

giant_rider said:
In my opinion there is not a significant benefit to porting SuperFroyo since we now have other Froyo roms (without sense ui) that....
(1) Run on 32a 3.22 and 6.35 radios
(2) Have JIT working
(3) Have overclock kernels available up to ~700+ MHz
(4) Have Spareparts, CyanogenMod Settings and SetCPU for tweaking rom performance
These roms can now easily get 4.0-5.0 in Linpack and are stable.
Out of curiousity, I ported SuperFroyo a few days ago. The performance tweaks in SupSetup were not capatible with the .32 Sanpei kernel that was available for the 32a 6.35 radio at the time I did the port. We recently have the .34 kernel for the 32a 6.35 radio (thanks to carz12 and Switch33). I will update the ported SuperFroyo with the .34 kernel for the 32a 6.35 radio tonight or tomorrow hopefully. I don't think the result will be better than the other Froyo roms we have now, but I am happy to post a link if people want it.
Click to expand...
Click to collapse
Hey giant_rider, I want link.
Thanks

giant please post the link

Here is a link to a ported SuperFroyo rom.
It is running Sanpei's .32 kernel for 32a 6.35 radio.
Some of the features in SupSetup are not enabled because they are not compatible with the kernel the way it is set up.
http://rapidshare.com/files/408904656/SuperFroyo2.4_32a_NR_v0.2.zip.html
I have been unable to get this rom to boot properly using the carz / switch .34 kernel. You can try flashing that kernel over this rom from recovery if you like. I think all of the settings in SupSetup could be enabled with the .34 kernel.
I am still sceptical whether this rom will be any better than the ones we have for 32a 6.35 or 3.22.
For a fast lite rom, I suggest you try flashing Switch's Fusebox Froyo, then install SetCPU and up the max CPU to 652 or 691 MHz. I did this tonight and got linpack of 4.6 and my phone is stable.

giant_rider,
Thanks

[KERNEL][ICS][Linux 3.0.44] Harsh Kernel P999 Build-0510 [zram][SNAPPY]]

Hello guys n gals,
This is T-Mobile G2X version of my Harsh Kernel for O2X based on 3.0.y sources.
It share same tweaks and changelog with its international brother O2X.
This is my FIRST kernel based on sources of wkpark and vadonka.
This kernel is compiled by me, and comes with more added patches by me.
If you like it hit THANKS button.
Click to expand...
Click to collapse
All credits goes to:
armcee (CM7 & CM9 GOD of LG devices)
CM Team (You guys rock)
wkpark (ported kernel 3.0.26 to our devices)
vadonka (various kernel tweaks and awesome sources)
pastime (helping at various stages, and awesome fixes)
Owain (Biggest motivation for compiling 100 times a day)
and to everybody else who participated in making this possible.
Harsh Kernel P999:
Code:
Build from 3.0.37 sources.
Compiled using tweaked CodeSourcery arm Toolchain.
Better battery.
Default SIO scheduler.
Working Data Usage ICS.
Working Data Usage Limit.
Fixed USB tethering(windows).
And many tweaks.
Changelog:
Build 0510 Stock & OC
Updated Linux version 3.0.44 now.
Stock & OC version both uploaded to goo.im.
linux version 3.0.43 and 3.0.44 brings lots of changes (150+ commits hope good)
Still works for both JB and ICS both.
build 0509 Stock & OC
Compile zram as module (Thanks Benee)
Fix zram for dual core
build 0309 Stock
Linux Version 3.0.42
JellyBean[Heckfest] supported (thanks Benee)
build 0208 Stock & OC
Linux Version 3.0.39
Reverted various fixes which were implemented in 1907
Compiled with linaro toolchain on OS X
build 1907 NO-OC
Linux Version 3.0.37
Improves SIO scheduler for flash storage.
Added V(R) I/O Scheduler. (select if from AnTuTu CPU Master)
other various fixes (thanks to vork[benee] and faux123)
build 1006 Stock & OC
Linux Version 3.0.34
Patches from NVIDIA for cpu control (power saving)
Lowmemory killer from linux 3.4 ported by vork (thanks benee)
build 0306 Stock
Some patches from Benee (vork)
And tegra OTG try update.
build 2205 Stock
Linux Version 3.0.32
Re-enabled ext3 ability (fix unsupported file system problem)
Increased XZ compression usage.
build 1505 Stock & OC
Added Force Fast Charging patch by Chad Froebel
Lots of tegra related v21 source drop fixes, thanks to faux123
New wifi code change, from v21 sources
As usual few kernel config changes (still have to find minimum config )
build 0805 Stock & OC
Linux Version 3.0.31
Battery heat protection (thanks wkpark)
And few more kernel config changes
build 0405 Stock & OC
v21y battery driver (thanks vadonka)
too many kernel config changes (100s of changes)
pmem size reduced (let me know 4 mb change can make difference or not)
build 2804 No-OC
Linux 3.0.30 sources
First attempt for CpuSpy to work
build 2704 Stock & OC
rmcc's tegra_odm_touch: More ICS-compatibility
Catalin Marinas: Kmemleak patches
build 2504 - NO-OC
Updated to Linux 3.0.29
Scheduler Tweak
Scheduler multi-core support
build 2204
OC Version of Build 1904
build 1904
ZRAM compression changed from LZO to Google's SNAPPY (~2x faster)
ZRAM disksize set to 64mb
SNAPPY KERNEL
build 1504 - OC
Build from kernel sources 3.0.28
USB Mass Storage support for both SD Cards (ROM required to make it work)
XZ Compression, so even smaller size of zips.
OC Enabled upto 1.4 GHz
zram enabled and allocated
And many small changer that are not stated here.
build 1104
Lower TouchLED Brightness
Kernel refresh, compiled with new toolchain
build 0604
SD Card IO speed fixed (thanks again wkpark)
Nothing much, just some cosmetic fixes in code
build 0504
Using AnyKernel by koush (easy flash for all ICS roms.)
Added Voodoo again
Fajarep BL values (better battery)
build ReBorn 0304
upgraded Linux kernel source version 3.0.27
various MMC tweak and safepoints
pastime .config fix for support voltage unit in uV
build ReBorn 0204-1
fixed WiFi not turning on
WiFi was not loading up before, NOW FIXED
build ReBorn 0204
ReBorn: used clean wkpark's sources
added patches handpicked (new branch).
removed voodoo sound.
better bettery & speed
build 3003
proper suspend (wkpark original work)
build 2903
latest wkpark's merge fixes (thanks)
pastime1971's fixes
build 2703-1
latest wkpark's fixes he posted. (thanks again)
Fixed reboot issue
build 2703
some more kernel config changes.
pastime kernel pull fix.
build 2503-3
some kernel config changes.
spica1234 call quality improvement patch
Compiled with more hard flags, faster compilation.
build-2503
Updated to kernel 3.0.26 (thanks vadonka)
Added Simple I/O scheduler as default
and few kernel config tweaks
build-2403-4
Removed Kernel Debugs (further cleaning)
implemented hard float in order to reduce compile time
added ramdisk tweaks
build-2403-2
Implemented cache (first try to improve performance)
improved gps (source wkpark)
build-2403-1
Fixed Internal Storage problems(thanks to wkpark)
few compiling fixes, cleaner build.
build-2303
Initial sources.
Added usb tethering
Fixed Data Usage and Limit
Added Voodoo Sound
Selfcompiled linaro toolchain​
Understanding build number:
build-ddmm-n
where dd=date, mm=month & n=compile number [start from 0/none]
Known bugs:
No HW Acceleration (Nvidia and LG at fault)
Reboot/Reboot recovery work 90% of time.
Download OC 0510 Link: Goo.im
Download NO-OC 0510 Link: Goo.im
My PIZZA suppliers (Donators, thanks a lot)
Owain van Brakel
Warren (djvoleur)
Gregory Martinson
Vu Phan
John(aragorn7)
sourcecode

Looks great!
Sent from my LG-P999 using XDA

zoppp said:
Looks great!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Thanks you. If you are on CM9 unofficial nightly, you can try it. I am out of thanks per day

Installed. Will test drive today.
Sent from my G2x running AOKP ICS Build 28

Is it overclocked?
Sent from my LG-P999 using xda premium

flak0 said:
Is it overclocked?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
No, its not overclocked.
Its on stock, will add overclock patch later, but defualt will always be stock.

Just for clarification: if hardware acceleration isn't yet included, what advantages are there to install this kernel over, say, faux's? Thanks.

GenghisKhan67 said:
Just for clarification: if hardware acceleration isn't yet included, what advantages are there to install this kernel over, say, faux's? Thanks.
Click to expand...
Click to collapse
Actually this is completely different kernel than faux kernel.
This kernel is not based on CM sources, it is based on kernel version 3.0.26, one of the latest in linux-3.0.y. If you guys know, Samsung Galaxy Nexus uses, kernel 3.0.8 in stock, this is kernel 3.0.26.
Faux kernel is based on CM sources linux-2.6.xx.x .
And there are no advantages as such, but deep sleep is finally working perfectly in kernel 3.0.y versions. So maybe better battery.

Working great on AOKP..... Battery seems a little bit better.
Sent from my LG-P999 using xda premium

the stock CM9 kernel has no HW accel, right? if so, i need this kernel for the voodoo, as stock CM9 doesn't have it.

joeyxl said:
the stock CM9 kernel has no HW accel, right? if so, i need this kernel for the voodoo, as stock CM9 doesn't have it.
Click to expand...
Click to collapse
True, stock CM9 do not have HW, neither do this kernel. And tegra2 devices will not have HW accel until Nvidia releases sources, or LG/T-Mobile release office ICS Rom.
Yes this kernel do have voodoo sound.

Appreciate your work. Thank you.
If you could please, in a timely fashion, provide the source to your changes and place it in the OP before the GPL police find out.
Thanks again!

Will there be a CM7 version of this kernel at all?

overground said:
Appreciate your work. Thank you.
If you could please, in a timely fashion, provide the source to your changes and place it in the OP before the GPL police find out.
Thanks again!
Click to expand...
Click to collapse
its already in its main thread in O2x, added it here too.
thendless said:
Will there be a CM7 version of this kernel at all?
Click to expand...
Click to collapse
No, not planned at the moment.

Nice!!! You work fast
Edit: Starting to like SIO, antutu benchmarks went up.
Sent from my LG-P999 using xda premium

Been following this project for awhile on other threads. I've been very impressed with this work. I've been curious about something, though, and didn't want to post this question in one of the main development threads.
What is the feasibility of upgrading the kernel to 3.1,3.2, or 3.3 series? For all I know it's completely impossible as I'm sure they had a reason to use 3.0 as the base for the project. I do find it interesting, though, that 3.3 comes with "android support" (not that I really know what that means either ).

MWBehr said:
Been following this project for awhile on other threads. I've been very impressed with this work. I've been curious about something, though, and didn't want to post this question in one of the main development threads.
What is the feasibility of upgrading the kernel to 3.1,3.2, or 3.3 series? For all I know it's completely impossible as I'm sure they had a reason to use 3.0 as the base for the project. I do find it interesting, though, that 3.3 comes with "android support" (not that I really know what that means either ).
Click to expand...
Click to collapse
yeah they have stated that next version will come with android support, it would not be 3.3, but would be 3.4. With more android related patches.
Guys even 3.0.y was a difficult task to port to tegra2, as no source, all thanks to wkpark and his awesome talents. I think your question can be better answered by him.
But code in 3.0.y to 3.1/3.2 has changed a lot, so would be very difficult to port, specially without any other android manufacturers not having 3.1/3.2 as base make it near impossible.

Harsh said:
yeah they have stated that next version will come with android support, it would not be 3.3, but would be 3.4. With more android related patches.
Guys even 3.0.y was a difficult task to port to tegra2, as no source, all thanks to wkpark and his awesome talents. I think your question can be better answered by him.
But code in 3.0.y to 3.1/3.2 has changed a lot, so would be very difficult to port, specially without any other android manufacturers not having 3.1/3.2 as base make it near impossible.
Click to expand...
Click to collapse
Thanks for the quick response. Ya, I was just curious more about if it was a possibility. If it takes a year or more, then that's what it takes. I have complete respect for the difficulties in porting something that's never been ported before.

so far so good...tks dev

Well...I can say this gets about 500 points higher on Quadrant 2.0 than Faux SV kernel. I didn't think it was fair to compare it to the OC version.