Develop Bugs

[Q] Help compiling rom for Find 7a

Hey all!
Trying to build my first rom using AOKP as source. I got everything setup correctly (i think so atleast), but after syncing the repo I keep getting an error.
When I try to lunch, breakfast, or brunch it keeps giving me the error below:
Code:
Which would you like? [aosp_arm-eng] 21
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[vendor/aokp/products/find7.mk]]: "device/oppo/find7/full_find7.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_find7'
** Do you have the right repo manifest?
Any idea? I know it's because /oppo/find7/ files aren't in the device folder, but how do I get them there? I have searched and tried multiple things and am not having any luck. Any help is appreciated!

You sure you're at the source root (e.g.~/android/system)?

I'm running this from root of ~/aokp where I init the repo. Should I be running commands from ~/aokp/system?

dscvads
i figured it out!
Brunching my first rom now using AOKP!
From there, I'm going to make a completely new rom called adastraROM.
Keep an eye out!

Having a similar problem
octonaut said:
i figured it out!
Brunching my first rom now using AOKP!
From there, I'm going to make a completely new rom called adastraROM.
Keep an eye out!
Click to expand...
Click to collapse
How did you solve it? Mind to share it

Need Device tree

Hey people ,
Can someone provide a relevant Xiaomi Redmi 1s device tree so I can start building customs ROM's for this device....

hackerzrulez007 said:
Hey people ,
Can someone provide a relevant Xiaomi Redmi 1s device tree so I can start building customs ROM's for this device....
Click to expand...
Click to collapse
Here is The Device tree :
https://github.com/armani-dev/android_device_xiaomi_armani
and here vender tree :
https://github.com/armani-dev/proprietary_vendor_xiaomi

Getting error while compiling AOSP with the armani device tree
I cloned these repos in device/ and vendor/ directories respectively.
I then ran . build/envsetup.sh which ran but gave this.
including device/android_device_xiaomi_armani/vendorsetup.sh
sh: 0: Can't open device/xiaomi/armani/patches/apply.sh
I anyways went ahead and hit lunch and then this happened when i passed cm_armani-userdebug as the selection.
Which would you like? [aosp_arm-eng] cm_armani-userdebug
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_armani". Stop.
** Don't have a product spec for: 'cm_armani'
** Do you have the right repo manifest?
I am trying to compile android lollipop with this device tree. Will this work? and if it can then where am I doing wrong?

praveenpuglia said:
I cloned these repos in device/ and vendor/ directories respectively.
I then ran . build/envsetup.sh which ran but gave this.
including device/android_device_xiaomi_armani/vendorsetup.sh
sh: 0: Can't open device/xiaomi/armani/patches/apply.sh
I anyways went ahead and hit lunch and then this happened when i passed cm_armani-userdebug as the selection.
Which would you like? [aosp_arm-eng] cm_armani-userdebug
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_armani". Stop.
** Don't have a product spec for: 'cm_armani'
** Do you have the right repo manifest?
I am trying to compile android lollipop with this device tree. Will this work? and if it can then where am I doing wrong?
Click to expand...
Click to collapse
these device tree won't work for cm12 ie lolipop
there are patch, which should be done before compiling rom

Can you tell me more ? I am not trying to build cm lollipop..i am trying to build AOSP stock rom. I just want to know if the cm 11 device tree can be used to conpile AOSP rom!

praveenpuglia said:
Can you tell me more ? I am not trying to build cm lollipop..i am trying to build AOSP stock rom. I just want to know if the cm 11 device tree can be used to conpile AOSP rom!
Click to expand...
Click to collapse
Won't work. Will need heck loads of patches and dirty hacks and display and media repos should be taken from armani-dev.

kD said:
Won't work. Will need heck loads of patches and dirty hacks and display and media repos should be taken from armani-dev.
Click to expand...
Click to collapse
What about using those device trees for cm12?

praveenpuglia said:
What about using those device trees for cm12?
Click to expand...
Click to collapse
As said earlier won't work

Actually OP need 1st step guide with current repo .... I think

delete

Delete this thread

