SS15
Page 30 of 38
3
.
If this still doesn’t work, turn off the developer options at the top, re-enable it, and re-
enable ‘USB Debugging
.’
4
.
You can get detailed info directly from ADB at each step to diagnose things
:
adb.exe shell dumpsys battery
#
Use -s SERIAL_NUMBER as first options if you have more than 1 Android attached
Unknown devices
Sometimes, within Liveviewer and device manager, the connected device may show up as an
unknown device
.
This can be due to the host system needing to be trusted on the device. This can be done on
the device itself on the initial connection
.
This could also be due to an insufficient number of endpoints available on the USB controller in
the host system. This limitation within the USB controller can only be resolved if you connect
fewer USB devices to the controller in question
.
For Apple devices there is a setting called "USB accessories" which can be activated, Once
activated it will reduce the amount of times a device will need to be unlocked/ trusted. More
information can be found at the link
.
Cannot connect any more devices
Sometimes, you may reach the endpoint limit of your USB controller and this may stop you
from being able to attach any more devices to your host system
.
You can create more space is to change connections from USB3 to USB2. You can change the
connection by disabling USB3 in the BIOS on startup
.
A much simpler way is to use USB2 cables instead of USB3 cables, limiting the connection to
USB2
.
7.5
.
Hub connection issues
If you have issues with the hub and connecting to your host system, please see below
troubleshooting solutions
.
