A phone that connects fine, works for a few minutes of file transfer or a logcat session, and then just drops off without any error, cable wiggle, or visible cause is a specific and frustrating pattern. It usually isn't the driver at all — it's a Windows power-management feature called USB selective suspend deciding the port has been idle long enough to power it down, and an Android phone mid-transfer doesn't always generate enough continuous traffic to convince Windows otherwise.
Selective suspend lets Windows power down individual USB ports independently rather than the whole USB controller, extending battery life on laptops by cutting power to devices Windows judges to be idle. The judgment of "idle" is based on USB traffic patterns that were designed with mice, keyboards, and printers in mind, not with a phone running a background ADB connection that sends data in irregular bursts rather than a steady stream.
adb logcat session or file copy drops partway through with no error in the phone's own USB notification, which stays showing as connected on the phone's side even after the PC has lost it.Disabling this only for the specific USB Root Hub the phone uses, rather than globally, keeps the battery-life impact minimal on a laptop while still fixing the disconnect for that port.
If disabling selective suspend on every root hub doesn't change anything, the disconnect is more likely a marginal cable or a genuinely loose port connection, since those produce a similar-looking but mechanically different disconnect pattern — often correlated with the laptop or cable being nudged, rather than purely with elapsed idle time.
For extended adb logcat captures or scripted automation that needs to survive hours unattended, combining a disabled selective suspend setting with switching the connection to Wi-Fi ADB removes the USB power-management variable from the equation entirely, since a wireless ADB connection isn't subject to USB port power states at all. Microsoft documents the underlying selective suspend mechanism in its USB driver design documentation for anyone building or debugging a driver against it directly.
Connecting through a USB hub introduces the hub's own power management alongside the PC's, and an unpowered or cheap hub is more aggressive about suspending idle downstream ports than a laptop's built-in root hub tends to be. Even after disabling selective suspend on every root hub in Device Manager, a hub sitting between the PC and the phone can still enforce its own suspend behavior that Windows' power settings don't directly control. Connecting the phone straight into a PC port, bypassing any hub entirely, is the fastest way to confirm whether a hub is the actual variable before spending more time adjusting Windows settings that don't reach the hub's own firmware.
Some laptops and desktops include their own firmware-level USB power management, separate from anything Windows controls, usually labeled something like "USB Power Delivery" or "ErP Ready" in BIOS/UEFI setup. Where the standard selective suspend fix in Windows doesn't fully resolve a disconnect pattern on a specific machine, checking for one of these firmware-level toggles, and disabling any aggressive power-saving mode there, occasionally succeeds where the operating-system-level settings alone did not.