Well, i suddenly visited Mipad sub-forum on XDA and i saw this...
What? You just rename repository from android_device_nvidia_shieldtablet to android_device_xiaomi_mocha...
And it is ALL what you did ???? OMG. No comments. Facepalm.
So i spent 1 hour of my life to make a mocha bring up.
https://github.com/vickdu31/android_device_xiaomi_mocha/pull/1/files
Also you should merge commits which will update selinux to kernel sources.
+ Do not forget about upstream patches.
Cherry-pick it from
https://github.com/CyanogenMod/android_kernel_nvidia_shieldtablet
If YOU continue do nothing, you will receive no result.

tank0412 said:
Well, i suddenly visited Mipad sub-forum on XDA and i saw this...
What? You just rename repository from android_device_nvidia_shieldtablet to android_device_xiaomi_mocha...
And it is ALL what you did ???? OMG. No comments. Facepalm.
So i spent 1 hour of my life to make a mocha bring up.
https://github.com/vickdu31/android_device_xiaomi_mocha/pull/1/files
Also you should merge commits which will update selinux to kernel sources.
+ Do not forget about upstream patches.
Cherry-pick it from
https://github.com/CyanogenMod/android_kernel_nvidia_shieldtablet
If YOU continue do nothing, you will receive no result.
Click to expand...
Click to collapse
Don't blame him. There is a will and intention of him to cook a rom. Everybody needs help and everybody was a beginner.

Yeah I have been pretty busy at school and other stuff so I don't have time, and still I have to learn couple things, I pulled the request, thanks.
I did this in this time : http://gbatemp.net/threads/release-haxchi-installer-1-1-noob-friendly.448890/
I think there is no big hurry and I am really busy at the moment, my point is to get more people working and ofcourse I have to start working on it asap !

There are people working
They just don't open a thread without having done anything because that's not really development

Harrynowl said:
There are people working
They just don't open a thread without having done anything because that's not really development
Click to expand...
Click to collapse
Can't find anyone working on it.. Is there any thread, forum or group or anything where people work ? Even on github I didnt find anything

vickdu31 said:
Can't find anyone working on it.. Is there any thread, forum or group or anything where people work ? Even on github I didnt find anything
Click to expand...
Click to collapse
Yes, it could be great to join your effort to not repeat same work.
Regards.

vickdu31 said:
Can't find anyone working on it.. Is there any thread, forum or group or anything where people work ? Even on github I didnt find anything
Click to expand...
Click to collapse
@Harrynowl is working as far as I know. I'm too but very busy lately.

Status !!?
vickdu31 said:
I create this thread to gather all potential developpers to join me and try to build a CM13.0 (at least a build that boot) for our Mi Pad.
I don't have much experience or knowledge yet but who knows, maybe we can get bootable build soon or later.
To all users : Do not expect anything from this thread in a while.
Current situation :
Just created the device tree from Nexus and Xiaomi sources.
To do right now :
- Totally modify the Device Tree (this is from nexus 9)
- Modify kernel to be able to try to even build something
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xioami_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
I think I cannot do everything all by myself within 6+ month so any help is very welcome just as pull requests.
XDA:DevDB Information
working on Mi Pad, ROM for the Xiaomi Mi Pad
Contributors
vickdu31
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-21
Last Updated 2016-11-26
Click to expand...
Click to collapse
Any progress to look forward to ?

Required help
Can some one guide me through the process of building the rom i already downloaded the cm 13 source. Searched many forums but not able to understand the process how to build for mocha @tank0412 @vickdu31 @Harrynowl

Rohit99 said:
Can some one guide me through the process of building the rom i already downloaded the cm 13 source. Searched many forums but not able to understand the process how to build for mocha @tank0412 @vickdu31 @Harrynowl
Click to expand...
Click to collapse
OMG.
Are you seriously?
. build/envsetup.sh
lunch
*enter number of mochas lunch combo"

You cannot build with these device sources because they are broken

Error while building
tank0412 said:
OMG.
Are you seriously?
. build/envsetup.sh
lunch
*enter number of mochas lunch combo"
Click to expand...
Click to collapse
Got this error while building using command
Code:
brunch mocha
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_mocha". Stop.
Device mocha not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for mocha 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:234: *** Can not locate config makefile for product "cm_mocha". Stop.
** Don't have a product spec for: 'cm_mocha'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
added repos in local_manifest.xml and roomservice.xml
Update :
i was able to brunch but stuck at this error
make: *** No rule to make target 'kernel/xiaomi/mocha/arch/arm/configs/cyanogenmod_mocha_defconfig', needed by '/home/uttara/rom/script/out/target/product/mocha/obj/KERNEL_OBJ/.config'. Stop.
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
@tank0412 please help

