yashsingh1/xdaforums huggingface dataset:
[Android] FayaX[PT]:
That was fixed already.

My error now is:

1 error generated.

target thumb C: clatd <= external/android-clat/clatd.c

build/core/binary.mk:706: recipe for target '/home/fayax/android/aosp-caf/out/target/product/bacon/obj/EXECUTABLES/bootanimation_intermediates/BootAnimation.o' failed

make: *** [/home/fayax/android/aosp-caf/out/target/product/bacon/obj/EXECUTABLES/bootanimation_intermediates/BootAnimation.o] Error 1

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

system/bt/tools/btsnoop_dump/btsnoop_dump.c:203:31: warning: incompatible pointer types passing 'struct sockaddr_un *' to parameter of type 'const struct sockaddr *' [-Wincompatible-pointer-types]

ret = connect(sk, &serv_addr, addr_len);

^~~~~~~~~~

bionic/libc/include/sys/socket.h:274:53: note: passing argument to parameter here

__socketcall int connect(int, const struct sockaddr*, socklen_t);

^

system/bt/tools/btsnoop_dump/btsnoop_dump.c:326:15: warning: unused parameter 'argc' [-Wunused-parameter]

int main (int argc, char * argv[])

^

system/bt/tools/btsnoop_dump/btsnoop_dump.c:326:28: warning: unused parameter 'argv' [-Wunused-parameter]

int main (int argc, char * argv[])

^

3 warnings generated.

make: *** wait: No child processes. Stop.

My device tree : https://github.com/FayaX-PT/android_device_oneplus_bacon/tree/bacon_aosp_6.0

My manifest: https://github.com/FayaX-PT/android_rom_development/tree/bacon_aosp_6.0

Sources: https://github.com/AOSP-CAF/platform_manifest
[Android] Arvind7352:
Is there any reference which explains '-k' & '-i' params/attrs in make.....

