CTRL+C not forwarded to SSH when typed on physical bluetooth keyboard

Hi Devolutions,

I recently started using Remote Desktop Manager on my Samsung Galaxy Tab Android tablet, and I'm very happy with it, as it is much better than the application I used previously. There is however one problem, which makes it very difficult to use.

I'm using my Android tablet in combination with a physical bluetooth keyboard (a Logitech K380). In a SSH session to a Linux server, the CTRL+<key> combinations do not seem to be correctly forwarded. This is at least not working for CTRL+C, CTRL+A and CTRL+K. I use those keyboard shortcuts a lot (in combination with `screen` and `joe`).

When I'm in a SSH session, and I disconnect the physical keyboard, the virtual on-screen keyboard is shown, and pressing CTRL+C is then working correctly (still being in that same session). Also with another Android application ('ConnectBot'), to the same server from the same tablet, with the same keyboard, the CTRL+C, CTRL+A and CTRL+K combinations are working without a problem. The same 'terminalinfo' and 'locale' settings are used in the SSH session by the Remote Desktop Manager and 'ConnectBot' applications.

I have tried different settings within the configuration of Remote Desktop Manager, and with different settings in the SSH Session configuration, however this doesn't resolve the problem.
I have tried different 'keyboard providers' (Swiftkey, Samsung keyboard and GBoard), but they all have the same problem when the physical keyboard is used. My preliminary conclusion is that Remote Desktop Manager does not correctly handle the CTRL+<key> presses when a physical keyboard is being used.

Used Remote Desktop Manager software version: 2024.1.5.3.

I hope this provides you with sufficient information, otherwise please let me know, if you need more information.
Can you investigate this problem, and advise a workaround or provide a solution?

Thanks in advance,
John