It seems like with so many different manufacturers some kernel sources or android sources would be leaked/released by now. I found some Kernel sources for a RK3368 device the Geekbox. They have Android Marshmallow and Kernel sources on their github here.
I'm wanting to add some features to the kernel or at least have an upgrade path versus having to buy a new radio next year. Main things i'm wanting are kernel tweaks for performance and different usb devices like an audio DAC, or newer wifi/bluetooth module. I bought a spare damaged radio. I'm going to see if i can get a kernel to boot.
Related
Can I use the stock kernel (Froyo) and the binary drivers that comes with the stock and use the aosp source code and build higher version of the platform (gingerbread, icecream ) as and when they are available?
Why do the kernel needs a change when upgrading from one version of android to another, the hardware doesn't change anyway.
tutysara said:
Can I use the stock kernel (Froyo) and the binary drivers that comes with the stock and use the aosp source code and build higher version of the platform (gingerbread, icecream ) as and when they are available?
Why do the kernel needs a change when upgrading from one version of android to another, the hardware doesn't change anyway.
Click to expand...
Click to collapse
OKAY LET´S GO MAN
you can´t port a kernel from froyo to ginger for example because the kernels are created with diferents codes...
if you want to create a custom kernel from a stock kernel you needs the "privative drivers" and the source code for to do this... gingerbread has another source code than ice cream (still closed source)
the same thing happens with AOSP (cyanogenmod for example) but they uses a pure LINUX code for to create a custom kernel..
AOSP also needs the source code of the android version for that are creating the kernel.
and the kernel need to be changued between android versions because are not compiled of equal way.
ext4, task admin... and H/W don´t works equal between android versions
Hi, may I ask somebody experienced with ROM building, if it is possible to build fully functional and stable build from AOSP sources if i have kernel sources for my device from vendor?
Nigfire said:
Hi, may I ask somebody experienced with ROM building, if it is possible to build fully functional and stable build from AOSP sources if i have kernel sources for my device from vendor?
Click to expand...
Click to collapse
Hi, yes. I've compiled lollipop nexus4 from aosp in ubuntu 14.04.1 x64 in vmware.
I've downloaded the source, included the proprietary files, and compiled android, compiled with make and make otapackage to generate the zip.
After that i've rooted the device, installed twrp.
Finally, i've downloaded the source kernel and compiled to generate the .img. I've flashed this to the device with fastboot, and
yeeeeeeh perfect!!!
obviously, after this, i've downloaded the gapps and installed.
But, which version would you compile? And which device? All the sources are available and open source?
i wana make AOSP build for Huawei Ascend G6, I have only kernel sources from vendor... I suppose that kernel will work with any version of android or not?
Nigfire said:
i wana make AOSP build for Huawei Ascend G6, I have only kernel sources from vendor... I suppose that kernel will work with any version of android or not?
Click to expand...
Click to collapse
Ok, you have the sources, very good.
mmm, i'm not sure that every kernel + android combinations work perfectly together.
For example, on my nexus4 i've kernel 3.4 and lollipop. Now, if android lollipop requires some modules/functionalities/"other magic stuff" to work properly from the kernel, and you install kernel 2.x.x without this feature, probably you'll have problems.
I mean, i'm not sure, but is only a logic hypothesis.
You can solve this problem using the latest official version of android from Huawei and your compiled kernel from Huawei sources. If this works, try to update android to another version with a custom rom. It works? Perfect!, It not works? Damn, restore the backup and use another older android version
To build android/kernel you must transform into a researcher :laugh:
I, on behalf of the owners of the Karbonn Titanium S5 Plus device, based on the Mediatek MT6582 chipset, need some help in building a kernel source (not a kernel from source) for this device. I have a few fully working custom ROMs, a Github Account, some forked repositories of other devices having the same chipset but minorly-different hardware, and some time. What do I have to do to get to building a kernel source for this device?
It is a dual-sim device, based on the Mediatek MT6582 SoC, having a prebuilt kernel version 3.4.5, with no kernel sources even for its clone, running Android Jelly Bean 4.2.2 . @superdragonpt had created some new kernels for some devices(eg. the Wiko Darkmoon, MT6582, he created a new kernel source and a new kernel) having no previous kernel sources, how can I do the same for my device?
The Android One devices (Indian) are based on the same chipset, and have the same features. But, the difference is that they have a smaller 5MP rear camera and a locked bootloader, while ours has a 8MP rear camera and an unlocked bootloader. Can their sources be used for my device?
Also, after creating a Kernel source, how can I create an AOSP source for this device? Please help me out with this.
Hi there,
All things about your device is in this thread:
[ROMs and Recoveries] Karbonn Titanium S5 Plus/ S5 + - All Things And Dev.
Take a close look there and see if you find an answer there.
Good luck
I know, I started that thread.
It contains many Roms for my device, but there are no updates for them because it does not have a kernel source. There are no new kernels for the device because a kernel source was not released by the company. So, I asked it here.
I forked the kernel source from another device having the same soc, but I wanted to know how to create one specifically for my device.
One more thing. How do you build a kernel from a kernel source? Please help me out. Thanks in advance.
You can learn more about kernel development here:
[GUIDE] Build Your Own Android Kernel{Easiest and Fastest Way] [Using The NDK]
[TUTORIAL][VIDEO]Build your own Android kernel
I suggest reading a couple of the relevant kernel tutorials found here: http://forum.xda-developers.com/chef-central/android
Good luck
Thread closed
Hi all,
I want to build my first rom. I'm a software developer (Java and Web), but my Linux knowledge is somewhat intermediate.
I have a Moto G4 Plus laying around. Here's what I have done so far:
1. Downloaded the AOSP source from Google for android-7.0.0_r15 (Nougat)
2. Found the Kernel Source for the Moto G4 Plus (Nougat)
I'm stuck at adding the device's kernel source to the AOSP source. How do I combine the two?
Here's the link for the kernel source: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPJS25.93-14-10
I've tried looking this up online but the results are very limited.
As far as I understand this kernel source provides everything I need to make the ROM compatible with my device, right?
Could someone point me to the right direction?
Much appreciated.
I'm new to the android build system but have been running stripped kernels for years. I'm working on a custom rom for a TCL A30 (MT6762/MT6765).
I've looked at the AOSP code base and TCL source, for a similar device, and it looks like the TCL source generates the needed kernel .config file with scripts. There are multiple scripts for different archs and cellphone carriers. My TCL A30 has a Bangkok_CC (ConsumerCellular) tag and I found arch/arm64/configs/bangkok_TF_defconfig (TracFone). There do not appear to be any patches in the TCL source. The source I found:
TCL-Mobile on sourceforge
Has the Tracfone TCL A3:
Tracfone TCL A3x product link
That source contains Bangkok_TF_defconfig.
I was able to adb pull /proc/config.gz directly from the device and it's running 4.19.126+ released last month.
First question: Can I generate a bangkok_CC_defconfig from /proc/config.gz in the AOSP code base? It is mosttly monolithic
Code:
cat .config | grep =m > kernel_modules.txt
CONFIG_IKHEADERS=m
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_SERIAL_OF_PLATFORM=m
CONFIG_BATTERY_MT6359=m
CONFIG_SND_SOC_MT6359_ACCDET=m
CONFIG_USB_DUMMY_HCD=m
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PLTFM=m
CONFIG_MMSTAT_TRACER=m
At the time of this post the latest upstream is 4.19.244
Second question: Are most Android projects like Debian/RHEL where they back patch kernel vulnerabilites? Would the most up-to-date kernel result from the latest AOSP source and would building it just be a matter of dropping in my /proc/config.gz and setting the build environment that I found in the TCL source?
I suspect that AOSP is contributing back to kernel.org. Third question: AOSP vs Kernel.org source? Does Google backport like RHEL/Debian? Or would I get a more recent,, secure kernel using upstream kernel.org source?.
Last question Clang vs GCC. I've just setup my Arch Linux build box w/ arm64_gcc. Speed is less important to me than stable builds. What are the arguments for one compiler over another?