[Q] Problem with Android-ViewPagerIndicator - Android Q&A, Help & Troubleshooting

Hi, I try to import and this Library in Eclipse:
https://github.com/JakeWharton/Android-ViewPagerIndicator
But there is a problem with the Maven installer because
he cannot resolve all the Depencies. From the "issue" tab
on github I got the info that I have update the depencies
from r4 to r6 in the pom.xml of the project. I tried this
but everytime I try to install the Library with "mvn install"
I get the following error:
Code:
c:\JakeWharton-Android-ViewPagerIndicator-3db7585>mvn install
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
com.viewpagerindicator:library:apklib:2.2.0
[WARNING] 'build.plugins.plugin.version' for com.jayway.maven.plugins.android.ge
neration2:maven-android-plugin is missing. @ line 36, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
com.viewpagerindicator:sample:apk:2.2.0
[WARNING] 'build.plugins.plugin.version' for com.jayway.maven.plugins.android.ge
neration2:maven-android-plugin is missing. @ line 48, column 12
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten t
he stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support buildin
g such malformed projects.
[WARNING]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Android-ViewPagerIndicator (Parent)
[INFO] Android-ViewPagerIndicator
[INFO] Android-ViewPagerIndicator Sample
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Android-ViewPagerIndicator (Parent) 2.2.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ parent ---
[INFO] Installing c:\JakeWharton-Android-ViewPagerIndicator-3db7585\pom.xml to C
:\Users\Cracksoldier\.m2\repository\com\viewpagerindicator\parent\2.2.0\parent-2
.2.0.pom
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Android-ViewPagerIndicator 2.2.0
[INFO] ------------------------------------------------------------------------
Downloading: http://r.jakewharton.com/maven/release/android/support/compatibilit
y-v4/r4/compatibility-v4-r4.pom
Downloading: http://repo1.maven.org/maven2/android/support/compatibility-v4/r4/c
ompatibility-v4-r4.pom
[WARNING] The POM for android.support:compatibility-v4:jar:r4 is missing, no dep
endency information available
Downloading: http://r.jakewharton.com/maven/release/android/support/compatibilit
y-v4/r4/compatibility-v4-r4.jar
Downloading: http://repo1.maven.org/maven2/android/support/compatibility-v4/r4/c
ompatibility-v4-r4.jar
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Android-ViewPagerIndicator (Parent) ............... SUCCESS [0.204s]
[INFO] Android-ViewPagerIndicator ........................ FAILURE [1.636s]
[INFO] Android-ViewPagerIndicator Sample ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.953s
[INFO] Finished at: Thu Dec 22 18:29:20 CET 2011
[INFO] Final Memory: 10M/108M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project library: Could not resolve dependencie
s for project com.viewpagerindicator:library:apklib:2.2.0: Could not find artifa
ct android.support:compatibility-v4:jar:r4 in com.jakewharton (http://r.jakewhar
ton.com/maven/release) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso
lutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :library
c:\JakeWharton-Android-ViewPagerIndicator-3db7585>
I am new to Maven and I cant get it working. I also tried to import
it as a normal Android Project and then assing the library to the
sample project but then I get 1053 error(s).
I changed the depencies in the pom.xml files so that it looks
likes this:
Code:
android.support
compatibility-v6
${android.support.version}
I also tried:
compatibility-r6
compatibility-v4-r6
and I also tried to change this:
Code:
r4
to this:
Code:
r6
But nothing worked.
I hope anybody can help me because I am desperated right now
I tried everything in the last 2 days.
Edit:// Problem is solved
Best Regards

Related

VanirAOSP compile fails at some api stuff

I'm getting this error when I try to compile VanirAOSP
Code:
/home/lozohcum/Vanir/out/target/common/obj/PACKAGING/public_api.txt:44533: warning 21: Method java.util.zip.ZipFile.ZipFile no longer throws exception java.util.zip.ZipException
/home/lozohcum/Vanir/out/target/common/obj/PACKAGING/public_api.txt:13415: error 13: Method android.media.audiofx.LoudnessEnhancer.getTargetGain has added 'final' qualifier
/home/lozohcum/Vanir/out/target/common/obj/PACKAGING/public_api.txt:13416: error 13: Method android.media.audiofx.LoudnessEnhancer.setTargetGain has added 'final' qualifier
prebuilts/sdk/api/19.txt:25: error 10: Removed field android.Manifest.permission.BIND_NFC_SERVICE
prebuilts/sdk/api/19.txt:13231: error 10: Removed field android.media.audiofx.AudioEffect.EFFECT_TYPE_LOUDNESS_ENHANCER
prebuilts/sdk/api/19.txt:13389: error 9: Removed public constructor LoudnessEnhancer(int)
******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.
******************************
make: *** [/home/lozohcum/Vanir/out/target/common/obj/PACKAGING/checkapi-last-timestamp] Error 38
I can compile AOSP 4.4.4 and CM11 4.4.4 with no errors, only Vanir fails. Doesn anyone know how can I overcome this?

[discussion/help] building miui 8 for oneplus x (patchrom project)

