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
Related
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).
Hi.
I am a noob, not a techy
just curios - how can your devs build ICS roms when Samsung themselves did not build/create/honed/refined the Vibrant for Android 4?
What I am trying to ask is, how can your devs manage to control the hardware via android 4, if Samsung did not supply the codes/drivers/source?
Thanks
I'm not 100% sure but I think I read somewhere you can use the source code to build a ROM and then they used the Gingerbread bootloader/kernel and from there it's debugging.... again I could be wrong.
I think they took the source, and compile the source with the characteristics of the device. then applications that do not work, modified or exchanged for other versions of other rom, like the kernel, and other modifications, which is why the rom, there are many versions which fix bugs Version earlier after many users try it. (an example of this is the ICS Passion, which is now in its version 13)
Well passion is based on cm9. Which is aosp rom using source code android releases. Basically if you have drivers for hardware and a device tree you can use that source to build for any device.
Wherelse Samsung roms are usually not directly from source but just modded firmware from Samsung leaks. Oems do use close sources drivers though, usually better and get more out of hardware.
Sent from my SGH-T959 using XDA App
I have a HTC One X, and I'd like to build a custom ROM for it.
But I'm not sure how different are the kernel source code from CyanogenMod and the kernel source code provided by HTC? For example, are there some CyanogenMod specific kernel modules?
I couldn't find much information on Google, and I think running a diff might be too much work to do.
Thanks!
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...
Are there any ROMs, based on the leaked kernel sources below?
https://github.com/rmtew/MediaTek-HelioX10-Kernel
All the ROMs, I've seen are based on prebuilt kernel.
Until we havent full kernel source we had to use prebuilt kernel. Nofearnohappy is trying to complete the source. Now its booting but still some things is broken
I would like to port SailfishOS, but for that I need the build the kernel from source.
On Nofearnohappy's github you can find source but i think it's not worth to spend so much time on building not fully functional rom