Related
This thread is for my personal kernel patches that I use to patch the main android kernel source to be able to build a working kernel for 32A Magic/Sapphire devices. Various people have chipped in during the development of this, please see the old thread for details.
The old dev thread is located here: http://forum.xda-developers.com/showthread.php?t=548061
Who is this for?
Anyone that builds kernels for HTC 32A Magic/Sapphire devices and has experience patching, configuring and building kernels for the ARM architecture. This thread is not intended as a guide for beginners.
Please do not ask how to build a kernel or how to configure a kernel.
Why?
It is true that HTC have released their kernel sources here, but one would have to use this exact source and would be unable to simply build a patch to make a 2.6.29 kernel due to the numerous differences in the HTC kernel source. One could not also just rely on pulling a new kernel snapshot from the main GIT tree. This patch intends to patch the kernel from the main msm branch with as little changes as possible.
What do you need?
Get the latest snapshot here (currently c7f8bcecb06b937c45dd0e342450a3218b286b8d.tgz)
Do not try and patch HTC's Kernel Source.
Notes:
For the time being, this patch works properly for both 2.6.27 and the 2.6.29 branch.
You will not be able to build kernels for 32B devices after you use this patch. Please keep a separate copy of your kernel for 32B devices.
[NEW] Built a 2.6.29 kernel from cyanogens /proc/config.gz, everything seems to be working fine.
The Files:
Kernel Patch 2.6.27 TT V3
Example Kernel:
32A Cyanogen 2.6.29 (v4.0.4 - stable version, updated 8/28) with wlan.ko - ONLY FOR USE WITH 4.0.4 CYANOGEN ROM (Cyanogen contains extra modules on his ROM for this kernel)
There seems to be a bug in 4.0.4 ROM where wifi tethering is not working. I have reverted back to 4.0.3 with the above kernel and all is working fine including tethering.
32A Cyanogen 2.6.29 (v4.1.1) with wlan.ko - ONLY FOR USE WITH 4.1.1 CYANOGEN ROM (Built from cyanogen github w 4.0.4 config)
Multi-touch is working in the browser.
32A Cyanogen 2.6.29 (v4.1.5) with wlan.ko - ONLY FOR USE WITH 4.1.5 CYANOGEN ROM (Built from cyanogen github w/4.1.5 config)
Cyanogen says he will be changing the scheduler to BFS soon.
32A Cyanogen 2.6.29 (v4.1.6) with wlan.ko - ONLY FOR USE WITH 4.1.6 CYANOGEN ROM (Built from cyanogen github w/4.1.6 config)
Includes BFS scheduler. Wow, browser flies.
32A Cyanogen 2.6.29 (v4.1.7) with wlan.ko - ONLY FOR USE WITH 4.1.7 CYANOGEN ROM (Built from cyanogen github w/4.1.7 config)
Haven't really tested this completely but seems fine.
32A Cyanogen 2.6.29 (v4.1.8) with wlan.ko - ONLY FOR USE WITH 4.1.8 CYANOGEN ROM (Built from cyanogen github w/4.1.8 config)
Camera working, Camcorder not working.
32A Cyanogen 2.6.29 (v4.1.9.2) with wlan.ko - ONLY FOR USE WITH 4.1.9.2 CYANOGEN ROM (Built from cyanogen github w/4.1.9.2 config)
Everything appears to be working properly
32A Cyanogen 2.6.29 (v4.1.11.1) with wlan.ko - ONLY FOR USE WITH 4.1.11.1 CYANOGEN ROM (Built from cyanogen github w/4.1.11.1 config)
Everything appears fine.
ROM boot images:
V2.1 eViL hero 2.9.5x (2.6.29, BFS, SLUB) 32A only (apply as update) - THIS IS EXPERIMENTAL. Any bugs, let me know.
Bluetooth,Wlan,Gps - working. (Not sure about headset but bluetooth turns on)
Graphic intensive apps - Working (Armadillo roll works, Gears gets 60fps)
Camera working this time
eViL hero 2.9.9 (2.6.29, SLUB, Anticipatory) 32A only (apply as update)
Seems to work properly!
Hero Volume Fix:
Hero Volume Fix (tested on eViL Hero) (Do a backup first and then test) -- Apply as update
Disclaimer:
These patches are experimental and should not be used for mission critical operations without extensive testing. I nor anyone else, will be held responsible for the use of these patches. If any damage or loss is experienced due to these patches, these are at your own risk. You will not be reimbursed by anyone for any amount what-so-ever.
Changelog:
V3
Added comments to changed values - may help to find errors in the future.
Changed Makefile.boot back to V1 to be the same as official HTC Source - (initrd_phys-y := 0x19A00000)
Changed EBI_SIZE to the same size as the HTC released kernel source.
Changed VMALLOC to the same size as the HTC released kernel source.
V2
Changed Makefile.boot - changed to initrd_phys-y := 0x1A200000 (credit to rayman84)
Great work. Looking forward to this.
I will have to learn how to compile a kernel now.
Tigertael..in the prevous thread u said..
Bluetooth and led working..
* SDCard
* Memory - (All memory)
* Camera - (Special thanks to zinx @ Freenode!)
* GPU1 - (Pretty sure this is right)
* ADSP - (Pretty sure this is right)
* MDP - (Untested)
* LED's - working fine.
* GPS -working fine.
* Bluetooth - working fine.
* WLAN - Working 100%
Click to expand...
Click to collapse
Does this mean if a Hero Cooker use this kernel then Bluetooth and Led Problem will be fix?
lesjaw said:
Tigertael..in the prevous thread u said..
Bluetooth and led working..
Does this mean if a Hero Cooker use this kernel then Bluetooth and Led Problem will be fix?
Click to expand...
Click to collapse
Unfortunately no. That was running on a stock ROM, not a Hero ROM.
The problem with Hero is the binaries that it was built upon was meant purely for the Hero. It's not known currently if you can correct this with a kernel, although I suspect you might be able to but only with the Hero sources for the kernel.
Even then it's a mission.
lesjaw said:
Tigertael..in the prevous thread u said..
Bluetooth and led working..
Does this mean if a Hero Cooker use this kernel then Bluetooth and Led Problem will be fix?
Click to expand...
Click to collapse
This means that bluetooth and the leds work correctly with a cupcake based rom. The Hero roms still have issues which will probably only be resolved when (if) the Hero source is released.
What in Cyanogen's kernel is working?
If multitouch is finally working, I love you
WaterMan! said:
What in Cyanogen's kernel is working?
If multitouch is finally working, I love you
Click to expand...
Click to collapse
I didn't even know Cyanogen had multitouch capable apps in his ROM.
If he does, he might've had to use kernel patches of his own and if this is so, he hasn't shared them with me.
Name display
How it s possible to add a caller name display in the rom as we know fido and rogers support this option thanks
roriii said:
How it s possible to add a caller name display in the rom as we know fido and rogers support this option thanks
Click to expand...
Click to collapse
This is a paid carrier feature, nothing to do with the ROM.
Clinton
TigerTael said:
I didn't even know Cyanogen had multitouch capable apps in his ROM.
If he does, he might've had to use kernel patches of his own and if this is so, he hasn't shared them with me.
Click to expand...
Click to collapse
I think the multitoch is more from some Android changes than kernel's , I read somewhere that The Kernel has already multitouch enabled, I fyou recall, it worked fine with Hero ROMs and stock kernel for Magic.
shwan_3 said:
I think the multitoch is more from some Android changes than kernel's , I read somewhere that The Kernel has already multitouch enabled, I fyou recall, it worked fine with Hero ROMs and stock kernel for Magic.
Click to expand...
Click to collapse
I do recall and I'm inclined to agree with you.
TigerTael said:
I do recall and I'm inclined to agree with you.
Click to expand...
Click to collapse
I can't say that my stock Magic (Vodacom) had multitouch enabled... It is enabled in Hero roms but that is in someway due to the HTC closed-source framework. The Magic (and Dream) kernels had no specific way of interpreting multitouch data without a kernel hack or modified dalvikvm).
http://lukehutch.wordpress.com/2009/01/25/get-multi-touch-support-on-your-t-mobile-g1-today/
Not only does the framework/kernel have to support multitouch, but the applications too.
That's true
Hi, I'm using your kernel 2.6.29 (from Cyanogen) in the bcook's porting of Cyanogen 4.0.4 (http://forum.xda-developers.com/showthread.php?t=544854). It works great but I don't understand why the multitouch doesn't work. It requires support by both the applications and kernel: the Cyanogen's browser package has multitouch (all the Dream and Magic 32B people use it) and your kernel should inherit it.
How did you compile it? Did you use, as base, the original kernel by Cyanogen from his git repository? Did you use his config file?
Thanks.
Actually, multi-touch IS working on the new kernel I built for 4.1.1
TigerTael said:
Actually, multi-touch IS working on the new kernel I built for 4.1.1
Click to expand...
Click to collapse
Do you mean that it is not working with the browser package in 4.0.4 or that you rebuild/fixed the kernel just for 4.1.1?
Can you provide a kernel for Cyanogen 4.0.4 (stable) with a working multitouch? I would keep my phone on the stable releases of Cyanogen. Thanks.
You can use the 4.1.1 kernel with 4.0.4 and multi-touch should work fine as well as all your other features. HOWEVER, please note that I could not get tether working in 4.0.4 or 4.1.1.
I am using 4.0.3 with 4.1.1 kernel, tether works, etc.
I'm using the new kernel from 4.1.1 in my Cyanogen 4.0.4 (I don't care about tethering): multitouch works well in the browser. Do you know if in Cyanogen there are other applications that support multitouch? Gallery don't.
The next step is to unify the kernel with the official one by Cyanogen (with some kind of board recognition on the boot phase) so we can just use the same official image.
Thanks to all!
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.
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
AOSP Kernels for HTC's 8x50, 7x30, and 8x60 Devices
Also available for the Motorola Xoom
Tiamat kernels are designed for use on all ROMs that are built from the AOSP source code. This includes ROMs built from MIUI, CyanogenMod, and others.
Tiamat receives no support for use with ROMs based on HTC's Sense - use at your own risk.
Click to expand...
Click to collapse
Tiamat Kernels
You can find full details about Tiamat Kernels at our website. The site is up and running and serves as a more centralized location to get updates, downloads, and changelogs for all Tiamat Kernels. There is no forum or Registration, it’s just a more convenient way to keep things organized as we work to add support for more devices.
Click to expand...
Click to collapse
Support
Join the Tiamat Kernel developers on IRC at irc.freenode.net, #tiamat. Support and questions are generally handled faster there than the forums. You can easily join via webchat here.
Click to expand...
Click to collapse
Special Thanks to:
toastcfh, slayher and the CyanogenMod team for the base kernels and everything else they do for the Android community
bcnice20 for generally being awesome
TeamWin for also generally being awesome
netarchy, chad0989, cuviper, and invisiblek for some great code
intersectRaven and redstar3894 for the Mjolnir compiler
JasonK75 for updating threads
Click to expand...
Click to collapse
Quick Links
Click to expand...
Click to collapse
8x50 Changelog
8x60 Changelog
7x30 Changelog
Downloads
FAQ
Source Code
im running the latest miui and installed this kernel no problems so far running nice.
This kernel supports many different devices?
Sent from my HTC Sensation 4G using XDA App
jerrylzy said:
This kernel supports many different devices?
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Yes it does support a lot of devices. 13 devices now have Tiamat Kernels and the Xoom has a Tiamat ROM to go with it.
Welcome to the empire ;p
Cayniarb said:
Yes it does support a lot of devices. 13 devices now have Tiamat Kernels and the Xoom has a Tiamat ROM to go with it.
Welcome to the empire ;p
Click to expand...
Click to collapse
hi mate, if you make a good kernel for our desense rom like an exclusive
we will be your betatesters
thx in advance mate
What do you mean by "7x30" and "8x50" ?
good job guys
is this kernel have battery drain fix for cyanogen and miui roms?
oooo, competition
welcome!
I've seen your git this morning.. and.. most of tweaks from my kernel source
Morak75 said:
What do you mean by "7x30" and "8x50" ?
Click to expand...
Click to collapse
It refers to the SnapDragon chipset....
MIUI 1.7.22
Sweet on MIUI .22 for me, battery drain good.
Morak75 said:
What do you mean by "7x30" and "8x50" ?
Click to expand...
Click to collapse
The Qualcomm Snapdragon 8x50 chipset is in the Inc, Evo, Desire, and N1.
The Qualcomm Snapdragon 8x55 chipset is referred to as the 7x30 chipset because it uses acpuclock-msm7x30 (no idea why, just the way it is). This is in the DesireHD/Inspire, DesireZ/G2, MyTouch 4G, Desire S, Merge, Inc2, IncS, TBolt, and Shift.
The x in those numbers is a modifier to indicate the radio(s) included with it.
johnny8910 said:
Sweet on MIUI .22 or me, battery drain good.
Click to expand...
Click to collapse
+1 Good performance on MIUI 1.7.22
Good explanation
Cayniarb said:
The Qualcomm Snapdragon 8x50 chipset is in the Inc, Evo, Desire, and N1.
The Qualcomm Snapdragon 8x55 chipset is referred to as the 7x30 chipset because it uses acpuclock-msm7x30 (no idea why, just the way it is). This is in the DesireHD/Inspire, DesireZ/G2, MyTouch 4G, Desire S, Merge, Inc2, IncS, TBolt, and Shift.
The x in those numbers is a modifier to indicate the radio(s) included with it.
Click to expand...
Click to collapse
Thanks for explaining that
Hi, this kernel use oc daemon?
No.
dd4285 said:
Hi, this kernel use oc daemon?
Click to expand...
Click to collapse
Sent from my Inspire 4G using XDA App
LorD ClockaN said:
oooo, competition
welcome!
I've seen your git this morning.. and.. most of tweaks from my kernel source
Click to expand...
Click to collapse
Not knowing who you are, let's assume I did not get anything from your kernel.
I honestly haven't been working on this series very long, so most of the modifications I have made are fairly common. Beyond that, the only other repos I've looked at on this are CM's, bcnice20's, and my own.
I realize I'm stepping into the 7x30 kernel scene a bit late in the life for a lot of the devices, and I'm not trying to piss off the established developers that are already here. I've had a lot of users asking me to take up these devices and, really, I'm bored waiting for kernel source for the Sensation and/or Evo 3D.
Since this one is for multi devices we cannot calculate with such things like audio boost as in LorD´s Kernel or do we ? The HTC Desire HD is a bit to silent with standard kernels.
peste76 said:
Since this one is for multi devices we cannot calculate with such things like audio boost as in LorD´s Kernel or do we ? The HTC Desire HD is a bit to silent with standard kernels.
Click to expand...
Click to collapse
I'm not sure I understand your question.
These kernels do have audio boost included though.
I think he means that kernels for the DHD usually have a 20% audio boost.
Sent from my Inspire 4G using XDA App
cayniarb said:
yes it does support a lot of devices. 13 devices now have tiamat kernels and the xoom has a tiamat rom to go with it.
Welcome to the empire ;p
Click to expand...
Click to collapse
2wcr support....????????????