HI OnePlus X users, I know there are some thread about the same..but they are almost dead and the OP of that threads are busy in some other project like AOSP N (7.0),CM 14 ect..so i took an initiative to work on MIUI 8 (6.0.1).and working on it from last few days.
there is a build from a chinese dev shumxin which is out a day before.you can find that thread here
http://forum.xda-developers.com/oneplus-x/general/rom-miui-8-oneplus-x-ported-shumxin-t3479012
So come to the point I started working on MIUI patchrom project and took a oxygenOS 3.1.3 as base so started here
first command for building and results
HTML:
PATCHROM_BRANCH = marshmallow
ANDROID_PLATFORM = 23
PORT_ROOT = /home/faa/patchrom
ANDROID_TOP =
ANDROID_OUT =
PORT_PRODUCT = Unknown
USE_ANDROID_OUT =
ANDROID_BRANCH =
HOST_OS = linux
After that command for patching OxygenOS 3.1.3 framework to work with MIUI 8
HTML:
[email protected] ~/patchrom/onyx $ make firstpatch
/home/faa/patchrom/tools/patch_miui_framework.sh /home/faa/patchrom/android/base-framework /home/faa/patchrom/android `pwd`
<<< create temp directory to store the old, new source and destination smali code with .line removed
<<< compute the difference between /home/faa/patchrom/onyx/temp/old_smali/framework.jar.out and /home/faa/patchrom/onyx/temp/new_smali/framework.jar.out
<<< apply the patch into the /home/faa/patchrom/onyx/framework.jar.out
patching file /home/faa/patchrom/onyx/framework.jar.out/./smali/android/content/pm/PackageParser.smali
Hunk #1 succeeded at 9781 (offset 121 lines).
Hunk #2 succeeded at 9793 (offset 121 lines).
patching file /home/faa/patchrom/onyx/framework.jar.out/./smali/android/content/res/Resources.smali
Hunk #3 succeeded at 4580 (offset 53 lines).
patching file /home/faa/patchrom/onyx/framework.jar.out/./smali/android/app/ResourcesManager.smali
Hunk #1 FAILED at 213.
Hunk #2 succeeded at 1908 (offset 922 lines).
1 out of 2 hunks FAILED -- saving rejects to file /home/faa/patchrom/onyx/temp/reject/framework.jar.out/./smali/android/app/ResourcesManager.smali.rej
patching file /home/faa/patchrom/onyx/framework.jar.out/./smali/android/app/SystemServiceRegistry.smali
patching file /home/faa/patchrom/onyx/framework.jar.out/./smali/android/graphics/Bitmap.smali
patching file /home/faa/patchrom/onyx/framework.jar.out/./smali/com/android/internal/os/ZygoteInit.smali
Hunk #1 FAILED at 347.
patch: **** Can't reopen file /home/faa/patchrom/onyx/framework.jar.out/./smali/com/android/internal/os/ZygoteInit.smali : No such file or directory
<<< compute the difference between /home/faa/patchrom/onyx/temp/old_smali/services.jar.out and /home/faa/patchrom/onyx/temp/new_smali/services.jar.out
<<< apply the patch into the /home/faa/patchrom/onyx/services.jar.out
patching file /home/faa/patchrom/onyx/services.jar.out/./smali/com/android/server/wm/WindowManagerService.smali
Hunk #1 FAILED at 708.
1 out of 1 hunk FAILED -- saving rejects to file /home/faa/patchrom/onyx/temp/reject/services.jar.out/./smali/com/android/server/wm/WindowManagerService.smali.rej
patching file /home/faa/patchrom/onyx/services.jar.out/./smali/com/android/server/am/ActivityStack.smali
Hunk #1 FAILED at 6636.
1 out of 1 hunk FAILED -- saving rejects to file /home/faa/patchrom/onyx/temp/reject/services.jar.out/./smali/com/android/server/am/ActivityStack.smali.rej
patching file /home/faa/patchrom/onyx/services.jar.out/./smali/com/android/server/am/ActivityManagerService.smali
Hunk #1 succeeded at 94288 with fuzz 1 (offset 11309 lines).
patching file /home/faa/patchrom/onyx/services.jar.out/./smali/com/android/server/SystemServer.smali
Hunk #1 succeeded at 197 (offset 55 lines).
patching file /home/faa/patchrom/onyx/services.jar.out/./smali/com/android/server/policy/PhoneWindowManager.smali
Hunk #1 succeeded at 484 (offset 21 lines).
<<< compute the difference between /home/faa/patchrom/onyx/temp/old_smali/telephony-common.jar.out and /home/faa/patchrom/onyx/temp/new_smali/telephony-common.jar.out
<<< apply the patch into the /home/faa/patchrom/onyx/telephony-common.jar.out
<<< compute the difference between /home/faa/patchrom/onyx/temp/old_smali/wifi-service.jar.out and /home/faa/patchrom/onyx/temp/new_smali/wifi-service.jar.out
mv: cannot stat '/home/faa/patchrom/onyx/wifi-service.jar.out': No such file or directory
cp: cannot stat '/home/faa/patchrom/onyx/temp/dst_smali_orig/wifi-service.jar.out': No such file or directory
<<< apply the patch into the /home/faa/patchrom/onyx/wifi-service.jar.out
cp: cannot stat '/home/faa/patchrom/onyx/wifi-service.jar.out': No such file or directory
/home/faa/patchrom/tools/patch_miui_framework.sh: line 69: cd: /home/faa/patchrom/onyx/temp/dst_smali_orig/wifi-service.jar.out: No such file or directory
>>> patch miui into target framework is done. Please look at /home/faa/patchrom/onyx/temp/reject to resolve any conflicts!
After that got very few rejects(about 3-5) in temp/reject folder which I fixed(may be not) by following this thread
http://forum.xda-developers.com/chef-central/android/guide-patchrom-rejects-fixing-tutorial-t3203287
AFTER APPLYING PATCH GAVE A COMMAND TO MAKE FLASHABLE ZIP and MIpatchtool started to copy resources in Base rom i.e OxygenOS.zip
HTML:
make fullota
and got this
HTML:
[email protected] ~/patchrom/onyx $ make fullota
unzip >/dev/null -n oxygenOS.zip -d oxygenOS
unzip >/dev/null oxygenOS.zip -d out/ZIP
To add prebuilt files
cp: cannot stat 'oxygenOS/system/bin/app_process64': No such file or directory
/home/faa/patchrom/build/prebuilt.mk:6: recipe for target 'add-prebuilt-files' failed
make: [add-prebuilt-files] Error 1 (ignored)
mv: cannot stat 'out/ZIP/system/bin/app_process64_miui': No such file or directory
/home/faa/patchrom/build/prebuilt.mk:6: recipe for target 'add-prebuilt-files' failed
make: [add-prebuilt-files] Error 1 (ignored)
To add preintall files
Add miui prebuilt completed!
/home/faa/patchrom/tools/apktool --quiet d -f oxygenOS/system/framework/framework-res.apk -o out/framework-res
/home/faa/patchrom/tools/linux-x86/aapt p -f -x --auto-add-overlay --wlan-replace Wi-Fi --wlan-replace WiFi \
--min-sdk-version 23 --target-sdk-version 23 \
-S /home/faa/patchrom/miui/src/config-overlay/v6/platform/v23/frameworks/base/core/res/res -S /home/faa/patchrom/miui/src/config-overlay/v6/platform/v21/frameworks/base/core/res/res -S /home/faa/patchrom/miui/src/config-overlay/v6/common/frameworks/base/core/res/res -S /home/faa/patchrom/miui/src/I18N_res/v6/common/frameworks/base/core/res/res \
-S out/framework-res/res -A out/framework-res/assets \
-M out/framework-res/AndroidManifest.xml -F out/framework-res.apk
GOT WARNINGS AS FOLLOWS (SHORTEN)
warning: string 'transient_navigation_confirmation_long' has no default translation.
warning: string 'usb_choose_notification_title' has no default translation.
warning: string 'use_physical_keyboard' has no default translation.
warning: string 'wifi_display_notification_connected_message' has no default translation.
warning: string 'wifi_display_notification_connected_title' has no default translation.
warning: string 'wifi_display_notification_connecting_message' has no default translation.
warning: string 'wifi_display_notification_connecting_title' has no default translation.
warning: string 'wifi_display_notification_disconnect' has no default translation.
warning: string 'year_picker_description' has no default translation.
#@echo "9Patch png fix out/framework-res.apk..."
#/home/faa/patchrom/tools/fix_9patch_png.sh >/dev/null framework-res oxygenOS/system/framework out
/home/faa/patchrom/tools/apktool --quiet if -p out/apktool out/framework-res.apk
<<< build out/framework-res.apk completed!
Copy: out/framework-res.apk to out/ZIP/system/framework/framework-res.apk
>>> Install framework resources for apktool...
/home/faa/patchrom/tools/apktool --quiet if -p out/apktool /home/faa/patchrom/miui/system/framework-res/XXHDPI/framework-res.apk -t miui
install /home/faa/patchrom/miui/system/app/XXHDPI/miui/miui.apk
install /home/faa/patchrom/miui/system/framework-res/XXHDPI/framework-ext-res/framework-ext-res.apk
install /home/faa/patchrom/miui/system/app/XXHDPI/miuisystem/miuisystem.apk
/home/faa/patchrom/tools/linux-x86/aapt p -f -u --package-id 0x11 --rename-manifest-package com.miui.rom --auto-add-overlay -z --wlan-replace Wi-Fi --wlan-replace WiFi \
REMAINING CODES (HORTEN)
HTML:
--min-sdk-version 23 --target-sdk-version 23 \
-S /home/faa/patchrom/miui/src/I18N_res/v6/common/miui/frameworks/base/core/res/res -S /home/faa/patchrom/miui/src/frameworks/base/core/res/res -S /home/faa/patchrom/miui/src/frameworks/opt/ToggleManager/res -M /home/faa/patchrom/miui/src/frameworks/base/core/res/AndroidManifest.xml \
-I out/apktool/1.apk -I out/apktool/16.apk -I /home/faa/patchrom/build/empty-res/17.apk -F out/framework-ext-res.apk
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-xhdpi/auto_disable_screenbuttons_float_bg_p.9.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-hdpi/boot_logo.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-xhdpi/boot_logo.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-xxhdpi/boot_logo.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-hdpi/boot_progress.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-hdpi/float_notification_button_bg_n.9.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
AND FINALLY
HTML:
/home/faa/patchrom/tools/apktool --quiet b out/framework -o out/framework.jar
out/framework/smali/android/view/Window.smali[101,0] The file must contain a .class directive
out/framework/smali/android/view/ThreadedRenderer.smali[3,0] The file must contain a .class directive
Exception in thread "main" brut.androlib.AndrolibException: java.util.concurrent.ExecutionException: brut.androlib.AndrolibException: Could not smali file: android/view/Window.smali
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:129)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:69)
at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:376)
at brut.androlib.Androlib.buildSources(Androlib.java:335)
at brut.androlib.Androlib.build(Androlib.java:292)
at brut.androlib.Androlib.build(Androlib.java:268)
at brut.apktool.Main.cmdBuild(Main.java:224)
at brut.apktool.Main.main(Main.java:84)
Caused by: java.util.concurrent.ExecutionException: brut.androlib.AndrolibException: Could not smali file: android/view/Window.smali
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:124)
... 7 more
Caused by: brut.androlib.AndrolibException: Could not smali file: android/view/Window.smali
at brut.androlib.src.SmaliBuilder.buildFile(SmaliBuilder.java:142)
at brut.androlib.src.SmaliBuilder.access$000(SmaliBuilder.java:64)
at brut.androlib.src.SmaliBuilder$1.call(SmaliBuilder.java:98)
at brut.androlib.src.SmaliBuilder$1.call(SmaliBuilder.java:94)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
out/framework/smali/android/view/View.smali[2,0] The file must contain a .class directive
out/framework/smali/android/view/WindowManagerPolicy.smali[3,0] The file must contain a .class directive
out/framework/smali/android/view/MotionEvent.smali[24,0] The file must contain a .class directive
out/framework/smali/android/view/Surface.smali[14,0] The file must contain a .class directive
out/framework/smali/android/view/WindowManager$LayoutParams.smali[2,0] The file must contain a .class directive
out/framework/smali/android/view/SurfaceControl.smali[31,0] The file must contain a .class directive
out/framework/smali/com/android/internal/os/RuntimeInit.smali[576,0] The file must contain a .class directive
out/framework/smali/com/android/internal/os/Zygote.smali[3,0] The file must contain a .class directive
farooque7508 said:
REMAINING CODES (HORTEN)
--min-sdk-version 23 --target-sdk-version 23 \ -S /home/faa/patchrom/miui/src/I18N_res/v6/common/miui/frameworks/base/core/res/res -S /home/faa/patchrom/miui/src/frameworks/base/core/res/res -S /home/faa/patchrom/miui/src/frameworks/opt/ToggleManager/res -M /home/faa/patchrom/miui/src/frameworks/base/core/res/AndroidManifest.xml \ -I out/apktool/1.apk -I out/apktool/16.apk -I /home/faa/patchrom/build/empty-res/17.apk -F out/framework-ext-res.apk/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-xhdpi/auto_disable_screenbuttons_float_bg_p.9.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-hdpi/boot_logo.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-xhdpi/boot_logo.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-xxhdpi/boot_logo.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-hdpi/boot_progress.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-hdpi/float_notification_button_bg_n.9.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
AND FINALLY
/home/faa/patchrom/tools/apktool --quiet b out/framework -o out/framework.jarout/framework/smali/android/view/Window.smali[101,0] The file must contain a .class directiveout/framework/smali/android/view/ThreadedRenderer.smali[3,0] The file must contain a .class directiveException in thread "main" brut.androlib.AndrolibException: java.util.concurrent.ExecutionException: brut.androlib.AndrolibException: Could not smali file: android/view/Window.smali at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:129) at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:69) at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:376) at brut.androlib.Androlib.buildSources(Androlib.java:335) at brut.androlib.Androlib.build(Androlib.java:292) at brut.androlib.Androlib.build(Androlib.java:268) at brut.apktool.Main.cmdBuild(Main.java:224) at brut.apktool.Main.main(Main.java:84)Caused by: java.util.concurrent.ExecutionException: brut.androlib.AndrolibException: Could not smali file: android/view/Window.smali at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:124) ... 7 moreCaused by: brut.androlib.AndrolibException: Could not smali file: android/view/Window.smali at brut.androlib.src.SmaliBuilder.buildFile(SmaliBuilder.java:142) at brut.androlib.src.SmaliBuilder.access$000(SmaliBuilder.java:64) at brut.androlib.src.SmaliBuilder$1.call(SmaliBuilder.java:98) at brut.androlib.src.SmaliBuilder$1.call(SmaliBuilder.java:94) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)out/framework/smali/android/view/View.smali[2,0] The file must contain a .class directiveout/framework/smali/android/view/WindowManagerPolicy.smali[3,0] The file must contain a .class directiveout/framework/smali/android/view/MotionEvent.smali[24,0] The file must contain a .class directiveout/framework/smali/android/view/Surface.smali[14,0] The file must contain a .class directiveout/framework/smali/android/view/WindowManager$LayoutParams.smali[2,0] The file must contain a .class directiveout/framework/smali/android/view/SurfaceControl.smali[31,0] The file must contain a .class directiveout/framework/smali/com/android/internal/os/RuntimeInit.smali[576,0] The file must contain a .class directiveout/framework/smali/com/android/internal/os/Zygote.smali[3,0] The file must contain a .class directive
Click to expand...
Click to collapse
Hi. I'm too trying to build... And stuck exactly at:
Zygote.smali[3,0] The file must contain a .class directive
Could you get past it?
@SalarX as you can see no replies in this thread...means no developers are interested in miui nor they are helping another people to do it..I am not an expert I need some help from experience developers is so important I think but unfortunately they are not helping..so I decided to quite this project.
farooque7508 said:
@SalarX as you can see no replies in this thread...means no developers are interested in miui nor they are helping another people to do it..I am not an expert I need some help from experience developers is so important I think but unfortunately they are not helping..so I decided to quite this project.
Click to expand...
Click to collapse
Okay...
But if something works I'll for sure tell you
Yeah thank you.
SalarX said:
Okay...
But if something works I'll for sure tell you
Click to expand...
Click to collapse
farooque7508 said:
Yeah thank you.
Click to expand...
Click to collapse
Hi, I am sorry to see the state of this thread.
Any chance the both of you are active on Telegram ?
We have super-active OnePlus X groups with all our developers, who are sometimes not as active on the forums due to personal reasons.
If you could PM me, I'd be too happy so share the Invite Links of our support chats.
i also getting same error .. anyone please help
Fap4k said:
REMAINING CODES (HORTEN)
HTML:
--min-sdk-version 23 --target-sdk-version 23 \
-S /home/faa/patchrom/miui/src/I18N_res/v6/common/miui/frameworks/base/core/res/res -S /home/faa/patchrom/miui/src/frameworks/base/core/res/res -S /home/faa/patchrom/miui/src/frameworks/opt/ToggleManager/res -M /home/faa/patchrom/miui/src/frameworks/base/core/res/AndroidManifest.xml \
-I out/apktool/1.apk -I out/apktool/16.apk -I /home/faa/patchrom/build/empty-res/17.apk -F out/framework-ext-res.apk
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-xhdpi/auto_disable_screenbuttons_float_bg_p.9.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-hdpi/boot_logo.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-xhdpi/boot_logo.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-xxhdpi/boot_logo.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-hdpi/boot_progress.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
/home/faa/patchrom/miui/src/frameworks/base/core/res/res/drawable-hdpi/float_notification_button_bg_n.9.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
AND FINALLY
HTML:
/home/faa/patchrom/tools/apktool --quiet b out/framework -o out/framework.jar
out/framework/smali/android/view/Window.smali[101,0] The file must contain a .class directive
out/framework/smali/android/view/ThreadedRenderer.smali[3,0] The file must contain a .class directive
Exception in thread "main" brut.androlib.AndrolibException: java.util.concurrent.ExecutionException: brut.androlib.AndrolibException: Could not smali file: android/view/Window.smali
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:129)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:69)
at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:376)
at brut.androlib.Androlib.buildSources(Androlib.java:335)
at brut.androlib.Androlib.build(Androlib.java:292)
at brut.androlib.Androlib.build(Androlib.java:268)
at brut.apktool.Main.cmdBuild(Main.java:224)
at brut.apktool.Main.main(Main.java:84)
Caused by: java.util.concurrent.ExecutionException: brut.androlib.AndrolibException: Could not smali file: android/view/Window.smali
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:124)
... 7 more
Caused by: brut.androlib.AndrolibException: Could not smali file: android/view/Window.smali
at brut.androlib.src.SmaliBuilder.buildFile(SmaliBuilder.java:142)
at brut.androlib.src.SmaliBuilder.access$000(SmaliBuilder.java:64)
at brut.androlib.src.SmaliBuilder$1.call(SmaliBuilder.java:98)
at brut.androlib.src.SmaliBuilder$1.call(SmaliBuilder.java:94)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
out/framework/smali/android/view/View.smali[2,0] The file must contain a .class directive
out/framework/smali/android/view/WindowManagerPolicy.smali[3,0] The file must contain a .class directive
out/framework/smali/android/view/MotionEvent.smali[24,0] The file must contain a .class directive
out/framework/smali/android/view/Surface.smali[14,0] The file must contain a .class directive
out/framework/smali/android/view/WindowManager$LayoutParams.smali[2,0] The file must contain a .class directive
out/framework/smali/android/view/SurfaceControl.smali[31,0] The file must contain a .class directive
out/framework/smali/com/android/internal/os/RuntimeInit.smali[576,0] The file must contain a .class directive
out/framework/smali/com/android/internal/os/Zygote.smali[3,0] The file must contain a .class directive
Click to expand...
Click to collapse
getting same error
himavanth.reddy925 said:
getting same error
Click to expand...
Click to collapse
It is due to wrong patch.
Fap4k said:
It is due to wrong patch.
Click to expand...
Click to collapse
how to correct the patch.. sir
himavanth.reddy925 said:
how to correct the patch.. sir
Click to expand...
Click to collapse
I am not sir bro..m still learning.
Refer to this video may you find a solution
First you need to know smali.
shumxin said:
First you need to know smali.
Click to expand...
Click to collapse
At last the guy is here. Please help the XDA devs trying to make MIUI. It's almost finished. (I think).
Anyways Good luck to the developers making MIUI. I'm totally here for testing the ROM. Thanks in advance for the ROM and Never Give UP!!
Fap4k said:
I am not sir bro..m still learning.
Refer to this video may you find a solution
Click to expand...
Click to collapse
thank u for providing video link
all rejects re patched.. but fullota has stoped with ana error
Code:
Recovery link files success
/home/hima/patchrom/tools/build_target_files.sh: line 154: ./customize_target_files.sh: Permission denied
/home/hima/patchrom/build/porting.mk:314: recipe for target 'fullota' failed
make: *** [fullota] Error 1
thanks in advance
himavanth.reddy925 said:
thank u for providing video link
all rejects re patched.. but fullota has stoped with ana error
thanks in advance
Click to expand...
Click to collapse
Looks like customize_target_file.sh denied permission..go to device folder and give execute permission to that particular file.
Thanks
I like this project and would donate for it

