yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Uldiniad:
you can install unofficial builds from threads like this: https://xdaforums.com/redmi-note-3/...dmi-note-3-t3739187/post75757671#post75757671 (just need to google lineage os 15.1 kenzo)

you can check with the official maintainer for your device if he's working on getting lineage-15.1 branch going: https://wiki.lineageos.org/contributors.html

you can contribute code yourself to get the device up-to-date for oreo: https://wiki.lineageos.org/contributing.html

you can fork all required repos and make your own lineage-15.1 branch and make your personal builds

you might get some help from here: https://webchat.freenode.net/?channels=lineageos-dev

this is the status of your device on LineageOS official review repo: https://review.lineageos.org/#/q/kenzo
[Android Software/Hacking General [Developers Only]] Jain2vicky@gmail.com:
my device doesn't have lineage os 15.1 yet?

how can i build an unofficial build for myself.

no lineage os 15.1 branch for my device exist??
[Android Software/Hacking General [Developers Only]] Uldiniad:
as I said in my post above, unless you find (by searching on Google) someone else (most likely on GitHub) that has a lineage-15.1 branch for your device (because your official LineageOS maintainer has not uploaded one yet on the official repos) you won't be able to unless you make your own branch and update the code yourself. Some links that I posted should help you to get started. In modding communities you're generally on your own. Lots of learning if you want to make your own builds. I've been working at it for over two years now and am still a noob in many ways, but I've learned how to make some stuff for myself by researching a lot, and making lots of mistakes.
[Android Software/Hacking General [Developers Only]] Uldiniad:
I've never seen this kind of error. seems like it is waiting for the next set of instructions but for some reason there is none. Google will be the most helpful in this case. Or maybe some people on the official LineageOS IRC chat.

If you're certain that your build environment on wsl is the same as your ubuntu/mac environment (with the exceptions/additions in my OP) and you know for a fact that the builds for your device on branch lineage-15.1 run fine on those environments then I am lost.

WSL is slower than native ubuntu on I/O but running it trough VM might be slowing it to death. That's the only reason I could see that it would fail on wsl on VM but that it would succeed on native mac/ubuntu. You could always go to wsl github and post an issue for your current situation (they'll ask you for a strace), but if the issue is too localized they probably won't help.
[Android Software/Hacking General [Developers Only]] taxueliuyun:
"WSL is slower than native ubuntu on I/O but running it trough VM might be slowing it to death" this sentence gave me help. I allocated 2G memory and 1 cpu to Windows 10 in virtualbox. So I changed the configuration: 8G memory and 4 cpu. After this, I build the code, the error has gone. The ninja files generated finished, source code begin compile. However, compile speed, really slow.

Finally, thank you very much for your help.
[Android Software/Hacking General [Developers Only]] Uldiniad:
Glad I was able to help. There's a reason why I put 16GB RAM as the first thing in my OP ;)
[Android Software/Hacking General [Developers Only]] Mcenzie:
[ 0% 97/86614] //frameworks/compile/mclinker/lib/Script:libmcldScript yacc ScriptParser.yy

FAILED: /home/mcenzie/android/lineage/out/soong/.intermediates/frameworks/compile/mclinker/lib/Script/libmcldScript/android_arm64_armv8-a_kryo_static_core/gen/yacc/frameworks/compile/mclinker/lib/Script/ScriptParser.cpp /home/mcenzie/android/lineage/out/soong/.intermediates/frameworks/compile/mclinker/lib/Script/libmcldScript/android_arm64_armv8-a_kryo_static_core/gen/yacc/frameworks/compile/mclinker/lib/Script/ScriptParser.h

BISON_PKGDATADIR=external/bison/data prebuilts/misc/linux-x86/bison/bison -d --defines=/home/mcenzie/android/lineage/out/soong/.intermediates/frameworks/compile/mclinker/lib/Script/libmcldScript/android_arm64_armv8-a_kryo_static_core/gen/yacc/frameworks/compile/mclinker/lib/Script/ScriptParser.h -o /home/mcenzie/android/lineage/out/soong/.intermediates/frameworks/compile/mclinker/lib/Script/libmcldScript/android_arm64_armv8-a_kryo_static_core/gen/yacc/frameworks/compile/mclinker/lib/Script/ScriptParser.cpp frameworks/compile/mclinker/lib/Script/ScriptParser.yy

prebuilts/misc/linux-x86/bison/bison: error while loading shared libraries: libc++.so: cannot open shared object file: No such file or directory

