August 24, 2020 at 07:31 #29087
I am currently experimenting with the Android Client in Desktop Mode (Galaxy S10, DEX).
Two problems came up:
- The attached keyboard behaved in a weird way. Alphabetical keystrokes (exclusively, numbers were not affected) only register in the remote session after the repeat delay is passed, and then I get multiple letters of course. This only occurs in the remote session within the NoMachine app, not in other apps (i.e. Chrome).
- The NoMachine app does not seem to support fullscreen in desktop mode, I can maximize the window, but then the DEX task bar stays in front, the window borders still exist and the remote session does not use all the available screen dimensions. There seem to be several apps (Netflix, Amazon) which properly support fullscreen in DEX mode, though I have no personal experience with them.
Any thoughts?August 28, 2020 at 14:50 #29222
Hi. Are you using the DeX box or the DeX application? The weird keyboard behaviour occurs also when using the app interface (e.g. when filling the hostname input), or only in the remote desktop? What is the remote desktop OS/Version?August 31, 2020 at 08:02 #29224
I use the following adapter:
So the Android device is directly connected to the monitor via HDMI, plus keyboard and mouse.
The weird behaviour does not occur in the app interface, only remote.
Remote OS is Ubuntu 20.04 with KDE Desktop.September 7, 2020 at 11:10 #29381
We still didn’t reproduce the issue, but we’ve found a problem with the backspace key which could be related and we’re investigating it. In the meanwhile you could try to install Simple Keyboard from the Store and switch to it when running NoMachine (even if using the external keyboard): one of our users has experienced a similar issue and has found that such keyboard app helps to work around the unexpected Android 10 kernel behaviour.September 10, 2020 at 07:56 #29406
I can confirm that the “Samsung Keyboard” is mostly to blame. With “Simple Keyboard” I no longer have the situation that all alphabetical keys are stuck, input feels a bit sluggish, which is acceptable in a remote session (however some keystrokes seem to get missed entirely with fast typing).
On another note, the right mouse button of a real mouse connected via USB is really difficult to trigger (something like: hold both buttons for two seconds). It seems to be related to right button emulation in touch mode. Is there a way to disable that?September 28, 2020 at 09:39 #29673
On another note, the right mouse button of a real mouse connected via USB is really difficult to trigger (something like: hold both buttons for two seconds). It seems to be related to right button emulation in touch mode. Is there a way to disable that?
We’re checking it and so far we didn’t find workarounds. I’ll tell you more as soon as we complete the investigation.September 30, 2020 at 15:24 #29732
Hi again. We’ve confirmed the issue, it’s caused by the mouse event ID received through DeX which bypasses our code translating the right mouse button event. Because of such issue these events are handled like touch events, so if you keep pressed the left mouse button you should trigger the right button event (it’s the tap&hold gesture). However we’ve documented here your report:
This topic was marked as solved, you can't post.