yashsingh1/xdaforums huggingface dataset:
[Android] Uchiha_Dev:
this might be a strange question, I am just curious.

Is there are a particular order in which the ROM is compilied like, libs first, then bins etc ?

If yes, can I change the order and make apps compile first ?

---------- Post added at 04:02 PM ---------- Previous post was at 04:00 PM ----------

pro tip : if you want to test the ROM for other things but errors pop up, use a make -i to ignore any build errors and compile the ROM. This might or might not be a relevant answer :p
[Android] SlimShady's:
Did it. Not even passing LG screen[emoji14]

Inviato dal mio LG-D405n utilizzando Tapatalk
[Android] Arvind7352:
Its better not to change the build sequence as the Apps are Dependent on Libs/Bins etc etc....

The main build sequence is at build/core/Makefile (Probably AFAIK)

Keep a track of the changes you're making, otherwise it becomes Unbuildable
[Android] laperry1:
hello everyone!! still learning from this awesome thread!!

i really need some help compiling the following lock screen weather commits in cm-13.0:

https://github.com/ResurrectionRemi...mmit/56a6c2ea80fb894911561f1ea51065275b2f7084

&

https://github.com/ResurrectionRemi...mmit/7fd01b391ad0f1d37e64cefa9d1fff1b59721bb2

&

https://github.com/ResurrectionRemi...mmit/82009d6b514a5fc835c272f0c7f20d8d15618caa

i've managed to get it to compile, but i still don't have ls weather setting... could someone please help?

https://github.com/laperry1/android...mmit/3feadef2a593071503472b5a5265a3b2df89a0a7

https://github.com/laperry1/android_frameworks_base/commit/57ffea94d1602c59ef85e58607a68076793574ff
[Android] FayaX[PT]:
Export includes file: external/sqlite/dist/Android.mk -- out/host/linux-x86/obj/SHARED_LIBRARIES/libsqlite_intermediates/export_includes

Notice file: external/sqlite/dist/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib64/libsqlite.so.txt

Export includes file: external/javasqlite/Android.mk -- out/host/linux-x86/obj/SHARED_LIBRARIES/libsqlite_jni_intermediates/export_includes

Notice file: external/javasqlite/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib64/libsqlite_jni.so.txt

Import includes file: out/host/linux-x86/obj/EXECUTABLES/dtbTool_intermediates/import_includes

make: *** No rule to make target 'out/target/product/bacon/kernel', needed by 'out/target/product/bacon/dt.img'. Stop.

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

Export includes file: device/qcom/common/dtbtool/Android.mk -- out/host/linux-x86/obj/EXECUTABLES/dtbTool_intermediates/export_includes

Note: Some input files use unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

1 warning

#### make failed to build some targets (01:20 (mm:ss)) ####

If someone know how to resolve :D

Thanks!
[Android] akhilnarang:
You have Kernel source synced in kernel/oneplus/msm8974?
[Android] FayaX[PT]:
Yes

(I dont know if matter, but I am trying build CAF AOSP with cyanogen device tree)

EDIT:I think that the problem was the wrong kernel path. I had it on kernel/oneplus/msm8479 and it should be on kernel/

-

---------- Post added at 12:39 AM ---------- Previous post was at 12:38 AM ----------

http://pastebin.com/N32UGip7

Wtf ??I dont see any error -.-
[Android] hdorius:
That error is no target to make kernel,still kernel error
[Android] FayaX[PT]:
Oh :( someone can explain or give a link for a tutorial to bring aosp-caf from cm device tree?
[Android] nimrodsv:
Hi all,

I'm have a build error with a rom that i'm trying to port to Moto X Pure, I think that I found the cause of the issue but don't know how to resolve it.

The error that I got is:

make: *** No rule to make target 'prebuilts/ndk/current/sources/cxx-stl/stlport/libs//libstlport_static.a', needed by '/home/nimrodsv/Android/SS/out/target/product/clark/obj_arm/SHARED_LIBRARIES/libRSSupport_intermediates/LINKED/libRSSupport.so'. Stop.

The red part of the error is : "//" where actually it should be "/arm64-v8a", I can manually fix it by copying the .a file to the incorrect path, but this is not the correct solution and will take me a lot of time to fix (as there are more than one library that have this issue, all of them are related to ndk by the way)

I'm pretty sure that this path can be configured with a condition in the build/core (or any other rom repo) or declaration in the device repo.

Does anyone knows where can I find it?

Thanks!
[Android] KeTuRr74:
You missed a repo .

Add this to your roomservice.xml located in /.repo/local_manifests/roomservice.xml

Do ctrl + h command to see hidden folders.

<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0" />
[Android] sh A ne:
Help with this error
[Android] nimrodsv:
Actually this repo is already included in my local manifest.

It seems to be a configuration issue as I'm trying to build SlimSaber which is not being built for x64 devices yet.
[Android] hahagu:
.. so what do I do now?

---------- Post added at 11:14 PM ---------- Previous post was at 11:14 PM ----------

do u mean the vendor folder in the src?
[Android] Uchiha_Dev:
Any fix for this

make: *** No rule to make target 'system/etc/permissions/android.software.live_wallpaper.xml', needed by 'packages/wallpapers/LivePicker/android.software.live_wallpaper.xml'. Stop.
[Android] jneto3000:
How can I get the vendor files only for d802 on the lge path from TheMuppets? Do I have to download all the files for all the LG devices there?
[Android] neonkat:
fork this.

*this is cm13.0 vendor tree
[Android] laperry1:
the device i'm compiling for is the one plus one... again, any assistance getting this working would be greatly appreciated!
[Android] jneto3000:
This type of error, how to solve it?

...

ERROR: /home/jneto/temasek/packages/providers/ThemesProvider/src/org/cyanogenmod/themes/provider/ThemesOpenHelper.java:538: ThemesColumns cannot be resolved to a variable

...

ERROR: /home/jneto/temasek/packages/providers/ThemesProvider/src/org/cyanogenmod/themes/provider/ThemePackageHelper.java:286: ThemesColumns cannot be resolved to a variable

...

ERROR: /home/jneto/temasek/packages/providers/ThemesProvider/src/org/cyanogenmod/themes/provider/PreviewGenerationService.java:422: ThemesColumns cannot be resolved to a variable

...

ERROR: /home/jneto/temasek/packages/providers/ThemesProvider/src/org/cyanogenmod/themes/provider/util/ProviderUtils.java:240: READ_THEMES cannot be resolved or is not a field

Install: /home/jneto/temasek/out/target/product/d802/system/priv-app/VpnDialogs/VpnDialogs.apk

make: ** [/home/jneto/temasek/out/target/common/obj/APPS/ThemesProvider_intermediates/with-local/classes.dex] Erro 41

make: ** Esperando que outros processos terminem.

make: Saindo do diretório `/home/jneto/temasek'

#### make failed to build some targets (05:20 (mm:ss)) ####
[Android] SlimShady's:
I'm having the same exact problem with Temasek 6.0

Inviato dal mio LG-D405n utilizzando Tapatalk
[Android] KeTuRr74:
cd packages/providers/ThemeProviders

git revert 43532de

This can fix the issue because we all get the same issue with this ThemeProvider.

If this not fix i will ty to search the right commit who made those errors
[Android] jneto3000:
Lots of:

"warning: string: 'X' has no default translation."

... "is missing X required localizations: ..."
[Android] Arvind7352:
You can ignore that [emoji6]
[Android] MJPollard:
Ignore them, they're just warnings. If I'm not mistaken, those warnings simply mean that there are no definitions for one or more of the English strings in values/strings.xml in the various values-XXX folders. The ROM works just fine without them; it simply defaults to the English strings.
[Android] jneto3000:
Thanks. But how can I ignore it?

Would the following work?

"add the lines in your /res/values.xml file in resource root tab like this:

<resources
xmlns:tools="http://schemas.android.com/tools"
tools:locale="en" tools:ignore="MissingTranslation">

... "
[Android] FayaX[PT]:
Notice file: packages/apps/Camera2/jni/NOTICE -- /home/fayax/android/aosp-caf/out/target/product/bacon/obj/NOTICE_FILES/src//system/lib/libjni_jpegutil.so.txt

Notice file: packages/apps/CertInstaller/NOTICE -- /home/fayax/android/aosp-caf/out/target/product/bacon/obj/NOTICE_FILES/src//system/app/CertInstaller/CertInstaller.apk.txt

make: *** No rule to make target '/home/fayax/android/aosp-caf/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.internal_intermediates/classes.jack', needed by '/home/fayax/android/aosp-caf/out/target/common/obj/APPS/ConfigPanel_intermediates/with-local/classes.dex'. Stop.

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

anyone can help, pls ?

Thanks
[Android] Arvind7352:
All the ROMs' apps give you this issue (not a big problem)

I have tested those apps too

Btw, I don't know much about that workaround you can try that on one of those Apps (I suggest you to ignore that and move on, it's okay)
[Android] jneto3000:
But after those errors it says: #### make failed to build some targets (07:31 (mm:ss)) ####

How can I move on? If I brunch again, won't the errors repeat?
[Android] MJPollard:
You don't need to do anything, because it doesn't affect the building of the ROM. In this case, "ignore it" doesn't mean "change something so that it doesn't show up," it means "don't pay any attention to it when you see it on your screen because it's no big deal." If Google and CyanogenMod took the time to eliminate each and every unimportant warning that comes up in the code, we'd never see a new release of Android ever again. :D
[Android] Arvind7352:
Hmm, totally unrelated...(For sure)

Show the entire or at least the error part
[Android] MJPollard:
Those aren't related to the translation warnings you're seeing. Something else must be up for the build to abort like that.
[Android] Arvind7352:
Sync these projects

Main :- CMSDK Vendor, sync at vendor/cmsdk

Dependency of [Main] :- CM Vendor, sync at vendor/cm

If you face any errors related to 'org.cyanogenmod.sdk' && you're not building a CM Based ROM, then

[Wait for it -- Posting]

Edit:

In Android.mk of vendor/cmsdk [MENTION=6938033]FayaX[PT][/MENTION]

Delete all lines after line number 99 (which shows "#the sdk") and things will be okay

Why? Because CM SDK API Is not needed for non-CM based ROMs (org.cyanogenmod.platform.sdk)
[Android] FayaX[PT]:
Thanks for your help man!!

Delete lines in which file ? :D
[Android] jneto3000:
Terminal was only showing 512 lines, so the make fails right after the errors with translation.

Putting to unlimited rollback and brunch again...

I see I'm still having java problems with theme, but now with path /packages/apps/ThemeChooser/

"...

Building with Jack: /home/jneto/temasek/out/target/common/obj/APPS/ThemeChooser_intermediates/with-local/classes.dex

ERROR: /home/jneto/temasek/packages/apps/ThemeChooser/src/org/cyanogenmod/theme/util/ThemedTypefaceHelper.java:25: The import org.cyanogenmod.internal.util.ThemeUtils cannot be resolved

ERROR: /home/jneto/temasek/packages/apps/ThemeChooser/src/org/cyanogenmod/theme/util/ThemedTypefaceHelper.java:73: ThemeUtils cannot be resolved to a variable

...

ERROR: /home/jneto/temasek/packages/apps/ThemeChooser/src/org/cyanogenmod/theme/chooser/AppReceiver.java:32: ACTION_THEME_INSTALLED cannot be resolved or is not a field

...

ERROR: /home/jneto/temasek/packages/apps/ThemeChooser/src/org/cyanogenmod/theme/chooser/ChooserDetailFragment.java:76: ThemeChangeListener cannot be resolved to a type

...

ERROR: /home/jneto/temasek/packages/apps/ThemeChooser/src/org/cyanogenmod/theme/chooser/ChooserDetailFragment.java:199: The method getThemeChangeRequestForSelectedComponents() from the type ChooserDetailFragment refers to the missing type ThemeChangeRequest

...

ERROR: /home/jneto/temasek/packages/apps/ThemeChooser/src/org/cyanogenmod/theme/chooser/ChooserDetailFragment.java:561: The method onProgress(int) of type ChooserDetailFragment must override or implement a supertype method

...

ERROR: /home/jneto/temasek/packages/apps/ThemeChooser/src/org/cyanogenmod/theme/chooser/ChooserDetailFragment.java:688: ThemesColumns cannot be resolved to a variable

make: ** [/home/jneto/temasek/out/target/common/obj/APPS/ThemeChooser_intermediates/with-local/classes.dex] Erro 41

make: ** Esperando que outros processos terminem.

...

Errors with string translations

...

warning: no entries written for string/notifications_off_title (0x7f0a02de)

warning: no entries written for string/notifications_off_text (0x7f0a02df)

make: leaving directory `/home/jneto/temasek'

#### make failed to build some targets (06:22 (mm:ss)) ####

"

EDIT: I did what [MENTION=5305791]KeTuRr74[/MENTION] said on my previous theme problems, on post #2702

Maybe I should do something equal to ThemeChooser path?
[Android] FayaX[PT]:
I am getting this error now:

make: *** No rule to make target '/.txt', needed by '/home/fayax/android/aosp-caf/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.

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

logtags: /home/fayax/android/aosp-caf/out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/src/src/java/com/android/internal/telephony/EventLogTags.java <= frameworks/opt/telephony/src/java/com/android/internal/telephony/EventLogTags.logtags
[Android] dkonect:
Hello great guide but for people who's need quickly ubuntu, it's so more really easy with a usb stick and the soft lily usb creator
[Android] MJPollard:
Warnings, not errors. Errors immediately stop the build, while warnings allow the build to continue. That's something you absolutely need to keep in mind, even though it sounds strange. ;)

The thing with building Android is, errors that occur during compilation aren't always caused by the lines immediately preceding the error message (I believe this is because compiling is done in multiple threads, where the results of successful threads can show up after the error until the compilation finally stops). You usually have to scroll up to find the offending line(s), which generally have "ERROR" somewhere in them. That tripped me up, too, when I first started building Android ROMs, as I'm use to compiling under Windows, where an error message will have the offending code displayed right above it.

One way that I think you could track errors down would be to compile with make bacon -j1 (use whatever is needed for your ROM in place of "bacon," which is what CyanogenMod uses) instead of running the brunch command (brunch is a complicated script thing; it eventually calls make, so you'd just be "cutting to the chase" by running make by itself). That would limit compiling to a single thread, and should display the actual error(s) immediately before it stops.
[Android] Arvind7352:
I faced the same here LOL (live Example)

make: *** No rule to make target `prebuilts/cmsdk/api/.txt', needed by `/home/arvind/tipsym/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
make: *** Waiting for unfinished jobs....
logtags: /home/arvind/tipsym/out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/src/src/java/com/android/internal/telephony/EventLogTags.java <= frameworks/opt/telephony/src/java/com/android/internal/telephony/EventLogTags.logtags
make: Leaving directory `/home/arvind/tipsym'

We're missing a Source (Prebuilt CMSDK)

try this (i'm trying it now)

clone THIS at prebuilts/cmsdk

and continue the build

UPDATE: IT worked! now CMSDK is prebuilt!
[Android] FayaX[PT]:
Are you trying use cm tree to build aosp ? :D

EDIT:

[MENTION=6049586]Arvind7352[/MENTION]

I did that and the error is there :(
[Android] Arvind7352:
That's a AOSPB Based ROM...

This is my first attempt for 6.0.1
[Android] Arvind7352:
Why are you using CM Vendor and CMSDK for?? [MENTION=6938033]FayaX[PT][/MENTION]

For CM Hardware Framework?

CMSDK API only works on CM(or CM based) ROMs if you're thinking about that
[Android] Uchiha_Dev:
well, could someone tell me which repos I need to patch to update from r26 to the latest r34 ?

answer is : almost everything, dang it this is a pain
[Android] KeTuRr74:
In your default.xml change at the first remote line, change r26 to r34, save and repo sync
[Android] DarkFrenzy:
I have build bliss 6.1 and it doesn't boot. And the culprit is vendor folder if I use vendor folder from a similar device than it boots but after finishing optimizing apps welcome to bliss then suddenly use logo comes and give a bootloop.

How can I fix the vendor?
[Android] KeTuRr74:
Take a logcat, if needed contact me i can help you for Bliss as a maintainer.
[Android] DarkFrenzy:
i did a search on the error i get in adb log and found a similar log here

https://gist.github.com/spezi77/b36768286c2bc9415699

and here is a little logs

12-18 17:44:42.906 3256 3256 I SystemServer: Package Manager
12-18 17:44:42.906 3256 3292 I DisplayManagerService: Display device changed s
tate: "Built-in Screen", ON
12-18 17:44:42.933 3256 3256 W SystemConfig: No directory /system/etc/sysconfi
g, skipping
12-18 17:44:42.991 3256 3256 D SELinuxMMAC: Using policy file /system/etc/secu
rity/mac_permissions.xml
12-18 17:44:43.194 3256 3256 E art : DexFile_getDexOptNeeded file '/system
/framework/org.apache.http.legacy.jar' does not exist
12-18 17:44:43.194 3256 3256 W PackageManager: Library not found: /system/fram
ework/org.apache.http.legacy.jar
12-18 17:44:43.236 3256 3256 D PackageManager: No files in app dir /vendor/ove
rlay
12-18 17:44:43.547 3317 3317 W linker : /system/lib/libmmjpeg.so has text rel
ocations. This is wasting memory and prevents security hardening. Please fix.
12-18 17:44:43.550 3317 3317 E mm-camera: qcamsvr_start: old_mode = 3f
12-18 17:44:43.619 184 184 W auditd : type=1325 audit(0.0:1036): table=nat
family=2 entries=11
[Android] Uchiha_Dev:
In default.xml in most lines the remote, revision etc is not mentioned. For example

<project path="frameworks/minikin" name="CyanogenMod/android_frameworks_minikin" remote="cm" revision="cm-12.1" groups="pdk-cw-fs" />

In this line ^ : I know that it is syncing and pulling the files from github.com/CyanogenMod/android_frameworks_minikin

<project path="frameworks/compile/libbcc" name="platform/frameworks/compile/libbcc" groups="pdk" />

the above line ^ : I don't know from which location it is pulling/syncing the above file from

I hope I am making sense, please help

---------- Post added at 06:45 AM ---------- Previous post was at 06:43 AM ----------

is that all I have to do ? I asked this question before to and some said that it is hard and a lot has to be changed. And if just changing the tag is enough why don't roms like rr remix, octos etc update their sources to the latest version ?
[Android] Arvind7352:
These Projects may (probably) be common for all recent revisions of Android -- Default Revision 'Origin' or 'Master'

If you don't see the remote then its Fetching from the GoogleGit - which maintains Pure Android Source Code
[Android] Uchiha_Dev:
so it's pulling/syncing them from https://android.googlesource.com/ ?

ohh yeah I get it now, anything that has platform at first is being pulled from google aosp (after comparing few lines I noticed it)
[Android] Arvind7352:
Yep, you're correct....

ROM maintainers not only update the source code but also fix their own additions to the ROM, so they require some time to do it. If it was AOSP, then you can directly update it :)
[Android] Uchiha_Dev:
I am syncing AICP lp5.1 and the sync always cancels at about 95-97% and stats again from 87% :/ It has happened about 20 times since yesterday

Fetching project CyanogenMod/android_hardware_qcom_audio

Fetching project CyanogenMod/android_hardware_qcom_audioB/s

error: RPC failed; result=56, HTTP code = 200 | 23.00 KiB/s

fatal: The remote end hung up unexpectedly

fatal: early EOF

fatal: index-pack failed

remote: Counting objects: 196, done

remote: Finding sources: 100% (664/664)
[Android] FayaX[PT]:
[MENTION=6534512]Uchiha_Dev[/MENTION]

Maybe you can try delete the project with problems and try again.
[Android] Uchiha_Dev:
you mean to say delete everything and restart ? or delete the project folder ?
[Android] Arvind7352:
Delete the Project folder at /.repo/project-objects and its corresponding extracted files under /.repo/projects

[MENTION=6534512]Uchiha_Dev[/MENTION] - Yes you have to
[Android] Uchiha_Dev:
delete the folder causing issues and repo sync again ?
[Android] MSF Jarvis:
Yes
[Android] Adromir:
As far as I know the 5.1.1 branch (correct me if I am wrong) isn't maintained anymore, so there won't be any changes in the source, so you could download it as zip file, so you don't have to resync it in the future if something goes wrong
[Android] Uchiha_Dev:
there is no .bashrc in any of my ROM sources, what do I do ?
[Android] Arvind7352:
.bashrc is in your /home folder

Edit with Higher Permissions

sudo nano ~/.bashrc

(to edit it with Root Permissions and Nano)

After doing your edits

source .bashrc (when at Home Directory)

This will Make Bash perform those changes

In my Understanding

(*) Nano is a Command-line powered Text Editor

(*) The Bash Takes a note of the Contents inside this file before starting up

(*) .bashrc is similar to the 'rc' files In the root directory.... The System performs all things requested by all *.RC files before entering System BootAnim
[Android] Uchiha_Dev:
trying to compile AICP and I get this error

ls: cannot access vendor/aicp/products/XXXXX.mk: No such file or directory

build/core/product_config.mk:231: *** Can not locate config makefile for product "aicp_XXXXX". Stop.

Device XXXXX not found. Attempting to retrieve device repository from AICP Github (http://github.com/AICP).
[Android] FayaX[PT]:
Maybe wrong names

Edit:
[MENTION=6534512]Uchiha_Dev[/MENTION]

See this post: http://xdaforums.com/showpost.php?p=54118852&postcount=9
[Android] Uchiha_Dev:
I edited my device tree, changed cm.mk to aicp.mk, changed vendor path to vendor/aicp/config, and also changed cm_xxx to aicp_xxx in aicp.mk (formerly cm.mk)
[Android] FayaX[PT]:
For which device are you trying to build?

Edit: [MENTION=6534512]Uchiha_Dev[/MENTION]

Try placing aicp.mk (cm.MK) in vendor/products
[Android] Uchiha_Dev:
did not work, I have done this in the past too with 2-3 ROMs and I have been successful I don't know WTF is wrong with AICP
[Android] Arvind7352:
Don't make excessive posts, share your Device's Git repo

And your edited [DeviceName].mk
[Android] Uchiha_Dev:
I do not have a git for my vendor and device
[Android] MSF Jarvis:
Then make one. It helps a lot, trust me.
[Android] Uchiha_Dev:
for now can you help me with the issue I am facing with AICP :/
[Android] Arvind7352:
Probably you have forgot this thing

Do these things

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

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

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

Each ROM has its own way of Adding a Device
[Android] akhilnarang:
Aicp needs a vendor/aicp/products/codename.mk
[Android] Uchiha_Dev:
yup, did it already
[Android] Arvind7352:
Check it...

Mainly those Make files involved in my guide

Added the Call for Device Make file?
[Android] Uchiha_Dev:
deleted
[Android] Uchiha_Dev:
Finally managed to start the compile :D

I am not able to clone this repo, this is the one giving me errors while syncing AICP, removed it from default.xml but it seems it is important for compiling. Even manually syncing it (cloning) it gives the same error

git clone https://android.googlesource.com/platform/prebuilts/qemu-kernel

Cloning into 'qemu-kernel'...

remote: Sending approximately 3.54 GiB ...

remote: Counting objects: 197, done

remote: Finding sources: 100% (197/197)

error: RPC failed; result=56, HTTP code = 200| 111.00 KiB/s

fatal: The remote end hung up unexpectedly

fatal: early EOF

fatal: index-pack failed

what do I do ?

Fixed : Got it from my previous ROM sources
[Android] Arvind7352:
Download the Qemu-Kernel manually

Select tgz option while browsing the source

And manually paste content in prebuilts/qemu-kernel

I always face this error, so I manually download it

Updated one is preferred, don't always pick up from old ones.

---------- Post added at 10:18 AM ---------- Previous post was at 09:58 AM ----------

Do this

mka libaudiopolicymanagerdefault OR mmm -B frameworks/av/services/audiopolicy (try this first, coz i'm unsure about the lib name)

now continue the build..
[Android] Uchiha_Dev:
Yeah I got it from my previous ROM sources, all is well compiling now