Database Info

Problem AOSP compiling

I get this error when compiling AOSP using device tree from CM7. Please any help is appreciated.
[email protected] ~/WORKING_DIRECTORY $ lunch
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. htc_ace-userdebug
5. htc_ace-eng
6. full_passion-userdebug
7. full_crespo4g-userdebug
8. full_crespo-userdebug
Which would you like? [full-eng] 5
build/core/product_config.mk:194: *** _nic.PRODUCTS.[[device/htc/ace/ace.mk]]: "device/htc/msm7x30-common/msm7x30.mk" does not exist. Stop.
** Don't have a product spec for: 'htc_ace'
** Do you have the right repo manifest?

[help]trying to build chroma rom

Please be patient as i am new in building roms[built 3-official roms], now am building chroma rom but bacon is an unsupported device. i have cloned all the proprietary blobs and kernel. but on 'lunch' i do not see my device.
any advice?
Code:
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_mips-eng
4. aosp_mips64-eng
5. aosp_x86-eng
6. aosp_x86_64-eng
7. full_fugu-userdebug
8. aosp_fugu-userdebug
9. mini_emulator_arm64-userdebug
10. m_e_arm-userdebug
11. m_e_mips64-eng
12. m_e_mips-userdebug
13. mini_emulator_x86_64-userdebug
14. mini_emulator_x86-userdebug
15. aosp_dragon-userdebug
16. aosp_dragon-eng
17. aosp_flounder-userdebug
18. aosp_angler-userdebug
19. aosp_bullhead-userdebug
20. hikey-userdebug
21. aosp_shamu-userdebug

You have modify device tree for building ROM
Take reference of other device's tree
Sent from my OnePlus One using XDA Labs

nathsagar96 said:
You have modify device tree for building ROM
Take reference of other device's tree
Sent from my OnePlus One using XDA Labs
Click to expand...
Click to collapse
I am trying to do that, but i am finding it very difficult, as i am starting building roms. And there aren't any latest guides about building unofficial roms.

This would help you
https://www.youtube.com/shared?ci=XJk1GDuh9gg
Sent from my OnePlus One using XDA Labs

I guess you are missing a file called vendorsetup.sh in your device tree.

Bongofriend said:
I guess you are missing a file called vendorsetup.sh in your device tree.
Click to expand...
Click to collapse
i set it up...noe the device shows in lunch menu...but on compiling i get errors....
Code:
No private recovery resources for TARGET_DEVICE bacon
Checking API: checkpublicapi-last
out/target/common/obj/PACKAGING/public_api.txt:1966: error 17: Field android.R.style.TextAppearance_Material_Wi
dget_Button_Inverse has changed value from 16974548 to 16974565
out/target/common/obj/PACKAGING/public_api.txt:2011: error 17: Field android.R.style.ThemeOverlay_Material_Dial
og has changed value from 16974550 to 16974564
out/target/common/obj/PACKAGING/public_api.txt:2012: error 17: Field android.R.style.ThemeOverlay_Material_Dial
og_Alert has changed value from 16974551 to 16974566
out/target/common/obj/PACKAGING/public_api.txt:2120: error 17: Field android.R.style.Theme_Material_Light_Light
StatusBar has changed value from 16974549 to 16974563
******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.

Can not locate config file for product "full_BLU_LIFE_ONE-eng". Stop.

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.

Porting Lineage-14.1 to SM-G925F

As far as I know there is no official support on the LineageOS github for the zerolte model and that's when I decided that I'd like to change that.
I created my own device tree, but there are still some important directories and files missing to get passed the brunch command for zerolte.
If any kind soul would be able to help me make the changes specific for this model I'd be so happy.
Here's the tree: https://github.com/Umeaboy/android_device_samsung_zerolte

