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

[DEVELOPERS-ONLY]CyanogenMod 12 EARLY Builds Discussions

Hello all,
I've started working on CM12 for RedMi 1S. So here I'm going to discuss about the further status and builds for the rom.
For those who wants to join and help out :-
Current Status :-
Tree is now buildable without any sort of errors
ROM doesn't boots stucks at MI logo
So Kernel ain't loading up yet
I'd request to make pull request if you've any fix for anything.
CREDITS :-
armani-dev(fefifofum, Kra1o5 for all their work and base tree)
CyanogenMod
If anyone missed here please pm me

ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F

kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707

Tarun93 said:
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Click to expand...
Click to collapse
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.

kD said:
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
Click to expand...
Click to collapse
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal

Tarun93 said:
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Click to expand...
Click to collapse
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.

kD said:
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
Click to expand...
Click to collapse
kkkkkkkkk keep me updated i will dig more info i can

kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.

jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?

jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
kD said:
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
Click to expand...
Click to collapse
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?

Awesome!

kD said:
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Click to expand...
Click to collapse
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.

i do agree with jsevi83 pal even i tried with my noob knowledge now m bored

jsevi83 said:
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
Click to expand...
Click to collapse
I went through your changes. I've came to some conclusions.
Add display_config header
Well it adds display_config header at CM11 but at CM12 it is already present.
display_config header at CM12 just add this line at the bottom rest all is same.
Code:
// set the view frame information in hwc context from surfaceflinger
int setViewFrame(int dpy, int l, int t, int r, int b);
This is the only extra part at CM12's display_config header?
So can you tell em do actually need to comment out this line?
Now libmemtrack is already present at CM12.
Now at media
mm-core/inc/QCMetaData.h is edited to disable few components but if i do the same at CM12 it throws the build error?
Build error is already posted above.
Any idea for fix would be really helpful.

good luck
:fingers-crossed: i am not a dev , but i can be a tester for yu guys .. good job friends , i wish to apreciate your effort towards redmi 1s.. hope to seee lolipop on our devices soon

the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b

thewisenerd said:
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
Click to expand...
Click to collapse
I've done those commits for fixing display. They were applied at CM11 same needs to be applied at CM12. So I need them.

https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))

thewisenerd said:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
Click to expand...
Click to collapse
yeah just figured out you're right. changes at media were just done to override the path because it was changed display-caf-legacy.
Removed those edits.
Now just need to fix display build error.
Building now will post error here soon.
p.s. thank you

Any update ?

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.

GPL Source Request

Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob

bob2600 said:
Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/blob/MMI-NPN25.137-15/arch/arm/configs/ext_config/mot8953-potter.config
:good:

The sources are already out....

Oh really? My bad... Can I just pull from that kernel-msm repo mentioned in the original post? Or is there a different repo just for Potter?

It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.

bob2600 said:
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
Click to expand...
Click to collapse
All the best. :good:

rayzen6 said:
All the best. :good:
Click to expand...
Click to collapse
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...

bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
Man yes let me mention the guy who successfully ​able to build with Alberto's sources. He is @i.snehal.kiran.
He has done this to compile but unfortunately for some reason he doesn't able to get the device to test. His msg is below
basically i have taken addison device tree ...just change the kernel path and defconfig name in boradconfig.mk ..makes it build boot.img
the source provided by motorola on github is full of errors..so use alberto's kernel for addison till you get official kernel from moto
https://github.com/Alberto97/android_kernel_motorola_msm8953
I edited the post bcz I thought u want to work with custom kernel for stock rom. And I thought this might not be useful.

bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.

rayzen6 said:
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
Click to expand...
Click to collapse
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.

bob2600 said:
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
Click to expand...
Click to collapse
Cool. Good work man. I'm in for testing.

Kernel sources are up
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPN25.137-33

ParanoidAndroid build error

Hello, guys.
I have a problem with building Paranoid on my D855 device, here's a log: https://pastebin.com/raw/EUZfeFgg
I put https://github.com/xiaolu/mkbootimg_tools already and that fixed dt.img problem, but there's next one with ramdisk-recovery.img (or recovery.img).
Can you help me?

What was your first error, show your device and common tree, show your local_manifest.

ppajdek said:
What was your first error, show your device and common tree, show your local_manifest.
Click to expand...
Click to collapse
the first error was the same, but instead of ramdisk-recovery.img/recovery.img was just dt.img
https://github.com/LineageOS/android_device_lge_d855
https://github.com/LineageOS/android_device_lge_g3-common
https://github.com/LineageOS/android_kernel_lge_g3
https://github.com/TheMuppets/proprietary_vendor_lge
these are all that I use

You must make device tree compatible with PA source.
https://github.com/AOSPA/android_vendor_pa/tree/nougat-caf/products
https://github.com/AOSPA/android_device_lge_d855
https://github.com/AOSPA/android_device_lge_g3-common
its old brach but get you idea
compare it to ex. "bacon" and make necessary changes
Im syncing PA right now, will try to build it

ppajdek said:
You must make device tree compatible with PA source.
https://github.com/AOSPA/android_vendor_pa/tree/nougat-caf/products
https://github.com/AOSPA/android_device_lge_d855
https://github.com/AOSPA/android_device_lge_g3-common
its old brach but get you idea
compare it to ex. "bacon" and make necessary changes
Im syncing PA right now, will try to build it
Click to expand...
Click to collapse
wielkie dzięki, spróbuję. można jakiś bliższy kontakt (telegram, whatsapp)?
(thank you so much, I am going to try it)