Database Info

[Q] Bluetooth media doesnt work on ported rom. Please help?

Any developer here??? Pls help me to fix bt media... My rom is HTC Sense 4 for htc explorer/pico which is ported by derefas from HTC Desire C. Bluetooth file transfer works very well but bt headset doesnt work. Here is the logcat.
E/BluetoothA2dpService.cpp( 349): onConnectSinkResult: D-Bus error: org.bluez.E
rror.Failed (Stream connection failed)
D/BluetoothA2dpService( 349): checkSinkSuspendState(): state=0,mTargetA2dpState
=-1
D/StateMachine( 349): handleMessage: new destination call exit
D/StateMachine( 349): invokeExitMethods: PendingCommandState
I/BluetoothProfileState( 349): Message:Entering Stable State
D/AudioService( 349): isSpecialCase=true , mEventAudioOnly=false , isStreamActi
ve=false
D/AudioService( 349): checkEqIdAndApplyEffect isHeadsetPlugged()=false , mBluet
oothHeadsetConnected=false , id=900 , mHtcSpecificAP=false , mGlobalSoundEffect=
900
V/AudioHardwareMSM72XX( 114): setParameters() global_effect=none
D/AudioService( 349): broadcastSoundEffectChanged beats state=false appName=BT
state changed
V/BluetoothEventManager( 2780): Received android.bluetooth.a2dp.profile.action.C
ONNECTION_STATE_CHANGED
I/LocalBluetoothProfileManager( 2780): Failed to connect A2DP device
D/StateMachine( 349): handleMessage: new destination call exit
D/StateMachine( 349): invokeExitMethods: OutgoingA2dp
I/BluetoothDeviceProfileState( 349): Entering ACL Connected state with: 102
D/BluetoothA2dpService( 349): A2DP state : device: C4:85:08:05:59:5A State:1->0
I/BluetoothA2dpService( 349): [embedded] A2DP state : address: C4:85:08:05:59:5
A name: SHEKHAR-PC State:1->0
D/BluetoothAdapterStateMachine( 349): BluetoothOn process message: 52
D/BluetoothService( 349): CONNECTION_STATE_CHANGE: C4:85:08:05:59:5A: 1 -> 0
V/BluetoothEventManager( 3562): Received android.bluetooth.a2dp.profile.action.C
ONNECTION_STATE_CHANGED
I/LocalBluetoothProfileManager( 3562): Failed to connect A2DP device
I/USERIAL_LINUX( 3593): ##### USERIAL_Ioctl: BT_Sleep, USERIAL_IO_BT_WAKE_DEASSE
RT ####
D/PhoneStatusBarPolicy( 634): isCdma():false hasService:true mSimState=UNKNOWN
gprsState=0 mDataState=0 dataActivity=1 mPhone.htcModemLinkOn:false hspa==true
E/ ( 3593): btm_sec_disconnected - Clearing Pending flag
W/ ( 3593): BTA_DM_LINK_DOWN_EVT::bdaddr c4:85:08:05:59:5a reason x13
I/ ( 3593): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTR
L) 11 pbytes (hdl 22)
D/DTUN_HCID4( 3608): dtun_dm_sig_link_down()
I/DTUN_HCID4( 3608): dtun_dm_sig_link_down device = 0x6f7900 reason = 19
I/DTUN_HCID4( 3608): [embedded]LINK_DOWN name = SHEKHAR-PC, address = C4:85:08:0
5:59:5A, reason = 0x13
D/BluetoothEventLoop( 349): Device property changed: C4:85:08:05:59:5A property
: Connected value: false
D/ ( 3593): >>> STOP GKI_timer_update(), wake_lock_count:0
D/ ( 3593): >>> SUSPENDED GKI_timer_update()
Can anyone guide me to fix this?

Proximity Sensor issues.

Hey guys. Recently I have been wondering what's going on with.my Sensor. It used to work just fine until I started flashing new Roms. I had the sensor working on the default.CM 9.1.0 rom and I can't remember another rom it worked with. I now have ViperS 1.6.3 for Sensation. I love this rom, but I checked AndroSensor and the status for the ProxSensor always says "Waiting for event" I am not sure what to do here, my sensor just doesn't work anymore! Troubleshooting ideas please!
Sent from Ty's ViperS Sensation. A beast of a phone.

