[Solved for now] Help with building LineageOS? - T-Mobile LG G4

I'm trying to compile LineageOS for the h811 from the github sources using the old CyangenMod method as a guide. I got the repo initialized and downloaded the sources, but when I got the the "breakfast" step I got these errors:
Code:
~/android/system $ breakfast h811
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_h811". Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "cm_h811". Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_h811". Stop.
Device h811 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Failed to search GitHub
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_h811". Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_h811". Stop.
** Don't have a product spec for: 'lineage_h811'
** Do you have the right repo manifest?
What am I missing?

Nevermind, it's working today. I guess something wasn't hooked up on the back end earlier.

Related

[Droid] Building CM6 from source Error

Hi, I posted this at the Cyanogen forums - but I figured I would ask here too:
I am trying to build CM6 from source. I have followed the Wiki but I am getting this error:
Code:
Finding NOTICE files: out/target/product/sholes/obj/NOTICE_FILES/hash-timestamp
Combining NOTICE files: out/target/product/sholes/obj/NOTICE.html
Target system fs image: out/target/product/sholes/obj/PACKAGING/systemimage_unopt_intermediates/system.img
Install system fs image: out/target/product/sholes/system.img
out/target/product/sholes/system.img+ total size is 152454720
error: out/target/product/sholes/system.img+ too large (152454720 > [151793664 - ])
make: *** [out/target/product/sholes/system.img] Error 1
make: *** Deleting file `out/target/product/sholes/system.img'
Any help would be great.. I have copied all of the proprietary files and have the latest source from the git repository.

[H][DEV] [T] Build CM12 for Xperia T Mint

Hello to everyone, my name is Tkd-Alex and I'm Italian :good: . Excuse me if I do English errors.
I woult to build the Cyanogenmod 12 for Xperia T mint by a source code of CM. Thanks to the cm wiki as I understand how this works. But I've errors with it! I hope you can help me. :angel:
Let's start! :laugh:
The first step to me is prepare the enviroment to build the rom. I've installed Ubuntu 13.10 64bit inside a Virtual Machine and I've installed Java and other tools/packages for building on it.
After basic installations I set up the repo command.
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Code:
sudo nano ~/.bashrc
Add at the end line: export PATH=~/bin:$PATH save and restart the bash
Code:
source ~/.bashrc
The second step is the Building.
Create the folder.
Code:
mkdir ~/cm12
Move in to the folder
Code:
cd ~/cm12
Initialize the CyanogenMod source repository
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
Sync the repo
Code:
repo sync
ERROR!
After repo sync I'll get prebuilt apps but when I send the command:
Code:
./get-prebuilts
I get the following error:
Code:
bash: ./get-prebuilts: File o directory not existing
Can anyone help me? @GabMus @updateing @WhiteNeo @Chefov01
You are not in the right directory.. "get-prebuilts" is an executable file that isn't present in the cm12 root directory.
Type this in Terminal before "./get-prebuilts":
Code:
cd ~/cm12/vendor/cm
However, afaik those prebuilt apps are no longer needed to build cm12. They have been removed from the build process some days ago.
WhiteNeo said:
You are not in the right directory.. "get-prebuilts" is an executable file that isn't present in the cm12 root directory.
Type this in Terminal before "./get-prebuilts":
Code:
cd ~/cm12/vendor/cm
However, afaik those prebuilt apps are no longer needed to build cm12. They have been removed from the build process some days ago.
Click to expand...
Click to collapse
bro is there any chance you could make a build for us T users? at least for testing purposes, im sure our developers would appreciate it a lot as well and would help as a starting point.. :-/
Not working.
WhiteNeo said:
You are not in the right directory.. "get-prebuilts" is an executable file that isn't present in the cm12 root directory.
Type this in Terminal before "./get-prebuilts":
Code:
cd ~/cm12/vendor/cm
However, afaik those prebuilt apps are no longer needed to build cm12. They have been removed from the build process some days ago.
Click to expand...
Click to collapse
Thank for reply, but I know that you say :highfive: . I had already tried the command ./get-prebuilts in the folder /cm12/vendor/cm but I forgot to say in the post. Now I'll try to ignore the prebuilds and download the muppets repo, extract the zip, rename in sony and copy the folder in /cm12/vendor. After that I will go in the root folder
Code:
croot
and try the brunch command
Code:
brunch mint
Is that correct?
tkd-alex said:
Thank for reply, but I know that you say :highfive: . I had already tried the command ./get-prebuilts in the folder /cm12/vendor/cm but I forgot to say in the post. Now I'll try to ignore the prebuilds and download the muppets repo, extract the zip, rename in sony and copy the folder in /cm12/vendor. After that I will go in the root folder
Code:
croot
and try the brunch command
Code:
brunch mint
Is that correct?
Click to expand...
Click to collapse
Well.. No.
For CM11 it would work, but CM12 needs different device files than the ones downloaded by "breakfast mint" or "brunch mint"..
I'm not quite sure it compiling Lollipop is a good start for learning android development if you've never built a rom before.
WhiteNeo said:
Well.. No.
For CM11 it would work, but CM12 needs different device files than the ones downloaded by "breakfast mint" or "brunch mint"..
I'm not quite sure it compiling Lollipop is a good start for learning android development if you've never built a rom before.
Click to expand...
Click to collapse
Infact with the breakfast command I've this:
Code:
[email protected]:~/cm12$ breakfast mint
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/sony/mint/cm.mk]]: "device/sony/common/resources.mk" does not exist. Arresto.
Device mint not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_sony_mint
Default revision: cm-12.0
Checking branch info
CyanogenMod/android_device_sony_mint already exists
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_sony_mint
Fetching projects: 100% (1/1), done.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/sony/mint/cm.mk]]: "device/sony/common/resources.mk" does not exist. Arresto.
** Don't have a product spec for: 'cm_mint'
** Do you have the right repo manifest?
We can not do anything?
tkd-alex said:
Infact with the breakfast command I've this:
Code:
[email protected]:~/cm12$ breakfast mint
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/sony/mint/cm.mk]]: "device/sony/common/resources.mk" does not exist. Arresto.
Device mint not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_sony_mint
Default revision: cm-12.0
Checking branch info
CyanogenMod/android_device_sony_mint already exists
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_sony_mint
Fetching projects: 100% (1/1), done.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/sony/mint/cm.mk]]: "device/sony/common/resources.mk" does not exist. Arresto.
** Don't have a product spec for: 'cm_mint'
** Do you have the right repo manifest?
We can not do anything?
Click to expand...
Click to collapse
Maybe you can check if some entries are missing in local_manifest (e.g. the sony common repo it listed there) mine is here: http://forum.xda-developers.com/showpost.php?p=57492538&postcount=52
And it's not a nice idea to learn building Android on T & CM12. It's not easy as CM11, lots of patches have to be applied to make it work...

[Q] Building androidarmv6 for Cooper

Hi, I'm trying to build androidarmv6 for Cooper. I synced all the repositories and then ran lunch and chose cm_cooper-userdebug, but the command fails with
Code:
lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng 7. cm_goldfish-userdebug 13. cm_cooper-eng 19. cm_gio-userdebug 25. cm_icong-userdebug
2. aosp_x86-eng 8. cm_goldfish-user 14. cm_cooper-userdebug 20. cm_tass-userdebug 26. cm_liberty-userdebug
3. aosp_mips-eng 9. mini_mips-userdebug 15. cm_p500-userdebug 21. cm_tassve-userdebug 27. cm_marvel-userdebug
4. vbox_x86-eng 10. mini_x86-userdebug 16. cm_beni-userdebug 22. cm_totoro-userdebug
5. mini_armv7a_neon-userdebug 11. cm_callisto-eng 17. cm_cooperve-userdebug 23. cm_skate-userdebug
6. cm_goldfish-eng 12. cm_callisto-userdebug 18. cm_galaxy5-userdebug 24. cm_chacha-userdebug
Which would you like? [aosp_arm-eng] cm_cooper-userdebug
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/cooper/cm.mk]]: "device/samsung/msm7x27-common/common.mk" does not exist. Schluss.
Device cooper not found. Attempting to retrieve device repository from androidarmv6 Github.
Found repository: android_device_samsung_cooper
Default revision: cm-11.0
Checking branch info
androidarmv6/android_device_samsung_cooper already exists
Syncing repository to retrieve project.
Fetching project repo
Fetching project androidarmv6/android_device_samsung_cooper
fatal: Invalid gitfile format: /ansys/android/.repo/repo/.git/clone.bundle
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Fetching projects: 100% (2/2), done.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/cooper/cm.mk]]: "device/samsung/msm7x27-common/common.mk" does not exist. Schluss.
** Don't have a product spec for: 'cm_cooper'
** Do you have the right repo manifest?
Can somebody explain to me what the problem is and/or where I might find the product spec / right repo manifest?
PsirusGT said:
Hi, I'm trying to build androidarmv6 for Cooper. I synced all the repositories and then ran lunch and chose cm_cooper-userdebug, but the command fails with
Code:
lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng 7. cm_goldfish-userdebug 13. cm_cooper-eng 19. cm_gio-userdebug 25. cm_icong-userdebug
2. aosp_x86-eng 8. cm_goldfish-user 14. cm_cooper-userdebug 20. cm_tass-userdebug 26. cm_liberty-userdebug
3. aosp_mips-eng 9. mini_mips-userdebug 15. cm_p500-userdebug 21. cm_tassve-userdebug 27. cm_marvel-userdebug
4. vbox_x86-eng 10. mini_x86-userdebug 16. cm_beni-userdebug 22. cm_totoro-userdebug
5. mini_armv7a_neon-userdebug 11. cm_callisto-eng 17. cm_cooperve-userdebug 23. cm_skate-userdebug
6. cm_goldfish-eng 12. cm_callisto-userdebug 18. cm_galaxy5-userdebug 24. cm_chacha-userdebug
Which would you like? [aosp_arm-eng] cm_cooper-userdebug
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/cooper/cm.mk]]: "device/samsung/msm7x27-common/common.mk" does not exist. Schluss.
Device cooper not found. Attempting to retrieve device repository from androidarmv6 Github.
Found repository: android_device_samsung_cooper
Default revision: cm-11.0
Checking branch info
androidarmv6/android_device_samsung_cooper already exists
Syncing repository to retrieve project.
Fetching project repo
Fetching project androidarmv6/android_device_samsung_cooper
fatal: Invalid gitfile format: /ansys/android/.repo/repo/.git/clone.bundle
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Fetching projects: 100% (2/2), done.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/cooper/cm.mk]]: "device/samsung/msm7x27-common/common.mk" does not exist. Schluss.
** Don't have a product spec for: 'cm_cooper'
** Do you have the right repo manifest?
Can somebody explain to me what the problem is and/or where I might find the product spec / right repo manifest?
Click to expand...
Click to collapse
Make sure common.mk exists in device/samsung/msm7x27-common. If it is not there download it from androidarmv6 github(dirty solution-download whole msm7x27-common folder & manually & place it inside device/samsung folder). And try brunch command.
"brunch cooper".

a530_zap-pro.b00 Missing - Trying to build Lineage OS 15.1

I was following the official guide to building Lineage OS 15.1 for Oneplus 3T but when I executed "extract-files.sh" I got error with some files being missing.Ignoring that, when I ran brunch oneplus3 I got:
Code:
[1060/1060] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
ninja: error: 'vendor/oneplus/oneplus3/proprietary/vendor/firmware/a530_zap-pro.b00', needed by '/home/user/Desktop/lineage/out/target/product/oneplus3/system/vendor/firmware/a530_zap-pro.b00', missing and no known rule to make it
20:25:42 ninja failed with: exit status 1
but I have checked with Root Browser and can say for sure that "a530_zap-pro.b00" file does not exist Anyone who has compiled Lineage OS before can you please tell how did you get it to work as the files don't exist. I'm currently on Oxygen OS Open Beta 24 with Magisk 16.3.
DelicatePanda said:
I was following the official guide to building Lineage OS 15.1 for Oneplus 3T but when I executed "extract-files.sh" I got error with some files being missing.Ignoring that, when I ran brunch oneplus3 I got:
Code:
[1060/1060] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
ninja: error: 'vendor/oneplus/oneplus3/proprietary/vendor/firmware/a530_zap-pro.b00', needed by '/home/user/Desktop/lineage/out/target/product/oneplus3/system/vendor/firmware/a530_zap-pro.b00', missing and no known rule to make it
20:25:42 ninja failed with: exit status 1
but I have checked with Root Browser and can say for sure that "a530_zap-pro.b00" file does not exist Anyone who has compiled Lineage OS before can you please tell how did you get it to work as the files don't exist. I'm currently on Oxygen OS Open Beta 24 with Magisk 16.3.
Click to expand...
Click to collapse
Put this in your local_manifest/roomservice.xml file :
<project path="vendor/oneplus" name="TheMuppet/proprietary_vendor_oneplus" revision="lineage=15.1" />
Click to expand...
Click to collapse
and then do a `repo sync`. This repo wll add all mandatory files (files which are extracted by the `extract-files.sh' tool) to your build tree.
casual_kikoo said:
Put this in your local_manifest/roomservice.xml file :
and then do a `repo sync`. This repo wll add all mandatory files (files which are extracted by the `extract-files.sh' tool) to your build tree.
Click to expand...
Click to collapse
Thank you for that but I was curious about how those files were obtained. And now I'm having another error:
Code:
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
Building DTBs
make: Entering directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
make[1]: Entering directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
CHK include/config/kernel.release
GEN ./Makefile
CHK include/generated/uapi/linux/version.h
Using /home/user/Desktop/lineage/kernel/oneplus/msm8996 as source for kernel
CHK include/generated/utsrelease.h
CALL /home/user/Desktop/lineage/kernel/oneplus/msm8996/scripts/checksyscalls.sh
make[2]: 'include/generated/vdso-offsets.h' is up to date.
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
ninja: build stopped: subcommand failed.
20:21:02 ninja failed with: exit status 1
DelicatePanda said:
Thank you for that but I was curious about how those files were obtained. And now I'm having another error:
Code:
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
Building DTBs
make: Entering directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
make[1]: Entering directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
CHK include/config/kernel.release
GEN ./Makefile
CHK include/generated/uapi/linux/version.h
Using /home/user/Desktop/lineage/kernel/oneplus/msm8996 as source for kernel
CHK include/generated/utsrelease.h
CALL /home/user/Desktop/lineage/kernel/oneplus/msm8996/scripts/checksyscalls.sh
make[2]: 'include/generated/vdso-offsets.h' is up to date.
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
ninja: build stopped: subcommand failed.
20:21:02 ninja failed with: exit status 1
Click to expand...
Click to collapse
Your output is missing some information, there is no error in this, except
Code:
ninja: build stopped : subcommand failed
casual_kikoo said:
Your output is missing some information, there is no error in this, except
Code:
ninja: build stopped : subcommand failed
Click to expand...
Click to collapse
Sorry for the delay I am attaching the output of entire "brunch oneplus3" command to this and could you please tell me from where the files in the repo were obtained. Thanks for the help:highfive:
DelicatePanda said:
Sorry for the delay I am attaching the output of entire "brunch oneplus3" command to this and could you please tell me from where the files in the repo were obtained. Thanks for the help:highfive:
Click to expand...
Click to collapse
You have some problem with jack-server :
FAILED: setup-jack-server
/bin/bash -c "(prebuilts/sdk/tools/jack-admin install-server prebuilts/sdk/tools/jack-launcher.jar prebuilts/sdk/tools/jack-server-4.11.ALPHA.jar 2>&1 || (exit 0) ) && (JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx2G" prebuilts/sdk/tools/jack-admin start-server 2>&1 || exit 0 ) && (prebuilts/sdk/tools/jack-admin update server prebuilts/sdk/tools/jack-server-4.11.ALPHA.jar 4.11.ALPHA 2>&1 || exit 0 ) && (prebuilts/sdk/tools/jack-admin update jack prebuilts/sdk/tools/jacks/jack-4.32.CANDIDATE.jar 4.32.CANDIDATE || exit 47 )"
Jack server already installed in "/home/user/.jack-server"
Launching Jack server java -XX:MaxJavaStackTraceDepth=-1 -Djava.io.tmpdir=/tmp -Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx2G -cp /home/user/.jack-server/launcher.jar com.android.jack.launcher.ServerLauncher
Jack server failed to (re)start, try 'jack-diagnose' or see Jack server log
No Jack server running. Try 'jack-admin start-server'
No Jack server running. Try 'jack-admin start-server'
Click to expand...
Click to collapse
In the root of your Android build directory
Code:
prebuilts/sdk/tools/jack-admin start-server
and then, straight after starting jack-server, relaunch your build process.
Also, judging from the log, jack-server is launching with 2G of RAM, which is very low IMO. If you have a low end PC, check this XDA thread, which explains you how to use Google Cloud for free to build ROM.
If you still have issues with jack-server, check this build guide by @nathanchance : there is a part about jack-server memory's problem (Ctrl + F -> "Jack issues").
Also, check a look at this Google Groups thread, this might help you.
Concerning TheMuppets : to be honest with you, I don't know exactly where files come from, BUT looking at commit messages on their Github, you can see, among others, that fourkbomb is pushing to this organization; a quick Google Search, you find his Github profile, he's a member of LineageOS. Also, you'll find a lot of ROMs builders TheMuppet' repo, so nothing to worry about (their repos are on Github, so you can check by yourself ).

How do I build LineageOS for the Pro1-X?

I tried to build using the Pro1 instructions (https://wiki.lineageos.org/devices/pro1/build) but the "breakfast pro1x" step doesn't work.
$ breakfast pro1x
16:47:13 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:353:
In file included from build/make/core/envsetup.mk:352:
build/make/core/product_config.mk:228: error: Can not locate config makefile for product "lineage_pro1x".
16:47:14 dumpvars failed with: exit status 1
Device pro1x not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_fxtec_pro1x
Default revision: lineage-20.0
Checking branch info
Using fallback branch: lineage-20
Checking if device/fxtec/pro1x is fetched from android_device_fxtec_pro1x
Adding dependency: LineageOS/android_device_fxtec_pro1x -> device/fxtec/pro1x
Syncing repository to retrieve project.
Fetching: 100% (1/1), done in 1.282s
repo sync has finished successfully.
Repository synced!
Looking for dependencies in device/fxtec/pro1x
Default revision: lineage-20.0
Checking branch info
Traceback (most recent call last):
File "/run/media/kevin/SEAGATE4TB/lineageos/android/lineage/vendor/lineage/build/tools/roomservice.py", line 308, in <module>
fetch_dependencies(repo_path)
File "/run/media/kevin/SEAGATE4TB/lineageos/android/lineage/vendor/lineage/build/tools/roomservice.py", line 228, in fetch_dependencies
dependency['branch'] = get_default_or_fallback_revision(dependency['repository'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/run/media/kevin/SEAGATE4TB/lineageos/android/lineage/vendor/lineage/build/tools/roomservice.py", line 262, in get_default_or_fallback_revision
result = json.loads(urllib.request.urlopen(githubreq).read().decode())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/urllib/request.py", line 216, in urlopen
return opener.open(url, data, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/urllib/request.py", line 525, in open
response = meth(req, response)
^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/urllib/request.py", line 634, in http_response
response = self.parent.error(
^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/urllib/request.py", line 563, in error
return self._call_chain(*args)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/urllib/request.py", line 496, in _call_chain
result = func(*args)
^^^^^^^^^^^
File "/usr/lib64/python3.11/urllib/request.py", line 643, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found
A comment was made about roomservice.xml which shows:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/fxtec/pro1x" remote="github" name="LineageOS/android_device_fxtec_pro1x" revision="lineage-20" />
</manifest>
It's trying to get the list of branches:
Requesting: https://api.github.com/repos/LineageOS/android_kernel_fxtec_s6115/branches
But this returns 404 because there are no branches. It's looking for the lineage-20.0 branch.
In comparison, for the Pro1, there are branches.
So then I guess the question becomes: how does one develop with a pre-release device that doesn't have branches yet?
Ahh, I see, I think the problem is in this file: https://github.com/LineageOS/android_device_fxtec_pro1x/blob/lineage-20/lineage.dependencies
The repository is incorrect:
"repository": "android_kernel_fxtec_s6115",
It should be sm6115.
Created issue: https://gitlab.com/LineageOS/issues/infra/-/issues/143
kevgrig said:
Ahh, I see, I think the problem is in this file: https://github.com/LineageOS/android_device_fxtec_pro1x/blob/lineage-20/lineage.dependencies
The repository is incorrect:
"repository": "android_kernel_fxtec_s6115",
It should be sm6115.
Click to expand...
Click to collapse
I've merged a fix with credit to you.
Thanks.
rm .repo/local_manifests/roomservice.xml and try again pls
npjohnson said:
I've merged a fix with credit to you.
Thanks.
rm .repo/local_manifests/roomservice.xml and try again pls
Click to expand...
Click to collapse
Thanks! I'll check soon
npjohnson said:
I've merged a fix with credit to you.
Thanks.
rm .repo/local_manifests/roomservice.xml and try again pls
Click to expand...
Click to collapse
Thanks, it's getting farther now. I removed .repo/local_manifests/roomservice.xml and re-ran `breakfast pro1x` but now it's complaining about missing vendor/fxtec/pro1x/pro1x-vendor.mk. Oddly, it's looking in vendor/fxtec which doesn't exist.
# breakfast pro1x
21:29:32 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:353:
In file included from build/make/core/envsetup.mk:352:
In file included from build/make/target/product/telephony_vendor.mk:21:
device/fxtec/pro1x/device.mk:479: error: vendor/fxtec/pro1x/pro1x-vendor.mk does not exist..
21:29:34 dumpvars failed with: exit status 1
Device pro1x not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_fxtec_pro1x
Looking up fxtec/pro1x
Default revision: lineage-20.0
Checking branch info
Requesting: https://api.github.com/repos/LineageOS/android_device_fxtec_pro1x/branches
Using fallback branch: lineage-20
Checking if device/fxtec/pro1x is fetched from android_device_fxtec_pro1x
Adding dependency: LineageOS/android_device_fxtec_pro1x -> device/fxtec/pro1x
Syncing repository to retrieve project.
Fetching: 100% (2/2), done in 2.005s
.repo/repo: project not found in manifest.
repo sync has finished successfully.
Repository synced!
Looking for dependencies in device/fxtec/pro1x
Default revision: lineage-20.0
Checking branch info
Requesting: https://api.github.com/repos/LineageOS/android_kernel_fxtec_sm6115/branches
Using fallback branch: lineage-20
Adding dependencies to manifest
Checking if kernel/fxtec/sm6115 is fetched from android_kernel_fxtec_sm6115
Adding dependency: LineageOS/android_kernel_fxtec_sm6115 -> kernel/fxtec/sm6115
Syncing dependencies
Fetching: 100% (2/2), done in 6m42.385s
Updating files: 100% (70635/70635), done.
Checking out: 100% (2/2), done in 14.935s
repo sync has finished successfully.
Looking for dependencies in kernel/fxtec/sm6115
kernel/fxtec/sm6115 has no additional dependencies.
Done
21:36:46 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:353:
In file included from build/make/core/envsetup.mk:352:
In file included from build/make/target/product/telephony_vendor.mk:21:
device/fxtec/pro1x/device.mk:479: error: vendor/fxtec/pro1x/pro1x-vendor.mk does not exist..
21:36:46 dumpvars failed with: exit status 1
21:36:48 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:353:
In file included from build/make/core/envsetup.mk:352:
In file included from build/make/target/product/telephony_vendor.mk:21:
device/fxtec/pro1x/device.mk:479: error: vendor/fxtec/pro1x/pro1x-vendor.mk does not exist..
21:36:48 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_pro1x'
** Do you have the right repo manifest?
# ls vendor/fxtec/pro1x
ls: cannot access 'vendor/fxtec/pro1x': No such file or directory
# ls vendor/
codeaurora crowdin lineage nxp qcom
kevgrig said:
Thanks, it's getting farther now. I removed .repo/local_manifests/roomservice.xml and re-ran `breakfast pro1x` but now it's complaining about missing vendor/fxtec/pro1x/pro1x-vendor.mk. Oddly, it's looking in vendor/fxtec which doesn't exist.
# breakfast pro1x
21:29:32 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:353:
In file included from build/make/core/envsetup.mk:352:
In file included from build/make/target/product/telephony_vendor.mk:21:
device/fxtec/pro1x/device.mk:479: error: vendor/fxtec/pro1x/pro1x-vendor.mk does not exist..
21:29:34 dumpvars failed with: exit status 1
Device pro1x not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_fxtec_pro1x
Looking up fxtec/pro1x
Default revision: lineage-20.0
Checking branch info
Requesting: https://api.github.com/repos/LineageOS/android_device_fxtec_pro1x/branches
Using fallback branch: lineage-20
Checking if device/fxtec/pro1x is fetched from android_device_fxtec_pro1x
Adding dependency: LineageOS/android_device_fxtec_pro1x -> device/fxtec/pro1x
Syncing repository to retrieve project.
Fetching: 100% (2/2), done in 2.005s
.repo/repo: project not found in manifest.
repo sync has finished successfully.
Repository synced!
Looking for dependencies in device/fxtec/pro1x
Default revision: lineage-20.0
Checking branch info
Requesting: https://api.github.com/repos/LineageOS/android_kernel_fxtec_sm6115/branches
Using fallback branch: lineage-20
Adding dependencies to manifest
Checking if kernel/fxtec/sm6115 is fetched from android_kernel_fxtec_sm6115
Adding dependency: LineageOS/android_kernel_fxtec_sm6115 -> kernel/fxtec/sm6115
Syncing dependencies
Fetching: 100% (2/2), done in 6m42.385s
Updating files: 100% (70635/70635), done.
Checking out: 100% (2/2), done in 14.935s
repo sync has finished successfully.
Looking for dependencies in kernel/fxtec/sm6115
kernel/fxtec/sm6115 has no additional dependencies.
Done
21:36:46 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:353:
In file included from build/make/core/envsetup.mk:352:
In file included from build/make/target/product/telephony_vendor.mk:21:
device/fxtec/pro1x/device.mk:479: error: vendor/fxtec/pro1x/pro1x-vendor.mk does not exist..
21:36:46 dumpvars failed with: exit status 1
21:36:48 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:353:
In file included from build/make/core/envsetup.mk:352:
In file included from build/make/target/product/telephony_vendor.mk:21:
device/fxtec/pro1x/device.mk:479: error: vendor/fxtec/pro1x/pro1x-vendor.mk does not exist..
21:36:48 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_pro1x'
** Do you have the right repo manifest?
# ls vendor/fxtec/pro1x
ls: cannot access 'vendor/fxtec/pro1x': No such file or directory
# ls vendor/
codeaurora crowdin lineage nxp qcom
Click to expand...
Click to collapse
You didn't extract proprietary blobs like the guide says.
Additionally, don't extra then, just grab vendor/fxtec/pro1x from GitHub.com/themuppets and add to your local manifest.
npjohnson said:
You didn't extract proprietary blobs like the guide says.
Additionally, don't extra then, just grab vendor/fxtec/pro1x from GitHub.com/themuppets and add to your local manifest.
Click to expand...
Click to collapse
Ahh yes, my apologies. I had read that section about extracting blobs some time ago and forgot about it.
# cd device/fxtec/pro1x
# ./extract-files.sh
[...]
# cd -
# breakfast pro1x
[...]
# brunch pro1x
Building. Thanks!
kevgrig said:
Ahh yes, my apologies. I had read that section about extracting blobs some time ago and forgot about it.
# cd device/fxtec/pro1x
# ./extract-files.sh
[...]
# cd -
# breakfast pro1x
[...]
# brunch pro1x
Building. Thanks!
Click to expand...
Click to collapse
good to hear!
Got to 99% on the build and then failed with lack of memory on a 16GB box (with almost every background process stopped):
dex2oatd F 02-16 15:22:03 770205 770205 mem_map_arena_pool.cc:65] Check failed: map.IsValid() Failed anonymous mmap((nil), 131072, 0x3, 0x22, -1, 0): Cannot allocate memory. See process maps in the log.
Will buy some more RAM...
kevgrig said:
Got to 99% on the build and then failed with lack of memory on a 16GB box (with almost every background process stopped):
dex2oatd F 02-16 15:22:03 770205 770205 mem_map_arena_pool.cc:65] Check failed: map.IsValid() Failed anonymous mmap((nil), 131072, 0x3, 0x22, -1, 0): Cannot allocate memory. See process maps in the log.
Will buy some more RAM...
Click to expand...
Click to collapse
I had the same problem. I installed kernel 5.19 and booted with it instead of 6.1, the problem disappeared.
mishurov said:
I had the same problem. I installed kernel 5.19 and booted with it instead of 6.1, the problem disappeared.
Click to expand...
Click to collapse
can confirm, it's a linux kernel issue

Categories

Resources