yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
If I wanted to remove something that is being called by Java. Example com.replica.replicaisland where would I find it. I know current.txt has a list of the API but where would the original call be from?
[Android Q&A, Help & Troubleshooting] cdesai:
In your source tree run

find . | xargs grep com.replica.replicaisland

That'll list all references to it.
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
Cool then I just remove all those references after?
[Android Q&A, Help & Troubleshooting] RaymanFX:
@ dreamboxuser ...

to resolve the error with replica island, just go to /<top_of_source_dir>/cts/tests/tests/openglperf/

you should now see a folder structure like this :

-assets

-res

-src

-Android.mk

-AndroidManifest.xml

Just rename the "Android.mk" to something like "Android.mk.disabled"

now, you just have to "make clean" and then build again, this time it should pass all the errors.
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
Awesomeness thank you so much. It actually has been driving me crazy for the last few days. You rule. Thanks so much.:D:D:D:D:D:D:D

Edit: success error bypassed
[Android Q&A, Help & Troubleshooting] RaymanFX:
Yeah, I felt the same way :D but luckily I was able to bypass it.

Glad you are proceeding, mate !

I am currently compiling TeamGummy and got my first builds up and running :)

Adding more features and TransformerParts app ..
[Android Q&A, Help & Troubleshooting] resac:
Thanks for tut..
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
Ya I just flashed it worked perfectly thanks a ton. Can't wait for the transformer parts. Muhahaha so much I wanna do like a bootanimation for big screens
[Android Q&A, Help & Troubleshooting] lithid-cm:
no need for find in this instance, useless overhead. grep has a recursive option.

grep -rn "com.replica.replicaisland" *

would search all files recursively and print out the line numbers of the instance.
[Android Q&A, Help & Troubleshooting] RaymanFX:
What about Nyancat in full 1280*800 resolution for our transformers ? :D

I could add the sound ...

Nothing could beat this anim for sure ... muhahaha ... BTW, Transformer Parts are almost done, currently fixing up ntfs stuff.

@all sorry for a little off topic talk :D now back to work.
[Android Q&A, Help & Troubleshooting] Deltatiger:
Building for wildfire (buzz)

Hey guys. I am building cm9 for htc wildfire aka buzz. But i get a few errors. Similar errors were fixed by changing the thing to PRODUCT_COPY_FILES in the blob files but it was already changed.

These are the errors i get.

Which would you like? [full-eng] 4
Looking for dependencies
Dependencies file not found, bailing out.

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.4
TARGET_PRODUCT=cm_buzz
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv6j
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IMM76I
============================================

deltaubuntu@deltaubuntu:~/WORKING_DIRECTORY$ make -j1
============================================

after this it goes on with few warnings and stuff and gives me

make: *** No rule to make target `vendor/htc/buzz/proprietary/libcamera.so', needed by `out/target/product/buzz/obj/lib/libcamera.so'. Stop.

Im building on ubuntu 12.04 LTS 64bit.
[Android Q&A, Help & Troubleshooting] dastin1015:
You're missing proprietary vendor files. Did you do the extract-files.sh step?

私のEVO 3Dから送信される。
[Android Q&A, Help & Troubleshooting] Deltatiger:
Yes. After setting up adb I downloaded the device specific files from ErwinP (from Here). Then i connected and then extract-files after which it did some stuff and also placed a few files in the vendor/htc/buzz.

According to This guide i forgot to place the vendor files in the vendor/htc/buzz before doing the extract-files.sh step. Does that cause the problem?
[Android Q&A, Help & Troubleshooting] dastin1015:
You're still missing files in the vendor/htc/buzz/proprietary directory. Place the missing file that is needed from the error in the directory.
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
Does the build process begin by Compiling the kernel then move on to the system then to the bootloader?
[Android Q&A, Help & Troubleshooting] dastin1015:
Kernel is precompiled and a part of the vendor files usually. Next is the boot.img and recovery.img and then the system.

私のEVO 3Dから送信される。
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
I was wondering because I am working on getting Gummy to compile for my galaxy y.

So when the apps like su start compiling would that be a good indication that the kernel (yes i am compiling the kernel) and recovery have successfully compiled?
[Android Q&A, Help & Troubleshooting] cdesai:
Not true for cm9, as we now use inline kernel building

For that just navigate to out/target/product/totoro and check if you have a boot.img
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
Still compiling but no boot.img yet. (Nervous) only a dual core and running at -j1 so its sooooo slowwww. I usually compile for my tf101 on j4 but the totoro build doesn't like it at all.