ClipTy said:
Hey guys. Recently I have been wondering what's going on with.my Sensor. It used to work just fine until I started flashing new Roms. I had the sensor working on the default.CM 9.1.0 rom and I can't remember another rom it worked with. I now have ViperS 1.6.3 for Sensation. I love this rom, but I checked AndroSensor and the status for the ProxSensor always says "Waiting for event" I am not sure what to do here, my sensor just doesn't work anymore! Troubleshooting ideas please!
Sent from Ty's ViperS Sensation. A beast of a phone.
Click to expand...
Click to collapse
Does the screen automatically turnoff when you take it close to your face on call....if so your proximity sensor is working...
Also there should be no issues in the sensor bcoz of VIperS rom....but if issue persists, full wipe and flash again.

I might need to full wipe.
Sent from Ty's ViperS Sensation. A beast of a phone.

murtazasamiwala said:
Does the screen automatically turnoff when you take it close to your face on call....if so your proximity sensor is working...
Also there should be no issues in the sensor bcoz of VIperS rom....but if issue persists, full wipe and flash again.
Click to expand...
Click to collapse
So I did a full wipe, flashed a clean ViperS rom, and I still get nothing. Went back to my previous back up.
I have been reading all over the place and tons of people never even found a solution for said issues. I'm going to ask on the Viper thread.

Any ideas? Cmon. Someone has to know.
Sent from Ty's ViperS Sensation. A beast of a phone.

Still searching the problem at here : http://forum.xda-developers.com/showthread.php?p=42735640#post42735640

teeebor said:
Still searching the problem at here : http://forum.xda-developers.com/showthread.php?p=42735640#post42735640
Click to expand...
Click to collapse
I have the same problem till Saturday. But I cannot post in the development thread and help to fix the problem.

x2ht1 said:
I have the same problem till Saturday. But I cannot post in the development thread and help to fix the problem.
Click to expand...
Click to collapse
Ok,
First check this directory: /sys/devices/virtual/optical_sensors
If it does not exist, you have the same problem. But if the folder exist, just wipe the cache and dalvik

No don't have this folder, too.
Till yesterday I have tried a several things.
First my Rom is Dark Sense 3.6, Sultan kernel from DS Store revision15 office version, Firmware 3.33 with Patch to HBoot 1.29.
1. I have tried a another kernel, didn't help.
2. Install a nandroid, didn't help.
3. Do a full wipe and install the Dark Sense Rom again, and didn't help.
4. Copie the scripts from the other thread (01lightsensor..e.g.) to the init.d folder, didn't help.
5. Then I tried to copy the optical_sensors Folder directly to sys/devices/virtual and then I get an error! "There is not enough space" (0Bit Free). Mhhh..that's not normal. I have root and read write access!
6. I tried a CW10.1 Rom and it work, till after a reboot.
Now I have install my nandroid and the issues still exist. I don't want to change my Rom, I like it.
Hope my post helps to solve the problem.

Yesterday I decided to change my Rom to CM10.1 from Albinoman...
The sensors works with this Rom! After some testing time I come to the result: that's not my rom. The camera is really bad against the HQCamera 1.5.
There is no Beats Audio, Sony xLoud and Bravia Engine 2.
...I make a full wipe again
Install my nandroid and the sensors still work
But I don't make a reboot. I thing after a reboot the sensor stops to work...

So you find our biggest problem. We can't figure out why is this happening. Sometimes after wipe it works, sometimes other firmwares work and sometimes RUU or Rom change work. There must be a bug in the boot, and don't know yet how to fix it :/
Anyway thanks for reply
Sent from my HTC Sensation Z710e using xda premium

teeebor said:
So you find our biggest problem. We can't figure out why is this happening. Sometimes after wipe it works, sometimes other firmwares work and sometimes RUU or Rom change work. There must be a bug in the boot, and don't know yet how to fix it :/
Click to expand...
Click to collapse
I thing the space is not the problem. It´s a virtual folder.
Now I can say Rom with Sense don´t work..
I have try a many roms (Elegancia, Dark Forest, DarkSense and the Stock ICS ROM 3.33.401.106). The sensors don´t work whith any of these
rom´s.
With other roms like CM9, CM10.1 or HyperSensation it works without issues...
I can post some pictures from my bootscreen log where you can see the error!

here is the pic
View attachment 2059400

I see it returns 0, but why? When it fails it must return a specific error code exept zero.
So in CM all optical sensors must work? Hmm i try it, but my preferred Launcher is Roise because Beats audio and GUI
Tomorrow i will share the result

