USB connection dead

[ilyats]

My brand new Nova 3 Color stopped being recognized by a computer over USB link less than 2 weeks after I received it. In addition, it becomes unstable when connected to computer, hanging up or rebooting randomly.
I have found other people having reported USB connection problem with Boox devices, has anybody experienced instability as well, has one found a solution? I have tried factory reset and enabling and disabling USB debugging and changing default USB mode in developer options (using third party launcher to get to Google android settings.)
Logs of my Linux system show one weird thing about time the problem started: at one moment Nova presented itself as mass storage device QUSB_BULK_SN by Qualcomm, rather than MTP device SDM636-MTP _SN by Onyx, as it regularly does. Does it suggest firmware problem?

[Renate]

QUSB_BULK is the Qualcomm Emergency DownLoader (EDL)
It means that something never got around to reconfiguring the USB.
If it were me, I'd check if that interface is actually live, but that's a bit complicated and also pointless.

Onyx does a lot of stupid stuff with the normal USB configuration.
I haven't figured it all out yet.

If you have a terminal program on the device itself I'd "getprop|grep usb"
Do you have some sort of recovery on this?

[ilyats]

Originally Posted by Renate

QUSB_BULK is the Qualcomm Emergency DownLoader (EDL)
It means that something never got around to reconfiguring the USB.
If it were me, I'd check if that interface is actually live, but that's a bit complicated and also pointless.

Onyx does a lot of stupid stuff with the normal USB configuration.
I haven't figured it all out yet.

If you have a terminal program on the device itself I'd "getprop|grep usb"
Do you have some sort of recovery on this?

getprop |grep usb

[init.svc.usbd]: [stopped]
[persist.data.df.dev_name]: [rmnet_usb0]
[persist.sys.usb.config]: [mtp]
[persist.sys.usb.ffbm-02.func]: [mtp]
[sys.usb.config]: [mtp,adb]
[sys.usb.configfs]: [1]
[sys.usb.controller]: [a800000.dwc3]
[sys.usb.diag.config]: [0]
[sys.usb.ffs.ready]: [1]
[sys.usb.state]: [mtp,adb]

Does 'stopped' value in the first string mean it doesn't listen on USB controller?
There is a recovery menu on it, I got into it a couple of times.

[Renate]

No, the "stopped" is ok.
Do you see this:

Poke3:/ # ls -l /config/usb_gadget/g1/configs/b.1
total 0
-rw-r--r-- 1 root root 4096 2021-06-13 21:24 MaxPower
-rw-r--r-- 1 root root 4096 2021-06-13 21:24 bmAttributes
lrwxrwxrwx 1 root root    0 2021-06-13 18:02 f1 -> ../../../../usb_gadget/g1/functions/mtp.gs0
lrwxrwxrwx 1 root root    0 2021-06-13 18:02 f2 -> ../../../../usb_gadget/g1/functions/ffs.adb
drwxr-xr-x 3 root root    0 1970-02-06 16:25 strings

What does "lsusb -v" on your Linux box say? (Just the interesting stuff, please.)
Or what does dmesg say when you plug it in?

Edit: Sorry you got me a bit confused. When you were talking about what you saw in old logs I thought you meant what you were seeing then.
That Mass Storage you were seeing was probably something related to charging mode where it switches to UMS "Linux-Stor" without any mounted volumes.

VID/PID and descriptors are what we need.

[ilyats]

Originally Posted by Renate

No, the "stopped" is ok.
Do you see this:

Poke3:/ # ls -l /config/usb_gadget/g1/configs/b.1
total 0
-rw-r--r-- 1 root root 4096 2021-06-13 21:24 MaxPower
-rw-r--r-- 1 root root 4096 2021-06-13 21:24 bmAttributes
lrwxrwxrwx 1 root root    0 2021-06-13 18:02 f1 -> ../../../../usb_gadget/g1/functions/mtp.gs0
lrwxrwxrwx 1 root root    0 2021-06-13 18:02 f2 -> ../../../../usb_gadget/g1/functions/ffs.adb
drwxr-xr-x 3 root root    0 1970-02-06 16:25 strings