FAQs and Common Error while building Custom ROMs.

Disclaimer:
Code:
All these FAQs and Solutions are taken from my knowledge and experience if anything wrong please point out so I can correct it.And feel free to add more FAQs and Errors from your side
Disclaimer: All these FAQs and Solutions are taken from my knowledge and experience if anything wrong please point out so I can correct it.And feel free to add more FAQs and Errors from your side
FAQ #1 : Easiest way to setup build environment ?
Answer: Their is a script will will make all the work easy by @akhilnarang
Steps to be followed:
Code:
git clone https://github.com/akhilnarang/scripts
cd scripts
bash setup/<name of script>
FAQ #2: Which is the best distro to build custom rom?
Answer: I will always recommend to use Ubuntu 14.04
Download Link : DOWNLOAD NOW
FAQ #3:If I have low internet speed how to sync sources that too 60Gb and all?
Answer: Use Google cloud Platform which is the best because internet speed syncs source within half an hour build speed max 2hour first build then less than 30mins
FAQ #4: Is any programming language required to study while building ROMs?
Answer: Absolutely No since for making roms from source you just require BASIC English thats it and few logic how does fuctions work etc.
FAQ #5: I have MacBook can I built on it since it is having BASH terminal?
Answer:Sure you don't need to install another distro inbuilt Mac OS is enough.
FAQ #6: While building it stopped what to do ?
Answer: Simplest way is copy whole data and paste in any IDE and search for "FAILED:" line and read it understand what made wrong then google how to fix it,Few common errors and their fixed are their below just bookmark if you need.
FAQ #7:I Googled still not found a solution how to fix it ?
Answer: Their are many ways ask on XDA else you get contact with developer of that rom message him and resolve it.
FAQ #8: Is there any full tutorial for NOOB users ?
Answer:
1 [[GUIDE][COMPLETE] Android ROM Development From Source To End
2 [GUIDE]A Noob Guide On Building Your Own Custom Kernel (ARM & MTK) (ARM64 coming)
3 [GUIDE][COMPLETE]How to build ROM with Google Cloud
FAQ #9: What is Cherry-picking is please explain?
Answer: It is actually taking a feature of one rom and then add to your rom by giving proper credits to author etc.There is a good tutorial for doing this refer to this
How to apply patches to the source ?.This will surely help you a lot.
FAQ #10: Is there any place where I can get full details of rom files folders etc ?
Answer: Yes there is an awesome post explaining everything.
[GUIDE] Understanding the Android Source Code
FAQ #11: I have one commit which is commit but I need to add proper author to it what to do?
Answer:
git commit --amend --author="NAME "
This will add author to last commit
FAQ #12: I have done changes I need to overwrite the commit its not allowing asking for pull and retry like that.
Answer: do same git push command just add " -f " tag so it overwrites the git.
for e.g.: " git push GitHub 7x -f "instead of "git push GitHub 7x "
FAQ #13: Any Simple way to resolve conflicts while cherry-picking ?
Answer: The best way is to use search tool and search for ">>>","<<<","===" remove, add keep both depending on code.Second Method is by using GitHub as search.
FAQ #14: Is there any simpler way to check cherry-picked correctly or not since building whole ROM takes time.
Answer: Build only the required package to check if it worked correctly then build Rom as whole .For e.g. you made changes to kernel and device tree in that case just use time mka boot image rather than time mka bacon.
FAQ #15:How to remove snap camera from building?
Answer:Remove Snap from BoardConfig and use zip contents and manifest to see what permissions to do, use PRODUCT_COPY_FILES command
FAQ #16: How is flashable ZIP of kernels made ?
Answer:Android zips have updater-script which is programmed in edifier,You basically need to make a flashable zip which would write boot.img into /dev/block/bla/bla/boot.
FAQ #17: Should I dexpreopt my builds?
Answer: Not necessary it is just first boot speeding up and take extra size around 100mb more.
FAQ #18: What does boot.img contain?
Answer: it has kernel and ramdisk
FAQ #19 What are BLOBS?
Answer: Blobs are vendor files and prebuilt libs which are found in system, importing them is copy paste + the mk file, It's usually found in /system/vendor and /system/lib.
Common Errors:
All these erros I mention are faced by me and solution which I did is written along.
#1:
libwpa_qmi_eap_proxy_
intermediates/export_includes', needed by '/home/vibhoothiiaanand/nuclea/out/target/product/oneplus2/obj/EXECUTABLE
S/wpa_supplicant_intermediates/import_includes', missing and no known rule to make it
make: *** [ninja_wrapper] Error 1
Solution:
First check wheather your vendor repo is broken or not or is it included or not if not clone it from correct source.
Clone wpa supplicant ,wpa_supplicant8 from lineageos and retry it
#2:Build is successful but its not booting what to do?
Solution: Make another build with permissive by adding
"androidboot.selinux=permissive" to BoardConfig.mk it should work.
#3:I have synced device tree but device is not showing in breakfast nor lunch menu
Solution:
1.first change romname.mk file to your rom name ,for e.g. you synced Du tree and trying to make nitrogen rom so mv du.mk nitrogen.mk.
2.Change vendorsetup.sh make appropriate name of device name with rom.
3.Change .dependencies name to rom name for e.g.. du.dependencies make it nitrogen.dependencies
4.Make AndroidProducts.mk and call device.mk from it.
Will show you how things are done.
Oneplus2 device tree modded for supporting VertexOS: Vertex-fy
Oneplus2 device tree modded for supporting Candy Rom :Candify
there will be so much commits like this just git search then your good to go.
This must be general case for most of the rom and devices just refer this.
#4:
ninja: error: '/home/vibhoothiiaanand/nitrogen/out/target/product/oneplus2/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by '/home/vibhoo
thiiaanand/nitrogen/out/target/product/oneplus2/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes', missing and no known rule to make it
make: *** [ninja_wrapper] Error 1
Solution:
this is common error and its due to missing hardware BLOBs so to fix this there are few things to clone
these files are to cross checked if not clone from lineage
hardware/qcom/display
hardware/qcom/display-caf
hardware/qcom/audio
hardware/qcom/audio-caf
hardware/qcom/media
hardware/qcom/media-caf
hardware/qcom/bootctrl
hardware/qcom/bt
hardware/qcom/bt-caf
hardware/qcom/camera
hardware/qcom/gps
hardware/qcom/wlan
hardware/qcom/wlan-caf
hardware/qcom/keymaster
and for cloning I will show you how its done for Oneplus2
git clone https://github.com/LineageOS/android_hardware_qcom_display.git -b cm-14.1 hardware/qcom/display/msm8994
git clone https://github.com/LineageOS/android_hardware_qcom_audio.git -b cm-14.1 hardware/qcom/audio/msm8994
git clone https://github.com/LineageOS/android_hardware_qcom_media.git -b cm-14.1 hardware/qcom/media/msm8994 git clone https://github.com/LineageOS/android_hardware_qcom_display.git -b cm-14.1-caf-8994 hardware/qcom/display-caf/msm8994
git clone https://github.com/LineageOS/android_hardware_qcom_audio.git -b cm-14.1-caf-8994 hardware/qcom/audio-caf/msm8994
git clone https://github.com/LineageOS/android_hardware_qcom_media.git -b cm-14.1-caf-8994 hardware/qcom/media-caf/msm8994
#5
device/generic/goldfish/data/etc/apns-conf.xml', needed by '/home/vibhoothiiaanand/nitrogen/out/target/product/oneplus2/system/etc/apns-conf.xml',
missing and no known rule to make it.
Solution:
just clone generic/goldfish from google since its old AF in lineage source
git clone https://android.googlesource.com/device/generic/goldfish device/generic/goldfish
#6
frameworks/native/build/phone-xxxhdpi-4096-dalvik-heap.mk" does not exist. Stop.
Solution:
Fix is just cherry-pick this commit
https://github.com/CyanogenMod/andr...mmit/6500d428ce816ffa0ba099221a4987ad7bfcb4ab
Done it must be fixed
#7
ERROR: couldn't find ro.product.model in build.prop
Solution:
This is not that common but this happens while compiling
fix is cherry-pick this commit
https://github.com/AICP/build/commit/df574f3e6ae115425b2c25e5b5e6772503ca0f65
#8
Model number unknown.
Solution:
Go to device tree and open init/init*.cpp make device name and instead of std::string device = property_get("ro..device"); change to std::string device = property_get("ro.product.device");
#9
Deleting obsolete path /home/vibhoothiiaanand/vertex/device/oneplus/oneplus2
Deleting obsolete path /home/vibhoothiiaanand/vertex/device/oppo/common
Deleting obsolete path /home/vibhoothiiaanand/vertex/kernel/oneplus/msm8894
Deleting obsolete path /home/vibhoothiiaanand/vertex/vendor/oneplus
Solution:
this is due to not declaring repos in local manifest
#10 Broken gestures
for this two things must be noted kernel and device common must match the node names in case of oneplus2
in kernel: drivers/input/touchscreen/synaptics_driver_s3320.c and configpanel/src/com/cyanogenmod/settings/device/utils/Constants.java should match node declaration values
#11 Dex2oated errors
it usually look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For this easy fix is disabling dexpreopt
#12 ninja: error: '/home/vibhoothiiaanand/vertex/out/target/common/obj/JAVA_LIBRARIES/rcscommon_intermediates/javalib.jar', needed by '/home/vibhoothiiaanand/vertex/out/target/product/oneplus2/dex_bootjars/system/framework/arm64/boot.art', missing and no known rule to make it
make: *** [ninja_wrapper] Error 1
make: Leaving directory `/home/vibhoothiiaanand/vertex'
For me this happened while building vertex for that I removed telephony entry from android_vendor_vertex/config/common.mk
#13 /out/target/product/oneplus2/obj/SHARED_LIBRARIES/libdhcpcd_intermediates/export_includes', needed by '/home/coolmohammad98/cr/out/target/product/oneplus2/obj/EXECUTABLES/ipacm_intermediates/
Solution
For this clone https://github.com/lineageos/android_external_libnfnetlink and then your good to go
Credit:
Special Thanks to @MZO
?
I was trying to build a rom for the h830 but i got this error similar to number 12 if you could help me out
make: *** No rule to make target '/home/melwyn/du/out/target/common/obj/JAVA_LIBRARIES/tcmiface_intermediates/javalib.jar', needed by '/home/melwyn/du/out/target/product/h830/dex_bootjars/system/framework/arm64/boot.art'. Stop.
make: *** Waiting for unfinished jobs....
host C: libssl_static-host_32 <= external/boringssl/src/ssl/tls_record.c
Full log https://pastebin.com/XftevYy2
Even if it takes a lot of time, can we build a ROM with 2GB RAM with patience ?
I am building hexagon rom for mi max 2
I got this error plea help me. How to fix this?
Any other troubleshooting tips on why a build won't boot?
FAILED: /home/abhivarma362/pix/out/soong/build.ninja
/home/abhivarma362/pix/out/soong/.bootstrap/bin/soong_build -t -l /home/abhivarma362/pix/out/.module_paths/Android.bp.list -b /home/abhivarma362/pix/out/soong -n /home/abhivarma362/pix/out -d /home/abhivarma362/pix/out/soong/build.ninja.d -o /home/abhivarma362/pix/out/soong/build.ninja Android.bp
error: system/bt/include/Android.bp:1:1: module "avrcp_headers" variant "linux_glibc_x86_64": source path oneplus/oneplus2/sepolicy/bluetooth does not exist
error: system/bt/types/Android.bp:9:1: module "libbluetooth-types" variant "linux_glibc_x86_64_static": source path oneplus/oneplus2/sepolicy/bluetooth does not exist
error: system/bt/types/Android.bp:9:1: module "libbluetooth-types" variant "linux_glibc_x86_64_static": source path oneplus/oneplus2/sepolicy/bluetooth does not exist
error: system/bt/packet/base/Android.bp:1:1: module "lib-bt-packets-base" variant "linux_glibc_x86_64_static": source path oneplus/oneplus2/sepolicy/bluetooth does not exist
ninja: build stopped: subcommand failed.
15:21:48 soong bootstrap failed with: exit status 1
what is this
Hello respected developers,
I loved the rom viper Os on my redmi 4a. I'm very enthusiastic and inspired by viper os to develop it for my other devices too. But first I tried to build the rom for my redmi 4a because i wanted to test the success of my building. I would like to inform you that i have gone through every process of establishing environment to reposync all learnig from aosp document and manifests on the viper os github and even downloaded device tree,vendor and kernel as from hayeki's git hub . and i made neccessary edits to androidproducts.mk , lineage_rolex.mk to naming viper_rolex.mk and setting device path.
And finally i proceeded by :
./build-envsetup.sh
lunch viper_rolex-userdebug
mka poison
The build process then followed for about 5 hrs and i was hopefully waiting close success but alas! I came up with a error given this way:
Warning: Stripped invalid locals information from 2 methods.
In /home/shrawan/Desktop/workon_viper/out/soong/.intermediates/frameworks/base/packages/EasterEgg/EasterEgg/android_common/combined/EasterEgg.jar:kotlin/collections/SlidingWindowKt$windowedIterator$1.class:
Methods with invalid locals information:
java.lang.Object kotlin.collections.SlidingWindowKt$windowedIterator$1.doResume(java.lang.Object, java.lang.Throwable)
In /home/shrawan/Desktop/workon_viper/out/soong/.intermediates/frameworks/base/packages/EasterEgg/EasterEgg/android_common/combined/EasterEgg.jar:kotlin/sequences/SequencesKt___SequencesKt$zipWithNext$2.class:
Methods with invalid locals information:
java.lang.Object kotlin.sequences.SequencesKt___SequencesKt$zipWithNext$2.doResume(java.lang.Object, java.lang.Throwable)
Some warnings are typically a sign of using an outdated Java toolchain. To fix, recompile the source with an updated toolchain.
[ 82% 60970/74331] build /home/shrawan...icy_tests_intermediates/sepolicy_tests
FAILED: /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/sepolicy_tests_intermediates/sepolicy_tests
/bin/bash -c "(/home/shrawan/Desktop/workon_viper/out/host/linux-x86/bin/sepolicy_tests -l /home/shrawan/Desktop/workon_viper/out/host/linux-x86/lib64/libsepolwrap.so -f /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/plat_file_contexts_intermediates/plat_file_contexts -f /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/vendor_file_contexts_intermediates/vendor_file_contexts -p /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/sepolicy_intermediates/sepolicy ) && (touch /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/sepolicy_tests_intermediates/sepolicy_tests )"
The following types on /data/ must be associated with the "core_data_file_type" attribute: netmgrd_data_file
[ 82% 60975/74331] //bionic/libc:commo...ioner preprocess include [linux_glibc]
warning: attempted to generate guard with empty availability: obsoleted = 23
warning: attempted to generate guard with empty availability: obsoleted = 21
ninja: build stopped: subcommand failed.
11:58:35 ninja failed with: exit status 1
#### failed to build some targets (04:38:04 (hh:mm:ss)) ####
I did a enough of the search in and out of the forum but i couldn't able to know what problem is this and i dont have any idea how to solve this. Please give me some light on what problem is this and guide me where should i be looking to solve. I have a great enthusiasm of learning but this problem solution isn't available or discussed properly in any place or maybe i didn't find the place where to look. Please help me on this[/QUOTE]
#AbitathaRoy said:
Even if it takes a lot of time, can we build a ROM with 2GB RAM with patience ?
Click to expand...
Click to collapse
you mean for a device with 2 GB ram ? or meant your building computer's ram...well if you meant for your computer then you can create a swap partition of about 4-6GB and linux will use it as virtual ram
I encountered the same problem
abhijiths362 said:
FAILED: /home/abhivarma362/pix/out/soong/build.ninja
/home/abhivarma362/pix/out/soong/.bootstrap/bin/soong_build -t -l /home/abhivarma362/pix/out/.module_paths/Android.bp.list -b /home/abhivarma362/pix/out/soong -n /home/abhivarma362/pix/out -d /home/abhivarma362/pix/out/soong/build.ninja.d -o /home/abhivarma362/pix/out/soong/build.ninja Android.bp
error: system/bt/include/Android.bp:1:1: module "avrcp_headers" variant "linux_glibc_x86_64": source path oneplus/oneplus2/sepolicy/bluetooth does not exist
error: system/bt/types/Android.bp:9:1: module "libbluetooth-types" variant "linux_glibc_x86_64_static": source path oneplus/oneplus2/sepolicy/bluetooth does not exist
error: system/bt/types/Android.bp:9:1: module "libbluetooth-types" variant "linux_glibc_x86_64_static": source path oneplus/oneplus2/sepolicy/bluetooth does not exist
error: system/bt/packet/base/Android.bp:1:1: module "lib-bt-packets-base" variant "linux_glibc_x86_64_static": source path oneplus/oneplus2/sepolicy/bluetooth does not exist
ninja: build stopped: subcommand failed.
15:21:48 soong bootstrap failed with: exit status 1
what is this
Click to expand...
Click to collapse
Do you have resolved it? I find bluetooth-types appearance in moudle_info.json. I want to delete it, but I don't know what has auto generate the module_info .
azwane said:
Hello respected developers,
I loved the rom viper Os on my redmi 4a. I'm very enthusiastic and inspired by viper os to develop it for my other devices too. But first I tried to build the rom for my redmi 4a because i wanted to test the success of my building. I would like to inform you that i have gone through every process of establishing environment to reposync all learnig from aosp document and manifests on the viper os github and even downloaded device tree,vendor and kernel as from hayeki's git hub . and i made neccessary edits to androidproducts.mk , lineage_rolex.mk to naming viper_rolex.mk and setting device path.
And finally i proceeded by :
./build-envsetup.sh
lunch viper_rolex-userdebug
mka poison
The build process then followed for about 5 hrs and i was hopefully waiting close success but alas! I came up with a error given this way:
Warning: Stripped invalid locals information from 2 methods.
In /home/shrawan/Desktop/workon_viper/out/soong/.intermediates/frameworks/base/packages/EasterEgg/EasterEgg/android_common/combined/EasterEgg.jar:kotlin/collections/SlidingWindowKt$windowedIterator$1.class:
Methods with invalid locals information:
java.lang.Object kotlin.collections.SlidingWindowKt$windowedIterator$1.doResume(java.lang.Object, java.lang.Throwable)
In /home/shrawan/Desktop/workon_viper/out/soong/.intermediates/frameworks/base/packages/EasterEgg/EasterEgg/android_common/combined/EasterEgg.jar:kotlin/sequences/SequencesKt___SequencesKt$zipWithNext$2.class:
Methods with invalid locals information:
java.lang.Object kotlin.sequences.SequencesKt___SequencesKt$zipWithNext$2.doResume(java.lang.Object, java.lang.Throwable)
Some warnings are typically a sign of using an outdated Java toolchain. To fix, recompile the source with an updated toolchain.
[ 82% 60970/74331] build /home/shrawan...icy_tests_intermediates/sepolicy_tests
FAILED: /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/sepolicy_tests_intermediates/sepolicy_tests
/bin/bash -c "(/home/shrawan/Desktop/workon_viper/out/host/linux-x86/bin/sepolicy_tests -l /home/shrawan/Desktop/workon_viper/out/host/linux-x86/lib64/libsepolwrap.so -f /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/plat_file_contexts_intermediates/plat_file_contexts -f /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/vendor_file_contexts_intermediates/vendor_file_contexts -p /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/sepolicy_intermediates/sepolicy ) && (touch /home/shrawan/Desktop/workon_viper/out/target/product/rolex/obj/ETC/sepolicy_tests_intermediates/sepolicy_tests )"
The following types on /data/ must be associated with the "core_data_file_type" attribute: netmgrd_data_file
[ 82% 60975/74331] //bionic/libc:commo...ioner preprocess include [linux_glibc]
warning: attempted to generate guard with empty availability: obsoleted = 23
warning: attempted to generate guard with empty availability: obsoleted = 21
ninja: build stopped: subcommand failed.
11:58:35 ninja failed with: exit status 1
#### failed to build some targets (04:38:04 (hh:mm:ss)) ####
I did a enough of the search in and out of the forum but i couldn't able to know what problem is this and i dont have any idea how to solve this. Please give me some light on what problem is this and guide me where should i be looking to solve. I have a great enthusiasm of learning but this problem solution isn't available or discussed properly in any place or maybe i didn't find the place where to look. Please help me on this
Click to expand...
Click to collapse
[/QUOTE]
I guess something is wrong with your sepolicy rules
Go to device/xiaomi/rolex/sepolicy folder
and look at file_contexts file
(also check /device/xiaomi/*-common folder
if you have any for your device)
compare it with other developers/maintainers device tree
also To be safe look at whole folder
thank you i will be looking it
azwane said:
I guess something is wrong with your sepolicy rules
Go to device/xiaomi/rolex/sepolicy folder
and look at file_contexts file
(also check /device/xiaomi/*-common folder
if you have any for your device)
compare it with other developers/maintainers device tree
also To be safe look at whole folder
Click to expand...
Click to collapse
[/QUOTE]
????
hello I have this problem, I tried 2 roms and had the same error if you can help me: [100% 1/1] /home/waynee/android/evox/out/soong/.minibootstrap/minibp /home/wayne
FAILED: /home/waynee/android/evox/out/soong/.bootstrap/build.ninja
/home/waynee/android/evox/out/soong/.minibootstrap/minibp -t -l /home/waynee/android/evox/out/.module_paths/Android.bp.list -b /home/waynee/android/evox/out/soong -n /home/waynee/android/evox/out -d /home/waynee/android/evox/out/soong/.bootstrap/build.ninja.d -globFile /home/waynee/android/evox/out/soong/.minibootstrap/build-globs.ninja -o /home/waynee/android/evox/out/soong/.bootstrap/build.ninja Android.bp
error: vendor/evolutionx/build/soong/Android.bp:1:1: module "soong-aosp" already defined
vendor/aosp/build/soong/Android.bp:1:1 <-- previous definition here
error: vendor/evolutionx/build/soong/Android.bp:9:1: module "soong-custom-generator" already defined
vendor/aosp/build/soong/Android.bp:9:1 <-- previous definition here
09:13:44 soong minibootstrap failed with: exit status 1
ninja: Entering directory `.'
ninja: error: '/.txt', needed by '/home/me/android/lineage/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp', missing and no known rule to make it
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
[email protected]:~/android/lineage$
someone plz point me in the right direction I have been trying to build this OS for almost a month... and so far I've made it to 1%... barely...
do you was find solution for Soong issues ?

Question ROM build failed due to CUDA

Hi,
so I've build ROM before (LineageOS and more recently Pixel Experience) but am running into an error which might be just a syntax problem in one of the source files. Before messing things up by editing these files myself, wanted to ask here which best course of action to take. (target phone: Redmi Note 10 Pro)
My build setup is a Proxmox 7 server hosting an Ubuntu 20.04 VM which has a Nvidia vGPU installed.
Bash:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2020 NVIDIA Corporation
Built on Mon_Nov_30_19:08:53_PST_2020
Cuda compilation tools, release 11.2, V11.2.67
Build cuda_11.2.r11.2/compiler.29373293_0
The build starts, but after completing the kernel compilation the following error occurs.
Bash:
In file included from ../../../../../../kernel/xiaomi/sm6150/init/version.c:9:
./include/generated/compile.h:7:24: warning: missing terminating '"' character [-Winvalid-pp-token]
#define LINUX_COMPILER "Android (6877366 based on r383902b1) clang version 11.0.2 (https://android.googlesource.com/toolchai
n/llvm-project b397f81060ce6d701042b782172ed13bee898b79)
^
./include/generated/compile.h:8:1: error: unknown type name 'Found'
Found CUDA installation: /usr/local/cuda, version 7.0, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315"
^
./include/generated/compile.h:8:11: error: expected ';' after top level declarator
Found CUDA installation: /usr/local/cuda, version 7.0, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315"
^
;
./include/generated/compile.h:8:103: warning: missing terminating '"' character [-Winvalid-pp-token]
Found CUDA installation: /usr/local/cuda, version 7.0, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315"
^
In file included from ../../../../../../kernel/xiaomi/sm6150/init/version.c:10:
In file included from ../../../../../../kernel/xiaomi/sm6150/include/linux/module.h:9:
In file included from ../../../../../../kernel/xiaomi/sm6150/include/linux/list.h:5:
../../../../../../kernel/xiaomi/sm6150/include/linux/types.h:102:10: error: unknown type name '__s8'; did you mean '__u8'?
typedef __s8 int8_t;
^~~~
__u8
../../../../../../kernel/xiaomi/sm6150/include/uapi/asm-generic/int-ll64.h:21:23: note: '__u8' declared here
typedef unsigned char __u8;
^
../../../../../../kernel/xiaomi/sm6150/init/version.c:46:26: error: expected ';' after top level declarator
LINUX_COMPILE_HOST ") (" LINUX_COMPILER ") " UTS_VERSION "\n";
^
;
../../../../../../kernel/xiaomi/sm6150/init/version.c:51:6: error: expected ';' after top level declarator
" (" LINUX_COMPILER ") %s\n";
^
;
2 warnings and 5 errors generated.
make[2]: *** [/home/wvthoog/android/pixel-experience/kernel/xiaomi/sm6150/scripts/Makefile.build:361: init/version.o] Error
1
make[2]: *** Waiting for unfinished jobs....
Like i said before, it looks like there are some syntax errors somewhere in one of the sourcefiles but at this point have no clue which files to edit to remedy this error.
Also, if i compile the same ROM for my Redmi Note 10 Pro (sweet) on another VM (Ubuntu 20.04) without a Nvidia GPU the build succeeds .
This sounds like a bug somewhere in one of the source files of Pixel Experience. Tried filing an issue on their Github page but their bot is fairly aggressive in closing issues if they don't meet their posting requirements.
So my question drills down to.... do other experience the same problem when using CUDA during the build process of Pixel Experience and possibly have a solution ?
Secondly, is there an option to disable CUDA during the build process ?
Thanks
populus_ said:
Hi,
so I've build ROM before (LineageOS and more recently Pixel Experience) but am running into an error which might be just a syntax problem in one of the source files. Before messing things up by editing these files myself, wanted to ask here which best course of action to take. (target phone: Redmi Note 10 Pro)
My build setup is a Proxmox 7 server hosting an Ubuntu 20.04 VM which has a Nvidia vGPU installed.
Bash:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2020 NVIDIA Corporation
Built on Mon_Nov_30_19:08:53_PST_2020
Cuda compilation tools, release 11.2, V11.2.67
Build cuda_11.2.r11.2/compiler.29373293_0
The build starts, but after completing the kernel compilation the following error occurs.
Bash:
In file included from ../../../../../../kernel/xiaomi/sm6150/init/version.c:9:
./include/generated/compile.h:7:24: warning: missing terminating '"' character [-Winvalid-pp-token]
#define LINUX_COMPILER "Android (6877366 based on r383902b1) clang version 11.0.2 (https://android.googlesource.com/toolchai
n/llvm-project b397f81060ce6d701042b782172ed13bee898b79)
^
./include/generated/compile.h:8:1: error: unknown type name 'Found'
Found CUDA installation: /usr/local/cuda, version 7.0, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315"
^
./include/generated/compile.h:8:11: error: expected ';' after top level declarator
Found CUDA installation: /usr/local/cuda, version 7.0, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315"
^
;
./include/generated/compile.h:8:103: warning: missing terminating '"' character [-Winvalid-pp-token]
Found CUDA installation: /usr/local/cuda, version 7.0, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315"
^
In file included from ../../../../../../kernel/xiaomi/sm6150/init/version.c:10:
In file included from ../../../../../../kernel/xiaomi/sm6150/include/linux/module.h:9:
In file included from ../../../../../../kernel/xiaomi/sm6150/include/linux/list.h:5:
../../../../../../kernel/xiaomi/sm6150/include/linux/types.h:102:10: error: unknown type name '__s8'; did you mean '__u8'?
typedef __s8 int8_t;
^~~~
__u8
../../../../../../kernel/xiaomi/sm6150/include/uapi/asm-generic/int-ll64.h:21:23: note: '__u8' declared here
typedef unsigned char __u8;
^
../../../../../../kernel/xiaomi/sm6150/init/version.c:46:26: error: expected ';' after top level declarator
LINUX_COMPILE_HOST ") (" LINUX_COMPILER ") " UTS_VERSION "\n";
^
;
../../../../../../kernel/xiaomi/sm6150/init/version.c:51:6: error: expected ';' after top level declarator
" (" LINUX_COMPILER ") %s\n";
^
;
2 warnings and 5 errors generated.
make[2]: *** [/home/wvthoog/android/pixel-experience/kernel/xiaomi/sm6150/scripts/Makefile.build:361: init/version.o] Error
1
make[2]: *** Waiting for unfinished jobs....
Like i said before, it looks like there are some syntax errors somewhere in one of the sourcefiles but at this point have no clue which files to edit to remedy this error.
Also, if i compile the same ROM for my Redmi Note 10 Pro (sweet) on another VM (Ubuntu 20.04) without a Nvidia GPU the build succeeds .
This sounds like a bug somewhere in one of the source files of Pixel Experience. Tried filing an issue on their Github page but their bot is fairly aggressive in closing issues if they don't meet their posting requirements.
So my question drills down to.... do other experience the same problem when using CUDA during the build process of Pixel Experience and possibly have a solution ?
Secondly, is there an option to disable CUDA during the build process ?
Thanks
Click to expand...
Click to collapse
Just bumped to your question, yes it happens with me too, Pcoco F3 Lineage, what I have done is to have a ubuntu (separate SSD) to boot from when I need to build, and use the other system for all other uses including cuda transcoding.
You're in the wrong forum. This is exclusively about the Xiaomi Redmi Note 10. No other version.
populus_ said:
Hi,
so I've build ROM before (LineageOS and more recently Pixel Experience) but am running into an error which might be just a syntax problem in one of the source files. Before messing things up by editing these files myself, wanted to ask here which best course of action to take. (target phone: Redmi Note 10 Pro)
My build setup is a Proxmox 7 server hosting an Ubuntu 20.04 VM which has a Nvidia vGPU installed.
Bash:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2020 NVIDIA Corporation
Built on Mon_Nov_30_19:08:53_PST_2020
Cuda compilation tools, release 11.2, V11.2.67
Build cuda_11.2.r11.2/compiler.29373293_0
The build starts, but after completing the kernel compilation the following error occurs.
Bash:
In file included from ../../../../../../kernel/xiaomi/sm6150/init/version.c:9:
./include/generated/compile.h:7:24: warning: missing terminating '"' character [-Winvalid-pp-token]
#define LINUX_COMPILER "Android (6877366 based on r383902b1) clang version 11.0.2 (https://android.googlesource.com/toolchai
n/llvm-project b397f81060ce6d701042b782172ed13bee898b79)
^
./include/generated/compile.h:8:1: error: unknown type name 'Found'
Found CUDA installation: /usr/local/cuda, version 7.0, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315"
^
./include/generated/compile.h:8:11: error: expected ';' after top level declarator
Found CUDA installation: /usr/local/cuda, version 7.0, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315"
^
;
./include/generated/compile.h:8:103: warning: missing terminating '"' character [-Winvalid-pp-token]
Found CUDA installation: /usr/local/cuda, version 7.0, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315"
^
In file included from ../../../../../../kernel/xiaomi/sm6150/init/version.c:10:
In file included from ../../../../../../kernel/xiaomi/sm6150/include/linux/module.h:9:
In file included from ../../../../../../kernel/xiaomi/sm6150/include/linux/list.h:5:
../../../../../../kernel/xiaomi/sm6150/include/linux/types.h:102:10: error: unknown type name '__s8'; did you mean '__u8'?
typedef __s8 int8_t;
^~~~
__u8
../../../../../../kernel/xiaomi/sm6150/include/uapi/asm-generic/int-ll64.h:21:23: note: '__u8' declared here
typedef unsigned char __u8;
^
../../../../../../kernel/xiaomi/sm6150/init/version.c:46:26: error: expected ';' after top level declarator
LINUX_COMPILE_HOST ") (" LINUX_COMPILER ") " UTS_VERSION "\n";
^
;
../../../../../../kernel/xiaomi/sm6150/init/version.c:51:6: error: expected ';' after top level declarator
" (" LINUX_COMPILER ") %s\n";
^
;
2 warnings and 5 errors generated.
make[2]: *** [/home/wvthoog/android/pixel-experience/kernel/xiaomi/sm6150/scripts/Makefile.build:361: init/version.o] Error
1
make[2]: *** Waiting for unfinished jobs....
Like i said before, it looks like there are some syntax errors somewhere in one of the sourcefiles but at this point have no clue which files to edit to remedy this error.
Also, if i compile the same ROM for my Redmi Note 10 Pro (sweet) on another VM (Ubuntu 20.04) without a Nvidia GPU the build succeeds .
This sounds like a bug somewhere in one of the source files of Pixel Experience. Tried filing an issue on their Github page but their bot is fairly aggressive in closing issues if they don't meet their posting requirements.
So my question drills down to.... do other experience the same problem when using CUDA during the build process of Pixel Experience and possibly have a solution ?
Secondly, is there an option to disable CUDA during the build process ?
Thanks
Click to expand...
Click to collapse
Face the same problem, How did you solved the error?
Ended up removing the Cuda Toolkit altogether since i couldn't find a solution.
populus_ said:
Ended up removing the Cuda Toolkit altogether since i couldn't find a solution.
Click to expand...
Click to collapse
Hi populus_:
Have you tried to disable the cuda toolkit detection when compiling the rom? Just romving the cuda tookit may be not a pretty solution. besuase i have install multi cuda tookit.
That was my initial question. How do i disable CUDA from building a ROM. Haven't found an answer yet.

