Develop Bugs

Building roms for Oppo N1

I understand there are some builds available on github ( https://github.com/omnirom/android_device_oppo_n1 ). Please could anyone guide on how to build it so we can test it on our devices. Thanks.

That would be a pretty in-depth guide.
Omnirom has their own wiki page that can teach you how to compile and port to your device.
http://docs.omnirom.org/Main_Page
:good:

Thank you Harfainx for sharing the guide, I'll try following it and post my finding(s) for everyone.

Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475

nospam said:
Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475
Click to expand...
Click to collapse
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.

I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk

Harfainx said:
I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.

Entropy512 said:
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.
Click to expand...
Click to collapse
Glad to hear an official response. Thanks for the update. :highfive:

viperdream26 said:
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.
Click to expand...
Click to collapse
Maintaining a thread is more work then you would ever think
At the moment I am more then full doing that at oppoforums

I'm going to take a crack at compiling the Cyanogen Source code to take a peek at the o-click issues.
I'm fairly knowledgeable in C, but haven't done any android/bluetooth coding before, so I think I have a snowball's chance in hell.
But it'll be an interesting exercise anyway.
So I'm following random links in:
http://wiki.cyanogenmod.org/w/Development
Mainly using this:
https://skydrive.live.com/view.aspx?cid=B3BFF0D42AE1E534&resid=B3BFF0D42AE1E534!107&app=OneNote
To set up virtualBox/Ubuntu/android SDK.
Although I am a bit confused about required JDK versions.
Is there a list of prefered JDK versions for different CM versions?
I also just noticed the page for the Find 5: aka
http://wiki.cyanogenmod.org/w/Build_for_find5
So I guess I'll use that as the instructions until the actual source code pull?
- Frank

You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick

Entropy512 said:
You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick
Click to expand...
Click to collapse
This is based on the Google BLE sample. It allows pairing with the o-click and will recognise single and double clicks on the remote
Sent from my N1 using Tapatalk

I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.

ChodTheWacko said:
I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.
Click to expand...
Click to collapse
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
add_lunch_combo cm_n1-user
add_lunch_combo cm_n1-userdebug
add_lunch_combo cm_n1-eng
Click to expand...
Click to collapse
Could you just be using the wrong vendorsetup script or should that one run first? Like I said, I'm still very new to this but wanted to at least point this out.

mybrotherischad said:
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
Click to expand...
Click to collapse
You're right, the n1 directory's vendor explicitly lists them.
I was looking at the wrong one I guess. Or it's not being used for some reason.
My Brunch n1 is also complaining with:
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
which doesn't look right, but I'm taking stuff one step at a time.
- Frank

Trying to build OMNI 4.4.4

I am trying to build OMNI 4.4.4 for H60-L02. Right now I have managed to see the bootanimation of omni and then I have a bootloop. These are the logs for anyone who are willing to help
Logcat : http://pastebin.com/RT5x5EjJ
Dmesg : http://pastebin.com/PSzj9XJR
So, let's try to build roms for honor 6 !!! Any help is welcome ....

I don't have the skills but I'm willing to support the initiative as far as I can!

Sounds like the same issue i had, check google-cert folder that you have it and also build the files so that you edit default storage path. It was a few months ago i tried to build my own and i ended up with similair problem and it was related to missing cert and wrong storage path.
Im no expert, its just a hobby of mine so i might be wrong

Is Cyanogenmod avialable to Honor 6
Is Cm 11 available to Honor 6

Kanth's said:
Is Cm 11 available to Honor 6
Click to expand...
Click to collapse
No Cyanogenmod available yet, we all wait for.

HTC HD2 has CM12 already ^^

spanorg said:
I am trying to build OMNI 4.4.4 for H60-L02. Right now I have managed to see the bootanimation of omni and then I have a bootloop. These are the logs for anyone who are willing to help
Logcat : http://pastebin.com/RT5x5EjJ
Dmesg : http://pastebin.com/PSzj9XJR
So, let's try to build roms for honor 6 !!! Any help is welcome ....
Click to expand...
Click to collapse
@spanorg, what do you think of the information of codeworkx?
Daniel Hillenbrand a.k.a. codeworkx is a member of Team CM and TeamHacksung, is a legend

panamera2011 said:
@spanorg, what do you think of the information of codeworkx?
Click to expand...
Click to collapse
Go! go! go!

panamera2011 said:
@spanorg, what do you think of the information of codeworkx?
Daniel Hillenbrand a.k.a. codeworkx is a member of Team CM and TeamHacksung, is a legend
Click to expand...
Click to collapse
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.

spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
Ok, thanks for try to build a CM :good:
Let's hope so!

spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
I've no doubt about this. @spanorg please help codeworkx (this IP the thread: http://forum.xda-developers.com/showthread.php?p=58283578).
He's searching for a tester whit competences. I think your help could be more precious now, you are a recognized developer and you can do more than a tester. you can collaborate whit him, and finally became our leader.
(we can ask for donations or other, if possible, to support your works)
Thanks.

spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.

codeworkx said:
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
Click to expand...
Click to collapse
Hi codeworkx, I tried to compile cyanogenmod11 with your reposity, but I haven't not file local_manifests.xml .. you can send me right local_manifests.xml ?

Steve Giordano said:
Hi codeworkx, I tried to compile cyanogenmod11 with your reposity, but I haven't not file local_manifests.xml .. you can send me right local_manifests.xml ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-6/orig-development/cyanogenmod-dev-thread-t3008138
please don't build if you don't know what you're doing.
This will not boot into android and requires a ton of work.

codeworkx said:
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
Click to expand...
Click to collapse
Do you have a link for the kirin stuff for bionic?

spanorg said:
Do you have a link for the kirin stuff for bionic?
Click to expand...
Click to collapse
sorry, my fault.
just stuff for the bootloader.
vendor/hisi/modem/drv/acore/bootable/bootloader/legacy/arch_balongv7r2

Is this project still active? Just curious.

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.

Device tree, Kernel source, Vendor blobs

Heya, I just got my hands on a J200H, and I get to keep it for a while.
As I was using it, I thought if there is any lineageos for it, and there is not.
Now it would be great if you guys point me where I can find Device tree, Kernel source, Vendor blobs for this device, so that I could start working on this device and add the repo to official lineageos server for build ( provided all things goes smoothly nearly one month is enough )
Also I saw some varients of this device, it would be great if you could add device models (the codes- like J200H) and their source codes too, I could try merging them into a universal source code and patch as universal makes less problem.
Thanks In advance! And any update will be posted here.

I doubt if the things mentioned are available.
But if the are really willing to do this than this can be useful .
Have a look a this
https://web.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
and this
https://forum.xda-developers.com/an...ow-to-create-device-tree-android-rom-t3498355

ad. said:
I doubt if the things mentioned are available.
But if the are really willing to do this than this can be useful .
Have a look a this
https://web.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
and this
https://forum.xda-developers.com/an...ow-to-create-device-tree-android-rom-t3498355
Click to expand...
Click to collapse
got em on samsungs website, but holy ****e their bandwidth....they are killing me.....
Just look at these download speed.... god no...
https://ibb.co/gnDQLQ

uts58 said:
got em on samsungs website
Click to expand...
Click to collapse
I don't know but I guess they are just kernel source .
Once downloaded you can know what is that actually.

@uts58 Are you still working on it????

General Finally! RM8P kernel code source is already released

(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Edit :
It's already released.
Now I hope the developers start creating fantastic roms for this beast phone

salahomer said:
(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Click to expand...
Click to collapse
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Edit: Cool! It's finally released!

JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Very soon, not now...so let us wait a few more days or weeks

JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
I see there are 7S and 6S kernels, but I don't see any custom ROMs for them, so idk if we will see any for this phone too.

The repo is now available, however, it's empty by the time of me posting this now. It took them two weeks just to create the repo, that's insane. Well, at least it finally happened. Waiting for sources to be uploaded, they probably have to use slow vpn or something to do that, so it might take quite a bit of time.

What can we do with the kernel source?

So it is here.

JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Edit :
It's already released, check again.
Now I hope the developers start creating a new fantastic roms for this beast phone

Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.

aaa.bbb111222 said:
Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.
Click to expand...
Click to collapse
So... What does that mean for new custom roms

gwenmillett said:
So... What does that mean for new custom roms
Click to expand...
Click to collapse
We're not gonna see them until someone writes these drivers or zte publishes them. Both are very unlikely, so...

Seems like they uploaded it again, on zips. I checked and it seems to contain several things inside the /drivers/nubia folder so we probably have now a full workable kernel source