What does "lsusb -v" on your Linux box say? (Just the interesting stuff, please.)
Or what does dmesg say when you plug it in?

Edit: Sorry you got me a bit confused. When you were talking about what you saw in old logs I thought you meant what you were seeing then.
That Mass Storage you were seeing was probably something related to charging mode where it switches to UMS "Linux-Stor" without any mounted volumes.

VID/PID and descriptors are what we need.

I cannot see /config, does the device have to be rooted for it? It does not connect, so lsusb doesn't show anything interesting. Usual messages in dmesg are like this:

[Jun14 07:05] usb 5-4: new full-speed USB device number 92 using ohci-pci
[  +0.160011] usb 5-4: device descriptor read/64, error -62
[  +1.208034] usb 5-4: device descriptor read/64, error -62
[  +0.292036] usb 5-4: new full-speed USB device number 93 using ohci-pci
[  +0.163989] usb 5-4: device descriptor read/64, error -62
[  +0.268011] usb 5-4: device descriptor read/64, error -62
[  +0.108117] usb usb5-port4: attempt power cycle
[  +0.739990] usb 5-4: new full-speed USB device number 94 using ohci-pci
[  +0.415941] usb 5-4: device not accepting address 94, error -62
[  +0.188047] usb 5-4: new full-speed USB device number 95 using ohci-pci
[  +0.415983] usb 5-4: device not accepting address 95, error -62
[  +0.000040] usb usb5-port4: unable to enumerate USB device

It did connect for a moment today, with such messages

