Some minor info on porting a custom ROM. - General Questions and Answers

Hey devs. I've worked with some ROMs and now I'm willing to port Blisspop ROM for my device. And all I have is the official kernel source, AOSP device source codes and some vendor codes using scripts. Now my questions are:
1. Are these data enough to start building the ROM?
2. I tried it using AOSP and CyanogenMod 5.1.1r3. But I always keep getting some files missing or compiler issues.
3. How do I apply patches from a URL?(I'm not fond of git)
4. Any link to a tutorial can be provided.
Additional info:
I'm working on Ubuntu 14.04 x64 LTS in VirtualBox.
Allocated 4 cores and 4gb RAM.
I'm porting it to an x86 arch device.
VHD size is 400gb.
And the kernel source is said to work with AOSP 4.4.2 though it functioned will with AOSP 5.1.1r3.
Also I followed several guides but most of them are for arm devices. And did not workout for me.
Kindly help me out guys.

Related

Need Help To Configure Android Kernel For BA

I am trying to compile android from source and here's my setup : -
-> Ubuntu latest on VirtualBox With all latest updates required from compiling along with source and kernel.
I need to know how to configure android kernel menuconfig for Htc BlueAngel.
Can any one point out some good tutorials for it where I can learn how to compile and configure Android kernel ?

[Q] Building stable rom with kernel sources

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:

[Q] Building first ROM from AOSP non Nexus, a couple of questions

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.

How do I build a kernel tree? Where do I start?

So I wanna compile a custom kernel for my device. For example, I want to make elementalX or maybe a hydra kernel for my device. But I need a kernel tree for my device, and due to my device being too unknown... nobody has made one. So could you link a guide of video showing step by step how to build a kernel tree?
A good reference can be found here:
[REFERENCE] How to compile an Android kernel
Introduction Hello everyone, I will be going over how to compile a kernel from beginning to end! Prerequisites: A Linux environment (preferably 64-bit) Knowledge of how to navigate the command line Common sense A learning spirit, there will be...
forum.xda-developers.com
And here:
Building Kernels | Android Open Source Project
source.android.com

Linux 6.3 supports our phone!

With the release of mainline Linux 6.3, you can find initial support for our phone (and many other Snapdragon 625/632/450 devices).
This is very, very "initial support" - for example, the display doesn't work. But it boots!
I'm continuing to add support for more functionality, but this is an important milestone that I wanted to share.
You can find the device tree at `arch/arm64/boot/dts/sdm450-motorola-ali.dts`
linux/arch/arm64/boot/dts/qcom/sdm450-motorola-ali.dts at master ยท torvalds/linux
Linux kernel source tree. Contribute to torvalds/linux development by creating an account on GitHub.
github.com
wow Bro I really like if all works on 6.3
Uclydde said:
With the release of mainline Linux 6.3, you can find initial support for our phone (and many other Snapdragon 625/632/450 devices).
Click to expand...
Click to collapse
It's the device tree source to build a dtb. But you still need a Kernel and a running build.

Categories

Resources