You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Contains a solution.]Android Bluetooth mouse and keyboard remote access to PC, after a period of time, the mouse and keyboard input becomes unresponsive, but the screen transmission remains normal.
#2438
Closed
3 tasks done
EnderCore opened this issue
Apr 18, 2024
· 3 comments
在我使用安卓串流链接pc时,当我使用蓝牙键鼠远程控制pc一段时间后(通常在几十分钟到一个小时),无论是键鼠还是触摸屏都无法控制远程pc(此时无法重启sunshine服务端,通过任务管理器杀死进程后sunshine也无法手动重新启动(杀死后手动打开,但是没有如何反应,可能任务管理器没有杀死他),此时只能重启PC),此时如果我直接操作sunshine服务端所在的pc时会发现键盘会保持按下操控链接断开前我最后按下的那个按键,直至我在服务端用usb链接键盘再次按下才那个按键时,pc的控制才能恢复正常,此时,远程串流的控制才能恢复正常When using an Android streaming link to connect to my PC, after a period of remote control with a Bluetooth keyboard and mouse (typically ranging from several tens of minutes to an hour), neither the keyboard, mouse, nor touchscreen can control the remote PC. At this juncture, restarting the Sunshine server is not feasible. Even after terminating the process via the task manager, manual attempts to restart Sunshine prove futile (despite attempts to manually reopen it, there is no response, possibly indicating the task manager's failure to terminate it). Hence, the only recourse is to reboot the PC. Should I directly operate the PC where the Sunshine server resides during this time, I notice that the keyboard maintains the last pressed key until I press it again using a USB-connected keyboard at the server end. Only then does control of the PC resume, and consequently, normal remote streaming control is restored.
EnderCore
changed the title
Android Bluetooth mouse and keyboard remote access to PC, after a period of time, the mouse and keyboard input becomes unresponsive, but the screen transmission remains normal.
[Contains a solution.]Android Bluetooth mouse and keyboard remote access to PC, after a period of time, the mouse and keyboard input becomes unresponsive, but the screen transmission remains normal.
Apr 18, 2024
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the nightly release?
Describe the Bug
在我使用安卓串流链接pc时,当我使用蓝牙键鼠远程控制pc一段时间后(通常在几十分钟到一个小时),无论是键鼠还是触摸屏都无法控制远程pc(此时无法重启sunshine服务端,通过任务管理器杀死进程后sunshine也无法手动重新启动(杀死后手动打开,但是没有如何反应,可能任务管理器没有杀死他),此时只能重启PC),此时如果我直接操作sunshine服务端所在的pc时会发现键盘会保持按下操控链接断开前我最后按下的那个按键,直至我在服务端用usb链接键盘再次按下才那个按键时,pc的控制才能恢复正常,此时,远程串流的控制才能恢复正常When using an Android streaming link to connect to my PC, after a period of remote control with a Bluetooth keyboard and mouse (typically ranging from several tens of minutes to an hour), neither the keyboard, mouse, nor touchscreen can control the remote PC. At this juncture, restarting the Sunshine server is not feasible. Even after terminating the process via the task manager, manual attempts to restart Sunshine prove futile (despite attempts to manually reopen it, there is no response, possibly indicating the task manager's failure to terminate it). Hence, the only recourse is to reboot the PC. Should I directly operate the PC where the Sunshine server resides during this time, I notice that the keyboard maintains the last pressed key until I press it again using a USB-connected keyboard at the server end. Only then does control of the PC resume, and consequently, normal remote streaming control is restored.
Expected Behavior
No response
Additional Context
No response
Host Operating System
Windows
Operating System Version
11
Architecture
64 bit
Sunshine commit or version
0.23.0
Package
Windows - installer
GPU Type
Intel
GPU Model
XE
GPU Driver/Mesa Version
31.0.101
Capture Method (Linux Only)
No response
Config
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: