I'm trying to create a build of lollipop dream, and every time I try to compile I get "build/core/product_config.mk:222: *** can not locate config makefile for product " cm_bacon". Stop. Don't have product spec for cm_bacon" I tried to create a full_bacon.mk based of the one that the team provided for their github, but its as if the computer doesn't recognize it. I'm still getting the same error code even if I rename the full_bacon.mk to cm_bacon.mk. any help?
I JUST STARTED COMPILING A ROM WITH SOURCE FOR VILLE C2. I GOT MANY WARNINGS DURING THE PROCESS BUT AT THE END I DIDN'T GOT ANY ERROR. BUT WHEN I CHECK FOR ROM.ZIP IN OUT FOLDER I FOUND NOTHING. CAN ANYONE HELP ME ABOUT THIS:crying::crying:
someone could help me with this error from already thank
ERROR: /media/jbcdroid/Backup/CyanPop/vendor/cmsdk/cm/lib/main/java/org/cyanogenmod/platform/internal/CMHardwareService.java:311: The method isSelfManaged() is undefined for the type SunlightEnhancement
full log: http://hastebin.com/iyotixifox.vhdl:crying:
CM Version: 12.1
I have the same problem and got around by doing a "return false" for the method in CMHardwareService.isSunlightEnhancementSelfManaged (instead of the check that happens there, which is
Code:
public boolean isSunlightEnhancementSelfManaged() {
return SunlightEnhancement.isSelfManaged();
}
The code seems to have been introduced as part of this commit ( 49a1ddcf1f90765b1326f6808f227bcf59e446bd on the cm_platform_sdk repo) but I cant find any references of this being implemented in the osprey specific repositories. Only the core implementation (in android_frameworks_opt_hardware/src/org/cyanogenmod/hardware/SunlightEnhancement.java) seems to have this implemented but none of the device specific ones.
Im quite a newbie to building, so please let me know if Im missing something or doing something wrong, but for now, Ive bypassed this to have a successful build.
Note: Cannot post links yet , which is why I had to provide a hash to the commit that lead to this behaviour.
Thanks
raja
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.
Hey I've been trying to port Ubuntu touch to the A10 following the official guide located here. I've found the device repository for the a10 here, and vendor blobs here. So the XML manifest file I ended up with is this:
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="a10_remote" fetch = "https://github.com/geckyn" revision="lineage-16.0"/>
<project path="device/samsung/a10" name="android_device_samsung_a10" remote="a10_remote"/>
<project path="kernel/samsung/a10" name="android_kernel_samsung_exynos7885" remote="a10_remote"/>
<project path = "vendor/samsung/a10" name="proprietary_vendor_samsung_a10" remote="a10_remote"/>
</manifest>
The "./halium/devices/setup a10" command exits with no errors. But then when I run "breakfast a10", I get the following output:
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "cm_a10". Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
Device a10 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for a10 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your lo
cal_manifests/roomservice.xml.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a10". Stop.
** Don't have a product spec for: 'lineage_a10'
** Do you have the right repo manifest?
The A10 doesn't have an official Lineage OS port, in my knowledge, so I understand that there would be no reference to it on Lineage's GitHub. And I don't mention this repository in my manifest. Why do I get this error then?
Hi, The official support of lineageOS 17.1 for the Samsung galaxy a10 at this time is not released.
You can use the source code of the unofficial port of lineageOS in this thread here : https://forum.xda-developers.com/t/...7-1-for-galaxy-a10-exynos-unofficial.4146815/
section Source Code.
I'm glad you're taking the time to wear this phone model, I've been waiting for a portage for a long time!
I'm french, sorry for my english.
Sundev79 said:
Hi, The official support of lineageOS 17.1 for the Samsung galaxy a10 at this time is not released.
You can use the source code of the unofficial port of lineageOS in this thread here : https://forum.xda-developers.com/t/...7-1-for-galaxy-a10-exynos-unofficial.4146815/
section Source Code.
I'm glad you're taking the time to wear this phone model, I've been waiting for a portage for a long time!
I'm french, sorry for my english.
Click to expand...
Click to collapse
Yeah I'm using the unofficial sources. The error I had above was apparently because of an uncompleted checkout. I am now stuck at another error while building. The entire output from make is here - https://pastebin.com/aznxR9rW. I'd be delighted if you could help.
I working on it, i trying to building halium on lineage-17.1 branch.
Ok, can you help-me, i have this error while launch the command breakfast :
Code:
[email protected]:~/halium-10.0$ breakfast a10
device/samsung/a10/BoardConfig.mk:153: error: device/samsung_slsi/sepolicy/sepolicy.mk: No such file or directory
15:23:39 dumpvars failed with: exit status 1
Device a10 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for a10 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
device/samsung/a10/BoardConfig.mk:153: error: device/samsung_slsi/sepolicy/sepolicy.mk: No such file or directory
15:23:41 dumpvars failed with: exit status 1
device/samsung/a10/BoardConfig.mk:153: error: device/samsung_slsi/sepolicy/sepolicy.mk: No such file or directory
15:23:43 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_a10'
** Do you have the right repo manifest?
[email protected]:~/halium-10.0$
I don't know much about halium 10. I'm building using Halium 9 and Lineage OS 16 sources. I've been able to build halium-boot.img successfully. I'm not the right person to ask as I haven't made a port before. I can make a log of all the steps I took with Halium 9 if you want. @Halium on Telegram will probably be the best place for clarifications. Good luck!
Hi ! do you have succeeded to a bootable build ? what tour advancement ?
Hi, were you able to carry it at the end ?? I am wanting to use ubuntu touch and I only found this thread related to that