[NeedHelp] [AOSP] When I try to build AOSP from source code, it has the following error

```
clang: error: clang frontend command failed with exit code 139 (use -v to see invocation)
Android (7485623, based on r416183b1) clang version 12.0.7 (https://android.googlesource.com/toolchain/
llvm-project c935d99d7cf2016289302412d708641d52d2f7ee)
Target: armv7a-unknown-linux-android10000
Thread model: posix
InstalledDir: prebuilts/clang/host/linux-x86/clang-r416183b1/bin
clang: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /home/logic/Android/out/soong/.temp/tree-236d56.c
clang: note: diagnostic msg: /home/logic/Android/out/soong/.temp/tree-236d56.sh
clang: note: diagnostic msg:
```
logic_f said:
```
clang: error: clang frontend command failed with exit code 139 (use -v to see invocation)
Android (7485623, based on r416183b1) clang version 12.0.7 (https://android.googlesource.com/toolchain/
llvm-project c935d99d7cf2016289302412d708641d52d2f7ee)
Target: armv7a-unknown-linux-android10000
Thread model: posix
InstalledDir: prebuilts/clang/host/linux-x86/clang-r416183b1/bin
clang: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /home/logic/Android/out/soong/.temp/tree-236d56.c
clang: note: diagnostic msg: /home/logic/Android/out/soong/.temp/tree-236d56.sh
clang: note: diagnostic msg:
```
Click to expand...
Click to collapse
@logic_f
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A. Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator

Categories

Resources