Hi there.
I wanted to know is the proprietary blobs and device/vendor tree different for each version of Android (like nouget vs Android o)?
Can a properly working proprietary blobs and device/vendor tree for Android 7 be used to port or build Android 8 based ROM once the latest version of Android comes out for full deployment?
Related
Dear all,
I was wondering, if I build Android from the AOSP source (and build in all the kernels etc. so it works on my LG G4), will all the security patches be applied by Google, or will I have to do it manually?
Thanks for your help (I'm new to building custom roms)
Hi..,
I am trying to build a Android O based custom rom for my device (Moto X Force /Droid Turbo2 i.e Kinzie) which has very little custom rom support and development support too.. Till now it has only Unofficial LineageOS14.1
Device Tree for Android 7.1 : https://github.com/lineageos-for-kinzie/android_device_motorola_kinzie
Vendor Tree for Android 7.1:
https://github.com/lineageos-for-kinzie/android_vendor_motorola_kinzie
I want to make this Device Tree compatible for Android 8.1 development but doesn't know where to start from.
If anybody can help and give his guidance then please share to this thread
I think it's best to start from the clark phone. LineageOS 15 is already out for clark and they have a very similar device tree.
I currently have an old TAB E sm t561. I want to compile android 11 for it. It's device tree ,vendor tree, common tree version is lineage os 15 I.e android 8
Its kernel source is lineage os 12 that is lollipop. Can i compile android 11 lineage os 18 rom?
nothing is impossible with *unix but thinking all the issue and troubleshooting that would come along the way i would say this is stupid idea ...
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?
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.