Develop Bugs

[Q] Compile CM9 help

After following this tutorial I compiled CM9 for my r800x and everything works fine but since I first compiled I have edited the SystemUI sources. The problem is when I compile it doesn't compile the new sources. Anyone know what I'm doing wrong? Sorry if this is a noob question.
Extra information (not sure if important but might help find the cause):
Using Xubuntu 12.10
Oracle Java 6
I edited /frameworks/base/packages/SystemUI
I compiled for zeusc instead of zeus

What more specifically did you modify? Not sure why it would not rebuild, unless there's some kind of issue with the timestamps or your system clock. (It knows to rebuild if the source files have a newer timestamp than the compiled files they produced)
You can always just do a clean build. You can even just change the output directory without messing up your current build:
http://source.android.com/source/initializing.html said:
export OUT_DIR_COMMON_BASE=<path-to-your-out-directory>
Click to expand...
Click to collapse
You can set that to a different directory and it will build it all over again, putting all the output in that directory instead. With this different, it won't affect the output of your current build and you can always clear this variable to go back. Then you can use this for comparison. Alternatively you can just wipe out your output directory and build it over. You may also be able to dig into your output directory and delete the compiled files for the sources you have modified and then it should definitely notice and rebuild those.
EDIT: Also note that there are build instructions on the CyanogenMod wiki: http://wiki.cyanogenmod.org/w/Build_for_zeus
On the repo init line you can also say '-b jellybean' instead of ics and it will build CM10 (which is pretty good too but not fully stable, it's CM10.1 that is more unstable)
I also noticed that in the 'stable' release of CM9 for zeus the proximity sensor does not work, but there are patches for it in the repo and I've built from source with CM10 and it works fine.
~Troop

Trooper_Max said:
What more specifically did you modify? Not sure why it would not rebuild, unless there's some kind of issue with the timestamps or your system clock. (It knows to rebuild if the source files have a newer timestamp than the compiled files they produced)
You can always just do a clean build. You can even just change the output directory without messing up your current build:
You can set that to a different directory and it will build it all over again, putting all the output in that directory instead. With this different, it won't affect the output of your current build and you can always clear this variable to go back. Then you can use this for comparison. Alternatively you can just wipe out your output directory and build it over. You may also be able to dig into your output directory and delete the compiled files for the sources you have modified and then it should definitely notice and rebuild those.
EDIT: Also note that there are build instructions on the CyanogenMod wiki: http://wiki.cyanogenmod.org/w/Build_for_zeus
On the repo init line you can also say '-b jellybean' instead of ics and it will build CM10 (which is pretty good too but not fully stable, it's CM10.1 that is more unstable)
I also noticed that in the 'stable' release of CM9 for zeus the proximity sensor does not work, but there are patches for it in the repo and I've built from source with CM10 and it works fine.
~Troop
Click to expand...
Click to collapse
Never even thought about changing the location it is output to or anything like that. Kinda feel dumb not trying that but I will soon. Also I've looked at CyanogenMod's wiki already. And is CM 10 working on zeusc? I thought it was still only zeus but I haven't checked in a while.

bandoncontortion said:
Never even thought about changing the location it is output to or anything like that. Kinda feel dumb not trying that but I will soon. Also I've looked at CyanogenMod's wiki already. And is CM 10 working on zeusc? I thought it was still only zeus but I haven't checked in a while.
Click to expand...
Click to collapse
Cj360 made a zeusc version and uploaded it to fxp cm10 page. I've tested it and it works great
Sent from my Xperia Play (r800x)

Also all I did to SystemUI was add one .java file. I didn't know zeusc had cm 10. I'll check it out.

bandoncontortion said:
Also all I did to SystemUI was add one .java file. I didn't know zeusc had cm 10. I'll check it out.
Click to expand...
Click to collapse
Make sure the timestamp of the file you added is newer than the time you built. Otherwise, make will not realize there is a new file. Seems like you must have modified some other source file though to make use of the new source file.
A simple way to update the timestamp of a file is the "touch" command. If you touch a file before your build, it should always rebuild that file unless you have more serious problems.
Also, I forgot about the zeusc not being as well supported... so hopefully all the fixes for CM10 on the zeusc are in the repositories.
I do like CM10 better than CM9... especially since I figure if we're going to ditch stock-based GB, there's even less reason to live in the past.
~Troop

Changing the timestamp didn't do anything. I'll try deleting the already compiled files and recompile everything over again tomorrow. Also CM10 is a lot better in my opinion too so I'll try it now so hopefully it'll work and fix the problems I'm having.

Trooper_Max said:
Make sure the timestamp of the file you added is newer than the time you built. Otherwise, make will not realize there is a new file. Seems like you must have modified some other source file though to make use of the new source file.
A simple way to update the timestamp of a file is the "touch" command. If you touch a file before your build, it should always rebuild that file unless you have more serious problems.
Also, I forgot about the zeusc not being as well supported... so hopefully all the fixes for CM10 on the zeusc are in the repositories.
I do like CM10 better than CM9... especially since I figure if we're going to ditch stock-based GB, there's even less reason to live in the past.
~Troop
Click to expand...
Click to collapse
CM10 works good on zeusc. Haven't found any bugs and I added the changes to it's SystemUI and it compiled it for me and works great. Thanks for the help!

[Q] RIL Development sgh-t999

Hi everyone,
recently I have built and flashed on my sgh-t999 (galaxy S3 US tmobile version) CM11 Nightly. For my pro0ject however I need to modify two libraries of the Radio Interface Layer (RIL), libril.so and libreference-ril.so. I tried to modify the ones in the forlder /hardware/ril/ and build everything again with no results. Any change that I made to those files (such as ril.cpp in the folder libril) would not affect the functionality of the phone.
Finally yesterday I understood that when I build those libraries for the target cm-d2tmo-eng, those files that I have modified are not considered at all! When the libraries are built indeed, the system automatically takes the libril.so and libreference.so present in the vendor folder!
The problem is that those libraries in the vendor folder and already compiled and I cannot modify them. The question is:
Is there any way that I compile those libraries from the source code that I have modified?
Thanks,
brok85

Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.

Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
Click to expand...
Click to collapse
Well, as fisrt I just wanted to insert some log to be able to follow the code execution from the logcat or do something similar.
Perseus71 said:
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
Click to expand...
Click to collapse
Sorry but I am kind of new on this things. I have already downloaded the source code from the device tree and made my modifications in the files ril.cpp contained in [path-to-android-source]/hardware/ril/libril/ril.cpp. What I did was commenting the whole code within the function RIL_onUnsolicitedResponse() and listenCallback() such that in theory, the phone is not able to display incoming calls for example. However after flashing the re-built android I am still able to receve calls. How can I "check in the changes if they boot ok on my device"?
Perseus71 said:
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
I tried to remove the libril.so in the vendor folder and compile again using
# . build/envsetup.sh
# lunch (and select d2tmo)
# mmm [path-to-android-source]/hardware/ril/libril".
The problem is that when I indicate the target after lunch, the compiler looks for the vendor libraries and stop the build. What I am doing wrong?

Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.

Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
Perseus71 said:
Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.
Click to expand...
Click to collapse
Actually this is what I get after deleting
libril.so in vendor/samsung/d2tmo/proprietary/lib/
and after executing mmm /hardware/ril/libril :
No private recovery resources for TARGET_DEVICE d2tmo
make: *** No rule to make target `vendor/samsung/d2tmo/proprietary/lib/libril.so', needed by `/home/brok85/Documents/android/system/out/target/product/d2tmo/system/lib/libril.so'. Stop.
make: Leaving directory `/home/brok85/Documents/android/system'

If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links

blackbeard said:
If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links
Click to expand...
Click to collapse
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?

brok85 said:
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?
Click to expand...
Click to collapse
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
And vendor-blobs.mk would be present in the vendor folder under your device folder

blackbeard said:
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
Click to expand...
Click to collapse
Well I have followed the guide in the following page
http://wiki.cyanogenmod.org/w/Build_for_d2tmo
The link from where I have obtained the repository is
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
and then
$ breakfast d2tmo
blackbeard said:
And vendor-blobs.mk would be present in the vendor folder under your device folder
Click to expand...
Click to collapse
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
thanks a lot for the help guys

brok85 said:
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
Click to expand...
Click to collapse
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.

Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all
I have compiled CM11 as it is and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
The procedure I have followed is the following one:
1) Delete the llibril.so and libreference-ril.so from the vendor library. These are the pre-compiled vendor libraries that I need to modify.
2) commented the lines from the vendor-blobs.mk that were including those two precompiled libraries.
3) go to android/system/ and run "mmm /hardware/ril/libril" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so respectively.
4) copied the new libraries just obtained in the vendor folder where the pre-compiled libraries were
5) re-include the lines commented in point 2).
6) run brunch d2tmo
7) flash the .zip obtained
Any mistake?

Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all. Yes I have built everything out of the box and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
I followed the following procedure to include my modified libraries:
1) Eliminate precompiled vendor libraries: libril.so and libreference-ril.so from the vendor folder
2) comment lines in the vendor-blobs.mk that included those two precompiled libraries
3) from /android/system/ executed command "mmm /hardware/ril/librail" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so
4) copied the new libraries in the vendor folder in the same places were the precompiled libraries were positioned
5) re-include the two lines that were commented in point 2)
6) build everything again with brunch d2tmo
7) flash the .zip obtained
Any mistake?

Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?

Perseus71 said:
Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?
Click to expand...
Click to collapse
It cannot even find the network operators. It says that it is impossible to connect and to try later...
mine is the Tmobile version of S3. May this influence?

That would depend on the changes you made. But otherwise not really. The underlying Device tree is unified for all US S3 devices.

[Q] How to edit roomservice.xml?

I'm studying how to build a rom.
I already downloaded cm12 source.
Then I have to edit the roomservice.xml but I don't know what to write there.
I'm following this guide http://forum.xda-developers.com/showthread.php?t=2292018

xwsa568 said:
I'm studying how to build a rom.
I already downloaded cm12 source.
Then I have to edit the roomservice.xml but I don't know what to write there.
I'm following this guide http://forum.xda-developers.com/showthread.php?t=2292018
Click to expand...
Click to collapse
Roomservice overrides default manifest. if you want just build cyanogenmod there's no need to edit it. If you want replace one package with another you should first remove project.
http://dev.mordesku.pl/experimental/geehrc-roomservice.xml here is my roomservice used to build madness mod.
After create or modify any local manifest you should sync repo with "repo sync" command.

Thank you for answer

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.

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)