Jun14 06:39] usb 2-4: new high-speed USB device number 88 using ehci-pci
[  +0.158359] usb 2-4: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 4.04
[  +0.000007] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000004] usb 2-4: Product: SDM636-MTP _SN:5A424592
[  +0.000003] usb 2-4: Manufacturer: ONYX
[  +0.000003] usb 2-4: SerialNumber: 8165caf3
[  +2.487370] usb usb2-port4: disabled by hub (EMI?), re-enabling...
[  +0.000013] usb 2-4: USB disconnect, device number 88
[  +0.618506] usb 5-4: new full-speed USB device number 50 using ohci-pci
[  +0.187330] usb 5-4: not running at top speed; connect to a high speed hub
[  +0.012009] usb 5-4: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 4.04
[  +0.000007] usb 5-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000004] usb 5-4: Product: SDM636-MTP _SN:5A424592
[  +0.000003] usb 5-4: Manufacturer: ONYX
[  +0.000003] usb 5-4: SerialNumber: 8165caf3
[ +34.301062] usb usb5-port4: disabled by hub (EMI?), re-enabling...
[  +0.000013] usb 5-4: USB disconnect, device number 50
[  +0.328852] usb 5-4: new full-speed USB device number 51 using ohci-pci
[  +0.163933] usb 5-4: device descriptor read/64, error -62
[  +0.300009] usb 5-4: not running at top speed; connect to a high speed hub
[  +0.012004] usb 5-4: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 4.04
[  +0.000005] usb 5-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000002] usb 5-4: Product: SDM636-MTP _SN:5A424592
[  +0.000002] usb 5-4: Manufacturer: ONYX
[  +0.000001] usb 5-4: SerialNumber: 8165caf3
[Jun14 06:40] usb usb5-port4: disabled by hub (EMI?), re-enabling...
[  +0.000011] usb 5-4: USB disconnect, device number 51
[  +0.321026] usb 5-4: new full-speed USB device number 52 using ohci-pci
[  +0.160018] usb 5-4: device descriptor read/64, error -62
[  +0.271993] usb 5-4: device descriptor read/64, error -62
[  +0.264148] usb 5-4: new full-speed USB device number 53 using ohci-pci
[  +0.160024] usb 5-4: device descriptor read/64, error -62
[  +0.268000] usb 5-4: device descriptor read/64, error -62
[  +0.108038] usb usb5-port4: attempt power cycle
[  +0.707865] usb 5-4: new full-speed USB device number 54 using ohci-pci
[  +0.033845] usb 5-4: not running at top speed; connect to a high speed hub
[  +0.016010] usb 5-4: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 4.04
[  +0.000008] usb 5-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000004] usb 5-4: Product: SDM636-MTP _SN:5A424592
[  +0.000002] usb 5-4: Manufacturer: ONYX
[  +0.000003] usb 5-4: SerialNumber: 8165caf3
[ +12.216957] usb usb5-port4: disabled by hub (EMI?), re-enabling...
[  +0.000016] usb 5-4: USB disconnect, device number 54
[  +0.341648] usb 5-4: new full-speed USB device number 55 using ohci-pci
[  +0.187989] usb 5-4: device descriptor read/64, error -62
[  +0.295328] usb 5-4: not running at top speed; connect to a high speed hub
[  +0.012896] usb 5-4: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 4.04
[  +0.000004] usb 5-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000002] usb 5-4: Product: SDM636-MTP _SN:5A424592
[  +0.000001] usb 5-4: Manufacturer: ONYX
[  +0.000001] usb 5-4: SerialNumber: 8165caf3
[Jun14 06:42] usb 5-4: USB disconnect, device number 55
[  +0.484579] usb 5-4: new full-speed USB device number 56 using ohci-pci
[  +0.164015] usb 5-4: device descriptor read/64, error -62
[  +0.296161] usb 5-4: device descriptor read/64, error -62
[  +0.291989] usb 5-4: new full-speed USB device number 57 using ohci-pci
[  +0.163914] usb 5-4: device descriptor read/64, error -62
[  +0.268123] usb 5-4: device descriptor read/64, error -62
[  +0.108038] usb usb5-port4: attempt power cycle
[  +0.775990] usb 5-4: new full-speed USB device number 58 using ohci-pci
[  +0.416007] usb 5-4: device not accepting address 58, error -62
[  +0.184007] usb 5-4: new full-speed USB device number 59 using ohci-pci
[  +0.034156] usb 5-4: not running at top speed; connect to a high speed hub
[  +0.013007] usb 5-4: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 4.04
[  +0.000008] usb 5-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000004] usb 5-4: Product: SDM636-MTP _SN:5A424592
[  +0.000003] usb 5-4: Manufacturer: ONYX
[  +0.000003] usb 5-4: SerialNumber: 8165caf3
[  +0.054088] usb 5-4: USB disconnect, device number 59
[  +0.510650] usb 2-4: new high-speed USB device number 91 using ehci-pci
[  +0.098000] ehci-pci 0000:00:13.2: port 4 reset error -110
[  +2.062091] usb 5-4: new full-speed USB device number 60 using ohci-pci
[  +0.160004] usb 5-4: device descriptor read/64, error -62
[  +0.296029] usb 5-4: not running at top speed; connect to a high speed hub
[  +0.011997] usb 5-4: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 4.04
[  +0.000010] usb 5-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000005] usb 5-4: Product: SDM636-MTP _SN:5A424592
[  +0.000004] usb 5-4: Manufacturer: ONYX
[  +0.000003] usb 5-4: SerialNumber: 8165caf3
[  +0.491929] usb 5-4: reset full-speed USB device number 60 using ohci-pci
[  +0.176024] usb 5-4: device descriptor read/64, error -62

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

[ilyats]

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

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.

[Renate]

It's clearly flailing.
Me, I'd connect my Beagle 480 USB hardware protocol analyzer.

I can't tell, does this support analog headphones in an adapter plugged into the Type C connector?
Or does it have a separate headphone jack?
The reason I ask if it it has analog over Type C then there is an additional multiplexor inline with the USB data.
That's another possible point of failure.

It looks like were talking warranty repair.

[ilyats]

Originally Posted by Renate

It's clearly flailing.
Me, I'd connect my Beagle 480 USB hardware protocol analyzer.

I can't tell, does this support analog headphones in an adapter plugged into the Type C connector?
Or does it have a separate headphone jack?
The reason I ask if it it has analog over Type C then there is an additional multiplexor inline with the USB data.
That's another possible point of failure.

It looks like were talking warranty repair.

It seems to have started working again. For warranty repair I have to travel to another city (I was considerate enough to buy it from an Israeli seller so I don't have to send it to China.)