I want to build a custom ROM (CosmicOS) for my device (ZenFone Selfie, Z00UD, supports all Z00T roms).
I've already found a proper device tree, but I'm unsure about kernel and vendor trees I'm about to use.
Kernel:
https://github.com/LineageOS/android_kernel_asus_msm8916
Vendor:
https://github.com/TheMuppets/proprietary_vendor_asus
Am I using proper kernel and vendor trees?
The reason why am I asking this question is because I couldn't find a kernel tree for my processor (MSM8939) in Lineage OS' github and Asus' vendor's proprietary has no Z00T subfile.
you need proper device trees...send me the link for device trees and is your phone has any current rom supported...if yes paste a link
govind1233 said:
you need proper device trees...send me the link for device trees and is your phone has any current rom supported...if yes paste a link
Click to expand...
Click to collapse
Device tree:
https://github.com/LineageOS/android_device_asus_Z00T
Supported ROMs:
https://forum.xda-developers.com/zenfone-2-laser/orig-development/rom-cyanogenmod-14-0-t3459745
https://forum.xda-developers.com/zenfone-2-laser/development/rom-resurrection-remix-n-t3509698
https://forum.xda-developers.com/zenfone-2-laser/development/rom-viper-os-v2-1-t3640026
There are even more of them, of course
As I said before, my phone (ZenFone Selfie, Z00UD) supports all ROMs that support Z00T variant of device (ZenFone 2 Laser)
Also, a source code of ROM I want to build:
https://github.com/Cosmic-OS
Take the same kernel as the devs use to build for Z00T and vendor of Asus from Muppets...it will be no problem if it won't vendor of Z00T...and also include the common trees of ur device...while building...and for vendor just create a file named vendorsetup.sh in ur device trees...
govind1233 said:
Take the same kernel as the devs use to build for Z00T and vendor of Asus from Muppets...it will be no problem if it won't vendor of Z00T...and also include the common trees of ur device...while building...and for vendor just create a file named vendorsetup.sh in ur device trees...
Click to expand...
Click to collapse
So you say that the kernel tree I've included in this thread is proper one, right? Or should I download the one from ASUS?
Yes...and try including common trees also
govind1233 said:
Yes...and try including common trees also
Click to expand...
Click to collapse
This?
https://github.com/LineageOS/android_device_asus_msm8916-common
darkeyes22 said:
This?
https://github.com/LineageOS/android_device_asus_msm8916-common
Click to expand...
Click to collapse
Yes
govind1233 said:
Yes
Click to expand...
Click to collapse
Thank you
Now this:
https://pastebin.com/Nc4yzCNi
Any suggestions?
Related
Hi guy's!
I am BlackFoxy, and i start make sources for ASUS Zenfone 2 Laser
But i need help
If you can, please help me
I in Facebook - https://www.facebook.com/misha.scvorzov
Device sources and more you can see on my GitHub Profile - https://github.com/BlackFoxy757
M here !
Love to help @Shanmugam k @Sujeet Ranipa
What exactly do you need help with?
hardslog said:
What exactly do you need help with?
Click to expand...
Click to collapse
Help with make kernel and correct device and vendor tree
BlackFoxy757 said:
Help with make kernel and correct device and vendor tree
Click to expand...
Click to collapse
Ok I'll give you a little information
1) There is a very highly likely chance that the laser-auto-focus will not work. Of course we don't know until we try but I am not confident because getting things like that which are not in common android source code is very difficult to get working.
2) There are many versions of the ZF2 laser, some come with different kernels therefore will need sources for each kernel (potentially). They also might share the same source (won't know unless I take a good look at it)
3) I am downloading the Kernel source for the ZE551KL and will upload it to github for a starting point. You can easily fork it from there into your github repo. It should be up in a day or less. By the looks of your github repo, you have a different model (one with a 410 snapdragon). Kernel sources are available from the asus.com website under support. You can download it from there for now and I can show you how to upload it to github.
4) If you plan on supporting all the ZF2 laser models, I would suggest for the device repos to make a "common" repo as they will share a lot of the same code, then have separate repos for each model for all the unique characteristics of them.
Edit: kernel uploading to my github. Internet is slow but you can see it soon by going to https://github.com/Hardslog/android_kernel_asus_zf2l
hardslog said:
Ok I'll give you a little information
1) There is a very highly likely chance that the laser-auto-focus will not work. Of course we don't know until we try but I am not confident because getting things like that which are not in common android source code is very difficult to get working.
2) There are many versions of the ZF2 laser, some come with different kernels therefore will need sources for each kernel (potentially). They also might share the same source (won't know unless I take a good look at it)
3) I am downloading the Kernel source for the ZE551KL and will upload it to github for a starting point. You can easily fork it from there into your github repo. It should be up in a day or less. By the looks of your github repo, you have a different model (one with a 410 snapdragon). Kernel sources are available from the asus.com website under support. You can download it from there for now and I can show you how to upload it to github.
4) If you plan on supporting all the ZF2 laser models, I would suggest for the device repos to make a "common" repo as they will share a lot of the same code, then have separate repos for each model for all the unique characteristics of them.
Edit: kernel uploading to my github. Internet is slow but you can see it soon by going to https://github.com/Hardslog/android_kernel_asus_zf2l
Click to expand...
Click to collapse
Yes. I think supported all Z2L
Thank you... we are waiting for you
How is it going?
do you can please creat a custom rom for ze500kl
BlackFoxy757 said:
Yes. I think supported all Z2L
Click to expand...
Click to collapse
There is already a custom ROM for Z00T and Z00L, and I think you should make one for a device that don't have it. Like Z00ED. Also I think you need to have the device so you can test it. No one likes broken ROMs
But.... Why u need make source for zen 2 laser?
Cyanogen have source for this.... And some device already custom.... Only ze500kl don't have.... But i think can use source of msm8916-common !
Hey guys, today after a long time i came back around to this subforum to see if there are any news for my yoga 2 380f but all i found were closed threads?! wtf happened?
after so many months of waiting one could finally unlock the bootloader and install a custom recovery - but now even the posts in these threads are empty.... why?
I am in the mids of gathering all the files that I did manage to get before they were removed. My tab is 1050f. Have all the stuff somewhere fore it
Sent from my SM-G901F using Tapatalk
I suspect a New dedicated forum
New TWRP 2.8.7.0 for YT2 1050 soon !
Hello !
Was CLOSED because not respected XDA rules about GPL !
Almost all work here on XDA require open source code ... he preferred to erase everything he did here instead to provide source code
About TWRP :
A recovery image does contain a Linux kernel which is under GPLv2, and the TWRP source code is under GPLv3 (see the license header in https://github.com/omnirom/android_b...d-6.0/twrp.cpp)
Click to expand...
Click to collapse
On the other hand, tomorrow I'll provide a new TWRP 2.8.7.0 UI 6.0 for Yoga Tablet 2 1050 !
I already managed to fix kernel issue on Stock Lenovo Kernel Android L .
I already pushed all my work on my github : twrp-yt2 for TWRP 2.8.7.0 and also for kernel ! I'll update kernel very soon , because right now is stock one .
Also in a short time I'll try to make a cm-13.0 for our device .
Best regards !
surdu_petru said:
Hello !
Was CLOSED because not respected XDA rules about GPL !
Almost all work here on XDA require open source code ... he preferred to erase everything he did here instead to provide source code
About TWRP :
On the other hand, tomorrow I'll provide a new TWRP 2.8.7.0 UI 6.0 for Yoga Tablet 2 1050 !
I already managed to fix kernel issue on Stock Lenovo Kernel Android L .
I already pushed all my work on my github : twrp-yt2 for TWRP 2.8.7.0 and also for kernel ! I'll update kernel very soon , because right now is stock one .
Also in a short time I'll try to make a cm-13.0 for our device .
Best regards !
Click to expand...
Click to collapse
Can I ask what device you are using as a Base or are you building a vendor folder from scratch
Thanks for your work. Looks like you have implemented pixel finger, I will try this later
pug1 said:
Can I ask what device you are using as a Base or are you building a vendor folder from scratch
Thanks for your work. Looks like you have implemented pixel finger, I will try this later
Click to expand...
Click to collapse
Yes, was started from scratch... should be OK for all YT2.
Also pixelflinger for _X86 are implemented, twrp works fine. ... and sure will work on stock Lenovo kernel for Android L.
Best regards.
I take it you will solve the vendor blobs as you build to find them out?
I have twrp 3.0.0-0 source so will try with that.
You said the kernel is solved? It will build if I sync your github? Have you built a kernel yet? If so what toolchain are you using? I couldn't get it to build as it could find my toolchain.
From the branch 5.1 on your github, it won't work with cm13 source?
Again thanks for your work matey
pug1 said:
I take it you will solve the vendor blobs as you build to find them out?
I have twrp 3.0.0-0 source so will try with that.
You said the kernel is solved? It will build if I sync your github? Have you built a kernel yet? If so what toolchain are you using? I couldn't get it to build as it could find my toolchain.
From the branch 5.1 on your github, it won't work with cm13 source?
Again thanks for your work matey
Click to expand...
Click to collapse
Kernel and also twrp must be compiled along with cm-12.1.
As I already said , my kernel source cannot be compiled ...( Lenovo do not provide a complete one ), but I'll update today later in order to fix all Lenovo issues.
Best regards.
New TWRP 2.8.7.0 for YT2 - 1050 ! Source code already available !
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890
Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:
Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you
any news @rrvuhpg ?
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !
Hello Folk,
i am Going to build custom roms for le 2 (x526) . But as of core requirement to build any custom rom , first i need 3 source codes which are
1)Kernel Sources (I have that)
2)Device tree sources (Hoping for someone to build this)
3)Vendor Tree sources (Again, we dont have that too)
So if you are serious about custom roms them support me and Ask for any experienced developer to Get these two Tree sources .
umangloria said:
Hello Folk,
i am Going to build custom roms for le 2 (x526) . But as of core requirement to build any custom rom , first i need 3 source codes which are
1)Kernel Sources (I have that)
2)Device tree sources (Hoping for someone to build this)
3)Vendor Tree sources (Again, we dont have that too)
So if you are serious about custom roms them support me and Ask for any experienced developer to Get these two Tree sources .
Click to expand...
Click to collapse
the kernel source you have is it working ???????????/
coz last i heard they removed it officially from their open source site coz they were not correct
Akhil16 said:
the kernel source you have is it working ???????????/
coz last i heard they removed it officially from their open source site coz they were not correct
Click to expand...
Click to collapse
they have removed from their site for all le Mobiles so i hope these are working .
umangloria said:
Hello Folk,
i am Going to build custom roms for le 2 (x526) . But as of core requirement to build any custom rom , first i need 3 source codes which are
1)Kernel Sources (I have that)
2)Device tree sources (Hoping for someone to build this)
3)Vendor Tree sources (Again, we dont have that too)
So if you are serious about custom roms them support me and Ask for any experienced developer to Get these two Tree sources .
Click to expand...
Click to collapse
This mobile contains snapdragon 652, which is rare currently in devices. So i don't think anyone has bring up device tree for this device. I am looking to purchase this device and then do some stuff for it, let's see if i bought it.
This might be helpful https://youtu.be/Uw_caMHZRC4
Looking for the Device Tree, Kernel, and Vendor for this tablet.
I am just learning. Is there a process for getting these from an existing tablet?
Thank you!
Darran
I found the device tree for the a similar tablet here:
https://github.com/Matshias/twrp_android_device_tb_8504x
Someone on reddit told me this:
If you can find something with similar specs and the same processor you can try adapting it to your device. The Samsung Note 4 and the S5 use the same sources with some minor adjustments. I've had good luck getting some kernel sources from Samsung just by contacting them and asking, but they're the only brand I have any experience with.
For vendor files you can try TheMuppets found here: https://github.com/TheMuppets
Or you can try to extract them yourself using this guide- https://wiki.lineageos.org/extracting_blobs_from_zips.html
Best of luck to you.
Click to expand...
Click to collapse
Is this sound advice?
drizzle123 said:
Someone on reddit told me this:
Is this sound advice?
Click to expand...
Click to collapse
Device tree and vendor are not the problem. Kernel source code is the thing that is required. Was going to buy tab4 10 but won't if lenovo is not willing to release the kernel source. I've repeatedly asked them to do so in the forums but they never reply. Maybe try mailing lenovo support and see if that helps...
thank you - do you know if they have a dev support e-mail or is it the standard support e-mail?
Your kernel sources are already available. Its included in the kernel of Tab 4 8 Plus.
yener90 said:
Your kernel sources are already available. Its included in the kernel of Tab 4 8 Plus.
Click to expand...
Click to collapse
Is a seperate defconfig specifically for tab4 8 available ?
skoar said:
Is a seperate defconfig specifically for tab4 8 available ?
Click to expand...
Click to collapse
Yes.
yener90 said:
Yes.
Click to expand...
Click to collapse
Nice. I never downloaded the source to check. Then doing a bringup should be easy
Where is the source that you all reference?
Probably part of this? https://forum.xda-developers.com/th...m-lineageos-16-0-lenovo-tab-3-8-plus-t3923143
drizzle123 said:
Where is the source that you all reference?
Probably part of this? https://forum.xda-developers.com/th...m-lineageos-16-0-lenovo-tab-3-8-plus-t3923143
Click to expand...
Click to collapse
Some things will match others need to be modified as per the non plus model. Vendor files can be extracted from the device and the device tree can be set up by referencing the plus model since they are not too different. As per the kernel try prebuilt first and see if it boots
drizzle123 said:
Where is the source that you all reference?
Probably part of this? https://forum.xda-developers.com/th...m-lineageos-16-0-lenovo-tab-3-8-plus-t3923143
Click to expand...
Click to collapse
Bad choice. You need a device tree from a device with Snapdragon 425 (MSM8917)
yener90 said:
Bad choice. You need a device tree from a device with Snapdragon 425 (MSM8917)
Click to expand...
Click to collapse
This device tree looks to have a Snapdragon 425 (MSM8917)
drizzle123 said:
This device tree looks to have a Snapdragon 425 (MSM8917)
Click to expand...
Click to collapse
Tab4 8 plus has snapdragon 625. Go to gsmarena and search by snapdragon 425 and you'll get a few devices then go from there and see if they have a custom rom. If they do then find the device tree for that device from github and modify it as required. For vendor extract it from the device. There are quite a few tutorials on xda. As for kernel download the one provided by lenovo for tab4 8 plus (it'll work for non plus model as well). As for defconfig extract it from boot.img again there are tutorials available.
I'll probably try to get los running on the tab4 10 later
I found the kernel and some associated files here:
https://pcsupport.lenovo.com/us/en/...ntent=20190613_20190613184825&linkId=68972849
I found a similar an MSM8917 Device Tree here:
https://github.com/redmidevs/android_device_xiaomi_rolex
I looked through muppets and didn't find any vendor files for the TB-850 or any TB devices. Will work on extracting the vendor files and getting them up on muppets. Can I use the extract-files.sh file from lineage to extract the vendor files for the TB-850?
https://github.com/TheMuppets/proprietary_vendor_lge
drizzle123 said:
I found a similar an MSM8917 Device Tree here:
https://github.com/redmidevs/android_device_xiaomi_rolex
I looked through muppets and didn't find any vendor files for the TB-850 or any TB devices. Will work on extracting the vendor files and getting them up on muppets. Can I use the extract-files.sh file from lineage to extract the vendor files for the TB-850?
https://github.com/TheMuppets/proprietary_vendor_lge
Click to expand...
Click to collapse
A good choice. Vendor files should be from the same device like device tree.
Use this one:
https://github.com/redmidevs/android_vendor_xiaomi_rolex/tree/lineage-15.1
You need just the camera blobs blobs from your device. But you can do this later.
More important are the firmware files because those are unique for every device.
Replace thos files with the one on your device:
https://github.com/redmidevs/androi...tree/lineage-15.1/proprietary/vendor/firmware
I suggest you to build Lineage15.1 first. The kernel works with Android 8.1.
Thank you for the guidance - looking to give this a try today
@highwaystar_ru @yener90 @codeworkx
I know this is not the place to ask but I haven't gotten any response from the places I was supposed to ask so bear with me
I'm building los 16 for lenovo tab4 10
I've setup the the device tree and vendor and am using prebuilt kernel but while building it stops at 69% with the following error
[ 69% 65628/93948] //vendor/lineage/build/soong:generated_kernel_includes generate
FAILED: /home/skoar/android/lineageos/out/soong/.intermediates/vendor/lineage/build/soong/generated_kernel_includes/gen/.dummy_dep
/home/skoar/android/lineageos/out/soong/host/linux-x86/bin/sbox --sandbox-path /home/skoar/android/lineageos/out/soong/.temp --output-root /home/skoar/android/lineageos/out/soong/.intermediates/vendor/lineage/build/soong/generated_kernel_includes/gen --copy-all-output -c 'make -j CFLAGS_MODULE="-fno-pic" -C O=__SBOX_OUT_DIR__ ARCH=arm64 CROSS_COMPILE="/usr/bin/ccache aarch64-linux-androidkernel-" CROSS_COMPILE_ARM32="arm-linux-androideabi-" headers_install' && touch /home/skoar/android/lineageos/out/soong/.intermediates/vendor/lineage/build/soong/generated_kernel_includes/gen/.dummy_dep
make: *** O=/home/skoar/android/lineageos/out/soong/.temp/sbox985711399: No such file or directory. Stop.
sbox command (make -j CFLAGS_MODULE="-fno-pic" -C O=/home/skoar/android/lineageos/out/soong/.temp/sbox985711399 ARCH=arm64 CROSS_COMPILE="/usr/bin/ccache aarch64-linux-androidkernel-" CROSS_COMPILE_ARM32="arm-linux-androideabi-" headers_install) failed with err "exit status 2"
[ 69% 65635/93948] //frameworks/base:gen-platform-proto-constants generate
ninja: build stopped: subcommand failed.
11:35:26 ninja failed with: exit status 1
Soooo any ideas ???
Here are the repositories I am setting up
https://github.com/darran-kelinske-fivestars/android_device_lenovo_tb8504f
https://github.com/darran-kelinske-fivestars/android_vendor_lenovo_tb8504f
https://github.com/darran-kelinske-fivestars/android_kernel_lenovo_tb8504f
tb8504 kernel looks like can be built with this config https://github.com/HighwayStar/andr...rm64/configs/msm8937_p3588_pcb-perf_defconfig Changes after splitting can be intergrated in 8953 kernel from lenovo-devs org.
vendor blobs and common device tree can be used from here https://github.com/lenovo-devs only some hals has to be renamed or replaced with ones name msm8937 instead of msm8953