Trying to do my own build for my G3 (D855). I've followed the tutorial on the lineage wiki but when i get to Brunch i get this error:
Looking for dependencies in device/lge/d855
Looking for dependencies in device/lge/g3-common
Looking for dependencies in device/qcom/common
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:252: *** Product "lineage_d855" ambiguous: matches device/vendor/lge/d855/lineage.mk device/lge/d855/lineage.mk. Stop.
build/core/product_config.mk:252: *** Product "lineage_d855" ambiguous: matches device/vendor/lge/d855/lineage.mk device/lge/d855/lineage.mk. Stop.
** Don't have a product spec for: 'lineage_d855'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
HELP! Please!!
Thanks
Attach your roomservice.xml. It is in .repo/local_manifests.
Thanks Gagmani. Manifest attached.
Try to add the following line to the manifest, repo sync and try breakfast. Meanwhile the dependencies error is I am also not sure about. I am also facing the same error. Tried all the suggestions here on XDA. But adding this line should help with ambiguous error. A person with an LG G3 could be more helpful.
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" revision="cm-14.1" />
same errors I'm afraid. thanks anyway
crispy77 said:
same errors I'm afraid. thanks anyway
Click to expand...
Click to collapse
add this in your local manifest
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-14.1" />
so it looks like this
Code:
<manifest>
<project name="LineageOS/android_device_lge_d855" path="device/lge/d855" remote="github"/>
<project name="LineageOS/android_device_lge_g3-common" path="device/lge/g3-common" remote="github"/>
<project name="LineageOS/android_kernel_lge_g3" path="kernel/lge/g3" remote="github"/>
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github"/>
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-14.1" />
</manifest>
then
Code:
make clean
repo sync
. build/envsetup.sh && lunch lineage_d855-userdebug && make -j8 otapackage
Thanks for the help. Will try again soon but just realised my drive has run out of space for the build ATM so off scavenging..
i just did a successful build (had to borrow some of the qualcomm files from the d855 & download proprietary files for the vs985 from github).... i'll go ahead and upload it, and if you need help building it i can offer what help i can (was my first build, roms working just as well as my other non verizon G3s though).
sorry wrong thread
Wrong thread sorry
Related
http://forum.xda-developers.com/showthread.php?t=1863547&highlight=signal
Im trying to compile my own AOSPA for the S4
i got a noob question. When I try to # Initialize the ParanoidAndroid Repo i get a error on the terminal that states
/home/joel/bin/repo: line 1: syntax error near unexpected token `newline'
/home/joel/bin/repo: line 1: `<!DOCTYPE html>'
can somebody help me on what extactly im doing wrong. Ive googled it and found nothing that helped out.
jm492705 said:
http://forum.xda-developers.com/showthread.php?t=1863547&highlight=signal
Im trying to compile my own AOSPA for the S4
i got a noob question. When I try to # Initialize the ParanoidAndroid Repo i get a error on the terminal that states
/home/joel/bin/repo: line 1: syntax error near unexpected token `newline'
/home/joel/bin/repo: line 1: `<!DOCTYPE html>'
can somebody help me on what extactly im doing wrong. Ive googled it and found nothing that helped out.
Click to expand...
Click to collapse
I will assume you followed the preceding instructions about installing Python and that it was configured correctly. I would say to "rm -rf ~/bin/repo", which will remove the folder /repo and all its contents... then to start back at #Install the Repo.
lordcheeto03 said:
I will assume you followed the preceding instructions about installing Python and that it was configured correctly. I would say to "rm -rf ~/bin/repo", which will remove the folder /repo and all its contents... then to start back at #Install the Repo.
Click to expand...
Click to collapse
i did what you told me to attempt and still got the same error when try to #Install the Repo. Is there anything else that i can do. i just don't get what im doing wrong because i did it right when i did my own CM build, just attempiting now to make my own AOSPA ROM for the S4.
i was able to Initialize the ParanoidAndroid Repo but now im stuck on adding the specific device trees for the S4. how do i find it and where? im confused
jm492705 said:
i was able to Initialize the ParanoidAndroid Repo but now im stuck on adding the specific device trees for the S4. how do i find it and where for my specific device? im confused on what to do next. plz help
Click to expand...
Click to collapse
jm492705 said:
i was able to Initialize the ParanoidAndroid Repo but now im stuck on adding the specific device trees for the S4. how do i find it and where? im confused
Click to expand...
Click to collapse
I assume there's a better way than mine, but I always go into <your source location>/.repo and edit manifest.xml to include CM's android_device_samsung_jf-common, android_device_samsung_jfltetmo, and android_kernel_samsung_jf. After adding them to your manifest, just do another repo sync and you should have everything you need to start cranking out a build...
lordcheeto03 said:
I assume there's a better way than mine, but I always go into <your source location>/.repo and edit manifest.xml to include CM's android_device_samsung_jf-common, android_device_samsung_jfltetmo, and android_kernel_samsung_jf. After adding them to your manifest, just do another repo sync and you should have everything you need to start cranking out a build...
Click to expand...
Click to collapse
is this the right informartion that i need to add to the manifest?
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_jfltetmo" path="device/samsung/jfltetmo" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_jf-common" path="device/samsung/jf-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_jf" path="kernel/samsung/jf" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
jm492705 said:
is this the right informartion that i need to add to the manifest?
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_jfltetmo" path="device/samsung/jfltetmo" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_jf-common" path="device/samsung/jf-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_jf" path="kernel/samsung/jf" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
Click to expand...
Click to collapse
That looks good, but I didn't even think that @ayysir has his PA tree on his github.
I've never built PA but I would assume you could use CM's tree with a few modifications here and there.
lordcheeto03 said:
That looks good, but I didn't even think that @ayysir has his PA tree on his github.
I've never built PA but I would assume you could use CM's tree with a few modifications here and there.
Click to expand...
Click to collapse
So would it be okay for me to put the CM trees that it in the local manifest? just making sure, and then do the repo sync sorry for the noobness just getting the hang of things and really intrested on building PA
jm492705 said:
So would it be okay for me to put the CM trees that it in the local manifest? just making sure, and then do the repo sync sorry for the noobness just getting the hang of things and really intrested on building PA
Click to expand...
Click to collapse
http://www.github.com/aospa-legacy
I am trying to compile CM12 on my own for the D850 and I am curious what people are using for the Local Manifest file. I found one thread talking about building CM12 for the LG G3, but it seemed to be for the D855 and it seemed like it might be using 3rd party sources on Github.
So I'm trying to find out what the full local manifest should be for my D850 CM12 build. I am a compile noob, so being able to tell me/show me what the full manifest file should contain would be greatly appreciated. Also, if you could tell/show me how you found out this information, so I can figure it out for myself in the future, that would be awesome
I found this on the CM website - http://wiki.cyanogenmod.org/w/Local_manifest
It tells me to grab this file on the LG G3 that I have CM12 on already "/system/etc/build-manifest.xml", but when I look at that file, it has HUGE. the local_manifest.xml file for the N5 that I'm building only has like 3-4 entries.
Is this huge file really the local_manifest that I need to use to build CM12 for the D850 LG G3?
Here's mine (edited for you), cyanogenmod doesnt seem to have "proprietary_vendor_lge", so i left it how I have mine.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/g3-common" name=CyanogenMod/android_device_lge_g3-common" remote="github" revision="cm-12.0" />
<project path="device/lge/d850" name="CyanogenMod/android_device_lge_d850" remote="github" revision="cm-12.0" />
<project path="kernel/lge/g3" name="CyanogenMod/android_kernel_lge_g3" remote="github" revision="cm-12.0" />
[B]<project path="vendor/lge" name="ResurrectionRemix/proprietary_vendor_lge" remote="github" revision="lollipop" />[/B]
<project path="device/qcom_common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.0" />
</manifest>
Thank you for the response. I did just find this in CM's github
- https://github.com/CyanogenMod/android_device_lge_g3-common
and this
- https://github.com/CyanogenMod/android_kernel_lge_g3
rhystagram said:
Here's mine (edited for you), cyanogenmod doesnt seem to have "proprietary_vendor_lge", so i left it how I have mine.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/g3-common" name=CyanogenMod/android_device_lge_g3-common" remote="github" revision="cm-12.0" />
<project path="device/lge/d850" name="CyanogenMod/android_device_lge_d850" remote="github" revision="cm-12.0" />
<project path="kernel/lge/g3" name="CyanogenMod/android_kernel_lge_g3" remote="github" revision="cm-12.0" />
[B]<project path="vendor/lge" name="ResurrectionRemix/proprietary_vendor_lge" remote="github" revision="lollipop" />[/B]
<project path="device/qcom_common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.0" />
</manifest>
Click to expand...
Click to collapse
Very awesome. Thank you for your help. Is there anything wrong/bad about using Resurrection's proprietary vendor one for my vanilla CM12 build for the d850?
I've seen someone using this one. . .
<project path="vendor/lge" name="sooti/proprietary_vendor_lge" remote="github" revision="cm-12.0" />
but it was for the D855. I don't know if these will mess up my build since I'm compiling for the D850 instead.
Again, thank you for the help. It is greatly appreciated.
view step 3 here, it has the local_manifest details, they're from sooti, which was before CM official builds..
maybe use his vendor, but official cm repostories for others.
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
just noticed you replied, pretty sure as long as you have the d850 files, and run the "brunch d850" the vendor will still run correctly, as it's a vendor for LGE.
rhystagram said:
view step 3 here, it has the local_manifest details, they're from sooti, which was before CM official builds..
maybe use his vendor, but official cm repostories for others.
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
just noticed you replied, pretty sure as long as you have the d850 files, and run the "brunch d850" the vendor will still run correctly, as it's a vendor for LGE.
Click to expand...
Click to collapse
Awesome. Thank you again, sooooo very much. It's running a repo sync now :fingers-crossed:
I'm used to running "time brunch <codename>"
is that the same as the "brunch <codename>" that you just suggested? I'm not sure what the difference between time brunch and just brunch
Enddo said:
Awesome. Thank you again, sooooo very much. It's running a repo sync now :fingers-crossed:
I'm used to running "time brunch <codename>"
is that the same as the "brunch <codename>" that you just suggested? I'm not sure what the difference between time brunch and just brunch
Click to expand...
Click to collapse
time brunch shows you how long it takes to build (i think), brunch just builds .
rhystagram said:
time brunch shows you how long it takes to build (i think), brunch just builds .
Click to expand...
Click to collapse
Well, it all seemed to work but then I got an error toward the end
Code:
/bin/sh: 1: lz4c: not found
make[4]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/doug/lgg3/kernel/lge/g3'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
real 52m2.413s
user 204m32.365s
sys 21m4.082s
I found a thread talking about that error and someone suggested to do a sudo apt-get install lzop, but it says I already have that
Code:
sudo apt-get install lzop
[sudo] password for doug:
Reading package lists... Done
Building dependency tree
Reading state information... Done
lzop is already the newest version.
The following packages were automatically installed and are no longer required:
libgpds0 linux-headers-3.13.0-32 linux-headers-3.13.0-32-generic
linux-headers-generic linux-image-3.13.0-32-generic
linux-image-extra-3.13.0-32-generic linux-image-generic python-pyudev
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Found a suggestion to run "sudo apt-get install liblz4-tool", I installed that and am trying the process over again
Enddo said:
Well, it all seemed to work but then I got an error toward the end
Code:
/bin/sh: 1: lz4c: not found
make[4]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/doug/lgg3/kernel/lge/g3'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
real 52m2.413s
user 204m32.365s
sys 21m4.082s
Click to expand...
Click to collapse
can't help here man, it's happened to me, only solution i found to fix it for me was to make a new directory & download all sources again & build from there. (didn't try the solution you are, let me know how it goes?)
rhystagram said:
can't help here man, it's happened to me, only solution i found to fix it for me was to make a new directory & download all sources again & build from there. (didn't try the solution you are, let me know how it goes?)
Click to expand...
Click to collapse
After doing a "sudo apt-get install liblz4-tool", I did the whole compile process over, didn't even do a make clean(but I might if there is something wrong with the flash), and it seemed to compile perfectly.
I had to let it run while I was sleeping so I didn't get a chance to flash it yet. Do you know if these are already 'bumped', or if I have to do something special to them now that they have been compiled? I'm almost certain the CM repos have the Bump code in them, but I just wanted to double check in case anyone else knows for sure
and thank you again for all the help. I just have no idea how to get the local manifest information for these builds. I've had help with both the N5 and now the G3. I would love to know how to figure out this on my own so I don't have to keep bothering the community
Do you know how to do this? How to know when you have enough items in the manifest and where to get them. It seems like most come from CM but on both the G3 and the N5, there's one that comes from somewhere else.
Like with the N5, it was the proprietary one that came from somewhere else
"<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.0"/>"
I just flashed it and it worked perfectly! Well, I had a force close error on a google app, so I uninstalled the updates, and updated it from Google Play and it launched. This was probably something to do with the dirty flash more than the compile
Thanks again @rhystagram !
I couldn't be more grateful
image is bumped yes
Target boot image: /home/rhys/newrr/out/target/product/d855/boot.img
/home/rhys/newrr/out/target/product/d855/boot.img maxsize=17031168 blocksize=135168 total=7329792 reserve=270336
bumped image: /home/rhys/newrr/out/target/product/d855/boot.img
Made boot image: /home/rhys/newrr/out/target/product/d855/boot.img
glad i could help & glad you got it working!!
I'm trying to build Nougat for this device, which has recently been given a CM14 branch.
I'm getting binary blobs from TheMuppets and after syncing, breakfast gives me this error.
Code:
$ breakfast mondrianwifi
including vendor/cm/vendorsetup.sh
build/core/config.mk:671: COMMON_GLOBAL_C(PP)FLAGS changed
build/core/config.mk:675: *** bailing.... Alto.
Device mondrianwifi not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_mondrianwifi
Default revision: staging/cm-14.0
Checking branch info
Using fallback branch: cm-14.0
Checking if device/samsung/mondrianwifi is fetched from android_device_samsung_mondrianwifi
CyanogenMod/android_device_samsung_mondrianwifi already fetched to device/samsung/mondrianwifi
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_samsung_mondrianwifi
Fetching projects: 100% (1/1), done.
Repository synced!
Looking for dependencies
Done
build/core/config.mk:671: COMMON_GLOBAL_C(PP)FLAGS changed
build/core/config.mk:675: *** bailing.... Alto.
build/core/config.mk:671: COMMON_GLOBAL_C(PP)FLAGS changed
build/core/config.mk:675: *** bailing.... Alto.
** Don't have a product spec for: 'cm_mondrianwifi'
** Do you have the right repo manifest?
This is my local manifest.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_mondrianwifi" path="device/samsung/mondrianwifi" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_kernel_samsung_mondrianwifi" path="kernel/samsung/mondrianwifi" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.0" />
</manifest>
Any clue?
Thanks.
Did you forget to run envsetup.sh first?
Which version of the MSM are you attempting to use?
Ichijoe said:
Did you forget to run envsetup.sh first?
Which version of the MSM are you attempting to use?
Click to expand...
Click to collapse
I didn't forget to run envsetup.sh
I'm using the MSM8974 repo that appears on github.
https://github.com/CyanogenMod/android_device_samsung_mondrianwifi/blob/cm-14.0/cm.dependencies
Which is this one
https://github.com/CyanogenMod/android_device_samsung_msm8974-common/tree/cm-14.0
Thanks for your reply.
(ratafraking stupid spellcheck!!)
It corrected JDK (Java Development Kit), back to MSM... Which is (if we're to be quite honest) a redundant question. As you really don't have much choice beyond the 8974.
But, my rational thinking is either telling me that JDK 7 is no longer supported, or you might have missed some dependency for JDK 8.
I only have JDK 8 installed, I have successfully compiled CM13 with it.
The choice of ROMs has slowly been dipping since Lollipop as more and more ROMs no longer have Official support for Galaxy Nexus.
At the same time, newer ROMs are popping up for other devices and they look quite interesting.
Ones I have been looking at are Dirty Unicorns, Screw'd, AICP and OctOS.
However, building an unofficial ROM has been troublesome for me.
I have been focusing on Marshmallow since there are still some bugs with AOSP/Unlegacy nougat.
My main issue is that it isn't clear which gnex repos I should be adding after I have sync'd the main ROM source.
There are lots of different forks around and it isn't clear which one to choose.
Which repos do I need to add for AOSP based ROMs?
What is the recommended way to add them?
Does it make any difference if the ROM uses Cyanogenmod or Omnirom as a base instead of AOSP?
Has anyone built these (or any other ROMs) privately and would like to share all the commands necessary for a successful build?
Take a look at this backstage development
https://www.androidfilehost.com/?a=show&w=files&flid=18435
SAOSP has more nougat builds,
Then Dirty Unicorn and Pure Nexus.....
Thank him -> @voidz777
My present time is 5 o'clock in the morning.
In other words, it is before going to work.
So I can not write much.lol
Hi, opticyclic
I did not ignore you.
I have been working forever since I got your email.
Because I can not tell the right way unless I port it before telling you.
I was doing screwed work for a while.
https://github.com/voidz777-crewd
But I can not boot it.
Probably, I think it is due to more optimizing.
I got tired because I got tired.lol
After a while, delete https: //github.com/voidz777-crewd.
It is another addition.
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" revision="master" groups="pdk,linux,arm" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" revision="aosp-6.0" />
<project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="unlegacy" revision="stable" groups="omap4" />
<project path="vendor/ti" name="proprietary_vendor_ti" remote="unlegacy" revision="stable" />
<project path="vendor/widevine" name="proprietary_vendor_widevine" remote="unlegacy" revision="aosp-6.0" />
I'm sorry, my English is not good.
If I could write in Japanese here, I can tell you a little more about the way of port.
There is no time now.
PS.Ah, oct could be pored immediately.
@voidz777 No apologies necessary!
Your posts about different ROMs on Google plus are actually what prompted me to try to build some myself!
Thanks for the info.
I'll post back after trying out a few different ROMs and give an update in the OP on any successes.
I tried to build octos with
Code:
repo init -u https://github.com/Team-OctOS/platform_manifest.git -b oct-mm
and this in .repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<project remote="unlegacy" path="device/samsung/tuna" name="android_device_samsung_tuna" />
<project remote="unlegacy" path="hardware/ti/omap4" name="android_hardware_ti_omap4" revision="stable" groups="omap4" />
<project remote="unlegacy" path="vendor/samsung" name="proprietary_vendor_samsung" />
<project remote="unlegacy" path="vendor/ti" name="proprietary_vendor_ti" revision="stable" />
<project remote="unlegacy" path="vendor/widevine" name="proprietary_vendor_widevine" />
</manifest>
However, they are doing something funny with the build/envsetup.sh and it isn't picking up the vendorsetup.sh so the device isn't picked up by brunch/breakfast etc.
As far as I can tell, there is no specific info on GitHub, GooglePlus or any posts on xda on how to add a new device for their ROM.
On to AICP....
Check vendor / rom - name or device / other - device /.
If oct it will be platform_vendor_to.
Let's see the commit log.
Is there any device added?
For example, let's look for mako.
https://github.com/Team-OctOS/platform_vendor_to/commit/d30dd90c018ca521d458c939a2c56ffc5a97741d
Mako has been added by this commitment.
Create the tuna file in the same way.
Well, will you continue your way of thinking? Or do you want to know the answer quickly?
Thanks for the tip.
If they are going to use a different build structure, it should really be on the README or a FAQ somewhere.
It's bad programming practice in general to expect people to search through commit logs just to try to work out how a project works.
So instead of just adding a local manifest, OctOs requires the following:
to.dependencies (same as local manifest but in JSON instead of XML)
to.mk - same as the device board (aosp_tuna.mk)
extra line in vendorsetup_community.sh - it ignores your vendorsetup.sh
Then do lunch aosp_tuna-userdebug.
Then do mka bacon
However, the first time I did this, it overwrote my .repo/local_manifest/roomsevice.xml with a generated version that contained octos revisions instead of the aosp revisions, which obviously failed as there is no octos revision in unlegacy!
Weirdly, after reverting the roomservice.xml and running lunch again didn't overwrite it.
AICP was more straightforward.
I just added the roomservice.xml and ran lunch aosp_tuna-userdebug and mka bacon.
However, both failed with the following error:
Code:
build/core/base_rules.mk:157: *** packages/apps/Nfc//nxp/jni: MODULE.TARGET.SHARED_LIBRARIES.libnfc_jni already defined by packages/apps/Nfc/nxp/jni/. Stop.
What is weird about this is that it is the same module defining the library, however, the first one has a double slash in the path!
Probably revert this commit
https://github.com/Team-OctOS/platf...mmit/1b8ed2250fc89adce8e0b0dbb6c5ca4d82705ccb
Sent from my Nexus 5
Good catch.
I wonder how that didn't cause a build failure on the build servers.
The next failure in both was:
Code:
build/core/base_rules.mk:157: *** hardware/invensense/60xx/mlsdk: MODULE.TARGET.SHARED_LIBRARIES.libmlplatform already defined by device/samsung/tuna/libsensors. Stop.
That was resolved by removing the Cyanaogenmod project and using the unlegacy one instead, so the local manifest now looks like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<remove-project name="CyanogenMod/android_hardware_invensense" />
<project name="android_device_samsung_tuna" path="device/samsung/tuna" remote="unlegacy" />
<project name="android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="unlegacy" revision="stable"/>
<project groups="omap4" name="android_hardware_ti_omap4" path="hardware/ti/omap4" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" />
<project name="proprietary_vendor_ti" path="vendor/ti" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_widevine" path="vendor/widevine" remote="unlegacy" />
</manifest>
I chose revision="stable" for android_kernel_samsung_tuna", although there is also "aosp-6.0-sound" but I just wanted any kernel to allow me to compile at this point.
The next error (both ROMs) is this (maven 3 is installed)
Code:
make: *** No rule to make target '/home/buildbot/android/aicp/out/target/common/obj/JAVA_LIBRARIES/ambientsdk_intermediates/aar/classes.jar', needed by '/home/buildbot/android/aicp/out/target/common/obj/APPS/messaging_intermediates/AndroidManifest.xml'. Stop.
This relates to this dir https://github.com/AICP/vendor_aicp/
Interestingly, ambientsdk dir existed all thoughout the n7.0 branch and only got removed recently in the n7.1 branch
https://github.com/AICP/vendor_aicp/commit/8f150895f8b361480ac91ef0ace941e06e9f548e
I also don't see any maven messages in the build log and com.cyngn.ambient/ambientsdk/ is not in my ~/.m2/repository which makes me wonder if I am missing a project.
The only similar errors I see online are if people don't have maven installed.
I tried removing the files like the 7.1 branch even though it felt wrong,
Code:
rm vendor/aicp/overlay/common/frameworks/base/core/res/res/values/cm_arrays.xml
rm -rf vendor/aicp/ambientsdk
Not surprisingly, it seems like something else is calling it as the same error pops up 25 mins into build.
repo grep ambientsdk shows ContactsCommon, Trebuchet and ContactsProvider using it in the Android.mk files and grepping for ambient shows lot of java imports.
So now I am stuck again.
To be honest, I wasn't expecting to have to deal with errors like this as they don't seem to be device specific.
i.e. there are builds for other devices so how did they compile?
i have posted nethunter rom here: https://forum.xda-developers.com/galaxy-nexus/development/rom-kali-linux-net-hunter-t3676472
Hi, I'm trying to build LOS 16.0 for the kltedv but it keeps crashing (error message at the end of post).
These are the steps I'm taking on Ubuntu.
Code:
repo init -u git://github.com/LineageOS/android.git -b lineage-16.0
Code:
repo sync --force-sync --no-clone-bundle --no-tags
Code:
cd .repo && mkdir local_manifests && cd local* && subl roomservice.xml
In roomservice.xml, I have
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="platform/prebuilts/qemu-kernel" />
<project name="knaik95/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_kltedv" path="device/samsung/kltevzw" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_klte-common" path="device/samsung/klte-common" remote="github" revision="lineage-16.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="lineage-16.0"/>
<project name="LineageOS/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" revision="lineage-16.0"/>
</manifest>
Code:
repo sync
Code:
source build/envsetup.sh
Code:
add_lunch_combo lineage_kltedv-userdebug
Code:
breakfast kltedv
And this is where it says
Code:
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_kltedv".
Has something changed in the build process from the upgrade from 15.1 to 16.0?
Same here. I am trying to build LOS16 for my moto device. Device tree builds fine with LOS 15.1. But fails for LOS 16. Error is same "build/make/core/product_config.mk:234: error: Can not locate config makefile for product". @knaik95, were you able to get pass this situation? Please update.
Thanks
KS
kalyansundhar said:
Same here. I am trying to build LOS16 for my moto device. Device tree builds fine with LOS 15.1. But fails for LOS 16. Error is same "build/make/core/product_config.mk:234: error: Can not locate config makefile for product". @knaik95, were you able to get pass this situation? Please update.
Thanks
KS
Click to expand...
Click to collapse
Defining AndroidProducts.mk in device tree resolved the problem.
Thanks
KS
kalyansundhar said:
Defining AndroidProducts.mk in device tree resolved the problem.
Thanks
KS
Click to expand...
Click to collapse
Yep. I also renamed lineage.mk to lineage_[device name].mk just to be safe. Did you get any farther? I was met with a bunch of missing dependencies after that. The first one was gradle-plugin, which I fixed by git cloning from the official aosp site, but the others I'm not sure how to get past.
knaik95 said:
Yep. I also renamed lineage.mk to lineage_[device name].mk just to be safe. Did you get any farther? I was met with a bunch of missing dependencies after that. The first one was gradle-plugin, which I fixed by git cloning from the official aosp site, but the others I'm not sure how to get past.
Click to expand...
Click to collapse
I didn't face any further issues so far. But I have to wait and watch.
Thanks
KS
Sent from my Moto G5s using Tapatalk
Can you explain that.. in that detail please
kalyansundhar said:
Defining AndroidProducts.mk in device tree resolved the problem.
Thanks
KS
Click to expand...
Click to collapse
there is a file exist in device tree AndroidProduct.mk
I wish you success @knaik95 with your build.
I do recall flashing your RR Oreo builds and they were awesome!!
pmduper said:
I wish you success @knaik95 with your build.
I do recall flashing your RR Oreo builds and they were awesome!!
Click to expand...
Click to collapse
Oh, uh.... yeah I figured out what I was doing a while ago. I've built and tested LiquidRemix based on Android Pie a couple times; I was satisfied with the result. Not a daily driver yet because we're atm without Xposed SDK28 so still on RR Oreo :silly:
knaik95 said:
Oh, uh.... yeah I figured out what I was doing a while ago. I've built and tested LiquidRemix based on Android Pie a couple times; I was satisfied with the result. Not a daily driver yet because we're atm without Xposed SDK28 so still on RR Oreo :silly:
Click to expand...
Click to collapse
Best of luck with your project.
I've been using a variety of Pie builds for the past couple of months. :good:
pmduper said:
Best of luck with your project.
I've been using a variety of Pie builds for the past couple of months. :good:
Click to expand...
Click to collapse
If you wanna give LiquidRemix a try, I can try to post a link. It was daily driver back when the Galaxy S3 was still relevant and the ROM was called LiquidSmooth. I haven't done a thorough examination of features and what not, but I'd say Liquid rivals the customizability of RR.
redacted