OK, here's the first error when running brunch zerolte:
Checking build tools versions...
build/core/binary.mk:1253: external/deqp/Android.mk: libdeqp: Unused source files: \
build/core/binary.mk:1253: external/deqp/Android.mk: libdeqp: Unused source files: \
build/core/binary.mk:1253: external/pdfium/third_party/pdfiumbigint.mk: libpdfiumbigint: Unused source files: bigint/BigInteger.cc bigint/BigIntegerUtils.cc bigint/BigUnsigned.cc bigint/BigUnsignedInABase.cc
build/core/binary.mk:1253: external/pdfium/third_party/pdfiumbigint.mk: libpdfiumbigint: Unused source files: bigint/BigInteger.cc bigint/BigIntegerUtils.cc bigint/BigUnsigned.cc bigint/BigUnsignedInABase.cc
./external/speex/Android.mk:56: TODOArm64: enable neon in libspeex
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
find: ‘/home/kristoffer/android/lineage/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates’: File or directory does not exist
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
build/core/base_rules.mk:183: *** hardware/samsung/audio: MODULE.TARGET.SHARED_LIBRARIES.audio.primary.universal7420 already defined by device/samsung/zerolte/audio.
build/core/ninja.mk:166: receipt for target ”/home/kristoffer/android/lineage/out/build-lineage_zerolte.ninja” failed
make: *** [/home/kristoffer/android/lineage/out/build-lineage_zerolte.ninja] Error 1
make: Leaving directory ”/home/kristoffer/android/lineage”
Is there's a repo missing in my manifest to get the files that are missing? When I google I can't seem to find which one.

Here's my local_manifest.

In fact there is a lineage os 14 build for s6 edge

alex.X said:
In fact there is a lineage os 14 build for s6 edge
Click to expand...
Click to collapse
Yes, but not one that works beyond the Setup guide.
Tried the Nexus zip already.

There is in fact even though it has quite a few bugs

alex.X said:
There is in fact even though it has quite a few bugs
Click to expand...
Click to collapse
Please point me to it.
As I said...... I already tried the Nexus version.

it would be so great to have a Lineage rom for our S6 edge ! is this phone so rare that it is not supported?
Still fed up with TW, but in love with this sreen.

I found a custom version of Lineage for this phone, but I'd prefer to build a clean version so that more updates/fixes come more often.
Here's the file: https://nexus-roms.eu/files/testing/zero/ResurrectionRemix-zero-multitarget-2017-06-14_1948.zip
If you don't care about loosing everything on your phone here's how to erase everything on it:
In TWRP
Click on Wipe.
Then click on Advanced wipe.
Select the following partitions to wipe:
Dalvik / ART Cache, System, Data, Internal Storage, Cache.
Now swipe to the right to wipe.
Go back one step and press Format data.
Type the word yes and press the blue button on the lower right corner that has a check mark in it.
Now, go back to main menu.
If you have downloaded the above mentioned zip file to your desktop and you have adb working on your local computer, connect the phone with a cable and type in the terminal:
Code:
adb devices
Once you've confirmed that the phone is recognized, do this command:
Code:
cd Desktop
adb push ResurrectionRemix-zero-multitarget-2017-06-14_1948.zip /sdcard/
It will take some time so grab a coffee or play with the cat.
Done?
Good!
Click Install.
Go all the way down to the bottom of that directory and click on the zip file and let it install.
Now just reboot the phone and wait until the boot is finished because the first boot will take a little while.

925I

Any news for release ???

On every lineage os rom I tried for g925f is the failure that, if I lock my phone with the powerbutton its impossible to turn it on again...I have to restart it. And also the sensitive buttons don't work

Billabomb75 said:
Any news for release ???
Click to expand...
Click to collapse
Well, there won't be one unless you're willing to help working on it.
Make a manifest that's as close as possible to Lineage stock and I'll add it to the repo and do a test build.
There aren't any repos for zerolte for Lineage as noone has added support for it.

Umeaboy said:
Well, there won't be one unless you're willing to help working on it.
Make a manifest that's as close as possible to Lineage stock and I'll add it to the repo and do a test build.
There aren't any repos for zerolte for Lineage as noone has added support for it.
Click to expand...
Click to collapse
Well I dont know how to work on android manifests

Billabomb75 said:
Well I dont know how to work on android manifests
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2329228 should help you learn how to do it.
I can't do ALL the work by myself you know.

Umeaboy said:
https://forum.xda-developers.com/showthread.php?t=2329228 should help you learn how to do it.
I can't do ALL the work by myself you know.
Click to expand...
Click to collapse
tnx m8 will look at

