I am having issues with custom rom that i built using lineage-15.1. My device is sanders. The camera is not working. The camera 2 app disappears soon after booting after installation. I installed open camera and it says camera is in use.
I got the logcats and i see this error -
02-12 10:46:44.252 760 760 F DEBUG : Abort message: 'CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": cannot locate symbol "_Z35eglQueryStringImplementationANDROIDPvi" referenced by "/system/vendor/lib/libguy.so"...'
I ran the nm command on the libguy.so and I find an undefined symbol there. I searched and found a shim that has this very symbol - libshim_camera_hal.so, I also found source files for this and found the function in device/motorola/sanders/libshims/camera_hal.cpp
I checked the shim file on the device, the shim file is present in /system/lib64 and /system/lib folders. libguy.so is in /system/vendor/lib and is 32bit.
Is this an LD_LIBRARY_PATH issue?
What can i do to fix this issue.
doors666 said:
I am having issues with custom rom that i built using lineage-15.1. My device is sanders. The camera is not working. The camera 2 app disappears soon after booting after installation. I installed open camera and it says camera is in use...
Click to expand...
Click to collapse
I don't have this device but, the following threads, that's device specific, may be helpful for what you are looking for and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=3722844
https://forum.xda-developers.com/showthread.php?t=3708082
https://forum.xda-developers.com/showthread.php?t=3708997
If all else fails, try posting your question within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3593531
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
are you building that lib shims?
in libshims/Android.mk
and in device.mk
Refer to this tree: https://github.com/Keertesh19/device_motorola_sanders
yes I am building that. the files do have slight differences though as I took the device,vendor,kernel from validus links. I also downloaded the validus tree using the manifest and built it and i get the same issue there also. but its not there in the latest published rom.
I still have this issue, tried a lot of things, but still no fix.
I downloaded the latest validus published ROM build and that works fine, no issues with the camera.
I synced the validus repo using the manifest file and made a build, camera does not work.
Steps -
repo sync with validus manifest.
lunch validus_sanders-userdebug
brunch sanders
clean install.
Am I missing some step here? One thing that bothered me is that brunch works fine, but make fails. The error (I think it was about java doc, it asks me to run make update-api, that also fails.
I extracted both the ROMs and did a compare on both ramdisk and /system, no significant difference that could cause this.
I extracted the shims from good rom and copied it onto the phone which had my built rom and it still did not work.
I tried fedora (26 and 27) and ubuntu (17.10 and 16.04 LTS) to make build, no difference.
I modified the initrc and modified the LD_SHIM_LIBS to include the full path for the shims, still does not work.
This is the error that I get in the logs -
03-02 09:32:31.853 2558 2558 I init : type=1400 audit(0.0:520): avc: denied { execute_no_trans } for uid=1006 path="/system/vendor/bin/mm-qcamera-daemon" dev="mmcblk0p53" ino=2817 scontext=u:r:init:s0 tcontext=ubject_r:vendor_file:s0 tclass=file permissive=1
03-02 09:32:31.924 2558 2558 F libc : CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": cannot locate symbol "_Z35eglQueryStringImplementationANDROIDPvi" referenced by "/system/vendor/lib/libguy.so"...
03-02 09:32:31.924 2558 2558 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2558 (mm-qcamera-daem), pid 2558 (mm-qcamera-daem)
03-02 09:32:31.939 2561 2561 E cutils-trace: Error opening trace file: No such file or directory (2)
03-02 09:32:31.936 2562 2562 I crash_dump32: type=1400 audit(0.0:521): avc: denied { ptrace } for uid=1006 scontext=u:r:crash_dump:s0 tcontext=u:r:init:s0 tclass=process permissive=1
03-02 09:32:31.945 2562 2562 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
03-02 09:32:31.946 691 691 I /system/bin/tombstoned: received crash request for pid 2558
03-02 09:32:31.947 2562 2562 I crash_dump32: performing dump of process 2558 (target tid = 2558)
03-02 09:32:31.947 2562 2562 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-02 09:32:31.947 2562 2562 F DEBUG : Build fingerprint: 'google/walleye/walleye:8.1.0/OPM1.171019.011/4448085:user/release-keys'
03-02 09:32:31.947 2562 2562 F DEBUG : Revision: '0'
03-02 09:32:31.947 2562 2562 F DEBUG : ABI: 'arm'
03-02 09:32:31.947 2562 2562 F DEBUG : pid: 2558, tid: 2558, name: mm-qcamera-daem >>> /system/vendor/bin/mm-qcamera-daemon <<<
03-02 09:32:31.947 2562 2562 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-02 09:32:31.948 2562 2562 F DEBUG : Abort message: 'CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": cannot locate symbol "_Z35eglQueryStringImplementationANDROIDPvi" referenced by "/system/vendor/lib/libguy.so"...'
03-02 09:32:31.948 2562 2562 F DEBUG : r0 00000000 r1 000009fe r2 00000006 r3 00000008
03-02 09:32:31.948 2562 2562 F DEBUG : r4 000009fe r5 000009fe r6 ff8a460c r7 0000010c
03-02 09:32:31.949 2562 2562 F DEBUG : r8 00000000 r9 ed86e010 sl 00000000 fp ff8a58a4
03-02 09:32:31.949 2562 2562 F DEBUG : ip ff8a4630 sp ff8a45f8 lr ed907309 pc ed905808 cpsr 200f0030
03-02 09:32:31.950 2562 2562 F DEBUG :
03-02 09:32:31.950 2562 2562 F DEBUG : backtrace:
03-02 09:32:31.950 2562 2562 F DEBUG : #00 pc 0005f808 /system/bin/linker (__dl_abort+63)
03-02 09:32:31.950 2562 2562 F DEBUG : #01 pc 00010931 /system/bin/linker (__dl___linker_init+2820)
03-02 09:32:31.950 2562 2562 F DEBUG : #02 pc 000156a4 /system/bin/linker (_start+4)
the latest changes to the device tree seems to have fixed this issue. thanx guys. though would love to know what was causing this issue.
Related
All 2.1 rom I tried it produces this error. (Sense-ui does not do it)
When I activate the wireless LAN, the phone shuts down the system process, and after a while the phone restarts.
I also went through several forums and everywhere, it was considered that the nearby AccessPoint-s one of the causes. Probably not good characters with ssid.
So critical, because the only place where I can use wireless LAN (home), and also hangs in the firmware.
This is a log:
Here is relevant part of logcat:
D/HomeLoaders( 757): ----> items cloned, ready to refresh UI
I/wpa_supplicant( 445): CTRL-EVENT-SCAN-RESULTS Ready
W/dalvikvm( 689): JNI WARNING: illegal continuation byte 0xa
W/dalvikvm( 689): string: 'bssid / frequency / signal level / flags / ssid
W/dalvikvm( 689): 00:1d:0f:b2:7c:9e 2417 -53 [WPA2-PSK-CCMP] sHome
W/dalvikvm( 689): 00:60:b3:2a:5a:87 2437 -91 PRAHA9.NET-R14-1
W/dalvikvm( 689): 00:02:72:7e:20:e5 2462 -92 Moje sÝŁ
W/dalvikvm( 689): 00:1b:9e:ef:1f:e7 2412 -93 [WEP] VOIP'
W/dalvikvm( 689): in Landroid/net/wifi/WifiNative;.scanResultsCommand
()Ljava/lang/String; (NewStringUTF)
I/dalvikvm( 689): "android.server.ServerThread" prio=5 tid=15 NATIVE
I/dalvikvm( 689): | group="main" sCount=0 dsCount=0 s=N obj=0x43c9b7e0 self=0x11e6b0
I/dalvikvm( 689): | sysTid=697 nice=-2 sched=0/0 cgrp=unknown handle=1173448
I/dalvikvm( 689): at android.net.wifi.WifiNative.scanResultsCommand(Nat ive Method)
I/dalvikvm( 689): at com.android.server.WifiService.getScanResults(Wifi
Service.java:1113)
I/dalvikvm( 689): at android.net.wifi.WifiManager.getScanResults(WifiMa
nager.java:538)
I/dalvikvm( 689): at com.google.android.location.NetworkLocationProvide
r$2.onReceive(NetworkLocationProvider.java:393)
I/dalvikvm( 689): at android.app.ActivityThread$PackageInfo$ReceiverDis
patcher$Args.run(ActivityThread.java:754)
I/dalvikvm( 689): at android.os.Handler.handleCallback(Handler.java:587 )
I/dalvikvm( 689): at android.os.Handler.dispatchMessage(Handler.java:92 )
I/dalvikvm( 689): at android.os.Looper.loop(Looper.java:123)
I/dalvikvm( 689): at com.android.server.ServerThread.run(SystemServer.j ava:444)
I/dalvikvm( 689):
E/dalvikvm( 689): VM aborting
I/DEBUG ( 682): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 682): Build fingerprint: 'google/passion/passion/mahimahi:2.1-
update1/ERE27/24178:user/release-keys'
I/DEBUG ( 682): pid: 689, tid: 697 >>> system_server <<<
I/DEBUG ( 682): signal 11 (SIGSEGV), fault addr deadd00d
I/DEBUG ( 682): r0 00000358 r1 afe1339d r2 0000000c r3 deadd00d
I/DEBUG ( 682): r4 00000026 r5 4594ed6c r6 fffe59bc r7 fffe59bc
I/DEBUG ( 682): r8 4594fd88 r9 427f3db4 10 427f3da0 fp 0011e6b0
I/DEBUG ( 682): ip ad080160 sp 4594ed10 lr afe1435d pc ad03549a cpsr 20000030
I/MediaUploader( 739): No need to wake up
I/ActivityManager( 689): Start proc com.esmertec.android.jbed for broadcast
com.esmertec.android.jbed/.BootCompleteReceiver: pid=859 uid=10025 gids={
3003, 1006}
D/MediaScannerService( 747): start scanning volume internal
Please help me if you can, and many other users!
Hello,
I would like to ask this question in superSU thread but i am not allowed to post there and it redirects me to this general forum section.
Here is the whole process, which makes me think that it is about superSU.
i have nexus 5 with 4.4.4 which is installed by flashing *.img files directly from recovery and only software i used to do this was adb.exe. Later i used superUS's CF-Auto-Root-hammerhead-hammerhead-nexus5.zip file to root. And i didn't set up any google account, just got catlog app from here and start to read it. At first boot of device, there was no error, nothing in catlog file like below and i didn't feel anything about error while using device. But at second reboot and later on "in this time i just granted su rights to catlog when superSU prompted" i saw this fatal errors in log cat file. These errors happen just after i type sim card's password and it happens in seconds, you feel this just a tiny freezing when you want to browse home to app section but later on, i guess this fatal errors caused all random reboots, i have. Do you have any idea? Please let me know, you may see log cat below, thank you.
Code:
07-27 01:06:14.865 I/ActivityManager(821): Start proc com.android.systemui for service com.android.keyguard/.KeyguardService: pid=891 uid=10012 gids={50012, 1028, 1015, 1035, 3002, 3001}
07-27 01:06:14.885 F/SystemServer(821): BOOT FAILURE making Package Manager Service ready
07-27 01:06:14.885 F/SystemServer(821): java.lang.SecurityException: Unable to find app for caller [email protected] (pid=821) when registering receiver [email protected]
07-27 01:06:14.885 F/SystemServer(821): at com.android.server.am.ActivityManagerService.registerReceiver(ActivityManagerService.java:13021)
07-27 01:06:14.885 F/SystemServer(821): at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1450)
07-27 01:06:14.885 F/SystemServer(821): at android.app.ContextImpl.registerReceiverAsUser(ContextImpl.java:1425)
07-27 01:06:14.885 F/SystemServer(821): at com.android.internal.content.PackageMonitor.register(PackageMonitor.java:84)
07-27 01:06:14.885 F/SystemServer(821): at com.android.server.pm.UserManagerService.systemReady(UserManagerService.java:237)
07-27 01:06:14.885 F/SystemServer(821): at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:10476)
07-27 01:06:14.885 F/SystemServer(821): at com.android.server.ServerThread.initAndLoop(SystemServer.java:893)
07-27 01:06:14.885 F/SystemServer(821): at com.android.server.SystemServer.main(SystemServer.java:1179)
07-27 01:06:14.885 F/SystemServer(821): at java.lang.reflect.Method.invokeNative(Native Method)
07-27 01:06:14.885 F/SystemServer(821): at java.lang.reflect.Method.invoke(Method.java:515)
07-27 01:06:14.885 F/SystemServer(821): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)
07-27 01:06:14.885 F/SystemServer(821): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)
07-27 01:06:14.885 F/SystemServer(821): at dalvik.system.NativeStart.main(Native Method)
07-27 01:06:14.885 W/SystemServer(821): ***********************************************
07-27 01:06:14.905 I/AppOps (821): Pruning old package media/1013: new uid=-1
07-27 01:06:14.905 I/ActivityManager(821): System now ready
Hello,
Tonight i installed 4.4.4. Release 2 and the result was same like 4.4.4 and error happened again with random reboots.
Later i installer Android L and rooted with superSU and get log cat, the above error was not there anymore but there were another errors, and after whole google update error stayed there and caused random reboots again. Log cats below..
Code:
07-27 04:08:45.218 W/Adreno-GSL(2203): <ioctl_kgsl_device_getproperty:663>: mmap failed: errno 22 Invalid argument
07-27 04:08:45.218 I/Adreno-EGL(2203): <qeglDrvAPI_eglInitialize:320>: EGL 1.4 QUALCOMM Build: I10246dbd022c719c705be805d5642cc8fdfbd2a2Date: 03/07/14
07-27 04:08:45.219 I/CanvasContext(2203): Initialized EGL, version 1.4
07-27 04:08:45.238 D/OpenGLRenderer(2203): Enabling debug mode 0
07-27 04:08:45.246 I/art (2261): Heap transition to ProcessStateJankImperceptible took 16.842864ms saved at least 761KB
07-27 04:08:45.305 E/libsigchain(2834): Unable to find next sigaction in signal chain
07-27 04:08:45.305 F/libc (2834): Fatal signal 6 (SIGABRT), code -6 in tid 2834 (main)
07-27 04:08:45.317 I/am_activity_launch_time(793): [0,681945986,eu.chainfire.supersu/.PromptActivity,234,234]
07-27 04:08:45.318 I/ActivityManager(793): Displayed eu.chainfire.supersu/.PromptActivity: +234ms
07-27 04:08:45.412 I/DEBUG (188): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-27 04:08:45.412 I/DEBUG (188): Build fingerprint: 'google/hammerhead/hammerhead:L/LPV79/1236599:user/release-keys'
07-27 04:08:45.412 I/DEBUG (188): Revision: '11'
07-27 04:08:45.412 I/DEBUG (188): pid: 2834, tid: 2834, name: main >>> app_process <<<
07-27 04:08:45.412 I/DEBUG (188): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
07-27 04:08:45.412 W/NativeCrashListener(793): Couldn't find ProcessRecord for pid 2834
07-27 04:08:45.441 I/DEBUG (188): r0 00000000 r1 00000b12 r2 00000006 r3 00000000
07-27 04:08:45.441 I/DEBUG (188): AM write failure (32 / Broken pipe)
07-27 04:08:45.441 I/DEBUG (188): r4 00000006 r5 00000000 r6 00000b12 r7 0000010c
07-27 04:08:45.441 I/DEBUG (188): r8 b6e31000 r9 000000cd sl 0000000c fp 000000cc
07-27 04:08:45.441 I/DEBUG (188): ip 0000000b sp be8066c0 lr b6d10371 pc b6d330d0 cpsr 000f0010
07-27 04:08:45.441 I/DEBUG (188): d0 ffffffffffffffff d1 ffffffffffffffff
07-27 04:08:45.441 I/DEBUG (188): d2 0000000000000000 d3 0000000000000000
07-27 04:08:45.441 I/DEBUG (188): d4 00740061004e002e d5 0041006500760069
Code:
07-27 04:44:08.076 D/GCM (1286): GcmService start Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.gcm.GcmService } com.google.android.gms.INITIALIZE
07-27 04:44:08.076 I/am_create_service(819): [0,84197316,.InitializeIntentService,10009,1315]
07-27 04:44:08.106 I/am_destroy_service(819): [0,84197316,1315]
07-27 04:44:08.230 D/AndroidRuntime(2904): Shutting down VM
07-27 04:44:08.275 I/am_create_service(819): [0,722177709,.CalendarProviderIntentService,10001,2450]
07-27 04:44:08.339 D/AndroidRuntime(2953): Shutting down VM
07-27 04:44:08.402 I/am_destroy_service(819): [0,722177709,2450]
07-27 04:44:08.442 E/libsigchain(2904): Unable to find next sigaction in signal chain
07-27 04:44:08.442 F/libc (2904): Fatal signal 6 (SIGABRT), code -6 in tid 2904 (main)
07-27 04:44:08.467 D/AndroidRuntime(2978): Shutting down VM
07-27 04:44:08.471 I/am_destroy_service(819): [0,537148119,1315]
07-27 04:44:08.488 I/am_create_service(819): [0,25537999,.IndexWorkerService,10009,1315]
07-27 04:44:08.549 D/AndroidRuntime(2993): Shutting down VM
07-27 04:44:08.550 E/libsigchain(2953): Unable to find next sigaction in signal chain
07-27 04:44:08.550 F/libc (2953): Fatal signal 6 (SIGABRT), code -6 in tid 2953 (main)
07-27 04:44:08.554 I/DEBUG (182): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-27 04:44:08.554 I/DEBUG (182): Build fingerprint: 'google/hammerhead/hammerhead:L/LPV79/1236599:user/release-keys'
07-27 04:44:08.554 I/DEBUG (182): Revision: '11'
07-27 04:44:08.555 I/DEBUG (182): pid: 2904, tid: 2904, name: main >>> app_process <<<
07-27 04:44:08.555 I/DEBUG (182): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
07-27 04:44:08.564 W/NativeCrashListener(819): Couldn't find ProcessRecord for pid 2904
07-27 04:44:08.602 I/am_create_service(819): [0,502940508,.AutoCacheSchedulingService,10057,2778]
07-27 04:44:08.606 I/am_destroy_service(819): [0,25537999,1315]
07-27 04:44:08.607 I/DEBUG (182): r0 00000000 r1 00000b58 r2 00000006 r3 00000000
07-27 04:44:08.607 I/DEBUG (182): AM write failure (32 / Broken pipe)
07-27 04:44:08.607 I/DEBUG (182): r4 00000006 r5 00000000 r6 00000b58 r7 0000010c
07-27 04:44:08.607 I/DEBUG (182): r8 b6e0f000 r9 000000cd sl 0000000c fp 000000cc
07-27 04:44:08.607 I/DEBUG (182): ip 0000000b sp bec736c0 lr b6cee371 pc b6d110d0 cpsr 000f0010
07-27 04:44:08.607 I/DEBUG (182): d0 ffffffffffffffff d1 ffffffffffffffff
07-27 04:44:08.607 I/DEBUG (182): d2 0000000000000000 d3 0000000000000000
07-27 04:44:08.607 I/DEBUG (182): d4 00740061004e002e d5 0041006500760069
07-27 04:44:08.607 I/DEBUG (182): d6 0073006500630063 d7 0063006500520073
Hello,
I followed log cat closely, this fatal signal 6 and followed long debug log only happens when an application interacts with superSU expacially when it asks for root access, meaning after first install on default access promt window and after every fresh starting and closing with toast notifications.
This happens on Android L and i am not sure if same thing happens in 4.4.4 by "BOOT FAILURE making Package Manager Service ready" error?
Please somebody let @Chainfire know this issue or bug (not sure), this is my 3 messages on this forum, i cant post this on superSU subforum.
Regards
Hello, i just tried to build NitrogenOS Oreo from source and the build was successful but when i try to boot it it gets stuck in a bootloop.
i ran adb logcat and i got this
(btw im new into this)
Code:
CANNOT LINK EXECUTABLE "/system/bin/app_process32": cannot locate symbol "__android_log_security" referenced by "/system/lib/libandroid_runtime.so"...
05-17 03:14:04.859 1282 1282 W crash_dump32: type=1400 audit(0.0:92): avc: denied { execute_no_trans } for path="/system/bin/crash_dump32" dev="sde19" ino=298 scontext=u:r:crash_dump:s0 tcontext=u:object_r:crash_dump_exec:s0 tclass=file permissive=0
05-17 03:14:04.846 1269 1269 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 1269 (app_process32)
05-17 03:14:04.857 1270 1270 F libc : CANNOT LINK EXECUTABLE "/system/bin/drmserver": cannot locate symbol "__android_log_is_debuggable" referenced by "/system/lib/libcutils.so"...
05-17 03:14:04.858 1270 1270 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 1270 (drmserver)
05-17 03:14:04.862 1274 1274 F libc : CANNOT LINK EXECUTABLE "crash_dump32": cannot locate symbol "__android_log_is_loggable_len" referenced by "/system/lib/libpackagelistparser.so"...
05-17 03:14:04.862 1274 1274 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 1274 (crash_dump32)
05-17 03:14:04.864 1274 1274 F libc : crash_dump helper failed to exec
05-17 03:14:04.864 1274 1274 F libc : failed to wait for crash_dump helper: No child processes
05-17 03:14:04.865 1269 1269 F libc : crash_dump helper failed to exec
05-17 03:14:04.866 1269 1269 F libc : crash_dump helper crashed or stopped
05-17 03:14:04.869 1279 1279 F libc : CANNOT LINK EXECUTABLE "crash_dump32": cannot locate symbol "__android_log_is_loggable_len" referenced by "/system/lib/libpackagelistparser.so"...
05-17 03:14:04.869 1279 1279 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 1279 (crash_dump32)
05-17 03:14:04.859 1284 1284 W crash_dump32: type=1400 audit(0.0:93): avc: denied { execute_no_trans } for path="/system/bin/crash_dump32" dev="sde19" ino=298 scontext=u:r:crash_dump:s0 tcontext=u:object_r:crash_dump_exec:s0 tclass=file permissive=0
not quite sure how can i fix it :crying:
i was wondering if any of the developers had a similar problem when they were building a rom
i also get the same error while trying to boot CosmicOS
EDIT: I just successfully compile and boot CosmicOS nogaut version with surprisingly low amount of bugs for a first boot but it still remains to be seen if it's stable enough. It seems that the boot loop only occurs on Oreo
Android Apk installs but crashes on launch. Tested on multiple devices (Oreo & above)
I have developed a simple Android apk in Kivy (1.11.1) and Python (3.8.1). The Kivy app works fine on my Linux system (Ubuntu 18.0.4) with no error or warning message. However, when I install the apk on my device, the app crashes soon after the splash screen with the below listed error message. It points to a null pointer dereference error. After multiple rounds of testing it appears that the error occurs whenever I import a custom module in my Python code. The code itself is working fine when run on a desktop or laptop as Kivy is a cross-platform framework. It is failing only when run on Android. Any suggestion would be highly appreciated.
--------- beginning of crash
11-16 09:19:19.961 2803 29315 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8 in tid 29315 (Preview3AAThrea), pid 2803 (prov.. @3.0-se)
11-16 09:19:20.044 31254 31254 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-16 09:19:20.045 31254 31254 F DEBUG : Build fingerprint: 'samsung/m10ltedd/m10lte:10/QP1A.190711.020/M105FDDU3CTI3:user/release-keys'
11-16 09:19:20.045 31254 31254 F DEBUG : Revision: '4'
11-16 09:19:20.045 31254 31254 F DEBUG : ABI: 'arm'
11-16 09:19:20.047 31254 31254 F DEBUG : Timestamp: 2020-11-16 09:19:20+0530
11-16 09:19:20.047 31254 31254 F DEBUG : pid: 2803, tid: 29315, name: Preview3AAThrea >>> /vendor/bin/hw/vendor.samsung.hard.. @3.0-service <<<
11-16 09:19:20.047 31254 31254 F DEBUG : uid: 1047
11-16 09:19:20.047 31254 31254 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8
11-16 09:19:20.048 31254 31254 F DEBUG : Cause: null pointer dereference
11-16 09:19:20.048 31254 31254 F DEBUG : r0 00000000 r1 00000000 r2 00000001 r3 00000000
11-16 09:19:20.048 31254 31254 F DEBUG : r4 ed439a80 r5 00000000 r6 00000001 r7 e5870058
11-16 09:19:20.048 31254 31254 F DEBUG : r8 ee41f300 r9 ed439a80 r10 f064d260 r11 e5870060
11-16 09:19:20.048 31254 31254 F DEBUG : ip ef83863c sp e58681a0 lr ef7ab3cb pc ef7ab3cc
11-16 09:19:20.068 31254 31254 F DEBUG :
11-16 09:19:20.068 31254 31254 F DEBUG : backtrace:
11-16 09:19:20.068 31254 31254 F DEBUG : #00 pc 0006a3cc /vendor/lib/libexynoscamera3.so (android::ExynosCameraFrame::getFrameDoneFirstEntity(unsigned int)+12) (BuildId: a9243cc5d0a5792ad1baf4e7cb2b99ed)
I'd like to know how to change the default camera on Android to a USB camera, I'd like to use my webcam to authenticate QR codes, but with emulator, the camera doesn't start, I can only get video through a USB camera (v4l2)
{
"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"
}
I compiled redroid11 from GitHub
Here some logs
Code:
06-20 21:04:15.902 16876 16876 F DEBUG : #08 pc 00003ceb /vendor/lib/hw/[email protected] (virtual thunk to android::hardware::camera::provider::V2_4::implementation::CameraProvider<android::hardware::camera::provider::V2_4::implementation::ExternalCameraProviderImpl_2_4>::~CameraProvider()+75) (BuildId: 61f370932646d54b04cc68702a95f8fa)
06-20 21:04:15.902 16876 16876 F DEBUG : #12 pc 00001aee /vendor/bin/hw/[email protected]4-external-service (BuildId: e02058b00fe96b518e5b0b850ff2870c)
06-20 21:04:15.902 16876 16876 F DEBUG : #13 pc 00001993 /vendor/bin/hw/[email protected] (main+179) (BuildId: e02058b00fe96b518e5b0b850ff2870c)
06-20 21:04:20.913 16884 16884 I [email protected]: [email protected] legacy service is starting.
06-20 21:04:20.913 16883 16883 I [email protected]: External camera provider service is starting.
06-20 21:04:20.925 16884 16884 E [email protected]: Could not load camera HAL module: -2 (No such file or directory)
06-20 21:04:20.925 16884 16884 E [email protected]: getProviderImpl: camera provider init failed!
06-20 21:04:20.925 16883 16883 I [email protected]: loadFromCfg: load external camera config succeed!
06-20 21:04:20.925 16883 16883 I [email protected]: loadFromCfg: device 0 will be ignored by external camera provider
06-20 21:04:20.926 16883 16883 I [email protected]: loadFromCfg: external camera cfg loaded: maxJpgBufSize 3145728, num video buffers 4, num still buffers 2, orientation 0
06-20 21:04:20.926 16883 16883 E HidlServiceManagement: Service [email protected]::ICameraProvider/external/0 must be in VINTF manifest in order to register/get.
06-20 21:04:20.926 16883 16883 E LegacySupport: Could not register service [email protected]::ICameraProvider/external/0 (-2147483648).
06-20 21:04:20.928 16884 16884 E LegacySupport: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
06-20 21:04:20.934 16888 16888 F DEBUG : pid: 16883, tid: 16883, name: android.hardwar >>> /vendor/bin/hw/[email protected] <<<
06-20 21:04:20.937 16888 16888 F DEBUG : #06 pc 0000e293 /vendor/lib/[email protected] (android::hardware::camera::provider::V2_4::implementation::ExternalCameraProviderImpl_2_4::HotplugThread::~HotplugThread()+99) (BuildId: c893ccbbe5cfdc71842b89443e84b793)
06-20 21:04:20.937 16888 16888 F DEBUG : #07 pc 0000e12d /vendor/lib/[email protected] (android::hardware::camera::provider::V2_4::implementation::ExternalCameraProviderImpl_2_4::~ExternalCameraProviderImpl_2_4()+45) (BuildId: c893ccbbe5cfdc71842b89443e84b793)
06-20 21:04:20.937 16888 16888 F DEBUG : #08 pc 00003ceb /vendor/lib/hw/[email protected] (virtual thunk to android::hardware::camera::provider::V2_4::implementation::CameraProvider<android::hardware::camera::provider::V2_4::implementation::ExternalCameraProviderImpl_2_4>::~CameraProvider()+75) (BuildId: 61f370932646d54b04cc68702a95f8fa)
06-20 21:04:20.937 16888 16888 F DEBUG : #12 pc 00001aee /vendor/bin/hw/[email protected] (BuildId: e02058b00fe96b518e5b0b850ff2870c)
06-20 21:04:20.937 16888 16888 F DEBUG : #13 pc 00001993 /vendor/bin/hw/[email protected] (main+179) (BuildId: e02058b00fe96b518e5b0b850ff2870c)
06-20 21:04:24.573 150 281 E CameraService: cameraIdIntToStrLocked: input id 0 invalid: valid range (0, 0)
06-20 21:04:24.573 150 281 I CameraService: CameraService::connect call (PID -1 "com.whatsapp", camera ID ) for HAL version default and Camera API version 1
06-20 21:04:24.573 150 281 E CameraService: shouldRejectSystemCameraConnection: Invalid camera id ,
06-20 21:04:24.573 150 281 W CameraService: Attempting to connect to system-only camera id , connection rejected
06-20 21:04:24.573 1455 16941 W CameraBase: An error occurred while connecting to camera 0: Status(-8, EX_SERVICE_SPECIFIC): '4: validateClientPermissionsLocked:1158: No camera device with ID "" isavailable'
06-20 21:04:25.914 17093 17093 I [email protected]: External camera provider service is starting.
06-20 21:04:25.920 17094 17094 I [email protected].4-service: [email protected] legacy service is starting.
06-20 21:04:25.932 17093 17093 I [email protected]: loadFromCfg: load external camera config succeed!
06-20 21:04:25.932 17093 17093 I [email protected]: loadFromCfg: device 0 will be ignored by external camera provider
06-20 21:04:25.932 17093 17093 I [email protected]: loadFromCfg: external camera cfg loaded: maxJpgBufSize 3145728, num video buffers 4, num still buffers 2, orientation 0
06-20 21:04:25.932 17093 17093 E HidlServiceManagement: Service [email protected]::ICameraProvider/external/0 must be in VINTF manifest in order to register/get.
06-20 21:04:25.932 17094 17094 E [email protected]: Could not load camera HAL module: -2 (No such file or directory)
06-20 21:04:25.933 17093 17093 E LegacySupport: Could not register service [email protected]::ICameraProvider/external/0 (-2147483648).
06-20 21:04:25.933 17094 17094 E [email protected]: getProviderImpl: camera provider init failed!
06-20 21:04:25.935 17094 17094 E LegacySupport: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
06-20 21:04:25.942 17101 17101 F DEBUG : pid: 17093, tid: 17093, name: android.hardwar >>> /vendor/bin/hw/[email protected] <<<
06-20 21:04:25.945 17101 17101 F DEBUG : #06 pc 0000e293 /vendor/lib/[email protected] (android::hardware::camera::provider::V2_4::implementation::ExternalCameraProviderImpl_2_4::HotplugThread::~HotplugThread()+99) (BuildId: c893ccbbe5cfdc71842b89443e84b793)
06-20 21:04:25.945 17101 17101 F DEBUG : #07 pc 0000e12d /vendor/lib/[email protected] (android::hardware::camera::provider::V2_4::implementation::ExternalCameraProviderImpl_2_4::~ExternalCameraProviderImpl_2_4()+45) (BuildId: c893ccbbe5cfdc71842b89443e84b793)
06-20 21:04:25.945 17101 17101 F DEBUG : #08 pc 00003ceb /vendor/lib/hw/[email protected] (virtual thunk to android::hardware::camera::provider::V2_4::implementation::CameraProvider<android::hardware::camera::provider::V2_4::implementation::ExternalCameraProviderImpl_2_4>::~CameraProvider()+75) (BuildId: 61f370932646d54b04cc68702a95f8fa)
06-20 21:04:25.945 17101 17101 F DEBUG : #12 pc 00001aee /vendor/bin/hw/[email protected] (BuildId: e02058b00fe96b518e5b0b850ff2870c)
06-20 21:04:25.945 17101 17101 F DEBUG : #13 pc 00001993 /vendor/bin/hw/[email protected] (main+179) (BuildId: e02058b00fe96b518e5b0b850ff2870c)
artbreguez said:
I'd like to know how to change the default camera on Android to a USB camera, I'd like to use my webcam to authenticate QR codes, but with emulator, the camera doesn't start, I can only get video through a USB camera (v4l2)
Click to expand...
Click to collapse
Hello and good afternoon, @artbreguez
Welcome to XDA. I hope you'll always find and 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