Develop Bugs

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

How to Build AOSB from source

I am wanting to build AOSB from source with newer CM 11 as base
How do I build it repo is https://github.com/AOSB?page=1
Many thanks hope someone can help please

anttaz said:
I am wanting to build AOSB from source with newer CM 11 as base
How do I build it repo is https://github.com/AOSB?page=1
Many thanks hope someone can help please
Click to expand...
Click to collapse
Assume you have setup build environment.
1. Repo init AOSB source
2. [email protected] device/htc/endeavoru, device/htc/tegra3-common, vendor/htc, kernel/htc to appropriate path.
3. Modify .mk file in device/htc/endeavoru per AOSB
Hint : maybe you also need more missing repo in AOSB from CM..especially wifi stuff

yes ubuntu build environment set up just need to know how to build. I am a bit of a newbie to Android, Many thanks for the response

audahadi said:
Assume you have setup build environment.
1. Repo init AOSB source
2. [email protected] device/htc/endeavoru, device/htc/tegra3-common, vendor/htc, kernel/htc to appropriate path.
3. Modify .mk file in device/htc/endeavoru per AOSB
Hint : maybe you also need more missing repo in AOSB from CM..especially wifi stuff
Click to expand...
Click to collapse
yes ubuntu build environment set up just need to know how to build. I am a bit of a newbie to Android, Many thanks for the response

Read some guide to understand a bit about build process.XDA university @ CM wiki have lot of resources.
repo init -u https://github.com/AOSB/android.git -b cm-11.0
They have crap commit for newbie to build..hope that link work.
After you have all device tree setup properly.
.build/envsetup.sh && brunch endeavoru

audahadi said:
Read some guide to understand a bit about build process.XDA university @ CM wiki have lot of resources.
repo init -u https://github.com/AOSB/android.git -b cm-11.0
They have crap commit for newbie to build..hope that link work.
After you have all device tree setup properly.
.build/envsetup.sh && brunch endeavoru
Click to expand...
Click to collapse
404 this is not the page you are looking for?

audahadi said:
Read some guide to understand a bit about build process.XDA university @ CM wiki have lot of resources.
repo init -u https://github.com/AOSB/android.git -b cm-11.0
They have crap commit for newbie to build..hope that link work.
After you have all device tree setup properly.
.build/envsetup.sh && brunch endeavoru
Click to expand...
Click to collapse
Read up I just don't get the device tree part of it now?

anttaz said:
Read up I just don't get the device tree part of it now?
Click to expand...
Click to collapse
Compare with other AOSB devices..what they change @ needed to compile for AOSB.

audahadi said:
Compare with other AOSB devices..what they change @ needed to compile for AOSB.
Click to expand...
Click to collapse
Well no luck as no other devices have a guide on building and asking the chefs of the ROMs on xda and on official asob site no response other than yourself. So still none the wiser

audahadi said:
Compare with other AOSB devices..what they change @ needed to compile for AOSB.
Click to expand...
Click to collapse
I have the manifest xml now will this help in the building process?

anttaz said:
I have the manifest xml now will this help in the building process?
Click to expand...
Click to collapse
Should be similar to this
http://wiki.cyanogenmod.org/w/Endeavoru_Info
Honestly..their source is crap..can't find much information to help you with. Just use another rom..

audahadi said:
Should be similar to this
http://wiki.cyanogenmod.org/w/Endeavoru_Info
Honestly..their source is crap..can't find much information to help you with. Just use another rom..
Click to expand...
Click to collapse
Many thanks for all your help anyways. Much appreciated

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.

[DISCUSSIONS][TESTING][ROM][UNOFFICIAL] CyanogenMod 13 ALPHA Build

This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_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
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13

Reserved

Edit 1:initial build didn't boot for me, no adb can't get log

Ok im gonna try it.
If you want, i can leave logcat for you

OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.

Ofc, it doesn't boot. And don't create threads without testing.

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.

Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought

Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar

Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.

Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha

You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.

What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?

highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10

Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.

highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet

My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.

drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.

Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.

Trying to build Resurrection Remix 6.0 for A5 2017

Hey y'all!
I've seen that there aren't any lineageos 15.1 roms for a5 2017 out there so I decided I will build my own.
I followed the guide on rr's github page and I when I typed "breakfast a5y17lte" I got a big error that it cannot find the makefile. Also in device/samsung/a5y17lte there wasn't "vendorsetup.sh".
Please help.

Hello,
First, you can't build booting oreo aosp rom from actual sources.
Second, if you can't deal with something like that - leave building your own rom, or if you want to fight with that error, just use google and little common sense, nothing hard.
Good luck!

I'm glad someone out there is building custom roms for a5 2017. I looked for some the other day and couldn't find many.
Sent from my Samsung SM-A520W using XDA Labs

sheepkill15 said:
Hey y'all!
I've seen that there aren't any lineageos 15.1 roms for a5 2017 out there so I decided I will build my own.
I followed the guide on rr's github page and I when I typed "breakfast a5y17lte" I got a big error that it cannot find the makefile. Also in device/samsung/a5y17lte there wasn't "vendorsetup.sh".
Please help.
Click to expand...
Click to collapse
I got the same issue. I imported vendorsetup.sh from a device repo for another device, and adapted it to my own.
Code:
add_lunch_combo rr_a5y17lte-userdebug
This makes it show up in lunch combo but i get the same error as you,
Code:
Which would you like? [aosp_arm-eng] 16
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/samsung/a5y17lte/rr.mk]]: "device/samsung/universal7880-common/common.mk" does not exist. Stop.
Device a5y17lte not found. Attempting to retrieve device repository from ResurrectionRemix-Devices Github (http://github.com/ResurrectionRemix-Devices).
Repository for a5y17lte not found in the ResurrectionRemix-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/roomservice.xml
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/samsung/a5y17lte/rr.mk]]: "device/samsung/universal7880-common/common.mk" does not exist. Stop.
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/samsung/a5y17lte/rr.mk]]: "device/samsung/universal7880-common/common.mk" does not exist. Stop.
** Don't have a product spec for: 'rr_a5y17lte'
** Do you have the right repo manifest?
I know this is very late too, but I'm just glad to see that I wasn't the only one having this issue.

YoMarshMellow said:
I got the same issue. I imported vendorsetup.sh from a device repo for another device, and adapted it to my own.
This makes it show up in lunch combo but i get the same error as you,
I know this is very late too, but I'm just glad to see that I wasn't the only one having this issue.
Click to expand...
Click to collapse
Actually, I managed to fix these and succesfully go along my merry way after a few days of google searches