Forum › Forums › spacedesk Discussions › Android USB connection only works with USB2.0 and not with USB3.1 (3.0)
- This topic has 5 replies, 2 voices, and was last updated 11 months, 1 week ago by spacedesk Christian.
-
AuthorPosts
-
December 6, 2023 at 7:58 am #24807vividParticipant
The Android USB connection only works when plugged into the USB2.0 port of my PC and not with USB3.1 (3.0). Is this expected behavior?
I tried “slowly plug and unplug USB cable a few times” as in the documentation and it works since it forces my USB3.1 cable to be recognized as USB2.0.December 6, 2023 at 9:00 am #24808spacedesk ChristianKeymasterHi @vivid,
spacedesk Android USB should work with both USB 2.0 and USB 3.0 ports and cables.
Have you tried troubleshooting your USB 3.1 port? does it work with file transfer?
Could you also try plugging it on your USB 3.1 port and check spacedesk Android Control in device manager if there are any errors (indicated by an exclamation mark).December 8, 2023 at 8:26 am #24824vividParticipantHello, Christian
Thank you for your responce.I’m trying several USB troubleshoot but currenty there is no improve.
File transfer seems to be working in USB 3.0.I found the following three messages:
####################################
Level: Error
Device USB\VID_0000&PID_0003\5&2cf64626&0&17 had a problem starting.
Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service:
Lower Filters: spacedeskDriverAndroidControl
Upper Filters:
Problem: 0x0
Problem Status: 0xC00000E5
####################################
Level: Warning
Device settings for USB\VID_0000&PID_0003\5&2cf64626&0&17 were not migrated from previous OS installation due to partial or ambiguous device match.
Last Device Instance Id: USB\VID_04D9&PID_4545\5&2cf64626&0&2
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0xF000FFFFFFFFF120
Present: false
Status: 0xC0000719
####################################
Level: Information
Device USB\VID_0000&PID_0003\5&2cf64626&0&17 was configured.
Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.22621.2506
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device Id: USB\CONFIG_DESCRIPTOR_FAILURE
Outranked Drivers: usb.inf:USB\CONFIG_DESCRIPTOR_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\ROOT_HUB30\4&6970116&0&0December 11, 2023 at 3:49 am #24844spacedesk ChristianKeymasterHi @vivid,
Could you maybe you please send us the Diagnostic logs of this Issue?
Just follow the steps below:
– open spacedesk Driver Console -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON (make sure to click Yes in the User Account Control box to proceed)
– please try to connect to your usb 3.1 port and reproduce the issue.
– switch Diagnostic Collection OFF
– click Save All Information button (if a message box appears, just click No to proceed)
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.December 11, 2023 at 7:58 am #24850vividParticipantHere you are.
I did a quick scan of Debugview.log and found USB 2.0 related messages around line 230, which maybe related to this issue?Attachments:
You must be logged in to view attached files.December 12, 2023 at 3:40 am #24865spacedesk ChristianKeymasterHi @vivid,
Did you plug in your cable before turning off the diagnostics?
Also, Could you please tell us the model of your Android device? -
AuthorPosts
- You must be logged in to reply to this topic.