teeebor said:
I see it returns 0, but why? When it fails it must return a specific error code exept zero.
So in CM all optical sensors must work? Hmm i try it, but my preferred Launcher is Roise because Beats audio and GUI
Tomorrow i will share the result
Click to expand...
Click to collapse
your right! normally there are the values from the light and proximity sensor. you see an errorcode he is at the line above.
smd_tty_open: DS open failed -19
Click to expand...
Click to collapse
The line isn´t ther when the sensors work! I thing he couldn´t open the driver, but why?
the app for the loading screen called "live dmesg lite"

x2ht1 said:
your right! normally there are the values from the light and proximity sensor. you see an errorcode he is at the line above.
The line isn´t ther when the sensors work! I thing he couldn´t open the driver, but why?
the app for the loading screen called "live dmesg lite"
Click to expand...
Click to collapse
It could not be a permission problem cause i fixed it. Maybe a malfunctioning driver that leave behind something that block the sensor's driver.I don't have a better idea.

CM doesn't help. But somehow I could get it to work.
Here is the log when the sensors failed to start:
{
"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"
}
And when it worked:
edit
The columns are the following: Type - Sender - PID - Message

Till yesterday my sensor work, too. but he restarts every time.
D/SensorService( 2473): enable: get sensor name = MPL accel
D/Sensors ( 2473): handle : 4 en: 1, v010.0 - Try to resolve lock issue
D/Sensors ( 2473): lock_status = 63
D/Sensors ( 2473): Andy: MPLSensor::enable: lock1
D/Sensors ( 2473): mEnabled = 0x10
D/Sensors ( 2473): set_power_states++: enabled_sensors: 16 dmp_started: 0
D/Sensors ( 2473): Before if statment: cs:0 rs:1 en_ped:0 da_ped:0 en_g:0 da_g:0
D/Sensors ( 2473): STOP timerirq_1
D/Sensors ( 2473): Starting DMP
I/ ( 2473): mpu3050_resume: Resuming to 0070
D/Sensors ( 2473): Exit: Starting DMP
D/Sensors ( 2473): set_power_states--
D/Sensors ( 2473): Andy: MPLSensor::enable: unlock1
D/Sensors ( 2473): MPLSensor::enable--1
D/Sensors ( 2473): (llu)G_Delay = 200
I/ ( 2473): mpu3050_resume: Resuming to 0070
I/ ( 2473): mpu3050_suspend: suspending sensors to 0070
I/ ( 2473): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 2473): Actual ODR: 25 Hz
D/SensorService( 2473): SensorDevice::activate--: handle = 0x4, enabled = 0x1
D/SensorService( 2473): pid=29490, uid=10176
D/Sensors ( 2473): (llu)G_Delay = 20
I/ ( 2473): mpu3050_resume: Resuming to 0070
I/ ( 2473): mpu3050_suspend: suspending sensors to 0070
I/ ( 2473): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 2473): Actual ODR: 25 Hz
D/SensorService( 2473): disable: get sensor name = MPL accel
D/Sensors ( 2473): handle : 4 en: 0, v010.0 - Try to resolve lock issue
D/Sensors ( 2473): lock_status = 4
D/Sensors ( 2473): Andy: MPLSensor::enable: lock1
W/MPL-sup ( 2473): MLGetAKMComassStatus, gAKMCompassStatus = 0
D/Sensors ( 2473): mEnabled = 0x0
D/Sensors ( 2473): set_power_states++: enabled_sensors: 0 dmp_started: 1
D/Sensors ( 2473): Before if statment: cs:0 rs:0 en_ped:0 da_ped:0 en_g:0 da_g:0
D/Sensors ( 2473): Stopping DMP
I/ ( 2473): mpu3050_suspend: suspending sensors to 0000
I/ ( 2473): mpu3050_suspend: Will resume next to 0070
D/Sensors ( 2473): inside if(s_use_timerirq)
D/Sensors ( 2473): set_power_states--
D/Sensors ( 2473): Andy: MPLSensor::enable: unlock1
D/Sensors ( 2473): MPLSensor::enable--1
D/SensorService( 2473): SensorDevice::activate--: handle = 0x4, enabled = 0x0
D/SensorService( 2473): pid=29490, uid=10176
Click to expand...
Click to collapse

after a week i can say that my sensors still work but sometimes the drivers restarts and then the sensors didn´t work.

The sensors still not working for me, but several days ago the proximity sensor lights up in red

[S4][DEVs only] Zoe development

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...

