Database Info

g1 MOBO with EVT1 32B ? Not PVT 32B? (solved see how)

ok some might have seen this strange board in a thread...
I had purchased a broken g1... and i talked about this strange EVT1 in hboot, and it would get stuck on G1 logo
so I waited until i got a usb/serial cable and jtag... I have both and i went on with the whole process
everything worked, up until i tried to get into the recovery, this device will not go into recovery for some reason.
==update==
looking at serial what its displaying... and it does go into recovery when the display turns off, the device is on, i just get error for the display and few others...
I had first the radio that was stated in the jtag process the 3.22.26.17
so hboot stating evt1 32b and were dread1000 or something like that supposed to be... i get drea*****
i researched and ran into other ppl that had a magic/sapphire that was evt 32b
fastboot/hboot is working at that point
here is a pic if you dont believe me
serial display of boot up... txt file is for boot recovery boot up
Code:
OEMSBL VERSION: 3.22.26.17
OEMSBL Build Date: Jan 17 2010 12:08:33
PLATFORM: DREAM
PID: 31
PLATFORM ID: 0
Boot CE manually...
Done.
+16 bit
-msm_nand_probe
[MDDI_HW_ERR] mddi_send_rtd fail!!
[MDDI_EID] mddi_eid_probe enter.
[EID_HW_ERR] mddi_eid_probe: Unknown panel type!!
GetModelName- Default[DREA*****]
Board_PID : 0x1F
Wlan data header ++++++++++++++++++++
Signature : 0xEE1251
UpdateStatus : 0x1
UpdateCount : 0x1
BodyLength : 0x2F0
BodyCRC : 0xC8545E10
aDieId(0) : 0x0
aDieId(1) : 0x0
aDieId(2) : 0x0
aDieId(3) : 0x0
countryID : 0x10
Wlan data header --------------------------
chipset_bootmode reset_reason:0
ARM11 Boot Mode: 0
Platform: HBOOT-7201A
###[ Fastboot Mode ]###

nobody has a clue