Rohit99 said:
Got this error while building using command
Code:
brunch mocha
added repos in local_manifest.xml and roomservice.xml
Update :
i was able to brunch but stuck at this error
@tank0412 please help
Click to expand...
Click to collapse
OMG. Are you seriously?
Put kernel sources to 'kernel/xiaomi/mocha/
It was writtent in the error!
No comments....
And rename defconfig of mocha to cyanogenmod_mocha_defconfig

tank0412 said:
OMG. Are you seriously?
Put kernel sources to 'kernel/xiaomi/mocha/
It was writtent in the error!
No comments....
And rename defconfig of mocha to cyanogenmod_mocha_defconfig
Click to expand...
Click to collapse
@tank0412 I'm very sorry for disturbing you this is my first build so please help, should i rename tegra_defconfig bcoz there is no file named defconfig

Rohit99 said:
@tank0412 I'm very sorry for disturbing you this is my first build so please help, should i rename tegra_defconfig bcoz there is no file named defconfig
Click to expand...
Click to collapse
Oh, GOD.
Check this:
https://github.com/vickdu31/android_kernel_xiaomi_mocha/pull/1/files
And turn on logic

Im working on other projects now, I don't have time at all, I can pull commits, I was thinking about closing this thread but since we can talk I can keep it open, but a discusion thread would be more apropriate

vickdu31 said:
Im working on other projects now, I don't have time at all, I can pull commits, I was thinking about closing this thread but since we can talk I can keep it open, but a discusion thread would be more apropriate
Click to expand...
Click to collapse
@vickdu31 you can close the thread i have created a new thread CM13

DEV's build's Q&A discussion board

As the title says. This board is created for questions and answers pertaining to getting new ROM's and ports for our P9000.
THIS IS NOT A BUG REPORT DISCUSSION.
New Development only.
If you would like to see a new ROM for the P9000? Build it, and share it. Check out some of the guides, then ask some questions on building it.
I will be staying with Mediatek devices for the long term and encourage more people like me to start bringing some development love to them.
Thank you

Some useful guides.
https://www.youtube.com/watch?v=aF--LQDgg1M
http://source.android.com/source/initializing.html
Any guides to add? I'll be glad to add them.

Credits:
@Deepflex (Active) Vendor, Device, Kernel sources
@Jonny (Active) TWRP and multiple additions to Kernel source
@skeleton1911 (Active) Stock based ROM's
@leskal (ACTIVE) device and kernel commits
Please let me know of any credits I'm missing.

Have been working on CandyRom6. Been getting a lunch error in line 234. Not quite sure how to get lunch to point to the correct mk file. candy/device/elephone/p9000/candy.mk. Any suggestions?

syncing AOKP MM. I enjoyed this rom in my samsung days.

something interesting to try for automating builds.
http://forum.xda-developers.com/chef-central/android/guide-tool-projekt-scribt-v1-33-t3503018

electrofryed said:
Have been working on CandyRom6. Been getting a lunch error in line 234. Not quite sure how to get lunch to point to the correct mk file. candy/device/elephone/p9000/candy.mk. Any suggestions?
Click to expand...
Click to collapse
Check the .mk files in the root of your device tree, I'm guessing you need to rename a reference in one of them from something like 'cm.mk' to 'candy.mk'

So far I've modified /AndroidProducts.mk cm.mk vendorsetup.sh I think I'm missing a file to modify. Just not sure which one. Unfortunately, since I didn't make a copy of the original Candy directory, I'll need to resync to get rid of my Troubleshooting changes. Good lesson. After each sync, make sure you make a backup of the original in case you forget the modifications you've made. Lol

I think I figured it out. My product name didn't match the vendorsetup.sh
Update: Nope. That didn't work. I've attached a screenshot of the changes I've made in case anyone wants to chime in.
Thank you

What lunch command are you using?

Jonny said:
What lunch command are you using?
Click to expand...
Click to collapse
I just used lunch to check the build. I used brunch for AOKP and it seems to be working at the moment. I'm going to re sync candy and start from scratch next weekend. I noticed when using lunch in AOKP, it used my git which wasn't setup when building candy.