[Q] Device encryption not starting

Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
I/MountService( 872): encrypting storage...
I/power ( 872): *** release_dvfs_lock : lockType : 1
D/SSRMv2:CustomFrequencyManagerService( 872): releaseDVFSLockLocked : Getting Lock type frm List : DVFS_MIN_LIMIT frequency : 1188000 uid : 1000 pid : 872 tag : [email protected]
D/lights ( 872): button : 0 +
D/lights ( 872): button : 0 -
D/qdutils ( 321): getuiClearRegion:70 wormRect( l = 0 t = 0 r = 720 b = 50)
D/qdutils ( 321): getuiClearRegion:76 FinalwormRect( l = 0 t = 0 r = 720 b = 50)
E/SMD ( 346): DCD ON
I/SecureStorage(12345): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(12345): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Load image request failed ret = -1, errno = 14
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
E/SecureStorage(12345): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(12345): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(12345): [ERROR]:Error cannot connect to TA/driver!
Click to expand...
Click to collapse
Any ideas?

ccoager said:
Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
Any ideas?
Click to expand...
Click to collapse
My recommendation? DON'T DO ENCRYPTION!! you may get your phone in a lockmode and unable to recover data..

Is there anything else that could be causing this?
I have not chosen device encryption and I am also seeing these messages in logcat..
I/SecureStorage(15360): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(15360): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_stor.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
E/SecureStorage(15360): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(15360): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(15360): [ERROR]:Error cannot connect to TA/driver!
E/SMD ( 213): DCD ON

Same Problem
I am getting the same thing and when I rooted my SCH-r530u I disabled the Knox thing
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon is preparing to run
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon successfully binded a socket
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_stor.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_storage.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Loading app sec_stor and sec_storage failed
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Fail to open session with qualcomm
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Error cannot connect to TA/driver!
02-20 22:57:12.161: V/AlarmManager(411): waitForAlarm result :8
Click to expand...
Click to collapse
What does it mean? I keep getting it every few seconds while the screen is on
* I was going to edit out the sad faces but its too funny cause it fits the situation perfectly*

[APP][PATCH] SnoopSnitch OnePlus Compatibility Patch

After some trial and error, I have identified the reason why snoopsnitch isn't working.
The issue is related to the DIAG initialization code in the diag-helper binary.
I'm attaching a working patch and a compiled APK (PM me for the link or maybe a mod. can attach it. I have 10 post link restriction) for your convenience.
PS: the code specifically look for OnePlus manufacturer but it may work on other devices too (with the appropriate changes)
Code:
diff --git a/contrib/diag_helper/jni/diag-helper.c b/contrib/diag_helper/jni/diag-helper.c
index ddb7fcb1..c1b00a33 100644
--- a/contrib/diag_helper/jni/diag-helper.c
+++ b/contrib/diag_helper/jni/diag-helper.c
@@ -3,6 +3,7 @@
#include <sys/socket.h>
#include <sys/stat.h>
#include <sys/un.h>
+#include <sys/system_properties.h>
#include <android/log.h>
@@ -13,6 +14,7 @@
#include <stdlib.h>
#include <unistd.h>
#include <arpa/inet.h>
+#include <string.h>
#define BUF_SIZE 1000000
@@ -62,9 +64,15 @@ open_diag_dev(void)
int diag_fd = -1;
int rv = -1;
int olderrno;
+ bool op = false;
+ char man[PROP_VALUE_MAX + 1];
+
+ __system_property_get("ro.product.manufacturer", man);
logmsg(ANDROID_LOG_DEBUG, "opening diag device");
+ if (strcasecmp("oneplus", man) == 0) op = true;
+
diag_fd = open("/dev/diag", O_RDWR|O_CLOEXEC);
if (diag_fd < 0) {
logmsg(ANDROID_LOG_FATAL, "error opening diag device: %m");
@@ -74,6 +82,7 @@ open_diag_dev(void)
const unsigned long DIAG_IOCTL_SWITCH_LOGGING = 7;
const int MEMORY_DEVICE_MODE = 2;
+ const int mode_param[] = { MEMORY_DEVICE_MODE, -1, 0 };
struct diag_logging_mode_param_t stMode = {
MEMORY_DEVICE_MODE, 0, 1
};
@@ -84,7 +93,10 @@ open_diag_dev(void)
rv = ioctl(diag_fd, DIAG_IOCTL_SWITCH_LOGGING, MEMORY_DEVICE_MODE);
if (rv < 0) {
olderrno = errno;
- rv = ioctl(diag_fd, DIAG_IOCTL_SWITCH_LOGGING, (void *)&stMode);
+ if(op)
+ rv = ioctl(diag_fd, DIAG_IOCTL_SWITCH_LOGGING, (void *)&mode_param, sizeof(mode_param));
+ else
+ rv = ioctl(diag_fd, DIAG_IOCTL_SWITCH_LOGGING, (void *)&stMode);
}
if (rv < 0) {
Credits: SRLabs, original author repository: https://opensource.srlabs.de/projects/snoopsnitch
{Mod edit: Added apk on request of OP @h3ph4est7s}

thanks
I've been looking for this for a while, I sent you a pm
it works perfectly thanks

Hi,
Thanks for the apk! It's great to see it again running (especially initializing) on my device, love it! As I already wrote in another posting in another thread (sorry for the double post, but in this specific case it's OK I think), there are two things that need to be mentioned:
- the patch level checks do not work on my device, maybe this depends in the ROM I'm using (I'm on Havoc 3.8 / Android 10) - I'll have to check if it maybe works with another ROM.
- I currently cannot say if the detection of silent SMS and IMSI Catchers really is working since I've havent't had such events till now. Silent SMSes should appear from time to time IMO. IMSI catcher events are extremely rare in my experience, I used Snoop Snitch for about one year two or three years ago and got two of those events in the whole year: one in Germany, one in Canada.
Cheers
Zap