did some more forum searching...
in this thread someone states
http://forum.xda-developers.com/showpost.php?p=7582535&postcount=1530
http://forum.xda-developers.com/showpost.php?p=7967905&postcount=1538
that E is for engineering and P is for production?
so it seems that i can get into recovery, BUT there is an error, right when i go into recovery the display is off and below errors and txt file from the serial say the rest of the story...
Code:
boot reason: PM_KPD_PWR_KEY_ON_RT_ST
(PowerOn Status,Boot Reason)=(1,1)
NAND_FLASH_READ_ID : HYNIX_256MB_FLASH_128MB_SDRAM
ARM9_BOOT_MODE0, Boot Android
+16 bit
-msm_nand_probe
[MDDI] Bitmap_Width = 480
[MDDI] Bitmap_Height = 640
[MDDI] RGB_Capability = 0x8888
[MDDI] Mfr_Name = 0xD263
[MDDI] Product_Code = 0x0
GetModelName- Default[DREA*****]
Board_PID : 0x1F
Wlan data header ++++++++++++++++++++
Signature : 0xEE1251
UpdateStatus : 0x1
UpdateCount : 0x1
BodyLength : 0x2F0
BodyCRC : 0xC8545E10
aDieId(0) : 0x0
aDieId(1) : 0x0
aDieId(2) : 0x0
aDieId(3) : 0x0
countryID : 0x10
Wlan data header --------------------------
chipset_bootmode reset_reason:0
ARM11 Boot Mode: 0
Platform: HBOOT-7201A
setup_tag addr=0xA0000100 cmdline add=0x98071C80
TAG:Ramdisk OK
TAG:smi ok, size = 64
TAG:hwid 0x0
TAG:skuid 0xFFFFFFFF
TAG:hero panel = 0x0
TAG:engineerid = 0xFFFFFFFF
Device CID is not super CID
CID is T-MOB010
setting.cid::T-MOB010
serial number: 0123456789*******
commandline from head: no_console_suspend=1 console=null
command line length =331
active commandline: board_trout.disable_uart3=0 board_trout.usb_h2w_sw=0 board_trout.disable_sdcard=0 smisize=64 androidboot.baseband=2.22.23.02 androidboot.cid=T-MOB010 androidboot.carrier=TMUS androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=0123456789*****
androidboot.bootloader=1.33.2005 no_console_suspend=1 console=null
PARTITIOM_NUM_MAX =6 Valid partition num=6
(note put **** in serial number)
im going to attach txt of the recovery boot up
this is from serial cable while home + power (recovery mode)
note this is with the 1.7 dream recovery and the 2.22.23.02 dream radio
also worked fine with the jtag radio and recovery, i believe same error
look at the error, seems with display? as i can pass commands blindly (tried to flash from memory card, but still i believe the device then reboots...)
ignore other errors as only mobo + display and daughter board are connected...
this is one error while going into recov:
hsusb: ONLINE -> OFFLINE
[ 7.667053] ekt8232_probe enter.
[ 7.670471] elan-touch 0-0010: without platform data??!!
[ 7.876098] elan-touch 0-0010: __hello_packet_handler: failed!
[ 7.882019] looks like it's not Elan, so..i'll quit
[ 7.926300] msm_i2c msm_i2c.0: error, status c8
[ 7.931091] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 7.936828] i2c_smbus_write_byte_data failed
[ 7.941375] msm_i2c msm_i2c.0: error, status c8
[ 7.946563] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.056213] msm_i2c msm_i2c.0: error, status 43c8
[ 8.061157] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.183258] msm_i2c msm_i2c.0: error, status c8
[ 8.188140] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.298706] msm_i2c msm_i2c.0: error, status c8
[ 8.303558] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.418060] msm_i2c msm_i2c.0: error, status c8
[ 8.422912] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.538055] msm_i2c msm_i2c.0: error, status c8
[ 8.542907] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.658050] msm_i2c msm_i2c.0: error, status c8
[ 8.662872] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.778167] msm_i2c msm_i2c.0: error, status c8
[ 8.783020] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.898071] msm_i2c msm_i2c.0: error, status c8
[ 8.902893] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 9.018066] msm_i2c msm_i2c.0: error, status c8
[ 9.022918] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 9.137939] i2c_smbus_read_byte_data failed
[ 9.142425] synaptics-rmi-ts: probe of 0-0020 failed with error -5
[ 9.150451] GPIO Input Driver: Start gpio inputs for trout-nav in interrupt mode
the error that keeps on repeating is:
msmfb_pan_display timeout waiting for frame start, 1 1
i attached hboot commands?!?

so i was playing with a lot of hboot commands that were in that txt file
i ran into writesku/readsku
so what did i do? write some diff words... and result? wow things change...
so how did i fix? simple plugged in a working G1 mobo and copied all the readsku info
now my EVT1 magically turned into PVT, though it now reads DREAM and not DREA**** and not DREAM1000 either... oh well
and i went right into recovery after rebooting
here are the contacts of readsku before and after (is cloned from other mobo)
messed up EVT mobo
Code:
hboot>readsku
skuid item:FunctionSKUField
index:0x0, value:0x0
skuid item:PCBIDField
index:0x1, value:0xFFFF
skuid item:RFSKUIDField_D0
index:0x2, value:0xFFFFFFFF
skuid item:RFSKUIDField_D1
index:0x3, value:0xFFFFFF
skuid item:RFSKUIDField_D2
index:0x4, value:0xFFFFFFFF
skuid item:RFSKUIDField_D3
index:0x5, value:0xFFFFDFFF
skuid item:RFSKUIDField_D4
index:0x6, value:0xFFFFBFFF
skuid item:RFSKUIDField_D5
index:0x7, value:0xEFFFFFFF
skuid item:RFSKUIDField_D6
index:0x8, value:0xFFFFFFFF
skuid item:RFSKUIDField_D7
index:0x9, value:0xFFFFFFFF
skuid item:SKUIDChecksum
index:0xA, value:0xFFFFFF
skuid item:EngineerID
index:0xB, value:0xFFFFFFFF
copy from working mobo
Code:
hboot>readsku
skuid item:FunctionSKUField
index:0x0, value:0x1BE00
skuid item:PCBIDField
index:0x1, value:0x80FFFFFF
skuid item:RFSKUIDField_D0
index:0x2, value:0x12
skuid item:RFSKUIDField_D1
index:0x3, value:0x20000D4
skuid item:RFSKUIDField_D2
index:0x4, value:0xFFFFFFFF
skuid item:RFSKUIDField_D3
index:0x5, value:0xFFFFFFFF
skuid item:RFSKUIDField_D4
index:0x6, value:0xFFFFFFFF
skuid item:RFSKUIDField_D5
index:0x7, value:0xFFFFFFFF
skuid item:RFSKUIDField_D6
index:0x8, value:0xFFFFFFFF
skuid item:RFSKUIDField_D7
index:0x9, value:0xFFFFFFFF
skuid item:SKUIDChecksum
index:0xA, value:0xD8A37369
skuid item:EngineerID
index:0xB, value:0xFFFFFFFF
as you can see the first line is the key and then others too...
this explains all the serial code that i saw, interesting that all the flashing erasing and what not did not touch these values
all those errors were because there was no id to the device and recovery couldnt ID it and couldnt init the display, and not only that funny how the keyboard maping wasnt working either... so its possible to change your device to whatever I guess, its just an ID tag