Edit: just failed. Compiler error grrrrr.
[Android Q&A, Help & Troubleshooting] championswimmer:
got a more intelligent method by cm9 team now..

once repo sync is done, go to ./vendor/cm

edit the file vendorsetup.sh

add your device line, for example for my device 'anzu'

add_lunch_combo cm_anzu-userdebug

add_lunch_combo full_anzu-userdebug

add_lunch_combo cm_anzu-eng

add_lunch_combo full_anzu-eng

now go back to source root,

run

. build/envsetup.sh

lunch

your device should be in list

chose it, then automatically it's source (along with any dependent source, like common, kernel, vendor, proprietary etc) will get downloaded

then

make otapackage
[Android Q&A, Help & Troubleshooting] flowish:
thanks for your tutorial, but im getting this error :

/bin/bash: command not found
make: *** [out/target/product/tass/system/build.prop] Error 127
make: *** Deleting file `out/target/product/tass/system/build.prop'
make: *** Waiting for unfinished jobs....

any idea ?? :confused:
[Android Q&A, Help & Troubleshooting] molo_king:
great and thanks!
[Android Q&A, Help & Troubleshooting] championswimmer:
anyone got to figure out how to solve this type of error

UNEXPECTED TOP-LEVEL ERROR:

java.lang.OutOfMemoryError: GC overhead limit exceeded

at java.util.HashMap.<init>(HashMap.java:187)

blah

blah blah...

upgrading to jdk6-u31 did NOT help

i had the error with u20, u26 and after upgrade with u31 too...

so any ideas guys ???
[Android Q&A, Help & Troubleshooting] cdesai:
type "which bash" and post the output

It means your pc does not have enough RAM available, and it ran out of free memory
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
As for the ram I found this on another tutorial here http://rootzwiki.com/index.php?/topic/18318-[TUTORIAL]-How-to-Compile-Gummy-for-Non-Moto-Devices#entry482777

Again not my work but it worked for me. Probably have to change gummy to whatever you are using.
[Android Q&A, Help & Troubleshooting] championswimmer:
but it does flow over to swap right? if ram is full??

i have 2.5gb ram and a 5gb swap disk... enough???
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
I have 3 gigs of ram and a 10 gig swap but I still got that error until I changed that and it worked.
[Android Q&A, Help & Troubleshooting] lanternslight456:
I've got 2g or ram and 5 of swap and have been able to compile successfully until I repo synced yesterday. Now it gets that memory error at the end as described. I'd successfully compiled just a few days ago though. I'll try the memory edit you mentioned and report back how it goes for me, cm9.

ok, i tried both 1024 as mentioned, and 512...

running: mkbootimg --kernel /tmp/targetfiles-6OULAx/BOOT/kernel --cmdline console=ttyHSL0,115200,n8 --base 0x80400000 --ramdiskaddr 0x81800000 --ramdisk /tmp/tmpeRBouv --output /tmp/tmp7LjFIu
running: openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
running: java -Xmx512 -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpUajvDH out/target/product/ville/cm_ville-ota-eng.jhutson456.zip
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:161)
at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)
at java.util.zip.ZipOutputStream.write(ZipOutputStream.java:272)
at com.android.signapk.SignApk.copyFiles(SignApk.java:422)
at com.android.signapk.SignApk.main(SignApk.java:490)

ERROR: signapk.jar failed: return code 1

make: *** [out/target/product/ville/cm_ville-ota-eng.jhutson456.zip] Error 1

is it possible to create that memory call as a variable? This way it could just grab whatever memory is available.
[Android Q&A, Help & Troubleshooting] Dreamboxuser:
Just a thought but maybe you need to change it to 0512 . Im no expert but it may be looking for a 4 digit number.
[Android Q&A, Help & Troubleshooting] skyhigh2004:
I'm having no luck either man. Here's a thread I started about the out of memory problem that I am having , http://xdaforums.com/showthread.php?t=1682722. I have tried everything I could find on the internet to fix it but every time I try and build cm it just fails as out of memory towards the end. The funny thing is I can build AOSP just fine and fast. I'm at a complete loss.

Sent from my GT-N7000 or Galaxy Nexus
[Android Q&A, Help & Troubleshooting] lanternslight456:
It's so frustrating because I was able to compile it just a few days ago. Then I did a repo sync, it updated some things, and I'm hosed...

Sent from AndroidInsomnia H.Q.
[Android Q&A, Help & Troubleshooting] lemonoid:
It works for any build I've had to do it for gummy, evervolv, and a couple of others and if it doesn't work try 512 instead of 1024. It should be line 374 in common.py
[Android Q&A, Help & Troubleshooting] lemonoid:
I don't think so. It is just looking for specific amounts of RAM and they will always be 256, 512, 1024 etc I've had 512 and it worked fine
[Android Q&A, Help & Troubleshooting] lanternslight456:
I've tried 1024, 512, and 256 with no luck. I have 2 gigs ram and 2 gigs swap. I even made sure that the terminal was the only thing open after a reboot... Still. The same memory fail.

Sent from AndroidInsomnia H.Q.
[Android Q&A, Help & Troubleshooting] lithid-cm:
Java is iffy. It also don't care about your swap. It binds to the physical ram when its allocated. Lowering this below 1Gig isn't suggested. ICS needs at least a gig of VMheap for the emulator. 512 was cutting it close in GB. If you want to compile, add more ram. Its that simple. You might be able to get away with it by doing either one of two things.

1. Installing a slimmer desktop. (XFCE, LXDE)

2. installing another distro as a dual boot with no gui.

Have fun.
[Android Q&A, Help & Troubleshooting] skyhigh2004:
I do get the "if you wanna compile get more ram" argument but why can I build aosp just fine on my ram but not cm? It makes no sense, if I need more ram I shouldn't be able to compile cm or aosp they are both ICS.

Sent from my GT-N7000 or Galaxy Nexus
[Android Q&A, Help & Troubleshooting] lithid-cm:
In the same that CM is not AOSP. CM is based off of AOSP. Is it possible that something was added to the build that requires the ram? Sure. I haven't looked through the most recent commits, buts CM is not AOSP, and I don't think it should be looked at the same.

Edit: Have you tried building with AOSP master? It is possible you might find the same issue since cm pulls in commits from AOSP as well.
[Android Q&A, Help & Troubleshooting] skyhigh2004:
No I can build AOSP master just fine. I wasnt trying to argue with you man was just trying to enlighten myself as to why cm is being a pain in my ass. I deleted my entire repo for cm and re synced today while I was at work from scratch so hopefully tonight I might have more luck. Hopefully it isnt something that cm added :(, I really wanna build it on my 6GB machine for a few weeks before I have to cash to max out its ram.
[Android Q&A, Help & Troubleshooting] lithid-cm:
You have a 6GB machine and you are having issues?
[Android Q&A, Help & Troubleshooting] skyhigh2004:
Yeah thats the part I dont understand. I can build aosp just fine and it actually builds fairly quickly. I started a thread for the exact build error I am getting but no dice there either. I really am at a loss thats why I thought and "hoped" that a fresh install and sync of the repo might help.

EDIT: heres the link to my thread. http://xdaforums.com/showthread.php?t=1682722
[Android Q&A, Help & Troubleshooting] rohan32:
I'm able to build AOKP in 30 minutes on subsequent builds (3 hours for fresh ones after make clean) and my system is a Core 2 Duo with 2gb of RAM.

And this is running 32bit Ubuntu.

So trust me, you really can build on anything if you have patience.

===============================================================================================

Also, now I am looking into compiling an AOSP ROM for the HTC One X AT&T. There currently are no device trees that I know of, so how do I make one?

Thanks.
[Android Q&A, Help & Troubleshooting] justlovejoy:
im sick please help, iz also mi birthday :(

I no want build with iassetredirectionmanager.java

u guys w/ java errors using wrong java versions

---------- Post added at 06:59 AM ---------- Previous post was at 06:55 AM ----------

WRONG JAVA VERSIONS GUYS

U NEED??? tell me command to check version and ill copy paste mine. i had dat problem b4!
[Android Q&A, Help & Troubleshooting] rohan32:
I'm getting this:

system@ubuntu:~/aosp_evita$ lunch

You're building on Linux

Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. cm_evita-userdebug
5. full_maguro-userdebug
6. full_tuna-userdebug
7. full_panda-eng

Which would you like? [full-eng] 4
build/core/product_config.mk:205: *** No matches for product "cm_evita". Stop.

** Don't have a product spec for: 'cm_evita'
** Do you have the right repo manifest?

Same error as others. I've tried fixing it with some other things in this thread but nothing worked so far.

The device tree I'm building from is located here:

https://github.com/vmagro/android_device_htc_evita

Thanks!
[Android Q&A, Help & Troubleshooting] justlovejoy:
please re read the op post #1 its at the very bottom. change the name in the file. full_evita? to cm. inside file. not file name
[Android Q&A, Help & Troubleshooting] dastin1015:
Read the following note and adapt to your problem.

~NOTE~

If you are running into issues such as:

Which would you like? [full-eng] 5
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
Device shooter not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for shooter not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.

** Don't have a product spec for: 'full_shooter'
** Do you have the right repo manifest?

What you need to do is to edit your blob to match the PRODUCT_NAME to the file name. For example with mine I have full_shooter.mk therefore in this file I need to have PRODUCT_NAME to match it. Whatever error it is looking for you just need to change the PRODUCT_NAME line to match what the error shows.
[Android Q&A, Help & Troubleshooting] rohan32:
My product name is already cm_evita and its still giving that problem.
[Android Q&A, Help & Troubleshooting] elbermu:
Open AndroidProducts.mk, look at the:

PRODUCT_MAKEFILES := $(LOCAL_DIR)/[another.mk]

Check if another.mk file exist AND that file has:

PRODUCT_NAME := cm_evita
[Android Q&A, Help & Troubleshooting] lpasq:
Hi all. Looking to fire up AOSP build hobby after years away from source building Nexus One ROMs. Question...Anyone here building for a Galaxy Note? I am going to get a VM fired up on my iMac and set a 64bit Ubuntu build environment this weekend and wonder where you pull from github and if device files are easily pulled. I am lazily asking you all here before starting my own research beginning soon.
[Android Q&A, Help & Troubleshooting] elbermu:
I reviewed the cm_evita git and maybe you haven't synced with CM9...
[Android Q&A, Help & Troubleshooting] rohan32:
Okay thanks! I will try that when I get home!

I have synced with AOSP but not CM9 since the end goal of this port is to build an AOSP ROM not a CM9 one. I'm using the 4.0.4_r1.2 repo by the way.
[Android Q&A, Help & Troubleshooting] rohan32:
With that fixed now I am getting this error:

make: *** No rule to make target `otapackage'. Stop.

