Ok I have my 4.2 sources and jackpot 3.0 master kernel,
android1234567 stated, "
I don't think I made a 4.2 kernel with the radio driver included. The kernel on my GitHub (sultan-kernel-jackpot-3.0) can be used with Android 4.2.X as long as it is built with the Android 4.2 sources/ramdisk (I used CM10.1 sources to build it). The way the kernel is packaged for this device is that the kernel source is built and generates a kernel image, then the kernel image is packaged with the ramdisk and recovery to create a boot.img (which can be flashed to the device). The reason why the current kernel isn't compatible with Android 4.2 is because the ramdisk and other parts of the boot.img (besides the kernel image) are built for Android 4.3 and don't work with 4.2. That means that the kernel source on my GitHub is fully compatible with Android 4.2 but it just needs to be put together with the proper Android 4.2 sources."
I need to turn jackpots 3.0 master kernel into a bootable kernel for slimbean 4.2 to get the FM radio driver working.
https://github.com/sultanxda/sultan-kernel-jackpot-3.0
If someone could point me in the right direction on what to do Id be very happy. I'm using Sultan Kernel r5 now but it doesnt have the FM driver. I want to add this into slimbean 4.2, Any advice would be most welcome.
mrshane88 said:
Ok I have my 4.2 sources and jackpot 3.0 master kernel,
android1234567 stated, "
I don't think I made a 4.2 kernel with the radio driver included. The kernel on my GitHub (sultan-kernel-jackpot-3.0) can be used with Android 4.2.X as long as it is built with the Android 4.2 sources/ramdisk (I used CM10.1 sources to build it). The way the kernel is packaged for this device is that the kernel source is built and generates a kernel image, then the kernel image is packaged with the ramdisk and recovery to create a boot.img (which can be flashed to the device). The reason why the current kernel isn't compatible with Android 4.2 is because the ramdisk and other parts of the boot.img (besides the kernel image) are built for Android 4.3 and don't work with 4.2. That means that the kernel source on my GitHub is fully compatible with Android 4.2 but it just needs to be put together with the proper Android 4.2 sources."
I need to turn jackpots 3.0 master kernel into a bootable kernel for slimbean 4.2 to get the FM radio driver working.
https://github.com/sultanxda/sultan-kernel-jackpot-3.0
If someone could point me in the right direction on what to do Id be very happy. I'm using Sultan Kernel r5 now but it doesnt have the FM driver. I want to add this into slimbean 4.2, Any advice would be most welcome.
Click to expand...
Click to collapse
Read here: http://wiki.cyanogenmod.org/w/Development?setlang=en
Meticulus said:
Read here: http://wiki.cyanogenmod.org/w/Development?setlang=en
Click to expand...
Click to collapse
Thank you, this is a viable source that will help me learn coding and development. I will study and work on building using this guide. :good:
mrshane88 said:
Thank you, this is a viable source that will help me learn coding and development. I will study and work on building using this guide. :good:
Click to expand...
Click to collapse
If you have any more specific questions. Let me know, I'll do my best...
Related
Hello all,
I am just trying a bit around with kernels, I downloaded the kernel source code for HTC Desire HD and I wondered if you just compile the kernel source code if it works under a AOSP ROM.
So actually the question is, what is the difference between a AOSP and Sense kernel from a dev point of view?
Thanks in advance.
You cannot use a sense kernel on an AOSP Rom, but I am sure they have to use some drivers from the published sense kernel source in AOSP builds.
Tubes6al4v said:
You cannot use a sense kernel on an AOSP Rom, but I am sure they have to use some drivers from the published sense kernel source in AOSP builds.
Click to expand...
Click to collapse
Yes, I know I can't use a Sense Kernel on a AOSP and vice versa, but what I want to now what the actual difference is in the kernel itself (which files are different, which kernelsettings etc.)
you can compare them together
I have a general question about building the Android kernel. For understanding purposes, I'm a C/C++/C# developer (and Android application developer), but have little functional knowledge of the Linux kernel.
With regard to porting Android, I'm curious how one builds the latest Kernel. The Android Kernel is not simply the standard Linux Kernel branch, correct? Where does one get the latest "Android" Kernel from? Does Google host a Kernel site as part of AOSP that we can sync with?
Once you have the latest Kernel, is it simply a matter of ensuring the Make file is accurate, adding the appropriate device drivers (as .so files?) for your particular hardware, and performing a Make? Then I assume you can update your device's Kernel with the one you've buildt?
In closing, for example, I'd like to sync the Android 3.0 Kernel, update the drivers necessary for my EVO 4G, build the latest Kernel, and then flash it to my phone. Just looking for some insight as I start getting educated on the topic.
Thanks for any advice you can offer!
Actually, the android kernel is very similar to the linux kernel (well it is based on the linux kernel). You can get the kernel from here: http://source.android.com/source/downloading.html. You can also take a look here: http://elinux.org/Android_Kernel_Download and here: http://elinux.org/Android_Kernel_Features. It will be quite difficult to build a kernel for your device without the source (there's none for 3.0.1 for your device), but you could still build it from a lower kernel version: http://linux.softpedia.com/progDownload/HTC-EVO-4G-Sprint-Kernel-Source-Code-Download-58254.html.
Thanks for the info, Theonew. When you say that it will be difficult for me to build the kernel for an EVO without the source, is that because the vendors (Qualcomm, for example) haven't made source for their devices available, so it's hard to build the drivers (.so files?) that are compatible with the latest kernel?
Shidell said:
Thanks for the info, Theonew. When you say that it will be difficult for me to build the kernel for an EVO without the source, is that because the vendors (Qualcomm, for example) haven't made source for their devices available, so it's hard to build the drivers (.so files?) that are compatible with the latest kernel?
Click to expand...
Click to collapse
HTC hasn't released the source of the kernel v3.0.1 (which comes in Ice Cream Sandwich) for your device (since it's not available for your device...yet at least).
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
DiegoConD said:
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
Click to expand...
Click to collapse
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
shimp208 said:
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
Click to expand...
Click to collapse
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
DiegoConD said:
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
Click to expand...
Click to collapse
The best way to start is use the ARMv6 branch of Cyanogenmod 11, replace the CM 10.1 in the previous linked build guide with cm-11.0 ("repo init -u git://github.com/androidarmv6/android.git -b cm-11.0"), and then to direct the build to use your kernel take a look at this guide on integrated kernel building with Cyanogenmod.
Ok so I have built cm11 for my device (galaxys s 4g), and ported cm11 from another device to (aries -> galaxy s 4g). CM11 has too much going on IMO and I just want pure aosp on my device, the problem is that there are no (recent) aosp roms for my device, or any similar devices.
So how do I port my device to a different flavor of android when there are no roms of that flavor?
What have I tried?
So far I have setup the aosp 4.4 repo to a different folder than my cm11 repo (the build environment files should be the same right?)
I tried using the manifest from the cm11 rom and buidling with aosp,that didnt work it didnt even finish compiling =(.
I browsed the aosp source for other devices by the same manufacturer, but everything looked completely different from what I am used to.
The most helpful guide in this direction sofar has been cyanogenmods guide but it has left me with more questions than answers.
What [I think] I need to know
Custom recovery - aosp doent seem to include a recovery, the cm guide says to start with the recovery. So i need to know if I need to add a custom recovery to aosp, or if i can install aosp roms from twrp without breaking it.
Binaries - It is safe to use the binaries used in CM11 for aosp/any other flavor, or are the binaries flavor specific? (im thinking they are safe to use, but not entirely sure).
Device files - what files should be safe to use for any flavor?
Kernel - Cm builds the kernel when you compile the rom (or so it says), does aosp build the kernel when you build the rom, or do I have to build the kernel separately? Is it safe to say use a CM11 kernel with an aosp rom?
Hi guys, I'm doing a Cyanogenmod 12.1 porting for my device that is unsupported. I can build everything and I get a flashable zip but I'm using a prebuilt stock kernel image extracted from the stock lollipop rom. After flashing, the phone does not boot and It's impossible even to access to logcat, so I think it's a kernel related issue. My question is:
- I have the stock kernel source (v.3.10) given by the vendor
- I have the cyanogenmod kernel source (v.2.69)
Do I have to build the stock kernel or I can build the cyanogenmod one by merging the drivers modules and others stuff?
And if I flash a wrong kernel image can my device become unusable?
I read that is not fair importing built kernel modules from other kernel version, but if I merge the kernel trees, is it the same?
Sorry in advance if my question is a noob question
Well I don't know much about porting roms or kernels though. But with what I've heard flashing the wrong kernels can permanently render your phone useless..
Sent from my Tecno F7 a ...?