Develop Bugs

Adding Note 4 to lineage OS

I have successfully completed the repo sync process for lineage-17.1 build
I have executed the command lunch lineage-trlte-userdebug to add SM-n910G device to my lineageOS build.
Returns this error
Code:
build/make/core/product_config.mk:223: error: Can not locate config makefile for product "lineage".
10:46:02 dumpvars failed with: exit status 1
Device lineage not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for lineage 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.
build/make/core/product_config.mk:223: error: Can not locate config makefile for product "lineage".
10:46:04 dumpvars failed with: exit status 1
build/make/core/version_defaults.mk:56: warning: Invalid TARGET_PLATFORM_VERSION 'userdebug', must be one of
build/make/core/version_defaults.mk:57: error: QP1A.
10:46:05 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage'
** Do you have the right repo manifest?
But the device is already avaiable under the following link
https://github.com/LineageOS/android_device_samsung_trlte-common
Please correct/advise what am I missing here.

Trying to build lineageos 18.1 for one plus one

Hi guys!
So I was following this https://wiki.lineageos.org/devices/bacon/build wiki to build a lineageos 18.1 ROM for my one plus one.
Unfortunately, when I get to the step for "breakfast bacon", I get the following errors.
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/target/product/product_launched_with_k.mk:2: error: _nic.PRODUCTS.[[device/oneplus/bacon/lineage_bacon.mk]]: "device/oppo/msm8974-common/msm8974.mk" does not exist.
22:35:04 dumpvars failed with: exit status 1
Device bacon not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_oneplus_bacon
Default revision: lineage-18.1
Checking branch info
Checking if device/oneplus/bacon is fetched from android_device_oneplus_bacon
LineageOS/android_device_oneplus_bacon already fetched to device/oneplus/bacon
Syncing repository to retrieve project.
sh: 1: repo: not found
Repository synced!
Looking for dependencies in device/oneplus/bacon
Looking for dependencies in device/oppo/msm8974-common
device/oppo/msm8974-common has no additional dependencies.
Looking for dependencies in kernel/oppo/msm8974
kernel/oppo/msm8974 has no additional dependencies.
Done
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/target/product/product_launched_with_k.mk:2: error: _nic.PRODUCTS.[[device/oneplus/bacon/lineage_bacon.mk]]: "device/oppo/msm8974-common/msm8974.mk" does not exist.
22:35:05 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/target/product/product_launched_with_k.mk:2: error: _nic.PRODUCTS.[[device/oneplus/bacon/lineage_bacon.mk]]: "device/oppo/msm8974-common/msm8974.mk" does not exist.
22:35:06 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_bacon'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
What am I doing wrong?
p.s. if I do a "breakfast d855", then I get no error.

My utter apologies for being so blind.
It is of course clearly written on that wiki that some devices would fail upon "breakfast" command being called due to the missing vendor files.
Hence one should first run "extract-files.sh" in the device specific folder. And indeed afterwards the breakfast command succeeds for "bacon".
I could be given a little margin for being a noob and also that my other device "d855" does not need extract-files.sh before breakfast.
Also what confused me yesterday was, that the paths contained oppo when infact I was building for bacon. I was sure something is wrong upstream.
My sincere apologies again for starting on xda with such a useless post.

Asus Zenfone 3 LineageOS 17.0

Hi guys,
I'm trying to build my own rom for my asus zenfone 3 on LineageOS 17.0, I followed these instructions (https://wiki.lineageos.org/devices/zenfone3/build) and now I'm stuck to breakfast zenfone3 command.
I have extract my proprietary blobs with the extract-files.sh and manually clone these repo into :
~/android/lineage/kernel/kernel/asus/msm8953/ <- https://github.com/LineageOS/android_kernel_asus_msm8953 (i also create a branch locally for lineage-17.0)
~/android/lineage/device/asus/zenfone3 <- https://github.com/LineageOS/android_device_asus_zenfone3
When I am try to do a breakfast i get these errors :
Bash:
~/android/lineage$ breakfast zenfone3
device/asus/zenfone3/BoardConfig.mk:212: error: cannot assign to readonly variable: PRODUCT_BOOT_JARS
09:47:09 dumpvars failed with: exit status 1
Device zenfone3 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_asus_zenfone3
Default revision: lineage-17.0
Checking branch info
Checking if device/asus/zenfone3 is fetched from android_device_asus_zenfone3
LineageOS/android_device_asus_zenfone3 already fetched to device/asus/zenfone3
Syncing repository to retrieve project.
Fetching: 100% (1/1), done in 0.259s
Garbage collecting: 100% (1/1), done in 0.005s
repo sync has finished successfully.
Repository synced!
Looking for dependencies in device/asus/zenfone3
Looking for dependencies in kernel/asus/msm8953
kernel/asus/msm8953 has no additional dependencies.
Looking for dependencies in packages/resources/devicesettings
packages/resources/devicesettings has no additional dependencies.
Done
device/asus/zenfone3/BoardConfig.mk:212: error: cannot assign to readonly variable: PRODUCT_BOOT_JARS
09:47:12 dumpvars failed with: exit status 1
device/asus/zenfone3/BoardConfig.mk:212: error: cannot assign to readonly variable: PRODUCT_BOOT_JARS
09:47:13 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_zenfone3'
** Do you have the right repo manifest?
Thanks !

If you actually get it working, can you please share it? Thanks!

