-
Notifications
You must be signed in to change notification settings - Fork 581
Description
What is the issue or idea you have?
I am experiencing two main issues while using STF (Smartphone Test Farm):
-
Device screen does not respond to clicks:
When connecting devices such as Xiaomi Redmi Note 14 and Samsung Galaxy Tab, the device screen appears successfully in the browser, but touch/click actions do not register neither back and home buttons work.
However, actions like opening Developer Options, Settings, etc., using the side buttons work normally.
This happens on Xiami Redmi note 14 but not on Galaxy Tab A9. On Tab it works fine -
ADB authentication failure after reconnecting:
On first connection, running adb connect ip:port works correctly and the device connects.
But after disconnecting and attempting to reconnect, it consistently shows:
failed to authenticate
This behavior occurs across both tested devices.
Does it only happen on a specific device? Please run adb devices -l and paste the corresponding row.
No, the issue occurs on multiple devices.
I tested on:
- Xiaomi Redmi Note 14
- Samsung Galaxy Tab A9
Please provide the steps to reproduce the issue.
- Set up STF and connect a device from another machine.
- From the second machine, run adb connect to connect via WiFi/remote ADB.
- Access the device in the STF browser interface.
- Observe that:
- The UI loads, but clicks/taps do not work.
- Disconnecting and reconnecting the device causes failed to authenticate errors.
What is the expected behavior?
- The device screen should be fully interactive, allowing click/touch events from the browser.
- ADB authentication should not fail on reconnection; the device should pair and reconnect reliably.
Do you see errors or warnings in the stf local output? If so, please paste them or the full log here.
No relevant errors or warnings appear in the stf local logs.