Database Info

[HOW-TO] Compiling System Apps (Contacts, Mms, Browser, etc.)

Hi all, before I begin, this is NOT meant to be a complete guide, but rather, just help to point in the right direction for those who want to compile/mod some of the system apps, but are a little lost. I was like this myself, and searched all over the place before putting bits and pieces together. Thanks goes out to xenio2000 and cytown for some of their advice.
Introduction:
To compile system apps such as Mms.apk, Contacts.apk, etc. you need the entire Android source. Also, you have to be running either Linux or OS X (with case-sensitive file system). Personally I dual boot Ubuntu 9.10 for it, so this instructions will be based on Ubuntu 9.10.
Step 1: Get Android Sources
To get the Android sources, follow the Linux instructions here: http://source.android.com/download
Remember you have to specify "-b donut" at the end of your repo command if you want to get the Donut base. Otherwise you will get master which is a mix of Eclair already .
Step 2: Get Java 5
If you are running Ubuntu 9.10, you will need to install Java 5 as you cannot compile AOSP on Java 6. I followed the instructions here: http://androidenea.blogspot.com/2009/12/ubuntu-910-java-5-and-android-open.html, and used Method 1. However, I downloaded Java 5 update 22 here: http://java.sun.com/javase/downloads/5u22/jdk (the one linked in the post is update 21).
The reason I use method 1 over method 2 is that this way, I only export the path when I want to compile (and it's only within the environment), while my browsers like Firefox, etc. are still running the latest Java 6.
Step 3: gcc
Lastly, I remember having some issues compiling due to gcc. I followed the guide here: http://www.mobileadvice.com.au/2009/11/how-to-compile-android-on-ubuntu-9-10/
Step 4: Compiling
Once all is done, you can "cd" to the root directory of your Android source, and type "make Contacts" or "make Mms". The first compilation will be a little long. I know of some people who do "make", that is they compile the entire source the first time, before using "mmm Phone". I don't recommend that because doing a "make" without any parameters will result in compilation of many apps you don't need, or want, and it's very slow.
Also, to "replace" the AOSP Contacts with let's say my Contacts, just "cd" to your root directory of Android, and type "git clone git://github.com/Wysie/android_packages_apps_Contacts.git". You can then play with my code but can't push back (need to know more git stuff for that). I suggest you fork the repos you are interested in, so you can push and make direct changes. Sorry I can't advice much on that, as I use git as though it's svn :X. I'm a git noob.
Hope it helps . As I said earlier, this is just to give you guys a rough idea of what's needed. In fact, I copied and paste my reply to someone else into here.

This will prove to be helpful, im sure. right now i dont have my Android environment setup, i had some problems upgrading to Karmic, and so i wiped my linux partition and started over with a fresh install. So far ive been too lazy to set it all up again, but already you've answered some questions i had, thanks!
-BMFC

Just a little suggestion:
If you use Ubuntu just to work on Android Source and nothing else, install Ubuntu 9.04 you will have less headache on compile and you can skip step 2 and 3 on Wysie guide.
Xenio

Xenio: you mean 8.04?

Ubuntu 8.04 is what Google suggest, I am using 9.04 and it is ok
With the 9.10 I have got a lot of problem with compile and java5/6
Probably with your tips is ok Ubuntu 9.10 but I use w7 for every day works
And I use Linux only for android source.
Xenio

hi wysie.
there appears to be no issues compiling AOSP with JDK 1.6. I only use this revision to compile.

Sorry for the really late reply, till today I still get "JDK 1.5 required" when trying to compile .

Hello!
I tried to compile Mms from rgv151 - nothing changed, just for fun = I received 'Error 41'.
if i try to compile stock mms from source it will work.
[email protected]:~/mydroid$ make Mms
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=1.6
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=Donut
============================================
build/core/copy_headers.mk:15: uwaga: polecenia zakrywające dla obiektu `out/target/product/generic/obj/include/libpv/getactualaacconfig.h'
build/core/copy_headers.mk:15: uwaga: ignoruję stare polecenia dla obiektu `out/target/product/generic/obj/include/libpv/getactualaacconfig.h'
Install: out/host/linux-x86/bin/aapt
Copying out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes-full-debug.jar
Install: out/host/linux-x86/framework/dx.jar
Install: out/host/linux-x86/bin/dx
target Prebuilt: libgoogleclient (out/target/common/obj/JAVA_LIBRARIES/libgoogleclient_intermediates/javalib.jar)
Copying out/target/common/obj/JAVA_LIBRARIES/ext_intermediates/classes-full-debug.jar
Install: out/host/linux-x86/bin/aidl
Copying out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/classes-full-debug.jar
target Java: Mms (out/target/common/obj/APPS/Mms_intermediates/classes)
android_packages_apps_Mms/src/com/android/mms/activity/VCardManager.java:304: incompatible types
found : java.lang.String
required: java.util.List<java.lang.String>
contactStruct.notes = contactC.getString(
^
android_packages_apps_Mms/src/com/android/mms/activity/VCardManager.java:358: addContactmethod(int,int,java.lang.String,java.lang.String,boolean) in android.syncml.pim.vcard.ContactStruct cannot be applied to (java.lang.String,java.lang.String,java.lang.String,java.lang.String)
contactStruct.addContactmethod(kind, data, type, label);
^
android_packages_apps_Mms/src/com/android/mms/transaction/SmsReceiverService.java:240: incompatible types
found : android.telephony.SmsMessage[]
required: android.telephony.gsm.SmsMessage[]
SmsMessage[] msgs = Intents.getMessagesFromIntent(intent);
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
3 errors
make: *** [out/target/common/obj/APPS/Mms_intermediates/classes-full-debug.jar] Błąd 41
Click to expand...
Click to collapse
Sorry for my English.
Greets, Laszlo.

[Q] Building AOSP ROM, yet want it to build to 'user' instead of 'userdebug'

Hi, i'm building my own Nexus 5 ROM from AOSP following this guide: http://nosemaj.org/howto-build-android-kitkat-nexus-5 Which has worked fine, except I want to get it to build to the 'User' buildtype rather than 'userdebug'. I changed "userdebug" to "user" within the 'device/lge/hammerhead/vendorsetup.sh' file in the hope that this would do it, but it appears to have built me an 'eng' build. Is there anything else I need to do, aside from changing the line in the vendorsetup.sh file.
Can anyone help?
Edit: Just to clarify, this is what it prints out when building, so it seems like it's building the 'user' type:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
TARGET_PRODUCT=aosp_hammerhead
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.12.5-1-ARCH-x86_64-with-glibc2.2.5
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=out
Click to expand...
Click to collapse
yet my final filename is: aosp_hammerhead-img-eng.[username].zip.

Just type "lunch" and pick using numbers the build you want.

rootSU said:
Just type "lunch" and pick using numbers the build you want.
Click to expand...
Click to collapse
Yeah but the hammerhead build, by default is a userdebug one, in the device/lge/hammerhead/vendorsetup.sh file, now I don't want to build the 'userdebug' variant, just the 'user' one, which isn't listed in Lunch. How do I build that one? Is it as simple as changing the line in the vendorsetup file to read "user" rather than "userdebug" and running . build/envsetup.sh then lunch, before I build it? Because (if you read what i'd posted in the OP) although it says it's building a "user" build, the suffix on the finished zip is "eng".

rootSU said:
Just type "lunch" and pick using numbers the build you want.
Click to expand...
Click to collapse
$ lunch
.. make your selection
$ choosevarient
... make your selection
Sent from my SHV-E300K using XDA Premium 4 mobile app
---------- Post added at 11:24 PM ---------- Previous post was at 11:22 PM ----------
bergqvistjl said:
device/lge/hammerhead/vendorsetup.sh
Click to expand...
Click to collapse
or edit to -user
Sent from my SHV-E300K using XDA Premium 4 mobile app

bergqvistjl said:
Yeah but the hammerhead build, by default is a userdebug one.
Click to expand...
Click to collapse
Hmm odd then. I dont understand. Historically when you type lunch, it should give you a numbered list of all devices, and each build option for each device and you just type the one you want. It shouldn't default to anything if you type just "lunch"

rootSU said:
Hmm odd then. I dont understand. Historically when you type lunch, it should give you a numbered list of all devices, and each build option for each device and you just type the one you want. It shouldn't default to anything if you type just "lunch"
Click to expand...
Click to collapse
No!
I want to get it to build to the 'User' buildtype rather than 'userdebug'.
I changed "userdebug" to "user" within the 'device/lge/hammerhead/vendorsetup.sh' file, and then selected it in Lunch, in the hope that this would do it, but it appears to have actually built me an 'eng' build, as the filename of the final zip file is:
aosp_hammerhead-img-eng.[username].zip. Is this normal?
The info that displays when the build begins is this, so it looks like it's picking up that it should build a user version:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
TARGET_PRODUCT=aosp_hammerhead
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.12.5-1-ARCH-x86_64-with-glibc2.2.5
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=out
Click to expand...
Click to collapse

koe1974 said:
or edit to -user
Click to expand...
Click to collapse
That's what i've done, but the filename of the built zip file indicates that it's an eng build: aosp_hammerhead-img-eng.[username].zip Which is right?

I use
$ lunch aosp_hammerhead-user
Then
$ make -j8 otapackage
to create flashable zip.
Changing the ending of aosp_hammerhead-user to "-userdebug" or to "-eng" gives the same filename as you mentoined in the op. However if you used "-user" there is no "su" file in the /system/xbin while with "-userdebug" you have and usb debugging is enabled by default. If you use "-eng" you get a red frame in applications if it hangs up, and you get an extra app called dev tools, besides these -eng is the same as -userdebug.
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
I use
$ lunch aosp_hammerhead-user
Then
$ make -j8 otapackage
to create flashable zip.
Changing the ending of aosp_hammerhead-user to "-userdebug" or to "-eng" gives the same filename as you mentoined in the op. However if you used "-user" there is no "su" file in the /system/xbin while with "-userdebug" you have and usb debugging is enabled by default. If you use "-eng" you get a red frame in applications if it hangs up, and you get an extra app called dev tools, besides these -eng is the same as -userdebug.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Thanks, it turns out it *is* building a user build after all, you're right in that the output filename doesn't change. Cheers

bergqvistjl said:
No!
Click to expand...
Click to collapse
No what???????

[Completed] Ninja_wrapper error

building my very first nougat ROM for the GT-I9505 (Jfltexx) but I keep getting this error when use the brunch command.
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/lochlan/LAOS/out/target/product/jfltexx/obj/lib/libtime_genoff.so.toc', needed by '/home/lochlan/LAOS/out/target/product/jfltexx/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/lochlan/LAOS'
I've done some research and still haven't come to a conclusion on what the hell it means...
Any and all help would be nice!

skyskidder said:
building my very first nougat ROM for the GT-I9505 (Jfltexx) but I keep getting this error when use the brunch command.
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/lochlan/LAOS/out/target/product/jfltexx/obj/lib/libtime_genoff.so.toc', needed by '/home/lochlan/LAOS/out/target/product/jfltexx/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/lochlan/LAOS'
I've done some research and still haven't come to a conclusion on what the hell it means...
Any and all help would be nice!
Click to expand...
Click to collapse
Did you get the vendor repo for your device? Please pay attention on this. I think your vendor repo is outdated and file libtime_genoff.so is missing.

blinoff82 said:
Did you get the vendor repo for your device? Please pay attention on this. I think your vendor repo is outdated and file libtime_genoff.so is missing.
Click to expand...
Click to collapse
Hello, this is what I'm using for my vendor repo
https://github.com/JDCTeam/android_vendor_cm
And you are correct about libtime_genoff.so is missing. I checked all my repos for that file and have gotten no results. Any idea on what I should do?
P.S. Thanks for your help thus far! It means a lot!

skyskidder said:
Hello, this is what I'm using for my vendor repo
https://github.com/JDCTeam/android_vendor_cm
And you are correct about libtime_genoff.so is missing. I checked all my repos for that file and have gotten no results. Any idea on what I should do?
P.S. Thanks for your help thus far! It means a lot!
Click to expand...
Click to collapse
You should use another vendor blobs like this https://github.com/DonkeyCoyote/proprietary_vendor_samsung/tree/android-7.1/jflte.
Add in local_manifest (roomservice.xml):
<project name="DonkeyCoyote/proprietary_vendor_samsung" path="vendor/samsung" revision="android-7.1" remote="github" />
Then: "repo sync -j1 --force-sync" and build again.
I never encountered with Samsung devices, I hope I did not make a mistake with path...

blinoff82 said:
You should use another vendor blobs like this https://github.com/DonkeyCoyote/proprietary_vendor_samsung/tree/android-7.1/jflte.
Add in local_manifest (roomservice.xml):
<project name="DonkeyCoyote/proprietary_vendor_samsung" path="vendor/samsung" revision="android-7.1" remote="github" />
Then: "repo sync -j1 --force-sync" and build again.
I never encountered with Samsung devices, I hope I did not make a mistake with path...
Click to expand...
Click to collapse
Hey thanks for the idea on using this new repo for the device blobs and providing the link! But i have a few questions.
#1. There are severely many less files in this new repo. Why is that?
#2 This effect anything with my rom? if so like what?
You dont need to give me a full out explanation a brief one will do if you can, if you cant dont sweat it!
I will also try this new repo when i get home and I'll update you on how it goes.
Thank you so very much!
-Sky

skyskidder said:
#1. There are severely many less files in this new repo. Why is that?
#2 This effect anything with my rom? if so like what?
Click to expand...
Click to collapse
1. Because this repo ONLY for jflte.
2. No effect, this is just blobs needed for your device and for compilation.

blinoff82 said:
1. Because this repo ONLY for jflte.
2. No effect, this is just blobs needed for your device and for compilation.
Click to expand...
Click to collapse
Welp. I tried what you told me to do and Ive gotten farther but i ran into another error.
FAILED: /bin/bash -c "(make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" VARIANT_DEFCONFIG= SELINUX_DEFCONFIG= cyanogenmod_jf_defconfig ) && (if [ ! -z "" ]; then echo "Overriding kernel config with ''"; echo >> /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/.config; make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" oldconfig; fi ) && (make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" savedefconfig ) && (if [ ! -z "" ]; then echo "Using additional config ''"; kernel/samsung/jf/scripts/kconfig/merge_config.sh -m -O /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/.config kernel/samsung/jf/arch/arm/configs/; make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" KCONFIG_ALLCONFIG=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/.config alldefconfig; fi )"
make: Entering directory '/home/lochlan/LAOS/kernel/samsung/jf'
GEN /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/Makefile
HOSTCC scripts/basic/fixdep
/home/lochlan/LAOS/kernel/samsung/jf/scripts/basic/fixdep.c:106:23: fatal error: sys/types.h: No such file or directory
compilation terminated.
scripts/Makefile.host:118: recipe for target 'scripts/basic/fixdep' failed
make[2]: *** [scripts/basic/fixdep] Error 1
/home/lochlan/LAOS/kernel/samsung/jf/Makefile:417: recipe for target 'scripts_basic' failed
make[1]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
make: Leaving directory '/home/lochlan/LAOS/kernel/samsung/jf'
[ 6% 2204/33925] target R.java/Manifest.java: framework-res (/home/lochlan/LAOS/out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp)
warning: string 'candidates_style' has no default translation.
warning: string 'gsm_alphabet_default_charset' has no default translation.
warning: string 'wfcSpnFormat' has no default translation.
nothing matches overlay file default_wallpaper.png, for flavor hdpi-v4
nothing matches overlay file default_wallpaper.png, for flavor xhdpi-v4
nothing matches overlay file default_wallpaper.png, for flavor xxhdpi-v4
nothing matches overlay file default_wallpaper.png, for flavor xxxhdpi-v4
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/lochlan/LAOS'
#### make failed to build some targets (08:00 (mm:ss)) ####
Click to expand...
Click to collapse
Any idea what this error is?

Sorry my friend you should think for yourself. That's all.
http://stackoverflow.com/questions/37771339/sys-types-h-no-such-file-or-directory

:QUICK UPDATE:
I don't think I'm ready to tackle a project of this scale yet. My frustration, lack of knowledge of compiling and knowledge of repo commands, java, and the damn terminal have caused as of now to post pone my attempts at making a ROM. With exams coming up I have take EVEN MORE time away from my attempts.
:SIDE NOTES:
I feel I have made some progress since the last post I have made with the help of @binoff82 of course. Slowly but surely I'm getting there. With the expense of many broken things in my room... Including a fractured wrist...
In a few days and or weeks time I will update the thread with another post either explaining my progress or if I'm just going to halt my attempts completely for quite a while.
-Sky
P.S. I should probably take anger management classes...

skyskidder said:
:QUICK UPDATE:
I don't think I'm ready to tackle a project of this scale yet. My frustration, lack of knowledge of compiling and knowledge of repo commands, java, and the damn terminal have caused as of now to post pone my attempts at making a ROM. With exams coming up I have take EVEN MORE time away from my attempts.
:SIDE NOTES:
I feel I have made some progress since the last post I have made with the help of @binoff82 of course. Slowly but surely I'm getting there. With the expense of many broken things in my room... Including a fractured wrist...
In a few days and or weeks time I will update the thread with another post either explaining my progress or if I'm just going to halt my attempts completely for quite a while.
-Sky
P.S. I should probably take anger management classes...
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you seen this excellent guide by jackeagle ?
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
that thread is probably your best bet for advice
Good Luck
Sawdoctor

sawdoctor said:
Greetings and welcome to assist. Have you seen this excellent guide by jackeagle ?
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
that thread is probably your best bet for advice
Good Luck
Sawdoctor
Click to expand...
Click to collapse
Hi, thanks for taking your time to help me. Sadly this is the original guide I have been following when attempting to build my ROM.

Can't Build otatools from Lineage OS Sources

Hi everybody I'm trying yo build a CWM recovery for my Phone using the sources of LineageOS 14.1.
I need build the otatools to use the makevendor.sh but i het this:
Code:
[email protected]:/home/los14.1# make -j4 otatools
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=
TARGET_PRODUCT=aosp_arm
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-59-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NMF26V
OUT_DIR=/home/los14.1/out
============================================
Running kati to generate build-aosp_arm.ninja...
No need to regenerate ninja file
Starting build with ninja
ninja: Entering directory `.'
ninja: error: unknown target 'otatools', did you mean 'obbtool'?
build/core/ninja.mk:151: fallo en las instrucciones para el objetivo 'ninja_wrapper'
make: *** [ninja_wrapper] Error 1
#### make failed to build some targets (01:53 (mm:ss)) ####
/home/los14.1/ is may repo directory
the jack-server appears to don't be installed. i try to install it but was installed in /root/. but the ¨make -j4 otatools" continue give me this error
OpenJDK 8
Ubuntu 16.04 LTS
I'm Sorry For my Very Bad English, Thanks

I'm having the same issue, but I'm trying to compile cyanogenmod 14. Anyone have any ideas?

General Custer said:
I'm having the same issue, but I'm trying to compile cyanogenmod 14. Anyone have any ideas?
Click to expand...
Click to collapse
Hi, you can try find the upackbootimg.sh in a website or un the repo files (i found this in system/core/i don't remember...)
Then copy and paste it in /bin/ folder
This is a temporatly solution, i finaly build my recovery, but don't boot ?

guillermo2309 said:
Hi, you can try find the upackbootimg.sh in a website or un the repo files (i found this in system/core/i don't remember...)
Then copy and paste it in /bin/ folder
This is a temporatly solution, i finaly build my recovery, but don't boot
Click to expand...
Click to collapse
Then this must not be my issue because ice already done that... I think mine might have more to do with it being a totally (as of yet) unsupported device

General Custer said:
Then this must not be my issue because ice already done that... I think mine might have more to do with it being a totally (as of yet) unsupported device
Click to expand...
Click to collapse
After copy the file you can run the build/tools/mkvendor.sh
You dont need run (make -j# otatools) this continue giving error

hi , i get the same error after i run the command(make -j4 otatools ), do you know ho
hi , i get the same error after i run the command(make -j4 otatools ), do you know how to fixed it now ? please help me .

Hi this is an old and probably dead thread, but I had the same problem and was not able to find the solution in the forums. That's why I still answer this old post.
For everyone finding this by googling: Be sure that you ran
Code:
source ./build/envsetup.sh
before
Code:
make otatools
Might be simple but can take some tries to figure out.
Sorry for reactivating this zombie thread, but as I said, there is nothing about that in the forums.
javaeryang said:
hi , i get the same error after i run the command(make -j4 otatools ), do you know how to fixed it now ? please help me .
Click to expand...
Click to collapse

Building Android for MSM (Release branch for MSM8996) fails setting up SDCLANG

Hi,
I am trying to build Android for MSM release (8.0.0, MSM8996) from source but failing.
It seems that inside /home/vagrant/android-msm/build/soong/cc/config/global.go file,
when it calls config.setSdclangVars() related file paths retrieved from environment variables such as $SDCLANG_AE_CONFIG is null(not set) causing build error.
SDCLANG is Snap Dragon Clang compiler I believe, and related documents don't have any info regarding $SDCLANG_AE_CONFIG and other environment variables that are not set.
I tried changing BoardConfig.mk to not use SDCLANG, but it still fails accessing SDCLANG related variables.
Can somebody help me fix this? Thanks
Code:
FAILED: out/soong/.bootstrap/soong-cc-config/test/test.passed
out/soong/.bootstrap/bin/gotestrunner -p ./build/soong/cc/config -f out/soong/.bootstrap/soong-cc-config/test/test.passed -- \ out/soong/.bootstrap/soong-cc-config/test/test -test.short
panic: read /home/vagrant/android-msm: is a directory
goroutine 1 [running]:
android/soong/cc/config.setSdclangVars()
/home/vagrant/android-msm/build/soong/cc/config/global.go:197 +0x20d4
android/soong/cc/config.init.2()
/home/vagrant/android-msm/build/soong/cc/config/global.go:169 +0xcc9
android/soong/cc/config.init()
/home/vagrant/android-msm/build/soong/cc/config/tidy_test.go:42 +0x3969
main.init()
/home/vagrant/android-msm/out/soong/.bootstrap/soong-cc-
config/test/test.go:34 +0x4e
ninja: build stopped: subcommand failed.
15:22:17 soong bootstrap failed with: exit status 1
make: *** [run_soong_ui] Error 1
make: Leaving directory `/home/vagrant/android-msm'

binerdd said:
Hi,
I am trying to build Android for MSM release (8.0.0, MSM8996) from source but failing.
Click to expand...
Click to collapse
For what device exactly?

Nonta72 said:
For what device exactly?
Click to expand...
Click to collapse
Well I have a Galaxy Note8, but does that matter in this case?
I have tried with TARGET_PRODUCT as "aosp_arm" and " msm8996-userdebug" but both fails the same.
Also to be specific, I do not want to build the whole kernel image, just some personal project that references some kernel data and send IOCTL commands to devices etc.
Thanks in advance.

I am having the same problem.
See my output for LA.UM.6.5.r1
I would think that a fresh clean sync of the sources would allow to build one of the supplied device trees but no such luck.
Almost appears to depend on some Qualcomm SDCLANG setup or something.
Not sure if their manifest is missing something or if my build environment is missing something.
I can build Nougat and Oreo for LineageOS roms so I'm pretty sure my build environment is correct.

android 8.0 for msm8996 build issue using sdclang compiler
hi,
i am trying to build android oreo for the msm8996 chip , and here's my log :
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=8.0.0
TARGET_PRODUCT=msm8996
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=kryo
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a9
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.10.0-37-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=OPR1.170623.026
OUT_DIR=out
============================================
ninja: no work to do.
[1/5] test android/soong/cc/config
FAILED: out/soong/.bootstrap/soong-cc-config/test/test.passed
out/soong/.bootstrap/bin/gotestrunner -p ./build/soong/cc/config -f out/soong/.bootstrap/soong-cc-config/test/test.passed -- out/soong/.bootstrap/soong-cc-config/test/test -test.short
panic: read /home/dolby/JK/android8msm: is a directory
goroutine 1 [running]:
android/soong/cc/config.setSdclangVars()
/home/dolby/JK/android8msm/build/soong/cc/config/global.go:197 +0x20d4
android/soong/cc/config.init.2()
/home/dolby/JK/android8msm/build/soong/cc/config/global.go:169 +0xcc9
android/soong/cc/config.init()
/home/dolby/JK/android8msm/build/soong/cc/config/tidy_test.go:42 +0x3969
main.init()
/home/dolby/JK/android8msm/out/soong/.bootstrap/soong-cc-config/test/test.go:34 +0x4e
ninja: build stopped: subcommand failed.
10:03:19 soong bootstrap failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
regards,
Jayakrishnan

Did you sovle this problem? I had same this error right now.
Best Regards,
Hao

this seems relevant:
https://developer.qualcomm.com/forum/qdn-forums/software/snapdragon-llvm-compiler-android/33437

Hi, bro. I met the sme issue while compiling msm-aosp. Have you solved it? Could you please give some advice?

jamuir said:
this seems relevant:
https://developer.qualcomm.com/forum/qdn-forums/software/snapdragon-llvm-compiler-android/33437
Click to expand...
Click to collapse
I tried following this. But issues still exists.

九面相柳 said:
I tried following this. But issues still exists.
Click to expand...
Click to collapse
I gave up trying to build in a CAF tree. I wasn't able to find any useful documentation on the build process. It seems the project is mainly targeted to partners who have access to proprietary board-support-packages.
The last thing I figured out was that you need to build using the snap-dragon clang compiler. There are some config files required to do that.
I created a json file at the root of my tree and pointed the soong build system to it using environmental variables:
Code:
export SDCLANG_CONFIG=sdclang.json
export SDCLANG_AE_CONFIG=sdclang.json
I based my json file on the one here:
https://github.com/Dragons-CAF/android_device_dragons_SDCLang/blob/O.1/sdclang.json

jamuir said:
I gave up trying to build in a CAF tree. I wasn't able to find any useful documentation on the build process. It seems the project is mainly targeted to partners who have access to proprietary board-support-packages.
The last thing I figured out was that you need to build using the snap-dragon clang compiler. There are some config files required to do that.
I created a json file at the root of my tree and pointed the soong build system to it using environmental variables:
Code:
export SDCLANG_CONFIG=sdclang.json
export SDCLANG_AE_CONFIG=sdclang.json
I based my json file on the one here:
https://github.com/Dragons-CAF/android_device_dragons_SDCLang/blob/O.1/sdclang.json
Click to expand...
Click to collapse
I give it up, too. Thank you all the same.