REPRODUCIBILITY: 100% (on Windows desktop) 0% (on Tumbleweed laptop)
OS VERSION: Win10 64 (10.0.19044) Sailfish (4.4.0.68)
HARDWARE: Xperia 10 iii
UI LANGUAGE: English
REGRESSION: Yes (compared to existing XA2 Plus phone which continues to connect fine)
DESCRIPTION:
Connecting to Win10 desktop via MTP Media Transfer mode generates a generic Windows device connection “ping”, followed by a notification pop-up from Windows Explorer saying “USB device not recognised”
Checking Device Manager the Xperia 10 iii is listed under [Universal Serial Bus Controllers] with a warning sign and “Unknown USB Device (Configuration Descriptor Request Failed)”
When connecting my XA2 Plus (also running 4.4.0.68) via MTP Media Transfer mode it connects with no issues. Same USB port, same USB cable.
Checking Device Manager the Xperia XA2 Plus is listed under [Portable Devices] as an “Xperia XA2 Plus -Dual Sim”
n.b. Using the same cable on a laptop running Opensuse Tumbleweed, both devices will connect fine.
n.b. This same Desktop / Windows / USB port / Cable was able to connect to the phone fine as part of the Sailfish flashing process.
PRECONDITIONS:
This occurs regardless of whether i try with the device as it was originally recognised under Device Manager:
[Universal Serial Bus Controllers] with a warning sign and “Unknown USB Device (Configuration Descriptor Request Failed)”
Or if I reconnect after having chosen to Uninstall that unknown USB device from Device Manager.
STEPS TO REPRODUCE:
- Attach USB cable
- Select “Media Transfer (MTP)” mode
EXPECTED RESULT:
As per my experience with the XA2 Plus over three and a half years and five major SFOS versions:
- Attach USB cable
- Select “Media Transfer (MTP)” mode
- Generic Windows device connection “ping”
- Windows explorer window opens on device \root
ACTUAL RESULT:
- Attach USB cable
- Select “Media Transfer (MTP)” mode
- Windows notification informs “USB device not recognised”
- Listed in Device Manager as “Unknown USB Device (Configuration Descriptor Request Failed)”
MODIFICATIONS:
Clean install of 4.4.0.68 on a brand new Xperia 10 iii checked as finctional in android before flashing.
ADDITIONAL INFORMATION:
Q - might this have something to do with the fastboot driver installed as part of the flashing process?
i.e. It is no longer the device Windows recognised it to be before flashing.