[ 0% 98/86614] //frameworks/compile/mclinker/lib/Script:libmcldScript yacc ScriptParser.yy [linux]

FAILED: /home/mcenzie/android/lineage/out/soong/.intermediates/frameworks/compile/mclinker/lib/Script/libmcldScript/linux_x86_64_static/gen/yacc/frameworks/compile/mclinker/lib/Script/ScriptParser.cpp /home/mcenzie/android/lineage/out/soong/.intermediates/frameworks/compile/mclinker/lib/Script/libmcldScript/linux_x86_64_static/gen/yacc/frameworks/compile/mclinker/lib/Script/ScriptParser.h

BISON_PKGDATADIR=external/bison/data prebuilts/misc/linux-x86/bison/bison -d --defines=/home/mcenzie/android/lineage/out/soong/.intermediates/frameworks/compile/mclinker/lib/Script/libmcldScript/linux_x86_64_static/gen/yacc/frameworks/compile/mclinker/lib/Script/ScriptParser.h -o /home/mcenzie/android/lineage/out/soong/.intermediates/frameworks/compile/mclinker/lib/Script/libmcldScript/linux_x86_64_static/gen/yacc/frameworks/compile/mclinker/lib/Script/ScriptParser.cpp frameworks/compile/mclinker/lib/Script/ScriptParser.yy

prebuilts/misc/linux-x86/bison/bison: error while loading shared libraries: libc++.so: cannot open shared object file: No such file or directory

[ 0% 106/86614] APK certs list: /home/mcenzie/android/lin...rts_intermediates/lineage_oneplus3-apkcerts-614519c814.txt

ninja: build stopped: subcommand failed.

22:02:24 ninja failed with: exit status 1

#### failed to build some targets (06:22 (mm:ss)) ####

Anyone knows the problem ?!
[Android Software/Hacking General [Developers Only]] Uldiniad:
my bad, I deleted libc++.so because I thought that it wasn't being used... :silly:

I've put it back, so sync the changes and rebuild ;)
[Android Software/Hacking General [Developers Only]] Mcenzie:
Thanks You. But Not Change. Its the same Error.
[Android Software/Hacking General [Developers Only]] Uldiniad:
Then have you changed your roomservice.xml to include the lines in the OP?

Because without my commits your computer will use 32-bit bison (which is the pkg that is complaining in your build) and fail.

You can check that you have my changes by accessing the prebuilts/misc folder and checking that you have lib64 and libc++.so under that folder.
[Android Software/Hacking General [Developers Only]] Mcenzie:
[MENTION=7350242]Uldiniad[/MENTION]

thats my roomservice.xml and my the folder from prebuilts/misc

<?xml version="1.0" encoding="UTF-8"?>

-<manifest>

<project name="LineageOS/android_device_oneplus_oneplus3" path="device/oneplus/oneplus3" remote="github" revision="lineage-15.1"/>

<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" revision="lineage-15.1"/>

<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github"/>

<project name="dianlujitao/android_kernel_oneplus_msm8996" path="kernel/oneplus/msm8996" remote="github" revision="lineage-15.1"/>

<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings"/>

<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="lineage-15.1"/>

<remove-project name="platform/prebuilts/misc"/>

<remove-project name="LineageOS/android_prebuilts_build-tools"/>

<project name="Uldiniad/android_prebuilts_misc" path="prebuilts/misc" remote="github"/>

<project name="Uldiniad/android_prebuilts_build-tools" path="prebuilts/build-tools" remote="github"/>

</manifest>
[Android Software/Hacking General [Developers Only]] Uldiniad:
your roomservice.xml seems right. In the prebuilts misc folder, can you check that you have a lib64 folder under linux-x86 and that the lib64 folder contains libc++.so?

If it is not there, then that is the issue.
[Android Software/Hacking General [Developers Only]] Mcenzie:
Ouh yes there is nothing. Where i can download it manually ?!
[Android Software/Hacking General [Developers Only]] Uldiniad:
my prebuilts/misc repo on GitHub has it. that is why I have the step of adding my custom repo to the roomservice.xml. repo sync is supposed to take care of downloading the folder.