[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?

[Q] what have i done wrong here (Root ics)

ive just followed this thread http://forum.xda-developers.com/showthread.php?t=2144738
and this was the output from the window
Code:
wait 5-seconds...
[*] msg size = 4
usb_write 21504
[*] data size = 21504
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 255028
usb_write 4
usb_write 255028
** Done **
< waiting for device >
sending 'recovery' (6187 KB)...
OKAY [ 3.219s]
writing 'recovery'...
OKAY [ 0.766s]
finished. total time: 3.984s
You chooesd ICS//TWRP Recovery
waiting for OMAP44xx device...
when i try any combination of keys to go into recovery its just a black screen. any ideas? id it actually finish? when it says waiting for omap44xx device i tried unplugging and plugging in the cable but it did nothing

just tried to reboot normally and it says security error

if anyone can get this up and running ill thank every one of their posts for a week... i cant believe its gone wrong for me AGAIN

seriously panicing now, cant get into SW mode, i can get into fastboot and SW via wpark but the flash wont go past 17%

flash process now gets to 30% and quits

I got security error as well with that tutorial. Flashing bootloaders and recovery using this http://forum.xda-developers.com/showthread.php?t=1978543 helped.
Also - I used SmartFlash to flash bin and fls

[ACKNOWLEDGED BUG] Android 5.1 Camera can't connect... ever

It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
Acknowledged bug by google https://code.google.com/p/android/issues/detail?id=160609

cthulu said:
It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?

zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes

cthulu said:
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes
Click to expand...
Click to collapse
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.

zagorteney said:
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.
Click to expand...
Click to collapse
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?

PHPanos said:
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?
Click to expand...
Click to collapse
And this was happening immediately after booting your phone? Then must be hardware. ?

It works fine everytime I reboot, for xx minutes. It's difficult to say for how long but not too long. I see that "Trusted face" unlock stops working and that's a signal the whole camera subsystem is gone. Everything else works just no camera access from any app is possible.

zagorteney said:
And this was happening immediately after booting your phone? Then must be hardware. ��
Click to expand...
Click to collapse
No. It works at first. Then after a few times of locking/unlocking the phone and opening the camera app and switching to front camera it shuts down. The problem goes away after a reboot but it comes back again after a while.
cthulu: We have both the same problem.

Same here for me since upgrading to 5.0 every now and then i must reboot my phone in order to fix it.This is really annoying maybe we should wait for a new camera app by google ?

Same issue
Hi guys,
This has been the problem for me since 5.0 . I thought maybe its just me. But after a while, the camera stops working. I assume this is a s/w issue since the phone was fine in Kitkat. Even in 5.1 the issue persists.

I am also getting frequent "can't connect to camera" since 5.1. Nexus 5.

Do you know if there's an issue for this in Google's issue tracker? I'm sure they won't check xda forums for bug reports.
I've clicked a few times to send the error to Google when starting the camera but I honestly don't think they're checking those...
I hoped full wipe will fix this but as it happens to the folks who did full wipe I'm rather not going to do it yet...

Already reported here https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609

zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.

THRUSTer said:
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.
Click to expand...
Click to collapse
You are on a right direction. Just start to read a little more careful.

Happens the same for me.
Some days ago i see that the face Trusted face have Stop. So, now i desible the Trusted face, clear data of camera app e until now (about 2 hours) the camera works fine, without any shut up.
Try you too, i think that the problems are in the Smart lock.

Many people have this issue since they moved to 5.1
'Hardware defect' and 'no full wipe' were told to be the culprit straight away, but looking at the bug report that seems unjustified, especially given the number of reports with exactly this issue.
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
zagorteney said:
Flash completely and it will fix it.
Click to expand...
Click to collapse
zagorteney said:
Then must be hardware. ?
Click to expand...
Click to collapse
So please be a bit more thorough in your advice....

Can't connect to camera error Nexus 5 Android 5.1
Hi gays, I am new here. I keep getting the ' can't connect to camera' error on my Nexus 5 Android 5.1, and I tried everything that is suggested here and it did not help. I turned off Face unlock, uninstall Viber and install again, cleared cache of the camera and force stop and everything else. Only help restart the device. I succeeded to catch the logcat with the error. Here is the logcat:
04-02 21:19:26.744 724-2687/? I/ActivityManager﹕ START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.GoogleCamera/com.android.camera.CameraLauncher bnds=[849,1532][1050,1784] (has extras)} from uid 10019 on display 0
04-02 21:19:26.747 724-2687/? V/WindowManager﹕ addAppToken: AppWindowToken{2498ae08 token=Token{83da7ab ActivityRecord{3a47c5fa u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher t32}}} to stack=1 task=32 at 0
04-02 21:19:26.751 724-819/? V/WindowManager﹕ Based on layer: Adding window Window{15bd6123 u0 Starting com.google.android.GoogleCamera} at 3 of 9
04-02 21:19:26.824 724-1360/? I/ActivityManager﹕ Start proc 22932:com.google.android.GoogleCamera/u0a42 for activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
04-02 21:19:26.837 1361-3270/? W/GsaThreadFactory﹕ Not creating another thread for Background Blocking because there are already 30
04-02 21:19:26.876 22932-22932/? W/ResourcesManager﹕ Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
04-02 21:19:26.935 22932-22932/? W/CAM_Log﹕ Tag SessionStatsCollector is 2 chars longer than limit.
04-02 21:19:26.989 22932-22932/? I/CameraManagerGlobal﹕ getCameraService: Reconnecting to camera service
04-02 21:19:27.254 22932-22979/? I/CAM2PORT_AndCamAgntImp﹕ Opening camera 0 with camera1 API
04-02 21:19:27.266 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 116
04-02 21:19:27.268 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.289 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 117
04-02 21:19:27.290 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.301 193-1682/? I/Camera2ClientBase﹕ Camera 0: Opened. Client: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.302 22932-22992/? W/CAM_PhotoData﹕ Zero dimension in ContentResolver for /storage/emulated/0/DCIM/Camera/IMG_20150402_180439.jpg:0x0
04-02 21:19:27.303 193-1682/? D/mm-camera-intf﹕ mm_camera_open: dev name = /dev/video1, cam_idx = 1
04-02 21:19:27.304 206-206/? I/mm-camera-sensor﹕ module_sensor_start_session:583 session 1
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ csiphy_open:126 VIDIOC_MSM_CSIPHY_IO_CFG failed
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:335 failed rc -1
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_close:2499 VIDIOC_MSM_SENSOR_CFG failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:500 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:612 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:617 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_get_capabilities:1632 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_query_mod:2421 failed rc -4
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_hardware_process_command:254: failed, subdev not opened
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_query_mod:268: failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_query_mod:1697] error in cpp query mod
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_module_set_session_data:2666 max delay 2 report dSelay 1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ isp_set_session_data: Session could not be found!
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_get_params_for_session_id:178, failed, session_id=0x1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_set_session_data:329, failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_set_session_data:1928] error in cpp set_session_data
04-02 21:19:27.307 206-206/? D/mm-camera﹕ module_faceproc_set_session_data:1836] Per frame control 2 1
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_sensor_stop_session:636 session 1
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_deinit_session:526 ref count 0
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:664 failed
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:669 failed
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:462, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:504, info: session 1 stopped.
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:322, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:361, info: session 1 stopped.
04-02 21:19:27.308 206-206/? E/mm-camera﹕ main: New session [1] creation failed with error
04-02 21:19:27.308 193-1682/? D/mm-camera-intf﹕ mm_camera_open: opened, break out while loop
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ mm_camera_open: cannot open control fd of '/dev/video1' (Bad address)
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ camera_open: mm_camera_open err = -1
04-02 21:19:27.308 193-1682/? E/QCamera3HWI﹕ camera_open failed.
04-02 21:19:27.308 193-1682/? E/Camera3-Device﹕ Camera 0: initialize: Could not open camera: No such device (-19)
04-02 21:19:27.308 193-1682/? E/Camera2ClientBase﹕ initialize: Camera 0: unable to initialize device: No such device (-19)
04-02 21:19:27.308 193-1682/? E/CameraService﹕ connectFinishUnsafe: Could not initialize client from HAL module.
04-02 21:19:27.308 193-1682/? I/Camera2Client﹕ Camera 0: Closed
04-02 21:19:27.309 193-1682/? I/Camera2ClientBase﹕ Closed Camera 0. Client was: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.313 193-1682/? W/AudioFlinger﹕ session id 116 not found for pid 22932
04-02 21:19:27.317 193-1682/? W/AudioFlinger﹕ session id 117 not found for pid 22932
04-02 21:19:27.318 22932-22979/? W/CameraBase﹕ An error occurred while connecting to camera: 0
04-02 21:19:27.318 22932-22979/? E/CAM2PORT_AndCamAgntImp﹕ RuntimeException during CameraAction[OPEN_CAMERA] at CameraState[1]
java.lang.RuntimeException: Fail to connect to camera service
at android.hardware.Camera.<init>(Camera.java:497)
at android.hardware.Camera.open(Camera.java:342)
at com.android.ex.camera2.portability.AndroidCameraAgentImpl$CameraHandler.handleMessage(AndroidCameraAgentImpl.java:370)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
04-02 21:19:27.371 22932-23015/? D/OpenGLRenderer﹕ Use EGL_SWAP_BEHAVIOR_PRESERVED: true
04-02 21:19:27.377 22932-22932/? D/Atlas﹕ Validating map...
04-02 21:19:27.381 724-1360/? V/WindowManager﹕ Adding window Window{312f9c81 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 3 of 10 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.387 22932-22932/? W/CAM_CameraActivity﹕ Camera open failure: HIST_ID0_-1_1_HEND
04-02 21:19:27.387 22932-22932/? E/CAM_Util﹕ Show fatal error dialog
04-02 21:19:27.402 724-2689/? V/WindowManager﹕ Adding window Window{302ae167 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 4 of 11 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.406 22932-22932/? D/WearableClient﹕ WearableClientImpl.onPostInitHandler: done
04-02 21:19:27.431 22932-23015/? I/Adreno-EGL﹕ <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 01/14/15, ab0075f, Id3510ff6dc
04-02 21:19:27.432 22932-23015/? I/OpenGLRenderer﹕ Initialized EGL, version 1.4
04-02 21:19:27.444 22932-23015/? D/OpenGLRenderer﹕ Enabling debug mode 0
04-02 21:19:27.487 22932-22932/? I/CAM_UsageStats﹕ PlayLogger.onLoggerConnected
04-02 21:19:27.512 724-2689/? D/WifiService﹕ acquireWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ onPreviewUIReady
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ attempted to start preview before camera device
04-02 21:19:27.518 724-851/? E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source 10007 txSuccessRate=0.00 rxSuccessRate=0.00 targetRoamBSSID=10:fe:ed:4e:a3:ae RSSI=-47
04-02 21:19:27.574 724-819/? I/ActivityManager﹕ Displayed com.google.android.GoogleCamera/com.android.camera.CameraLauncher: +790ms
Please HELP, it's really annoying
Best regards.

meranto said:
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
So please be a bit more thorough in your advice....
Click to expand...
Click to collapse
Nope..
https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609
has a lot of people who didn't use face unlock and still experienced the issue.

Replay
Hi meranto,
thanks for the replay. I did not use face unlock and the issue still show up

[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!