I'm trying to make a diff of what modifications HTC actually made to the android kernel for the thunderbolt. Problem is that I don't know at what point they forked it. Would they have used kernel/common.git or kernel/msm.git from android.git.kernel.org? They have linux 2.6.32-21 but the 2.6.32 heads from both those repos are 2.6.32-9.
Any help would be much appreciated. Thanks.
Related
Hey everyone,
This is mainly a heads up for kernel devs who are looking to complete an AOSP compatible kernel for the Rezound. Seeing that the Linux and Android trees have finally been merged (at least kernel wise) it should be SLIGHTLY easier to build a working Rezound kernel from source. I'm sure lots of work will have to be put into the process and perhaps Devs will only really be able to backport from 3.3 to a 3.0.x kernel, but this release improves my outlook of CM9 and other AOSP projects for our device.
http://kernelnewbies.org/Linux_3.3#head-b733d694037e0b34ad47e1b5d38ebc4d1bd1d89f
Thanks to all the Rezound devs for their hard work and I look forward to seeing what the future brings.
Best of luck,
DeathByFugu (Josh)
I have googled my butt off to no avail. I would love to know what needs to be modified in the GB source code to use with CM9. If anyone can point me in the general direction it would be greatly appreciated!
Well the big one is you need a kernel that supports it. Look into patching a Linux 2.6.x kernel to 3.0...have fun. After that it will just be trial and error with different libraries and the like.
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!
Hey all,
I thought I knew what I was doing when backporting but now I am lost.
I am trying to integrate Bluez 5.18 into Dirty Unicorns kitkat for my Galaxy note 2. I thought I could copy the backport 3.14 compat, backport includes and the drivers into my kernel source but I am now unsure I am doing it right. If anyone has any info on backporting for android I would really appreciate it. Things I am unsure of is if I am doing it right by copying the files into the kernel source or if I need to use the backport differently.
Any help is greatly appreciated and needed.
Thanks
Brian
Hi all!
I've been looking for resources or tutorials on how to port a custom kernel like franco kernel to a currently not supported device, but seem to not be able to find any.
I'm a programmer myself, although I'm not very familiar with C, I think I'm still comfortable to make some non-drastic changes to the code. I've never worked on kernels or OS before, but it's going to be fun to learn new things. Since my goal is just to port an existing kernel, I think it's not going to be too hard in comparison to adding new features to the kernel.
I currently have a phone with already released OEM kernel source code, and would like to start with porting a custom kernel to it.
Thanks in advance to anyone who can point me to the right direction!