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.
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.
I am now starting to read the documentation related to Ubuntu touch and how to build that, any experienced dev want to share some lights on how to build that for our beloved pocophone?
https://docs.halium.org/en/latest/porting/first-steps.html
I'm in
Sent from my beryllium using XDA Labs
thanas said:
I'm in
Click to expand...
Click to collapse
This project uses android 7.1 base, not existing for our phone...
Don't known if we can use 8.1 base...
Device tree is portable but haven't read at all about Ubuntu touch. What about vendor fw?
Sent from my beryllium using XDA Labs
Vendor blobs go in the vendor/ folder in Halium source tree
Thats the info they give...
Contact me on telegram. I will research as well about this. Have a good system however I have space management issues so don't know if I'm able to compile myself. @thanas8
Sent from my beryllium using XDA Labs
Go on guys!
@abhishek987 do you think its possible to port ubuntu touch to pocophone?
Care to help?
@milouk care to participate?
@Shahan_mik3 can you help?
@CosmicDan mind to help?
Well the place project is stopped is here:
This the instructions:
The Device Repository
Next, we’ll fill the manifest with information. Start with your device repository. Create the following line between the <manifest> and </manifest> tags, replacing the information inside the square brackets with your own:
<project path="device/[manufacturer]/[device]" name="[repository name]" remote="[remote]" revision="[revision]" />
Note
The revision attribute may be omitted if the default revision for this remote is the one that you wish to use.
If you’re not sure of your remote, jump down to Remotes.
Dependencies
Now create more lines like the previous, using the cm.dependencies or lineage.dependencies file you found earlier in your device repository. This file lists all of the other repositories that you need to build for your selected device. It’s listed in a fairly straightforward way, so create a line for each of the entries in there using the following template:
<project path="[target_path]" name="[repository]" remote="[remote]" revision="[revision]" />
The target path is found in the repository’s name. The preceding “android” or “proprietary” is omitted and underscores are replaced with slashes. For example, android_device_lge_bullhead goes in device/lge/bullhead.
This is the file builded:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/beryllium" name="android_device_xiaomi_beryllium" remote="los" />
<project path="kernel/xiaomi/sdm845" name="los/android_kernel_xiaomi_sdm845" remote="los" revision="pgz-14.1-eb8" />
<project path="vendor/xiaomi" name="proprietary_vendor_xiaomi" remote="them" />
<project path="device/xiaomi/sdm845-common" name="android_device_xiaomi_sdm845-common" remote="los"/>
</manifest>
And this is the error:
[email protected]:/media/x/x/hal$ ./b.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/xiaomi/beryllium/lineage.mk]]: "build/target/product/product_launched_with_o_mr1.mk" does not exist. Stop.
Device beryllium not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_xiaomi_beryllium
Traceback (most recent call last):
File "vendor/cm/build/tools/roomservice.py", line 263, in <module>
default_revision = get_default_revision()
File "vendor/cm/build/tools/roomservice.py", line 117, in get_default_revision
return r.replace('refs/heads/', '').replace('refs/tags/', '')
AttributeError: 'NoneType' object has no attribute 'replace'
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/xiaomi/beryllium/lineage.mk]]: "build/target/product/product_launched_with_o_mr1.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/xiaomi/beryllium/lineage.mk]]: "build/target/product/product_launched_with_o_mr1.mk" does not exist. Stop.
Don't have a product spec for: 'lineage_beryllium'
Do you have the right repo manifest?
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/xiaomi/beryllium/lineage.mk]]: "build/target/product/product_launched_with_o_mr1.mk" does not exist. Stop.
Device beryllium not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_xiaomi_beryllium
Traceback (most recent call last):
File "vendor/cm/build/tools/roomservice.py", line 263, in <module>
default_revision = get_default_revision()
File "vendor/cm/build/tools/roomservice.py", line 117, in get_default_revision
return r.replace('refs/heads/', '').replace('refs/tags/', '')
AttributeError: 'NoneType' object has no attribute 'replace'
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/xiaomi/beryllium/lineage.mk]]: "build/target/product/product_launched_with_o_mr1.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/xiaomi/beryllium/lineage.mk]]: "build/target/product/product_launched_with_o_mr1.mk" does not exist. Stop.
Don't have a product spec for: 'lineage_beryllium'
Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
following for any update....
I hope you guys succeed... I heard it is quite difficult to port ubuntu touch for not supported device and people face many errors so they give it up. BTW i don't know anything about rom development. I am a total noob.
But best wishes to you guys
Anyone wanting to join glad to hear
Sent from my beryllium using XDA Labs
This sounds like a great idea. I am following the ubports community since a long time and just love the project. I cross my fingers that you succeed. I can't offer any help as I am lacking the brain capicity to code but my thoughts are with you. As @ tejjoshii already said, I also believe the porting processs is super complicated.
Have you heard of Maru OS. It's based on lineage os and debian or ubuntu. The building process seems pretty straight forward. You just need to patch the lineage os files with the maru os files. As our device sadyl doesn't have hdmi out we could usegoogle chromecast to mirror it to a screen (that#s how they do it with the nexus 5x)- Maybe that would be for the meantime a good alternative. It combines the good two worlds of android and linux. When you connect it to a screen it boots up a full linux system. It's fully open source At the moment the htc 10, samsung galaxy s9, nexus 5 and nexus 5x and some other devices are supported.
https://groups.google.com/forum/#!forum/maru-os-dev
https://maruos.com/#/
Gave up on it too much effort to do alone since it's no Android to Android port. I'll reconsider if anyone contributes
I know it's not exactly ubuntu touch but I am running a recent Ubuntu installed alongside the Android through UserLAnd app. My phone is not even unlocked/rooted (the app uses proot). Thanks to the fast built-in storage on our phone, it's actually running quite decently. The xfce4 desktop is quite usable and so are the more demanding programs like gimp, inkscape, libreoffice, rawtherapee. The speed is comparable to my older iMac with the i5 processor. As you don't get a direct display access, you start X through vncserver and connect to it through an android vnc client. It's cool that it basically acts just like another android app so you get to enjoy the best of both worlds. It's too bad we can't easily connect our phone to and external monitor like I could with my old galaxy S5.
I've been running a linux distro on my phones for more than 7 years and for me it's one of the coolest things about android - that you can reuse existing linux kernel to run a full linux distribution.
You might want to have a look at this thread:
https://forum.xda-developers.com/poco-f1/help/maru-os-pocophone-t3900651
Maybe we have soon Linux (Debian) and lineage os up and running on our beloved pocophone. Connect it to a screen via chromecast and you'll have a proper convergence experience. One of the devs of the maru OS team is interested to port for the poco
Can someone explain what would maru OS offer that is not already available through UserLAnd?
dsvilko said:
Can someone explain what would maru OS offer that is not already available through UserLAnd?
Click to expand...
Click to collapse
Please correct me if I'am mistaken I don't have much experience with userland. When you run linux through userland can you mirror it to a big screen? But I believe the difference is that when you start Linux through userland you can't use the android part of the phone at the same time. Is that correct?
With Maru OS I believe it's different. Once you connect your phone with a cable or wirelesse solution to a screen it automatically boot up full linux distro (people are running ubuntu and debian at the moment and some seem keen to experiment with kde). Yo can use still the android part of your phone as regular, do phone calls etc.?
Here is an older video to give you a rough idea:
https://www.youtube.com/watch?v=iF7yK7HAyVM
Here is also a great interview with one of the main devs at latenight linux.
https://latenightlinux.com/late-night-linux-episode-59
You might also want to read though the posts in their dev group:
https://groups.google.com/forum/#!forum/maru-os-dev
Hey I've been trying to port Ubuntu touch to the A10 following the official guide located here. I've found the device repository for the a10 here, and vendor blobs here. So the XML manifest file I ended up with is this:
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="a10_remote" fetch = "https://github.com/geckyn" revision="lineage-16.0"/>
<project path="device/samsung/a10" name="android_device_samsung_a10" remote="a10_remote"/>
<project path="kernel/samsung/a10" name="android_kernel_samsung_exynos7885" remote="a10_remote"/>
<project path = "vendor/samsung/a10" name="proprietary_vendor_samsung_a10" remote="a10_remote"/>
</manifest>
The "./halium/devices/setup a10" command exits with no errors. But then when I run "breakfast a10", I get the following output:
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "cm_a10". Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
Device a10 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for a10 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your lo
cal_manifests/roomservice.xml.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
** Don't have a product spec for: 'lineage_a10'
** Do you have the right repo manifest?
The A10 doesn't have an official Lineage OS port, in my knowledge, so I understand that there would be no reference to it on Lineage's GitHub. And I don't mention this repository in my manifest. Why do I get this error then?
Hi, The official support of lineageOS 17.1 for the Samsung galaxy a10 at this time is not released.
You can use the source code of the unofficial port of lineageOS in this thread here : https://forum.xda-developers.com/t/...7-1-for-galaxy-a10-exynos-unofficial.4146815/
section Source Code.
I'm glad you're taking the time to wear this phone model, I've been waiting for a portage for a long time!
I'm french, sorry for my english.
Sundev79 said:
Hi, The official support of lineageOS 17.1 for the Samsung galaxy a10 at this time is not released.
You can use the source code of the unofficial port of lineageOS in this thread here : https://forum.xda-developers.com/t/...7-1-for-galaxy-a10-exynos-unofficial.4146815/
section Source Code.
I'm glad you're taking the time to wear this phone model, I've been waiting for a portage for a long time!
I'm french, sorry for my english.
Click to expand...
Click to collapse
Yeah I'm using the unofficial sources. The error I had above was apparently because of an uncompleted checkout. I am now stuck at another error while building. The entire output from make is here - https://pastebin.com/aznxR9rW. I'd be delighted if you could help.
I working on it, i trying to building halium on lineage-17.1 branch.
Ok, can you help-me, i have this error while launch the command breakfast :
Code:
[email protected]:~/halium-10.0$ breakfast a10
device/samsung/a10/BoardConfig.mk:153: error: device/samsung_slsi/sepolicy/sepolicy.mk: No such file or directory
15:23:39 dumpvars failed with: exit status 1
Device a10 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for a10 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
device/samsung/a10/BoardConfig.mk:153: error: device/samsung_slsi/sepolicy/sepolicy.mk: No such file or directory
15:23:41 dumpvars failed with: exit status 1
device/samsung/a10/BoardConfig.mk:153: error: device/samsung_slsi/sepolicy/sepolicy.mk: No such file or directory
15:23:43 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_a10'
** Do you have the right repo manifest?
[email protected]:~/halium-10.0$
I don't know much about halium 10. I'm building using Halium 9 and Lineage OS 16 sources. I've been able to build halium-boot.img successfully. I'm not the right person to ask as I haven't made a port before. I can make a log of all the steps I took with Halium 9 if you want. @Halium on Telegram will probably be the best place for clarifications. Good luck!
Hi ! do you have succeeded to a bootable build ? what tour advancement ?
Hi, were you able to carry it at the end ?? I am wanting to use ubuntu touch and I only found this thread related to that