try this and let me know if it works (assuming you don't have not made any changes to any files in the source code that you want to keep, because this will set your your source code to be exactly on track with all repos online)

repo forall -vc "git reset --hard" && repo sync
[Android Software/Hacking General [Developers Only]] Mcenzie:
so for now i become this error

[ 0% 908/98513] APK certs list: /home/mcenzie/android/lin...rts_intermediates/lineage_oneplus3-apkcerts-9f6a5688b3.txt

FAILED: /home/mcenzie/android/lineage/out/target/product/oneplus3/obj/PACKAGING/apkcerts_intermediates/lineage_oneplus3-apkcerts-9f6a5688b3.txt

/bin/bash /home/mcenzie/android/lineage/out/target/product/oneplus3/obj/PACKAGING/apkcerts_intermediates/lineage_oneplus3-apkcerts-9f6a5688b3.txt.rsp

/home/mcenzie/android/lineage/out/target/product/oneplus3/obj/PACKAGING/apkcerts_intermediates/lineage_oneplus3-apkcerts-9f6a5688b3.txt.rsp: fork: Invalid argument

[ 0% 917/98513] Export includes file: -- /home/mcenzie/a...IBRARIES/libGLESv1_CM.ndk.15_intermediates/export_includes

ninja: build stopped: subcommand failed.

13:25:07 ninja failed with: exit status 1

#### failed to build some targets (07:02 (mm:ss)) ####
[Android Software/Hacking General [Developers Only]] Uldiniad:
look at the branches in the link. there is no lineage-16.0
[Android Software/Hacking General [Developers Only]] Uldiniad:
when I run source build/envsetup.sh at the root of the android tree (~/android/lineage if you followed the guide to the letter), I get this:

including device/generic/car/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/generic/uml/vendorsetup.sh
including vendor/lineage/vendorsetup.sh
including sdk/bash_completion/adb.bash

should be similar for you
[Android Software/Hacking General [Developers Only]] Uldiniad:
I get this instead, which seems correct and to me means the device is not ready to build yet. Maintainers are probably still working on bringup

breakfast dumpling
including vendor/lineage/vendorsetup.sh
device/oppo/common/common.mk:25: error: _nic.PRODUCTS.[[device/oneplus/dumpling/lineage_dumpling.mk]]: "vendor/oneplus/msm8998-common/msm8998-common-vendor.mk" does not exist.
19:21:08 dumpvars failed with: exit status 1
Device dumpling not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_oneplus_dumpling
Default revision: lineage-16.0
Checking branch info
Checking if device/oneplus/dumpling is fetched from android_device_oneplus_dumpling
LineageOS/android_device_oneplus_dumpling already fetched to device/oneplus/dumpling
Syncing repository to retrieve project.
Fetching project LineageOS/android_device_oneplus_dumpling

Repository synced!
Looking for dependencies in device/oneplus/dumpling
Looking for dependencies in device/oneplus/msm8998-common
Looking for dependencies in device/oppo/common
Looking for dependencies in packages/resources/devicesettings
packages/resources/devicesettings has no additional dependencies.
Looking for dependencies in kernel/oneplus/msm8998
kernel/oneplus/msm8998 has no additional dependencies.
Done
device/oppo/common/common.mk:25: error: _nic.PRODUCTS.[[device/oneplus/dumpling/lineage_dumpling.mk]]: "vendor/oneplus/msm8998-common/msm8998-common-vendor.mk" does not exist.
19:21:10 dumpvars failed with: exit status 1
device/oppo/common/common.mk:25: error: _nic.PRODUCTS.[[device/oneplus/dumpling/lineage_dumpling.mk]]: "vendor/oneplus/msm8998-common/msm8998-common-vendor.mk" does not exist.
19:21:10 dumpvars failed with: exit status 1

** Don't have a product spec for: 'lineage_dumpling'
** Do you have the right repo manifest?
[Android Software/Hacking General [Developers Only]] seadersn:
you need the proprietary vendor files ;) it's another repo, by the lineageos team, and located at github.com/TheMuppets. pick your needed folders (proprietary_vendor_oneplus_msm8998-common i think, and your device specific tree), and then be able to build :good:
[Android Software/Hacking General [Developers Only]] Uldiniad:
that's fair. I didn't test with the proprietary vendor files. will test and see if I run into the same issue as hachi1211
[Android Software/Hacking General [Developers Only]] Uldiniad:
it works for me, mind trying again. make sure you sync the repos first.