Need help building LineageOS 16.0

Hello everyone, this is my first post on XDA Forums. I'm trying to build LineageOS 16.0 for a Samsung Galaxy W (GT-I8150), but I'm running into some trouble. I'm following this guide since It's the only good guide I found, but when I run breakfast GT-I8150 as the guide says, it throws build/make/core/product_config.mk:234: error: Can not locate config makefile for product "GT". since this device wasn't and isn't supported by LineageOS, so the repos aren't available wherever it's looking for. They are available elsewhere, but not in the official repos, so it can't find the stuff it needs. For this reason, I need to make breakfast search elsewhere. I already have the links needed, I just don't know how to let breakfast look in those repos.
Device I'm building for: Samsung Galaxy W (GT-I8150)
OS I'm using for the build: Ubuntu Desktop 20.04.4 LTS
CPU architecture: x86_64
This is the complete output of breakfast GT-I8150:
Code:
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "GT".
13:18:45 dumpvars failed with: exit status 1
Device GT not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for GT 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.
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "GT".
13:18:46 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "GT".
13:18:47 dumpvars failed with: exit status 1
** Don't have a product spec for: 'GT'
** Do you have the right repo manifest?
I also don't have a roomservice.xml file so I can't modify that either. If anyone has a better guide for building LineageOS 16 then please post it.

Pixel Experience 12 for Moto Z2 Play albus

I know development stopped for this phone but I was looking to see how difficult it would be to build my own ROM with PE 12 following this guide and it appears I need some binaries but I have no idea how to get that so I am failing here:
Code:
[email protected]:~/android/pe# source build/envsetup.sh
including vendor/aosp/vendorsetup.sh
[email protected]:~/android/pe# lunch aosp_albus-userdebug
02:35:02 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:02 dumpvars failed with: exit status 1
Device albus not found. Attempting to retrieve device repository from PixelExperience-Devices Github (http://github.com/PixelExperience-Devices).
Found repository: device_motorola_albus
Checking branch info
Calculated revision: twelve
Branch twelve not found
02:35:05 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:05 dumpvars failed with: exit status 1
02:35:07 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:08 dumpvars failed with: exit status 1
** Don't have a product spec for: 'aosp_albus'
** Do you have the right repo manifest?
Any idea how difficult it is to get past this and to get a PE 12 ROM built for this device? I assume once I get the binaries I would also need to modify some code and a bunch of files...

nmajin said:
I know development stopped for this phone but I was looking to see how difficult it would be to build my own ROM with PE 12 following this guide and it appears I need some binaries but I have no idea how to get that so I am failing here:
Code:
[email protected]:~/android/pe# source build/envsetup.sh
including vendor/aosp/vendorsetup.sh
[email protected]:~/android/pe# lunch aosp_albus-userdebug
02:35:02 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:02 dumpvars failed with: exit status 1
Device albus not found. Attempting to retrieve device repository from PixelExperience-Devices Github (http://github.com/PixelExperience-Devices).
Found repository: device_motorola_albus
Checking branch info
Calculated revision: twelve
Branch twelve not found
02:35:05 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:05 dumpvars failed with: exit status 1
02:35:07 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:08 dumpvars failed with: exit status 1
** Don't have a product spec for: 'aosp_albus'
** Do you have the right repo manifest?
Any idea how difficult it is to get past this and to get a PE 12 ROM built for this device? I assume once I get the binaries I would also need to modify some code and a bunch of files...
Click to expand...
Click to collapse
You are missing all the trees for the device; as you seem to have no clue i'd recommend you at least start by building A11. A12 won't boot on albus without significant modifications to the rom, which PE has not included in it's upstream.
For building a rom you need:
The rom structure (Duh)
The device tree (usually called device_brand_codename, in this case device_motorola_albus and store in device/motorola/albus to be properly detected)
The kernel tree (which usually inherits the name of the SOC, in this case msm8953 and goes into kernel/msm8953)
Vendor tree (which follows the same naming convention as device tree and goes in vendor/motorola/albus)

marcost22 said:
You are missing all the trees for the device; as you seem to have no clue i'd recommend you at least start by building A11. A12 won't boot on albus without significant modifications to the rom, which PE has not included in it's upstream.
For building a rom you need:
The rom structure (Duh)
The device tree (usually called device_brand_codename, in this case device_motorola_albus and store in device/motorola/albus to be properly detected)
The kernel tree (which usually inherits the name of the SOC, in this case msm8953 and goes into kernel/msm8953)
Vendor tree (which follows the same naming convention as device tree and goes in vendor/motorola/albus)
Click to expand...
Click to collapse
Thanks for the reply, and yea maybe I’ll start with PE 11 then. Would building that provide the trees for the device or how do you go about getting those? I did read about the modifications needed for PE 12 to get around the iptables drop but willing to mess with it and only plan to use this phone for the projector mod.

nmajin said:
Thanks for the reply, and yea maybe I’ll start with PE 11 then. Would building that provide the trees for the device or how do you go about getting those? I did read about the modifications needed for PE 12 to get around the iptables drop but willing to mess with it and only plan to use this phone for the projector mod.
Click to expand...
Click to collapse
Given the fact that this device had official PE 11 support, those trees (for A11) would be hosted on the PE-Device github. The vendor tree however would be hosted in their gitlab (or you can generate it with the device tree, by having the device plugged in and running extract-files