I am also facing the same DIAG_CHAR initializing issue. I used your snoopsnitch apk to test on my Oneplus 5, LOS16. The app started, but closed immediately. The backend service keep on restarted. My logcat shows as below.
12-11 13:16:12.186 9407 9407 E [email protected]: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
12-11 13:16:12.198 9417 9417 I diag-helper: starting
12-11 13:16:12.198 9417 9417 I diag-helper: test mode invoked
12-11 13:16:12.198 9417 9417 D diag-helper: opening diag device
12-11 13:16:12.198 9417 9417 F diag-helper: error setting diag device logging mode: Bad address/Invalid argument
12-11 13:16:12.199 9417 9417 E diag-helper: error opening DIAG device
12-11 13:16:12.200 9261 9261 E msd-service: Terminating MsdService after shutting down due to an unexpected error
12-11 13:16:12.202 9261 9261 I opSnitchServic: System.exit called, status: 1
12-11 13:16:12.202 9261 9261 I AndroidRuntime: VM exiting with result code 1, cleanup skipped.
12-11 13:16:12.215 1359 9176 I ActivityManager: Process .SnoopSnitchService (pid 9261) has died: fore SVC
12-11 13:16:12.215 1359 9176 W ActivityManager: Scheduling restart of crashed service de.srlabs.snoopsnitch/.qdmon.MsdService in 1000ms
12-11 13:16:12.215 1359 1405 W libprocessgroup: kill(-9261, 9) failed: No such process
12-11 13:16:12.215 1359 1405 I libprocessgroup: Successfully killed process cgroup uid 10092 pid 9261 in 0ms
Click to expand...
Click to collapse
Any kind of help is appreciated.

Installed this Mod on my OP7T Pro, but it crashes at start. The unmodified version starts flawless, but did mit recognize root privileges (message at the bottom "snoopsnitch require root access..."). On clicking the start network test button it tells me "could not initialize the diag interface". I checked diag_char in system and it is enabled. No Idea whats wrong. Using Android 10 with latest stabile stock OS.

EinsteinXXL said:
Installed this Mod on my OP7T Pro, but it crashes at start. The unmodified version starts flawless, but did mit recognize root privileges (message at the bottom "snoopsnitch require root access..."). On clicking the start network test button it tells me "could not initialize the diag interface". I checked diag_char in system and it is enabled. No Idea whats wrong. Using Android 10 with latest stabile stock OS.
Click to expand...
Click to collapse
Same here with Oxygen OS 11 beta. The modded app crashes on start and the original app can't "initilize diag driver."

On my OP3T with Android 11 (Arrow OS) it works. Same again as before: Starting and initializing perfectly, but the patch level checks do not work.
The Problem seems to be device-/SOC - specific.

Hello and thank you so very much for this. I had been wanting to use it for s long time and finally came across your workaround. Unfortunately it didn't work for me. I originally installed through nethunter store but I uninstalled that and installed yours. I am running Jaguar OS on OP8T rooted with magisk. I created a logcat hoping that you'll be able to hero me get it going. I am attaching it here. Thank you!