After I type the make -j2 otapackage that error comes out.

Please help me, I'm a newb :)
[Android Q&A, Help & Troubleshooting] paxChristos:
If you're making CM9, try make -j2 bacon
[Android Q&A, Help & Troubleshooting] b.huss2:
ok guys, with the op's instructions and just reading through the issues in this thread I've been able to get a lot of things worked out. I've got to the point where I can "make" and it runs for a while but eventually quits with errors. Anyone help me with this?

last few lines:

arm-linux-androideabi-g++: error trying to exec 'prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../libexec/gcc/arm-linux-androideabi/4.4.3/cc1plus': execv: Argument list too long

make: *** [out/target/product/shooter/obj/SHARED_LIBRARIES/libstdc++_intermediates/src/one_time_construction.o] Error 1

make: *** Waiting for unfinished jobs....

arm-linux-androideabi-g++: error trying to exec 'prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../libexec/gcc/arm-linux-androideabi/4.4.3/cc1plus': execv: Argument list too long

make: *** [out/target/product/shooter/obj/SHARED_LIBRARIES/libstdc++_intermediates/src/new.o] Error 1
[Android Q&A, Help & Troubleshooting] b.huss2:
Anyone still participating in this thread? i would love to get this figured out.
[Android Q&A, Help & Troubleshooting] djsubtronic:
After trying to rebulid from scratch, getting the device repos, I get this error on "lunch"