electrofryed said:
I just used lunch to check the build. I used brunch for AOKP and it seems to be working at the moment. I'm going to re sync candy and start from scratch next weekend. I noticed when using lunch in AOKP, it used my git which wasn't setup when building candy.
Click to expand...
Click to collapse
I recomend the brunch command as on official build guide of cm

Yeah. I tried brunch and "rainbowfarts" (recommended by AOKP. Lol. It stops when calling for maven 1.6 (I'm on 2.10). I think I need to find the file that will link my builds to my build environment path.

leskal said:
I recomend the brunch command as on official build guide of cm
Click to expand...
Click to collapse
BTW. Glad to see you here. I've seen your work on git and wanted to credit you.

electrofryed said:
BTW. Glad to see you here. I've seen your work on git and wanted to credit you.
Click to expand...
Click to collapse
Nice, also check this guide: https://wiki.cyanogenmod.org/w/Build_for_huashan#Install_the_Build_Packages
Maybe you will fix the prob with the "brunch" command

leskal said:
Nice, also check this guide: https://wiki.cyanogenmod.org/w/Build_for_huashan#Install_the_Build_Packages
Maybe you will fix the prob with the "brunch" command
Click to expand...
Click to collapse
Great guide!! I see a few big differences between this guide and some of the others. The biggest is the method of getting java 7 for 16.04. I've been using Oracle and open Java 8 the whole time.

Update. I got past the initial halts in the AOKP build. When it finishes, I will be testing. (in the morning EST)
Update: spoke too soon. Kernel compiling issues. Another hurdle. Ugh

Hello,
i started my first build-experience with downloading the cm13 sources and the p9000 sources form deepflex. Since yesterday i have an successful build cm_p9000-ota.zip package but after installation it ends in an bootloop!! I have no idea where to start searching for the mistake... I get no error massage while installing it.
Could someone give me a hint?

electrofryed said:
Update. I got past the initial halts in the AOKP build. When it finishes, I will be testing. (in the morning EST)
Update: spoke too soon. Kernel compiling issues. Another hurdle. Ugh
Click to expand...
Click to collapse
You need to fix includes when building out of mtk build chain, or use other sources that already have this done

OK, i get it running!
But, is their a reason why "/android_device_elephone_p9000/mediatek_driver_nl80211.h" is missing in the repo? Sorry, but i am totally new and trying to understand how these builds work and what exactly is needed to build a bugles ROM.

[ROM][UNOFFICIAL][10] e/OS 0.22 q for Motorola One xt1941-4

Following this thread, I recently built e/OS 0.22q for Motorola One xt1941-4 (deen). Please refer to https://e.foundation/e-os/ to learn more about e/OS.
After several weeks of usage this ROM seems to be very useful. Find the zip file with the images of the Andoid 10 version here. Unzip and flash using adb and fastboot. Please use at your own risk!
I used the following repos in my local manifest:
https://github.com/electimon/device_motorola_deen, branch Lineage-17.1
https://github.com/electimon/vendor_motorola_deen, branch Lineage-17.1
https://github.com/100Daisy/android_kernel_motorola_deen, branch android-10-release-qpks30.54-22-13
In addition, I included
https://github.com/LineageOS/android_system_qcom, branch Lineage-17.1
which is obviously needed by some stuff from vendor. Vendor files are from 2019, so if someone could provide a more recent repo, I would be glad to know (last stock rom provided by Motorola is from October 2021)
All credits go to the creators of the LineageOS 17.1 port (link to thread at the top of this post)! Very good job guys!

Works just fine, thanks.

LSV12 said:
Works just fine, thanks.
Click to expand...
Click to collapse
Thanks!

Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian

01nick07 said:
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
Click to expand...
Click to collapse
I'm sorry, but I have no time and I am not good at making tutorials at all. Please refer to the thread referenced at the beginning of the initial post. There you should find all necessary information. If this is not enough, do some more searching and reading on XDA. If you still feel uncomfortable, stay with the stock rom.

Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'

xdadevc said:
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
Click to expand...
Click to collapse
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...

HerrElling said:
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
Click to expand...
Click to collapse
I read your article and managed to follow it and compile my own e/os. I'm also not an android developer. I did some kernel work in the early days, around Android 2.0 but my path diverged and now I'm completely lost.
Let's keep in touch. If you restart your efforts, I'll be happy to contribute. Meanwhile I'll try my best to get some info from the e/os forums and (pray) the lineageos residual devs.