Quote:
Originally Posted by Renate
Everything data-wise looks good there.
18d1/4ee2 is correct for MTP, ADB.
It's failing on the first transaction, requesting the device descriptor.
You've got an electrical signal problem of some sort.
First step: Blow out all the connectors, different cable, different port, different hub, different computer.
You might have a broken or bad ground. It could be shielding on the cable. It could be a bad power supply on the hub/computer.
|
I have already tried different cable and different computer, the problem must be the USB port on the device.
It did connect now, so I was able to save output of adb logcat, this place may be interesting
Code:
06-14 17:09:26.218 701 1387 E android.hardware.usb@1.0-service: uevent received SUBSYSTEM=dual_role_usb
06-14 17:09:26.218 701 1387 I android.hardware.usb@1.0-service: otg_default
06-14 17:09:26.223 1243 1263 I EntropyMixer: Writing entropy...
06-14 17:09:26.223 694 694 I SDM : update_to_display[0/1] -- marker[2689] waveform_mode = 1, update_mode = 0, Rect[0 0 1872 1404], flags = 2000
06-14 17:09:26.223 701 1387 I android.hardware.usb@1.0-service: canChangeMode: 1 canChagedata: 0 canChangePower:0
06-14 17:09:26.225 1243 1385 I UsbPortManager: ClientCallback V1_0: otg_default
06-14 17:09:26.225 1243 1261 I UsbPortManager: USB port changed: port=UsbPort{id=otg_default, supportedModes=dualsupportedContaminantProtectionModes=0supportsEnableContaminantPresenceProtection=falsesupportsEnableContaminantPresenceDetection=false, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device], contaminantDetectionStatus=0, contaminantProtectionStatus=0}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false, connectedAtMillis=28830197, lastConnectDurationMillis=0
06-14 17:09:26.227 3814 3814 I DeviceReceiver: Received[298]: android.intent.action.ACTION_POWER_CONNECTED data null
06-14 17:09:26.227 4004 4004 I DeviceReceiver: Received[241]: android.intent.action.ACTION_POWER_CONNECTED data null
06-14 17:09:26.227 4079 4079 I DeviceReceiver: Received[244]: android.intent.action.ACTION_POWER_CONNECTED data null
06-14 17:09:26.228 4102 4102 I DeviceReceiver: Received[244]: android.intent.action.ACTION_POWER_CONNECTED data null
06-14 17:09:26.228 4066 4066 I DeviceReceiver: Received[244]: android.intent.action.ACTION_POWER_CONNECTED data null
06-14 17:09:26.229 7914 7914 V EventReceiver: Received event android.intent.action.ACTION_POWER_CONNECTED
06-14 17:09:26.229 7377 7377 I DeviceReceiver: Received[150]: android.intent.action.ACTION_POWER_CONNECTED data null
06-14 17:09:26.229 2185 2185 I DeviceReceiver: Received[308]: android.intent.action.ACTION_POWER_CONNECTED data null
06-14 17:09:26.229 3864 3864 I DeviceReceiver: Received[231]: android.intent.action.ACTION_POWER_CONNECTED data null
06-14 17:09:26.230 1408 1408 D KeyguardUpdateMonitor: received broadcast android.intent.action.BATTERY_CHANGED
06-14 17:09:26.230 4118 4118 I DeviceReceiver: Received[244]: android.intent.action.ACTION_POWER_CONNECTED data null
06-14 17:09:26.233 696 696 E qdlights: set_speaker_light_locked mode 0, colorRGB=FFFF0000, red=255, green=0, blue=0, blink=0, onMS=0, offMS=0
06-14 17:09:26.235 1243 1280 D PowerManagerService: wakeUpNoUpdateLocked: !!!rejected!!! eventTime=28829124, mLastSleepTime=13295984, uid=1000, mWakefulness=1, reason=WAKE_REASON_PLUGGED_IN, details= android.server.power:PLUGGED:true
dmesg shows nothing at that time, but ~6mins later (probably after I reconnected the cable) it gets connection after some errors.