[Teracube 2e/Emerald] USB OTG dongle not working after 1.17-s upgrade
- /e/ version: 1.17-s
- Device model(s): emerald
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes/no
Summary
Since upgrading my Teracube 2e ('emerald' variant) to /e/OS 1.17-s, the device no longer recognizes when a USB OTG adapter is inserted.
The problem
Steps to reproduce
- Upgrade a 2e/emerald device from 1.16-s to 1.17-s via OTA,
- Insert a USB OTG dongle with storage device or keyboard/mouse attached.
What is the current behavior?
OTG dongle and attached device receive no power (indicated by LEDs on the device), trigger no events within the UI.
What is the expected correct behavior?
The dongle and attached device should power up and Android should report that USB storage is plugged in (if used with a USB pen drive) or indicate a keyboard is plugged in (when using with a USB keyboard).
While I only have a single OTG dongle to test with, I've ruled out port failure on the phone (USB charging and file transfer work as expected) and hardware failure of the dongle itself (it works as expected when attached to another phone).
Technical information
Executing lsusb
in a rooted ADB shell shows a single USB device (a root hub) regardless if the dongle's inserted or not. Meanwhile, a different, healthy phone shows three devices with the dongle inserted and none with it removed.
emerald:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
For comparison, other Android phone with OTG dongle inserted (0781:5575
is the ID of the pen drive attached to the adapter):
channel:/ # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 0781:5575
Bus 002 Device 001: ID 1d6b:0003
I can provide logcats upon request, but please let me know what to filter for.