I know that this source is not Lineage but I would think the basic principles for building for an supported device under Lineage would also be applicable to any other source repository.
All of the guides I have found only tell you how to build for a supported device and not any help for an unsupported one. I figured out how to sync a suitable device tree and kernel etc but since the rom source repository does not support my device I can't go any further. I can't get it to build from my sync'd local sources it keeps trying to pull stuff from the original source repository so builds fail at the start.
I have setup a local manifest for this project that sync's the device tree and a kernel and the proprietary blobs and this sync completes without error. next I ran - source build/envsetup.sh and then brunch hlte (not a supported device I know) but that throws up this error -
build/core/product_config.mk:248: * Can not locate config makefile for product "gzosp_hlte". Stop.
Device hlte not found. Attempting to retrieve device repository from GZOSP-Devices Github (http://github.com/GZOSP-Devices).
Repository for hlte not found in the GZOSP-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/gzosp_manifest.xml
build/core/product_config.mk:248: * Can not locate config makefile for product "gzosp_hlte". Stop.
So I think that the error basically means that github.com/GZOSP-Devices does not have the hlte device listed so can anyone tell me how to make the build point to my local repository after I have sync'd so that it at least starts to build ?
I am a newbie to rom building and have much to learn but I would really appreciate any help you guys could give.
Thanks in advance for any an all help offered.
Related
I have been following the XDA Guide on porting roms found here: http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code
I am stuck at the point where I am supposed to fork the device's proprietary vendor files.
What I am trying to do is Port Omnirom for the international S3 to the US (d2lte).
This is my first attempt at a port. I can not find the the proprietary vendor files on the CM github as labelled in this guide. Have they changed the format or am I missing something now that there are unified builds?
Any help appreciated as I am clueless how to proceed without being able to fork the proprietary vendor files.
Thanks
TheMuppets is the place to look:
https://github.com/themuppets
Hi, I am new to the entire developing community, and so I apologize in advanced for my noobish question. So I am building CM 12.1 for the Galaxy Avant for learning purposes and to use a stable lollipop rom as my daily driver. I have been following a tutorial to build the software, but I am stuck on the "lunch" part of the tutorial. Every time I try to "lunch" my device, I receive the following error:
build/core/product_config.mk:234: *** Can not locate config makefile for product "afyonltetmo". Stop.
Device afyonltetmo not found. Attempting to retrieve device repository from CyanogenMod Github (h tt p://github. com /CyanogenMod).
Repository for afyonltetmo not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:234: *** Can not locate config makefile for product "afyonltetmo". Stop.
** Don't have a product spec for: 'afyonltetmo'
** Do you have the right repo manifest?
What do I do?????? Can someone give me a detailed explanation on what to do and how? Please help. And again, sorry for the noobish question.
So I have been at my wits end the last couple days trying to figure out exactly what's going on. I have a BLU Life One 2015, (X011Q) which is unsupported on basically every custom ROM/recovery/whatever. There is no repo for it on github, (except my own, which I'm having trouble with, and is the point of this post) no released device tree (if I'm using the right word), the only source code released for it is for the kernel on Android 4.4.4.
This far, I've extracted the required files from the boot.img (I also have the recovery.img and build.prop) using a guide I found on XDA University to build CWM out of the cyanogenmod source code. (I can't post the link to this guide, unfortunately, because I'm too new a user)
Everything in that tutorial goes fine (though it might be worth noting i have to use obbtool instead of otatools) until I get to the point where I have to run "lunch full_’device_name-eng" (For me, this is: lunch full_BLU_LIFE_ONE-eng). When I do, I run into this:
Code:
build/core/product_config.mk:245: *** Can not locate config makefile for product "full_BLU_LIFE_ONE". Stop.
Device BLU_LIFE_ONE not found. Attempting to retrieve device repository from CyanogenMod Github (http //github.com/CyanogenMod).
Repository for BLU_LIFE_ONE not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:245: *** Can not locate config makefile for product "full_BLU_LIFE_ONE". Stop.
build/core/product_config.mk:245: *** Can not locate config makefile for product "full_BLU_LIFE_ONE". Stop.
** Don't have a product spec for: 'full_BLU_LIFE_ONE'
** Do you have the right repo manifest?
In case this is helpful:
From build.prop
Code:
ro.product.brand=BLU
ro.product.device=BLU_LIFE_ONE
Files that were extracted with mkvendor.sh:
Code:
AndroidBoard.mk
AndroidProducts.mk
BoardConfig.mk
cm.mk
device_BLU_LIFE_ONE.mk
kernel
recovery.fstab
system.prop
My main thought is that I'm lacking a device tree, but after searching for others, I wonder what else would be in one, and if the files I've got don't constitute some part of the device tree.
TL;DR
Do I need to create a device tree myself for a device that has no support yet whatsoever for any kind of custom ROM/Recovery? And if so, how?
Any and all help is greatly appreciated.
Hi guys. Im trying to compile Resurrection Remix based on lolipop for my HTC Desire 620. I have downloaded RR sources, device, kernel and vendor also - github.com/bartek2017
My roomservice.xml
Code:
<manifest><project name="bartek2017/android_kernel_htc_a31ul" path="kernel/htc/a31ul" remote="github" revision="cm-12.1"/><project name="HTC-MSM8916/android_device_htc_a31ul" path="device/htc/a31ul" remote="github" revision="cm-12.1"/><project name="bartek2017/proprietary_vendor_htc" path="vendor/htc/a31ul" remote="github" revision="master"/></manifest>
Firstly after typing ". build/envsetup.sh" and "lunch" I don't see any option to choose RR for this HTC. I think it's probably because I havent created any new folder in "device/generic/..." but I dont know what should be in "AndroidProducts.mk" and "vendorsetup.sh". Secondly I also dont know if I have to change anything in "device/htc/a31ul/" files like cm.mk or cmdependencies.mk
And this error below - ??? In sources there is nothing like "device/htc/msm8916...". After creating this folder I got something similiar to Cycle detected.
Code:
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/htc/a31ul/cm.mk]]: "device/htc/msm8916-common/msm8916.mk" does not exist. Stop.
Device a31ul not found. Attempting to retrieve device repository from CyanogenMod Github (CyanogenMod).
Repository for a31ul not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/htc/a31ul/cm.mk]]: "device/htc/msm8916-common/msm8916.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_a31ul'
** Do you have the right repo manifest?
Please help me. I'll be thankful for any tip. I really want to learn how to compile roms but Im stuck
Hello, can someone give me a hint, howto build Lineage (based on the work of @SyberHexen) on my own?
I think the most work is done, but I wan't to dig a bit deeper into it.
I know there are several guides, specific to one device but I don't know how to include the sources of SyberHexen.
Thanks!
Setup your build environment with Java and all the required packages. Setup repo and grab the source code. Clone the device, kernel and vendor trees. Go through the steps to initialize your build system then build the ROM.