Related
Hi there
I'm Chaosz-X, known from some kernel work for the HTC Desire, and my custom ROM, and one of the first people (with Texasice, Sandvold, and Shaky153) to get ICS running on the Desire. Since it wouldn't be a bad idea at all to update the kernels of our devices to 3.0, as that is the recommended version for 4.0.3 of ICS, I decided to work ono that.
I took the Tiamat 8x50 source as a base, and applied all the changes of 2.6.39.4. Once this version is up and running, we should be able to download a brand new version of the kernel as 1 patchset, and apply it within a couple of minutes. And more importantly, it will make the work on porting of drivers (e.g. HWA) easier as our kernel isn't a bottleneck anymore. I just finished uploading the source code of this 2.6.39 kernel, and with a few modifications, it should run on the Nexus One too I think. So here is the link:
http://api2.ge.tt/0/8XflAuC/0/blob/download
The file in the root called 'RENAME THIS TO (DOT)config', you can remove it. It is the .config of the Desire. Instead, copy \arch\arm\config\tiamat_mahimahi_defconfig to the root of the folder, and rename it to .config
Edit the MAKEFILE in the root to redirect to the place of the toolchain. The line that has to be edited for this is:
CROSS_COMPILE ?= arm-eabi-
Get Linaro Toolchain for Android, and replace this arm-eabi- with the location of the Linaro toolchain. Enter the terminal, get root access, and type:
make menuconfig
And press EXIT, and YES to save. Then enter
make -j2 -i (if you have 2 cores, if you have 4, you can try -j4)
And it should compile. It will tell you where it put the WiFi 4329 drivers, and you should find a zImage in /arch/arm/boot/. I never checked how the Nexus One has to be flashed with a new kernel, but this zImage is the one you need to get on your device (pretty sure some people here can take care of this ).
And then, report in this topic how it works, what works and what doesn't, etc. I haven't tried compiling this yet as I don't have my Linux machine here atm, so you may run into errors and it can stop compiling: if so, tell me.
(and make sure you got all the dependencies to build a kernel, if you don't know which one you need, Google it)
Sounds promising. Is everything from desire thread working for N1?
You mean in the kernel? This kernel is based on Tiamat, and that was the one we were using for ICS, and only tethering through USB (natively) and real HWA without hacks wasn't working, and I applied modifications from 2.6.39 source to get the kernel to new standards, so it should work better on ICS. I don't know whether it really fixes the issue, because I haven't tested it yet (don't have a N1 around here, and I don't have a Linux machine with me here atm).
I hope to update it once again to Linux 3.0 kernel in one or two weeks, along with modifications from CodeAurora which got everything running on the DHD too. But for now, this kernel may already fix the issues, but we don't know until we flash 'em
Chaosz-X said:
You mean in the kernel? This kernel is based on Tiamat, and that was the one we were using for ICS, and only tethering through USB (natively) and real HWA without hacks wasn't working, and I applied modifications from 2.6.39 source to get the kernel to new standards, so it should work better on ICS. I don't know whether it really fixes the issue, because I haven't tested it yet (don't have a N1 around here, and I don't have a Linux machine with me here atm).
I hope to update it once again to Linux 3.0 kernel in one or two weeks, along with modifications from CodeAurora which got everything running on the DHD too. But for now, this kernel may already fix the issues, but we don't know until we flash 'em
Click to expand...
Click to collapse
AMAZING news for us N1 owners. We've been waiting for a 3.0 kernel for some time now. True HW Acceleration on ICS ROMs puts a BIG smile on my face!
Great job man.
Sent from my Nexus One using xda premium
Yeah
Now, who wanna try it ?
Sounds very promising, Chaos-X!
What we would need now, however, is for someone to pack this into a boot.img (or flashable zip) for easy installation.
xeloni said:
Now, who wanna try it ?
Click to expand...
Click to collapse
If someone will compile and pack into a flashable zip....I'll test it.
Sent from my Nexus One using xda premium
PHP:
include/linux/types.h:156: error: redefinition of typedef 'dma_addr_t'
/home/zyr3x/android/kernel/222/arch/arm/include/asm/types.h:23: note: previous declaration of 'dma_addr_t' was here
no make
Remove the declaration on line 156 then, seems pretty obvious to me ;p And make sure you're building with -i
this not help, mass errors
This news is great to hear. If I read correctly, hopefully a 3.0 kernel will be on it's way. Finally we will be able to get ICS in full hardware acceleration mode! Long live the N1 and the devs here on XDA!
No luck compiling I assume? :/
Sent from my Nexus One using xda premium
- If you are able to build a zImage, I believe, it is pretty simple to convert it to boot.img. Android provides a host side utility mkbootimg.
- It is build during Android compilation process. It takes the zImage, ram-disk and concatenates them to form boot.img which has a header to identify where kernel starts, where ram-disk starts etc embedded into the boot.img.
Its syntax is:
mkbootimg --kernel <path_of_zImage>/zImage --ramdisk <path_of_ramdisk>
The only thing that needs to be checked is, will the default ramdisk (from any working boot.img) work with new kernel?
From Desire topic:
Think it's almost done... The BCM4329 module caused an error, which took some time to fix, and atm there's an issue in 80211 functionality, and when that's done I think we're pretty close to getting final image
Click to expand...
Click to collapse
Still working on it
This is so exciting, is this all that's standing in the way of full Hardware acceleration?
Well, theoretically no. You could port over all stuff from a 3.0 kernel to a 2.6 kernel regarding HWA, and it could simply work. However, ICS is recommended to work with a 3.0 kernel, and a later version of Android maybe won't even work anymore with a 2.6 kernel, so the earlier we move on to the latest kernel, the better. Even if HWA wouldn't be working in this new build, it certainly will be much easier to fix it, because the entire environment is now ready for a patch for a 3.0 kernel.
Example:
You want the HWA fix from 3.0 in 2.6. You port it (which takes time), and then you see it depends on something else > port that over too. Oh wait, that conflicts with this old snippet of code, fix that...etcetera.
In our new build: the fix is already there and working, or we can simply fix it once, and don't have to worry about 50 other files which got broken dependencies.
BTW, build finished for Desire, uploading it now. If it boots for a Desire, I'm compiling it for the Nexus One too today or tomorrow. Though I will need someone from your community with a CM7 running device, but more info on that coming
Chaosz-X said:
Well, theoretically no. You could port over all stuff from a 3.0 kernel to a 2.6 kernel regarding HWA, and it could simply work. However, ICS is recommended to work with a 3.0 kernel, and a later version of Android maybe won't even work anymore with a 2.6 kernel, so the earlier we move on to the latest kernel, the better. Even if HWA wouldn't be working in this new build, it certainly will be much easier to fix it, because the entire environment is now ready for a patch for a 3.0 kernel.
Example:
You want the HWA fix from 3.0 in 2.6. You port it (which takes time), and then you see it depends on something else > port that over too. Oh wait, that conflicts with this old snippet of code, fix that...etcetera.
In our new build: the fix is already there and working, or we can simply fix it once, and don't have to worry about 50 other files which got broken dependencies.
BTW, build finished for Desire, uploading it now. If it boots for a Desire, I'm compiling it for the Nexus One too today or tomorrow. Though I will need someone from your community with a CM7 running device, but more info on that coming
Click to expand...
Click to collapse
I can try it with MeDroid ICS 4.0.3 V6 if the kernel's theoretically supported.
woozyking said:
I can try it with MeDroid ICS 4.0.3 V6 if the kernel's theoretically supported.
Click to expand...
Click to collapse
Ditto from me.
Sent from my Nexus One using xda premium
theoretically it will work on all devices. In fact, just wait )
i can also test kernel if needed, on any rom suggested by Chaosz-X
Hello People of XDA!
You may have seen this ROM before, but the ports have been messy with files that our device does not use. I have rebuilt this ROM myself using FXP125 Base ROM and the latest JoyOs 1.2.2
During my porting adventure, I ran into alot of problems getting things to work. But after about 20 fresh installs, I managed to get a fully working clean ROM.
The ROM however has one issue. The two lights between the bottom buttons do not work. I don't know why, maybe one of you could shed some light on the subject.
I have NOT Kanged this release BUT feel free to modify and distribute better versions, after all it is open source
Link to download: http://www.mediafire.com/?2dw7h70s2l1u4pe (66.12MB)
Install Procedure: Unlocked Bootloader Only
*Use the backup/restore feature in CWM Recovery to avoid loss of data.
1. Download Ckernel CM7 from here: http://forum.xda-developers.com/showpost.php?p=26638116&postcount=51
*Credit lies with Championswimmer for the Kernel
2. Download this ROM & copy to your SDCard
3. Flash Ckernel CM7 using Flashtools (will add links later)
4. Boot into Recovery and format dalvik cache, cache, data & system
5. Install .zip using CWM Recovery
6. Reboot device and wait for cache to rebuild
7. Do a second reboot for all apps to display. (torch, filemanager)
8. Enjoy
I will probably try and port other ROM's if requests are made.
PLEASE READ OP BEFORE ADDING NOOB COMMENTS. If you dont know how to flash a Kernel or unlock your bootloader, search the forum because its all there.
Bugs
-no hw LED's
-low fps recording on video camera. Photo camera works perfect with auto-focus
-waiting for reports by testers
Thank you for trying my version of this ROM.
NEW KITCHEN!!! Introducing... The Port Hub
I have made my own little basic kitchen to help port roms. If you like porting roms, this maybe useful to you.
http://www.mediafire.com/?31r3wz0z35sgwg4
You dont even need to download base rom, files have been included from FXP125 base, just put your port in the PORT folder and use the One click.bat
If it does not zip the rom, install 7zip before zipping!
Can you port meizu os??
sent from my oodie powered x10i spaceship
1eyedmonster said:
Can you port meizu os??
sent from my oodie powered x10i spaceship
Click to expand...
Click to collapse
Im sorry but I cannot make a port of meizu (flymeOs) because it is based on android 4.0. I am unfamiliar with the 4.0 base at this time. Sorry
can we use doomkernal?
simant said:
can we use doomkernal?
Click to expand...
Click to collapse
nope you cnt use ,use FXP kernel or posted kCernel (link) in OP.. :good:
I am not sure, try it! but make sure to flash wifi modules. Otherwise, try CKernel, it is one of the best kernels.
legzd2010 said:
I am not sure, try it! but make sure to flash wifi modules. Otherwise, try CKernel, it is one of the best kernels.
Click to expand...
Click to collapse
I guess doom kernels are best for stock based rom,those are not for FXP..correct me if i am wrong
angelnaina said:
I guess doom kernels are best for stock based rom,those are not for FXP..correct me if i am wrong
Click to expand...
Click to collapse
I used DoomKernel a while ago, but now to me it feels outdated so I use Ckernel. But DoomLords Kernel is very stable and it may run on this version but I cannot say that I have tried it. but yes, as I am using a FXP base, an FXP based Kernel is needed
Just installed it and soo far soo good I would love to see lewa OS port from you, thx for this rom, smooth and fast, so far no bugs found.
motoman992 said:
Just installed it and soo far soo good I would love to see lewa OS port from you, thx for this rom, smooth and fast, so far no bugs found.
Click to expand...
Click to collapse
Thanks for trying my Rom. I have made a port from lewa earlier today, but there is a bug with the lockscreen resolution. but I will release when this is fixed as everything else works
I have also ported MIUI today and its nice and smooth without any modifications, so a couple of tweeks and I will upload that too
Great news, this joy rom is fasta and everything but i really dont like its UI so i cant wait to change it with your lewa
can u upload Screen Shot ? =.=
Meizu m9 2.3 gb this has already been ported to the htc evo so can it be ported to Ours????
http://www.mediafire.com/?96q6n37nnh2bsoy
Sent from my oodie powered x10i spaceship
can ul port it to locked bl?
I'm aware that there are custom kernels for 5.0 by rumirand and entropy,
but rumirand's kernel is not really 100% compatible with YP-GB70 (KOR) and this is the device that i currently have.
Unfortunately, even in Korea GP forum, there is absolutely no custom kernel for 5.0 (Tegrak Kernel exists for 4.0)
So i wanted to develop it on my own so i've been searching for instructions.
I've instaled ubuntu, installed bunch of stuffs.
but i have no idea how to start. all those guides were incoherent.
can somebody tell me some basic infos and things that i should know for developing YP-GB70 kernel?
I would advice starting with reading about linux kernel structure, how it works etc.
I would like to develop new kernel for 5.0 too
Send from samsung galaxy s wifi 5.0 running paranoidandroid.
search, search, search!
That's what I had to do. I now have a modified, compiled and running kernel with no prior experience. Follow that guide, look at the android site for setting up an environment, etc.
Then you need your source files + initramfs. I don't think samsung has released their initramfs source so you're going to need to find it elsewhere. Samsung stuff is also different than the nexus things that the android site refers to so you need to take bits and pieces of information from places and piece it together yourself. I recommend looking at other kernel builder's githubs too, I've modified others sources and have wound up with good results.
exodus454 said:
search, search, search!
That's what I had to do. I now have a modified, compiled and running kernel with no prior experience. Follow that guide, look at the android site for setting up an environment, etc.
Then you need your source files + initramfs. I don't think samsung has released their initramfs source so you're going to need to find it elsewhere. Samsung stuff is also different than the nexus things that the android site refers to so you need to take bits and pieces of information from places and piece it together yourself. I recommend looking at other kernel builder's githubs too, I've modified others sources and have wound up with good results.
Click to expand...
Click to collapse
yeah that's what i was doing. i managed to extract initramfs from the zimage but dont know what to do anymore :silly:
Do you have any idea if the initramfs is the same between your version and the rest of the world? You might be able to use an already extracted version.
Sent from my YP-G70 using xda premium
exodus454 said:
Do you have any idea if the initramfs is the same between your version and the rest of the world? You might be able to use an already extracted version.
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
yes? i searched github but there weren't any for GB70 (there was g70)
So i just did it by myself, which took me around an hour. Everything was new to me so uploading GB70 initramfs to github took me like 30 mins.:silly:
my next step is to add cwm recovery to the kernel and it;s quite hard. most of the guides written in this forum are usually written for specific devices.
Before you start modifying the kernel, and i suggest you try compiling it to make sure your sources are good.
Sent from my SGP5 with XDA Premium
exodus454 said:
Before you start modifying the kernel, and i suggest you try compiling it to make sure your sources are good.
Sent from my SGP5 with XDA Premium
Click to expand...
Click to collapse
It can't be wrong. I got the zImage from Korean stock rom tar. But you are right. I gotta try decompiling and compiling to make sure
stylemate said:
It can't be wrong. I got the zImage from Korean stock rom tar. But you are right. I gotta try decompiling and compiling to make sure
Click to expand...
Click to collapse
Just a note..you can't decompile a kernel binary. The farthest you can go is extracting the initramfs from it. To get a kernel you would have to build it from source.
Sent from my HTC One S using Tapatalk 2
klin1344 said:
Just a note..you can't decompile a kernel binary. The farthest you can go is extracting the initramfs from it. To get a kernel you would have to build it from source.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
oops seems like i made a noobish term mistake there
i wanted to write unpack but thought that decompile can be used also. Thanks!
Originally Posted by x2kjosh
Hey
So I was able to get the new kernel to build per those directions I posted. It made a bunch of modules too. I'm wondering if with this kernel and the modules it creates if we can port to the CM10 build the EVO 4G lte uses. A thought. It may require further tweaking but it could be a start. I packaged the kernel up with a CM10 HTC ramdisk to make a boot.img file. Ported it to the EVO 4g LTE CM10 ROM and got to the CM Splash screen. I googled the errors I was getting from the logcat and found others had same problems going from ICS to JB so I attempted to add those fixes in but the zip file didnt make correctly
We need help! There has been plenty of talk about aosp but no action! Thanks to mdmower for providing this http://forum.xda-developers.com/showpost.php?p=36523562&postcount=27
Would it be easier to build cm9.1 from source since our latest ota source dropped?
Linch89 said:
Originally Posted by x2kjosh
Hey
So I was able to get the new kernel to build per those directions I posted. It made a bunch of modules too. I'm wondering if with this kernel and the modules it creates if we can port to the CM10 build the EVO 4G lte uses. A thought. It may require further tweaking but it could be a start. I packaged the kernel up with a CM10 HTC ramdisk to make a boot.img file. Ported it to the EVO 4g LTE CM10 ROM and got to the CM Splash screen. I googled the errors I was getting from the logcat and found others had same problems going from ICS to JB so I attempted to add those fixes in but the zip file didnt make correctly
We need help! There has been plenty of talk about aosp but no action! Thanks to mdmower for providing this http://forum.xda-developers.com/showpost.php?p=36523562&postcount=27
Would it be easier to build cm9.1 from source since our latest ota source dropped?
Click to expand...
Click to collapse
If we can find the CM9 source for an HTC MSM8960 based phone, yes, and I'd prefer that first personally...
https://github.com/htc-msm8960
Sent from my Motorola Galaxy s3 using Tapatalk 2
You got a splash screen great ill mix our builds since they are at the same level uf you dont mind
Sent from my ADR6410LVW using xda app-developers app
Josh has it what we're trying to start with is a stable cm9.1 port from another phone the International one x has it same 8960 tree
Anyone want to try and work on this with me?
Yes I want to what do you need I am new but I can learn anything. You need me to and fast
Sent from my ADR6410LVW using xda premium
Hi, i wan't to use the Olympus Kernel Project in MIUI v5 ROM.
¿Is there any way?
Thanks.
_Damian said:
Hi, i wan't to use the Olympus Kernel Project in MIUI v5 ROM.
¿Is there any way?
Thanks.
Click to expand...
Click to collapse
yes. i have not tested the kernel out on that ROM. What you need to do is unpack the boot.img, swap out the existing kernel for the new kernel, pack the boot.img back up, and test it out via fastboot before flashing with the command "fastboot boot insert_img_name_here.img"
Sent from my MB860 using xda app-developers app
I think it has to be a leak or 3.1.10 based rom for the libs, not the one with gingerbread kernel. So you cannot take the miui with old kernel and flash Phoenix kernel. You could also build it from source.
Edit: why is that post more than two weeks old?
Or you can just wait and help testing this guys (aka Hai_Duong and a ghost developer called "santajin") the 3.x kernel under MIUI v5:
http://forum.xda-developers.com/showthread.php?t=2213168&page=34