breakfast dumpling
including vendor/lineage/vendorsetup.sh
Looking for dependencies in device/oneplus/dumpling
Looking for dependencies in device/oneplus/msm8998-common
Looking for dependencies in device/oppo/common
Looking for dependencies in packages/resources/devicesettings
packages/resources/devicesettings has no additional dependencies.
Looking for dependencies in kernel/oneplus/msm8998
kernel/oneplus/msm8998 has no additional dependencies.

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
LINEAGE_VERSION=16.0-20181027-UNOFFICIAL-dumpling
TARGET_PRODUCT=lineage_dumpling
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a73
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=cortex-a73
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.18.0-10-generic-x86_64-Ubuntu-18.10
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PPR2.181005.003
OUT_DIR=/home/uldiniad/android/lineage/out
PRODUCT_SOONG_NAMESPACES= hardware/qcom/audio-caf/msm8998 hardware/qcom/display-caf/msm8998 hardware/qcom/media-caf/msm8998
TARGET_USE_SDCLANG=true
============================================
[Android Software/Hacking General [Developers Only]] maqo314:
I've got troubles trying to compile for Xiaomi Redmi Note 4 (mido): When I tried to "breakfast mido" I realized that there's no "lineage-16.0" branch for it on GitHub yet and I get this error message:

including vendor/lineage/vendorsetup.sh
08:21:17 Could not create module-finder: finder encountered 5 errors: [
/home/marco/android/lineage/16.0/external/python/cpython2/Mac: open /home/marco/android/lineage/16.0/external/python/cpython2/Mac: no such file or directory
/home/marco/android/lineage/16.0/external/python/cpython2/Objects: open /home/marco/android/lineage/16.0/external/python/cpython2/Objects: no such file or directory
/home/marco/android/lineage/16.0/external/jcommander/src/main/java/com/beust/jcommander/defaultprovider: lstat /home/marco/android/lineage/16.0/external/jcommander/src/main/java/com/beust/jcommander/defaultprovider: no such file or directory
/home/marco/android/lineage/16.0/external/jcommander/src/main/java/com/beust/jcommander/internal: lstat /home/marco/android/lineage/16.0/external/jcommander/src/main/java/com/beust/jcommander/internal: no such file or directory
/home/marco/android/lineage/16.0/external/jcommander/src/main/java/com/beust/jcommander/validators: lstat /home/marco/android/lineage/16.0/external/jcommander/src/main/java/com/beust/jcommander/validators: no such file or directory]
Device mido not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_xiaomi_mido
Default revision: lineage-16.0
Checking branch info
Default revision lineage-16.0 not found in android_device_xiaomi_mido. Bailing.
Branches found:
cm-14.1
lineage-15.0
lineage-15.1
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
08:21:49 Could not create module-finder: finder encountered 1 errors: [/home/marco/android/lineage/16.0/developers/build/prebuilts/gradle/WatchFace/Wearable/src/main/res/values-hdpi: open /home/marco/android/lineage/16.0/developers/build/prebuilts/gradle/WatchFace/Wearable/src/main/res/values-hdpi: no such file or directory]
08:22:16 Could not create module-finder: finder encountered 1 errors: [/home/marco/android/lineage/16.0/external/vim/runtime/lang: open /home/marco/android/lineage/16.0/external/vim/runtime/lang: no such file or directory]

** Don't have a product spec for: 'lineage_mido'
** Do you have the right repo manifest?

Would it be safe to "export ROOMSERVICE_BRANCHES=lineage-15.1" or could this seriously harm my device (e.g. bricking)?
[Android Software/Hacking General [Developers Only]] Uldiniad:
you can give it a try. caveats: if you run into problems I won't help cause I only care about errors caused by wsl and running on fallback branches is more likely to cause device tree errors (which the maintainer may care about or be working on, but I am not a device maintainer). about device bricking, it may. chances are low since your phone should have recovery mode and fastboot mode (or equivalent) which makes it harder for you to hard brick your phone. so even if flashing your custom built rom zip causes bootloops or hanging or anything else bad, you should still be able to recover from it. hope this answer your question
[Android Software/Hacking General [Developers Only]] skythian:
SyntaxError: invalid syntax
[ 0% 4/95197] //frameworks/base/services/core:services.core.unboosted logtags java/com/android/server/EventLogTags.logtags [common]
FAILED: /home/majordan/android/lineage/out/soong/.intermediates/frameworks/base/services/core/services.core.unboosted/android_common/gen/logtags/frameworks/base/services/core/java/com/android/server/EventLogTags.java
build/tools/java-event-log-tags.py -o /home/majordan/android/lineage/out/soong/.intermediates/frameworks/base/services/core/services.core.unboosted/android_common/gen/logtags/frameworks/base/services/core/java/com/android/server/EventLogTags.java frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
File "build/tools/java-event-log-tags.py", line 39
except getopt.GetoptError, err:

Trying to figure this error out right now. It's throwing an error over the comma, which leads me to believe it's trying to compile Python2 code with Python3. I've tried aliasing the python command to force it to use Python2, but it's still not working. Any help?
[Android Software/Hacking General [Developers Only]] scottysau:
Has anyone successfully built kltedv or cheeseburger. My build crashed after spitting out heaps of warnings after during the build eventually failing about an hour in.

Don't ask me for specifics. I'm miles from the laptop now. Instructions given in post one were followed and executed correctly.
[Android Software/Hacking General [Developers Only]] Ph9214:
How do I manually do the breakfast if my device is not in the official/default repos?
[Android Software/Hacking General [Developers Only]] Uldiniad:
. build/envsetup.sh && lunch <device_name> (&& make (install-)clean) && make -j* bacon

if you have a device tree from another branch or maybe use

export ROOMSERVICE_BRANCHES=<branch>

. keep in mind I will not help you if you get errors in this case since I am only interested in errors coming solely from wsl incompatibility, not broken/unfinished/unofficial device trees.
[Android Software/Hacking General [Developers Only]] Uldiniad:
warnings and aosp pretty much go hand in hand.

I would need specifics to check if it is wsl. But I'm willing to bet it's not wsl. I can't build klte on native Ubuntu yet without picking patches from gerrit. Things are still being worked on in 16.0 as described in my announcements and on the article.
[Android Software/Hacking General [Developers Only]] Uldiniad:
is there more stuff printed by the error? this one intrigues me. concerning python versions, you shouldn't need to touch anything if you followed the guide step-by-step
[Android Software/Hacking General [Developers Only]] scottysau:
Thanks for your reply. When I get back I'll sync and build again. I'll cut and paste the terminal, throw it in a file & pm it. Otherwise it will fill this thread up.

One thing I did notice is the roomservice file looked like this with no intervention from me (I have tried to fix the syntax in this post. Hopefully I haven't buggered it up and it's a true representation. I cut & past from terminal into windows 10 text file uploaded into OneDrive).

sudo nano .repo/local_manifests/roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="LineageOS/android_device_oneplus_cheeseburger" path="device/oneplus/cheeseburger" remote="github" />

<project name="LineageOS/android_device_oneplus_msm8998-common" path="device/oneplus/msm8998-common" remote="github" $

<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />

<project name="LineageOS/android_kernel_oneplus_msm8998" path="kernel/oneplus/msm8998" remote="github" />

<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="$

<project name="LineageOS/android_device_samsung_kltedv" path="device/samsung/kltedv" remote="github" />

<project name="LineageOS/android_device_samsung_klte-common" path="device/samsung/klte-common" remote="github" />

<project name="LineageOS/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" $

<project name="LineageOS/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" />

<project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" />

<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />

<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" />

</manifest>

The rest I'll get to you later. Tried to build kltedv & cheeseburger only.

Actually this may of been where I stuffed up - hmmmm. Your line is missing. Damn.
[Android Software/Hacking General [Developers Only]] seadersn:
roomservice.xml is filled by lineage.dependencies, it adds these entries there.
[Android Software/Hacking General [Developers Only]] Uldiniad:
this line seems incomplete to me (seems to be missing github for some reason):

<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="$

otherwise, yes, I do not see TheMuppets repo (it's one of the steps described on OP) in there which is a manual addition I recommend since I have not tried extracting the proprietary blobs from a phone from within wsl (may or may not work).

and for the errors on kltedv, if it is about O_CREAT or O_TMPFILE you need the following for now to succsefully build (can't guarantee it will boot or work well since most device trees are not ready to ship yet)

repopick -t pie-mode-bits

https://review.lineageos.org/#/q/branch:lineage-16.0+topic:pie-mode-bits
[Android Software/Hacking General [Developers Only]] Uldiniad:
might be related to sepolicy? https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_oneplus3/+/205686/

not sure what else could be causing that if you didn't have wsl and messed around with python packages and versions prior to or while following the guide. the packages on OP are enough to build. if you're confident that the setup was fine, then maybe try `make clobber` and then repo sync and brunch again?