alex.X said:
In fact there is a lineage os 14 build for s6 edge
Click to expand...
Click to collapse
None of Lineage OS works on Galaxy S6 , i downloades 4 ROMs , none working. I had hope for one but when i turn screen of it doesnt come back

Its good to see Lineage is working on this.....waiting for a quick stable version from the team.
Very Thanks in advance.

[UNOFFICIAL][G920/5F][7.1.2] LineageOS 14.1 Stable Version
https://forum.xda-developers.com/galaxy-s6/orig-development/rom-lineageos-14-1-t3598775

Lol, TeamNexus always release a multitarget build here and for multitarget I mean 920/5 F/I/T/W8. You can build 925 if you want, I always build mine since my device is not supported (925S)

Question abut command "lunch" for AOSiP huawei honor 5x

I am trying build my own rom from source code, but when i reached to command "lunch", i got an error,
..............................................................................................................................................................
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:43 dumpvars failed with: exit status 1
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:45 dumpvars failed with: exit status 1
** Don't have a product spec for: 'Huawei'
** Do you have the right repo manifest?
...........................................................................................
I tried "lunch Huawei Honor 5x", "lunch device_huawei_kiwi". "lunch kiwi", still got a same error.
Can anyone tell me what is the right name of Huawei Honor 5x for ASOiP. Thanks in advance.

david3709 said:
I am trying build my own rom from source code, but when i reached to command "lunch", i got an error,
..............................................................................................................................................................
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:43 dumpvars failed with: exit status 1
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:45 dumpvars failed with: exit status 1
** Don't have a product spec for: 'Huawei'
** Do you have the right repo manifest?
...........................................................................................
I tried "lunch Huawei Honor 5x", "lunch device_huawei_kiwi". "lunch kiwi", still got a same error.
Can anyone tell me what is the right name of Huawei Honor 5x for ASOiP. Thanks in advance.
Click to expand...
Click to collapse
What software tools are you using to build your ROM?

Thanks for your response.
I did not use any software, i follow the instruction of AlaskaLinuxUser, he has lot of videos for compling custom rom.
I am working in Ubuntu 22.04, and openjdk18, the latest git and repo. And i also use lineage os instruction(https://wiki.lineageos.org/devices/kiwi/build) for reference.
The manifest is from "https://github.com/AOSiP/platform_manifest/tree/pie"
Before command "lunch", everything is ok, and "repo sync -j 4 -c" is fine, no error.
This error looks like the name of device is wrong.
For Lineageos 17.1, i am using "kiwi", it works and already flashed my compiling rom on my phone, and everything is working fine, just sometimes has response lag problem. That is the reason i want to try another rom, i can not accept response lag, want to good performance.
There is office AOSiP rom for my phone, i just want to try to build my own rom for practice and later do some changes.

I am using terminal to build my own rom, and stuck on "lunch", can not find the right device name for honor 5x. need help.

david3709 said:
I am using terminal to build my own rom, and stuck on "lunch", can not find the right device name for honor 5x. need help.
Click to expand...
Click to collapse
david3709 said:
Thanks for your response.
I did not use any software, i follow the instruction of AlaskaLinuxUser, he has lot of videos for compling custom rom.
I am working in Ubuntu 22.04, and openjdk18, the latest git and repo. And i also use lineage os instruction(https://wiki.lineageos.org/devices/kiwi/build) for reference.
The manifest is from "https://github.com/AOSiP/platform_manifest/tree/pie"
Before command "lunch", everything is ok, and "repo sync -j 4 -c" is fine, no error.
This error looks like the name of device is wrong.
For Lineageos 17.1, i am using "kiwi", it works and already flashed my compiling rom on my phone, and everything is working fine, just sometimes has response lag problem. That is the reason i want to try another rom, i can not accept response lag, want to good performance.
There is office AOSiP rom for my phone, i just want to try to build my own rom for practice and later do some changes.
Click to expand...
Click to collapse
Using newer ROMs on older devices is going to cause lag, that is normal. The problem is not the ROM, the problem is your hardware wasn't designed to use newer, more demanding software.

yes, you are right, that is why i want to try android PIE, the reason for building AOSiP Pie is i want to do more practice, after more try, i can really build my own custom rom, right now what i only can do now is to rebuild some custom rom.