Related
Hey Guyz.!
I know this questions has many answer but I cant get them work.
I tried Reverse Tether paid app from market. Android Reverse Tethering
So any help?
I actually want to use whats app. So plz help
http://forum.xda-developers.com/showthread.php?t=1371345
i use it everyday.
REVERSE TETHERING HELP from amit
-------------------------YOUR PHONE MUST BE ROOTED--------------------------
Hey man!!!!!!!!! i think that you are having trouble to use reverse tethering . just follow the steps bellow:-
1) go to filecrop and type reverse tethering 2.26(11mb) n download it.(i'm not able to post the direct link because i'm a new comer, please understand)
2)now extract it and open it
3)there you will see a file "android tool", run it.
4)Now connect your device make sure that usb debugging is enabled in your device if not, do this:-
menu>settings>developer tools>usb debugging ,just enable it.
5)after that, in the android tool click the refresh device button and after that click on connect.
6)super user may ask you to grant request, allow.
7)ENJOYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
reverse thether
blade8686 said:
-------------------------YOUR PHONE MUST BE ROOTED--------------------------
Hey man!!!!!!!!! i think that you are having trouble to use reverse tethering . just follow the steps bellow:-
1) go to filecrop and type reverse tethering 2.26(11mb) n download it.(i'm not able to post the direct link because i'm a new comer, please understand)
2)now extract it and open it
3)there you will see a file "android tool", run it.
4)Now connect your device make sure that usb debugging is enabled in your device if not, do this:-
menu>settings>developer tools>usb debugging ,just enable it.
5)after that, in the android tool click the refresh device button and after that click on connect.
6)super user may ask you to grant request, allow.
7)ENJOYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Click to expand...
Click to collapse
I am getting connection problem
01-27 12:00:42:402 W/I Connecting to device...
01-27 12:02:36.68 A/D [BL] enqueueNotificationInternal - START, service.tracetool / 10002 / 10824 / null / 1 / Notification(vibrate=null,sound=null,defaults=0x0,flags=0x42)
01-27 12:00:46:031 L/I Reverse tethering started. Process id is 10824
01-27 12:02:36.68 A/I SocketService.onStartCommand. Action = TTServiceStart
01-27 12:02:36.68 A/I UsbThread9.run() needToBeClosed is true
01-27 12:02:36.69 A/I UsbThread : thread main : wait current UsbThread to terminate 0
01-27 12:00:46:222 W/I Wait for android connection ready. If nothing happens now, close the program and retry
01-27 12:00:46:333 W/I waiting android server connection ... 1
01-27 12:02:37.33 A/I UsbThread9 : thread stopped
01-27 12:02:37.69 A/I TunnelController : thread started
01-27 12:02:37.69 A/I UsbThread10 : thread started
01-27 12:02:37.69 A/I UsbThread10 : Create usb socket
01-27 12:02:37.69 A/I UsbThread10 : usbServerSocket : Waiting for the host to connect
01-27 12:00:47:360 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:48:370 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:49:383 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:50:397 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:51:409 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:52:425 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:53:436 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:54:450 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:55:465 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:56:479 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:57:494 W/E connect exception : Socket Error # 10013
Access denied.
01-27 12:00:58:507 W/E connect exception : Socket Error # 10013
Access denied.
Server List
DNS List
192.168.1.1[default]
Using this mod: http://forum.xda-developers.com/showthread.php?t=2436347
we are currently stuck here (no front camera and zoom bug), enabling front camera we got this:
Code:
[COLOR="Red"]E/ ( 274): [AWB Calibration] read fuse ID fail
E/mm-camera( 274): [sensor_getVersion] get version fail
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL[/COLOR]
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
D/Vold ( 245): Receive camera burst event
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
W/S_CameraController( 4045): OIS is not supported.
W/S_CameraController( 4045): Video slow motion is not supported.
W/S_CameraController( 4045): Video Stabilization is not supported.
W/S_CameraController( 4045): Video 720p 60fps is not supported.
W/S_CameraController( 4045): Video HDR is not supported.
W/S_CameraController( 4045): Photo HDR is not supported.
E/S_CameraController( 4045): SupportedList.FlashMode == null
W/S_ZoeController( 4045): exitZoeMode() - Zoe mode is not entered
D/Property( 4045): [ICaptureResolutionManager.PhotoResolution] PHOTO_16_9_3264x1840(3264x1840) -> PHOTO_4_3_640x480(640x480)
D/Property( 4045): [ICaptureResolutionManager.VideoResolution] QHD(960x544) -> VGA(640x480)
E/S_CameraController( 4045): not support FlashMode !!
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
[COLOR="Red"]E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setFocusMode(const android::CameraParameters&):Could not look up str value
E/QCameraHWI_Parm( 260): Invalid focus mode value: continuous-picture[/COLOR] [COLOR="Blue"]-> need framework fix, but it's not a big problem[/COLOR]
E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setParameters(const android::CameraParameters&): 2171, rc = -22
D/Vold ( 245): Receive camera burst event
[COLOR="Red"]E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
E/S_CameraController( 4045): setParameters exception[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
E/mm-camera( 274): camif_client_set_params: camif has associated with obj mask 0x1
E/mm-camera( 274): config_MSG_ID_RESET_ACK CAMIF_PARAMS_ADD_OBJ_ID failed -1
[COLOR="Red"]F/libc ( 274): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4116 (mm-qcamera-daem)[/COLOR][COLOR="Blue"] -> i think it's crashing because of other problems[/COLOR]
I/DEBUG ( 257): debuggerd: 2013-09-20 03:00:40
I/DEBUG ( 257): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 257): Build fingerprint: 'htc/htc_europe/ville:4.2.2/JDQ39/240250.1:user/release-keys'
I/DEBUG ( 257): Revision: '3'
I/DEBUG ( 257): pid: 274, tid: 4116, name: mm-qcamera-daem >>> /system/bin/mm-qcamera-daemon <<<
....
I/DEBUG ( 257): backtrace:
I/DEBUG ( 257): #00 pc 00000000 <unknown>
I/DEBUG ( 257): #01 pc 0005ce0d /system/lib/liboemcamera.so
I/DEBUG ( 257): #02 pc 0002484d /system/lib/liboemcamera.so
I/DEBUG ( 257): #03 pc 0000e4b8 /system/lib/libc.so (__thread_entry+72)
I/DEBUG ( 257): #04 pc 0000dba4 /system/lib/libc.so (pthread_create+160)
I/DEBUG ( 257):
I/DEBUG ( 257): stack:
I/DEBUG ( 257): 4078e800 0003eed4
I/DEBUG ( 257): 4078e804 4043ce21 /system/lib/liboemcamera.so (vfe_config_mode+732)
I/DEBUG ( 257): 4078e808 00000005
I/DEBUG ( 257): 4078e80c 404a32c0
I/DEBUG ( 257): 4078e810 00000001
I/DEBUG ( 257): 4078e814 4078e88c [stack:4116]
I/DEBUG ( 257): 4078e818 00000000
I/DEBUG ( 257): 4078e81c 407b738c [stack:4116]
I/DEBUG ( 257): 4078e820 40436179 /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e824 4043909d /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e828 40438e7d /system/lib/liboemcamera.so
...
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 4144): Cannot init Gesture library[/COLOR] [COLOR="Blue"]-> missing libs? not a big problem btw[/COLOR]
W/S_OperationTimeoutController( 4045): [Timeout] Name : Start preview
W/S_OperationTimeoutController( 4045): [Timeout] Start time : 1379638840004
W/S_OperationTimeoutController( 4045): [Timeout] Timeout : 5000
W/S_OperationTimeoutController( 4045): [Timeout] Call-back executor : [email protected]
W/S_HTCCamera( 4045): notifyCameraThreadBlocked(BlockedInCameraDriver)
W/S_HTCCamera( 4045): onCameraThreadBlocked(BlockedInCameraDriver)
W/S_AutoFocusController( 4045): unlockAutoFocus() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoExposure() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoWhiteBalance() - Null handle
W/S_HTCCamera( 4045): onPause() - mIsUIReady = false
W/AudioService( 920): stream was not muted by this client
E/AudioService( 920): Could not get client death handler for stream: 5
W/S_HTCCamera( 4045): onPause mIdle is false
W/S_HTCCamera( 4045): OnPause - Freeze UI !!!
W/S_HTCCamera( 4045): doOnPause() - start
W/S_HTCCamera( 4045): stopAccelerometer() - isAccelerometerStarted = false
W/S_HTCCamera( 4045): OnPause - hide UI, set mMainLayout invisible
W/S_HTCCamera( 4045): doOnPause() - end
[COLOR="Red"]E/mm-libcamera2( 260): mm_camera_stream_fsm_reg: ioctl VIDIOC_STREAMON failed: rc=-1
E/mm-libcamera2( 260): mm_camera_ch_fn: Failed in STREAM ON
E/mm-libcamera2( 260): mm_camera_action_start: rc=-1[/COLOR] [COLOR="Blue"]-> very important[/COLOR]
E/QCameraHWI_Still( 260): android::status_t android::QCameraStream_Snapshot::startStreamZSL(): Failure starting ZSL stream
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_find_mctl_inst: no match for mctl_id = 1
E/mm-camera( 4144): qcamsvr_process_server_node_event: MSM_V4L2_* - cannot find mctl, id = 1[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
is there a dev that already encountered this problem, and can help us?
@ImagioX1 @E.Cadro @olvrick @Turge @Zarboz
pirlano said:
Using this mod: http://forum.xda-developers.com/showthread.php?t=2436347
we are currently stuck here (no front camera and zoom bug), enabling front camera we got this:
Code:
[COLOR="Red"]E/ ( 274): [AWB Calibration] read fuse ID fail
E/mm-camera( 274): [sensor_getVersion] get version fail
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL[/COLOR]
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
D/Vold ( 245): Receive camera burst event
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
W/S_CameraController( 4045): OIS is not supported.
W/S_CameraController( 4045): Video slow motion is not supported.
W/S_CameraController( 4045): Video Stabilization is not supported.
W/S_CameraController( 4045): Video 720p 60fps is not supported.
W/S_CameraController( 4045): Video HDR is not supported.
W/S_CameraController( 4045): Photo HDR is not supported.
E/S_CameraController( 4045): SupportedList.FlashMode == null
W/S_ZoeController( 4045): exitZoeMode() - Zoe mode is not entered
D/Property( 4045): [ICaptureResolutionManager.PhotoResolution] PHOTO_16_9_3264x1840(3264x1840) -> PHOTO_4_3_640x480(640x480)
D/Property( 4045): [ICaptureResolutionManager.VideoResolution] QHD(960x544) -> VGA(640x480)
E/S_CameraController( 4045): not support FlashMode !!
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
[COLOR="Red"]E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setFocusMode(const android::CameraParameters&):Could not look up str value
E/QCameraHWI_Parm( 260): Invalid focus mode value: continuous-picture[/COLOR] [COLOR="Blue"]-> need framework fix, but it's not a big problem[/COLOR]
E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setParameters(const android::CameraParameters&): 2171, rc = -22
D/Vold ( 245): Receive camera burst event
[COLOR="Red"]E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
E/S_CameraController( 4045): setParameters exception[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
E/mm-camera( 274): camif_client_set_params: camif has associated with obj mask 0x1
E/mm-camera( 274): config_MSG_ID_RESET_ACK CAMIF_PARAMS_ADD_OBJ_ID failed -1
[COLOR="Red"]F/libc ( 274): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4116 (mm-qcamera-daem)[/COLOR][COLOR="Blue"] -> i think it's crashing because of other problems[/COLOR]
I/DEBUG ( 257): debuggerd: 2013-09-20 03:00:40
I/DEBUG ( 257): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 257): Build fingerprint: 'htc/htc_europe/ville:4.2.2/JDQ39/240250.1:user/release-keys'
I/DEBUG ( 257): Revision: '3'
I/DEBUG ( 257): pid: 274, tid: 4116, name: mm-qcamera-daem >>> /system/bin/mm-qcamera-daemon <<<
....
I/DEBUG ( 257): backtrace:
I/DEBUG ( 257): #00 pc 00000000 <unknown>
I/DEBUG ( 257): #01 pc 0005ce0d /system/lib/liboemcamera.so
I/DEBUG ( 257): #02 pc 0002484d /system/lib/liboemcamera.so
I/DEBUG ( 257): #03 pc 0000e4b8 /system/lib/libc.so (__thread_entry+72)
I/DEBUG ( 257): #04 pc 0000dba4 /system/lib/libc.so (pthread_create+160)
I/DEBUG ( 257):
I/DEBUG ( 257): stack:
I/DEBUG ( 257): 4078e800 0003eed4
I/DEBUG ( 257): 4078e804 4043ce21 /system/lib/liboemcamera.so (vfe_config_mode+732)
I/DEBUG ( 257): 4078e808 00000005
I/DEBUG ( 257): 4078e80c 404a32c0
I/DEBUG ( 257): 4078e810 00000001
I/DEBUG ( 257): 4078e814 4078e88c [stack:4116]
I/DEBUG ( 257): 4078e818 00000000
I/DEBUG ( 257): 4078e81c 407b738c [stack:4116]
I/DEBUG ( 257): 4078e820 40436179 /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e824 4043909d /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e828 40438e7d /system/lib/liboemcamera.so
...
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 4144): Cannot init Gesture library[/COLOR] [COLOR="Blue"]-> missing libs? not a big problem btw[/COLOR]
W/S_OperationTimeoutController( 4045): [Timeout] Name : Start preview
W/S_OperationTimeoutController( 4045): [Timeout] Start time : 1379638840004
W/S_OperationTimeoutController( 4045): [Timeout] Timeout : 5000
W/S_OperationTimeoutController( 4045): [Timeout] Call-back executor : [email protected]
W/S_HTCCamera( 4045): notifyCameraThreadBlocked(BlockedInCameraDriver)
W/S_HTCCamera( 4045): onCameraThreadBlocked(BlockedInCameraDriver)
W/S_AutoFocusController( 4045): unlockAutoFocus() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoExposure() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoWhiteBalance() - Null handle
W/S_HTCCamera( 4045): onPause() - mIsUIReady = false
W/AudioService( 920): stream was not muted by this client
E/AudioService( 920): Could not get client death handler for stream: 5
W/S_HTCCamera( 4045): onPause mIdle is false
W/S_HTCCamera( 4045): OnPause - Freeze UI !!!
W/S_HTCCamera( 4045): doOnPause() - start
W/S_HTCCamera( 4045): stopAccelerometer() - isAccelerometerStarted = false
W/S_HTCCamera( 4045): OnPause - hide UI, set mMainLayout invisible
W/S_HTCCamera( 4045): doOnPause() - end
[COLOR="Red"]E/mm-libcamera2( 260): mm_camera_stream_fsm_reg: ioctl VIDIOC_STREAMON failed: rc=-1
E/mm-libcamera2( 260): mm_camera_ch_fn: Failed in STREAM ON
E/mm-libcamera2( 260): mm_camera_action_start: rc=-1[/COLOR] [COLOR="Blue"]-> i don't think it's too much important[/COLOR]
E/QCameraHWI_Still( 260): android::status_t android::QCameraStream_Snapshot::startStreamZSL(): Failure starting ZSL stream
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_find_mctl_inst: no match for mctl_id = 1
E/mm-camera( 4144): qcamsvr_process_server_node_event: MSM_V4L2_* - cannot find mctl, id = 1[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
is there a dev that already encountered this problem, and can help us?
@ImagioX1 @E.Cadro @olvrick @Turge @Zarboz
Click to expand...
Click to collapse
grep is your friend
MCTL_COMPID_ACTUATOR
Zarboz said:
grep is your friend
MCTL_COMPID_ACTUATOR
Click to expand...
Click to collapse
i know, the problem is in liboemcamera.so, mctl_init & sensor_init are changed, and i'm looking at this
i was just asking if One XL devs already solved this problem in the past or not, or if you have some hints
In One S liboemcamera there is one only "MCTL_COMPID_ACTUATOR handle is NULL" reference:
.rodata:000BBAEA aMctl_compid__0 DCB "MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
In One liboemcamera there are three reference:
.rodata:000AAB54 aMctl_compid_ac DCB "MCTL_COMPID_ACTUATOR handle is NULL",0xA,0 ; DATA XREF: sub_1F240+A64o
.rodata:000C650C aSMctl_compid_0 DCB "%s MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
.rodata:000C7EF4 aSMctl_compid_2 DCB "%s: MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
the one causing the error is the first
in dmesg, error happens beetween this two lines:
<6>[ 141.009064] c1 4731 [CAM] mt9v113_ioctl, cfgtype = 10
(reached with original cam and zoe mod)
it's in drivers/media/video/msm/sensor/mt9v113_v4l2.c
function: int mt9v113_sensor_config(void __user *argp)
<6>[ 141.009430] c1 4731 [CAM] vfe32_proc_general: cmdID = START
(start is not reached with Zoe mod)
it's in drivers/media/video/msm/vfe/msm_vfe32.c
function: static int vfe32_proc_general(
struct msm_cam_media_controller *pmctl,
struct msm_isp_cmd *cmd,
struct vfe32_ctrl_type *vfe32_ctrl)
Will be great to be ported this feature and new [ROM] MaximusHD 10.0.0 - 4.2.2 Sense 5 -> will be the best one for ONE S
Will wait this with big impatience to be fixed and work of my favorite phone - One S
Thanks
i'm using this tutorials to try to debug liboemcamera.so:
http://forum.xda-developers.com/showthread.php?t=2050393
http://forum.xda-developers.com/showthread.php?t=1374345
but i'm currently stuck here:
http://forum.xda-developers.com/showpost.php?p=45827106&postcount=13
EDIT: solved few problem
but now, i'm stuck, again
ptrace: I/O error.
If someone want to try to debug native android library using IDA Pro...
[console 1] -> one time only
adb push the gdbserver from ndk to data/local/tmp
adb shell su
adb chmod 755 gdbserver
[console 2] -> don't forget it or debug client will not connect!
adb forward tcp:1111 tcp:1111
[console 3] -> start binary you want to debug (or binary that load library that you want to debug liboemcamera.so in my case, using mm-qcamera-app) -> leave it opened
adb shell
su
echo 0 > /proc/sys/kernel/randomize_va_space (this is to disable ASLR, that cause library to be loaded at random address)
cd system/bin
./mm-qcamera-app
1 or 2
[console 4]->leave it opened
adb shell
su
echo 0 > /proc/sys/kernel/randomize_va_space (just to be sure)
ps (look at PID of mm-qcamera-app)
cd data/local/tmp
./gdbserver --attach :1111 PID_NUMBER_of_mm-qcamera-app
[console 5]
(adb pull system/lib and system/bin here->C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86_64/bin)
(start gdb from ndk from command line)
gdb.exe
(gdb) set height 0
(gdb) set solib-search-path ./
(gdb) directory C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86_64/bin
(gdb) target remote 127.0.0.1:1111
Remote debugging using 127.0.0.1:1111
0x4005fe48 in ?? ()
(gdb) info sharedlibrary
Reading symbols from C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/preb
uilt/windows-x86_64/bin/mm-qcamera-app...done.
WARNING: no debugging symbols found in C:/android-ndk-r9/toolchains/arm-linux-an
droideabi-4.6/prebuilt/windows-x86_64/bin/mm-qcamera-app.
Either the binary was compiled without debugging information
or the debugging information was removed (e.g., with strip or strip -g).
Debugger capabilities will be very limited.
For further information: http://wiki/Main/GdbFaq#No_debugging_symbols_found
From To Syms Read Shared Object Library
0x40003240 0x4000b978 No C:/android-ndk-r9/toolchains/arm-linux-andro
ideabi-4.6/prebuilt/windows-x86_64/bin/system/bin/linker
0x40055940 0x40085d0c No libc.so
0x400a07f4 0x400a0998 No libstdc++.so
0x400a4e80 0x400b5164 No libm.so
0x40044180 0x40045d44 No liblog.so
0x40027a18 0x4003059c No libcutils.so
0x4025f6a0 0x40263008 No libgemini.so
0x4022f578 0x402543cc No libmmjpeg.so
0x400ca8b0 0x40161250 No liboemcamera.so
0x40296638 0x40296b50 No libmmstillomx.so
0x402a1494 0x402a1630 No libimage-omx-common.so
0x4029a658 0x4029e414 No libimage-jpeg-enc-omx-comp.so
0x4028a284 0x40291a5c No libmmcamera_interface2.so
(gdb)
NOW you have information about library base address! Nice! Copy and paste these information
Now you can just use CTRL+C on console 4, and execute instruction for console 4 again, so we can debug using IDA this time
(IDA)
for new versions->Debugger, Debugger option, option, uncheck "Use hardware temporary breakpoints"
Debugger,Switch Debugger,Remote GDB debugger and check Set as default debugger
Debugger, Process option, applicazion path (../system/bin/blabla), input file (same or ../system/lib/libblabla.so if debugging lib), Hostname: localhost, Port 1111 (or select youself, you will need to use it for all commands) and check "Set as default network setting"
Now load the file you want to debug
File->Open->liboemcamera.so in my case->Ok/Load->Check "Manual load" from the popup->OK->Input 0:400ca8b0 in my case (base address)->Load all section or section that you need->Yes
Wait for autoanalysis, and do some static analysis by yourself, set some breakpoint, etc,etc
When you are ready to debug: Debugger,Start process, Yes
TADA! The ****ing IDA+gdb should now be able to do step by step debug, but i got a ****ing ptrace: I/O error.
using HTC One Mini libs + updating kernel camera parts from HTC One Mini source, front camera is working good, but rear camera quality is really really bad, need a fix
i'll post an alpha mod soon
zoom bug (green rectangle on jpeg) is still present
EDIT: quality became bad because of wrong Auto White Balance not working good with M4 libs, so with a clean installation it will still working good, but if you came from Zoe fix from Magio, you will need to go back to stock libs/camera apps or do a fresh installation
zoe is working but need camera.apk modding to force it (it should be easy, since apk can be decompiled almost to source code)
install over a stock camera
kernel with M4 kernel camera patch: http://www.4shared.com/zip/CRNRFvCD/fabane_ville_m4_cam_26_09_13_v.html
test M4 libs+camera: http://www.4shared.com/zip/wW302ToJ/FixedZoeMagioV4_M4_ville.html
front facing camera is working, zoe needs to be enabled camera.apk side
pirlano said:
install over a stock camera
kernel with M4 kernel camera patch: http://www.4shared.com/zip/CRNRFvCD/fabane_ville_m4_cam_26_09_13_v.html
test M4 libs+camera: http://www.4shared.com/zip/wW302ToJ/FixedZoeMagioV4_M4_ville.html
front facing camera is working, zoe needs to be enabled camera.apk side
Click to expand...
Click to collapse
Well this work over your old kernel to make the one xl roms boot
Sent from my HTC One S using Tapatalk 2
yes, camera part only is changed, tomorrow i'll work on camera.apk
pirlano said:
yes, camera part only is changed, tomorrow i'll work on camera.apk
Click to expand...
Click to collapse
Ok cool need any help send me a pm
Sent from my HTC One S using Tapatalk 2
Hey guys, I know this is still in development but when finished will it work with the Maximus Rom?
Sent from my HTC One S using xda app-developers app
razlack said:
Hey guys, I know this is still in development but when finished will it work with the Maximus Rom?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
the question is not "when", but, "if"
i'll start lessons next week, so i will be unable to continue
EDIT:
today, instead of looking at m4 camera.apk, i tryed to fix ffc with stock kernel and m7 libs, i think i have found the solution, don't know if it will work, but it's the better idea that i have found until now
EDIT2:
mt9v113 seems to be incompatible with m7 libs, cannot found a solution, we need an experienced arm hacker or hex-rays arm decompiler (if someone use it at work, license is too expensive for home users)
an ather way it's to create a mt9v113_act.c driver, but i think i'm not able to do that, and if it will work, but maybe a dummy one will work too, will try when i have time
for now the only way it's to use m4 libs, so camera.apk needs hacking (this is much more easy), i will try tomorrow
I'm also trying to understand what's causing the zoom bug...
also with both m4 and m7 libs (with kernel patches to make camera working) manual touch autofocus seems to be buggy with slow motion mode and with 60fps mode
and camera auto white balance need a fix, i'm starting to think that it's better to mod our stock camera, without zoe...****ing close source libs...
Hi
I updated my Google Play services to latest and I have been getting this notification when I go to Internet wifi or mobile data.
authorization problem if the problem persists please log in and log out and try it again.
I do not want to make factory reset until CM12 comes out.
here is logcat
Code:
--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
E/wpa_supplicant( 2513): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/WifiStateMachine( 794): Unexpected BatchedScanResults :null
E/wpa_supplicant( 2513): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/ConnectivityService( 794): Unexpected mtu value: [email protected]
E/PlayEventLogger( 3088): Invalid device id 9cb3889439509678
E/PhoneMonitor( 3153): onOtaspChanged old =0, new =3
E/AudioManagerAndroid( 3182): BLUETOOTH permission is missing!
E/AudioManagerAndroid( 3385): BLUETOOTH permission is missing!
F/ActivityManager( 794): Service ServiceRecord{42866038 u0 com.google.android.music/.net.NetworkMonitor} in process ProcessRecord{42e61648 3088:com.google.android.music:main/u0a65} not same as in map: null
F/ActivityManager( 794): Service ServiceRecord{427a3950 u0 com.google.android.music/.preferences.MusicPreferenceService$MusicPreferenceServiceBinder} in process ProcessRecord{42e61648 3088:com.google.android.music:main/u0a65} not same as in map: null
E/AuthorizationBluetoothService( 1571): Proximity feature is not enabled.
E/GCoreFlp( 1608): Bound FusedProviderService with LocationManager
E/AudioManagerAndroid( 3758): BLUETOOTH permission is missing!
E/dalvikvm( 3798): Could not find class 'android.app.Notification$Action$Builder', referenced from method f.a
E/dalvikvm( 3798): Could not find class 'android.app.RemoteInput[]', referenced from method f.a
E/SQLiteLog( 3798): (1) no such table: mmsconfig
E/Babel ( 3798): canonicalizeMccMnc: invalid mccmnc nullnull
P.S: I have removed google play services and updated it back still this problem is there. Then when I change my language to English notification stays in my language
EDIT: It is pure stock no Root or anything!
Same error
I have the same error "PlayEventLogger( 3088): Invalid device id" on my Moto G 1st gen
Android IPC binder throwing "failed to retrieve pid" in Samsung Galaxy S6 Nougat 7.0
Hi,
1). I just updated my Samsung Galaxy S6 device to Nougat 7.0.
2). Then after i rooted the phone, put the device into SELINUX permissive mode by doing the following command.
setenforce 0
3).Downloaded and compiled "SM-G920I_SWA_NN_Opensource" from opensource.samsung.com site.
4).Flash the kernel image using mkbootimg
5).Then i installed my android test application which calls IPC binder native service methods (testservice) from JNI (IPC client). For the first time after installation, application is able to get the testservice binder object if i called as below in JNI file,
binder = sm->getService(android::String16("testservice"));
6).But from the second time onwards i am getting the following error,
09-14 19:42:51.217 3177 3177 E ServiceManager: SELinux: getpidcon(pid=0) failed to retrieve pid context.
09-14 19:42:51.218 9675 10155 I ServiceManager: Waiting for service testservice...
09-14 19:42:51.422 3721 6035 D TelephonyManager: getAllCellInfo : Caller (PID / UID / TID): 3721 / 1000 / 6035
09-14 19:42:52.220 3177 3177 E ServiceManager: SELinux: getpidcon(pid=0) failed to retrieve pid context.
09-14 19:42:52.221 9675 10155 I ServiceManager: Waiting for service testservice..
Getting the above logs continuously even though the testservice is running in the background.
Please help to sort out the issue.
Hello sr4shantan,
Were you able to resolve the issue? I am facing similar issue on Samsung GS7 Edge phone after upgrading to Nougat 7.0. Any pointers to help resolve the issue would be appreciated.
Thanks
sr4shantan said:
Hi,
1). I just updated my Samsung Galaxy S6 device to Nougat 7.0.
2). Then after i rooted the phone, put the device into SELINUX permissive mode by doing the following command.
setenforce 0
3).Downloaded and compiled "SM-G920I_SWA_NN_Opensource" from opensource.samsung.com site.
4).Flash the kernel image using mkbootimg
5).Then i installed my android test application which calls IPC binder native service methods (testservice) from JNI (IPC client). For the first time after installation, application is able to get the testservice binder object if i called as below in JNI file,
binder = sm->getService(android::String16("testservice"));
6).But from the second time onwards i am getting the following error,
09-14 19:42:51.217 3177 3177 E ServiceManager: SELinux: getpidcon(pid=0) failed to retrieve pid context.
09-14 19:42:51.218 9675 10155 I ServiceManager: Waiting for service testservice...
09-14 19:42:51.422 3721 6035 D TelephonyManager: getAllCellInfo : Caller (PID / UID / TID): 3721 / 1000 / 6035
09-14 19:42:52.220 3177 3177 E ServiceManager: SELinux: getpidcon(pid=0) failed to retrieve pid context.
09-14 19:42:52.221 9675 10155 I ServiceManager: Waiting for service testservice..
Getting the above logs continuously even though the testservice is running in the background.
Please help to sort out the issue.
Click to expand...
Click to collapse
Android 11 here: Lineage 18.1 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)
LEGAL
https://lineageos.org/legal/
You flash this ROM on own risk!
XDA:DevDB Information
Lineage 17 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)
Multi ROM from sources supporting devices:
Sharp Aquos S2 4/64 -SS2/C10,
Sharp Aquos S2 6/128 -SAT,
Sharp Aquos S3 -sdm630 (HH1/HH6).
Sharp Aquos P6
Nokia x6 (DRG)
Contributors/Maintainers
heineken78
ROM OS Version: Android 10
ROM Kernel: CAF 4.4.205
ROM Firmware Required: Minimum update installed 2130WW/CN -for S2. For S3 - D350KR, Nokia DRG - Android 9-10.
Based On: Android 10- Lineage 17.1
Recovery: TWRP included.
Device sources: here
Gapps: Not included. Recommend to use only NANO version, because it includes necessary apps like Welbeing
Data Encryption: encrypted;
Do not: use boot(twrp) or vendor with other older/stock roms.
Version Information
Status: Beta
Created 2019-11-03
Last Updated LOS 17.1 2020-09-02
Sources: https://github.com/Eddie07
DOWNLOAD:
Gdrive folder
Changelog 02.09.2020:
Lineage OS 17.1 02/09/20 for SAT/SS2/HH6/HD1
-kernel: optimize power driver;
-kernel: fix mdsi panel on from suspend crushes;
-vendor/system:implement from sources Bluetooth QTI;
-vendor/System:implement from sources perf QTI;
-vendor/system:implement com.qualcomm.gps and drivers from sources;
-kernel/system/vendor: new touchscreen gestures;
-system: more options for Android 10 gestures;
-system: disable magnet sensor;
-system: implement new telecom framework from sources;
-system: sim toogle swithes;
-vendor/system: audio enhancements.
-selinux fixes;
-GSI:flash and go.
-other.
Changelog 07.08.2020:
-remove restrictions for audio records
-fixed auto recording option in Dialer
-icon packs support option for LA Trebuchet: nova, etc.
-long screenshot (Q from ASUS);
-enabled show mv of QC in lockscreen.
-fixes screen on bug after suspend
Changelog 02.08.2020:
Kernel:
-Livedisplay for S2 & S3 & NOkia DRG; -Fast charging S2;
System:
-ARcore support without Magisk;
-Dialer: autorecording;
-Quick internet change via QCTiles (multisim); -Imitation of wifi for android when using a mobile network: persist.force.unmetered = true: -Display Profiles (4) for S2 & S3
Vendor:
- updating halls; - selinux fixes; - fix for gsi boot; - other garbage to make everything work.
Changelog 13.05.2020:
-updated recovery 3.4.0: supports OTA updates, key decryption works;
-added custom face unlock: may need to assign camera perms manually;
-fixed sensors init issue;
-updated vendor.
Note: due to fixes in encryption this version needs fresh boot after format! Backup your data.
Use old backup, and apply gapps zip only after the first boot of system, dont boot to recovery after formatting.
LOS 17.1 beta 13b-04-2020
-fixed selinux denials: sensors issue, ril;
LOS 17.1 beta 13-04-2020
-LOS Android update android-10.0.0_r33 (05.04)
-added Nokia DRG (x6) support
-fixed configs media -front camera video fail fix in gcam.
-updated audio configs to Q.
-selinux still in testing.
LOS 17.1 beta 23-02-2020
-Able to disable sim card (if 2)- experimental;
-Lineage vendor implementations: Off screen gestures; Adjustable vibrations ( 3 levels);- More overlays.
- yuv support;
Also:
Kernel:
Power, sound, display changes, updated latest wifi driver. Also defined min brightness and tfa chip switching via nodes.
System:
Extra Minimum brightness option, reorganized, added settings, implementation of google personalisation (work but Screen Attention fails) no need gapps. 6x5 grid for launcher, option to add quick tile rows.
Vendor:
Made real blue accent color pickable, sound chip tweaking.
Still to do:virtual displays and wfd. (I think problem is hwc sources, need fix later)
LOS 17.1 daily 04-02-2020
-VENDOR: fixes wifi sharing (want working in last two builds), fixed diag_lsm error,
added support of external usb cameras.
LOS 17.1 daily 02-02-2020
-KERNEL: power drain fix to all previous kernels from 28.12 due hotplug conflict with PERF2.0 hal;
merged with LA.UM.8.2.r2-00700-sdm660.0;
updated qcacld (wifi);
not tested with s3.
-SYSTEM: Latest LOS updates, more telephony implementations from nokia stock Q;
-VENDOR: LOS updates, qcom caf updates, more display implementations.
LOS 17.1 test 08-01-2020
-New LOS Android;
-Kernel battery control changes (s2)
-gps enchantment, phone enchantments.
05-01-2020
-kernel: thermal related fixes.
-system: Snap camera replace by stock FIH cam, qcom ril framework blobs remade.
-vendor: manual network selection fix, new thermal impl.Fixed compatibility with GSI roms: camera and softkey navigation bar enabled.
25-12-2019
Kernel:
-merged 4.4.205;
-camera fix for gcam, dualcam; use this cam with dualcam enabled.
If gcam keeps crashing disable dualcam: persist.vendor.camera.expose.aux=0
-showing battery type (C10/S2);
System and Vendor:
-LOS up-to-date;
-implementation on new qcom encryption, booting faster;
-LOS beta circle battery icon ;
Note if you find that media folder is not getting encrypted with key/password - make full format from twrp and boot with current version.
14-12-2019
service pak N141219
28-11-2019
kernel: changes in kernel config
system: LOS 17.1 upd up 27.11
vendor: upd ril, qti, camera blobs, fixed PERF drain, fix bt lags, add APTX Bt codec.
-Rounded corners can be now disabled via vendor/build.prop.
-GUI of S3 of S2 can be chosen from developers settings (remain for GSI too)
17-11-2019
Update Android 10.0.0_r11
15-11-2019
-supports Sharp Aquos S3 models -HH1 and HH6!
-Los up-to-date
05-11-2019
-kernel updated to 4.4.194 (caf LA.UM.8.2.r1-04800-sdm660.0)
-CAMERA: latest camera vendor blobs Q from 2060 Nokia PL2 (test option prop persist.cam.dv=(PL2/B2N/C1N) for camera hal)
-PERFORMANCE: PERF 2.0 fixed
-LINEAGE: current Lineage updates from mainstream(not much)
-SOUND: revert to stock soundtrigger
-VNDK rebuild with Q rules
-added many enhancements in build.props
03-11-2019
First release
Installation
1. First time
Enter twrp or from fastboot and flash images: boot, system, vendor. Reboot back recovery and format data. Install Gapps same time (as option).Reboot to new system.
2. Next updates/upgrades
Enter twrp and flash new images. If you had installed Gapps, flash same zip file o gapps. Reboot to system.
Pls note: Due to changes in encryption, if your data is before July 2020, you will have to format data to be able to use newer roms.
Bugs:
-Minor LOS bugs.
-You will find may be
Please donate if you want to support my work.
I'm testing rom from yesterday. Updated from treble 3.4
Does't show % battery in status bar and the battery icon can't be changed.
There is a problem when I kill applications, it shows a problem with the launcher - operation stops and cant kill applikactions.
Some app from playstore like revolut isn't compatybile with 17.
Gcam working.
Thx for great work.
iiandrusii said:
I'm testing rom from yesterday. Updated from treble 3.4
Does't show % battery in status bar and the battery icon can't be changed.
There is a problem when I kill applications, it shows a problem with the launcher - operation stops and cant kill applikactions.
Some app from playstore like revolut isn't compatybile with 17.
Gcam working.
Thx for great work.
Click to expand...
Click to collapse
% of battery is still to do (Linage bug), there are others too..
About error, may be its because of current launcher problem. I don't have such.
I used vendor rom gsi I installed the camera and the flash didn't work
amiali said:
I used vendor rom gsi I installed the camera and the flash didn't work
Click to expand...
Click to collapse
I'm not able to test GSI's, pls bugs with LOS17 system/vendor. Try another GSI.
I tested three gsi models. The camera and the flash don't work
Hello heineken78. First of all thank you very much for all your work and help with this device.
I wanted to report 3 problems I saw with the ROM:
1) I cannot use NFC: when placing the NFC card near the phone NFC trigger reacts (it blocks, disables and enables) but it doesn't seem to work. The same works, for example, on 4.1. Is there something I could try?
2) I couldn't find a way to disable fingerprint actions on screen on when using gestures, which makes it trigger sometimes accidentally.
3) Data doesn't seem to be encrypted. When accessing TWRP it doesn't ask for a password and I can read sdcard without issues. Not sure if this is common with Android 10 as of yet.
Other than that, the ROM seems to be working perfectly, which is a lot since Android Q is really new.
Thanks!
jokolom said:
1) I cannot use NFC: when placing the NFC card near the phone NFC trigger reacts (it blocks, disables and enables) but it doesn't seem to
work. The same works, for example, on 4.1. Is there something I could try?
Click to expand...
Click to collapse
NFC works, people use safetynetfix and pay with gpay app
jokolom said:
2) I couldn't find a way to disable fingerprint actions on screen on when using gestures, which makes it trigger sometimes accidentally.
Click to expand...
Click to collapse
to do
jokolom said:
3) Data doesn't seem to be encrypted. When accessing TWRP it doesn't ask for a password and I can read sdcard without issues. Not sure if this is common with Android 10 as of yet.
Click to expand...
Click to collapse
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.
heineken78 said:
NFC works, people use safetynetfix and pay with gpay app
to do
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.
Click to expand...
Click to collapse
I have reinstalled LOS17 to retry these things on my phone, and this is the summary:
- Encryption: OK. I have now verified that after installing the ROM, wiping data and rebooting, data in TWRP shows as encrypted even though password will not match like you say (file names appear as garbled characters) so this seems to be working OK.
- NFC: I still cannot make NFC work. I have installed safetypatch on Magisk, CTS profile and basic integrity show as OK on Magisk. Not sure what makes NFC not work, maybe I'm missing something.
- Notification LED: I cannot see notification LED working after receiving a notification, such as Whatsapp.
- Warning message on boot: a warning message triggers on system reboot. This is a minor detail since it's just an informative message.
Other than that, everything seems to be working correctly. I will keep using this ROM as a daily driver and report any other problem I can see.
Thank you!
heineken78 said:
NFC works, people use safetynetfix and pay with gpay app
to do
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.
Click to expand...
Click to collapse
After installing latest version (0611) now NFC card makes sound when it's near the phone and opens NFC app. However, it seems to crash. I have taken a logcat regarding NFC problem. These are the following lines worthy of notice, please tell me if this helps:
Code:
11-06 12:35:07.189 11571 11618 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'short android.os.Bundle.getShort(java.lang.String)' on a null object reference
11-06 12:35:07.189 11571 11618 E AndroidRuntime: at android.nfc.tech.NfcA.<init>(NfcA.java:76)
11-06 12:35:07.189 11571 11618 E AndroidRuntime: at android.nfc.tech.NfcA.get(NfcA.java:62)
Code:
11-06 12:35:07.853 3646 11670 E libnfc_nci: [ERROR:phNxpExtns.cpp(220)] Error Sending msg to Extension Thread
11-06 12:35:07.854 879 879 D NxpExtns: find found MIFARE_READER_ENABLE=(0x1)
11-06 12:35:07.854 879 879 D NfccPowerTracker: NfccPowerTracker::ProcessCmd: Enter,Recieved len :4
Code:
11-06 12:35:59.782 10874 10874 I RenderThread: type=1400 audit(0.0:846): avc: denied { execute } for path="/vendor/lib/hw/gralloc.sdm660.so" dev="mmcblk0p80" ino=776 scontext=u:r:untrusted_app_27:s0:c168,c256,c512,c768 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
According to logcat, even though it doesn't work, it seems to know the card type (mifare):
Code:
11-06 12:35:10.155 758 3327 D NxpHal : NxpNci: RF Interface = MIFARE
11-06 12:35:10.155 758 3327 D NxpHal : NxpNci: Protocol = MIFARE
Thank you!
amiali said:
I tested three gsi models. The camera and the flash don't work
Click to expand...
Click to collapse
release 06/11/19 fixes this issue.
jokolom said:
According to logcat, even though it doesn't work, it seems to know the card type (mifare):
Click to expand...
Click to collapse
config nfc-nxp.conf needs to be fixed to new drivers.
unfortunately im not able to use nfc at all on my SAT - antenna is broken.
so someone has to do it...
heineken78 said:
config nfc-nxp.conf needs to be fixed to new drivers.
unfortunately im not able to use nfc at all on my SAT - antenna is broken.
so someone has to do it...
Click to expand...
Click to collapse
I have found this file: /vendor/etc/libnfc-nxp.conf. Is that the file you reference to?
What can I do to help? I have no problem trying thing but I would need some pointers on what should be changed.
Thank you
Here's : /vendor/etc/libnfc-nxp.conf from 2080WW SAT (stock Oreo).
View attachment libnfc-nxp.zip
paulzie said:
Here's : /vendor/etc/libnfc-nxp.conf from 2080WW SAT (stock Oreo).
View attachment 4869289
Click to expand...
Click to collapse
I have just tried it. Instead of crashing, it will get stuck while trying to read the NFC card. Moreover, the NFC settings get stuck as well.
Thanks
Many GCam mod versions stop to get HDR+ shots at some point. Usually it start with exception in UI handler thread:
11-07 20:51:03.620 6899 7544 I CAM_PhotoCaptureSession: [409d074|IMG_20191107_205058] saveAndFinish
11-07 20:51:03.621 6899 7544 W System.err: java.util.concurrent.ExecutionException: java.lang.Exception
11-07 20:51:03.621 6899 7544 W System.err: at oxp.a(Unknown Source:20)
11-07 20:51:03.621 6899 7544 W System.err: at oxp.get(Unknown Source:475)
11-07 20:51:03.621 6899 7544 W System.err: at oxz.get(Unknown Source:0)
11-07 20:51:03.621 6899 7544 W System.err: at lqi.b(Unknown Source:6)
11-07 20:51:03.622 6899 7544 W System.err: at iqu.a(Unknown Source:46)
11-07 20:51:03.622 6899 7544 W System.err: at hfd.run(Unknown Source:44)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
11-07 20:51:03.622 6899 7544 W System.err: at java.lang.Thread.run(Thread.java:919)
11-07 20:51:03.622 6899 7544 W System.err: at loy.run(Unknown Source:5)
11-07 20:51:03.622 6899 7544 W System.err: Caused by: java.lang.Exception
11-07 20:51:03.622 6899 7544 W System.err: at lqi.a(Unknown Source:4)
11-07 20:51:03.622 6899 7544 W System.err: at frh.d(Unknown Source:35)
11-07 20:51:03.622 6899 7544 W System.err: at egc.a(Unknown Source:152)
11-07 20:51:03.622 6899 7544 W System.err: at eeg.y(Unknown Source:158)
11-07 20:51:03.622 6899 7544 W System.err: at eeg.o(Unknown Source:32)
11-07 20:51:03.622 6899 7544 W System.err: at efb.onShutterButtonClick(Unknown Source:44)
11-07 20:51:03.622 6899 7544 W System.err: at jyl.onShutterButtonClick(Unknown Source:25)
11-07 20:51:03.622 6899 7544 W System.err: at com.google.android.apps.camera.ui.shutterbutton.ShutterButton.performClick(Unknown Source:98)
11-07 20:51:03.622 6899 7544 W System.err: at android.view.View.performClickInternal(View.java:7117)
11-07 20:51:03.623 6899 7544 W System.err: at android.view.View.access$3500(View.java:801)
11-07 20:51:03.623 6899 7544 W System.err: at android.view.View$PerformClick.run(View.java:27351)
11-07 20:51:03.623 6899 7544 W System.err: at android.os.Handler.handleCallback(Handler.java:883)
11-07 20:51:03.623 6899 7544 W System.err: at android.os.Handler.dispatchMessage(Handler.java:100)
11-07 20:51:03.623 6899 7544 W System.err: at android.os.Looper.loop(Looper.java:214)
11-07 20:51:03.623 6899 7544 W System.err: at android.app.ActivityThread.main(ActivityThread.java:7356)
11-07 20:51:03.623 6899 7544 W System.err: at java.lang.reflect.Method.invoke(Native Method)
11-07 20:51:03.623 6899 7544 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
11-07 20:51:03.623 6899 7544 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
And then no more shots could be taken until rebooted (probably camera left in illegal state after exception):
11-07 20:51:27.555 6899 7388 E CAM_HdrPBurstTkr: Failed to receive any frames. Aborting capture for shot 6
11-07 20:51:27.558 6899 7388 I CAM_HdrPShotParams: HDR+ pipeline reported shotId 6 was aborted.
11-07 20:51:27.559 6899 6899 I CAM_VirtualCameraManage: Disconnecting camera 0 asynchronously.
11-07 20:51:27.559 6899 6936 I CAM_CamDevLsnrShim: Camera device 1548342258(0) has been disconnected.
11-07 20:51:27.559 6899 7388 W libgcam : [pipeline_manager.cc:853]: AbortShot: Shot aborted by AbortShot() during capture.
11-07 20:51:27.559 6899 6936 I CAM_VirtualCameraManage: Camera device 0 was closed.
11-07 20:51:27.560 6899 6899 I CAM_CptrBtnReadiness: addCameraReadinessCallback: cameraReadiness=Obs.of{false}
11-07 20:51:27.563 6899 7388 I CAM_PictureTakerImpl: availability: get=true ret=filtered{DerefObs{filtered{TransformedObs{[email protected], [email protected]}}}} [email protected]
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: PictureTaker command failed: [email protected][status=SUCCESS, result=[[email protected]]]
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: mbl: HDR+ shot didn't succeed
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at den.a(Unknown Source:574)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at fan.a(Unknown Source:20)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at eyz.a(Unknown Source:39)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at fal.a(Unknown Source:7)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at hfu.a(Unknown Source:146)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at gnw.run(Unknown Source:42)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at pal.b(Unknown Source:2)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at ozq.run(Unknown Source:22)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at paj.run(Unknown Source:4)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.lang.Thread.run(Thread.java:919)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at loy.run(Unknown Source:5)
11-07 20:51:27.564 6899 7388 I CAM_PictureTakerImpl: PictureTakerCommand.run: success=false
jokolom said:
I have just tried it. Instead of crashing, it will get stuck while trying to read the NFC card. Moreover, the NFC settings get stuck as well.
Thanks
Click to expand...
Click to collapse
that what Im trying to tell you. Paul shared old config, I have put modified to work with new hals.
May be you can compare both and fix it.
My nfc is not working due antenna problems.
Thats it!
@heineken78 Sorry but I can't find link to download rom files in first post (update 2019-11-06 too) .
iiandrusii said:
@heineken78 Sorry but I can't find link to download rom files in first post (update 2019-11-06 too) .
Click to expand...
Click to collapse
This is question to XDA designer. Change XDA style page and find tabs, we are on "di-scussion" now, next is " downloads"...
I found ? thx