I am experiencing an issue with USB connectivity on my Redmi Note 13 4G running HyperOS.eu version 2.0.10.0 Stable
When I connect the device to my computer, it initially only charges. Neither MTP (File Transfer) nor ADB are detected immediately. The device eventually gets detected correctly for data transfer, but only after I re-plug the USB cable several times(or wait for about 2 minutes) which is very frustrating.
This behavior is specific to HyperOS.eu on this device. I previously used several AOSP-based ROMs on the same Redmi Note 13 with the same computer and cables, and USB detection (both MTP and ADB) was instant and reliable every time.
To investigate the issue, I captured dmesg logs on my system when the device was connected and only charging initially. The logs show that the system briefly attempts to identify the phone as a UVC (USB Video Class) device before eventually recognizing it correctly as a Xiaomi phone (Vendor ID 2717, Product ID ff48). This suggests a potential issue with how HyperOS.eu initializes the USB connection and presents the device descriptors to the host system.
Here are the relevant dmesg logs from the point of connection until detection:
Since this issue did not occur on AOSP ROMs, I suspect it is related to the HyperOS.eu ROM's handling of the initial USB connection.
Could you please look into this behavior? Any assistance or guidance would be greatly appreciated. Thank you for your great work.
When I connect the device to my computer, it initially only charges. Neither MTP (File Transfer) nor ADB are detected immediately. The device eventually gets detected correctly for data transfer, but only after I re-plug the USB cable several times(or wait for about 2 minutes) which is very frustrating.
This behavior is specific to HyperOS.eu on this device. I previously used several AOSP-based ROMs on the same Redmi Note 13 with the same computer and cables, and USB detection (both MTP and ADB) was instant and reliable every time.
To investigate the issue, I captured dmesg logs on my system when the device was connected and only charging initially. The logs show that the system briefly attempts to identify the phone as a UVC (USB Video Class) device before eventually recognizing it correctly as a Xiaomi phone (Vendor ID 2717, Product ID ff48). This suggests a potential issue with how HyperOS.eu initializes the USB connection and presents the device descriptors to the host system.
Here are the relevant dmesg logs from the point of connection until detection:
[ 4005.373648] usb 2-8: Failed to query (GET_INFO) UVC control 2 on unit 2: -110 (exp. 1).
[ 4010.492810] usb 2-8: Failed to query (GET_INFO) UVC control 3 on unit 2: -110 (exp. 1).
[ 4015.613198] usb 2-8: Failed to query (GET_INFO) UVC control 6 on unit 2: -110 (exp. 1).
[ 4020.732999] usb 2-8: Failed to query (GET_INFO) UVC control 7 on unit 2: -110 (exp. 1).
[ 4025.852919] usb 2-8: Failed to query (GET_INFO) UVC control 8 on unit 2: -110 (exp. 1).
[ 4030.973282] usb 2-8: Failed to query (GET_INFO) UVC control 9 on unit 2: -110 (exp. 1).
[ 4036.092995] usb 2-8: Failed to query (GET_INFO) UVC control 10 on unit 2: -110 (exp. 1).
[ 4041.212951] usb 2-8: Failed to query (GET_INFO) UVC control 1 on unit 2: -110 (exp. 1).
[ 4046.333301] usb 2-8: Failed to query (GET_INFO) UVC control 5 on unit 2: -110 (exp. 1).
[ 4051.453668] usb 2-8: Failed to query (GET_CUR) UVC control 5 on unit 2: -110 (exp. 1).
[ 4056.573634] usb 2-8: Failed to query (GET_INFO) UVC control 11 on unit 2: -110 (exp. 1).
[ 4061.693068] usb 2-8: Failed to query (GET_INFO) UVC control 2 on unit 1: -110 (exp. 1).
[ 4066.813308] usb 2-8: Failed to query (GET_INFO) UVC control 3 on unit 1: -110 (exp. 1).
[ 4071.933115] usb 2-8: Failed to query (GET_INFO) UVC control 4 on unit 1: -110 (exp. 1).
[ 4082.173553] usb 2-8: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
[ 4087.293232] uvcvideo 2-8:1.1: Failed to query (129) UVC probe control : -110 (exp. 26).
[ 4087.293242] uvcvideo 2-8:1.1: Failed to initialize the device (-5).
[ 4087.293626] usb 2-1: USB disconnect, device number 66
[ 4087.543146] usb 2-1: new high-speed USB device number 68 using xhci_hcd
[ 4087.676496] usb 2-1: New USB device found, idVendor=2717, idProduct=ff48, bcdDevice= 5.15
[ 4087.676503] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4087.676506] usb 2-1: Product: Redmi Note 13
[ 4087.676508] usb 2-1: Manufacturer: Xiaomi
[ 4087.676510] usb 2-1: SerialNumber: <redacted>
[ 4087.686323] usb 2-8: USB disconnect, device number 67
[ 4087.929803] usb 2-8: new high-speed USB device number 69 using xhci_hcd
[ 4088.128306] usb 2-8: New USB device found, idVendor=5986, idProduct=0268, bcdDevice= 0.03
Since this issue did not occur on AOSP ROMs, I suspect it is related to the HyperOS.eu ROM's handling of the initial USB connection.
Could you please look into this behavior? Any assistance or guidance would be greatly appreciated. Thank you for your great work.