I need to know about it :)
[Android] Uchiha_Dev:
-i ignores nay errors and continues building, -k also kind of does the same but not as effective as -i
[Android] Arvind7352:
If you don't know what does it specifically do, then ignore adding those, and try solving errors ;)
[Android] Uchiha_Dev:
I knew about -i and I have built CM 13 and booted it even though it was giving errors (ignored via -i), well with few bugs because of the ignored errors. Used -k for the first time, read it somewhere, now trying aagain with -i only.
[Android] Arvind7352:
Ignores errors!? (If you're right)

Then don't do that. luckily you got it to boot that doesn't mean using that is correct.

Make a habit to face everything [emoji5] ([emoji13]), else you can't solve an error

But I still think... Is there a parameter which can make you ignore errors and give a successful build... Can you share the reference if you find it?
[Android] lilferraro:
Does anyone know how to fix this? I used the same device setup for bliss minus the vendor stuff?

including vendor/cm/vendorsetup.sh
build/core/envsetup.mk:165: *** No config file found for TARGET_DEVICE t02ltespr. Stop.
Device lt02ltespr not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for lt02ltespr not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/envsetup.mk:165: *** No config file found for TARGET_DEVICE t02ltespr. Stop.

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

I have added everything needed to my local_manifest.xml and vendorsetup.sh. If someone could look at my device on github and see why its askin me for device config?

https://github.com/lilferraro/android_device_samsung_lt02ltespr/tree/cm-13.0

and

https://github.com/lilferraro/android_device_samsung_lt02ltexx-common/tree/cm-13.0

~~Thank You~~

***EDIT: Solved by correcting typo... Sorry for taking up space in thread.
[Android] laperry1:
bump... ... again, any assistance getting this working would be greatly appreciated!
[Android] JonathanRAZ:
I iam getting xlint error can anyone help
[Android] hdorius:
Pastebin your error, can't help you if u not posted it
[Android] JonathanRAZ:
http://pastebin.com/DGy28pvB [MENTION=841471]HDO[/MENTION]riius

---------- Post added at 03:21 AM ---------- Previous post was at 03:19 AM ----------
[Android] Uchiha_Dev:
yes, I do try to solve as many errors as I can but there are tons of errors in so many apk's (really) SettingsProvider, ThemesProvider and many other issues in libstagefright related files, I hadn't even touched them.

---------- Post added at 05:32 AM ---------- Previous post was at 05:28 AM ----------

Ok, AICP compiled successfully this time, everything is present but services.jar is missing classes.dex :/ All the jar's which were missing classes.dex in first compile are now good except for services.jar

---------- Post added at 05:47 AM ---------- Previous post was at 05:32 AM ----------

Here are the errors I get, they are not all of the errors I get, only the errors which were logged in terminal

http://pastebin.com/BE8XkPpi

I didn't even touch any of those files
[Android] Arvind7352:
Delete, I was wrong... Dex2oatd does the Pre-Opt work

Try without Jack Toolchain
[Android] Uchiha_Dev:
The ROM is deodexed, there is no odex (and I know what odexing and deodexing means)
[Android] MZO:
I'd like to thank you for this guide. Slick and understandable
[Android] Uchiha_Dev:
[MENTION=6049586]Arvind7352[/MENTION]

export ANDROID_COMPILE_WITH_JACK:=false

-bash: export: `ANDROID_COMPILE_WITH_JACK:=false': not a valid identifier

nevermind, had to remove : from :=
[Android] Arvind7352:
Edited the Post Already!!

Remove that colon

Happy Building[emoji6]

I have started my Build just now...(a Last try, without Jack)
[Android] Uchiha_Dev:
didn't see the edit, figured it out had to remove :

good luck (y) I am going to build too
[Android] Uchiha_Dev:
I always get this error while compiling AICP !

http://pastebin.com/Bbp4ddbi

I haven't even touched the file causing error

Edit : Fixed it, hell yeah :3
[Android] Arvind7352:
https://android.googlesource.com/pl...stagefright/codecs/on2/enc/SoftVPXEncoder.cpp

Replace this file and try

The contents in this file are the same as of CyanogenMod/AOSP (the link I gave)/SlimROMs code (the file, Compared each of them )

AICP's file have a couple of lines (5-10) missing when compared with these Repo's

Just a guess, try it
[Android] Uchiha_Dev:
you were a little bit too late haha, I fixed it long ago, even fixed other errors. Compiling good now. Just worried about the app and jar compiling. They seem to bombard me with errors, will have to wait a few more hours to reach that point
[Android] Jacky_Chen:
Thank you for your prompt reply.

I followed the guide and download the CM11.0,is this wrong?(forgive my poor English...)

so I want to make the newest CM11 to be used on my Nexus 4. Also it's just a try for learning how to make a rom from source.

but As i mentioned above,I don't quite understand where to findout the information to write on the local_manifest.xml.

Thank u again,hope your reply!:D
[Android] jackeagle:
Your device is Officially Supported and hence to build Cm11 Rom you dont need Local_manifest.xml...Just download the sources and . build/envsetup.sh

brunch mako

it will download the device/kernel/vendor trees on its own once u use above commands.
[Android] Jacky_Chen:
You mean that if Device is supported by the rom officially,then I don't need Local_manifest.xml . By another way,if the Device is not supported by the rom,then Local_manifest.xml is essential? is this correct?

So much thank for u!:victory:
[Android] RVR:
yes thats right
[Android] keshavt:
[MENTION=5216756]jackeagle[/MENTION] ,no CarbonRom is their for my device and I want to port it. How can I do it?

TIA

Sent using XDA Premium app.
[Android] jackeagle:
may i know which device you are talking about ? and no use of porting Rom's instead always build from source and this Guide for that purpose only :)
[Android] keshavt:
[MENTION=5216756]jackeagle[/MENTION] it is Galaxy Grand 2 SM-G7102.

Sent using XDA Premium app.
[Android] jackeagle:
For Grand 2 Cm11 is in Progress just wait for it ... Porting is very difficult and needs some knowledge too let cm11 arrive and then build from source if possible..
[Android] DOBBY0:
Already have a build of CM

Built Cyanogenmod over the weekend, but I wanted to add features from other roms to it. Not really sure how to do that. Could I get some help?
[Android] Kishan14:
Fir that u gotta cherry-pick the features... Cherry-Picking is easy.. But solving it's error is not.. So first start from basic ones... Here cherry-pick is not explained... U can try searching on xda and Google - a best friend.. ;)
[Android] störte:
Hi

I like your Tutorial .

Just one Question.

I want to replace the cm11 Kernel with another one. Do i have to add this then to my local manifest ?
[Android] amitman76:
Need Some More Info

Thanks a lot for this Information . I am bit confused on on part . Sorry , as I am very new to android

**************************************************************************************************************************************

ow before starting with Building guide you have to Download your Device Identity That is has follows

1) Device Tree

2) Vendor

3) Kernel

The Above files are very Vital Parameters of building they specify your device and its Characteristics.

Now you might think from where you have to download those files?

Don't be confused its simple Search in our device forum for CM Tree and Kernel and Vendor. The Dev of CM for your Device forum will specify it in his ROM thread.

Once you obtain the github for your Device Tree, Vendor and Kernel. Enter following command

*********************************************************************************************************

I am presently trying to port for my Smart Phone Spice MI 435. So , how do I get the Device Tree for this ?? or where Do I have to search for and what is Device Forum for CM Tree ?

Regards

Amit

Regards
[Android] Kishan14:
For any unofficial device and extra stuff u wanna download with your source, you should use local_manifests.xml.. So your answer is yes..!

First check if cyanogenmod is available for your device.. If yes then use its device tree..
[Android] AndroidOrDie:
Hi, can anyone help my how to patch omni rom with justachis http://xdaforums.com/showthread.php?t=2754997 ? I successfully compiled working omni rom from source for my n7000 but i dont know how to start now. :( thanks
[Android] kdp162:
Setting up build enviorment

I'm using this guide to set up to build for the first time I get as far as the init and when I do I get this error

error: in `init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat --repo-url=https://gerrit.googlesource.com/git-repo --repo-branch=stable`: revision kitkat in manifests not found﻿

Any help would be appreciated.
[Android] jackeagle:
Hi,

If you are building Rom from AOSPA then Repo Init Command is has Follows

repo init -u https://github.com/AOSPA/manifest -b kitkat

copy paste above command and Repo init then repo sync :)
[Android] letmedanz:
Could someone with the know how put together a guide for setting up Android Environment for non-ubuntu based Linux distros?

