Anyone here can u tell me how to create source code of a new device as my device is INFOCUS M680, kernel source.
I have used another device as same board to create source of my device but the kernel source is different. So anyone can tell me how to create kernel source and device tree.
My kernel version is 3.18.19+
U can't "create" kernel sources... If the manufacturer provides the sources, then u can use that and make modifications to it to boot AOSP based roms
Related
I Have a compiled boot.img with me
Do i still need the Device tree to build the ROM from AOSP code ??
does anyone know how can i proceed further ?
Hello XDA Developers
I Wanted To Ask about something confusing
Now To Build An AOSP ROM You Need The Source Code OF The Phone
What I Wanted To Know What's The Difference Between Device Tree And Vendor
And Last Thing If My Phone Running Kernel 3.4.67 Can I Change It To Be Like 3.10.72 (If There's A Source Available )
Sorry For Asking But I Haven't Seen How The Source Looks Like And Thanks In Advance :good::laugh:
This is a defconfig extracted from LYF water F1S LS-5201 ,It is used to compile custom kernel as well as to update it hence we can completely build custom ROM later.
For kernel now we need only defconfig and have it soon kernel will be released with it.
For ROMs we need device tree and vendor tree with system image modifications ,it will next project after this.
You can contribute and ask but this is complete experimental and not stable yet.:laugh:
Link:
https://github.com/mbkasder/LYF-Water-F1S/tree/Defconfig
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
I Have Oreo Based Stock Rom And Its Relevant Device Tree. I Want To Build Latest Version Of Aosp Or LineageOs Then Why Do I Need To Port My Current Device Tree To Newer Android Version. As Far As I Knows Device Tree Is A Hardware Description And Should Not Change With Android Version Because The Hardware Information Is Constant. The Kernel Tree And Vendor Tree Remains Same And Dont Change With Newer Android Version Then Why Device Tree Changes With Newer Android Version.
For Example, The Device Tree Based On Oreo Will Not Work With Android 12 We Need To Port It First.But The Kernel Tree And Vendor Tree Which Was Working In Oreo Will Continue To Work Further Without Any Modification.
Priyanshu jangid said:
I Have Oreo Based Stock Rom And Its Relevant Device Tree. I Want To Build Latest Version Of Aosp Or LineageOs Then Why Do I Need To Port My Current Device Tree To Newer Android Version. As Far As I Knows Device Tree Is A Hardware Description And Should Not Change With Android Version Because The Hardware Information Is Constant. The Kernel Tree And Vendor Tree Remains Same And Dont Change With Newer Android Version Then Why Device Tree Changes With Newer Android Version.
For Example, The Device Tree Based On Oreo Will Not Work With Android 12 We Need To Port It First.But The Kernel Tree And Vendor Tree Which Was Working In Oreo Will Continue To Work Further Without Any Modification.
Click to expand...
Click to collapse
Sometimes the partition structure is changed from one version to the next, this changes the tree in order to compile the ROM with the correct partitioning structure.