Launcher remote prevents server from dequeing event handlers making remote control unusable
Tomasz Kłeczek 12
After a program is launched by "Launcher" remote, no further interaction between client app and server is possible (the event handlers are received by the server and enqueued, but are never dequeued/handled).
When the application is closed manually on the server OS, all the events that were received during the period app was launched are dequeued and remote client is usable again.
Reproduce steps (reproducibility: 4/4 on my setup):
Choose "Launcher" remote
Choose any application (e.g. tried 'VLC', 'Image viewer', 'Smplayer', 'Firefox')
=> Result: The application is launched and and the remote control is not working until application is closed.
Device OS: Android 6.0.1
Sever OS: Fedora 24
UR Server Version: 22.214.171.1240
UR Client Version: 3.7.1 (37003)
Program I try to control: does not matter, the problems exists no matter which exact application I am trying to launch.
Same behavior is observed for Command launcher.
Also for newer app versions:
Device OS: Android 8.1.0
Sever OS: Ubuntu 16.04
UR Server Version: 126.96.36.1995
UR Client Version: 3.11.0 (311000)