Switched to opensuse & finding it quite difficult to put 2 things together.. haha
[Android] ##W4TCH0UT##:
Well I don't recommend installing opensuse. Idk if it can build android. Use bbqlinux, it has all packages pre installed. All you need to do is compile, with changes of course. Arch Linux is good too. Older versions of Linux are mostly not capable to build android.
[Android] Arvind7352:
Only Post your errors if you have completely NO-IDEA about a thing/error, or if you need some opinions on your solution to a particular thing....

It wastes other people's (including me) efforts in searching and giving you a solution, if you know..... :)

Not a warning, an advice (purely.. Don't take this in a wrong tone)
[Android] FayaX[PT]:
target thumb C++: libjni_latinime_common_static <= packages/inputmethods/LatinIME/native/jni/src/utils/jni_data_utils.cpp

device/oppo/common/overlay/frameworks/base/core/res/res/values/config.xml:24: error: Resource at config_deviceKeyHandlerLib appears in overlay but not in the base package; use <add-resource> to add.

device/oppo/common/overlay/frameworks/base/core/res/res/values/config.xml:28: error: Resource at config_deviceKeyHandlerClass appears in overlay but not in the base package; use <add-resource> to add.

device/oppo/common/overlay/frameworks/base/core/res/res/values/config.xml:32: error: Resource at config_deviceKeyHandlerLib appears in overlay but not in the base package; use <add-resource> to add.

device/oppo/common/overlay/frameworks/base/core/res/res/values/config.xml:36: error: Resource at config_deviceKeyHandlerClass appears in overlay but not in the base package; use <add-resource> to add.

device/oneplus/bacon/overlay/frameworks/base/core/res/res/values/config.xml:51: error: Resource at config_deviceHardwareWakeKeys appears in overlay but not in the base package; use <add-resource> to add.

device/oneplus/bacon/overlay/frameworks/base/core/res/res/values/config.xml:207: error: Resource at config_intrusiveBatteryLed appears in overlay but not in the base package; use <add-resource> to add.

device/oneplus/bacon/overlay/frameworks/base/core/res/res/values/config.xml:309: error: Resource at config_multiColorNotificationLed appears in overlay but not in the base package; use <add-resource> to add.

device/oneplus/bacon/overlay/frameworks/base/core/res/res/values/config.xml:313: error: Resource at config_multiColorBatteryLed appears in overlay but not in the base package; use <add-resource> to add.

build/core/package_internal.mk:276: recipe for target '/home/fayax/android/aosp-caf/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk' failed

make: *** [/home/fayax/android/aosp-caf/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Error 1

make: *** Deleting file '/home/fayax/android/aosp-caf/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk'

make: *** Waiting for unfinished jobs....
[Android] Uchiha_Dev:
I first looked for a solution and did not find, spent 15-20 minutes. Just after I posted my problem, 3 minutes later I find a solution. That happen to me every time :p

---------- Post added at 11:32 AM ---------- Previous post was at 11:29 AM ----------

you should go through the log and go to the .xml which is giving errors, look at the line number find that line and look at the problem and then search for it. I did the same when I was getting the issue I just posted a few hours agob and fixed it
[Android] FayaX[PT]:
For now I just commented it :D

new error :(

http://pastebin.com/pAHgFuJZ
[Android] Uchiha_Dev:
no idea about kernel

What I am interpreting is even if you have disabled module support, the makefile specifies to build modules. You need to enable module support or delete specify to not build modules (I might be 100% wrong about this)
[Android] Uchiha_Dev:
Please help me with this, boot.img issue

http://pastebin.com/TG0WZRCp I have found no solution since past 30 minutes
[Android] neonkat:
boot.img is larger than the partition,try to *resize the partition.(recovery_image_partition_size)
[Android] MSF Jarvis:
Or maybe change the compression method in the kernel defconfig to XZ if not already done so.
[Android] Uchiha_Dev:
[MENTION=5991747]neonkat[/MENTION] [MENTION=6552280]MSF Jarvis[/MENTION]

I did, Every time I increase the partition max value the boot.img size gets even bigger
[Android] MSF Jarvis:
That's ****ed up (Don't mind the slang). You have an idea how to change the ramdisk compression method??
[Android] neonkat:
better use xz compression as suggested by Jarvis.for me,it reduced zimage from ~8mb to ~6 mb.
[Android] MSF Jarvis:
If you look at my GitHub profile at https://GitHub.com/MSF-Jarvis , you'll see the kernel repo for HTC Pico and I have indeed played with the compression, you can see the commits for reference.
[Android] Uchiha_Dev:
[MENTION=6552280]MSF Jarvis[/MENTION] thanks man, you saved me some sleep, it worked. Huge huge thanks
[Android] MSF Jarvis:
And this stole a night's sleep from me because TWRP refused to fit on the oldie device I maintain, as you can see from the commit message. Nonetheless, happy to be able to help someone!
[Android] Uchiha_Dev:
why not port the recovery instead of building ? And I have seen some guys reduce the size of TWRP to about 6 MB (fully working)
[Android] MSF Jarvis:
I'm one of those guys. Only that mine is 5 MB ;) and I like the feel of "Official TWRP Maintainer for HTC Pico", that's why I build it. Going to get this current device officially supported as well. When I have time.
[Android] Uchiha_Dev:
Whoa man, that's insane. Must be hours of researching different compression and fixing issues

---------- Post added at 05:40 PM ---------- Previous post was at 05:39 PM ----------

Also can I use your commits to decrease the size of TWRP that I will build as well ?
[Android] MSF Jarvis:
What was more ****ed up is that I was at Dad's laptop, so had to keep bugging Dees_Troy for fresh test builds. He too helped me a lot with that, so a :good: to him as well.

---------- Post added at 05:43 PM ---------- Previous post was at 05:42 PM ----------

Of course! They're not some hidden voodoo I did, just a plain defconfig change, anyone could have done it.
[Android] Uchiha_Dev:
thank you, really great job with your work :D I will definitely press the thanks button tomorrow (used all of my thanks today)

---------- Post added at 06:03 PM ---------- Previous post was at 05:51 PM ----------

another question, how do I prevent recovery from being built while compiling a ROM ?
[Android] MSF Jarvis:
No idea, but I'm sure a look through build/core/Makefile will yield positive results.
[Android] Uchiha_Dev:
compile hung at Install : /.../.../.../Email.apk since the past 15+ minutes
[Android] katinatez:
[MENTION=7041450]JonathanRAZ[/MENTION]

If you use bbqlinux, the terminal command is

sudo pacman -S maven

In addition you have enter another command

sudo geany ~/.bashrc

Then add this line at bottom

export JAVA_HOME=/usr/lib/jvm/default

Save, then open new terminal and compile
[Android] DarkFrenzy:
anybody?
[Android] lilferraro:
Build missing files....

Hello Im compiling cm-13 for galaxy tab 3 (lt02ltespr) and have completed 3 builds and none of them boot so I cant get a logcat. I can get it to boot by flashing vendor files from another rom but that is useless in the end. I want to first say that my device is not supported but it is almost identical to 2 other devices (s4mini & galaxy mega) that Ive already ported roms from. Ive also built cm13 kernel working on my device. I finally found out that my vendor files are missing from my latest build and a lot of important stuff, so I was wondering if someone could look at my device repos and see what I need to do to build these files that are missing? Or could I somehow use PRODUCT_COPY_FILES: or use BUILD_PREBUILT instead to add missing .so files from another rom lol? Is that even possible? Thank you in advance

Device-repo

Device-common-repo

Device-common-extra-repo

Edit: LOL Same as post above me...

Proprietary-repo
[Android] Uchiha_Dev:
thanks to [MENTION=6552280]MSF Jarvis[/MENTION] [MENTION=6049586]Arvind7352[/MENTION] finally able to compile AICP lp successfully, the ROM is working perfectly. Except for 1 thing, on first boot the camera shows up and when I open it, it says Unfortunately Camera has stopped, and when I reboot the camera app vanishes but I am able to launch it via lockscreen but it still gives the Unfortunately Camera has stopped. Any solution ?
[Android] Arvind7352:
Tried other App?

Push Google Cam to system, reboot and try opening it....

If it didn't, take a log of it When you open it... (Or when you boot to system and Find the App missing)

Try finding it's solution in Google/post it here itself, maybe someone has already solved it...
[Android] DarkFrenzy:
use open camera app from play store. it works
[Android] Uchiha_Dev:
going to try other apps, will report back in a while with logs

---------- Post added at 05:17 AM ---------- Previous post was at 05:17 AM ----------

I will try, thank you

---------- Post added at 05:24 AM ---------- Previous post was at 05:17 AM ----------

Tried Open camera and I get, Failed to open camera, Camera may be in use by another application
[Android] DarkFrenzy:
then you need to fix the camera libs. if u get fixed plz tell me how u fixed it
[Android] Uchiha_Dev:
I get this in the logcat

E/CameraService( 154): getCameraVendorTagDescriptor: camera hardware module doesn't exist

E/CameraMetadata-JNI( 4297): CameraMetadata_setupGlobalVendorTagDescriptor: Failed to setup vendor tag descriptors, received error No such device (-19)
[Android] JonathanRAZ:
I need some help i get this error

http://pastebin.com/bHi5tcpA
[Android] Uchiha_Dev:
I have completed my AICP build, I need to add a new fix to it, will doing a recompile without make clean add/implement the new fix
[Android] Jeik:
Hey guys.

I am having problems with my PAC 5.1 builds.

I made my build on 31.1.,and it was all fine.

I resynced everything after I saw that the PAC source had been brought up to r34,but everything changed.

The lunch command doesn't show the name of the PAC zip that will be made,and the produced zip has a different name when compared to my 31.1. build.

When it boots,Settings FC,and I can't get past the Setup screen. .--------.

Is anyone experiencing similar issues after the r34 bring-up?
[Android] JonathanRAZ:
No private recovery resources for TARGET_DEVICE nobleltetmo
[Android] KeTuRr74:
You should add this line to your lt02ltexx-common-vendor-blobs.mk file in your vendor/lt02ltexx-common.

vendor/samsung/lt02ltexx (or lte02lte-common/proprietary/lib/thenameofthemissinglib or bin or etc files:system/vendor/lib/thenameofthemisdinglib or bin etc... \

If i need a file in vendor/lib/drm for example i will modify the line to :

vendor/samsung/lt02ltexx or lt02lte-common/vendor/lib/drm/libdrm.so:system/vendor/lib/drm/libdrm.so \

This is only a example. I hope you understood.
[Android] DarkFrenzy:
all the lines are already present but its not working
[Android] MSF Jarvis:
PAC ROM uses its own script rather than standard lunch and brunch, which results into cm-12.1-*.zips since PAC ROM haven't modded the build system.
[Android] Arvind7352:
Get to know which modules/apps are getting reinstalled,

then push only those files to your /system partition. If it worked, then remake a Flashable ROM Zip.

These things are unrelated. Find the Actual error...

This message comes for me too, but it goes on
[Android] Uchiha_Dev:
Sadly nothing seems to fix the camera
[Android] DarkFrenzy:
Me too never fixed camera living without a camera.

Did u compiled the kernel with all the required camera configs?

Dev do u know if I need to define a resolution when building for tablets

Where to define that?

After building Rom from source we get the screen rotate bug and screencast record bug.

Do u have any idea?
[Android] JonathanRAZ:
I think its compiling great it said after some hour or more it said Building kernel i guess is working......i had to install ubuntu reinstall all sources plus maven and some patches as of now its still compiling so lets see thank you and the others for help
[Android] FayaX[PT]:
HelloQ

My rom compiles but does not even enter the boot animation :(

What can I do ?
[Android] JonathanRAZ:
Git init broke my build how to fix :(
[Android] katinatez:
I had the camera Force Close, all the time about a year ago; and it turned out to be the custom toolchain.

I would make a clobber build and clear cache and compile with default toolchains, see if that helps

You define the resolution in device boardconfig.mk

The screen rotation is defined in same place when compiling twrp, but forgot the actual code to place, on the road now.
[Android] JonathanRAZ:
Help please http://pastebin.com/8UGKDvhx
[Android] Uchiha_Dev:
using the default toolchain, tried with custom too, same result
[Android] KeTuRr74:
Your kernel is broken. Use another source.
[Android] xmicroman:
Deleted