yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] ultravioletnanokitty:
this isn't exactly a compilation issue, but it is directly related to building from source for my device.

does anyone have a clue what i need to do about either of these two issues? http://xdaforums.com/showpost.php?p=43631962&postcount=30

this is occurring under cm10, and https://github.com/ultravioletnanokitty/android_device_zte_V55-wifionly/tree/4.1 is my device config.
[Android Q&A, Help & Troubleshooting] bart452:
Did you fix it?
[Android Q&A, Help & Troubleshooting] LeMuecke:
No, but I plan to do the next days. Did you do with the fix in one of the lg forums or the cherrypick from github of paranoid?
[Android Q&A, Help & Troubleshooting] bart452:
You mean halo?

I got halo from this, it's just stock cm-10.1 with halo

https://github.com/UgoRaffaele?tab=repositories
[Android Q&A, Help & Troubleshooting] desalesouche:
hi, i have been reading until page , will continue, but as i am quite exhausted i will post my problem:

so here is my little log:

ls: cannot access device/*/u8860/cm.mk: No such file or directory

build/core/product_config.mk:234: * ** Cannot locate config makefile for product "cm_u8860". Stop.

device=huawei honor(u8860)

trying to build beanstalk http://xdaforums.com/showthread.php?t=2339050

https://github.com/desalesouche/android_vendor_huawei-1
[Android Q&A, Help & Troubleshooting] killersloth:
You need cm.mk file in your device tree.

Use a different devices cm.mk as reference, adapt it to your device.
[Android Q&A, Help & Troubleshooting] ktempleton:
Also if you notice you have one make sure you have renamed your device folder and have it under the correct listing for example

device/huawei/u8860
[Android Q&A, Help & Troubleshooting] desalesouche:
i think i have some progress isn't it? : http://pastebin.com/WwGUVnXd

now i am trying to understand errors (googling...)

edit:another pastebin http://pastebin.com/WwGUVnXd

some advice please?
[Android Q&A, Help & Troubleshooting] awidawad:
What device tree are you using? The cm.mk file or Android.mk file thinks you need a prebuilt kernel. Post your device tree I could fix it.
[Android Q&A, Help & Troubleshooting] desalesouche:
]

i Put this in device/huawei/msm7x30-common folder - https://github.com/cm2huawei/android...msm7x30-common

This as main device tree: device/huawei/u8860 - https://github.com/ShenduOS/android_device_huawei_u8860

This as vendor: https://github.com/cm2huawei/android_vendor_huawei

kernel: https://github.com/cm2huawei/android_kernel_huawei_honor

or that one : https://github.com/cm2huawei/kernel_huawei_u8860

does these informations are ok for you?

thank you very much.

isn't that too much include? =

desalesouche@desalesouche-System-Product-Name:~/beanstalk$ . build/envsetup.sh && brunch u8860

including device/generic/armv7-a-neon/vendorsetup.sh

including device/generic/armv7-a/vendorsetup.sh

including device/generic/goldfish/vendorsetup.sh

including device/generic/mips/vendorsetup.sh

including device/generic/x86/vendorsetup.sh

including device/huawei/u8860/vendorsetup.sh

including device/ti/panda/vendorsetup.sh

including vendor/cm/vendorsetup.sh

including sdk/bash_completion/adb.bash

including vendor/cm/vendorsetup.sh

Trying dependencies-only mode on a non-existing device tree?
[Android Q&A, Help & Troubleshooting] awidawad:
No it doesn't seem too much. I've compiled a local_manifest.xml you can try. Copy and paste the following into .repo/local_manifest.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<!-- Add in remotes -->
<remote name="gh" fetch="git://github.com/" />

<!-- Add device paths -->
<project path="hardware/msm7k" name="ShenduOS/android_hardware_msm7k" remote="gh" revision="jellybean"/>
<project path="device/huawei/msm7x30-common" name="ShenduOS/android_device_huawei_msm7x30-common" remote="gh" revision="jellybean" />
<project path="device/huawei/u8860" name="zyr3x/android_device_huawei_u8860" remote="gh" revision="jellybean" />
<project path="vendor/huawei" name="ShenduOS/android_vendor_huawei" revision="jellybean" remote="gh" />
<project path="hardware/libhardware_legacy" name="ShenduOS/android_hardware_libhardware_legacy" remote="gh" revision="jellybean" />
<project path="hardware/qcom/audio" name="ShenduOS/android_hardware_qcom_audio" remote="gh" revision="jellybean" />
<project path="hardware/qcom/display" name="ShenduOS/android_hardware_qcom_display" remote="gh" revision="jellybean" />
<project path="hardware/qcom/gps" name="ShenduOS/android_hardware_qcom_gps" remote="gh" revision="jellybean"/>
<project path="hardware/qcom/media" name="ShenduOS/android_hardware_qcom_media" remote="gh" revision="jellybean" />
<project path="hardware/libhardware" name="ShenduOS/android_hardware_libhardware" remote="gh" revision="jellybean"/>
<project path="device/generic/goldfish" name="ShenduOS/android_device_generic_goldfish" remote="gh" revision="jellybean" />

</manifest>
[Android Q&A, Help & Troubleshooting] desalesouche:
thank you very much...

how can i open .repo ?

edit : i found...sorry it was under beanstalk/.repo

edit bis: http://pastebin.com/A0S6bGbD
[Android Q&A, Help & Troubleshooting] awidawad:
You need to fetch prebuilts. Run this before you brunch your device:

vendor/cm/get-prebuilts
[Android Q&A, Help & Troubleshooting] desalesouche:
so, now it is the first time it is compiling for so long time.... :o

great. will give feed back when compilation would end. :D

edit: http://pastebin.com/80DewsMc

edit bis: as i watch in out /... i can see a part of the rom is done. but i have only 5 or 6 apps in system/app.

kernel is missing. :cyclops: but that is already a good good progress...

lets try again :silly:

edit ter: i did a repo sync under /beanstalk

and it did sync with shendu githb, i think according the local_manifest.xml.

so i did again vendor/cm/get-prebuilts in terminal then i compiled..

here is a new pastebin http://pastebin.com/xEebrmay
[Android Q&A, Help & Troubleshooting] hell_lock:
I have the same error
[Android Q&A, Help & Troubleshooting] bart452:
Tell me if you fixed it, I'm stuck...
[Android Q&A, Help & Troubleshooting] vpart_aeip:
please help me, I have a problem in compile Pac-man for the device Ancora :(

i'm sory for bad english :(
[Android Q&A, Help & Troubleshooting] desalesouche:
compiling carbon for u8860

here is my last errors http://pastebin.com/nuXTDw2N any help please?

thank you.

edit still trying to finish compilation...anyone heard about that error?

make: *** No rule to make target `/home/desalesouche/carbon/out/host/linux-x86/bin/minigzip', needed by `/home/desalesouche/carbon/out/target/product/u8860/ramdisk.img'. Stop.
[Android Q&A, Help & Troubleshooting] nolinuxnoparty:
http://pastebin.com/pE7aSrwV

While compiling PAC for HTC Pico :|
[Android Q&A, Help & Troubleshooting] soccerfan6789:
http://pastebin.com/Jpa6SDMD

Full log ^^

Seems to he something wrong with Bluetooth...bottom line error:

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/shariq/aosp/kernel/samsung/msm8660-common'

make: *** [TARGET_KERNEL_BINARIES] Error 2

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

create a new version of this paste
[Android Q&A, Help & Troubleshooting] krislibaeer:
please do not use screenshots and that font :laugh: it is really hard to read

please post it in a file or on pastebin

but i think i know the problem

use this frameworks_native https://github.com/Team-Kang-Droid/android_frameworks_native/tree/jb4.2-TRDS important use branch jb4.2-TRDS

and this frameworks_av https://github.com/camcory/platform_frameworks_av branch cm-10.1

you have duplicated lines in msm_ion.h and in ion.h

your device tree ??? link??

bionic/libc/kernel/common/linux/msm_ion.h:24:47: error: conflicting declaration 'ION_HEAP_TYPE_IOMMU'

device/htc/pico/include/linux/ion.h:43:2: error: 'ION_HEAP_TYPE_IOMMU' has a previous declaration as 'ion_heap_type ION_HEAP_TYPE_IOMMU'

bionic/libc/kernel/common/linux/msm_ion.h:25:44: error: conflicting declaration 'ION_HEAP_TYPE_CP'

device/htc/pico/include/linux/ion.h:44:2: error: 'ION_HEAP_TYPE_CP' has a previous declaration as 'ion_heap_type ION_HEAP_TYPE_CP'

bionic/libc/kernel/common/linux/msm_ion.h:27:6: error: multiple definition of 'enum ion_heap_ids'

device/htc/pico/include/linux/ion.h:65:6: error: previous definition here

bionic/libc/kernel/common/linux/msm_ion.h:45:6: error: multiple definition of 'enum ion_fixed_position'

device/htc/pico/include/linux/ion.h:82:6: error: previous definition here

bionic/libc/kernel/common/linux/msm_ion.h:85:8: error: redefinition of 'struct ion_flush_data'

device/htc/pico/include/linux/ion.h:695:8: error: previous definition of 'struct ion_flush_data'

bionic/libc/kernel/common/linux/msm_ion.h:94:8: error: redefinition of 'struct ion_flag_data'

device/htc/pico/include/linux/ion.h:711:8: error: previous definition of 'struct ion_flag_data'
[Android Q&A, Help & Troubleshooting] awidawad:
I'm getting these errors too I'm guessing you have an msm7x30 device? I'm on to something right now in terms of fixing it but when it compiles the ROM won't boot
[Android Q&A, Help & Troubleshooting] LeMuecke:
Hey guys, everyone says you need lots of RAM to build Android, or to build it fast. But if I watch my building process, not the half of my RAM (6GB) is used.

Is there any way to get it to use more RAM, so the whole building process gets faster?

Regards, LeMuecke
[Android Q&A, Help & Troubleshooting] cj360:
How many threads are u using? -j8 should use most~to~all of it. If not u can always increase the -j# number of threads you're using to build.
[Android Q&A, Help & Troubleshooting] LeMuecke:
I use -j3, as the rule was number of cores +1, but I'll try :)
[Android Q&A, Help & Troubleshooting] rpeters1428:
Hello,

I was trying to build and compile jb 4.3 for mako (Nexus 4).

I did repo sync just fine and everything worked until the compile make command and this is what I got:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.2.1.000.000
TARGET_PRODUCT=full_mako
TARGET_BUILD_VARIANT=userdebug
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.5.0-37-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
OUT_DIR=out
============================================
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
No private recovery resources for TARGET_DEVICE mako
make: *** No rule to make target `j5'. Stop.

I tried all possibilities and still got the same thing in the end. I am brand new at trying this so any help would be wonderful.
[Android Q&A, Help & Troubleshooting] ktempleton:
You need to type

make bacon -j5 from what you posted it looks like you forgot to put. - in front of the j

Or make otapackage -j5
[Android Q&A, Help & Troubleshooting] hell_lock:
While compiling cm10.2 I got this:

frameworks/av/media/libstagefright/AwesomePlayer.cpp:1016: error: undefined reference to 'android::LPAPlayer::mObjectsAlive'
frameworks/av/media/libstagefright/AwesomePlayer.cpp:1088: error: undefined reference to 'android::LPAPlayer::LPAPlayer(android::sp<android::MediaPlayerBase::AudioSink> const&, bool&, android::AwesomePlayer*)'
frameworks/av/media/libstagefright/AwesomePlayer.cpp:1689: error: undefined reference to 'android::LPAPlayer::mObjectsAlive'
collect2: error: ld returned 1 exit status
[Android Q&A, Help & Troubleshooting] LeMuecke:
Which repos are you using?
[Android Q&A, Help & Troubleshooting] blackmambazzz:
Cyanogen has made a workaround which ifdeffed the A2DP notification stuff out to get it compile.

But I cannot confirm that it works because on my msm7x30 device cm-10.2 isnt booting.

http://review.cyanogenmod.org/#/c/46451/
[Android Q&A, Help & Troubleshooting] desalesouche:
hi i hope that this is one of my last errors compiltaion...

http://pastebin.com/64r4kXuE

error: do_inode_allocate_extents: Failed to allocate 64 blocks

+ '[' 1 -ne 0 ']'

+ exit 4

error: failed to build /home/desalesouche/beanstalk/out/target/product/u8800pro/obj/PACKAGING/systemimage_intermediates/system.img from /home/desalesouche/beanstalk/out/target/product/u8800pro/system

make: *** [/home/desalesouche/beanstalk/out/target/product/u8800pro/obj/PACKAGING/systemimage_intermediates/system.img] Error 1

make: *** Deleting file `/home/desalesouche/beanstalk/out/target/product/u8800pro/obj/PACKAGING/systemimage_intermediates/system.img'

any help please?

EDIT: the rom size is too big for my device...i have to trim it down.so i can make ota package

where to delete ringtones and other from .mk before to compile...?

thank you.
[Android Q&A, Help & Troubleshooting] LighingBB:
Do you have enough free disk space on HDD?
[Android Q&A, Help & Troubleshooting] desalesouche:
desalesouche@desalesouche-System-nogiveup:~$ df -h

Filesystem Size Used Avail Use% Mounted on

/dev/sda1 543G 61G 455G 12% /

none 4,0K 0 4,0K 0% /sys/fs/cgroup

udev 3,9G 4,0K 3,9G 1% /dev

tmpfs 796M 1004K 795M 1% /run

none 5,0M 0 5,0M 0% /run/lock

none 3,9G 156K 3,9G 1% /run/shm

none 100M 36K 100M 1% /run/user

desalesouche@desalesouche-System-nogiveup:~$ it seem yes...
[Android Q&A, Help & Troubleshooting] hazedabeast:
KCONFIG_SELINUX((null))

KCONFIG_LOG_SELINUX((null))

KCONFIG_VARIANT((null))

***

*** You must specify VARIANT_DEFCONFIG !

***

make[3]: *** [cyanogen_d2spr_defconfig] Error 1

make[2]: *** [cyanogen_d2spr_defconfig] Error 2

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/hamzeh/JB/nexus/kernel/samsung/d2'

make: *** [/home/hamzeh/JB/nexus/out/target/product/d2spr/obj/KERNEL_OBJ/.config] Error 2
[Android Q&A, Help & Troubleshooting] hazedabeast:
any ideas?
[Android Q&A, Help & Troubleshooting] desalesouche:
after compiling and getting the zip, ii have that error

Error in path/to/zip/xyz.zip

(Status 6)

Installation aborted

can someone give help please?
[Android Q&A, Help & Troubleshooting] speed_bot:
ok guys after being inactive due to personel reasons i will be active in the thread again :p

.ok do this bro reboot to recovery select that zip to install after that goto advanced and select export recovery log and gimme the log.
[Android Q&A, Help & Troubleshooting] speed_bot:
use prebuilt kernel rather than inline building
[Android Q&A, Help & Troubleshooting] Kayant:
Also another come across this issue??

Install system fs image: /home/kayant/PAC/out/target/product/mb526/system.img
/home/kayant/PAC/out/target/product/mb526/system.img+ maxsize=331776192 blocksize=135168 total=345704832 reserve=3379200
error: /home/kayant/PAC/out/target/product/mb526/system.img+ too large (345704832 > [335155392 - 3379200])
make: *** [/home/kayant/PAC/out/target/product/mb526/system.img] Error 1
make: *** Deleting file `/home/kayant/PAC/out/target/product/mb526/system.img'

Is there any way I can reduce the system size so it compiles?

Thanks for the help ^_^
[Android Q&A, Help & Troubleshooting] desalesouche:
will try to provide log by one of my friend who have the phone, mine is still in shop to be fixed...

by the way:

i did repo sync and then tried to recompile=

packages/apps/DSPManager/cyanogen-dsp/cyanogen-dsp.cpp:211:1: sorry, unimplemented: non-trivial designated initializers not supported

packages/apps/DSPManager/cyanogen-dsp/cyanogen-dsp.cpp:211:1: sorry, unimplemented: non-trivial designated initializers not supported

packages/apps/DSPManager/cyanogen-dsp/cyanogen-dsp.cpp:211:1: sorry, unimplemented: non-trivial designated initializers not supported

packages/apps/DSPManager/cyanogen-dsp/cyanogen-dsp.cpp:211:1: warning: missing initializer for member 'audio_effect_library_s::release_effect' [-Wmissing-field-initializers]

packages/apps/DSPManager/cyanogen-dsp/cyanogen-dsp.cpp:211:1: warning: missing initializer for member 'audio_effect_library_s::get_descriptor' [-Wmissing-field-initializers]

make: *** [/home/desalesouche/beanstalk/out/target/product/u8800pro/obj/SHARED_LIBRARIES/libcyanogen-dsp_intermediates/cyanogen-dsp.o] Error 1

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

any advice please?

building beanstalk 1.300 for huawei u8800pro
[Android Q&A, Help & Troubleshooting] speed_bot:
instead increase the system image size in boardconfig
[Android Q&A, Help & Troubleshooting] speed_bot:
uncomment dsp manager for now
[Android Q&A, Help & Troubleshooting] fOmey:
Im experiencing the same issue, Must of been some changes pushed over to the cyanogen repo..

Can you please elaborate on this..
[Android Q&A, Help & Troubleshooting] speed_bot:
goto packages/apps/dsp

rename Android.mk to

Android.mk.Disabled
[Android Q&A, Help & Troubleshooting] fOmey:
Excellent, Just wanted to clarify.
[Android Q&A, Help & Troubleshooting] desalesouche:
Creating filesystem with parameters:

Size: 264634368

Block size: 4096

Blocks per group: 32768

Inodes per group: 8080

Inode size: 256

Journal blocks: 1024

Label:

Blocks: 64608

Block groups: 2

Reserved block group size: 15

error: do_inode_allocate_extents: Failed to allocate 224 blocks

+ '[' 1 -ne 0 ']'

+ exit 4

error: failed to build /home/desalesouche/beanstalk/out/target/product/u8800pro/obj/PACKAGING/systemimage_intermediates/system.img from /home/desalesouche/beanstalk/out/target/product/u8800pro/system

make: *** [/home/desalesouche/beanstalk/out/target/product/u8800pro/obj/PACKAGING/systemimage_intermediates/system.img] Error 1

make: *** Deleting file `/home/desalesouche/beanstalk/out/target/product/u8800pro/obj/PACKAGING/systemimage_intermediates/system.img'

does the solution is same as that one?: instead increase the system image size in boardconfig

thank you...

here is my boardconfig.mk

BOARD_BOOTIMAGE_PARTITION_SIZE := 0x04200000

BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x05300000

BOARD_SYSTEMIMAGE_PARTITION_SIZE := 264634368 #256MB

BOARD_USERDATAIMAGE_PARTITION_SIZE := 274464768 #1GB

BOARD_PERSISTIMAGE_PARTITION_SIZE := 5242880 #5MB

BOARD_CACHEIMAGE_PARTITION_SIZE := 134217728 #128MB

BOARD_TOMBSTONESIMAGE_PARTITION_SIZE := 4096000 #4000KB

BOARD_FLASH_BLOCK_SIZE := 131072

EDIT: fixed

error: do_inode_allocate_extents: Failed to allocate 224 blocks

Block size: 4096

mutiply number of block with number of number of block size(226*4096=917504)

add result to BOARD_SYSTEMIMAGE_PARTITION_SIZE := 264634368 #256MB

(917504+264634368= 265551872)= new value of BOARD_SYSTEMIMAGE_PARTITION_SIZE := 265551872 #256MB

and after that=

Package Complete: /home/desalesouche/beanstalk/out/target/product/u8800pro/BeanStalk1.300-20130805-u8800pro.zip :silly:

this lastfix is due to my old step father...
[Android Q&A, Help & Troubleshooting] Sushibagel:
Hey everyone I need some help. I'm trying to build PAC using some of my own edited repos. In my local manifest I've used some remove-project commands but those keep failing. Below is what I use to remove. I've tried replacing PAC-man with pac-man, pac, cm CyanogenMod and probably a few more that I forgot but can't seem to get the removes to work. Any help will be much appreciated.

<remove-project name="PAC-man/android_frameworks_base" />
[Android Q&A, Help & Troubleshooting] ktempleton:
Did you try platform instead of pacman
[Android Q&A, Help & Troubleshooting] Kayant:
Pac-man use a different config for their naming of repos in their manifest.

It should be <remove-project name="android_frameworks_base" />

Look here for more examples ---> https://github.com/Kayant/Central_manifest_4.2/blob/PAC4.3/local-manifest4.3.xml

the remove command uses only what is in the name="..." string in default.xml
[Android Q&A, Help & Troubleshooting] vpart_aeip:
hello guys,I have problems in compiling pac-man for ancora device, please help me :(

this log error http://pastebin.com/tXWkDWT0
[Android Q&A, Help & Troubleshooting] desalesouche:
beanstalk is not booting...

http://pastebin.com/Eu2vFvyx

any advice please?

thank you.
[Android Q&A, Help & Troubleshooting] iron86:
Hi all!

How to create configs (device tree and proprietary files) for unsupported cyanogenmod device?

My device is OPPO Finder X907, kernel source

thanks
[Android Q&A, Help & Troubleshooting] Kayant:
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
[Android Q&A, Help & Troubleshooting] iron86:
Already read. Besides many other similar instructions for example this, but all a distant leadership. I would like more detail
[Android Q&A, Help & Troubleshooting] Sushibagel:
Seems to have worked thanks!
[Android Q&A, Help & Troubleshooting] Astrali:
what to do when i dont got these proprietary blob files yet and cant seem to find any on github?

my vendor is FAEA

and my device is the FAEA F1 - codename: msm8x25q_n451_f1

i managed to get my build enviroment up and running but the output recoverys just result in a black or backlightened screen.

i guess thats because of missing proprietary files (no vendor directory at the moment).

i would appreciate any help i could get :)

Greets - Astrali
[Android Q&A, Help & Troubleshooting] TheMrcool212:
I was building CM10.2 ROM for my TF101. The build was fine like normally i done. When it almost finishes i got this error:

raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/dev/block/mmcblk0p1 /system ext4 ro wait"

If someone want to take a look at the fstab file, here it is: https://github.com/josteink/device_asus_tf101/blob/jellybean_4.3/fstab.ventana
[Android Q&A, Help & Troubleshooting] awidawad:
[MENTION=4445428]speed_bot[/MENTION] I'm still getting these errors do they ring a bell? I'm in need of your magical advice! Thanks!
[Android Q&A, Help & Troubleshooting] xtrymind:
i have succesfully build cm10.1 for my ace2, but after flash it via cwm, it stuck on samsung logo...

other people build with same device tree have succesfully booting, any idea whats wrong? :confused:
[Android Q&A, Help & Troubleshooting] ultravioletnanokitty:
i don't know about your repos, but the msm8x60 display repos have the TARGET_PREBUILT_HEADERS variable, which allow you to use the generic headers if your device's are out of date like mine are. add

TARGET_PREBUILT_HEADERS := true

to your BoardConfig.mk and see how it goes.
[Android Q&A, Help & Troubleshooting] Astrali:
i am stuck :(

i still dont get forward .. :(

i just tried the Gscript from here : http://xdaforums.com/showthread.php?t=2156913&page=2

but it gives me lots of errors and no recovery.img will be pulled from my device.

as far as i can guess for my device there is no real "recovery" partition it is more likely to be built in the kernel somehow.

i got a running chinese CWM port called cofface but i am not able to read chinese.

Taking this one as base for a new recovery (via builder) does not work.

having a nand backup of my system with a "fakeflash" CWM i already got (from faea forum) extracts a recovery.img but this one either does not work for using the builder.

it got same size as the boot.img this leads me to think it is not really the recovery.img

so i decided to compile my own from scratch.

but theres no manifest.xml for my device

so i am stuck again!

please give me a hint on how to proceed :)

my vendor is FAEA

and my device is the FAEA F1 - codename: msm8x25q_n451_f1 this code was also shown sometimes on builder.clockworkmod

but all i noticed didnt boot correctly (screen stays black).

i count on you guys! :D

Greets - Astrali
[Android Q&A, Help & Troubleshooting] speed_bot:
link me to the hardware sources that u r using
[Android Q&A, Help & Troubleshooting] desalesouche:
at k2wl

^
[COLOR="Red"]Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
[/COLOR]
try make update-api
[Android Q&A, Help & Troubleshooting] desalesouche:
here you have all repository. https://github.com/Herna-u880pro?tab=repositories

and last pastebin http://pastebin.com/FK3Jf9Gv

may i ask how to fix please?
[Android Q&A, Help & Troubleshooting] desalesouche:
hi please some help...or advice? :)

http://pastebin.com/nbeX1BUW
[Android Q&A, Help & Troubleshooting] LighingBB:
I've got such kind of errors when don't included some libraries in project. Maybe you edited Makefile or Android.mk and deleted or commented a bit more then needed?
[Android Q&A, Help & Troubleshooting] LighingBB:
Does anyone know how to deal with it?:(