I am trying to run my xbox360 kinect on my raspberry pi 2. I have followed this guide (https://github.com/xxorde/librekinect*)without errors but at the last command ( make load ) gives me this error:
[email protected]:/home/pi/librekinect-master# ls
gspca.c gspca.h kinect.c Makefile readme.md unload_drivers.sh
[email protected]:/home/pi/librekinect-master# make load
make unload_drivers
make[1]: Entering directory '/home/pi/librekinect-master'
sudo sh unload_drivers.sh
Error: Module kinect is not currently loaded
Error: Module gspca is not currently loaded
Error: Module gspca_main is in use by: gspca_kinect
Error: Module gspca_kinect is in use
Error: Module * is not currently loaded
make[1]: Leaving directory '/home/pi/librekinect-master'
sudo modprobe videodev
sudo insmod gspca.ko
Error: could not load module gspca.ko: No such file or directory
Makefile:42: recipe for target 'load' failed
make: *** [load] Error 1
[email protected]:/home/pi/librekinect-master#
nik012003 said:
I am trying to run my xbox360 kinect on my raspberry pi 2. I have followed this guide (https://github.com/xxorde/librekinect*)without errors but at the last command ( make load ) gives me this error:
[email protected]:/home/pi/librekinect-master# ls
gspca.c gspca.h kinect.c Makefile readme.md unload_drivers.sh
[email protected]:/home/pi/librekinect-master# make load
make unload_drivers
make[1]: Entering directory '/home/pi/librekinect-master'
sudo sh unload_drivers.sh
Error: Module kinect is not currently loaded
Error: Module gspca is not currently loaded
Error: Module gspca_main is in use by: gspca_kinect
Error: Module gspca_kinect is in use
Error: Module * is not currently loaded
make[1]: Leaving directory '/home/pi/librekinect-master'
sudo modprobe videodev
sudo insmod gspca.ko
Error: could not load module gspca.ko: No such file or directory
Makefile:42: recipe for target 'load' failed
make: *** [load] Error 1
[email protected]:/home/pi/librekinect-master#
Click to expand...
Click to collapse
Hello, just for refernce I've found this on the redme file in the repo:
"make load" fails
Is the kernel compatible to the sources you use? Compile a kernel and load it.
Are you sure you have compiled the kernel without any errors. This error tells me that something is wrong with kernel compilation
Code:
Error: could not load module gspca.ko: No such file or directory
root-expert said:
Hello, just for refernce I've found this on the redme file in the repo:
"make load" fails
Is the kernel compatible to the sources you use? Compile a kernel and load it.
Are you sure you have compiled the kernel without any errors. This error tells me that something is wrong with kernel compilation
Code:
Error: could not load module gspca.ko: No such file or directory
Click to expand...
Click to collapse
I have opened an issue on github with other info:
https://github.com/xxorde/librekinect/issues/25#issuecomment-95719253
nik012003 said:
I have opened an issue on github with other info:
https://github.com/xxorde/librekinect/issues/25#issuecomment-95719253
Click to expand...
Click to collapse
Did you update your makefile as he said. Run this on your raspberry pi 2:
Code:
uname -m
You should get something like armv7l.
root-expert said:
Did you update your makefile as he said. Run this on your raspberry pi 2:
Code:
uname -m
You should get something like armv7l.
Click to expand...
Click to collapse
Yes I have updated the file
I get armv7l
I am starting this thread to bring up AOSP/CAF based roms to our device gt-i9192 s4 mini duos.
This thread is for developers only and only rom building and rom bring up questions and discussions are allowed in this thread.
Best way is post the building errors, logcats, source code tree links here so that we all can help each other to fix the errors while building or rom booting.
For those who are keen to learn fixing bugs should read following article by great developer pawitp
https://medium.com/@pawitp/investigating-and-fixing-an-android-rom-bug-685f3e2e3806
Generally for aosp rom bring up - you need 2 files in your device trees
Code:
aosp_serranodsdd.mk
AndroidProducts.mk
like in other devices
See following commit to make your tree compatible with aosp
Code:
https://github.com/pawitp/android_device_samsung_i9082/commit/e5bf34bdfb42394e562ae66e068367dec38a6459
like this i have created one for us
Code:
https://github.com/i9192/android_device_samsung_serranodsdd/blob/n/aosp_serranodsdd.mk
https://github.com/i9192/android_device_samsung_serranodsdd/blob/n/AndroidProducts.mk
some of aosp roms need special files for their bring up like
for cm - cm.mk
for omni - omni_device.mk
for broken - broken.mk
for tipsy - tipsy.mk
for PA - pa_device.mk
for krexus - krexus_device.mk
for purenexus - pure_device.mk
All those who are building can post their questions, queries , bugs on this thread...we will fix them together
some one else working on n preview other than me???? or someone is willing to build and work on it ????
if yes post your questions ..i will try to answer that here
k2wl said:
some one else working on n preview other than me???? or someone is willing to build and work on it ????
if yes post your questions ..i will try to answer that here
Click to expand...
Click to collapse
yes i was working on it but its now in the queue , display was blank but i was getting the logcat.
now i m working to build AOSP 6.0 , i got a sepolicy denial so i fixed it with this commit https://github.com/FaArIsH/platform...mmit/e35f718c7939b0f178bd1869396a472daa404075
but now i m getting this error
Code:
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for qtitetherservice.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.seemp.health.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.auth.securesampleauthdaemon.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.qseeproxysample.
i have removed the line vendor/aosp/sepolicy from msm8930-common and its now finished building but i don't think it will boot becasue i skipped the sepolicy error
DarkFrenzy said:
yes i was working on it but its now in the queue , display was blank but i was getting the logcat.
now i m working to build AOSP 6.0 , i got a sepolicy denial so i fixed it with this commit https://github.com/FaArIsH/platform...mmit/e35f718c7939b0f178bd1869396a472daa404075
but now i m getting this error
Code:
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for qtitetherservice.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.seemp.health.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.auth.securesampleauthdaemon.
/home/farish_priv/ap/out/target/product/serranodsdd/obj/ETC/service_contexts_intermediates/service_contexts: Mult
iple same specifications for com.qualcomm.qti.qseeproxysample.
i have removed the line vendor/aosp/sepolicy from msm8930-common and its now finished building but i don't think it will boot becasue i skipped the sepolicy error
Click to expand...
Click to collapse
use permissive mode for now and use sonyaosp sepolicy for time being...it builds fine and as we use permissive mode you get rid of major denials for boot.
post your logcat here
k2wl said:
some one else working on n preview other than me???? or someone is willing to build and work on it ????
if yes post your questions ..i will try to answer that here
Click to expand...
Click to collapse
My device is defective, I will be sending him to repair and as soon as pick it back I'll get to work with n preview (to help).
tioguda said:
My device is defective, I will be sending him to repair and as soon as pick it back I'll get to work with n preview (to help).
Click to expand...
Click to collapse
great
aosp-caf
For CAF sources, should I use the regular CM device tree or AOSP? I am trying CM tree except for the aosp_serranodsdd and AndroidProducts..mk files.
How do you fix this properly?
Code:
build/core/Makefile:46: *** Prebuilt apk found in PRODUCT_COPY_FILES: device/samsung/serrano-common/prebuilt/Eleven.apk:system/app/Eleven/Eleven.apk, use BUILD_PREBUILT instead!. Stop.
I deleted the line in serrano-common.mk because I can't figure out how to use build_prebuilt
I am also getting stuck at this error:
Code:
*** No rule to make target `/home/endre/aosp-caf/out/target/product/serranodsdd/obj/SHARED_LIBRARIES/libaudiopolicymanager_intermediates/export_includes', needed by `/home/endre/aosp-caf/out/target/product/serranodsdd/obj/SHARED_LIBRARIES/libaudiopolicyservice_intermediates/import_includes'. Stop.
One more question. Is there a general guide on how to troubleshoot these "No rule to make target" errors? It drives me crazy that usually both files the error message is referring to are in the "out" folder and I have no idea where the original command line is or what to do. I am also trying a PA build and that one keeps dying on me as well with this type of error just on a different file.
csendre said:
For CAF sources, should I use the regular CM device tree or AOSP? I am trying CM tree except for the aosp_serranodsdd and AndroidProducts..mk files.
How do you fix this properly?
Code:
build/core/Makefile:46: *** Prebuilt apk found in PRODUCT_COPY_FILES: device/samsung/serrano-common/prebuilt/Eleven.apk:system/app/Eleven/Eleven.apk, use BUILD_PREBUILT instead!. Stop.
I deleted the line in serrano-common.mk because I can't figure out how to use build_prebuilt
I am also getting stuck at this error:
Code:
*** No rule to make target `/home/endre/aosp-caf/out/target/product/serranodsdd/obj/SHARED_LIBRARIES/libaudiopolicymanager_intermediates/export_includes', needed by `/home/endre/aosp-caf/out/target/product/serranodsdd/obj/SHARED_LIBRARIES/libaudiopolicyservice_intermediates/import_includes'. Stop.
One more question. Is there a general guide on how to troubleshoot these "No rule to make target" errors? It drives me crazy that usually both files the error message is referring to are in the "out" folder and I have no idea where the original command line is or what to do. I am also trying a PA build and that one keeps dying on me as well with this type of error just on a different file.
Click to expand...
Click to collapse
for caf or aosp build use cm tree...you need to fix your tree for errors.
for prebuilt apk error use following commit in build folder. Apply this commmit and it should build prebuild apks copies properly during build
https://github.com/i9192/platform_build/commit/6ceb823426e5f8b20fd39862013c909d37b415e9
Click to expand...
Click to collapse
for libaudiopolicyservice_intermediates error you need to set
BOARD_USES_GENERIC_AUDIO := false
Click to expand...
Click to collapse
flag in your boardconfig.mk
No rule to make target means something is missing on your device tree to build that particular thing.YOu need to search for it.
Like for audiopolicyservice error i search github for
SHARED_LIBRARIES/libaudiopolicyservice_intermediates/import_includes
Click to expand...
Click to collapse
and in issues i found a thread disccussing something...there someone told that you need to set that flag to get rid of error.
https://github.com/hak86/android_device_huawei_p8litekirin/issues/7
Click to expand...
Click to collapse
you need to search on google,xda,github, for this ...sometimes you need to ask cm team on their developer channel on irc, sometimes you need to discuss things with developers of that particular rom over their official community page like on google plus or something else...most of the time you will get the answer...and look for commits from good developers...like cm team, pawitp, purenexus, krexus, screwdaosp. Their commits most of the time show us the way.
k2wl said:
some one else working on n preview other than me???? or someone is willing to build and work on it ????
if yes post your questions ..i will try to answer that here
Click to expand...
Click to collapse
Sorry for the intrusion on the topic (I'm not developer), but wish you good luck in your intention. Remember that we have a device that is the last of its class: Good and Compact.
I could buy another model, but I opted for a new battery. Two years using S4 Mini. And I will continue. Until all give up it.
While there are developers, S4 Mini will remain alive.
ADR USR said:
Sorry for the intrusion on the topic (I'm not developer), but wish you good luck in your intention. Remember that we have a device that is the last of its class: Good and Compact.
I could buy another model, but I opted for a new battery. Two years using S4 Mini. And I will continue. Until all give up it.
While there are developers, S4 Mini will remain alive.
Click to expand...
Click to collapse
yes... last of it's class really...i am willing to go beyond to keep this device alive.
after iphone se i thought android oems will introduce smaller devices but still nothing...
and if i can boot up aosp 7.0 then i think ...arco and others who are working on cm14 afterwords will support this device too.
why these libs are not building (there are not in the zip file nor in the our dir) does android N doesnt need them ?
libOmx*
liboverlay.so
libstagefrighthw.so
and few others
DarkFrenzy said:
why these libs are not building (there are not in the zip file nor in the our dir) does android N doesnt need them ?
libOmx*
liboverlay.so
libstagefrighthw.so
and few others
Click to expand...
Click to collapse
as i can see new n preview build system somehow does not build libstagefrighthw.so but it build libstagefright.so only..but all zips for preview builds for all devices have libstagefrighthw.so...i am working on that since last two days to build libstagefrighthw.so from source..but i guess we have to use it as prebuild file from cm 13 roms.
as i have compared...audio,media,display folders are not changed much in n preview so i guess we can safely use that prebuilt binary from cm 13 tree
UPDATE_
found the issue...it looks like cm repos we use does not build libstagefrighthw lib...i will fix this issue soon
Trying to build tipsy rom and the build dies when it gets to the kernel with the following error
Code:
arm-eabi-gcc: No such file or directory
Is your PATH set correctly?
make[4]: *** [scripts/mod/empty.o] Error 2
make[3]: *** [scripts/mod] Error 2
make[3]: *** Waiting for unfinished jobs....
SHIPPED scripts/genksyms/parse.tab.c
I checked the staging area and build tools are present in the usual /prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin folder, so probably the path is not set right, but where is this set, how do I check it?
csendre said:
Trying to build tipsy rom and the build dies when it gets to the kernel with the following error
Code:
arm-eabi-gcc: No such file or directory
Is your PATH set correctly?
make[4]: *** [scripts/mod/empty.o] Error 2
make[3]: *** [scripts/mod] Error 2
make[3]: *** Waiting for unfinished jobs....
SHIPPED scripts/genksyms/parse.tab.c
I checked the staging area and build tools are present in the usual /prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin folder, so probably the path is not set right, but where is this set, how do I check it?
Click to expand...
Click to collapse
add this line to BoardConfigCommon.mk or BoardConfig.mk
Code:
# Kernel Toolchain
KERNEL_TOOLCHAIN := $(ANDROID_BUILD_TOP)/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin
KERNEL_TOOLCHAIN_PREFIX := arm-eabi-
@DarkFrenzy thanks, this worked! This seems to be a workaround though, shouldn't this path be defined somewhere in the build directory?
This reminds me, does anyone know a guide/list with commands/parameters that can be set in boardconfig and device make files? Also, how do you decide if a configuration should be set in boardconfig.mk, device.mk or another make file?
I am stuck again. Should I remove fileutils completely considering it is part of CM and not aosp? If so, how? If i just delete it, I get "no rule to make file" type errors.
Code:
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/KeyDisabler.java:19: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/KeyDisabler.java:35: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/KeyDisabler.java:39: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/KeyDisabler.java:43: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:21: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:48: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:49: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:50: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:84: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/TouchscreenHovering.java:95: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/SerialNumber.java:20: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../device/samsung/serrano-common/cmhw/org/cyanogenmod/hardware/SerialNumber.java:46: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:19: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:30: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:31: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:32: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:33: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:34: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:35: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:40: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:48: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:56: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:64: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:72: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/VibratorHW.java:79: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:21: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:38: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:39: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:49: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/AdaptiveBacklight.java:60: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:21: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:48: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:49: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:50: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:83: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/HighTouchSensitivity.java:94: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:19: The import cyanogenmod cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:20: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:51: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:53: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:64: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:65: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:66: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:67: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:79: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:85: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:102: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:120: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:122: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/DisplayModeControl.java:134: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:21: The import org.cyanogenmod.internal cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:40: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:41: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:51: FileUtils cannot be resolved
ERROR: /home/endre/tipsy/frameworks/opt/hardware/../../../hardware/samsung/cmhw/org/cyanogenmod/hardware/SunlightEnhancement.java:62: FileUtils cannot be resolved
make: *** [/home/endre/tipsy/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.hardware_intermediates/with-local/classes.dex] Error 41
make: *** Waiting for unfinished jobs....
csendre said:
I am stuck again. Should I remove fileutils completely considering it is part of CM and not aosp? If so, how? If i just delete it, I get "no rule to make file" type errors.
Click to expand...
Click to collapse
Revert that commit https://github.com/CyanogenMod/andr...mmit/afc6bd83906e04b939a1ed8c35b31d02cd631c48
Sent from my SM-T217S using Tapatalk
DarkFrenzy said:
Revert that commit https://github.com/CyanogenMod/andr...mmit/afc6bd83906e04b939a1ed8c35b31d02cd631c48
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
That was the first thing I tried because I remembered I had the same errors with AOKP when it was merged, but here for some reason it didn't help
csendre said:
That was the first thing I tried because I remembered I had the same errors with AOKP when it was merged, but here for some reason it didn't help
Click to expand...
Click to collapse
U should delete this file if it's there in cmhw DisplayColorCalibration.java
Edit: now I remembered u should revert this commit
https://github.com/CyanogenMod/andr...mmit/d8a7052baa47785c616774f8e2e9acea6246b23a
Sent from my SM-T217S using Tapatalk
DarkFrenzy said:
U should delete this file if it's there in cmhw DisplayColorCalibration.java
Edit: now I remembered u should revert this commit
https://github.com/CyanogenMod/andr...mmit/d8a7052baa47785c616774f8e2e9acea6246b23a
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
Yes, this looks to be the one. I'll try this evening.
Hi! I am trying to build OnePlusOSS (CAF) Oreo for my OP3T (not OxygenOS mixed up the title sorry) but I'm running into errors. I already had some bluetooth errors that I fixed with this commit: https://github.com/AOSPA/android_system_bt/commit/c78c34cdbd6d7163ad93454b5909a04a201117a1
but I now have a new issue, and I can't find a solution. The error I get is this:
Code:
[ 50% 1/2] glob device/*/*/Android.bp
ninja: error: 'out/target/common/obj/JAVA_LIBRARIES/com.qualcomm.qti.camera_intermediates/javalib.jar', needed by 'out/target/product/msm8996/dex_bootjars/system/framework/arm64/boot.art', missing and no known rule to make it
12:30:26 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
Someone had a similar error and the fix was this: https://developer.qualcomm.com/download/sdllvm/snapdragon-llvm-compiler-android-linux64.tar.gz I don't use the toolchain in that post, but there was an error there similar to the one I got. You can visit that link and see the reply and the error that the other person got if you want.
Code:
Hello Fenil, you should see the product package here https://source.codeaurora.org/quic/la/device/qcom/common/tree/base.mk?h=LA.UM.6.7.r1-04900-8x09.0#n1066 in your environment (line 1066) and the QTIC_EXTENSION flag should be enabled here https://source.codeaurora.org/quic/la/platform/vendor/qcom/msm8909go/tree/msm8909go.mk?h=qcom-devices.lnx.1.9.r4-rel#n34(line 34). Can you confirm that? If it is all set up correctly, check vendor/qcom/proprietary. If you need more help with this, you can email me at [email protected]
but that is a different chipset and won't work for my device.
Any help would be awesome! Also, where can I get vendor/qcom/proprietary? Or is that not given out lol.
Sorry, full link for that reply is https://source.codeaurora.org/quic/...ree/base.mk?h=LA.UM.6.7.r1-04900-8x09.0#n1066 and https://source.codeaurora.org/quic/...sm8909go.mk?h=qcom-devices.lnx.1.9.r4-rel#n34
I am trying to compile some C++ source files into a native library using Android studio, NDK and Cmake, but upon building, I get the error:
Code:
A problem occurred configuring project ':mobile'.
> C:\Users\User\Documents\B3d\mobile\.externalNativeBuild\cmake\debug\armeabi-v7a\compile_commands.json
I went to the folder mentioned in the error and 'compile_commands.json' does not exist there. What could be the problem?
After upgrading gradle plugin, I get the error:
Code:
C:\Users\User\Documents\B3d\mobile\CMakeLists.txt : C/C++ debug|armeabi-v7a : Could not get version from cmake.dir path '"C:\Android\android-sdk\cmake\3.19.0"'.
I removed the quotes from cmake.dir path in local.properties and this error was gone, next I got another error:
Code:
exception while building Json $C:\Users\User\Documents\B3d\tv\.cxx\cmake\debug\armeabi-v7a\compile_commands.json (The system cannot find the file specified)