NEW:
Working .34-rc3 kernel available at http://forum.xda-developers.com/showpost.php?p=6290443&postcount=45
OLD:
Code:
This is an experimental .34-rc2 kernel for the Nexus One.
Provided in the zip file is a folder (2.6.34-rc2-termana-nexusone) and the kernel (zImage).
It is extremely experimental, so only follow this if you [B][I][U]really[/U][/I][/B] know what your doing and know how to reflash another kernel back to make it boot again if it doesn't boot. I'm not responsible if your device curls over and dies.
Use adb to push the folder into /system/lib/modules/ and then use fastboot to flash the kernel.
The kernel is a rebase of cyanogen's .33.1 kernel to the latest .34-rc2 kernel. So nothing particularly new about it, besides the satisfaction that not many people would be running this kernel version on devices.
Zip file: bit.ly/94Oo6m (To download it click the link next to the text "Save file to your PC:")
Edit: Being a new member of xda-developers forum, it wouldn't let me post the link properly, but just copy and paste it and you'll be fine.
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
I just flashed the zimage, and the phone went into a boot loop. Do I have to install anything else?
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Will give it a go nad logcat it
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
thanks, thought it was a mistake that you said push that folder, glad you clarified it for me
thanks again
jlevy73 said:
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
Click to expand...
Click to collapse
damn, that is long; won't bother reading that thing
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
I used this:
adb push 2.6.34-rc2-termana-nexusone /system/lib/modules/2.6.34-rc2-termana-nexusone
Click to expand...
Click to collapse
...and it still went into a boot loop for me.
hotweiss said:
I used this:
...and it still went into a boot loop for me.
Click to expand...
Click to collapse
You sure that wouldn't create a folder within a folder?
Not really sure just saying...
So is this working for you Termana?
I tried both have the subfolder and just pushing all the files to /modules and both produced a bootloop
i pushed the folder to /system/lib/modules/ and flashed zimage, but just get bootloop
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
I seriously thought, you tested it on your Nex before posting it....was a missunderstanding.
Termana said:
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
Click to expand...
Click to collapse
Did you cross compile the source against the ARM source?
hotweiss said:
Did you cross compile the source against the ARM source?
Click to expand...
Click to collapse
You might need to rephrase your question as the way you've said it doesn't let me know exactly what you mean by "ARM source". Do you mean using the Android ARM toolchain or what?
To anyone that is willing to help me test:
New build available at - bit.ly/c1tFqg (just the zImage, don't worry about pushing the modules for now)
Info:
This is a .33.1 kernel not a .34-rc2 kernel HOWEVER, I wanted to get the source that I'm rebasing off tested to make sure it boots, because if the source I'm pulling from doesn't boot, then obviously my rebases aren't going to either. So, please test it and tell me if it boots, if it does, I'll have another .34-rc2 kernel build up shortly after. If it doesn't, I may have to try rebasing from the official .32 kernel rather than the current source I'm rebasing from at the moment (which is .33.1).
Booted for me.
Code:
2.6.33.1-cyanogenmod
[email protected] #1
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Justin241982 said:
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Click to expand...
Click to collapse
I wouldn't post it yet. The first one he posted doesn't boot and the second one he posted I don't believe has any optimizations.
I've been digging through the Vibrant forums for a while now, and I would like to try my hand at building the Froyo release. I downloaded the source and can compile the kernel just fine, but the platform part I am in the dark. Could someone help me with how to build the platform part? Once I get that done, I'll dig around to see how to convert it over to a flashable zip. Thanks in advance.
Slashazard said:
I've been digging through the Vibrant forums for a while now, and I would like to try my hand at building the Froyo release. I downloaded the source and can compile the kernel just fine, but the platform part I am in the dark. Could someone help me with how to build the platform part? Once I get that done, I'll dig around to see how to convert it over to a flashable zip. Thanks in advance.
Click to expand...
Click to collapse
Hey. I myself learning to build my own custom rom too!
Sent from my SGH-T959 using XDA Premium App
The platform source has not been released (and never will be). Only kernel source is required to be released.
Sent from my SGH-T959 using XDA App
In the source package there is a platform tar file. Do I download the AOSP code and overwrite those folders with what was in the platform tar from Samsung? Then build like AOSP?
go into android developement section here on xda or Ask some of developers here, if u ask nicely i think they might help u.
If i wanted to add the volume fix to an exsisting kernel how could i go about that? Is it located in the lib/modules? I have a bit of experience with this but wanted to make sure.
You need to pull the source from bit bucket for the kernel you want to use. Once you have the source tree downloaded, modify the code with the fix, then compile it. You will have just created the Zimage which in combination with RAMDisk creates the boot.img.
It is far from a easy task.
DroidTh3ory said:
You need to pull the source from bit bucket for the kernel you want to use. Once you have the source tree downloaded, modify the code with the fix, then compile it. You will have just created the Zimage which in combination with RAMDisk creates the boot.img.
It is far from a easy task.
Click to expand...
Click to collapse
Whats the fix? A line of code that has to be added? I may wanna play around tonight.
fixxxer2008 said:
Whats the fix? A line of code that has to be added? I may wanna play around tonight.
Click to expand...
Click to collapse
Here is the code....
http://code.tiamat-dev.com/7x30/htc...7760b9641d9c24af6787cc53f993f16455314cb/diffs
It has been merged into IMO 's latest kernel as well as in the modded kernel in my A05P ROM.
Sent from my PUR3 A05P using XDA App
The proyect its now opensource, can anyone compile this? like a stand alone app so we can install it in any tablet?
https://github.com/Onskreen/cornerstone
Thx
It is unfortunately not that simple. CornerStone has parts that come as patched system files.
It needs to either be included in a ROM or come as a patch (.zip) for a specific ROM.
cyansmoker said:
It is unfortunately not that simple. CornerStone has parts that come as patched system files.
It needs to either be included in a ROM or come as a patch (.zip) for a specific ROM.
Click to expand...
Click to collapse
I tried patching a few rom-s but with no success...
Anybody got it working?
Hi,
first of all, i know that it is prohibited to do that for public roms, but i want to do it for my own builds.
Until CM11 it was pretty easy to integrate. But how can i do that during build time with CM12?
Any advices, how to integrate the package?
Cheers and Thanks
Saint.
With CM plan to separate its self from Google completely they have made it just about impossible. Not to mention you would have to rewrite the whole built script
zelendel said:
With CM plan to separate its self from Google completely they have made it just about impossible. Not to mention you would have to rewrite the whole built script
Click to expand...
Click to collapse
Hi,
thnx for the answer at first, hmmmm it thing it should not be that hard, the updater script of the tools would need to be attached to the updater-script of the rom and all the stuff would have to be put into the source itself, the question is where to put it to?