Which would you like? [full-eng] 7
build/core/config.mk:145: *** No config file found for TARGET_DEVICE device_ville. Stop.

** Don't have a product spec for: 'device_ville'
** Do you have the right repo manifest?

Any ideas?
[Android Q&A, Help & Troubleshooting] paxChristos:
Check your cm.mk file in your device tree, it's not matching the call in lunch
[Android Q&A, Help & Troubleshooting] djsubtronic:
I changed .../ville/cm.mk as so:

# Device naming
PRODUCT_DEVICE := ville
PRODUCT_NAME := device_ville
PRODUCT_BRAND := htc
PRODUCT_MODEL := HTC One S
PRODUCT_MANUFACTURER := HTC

But still get the same error...

EDIT: silly typing errors.... solved it now!

Thank you

---------- Post added at 05:15 AM ---------- Previous post was at 05:03 AM ----------

My errors just keep getting more and more colourful

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.1
TARGET_PRODUCT=device_ville
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-2.6.32-38-generic-x86_64-with-Ubuntu-10.04-lucid
HOST_BUILD_TYPE=release
BUILD_ID=JRO03C
OUT_DIR=out
============================================
frameworks/base/Android.mk:331: frameworks/base/../../system/media/mca/Docs.mk: No such file or directory
build/core/base_rules.mk:79: *** Module name: keystore
build/core/base_rules.mk:80: *** Makefile location: frameworks/base/cmds/keystore
build/core/base_rules.mk:81: *
build/core/base_rules.mk:82: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:83: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:84: *
build/core/base_rules.mk:85: * optional, debug, eng, tests, samples
build/core/base_rules.mk:86: *
build/core/base_rules.mk:87: * If the module is expected to be in all builds
build/core/base_rules.mk:88: * of a product, then it should use the
build/core/base_rules.mk:89: * "optional" tag:
build/core/base_rules.mk:90: *
build/core/base_rules.mk:91: * Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:92: * Android.mk for the affected module, and add
build/core/base_rules.mk:93: * the LOCAL_MODULE value for that component
build/core/base_rules.mk:94: * into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:95: * makefile(s) where it's necessary, if
build/core/base_rules.mk:96: * appropriate.
build/core/base_rules.mk:97: *
build/core/base_rules.mk:98: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:99: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:100: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:101: * build/target/product/core.mk
build/core/base_rules.mk:102: *
build/core/base_rules.mk:103: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.

Any ideas?
[Android Q&A, Help & Troubleshooting] dastin1015:
Add this line:

LOCAL_MODULE_TAGS := optional

to the Android.mk in this directory frameworks/base/cmds/keystore
[Android Q&A, Help & Troubleshooting] djsubtronic:
I didn't even have Android.mk in that folder, so I created it anyway and added that line, but I still got the same error....
[Android Q&A, Help & Troubleshooting] djsubtronic:
Ok I made teh necessary changes but I'm still getting the exact same error. Wtf...
[Android Q&A, Help & Troubleshooting] paxChristos:
Try putting this in your Android.mk:

#
# Copyright (C) 2009 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

LOCAL_PATH:= $(call my-dir)

include $(CLEAR_VARS)
LOCAL_SRC_FILES := keystore.cpp
LOCAL_C_INCLUDES := external/openssl/include
LOCAL_SHARED_LIBRARIES := libcutils libcrypto
LOCAL_MODULE:= keystore
include $(BUILD_EXECUTABLE)

include $(CLEAR_VARS)
LOCAL_SRC_FILES := keystore_cli.cpp
LOCAL_C_INCLUDES := external/openssl/include
LOCAL_SHARED_LIBRARIES := libcutils libcrypto
LOCAL_MODULE:= keystore_cli
LOCAL_MODULE_TAGS := debug
include $(BUILD_EXECUTABLE)

If you were missing that file (i just copy/pasted outta mine) you probably need to re-sync & make clobber before you rebuild.

Pax
[Android Q&A, Help & Troubleshooting] paxChristos:
Just saw this

You're compiling jb (instructions *should* be the same) so it might be that this particular module is broken in building/rom, so far.

Pax
[Android Q&A, Help & Troubleshooting] :
Dear Dustin sorry to interupt your thread im going to write some fixes ^^

make: *** No rule to make target `out/target/product/galaxys2/obj/SHARED_LIBRARIES/libmediayamahaservice_intermediates/export_includes', needed by `out/target/product/galaxys2/obj/EXECUTABLES/mediaserver_intermediates

This can be fixed by

mkdir -p out/target/product/galaxys2/obj/SHARED_LIBRARIES/libmediayamahaservice_intermediates/

touch out/target/product/galaxys2/obj/SHARED_LIBRARIES/libmediayamahaservice_intermediates/export_includes

i also had the problem when

[B]make: *** No rule to make target `out/target/product/galaxys2/obj/SHARED_LIBRARIES/libTvOut_intermediates/export_includes', needed by `out/target/product/galaxys2/obj/EXECUTABLES/mediaserver_intermediates[/B]

and it was fixed by

mkdir -p out/target/product/galaxys2/obj/SHARED_LIBRARIES/libLibTvOut_intermediates/

touch out/target/product/galaxys2/obj/SHARED_LIBRARIES/libTvOut_intermediates/export_includes

Cheers