Bug Report

Scroll wheel of external mouse is not working unless scrolling very fast, which is insensitive.

When I connect to a standard win 10 RDP server from my tablet I want to have full available area used, so I selected "Current work area size" and "Dynamic resolution" options in the display tab of RDP entry settings, to make it adjust to the available area. After I connect, there are black bars on the left and right edge of the connection. Instead of adjusting the connection dimensions, the connection is scaled down to fit. The same happens when the full screen mode is entered, but instead, the black bars appear on the top and bottom of the screen, in the place where status bar and navigation bar + bottom connections strip normally reside. Also the connection is done at 1:1 DPI scaling, instead of following the android DPI settings, so text is super small on high resolution display. Enabling "Force dynamic resolution" option does not change anything upon reconnection and the toggle for it is reverted to turned off state. Rotation of a device also does not trigger the resolution change of the RDP connection and old aspect ratio is just rotated, creating even bigger black bars. Also, on rotation, the cursor gets glitched. Additionally, sometimes, when connecting, the connection dimensions will be too small. I think it is caused by some race condition with the code calculating available workspace dimensions, sometimes before, rather than after the on screen keyboard is hidden. I expect the behavior of "Current work area size" and "Dynamic resolution" options to be the same as the official RDP app from MS, with "Match this device" option enabled. It should always fill the whole available workspace area (minus status bar, navigation bar and connection strip, but only when they are visible) and recalculate dimensions whenever the full screen mode is entered, device is rotated or split screen/ multi window desktop mode is enabled and resized (like the Samsung dex or the new android 16 desktop mode from google). It should also always set the correct DPI. By default the DPI of the android device, maybe with an option to set it manually. In the attached screen recording it is shown what I described above. I use XML data source and app version is 2205.3.2.6.

As in video, the colors are shifted or inverted. Blue spinner is orange and red not-allowed is blue. Additionally, when changing window size, sometimes the cursor gets corrupted before the correct one is loaded, or a small black cursor is used. The cursor can be fixed from corrupted state or black icon by changing window size again, or changing cursor in OS, for example on the page https://vibhorjaiswal.github.io/Cursor-Test/ .

Hi, I have a problem with not being able to open context menus with a touchpad integrated into tablet keyboard - OnePlus Pad 3 QWERTY Smart Keyboard. I think the right mouse button isn't emitted by keyboard firmware, only left mouse button. I would like to have a way to make long press of a touchpad be treated as right click, just like with display touch. Additionally the tablet's keyboard win key is not caught nor the ctrl+shift+esc combo, but just esc key is caught as exit of android app. On external usb keyboard ctrl+shift+esc works, but win+x or just win key does not, and triggers gemini. I believe that keyboard shortcuts are android limitations, while tablet's keyboard has junk firmware and nothing can be done about those, but I would really like to have an option to support the touchpad with long press in RDM setting, to enable opening context menus.

I'm using RDP on Honor Magic7 Pro, an Android phone. All is perfect except some keys dont work with RDP 'plus' or 'equals' key. They works fine outside RDP all keys in number pad, regardless of num lock on/off I have tried encode key with unicode, which makes things worse, in which case only 'space' key works.

Device Model: Samsung Tab S8+ Operating System: Android 15, OneUI 7.0 RDM Version: 2025.2.0.17 Peripherals: External monitor, Bluetooth mouse, Bluetooth keyboard Specific Mode: DeX mode on extended screen, Tablet Mode on primary screen RDP will show blackscreen when you select the external screen in the dialog while the app is displayed in the main screen. You can also reactivate this bug when you first RDP on the primary screen and then run the app and start RDP session in the external. However RDP will only have this bug when remoting on the external one. I didn't see such bug when remoting on primary after alternating between screens. I think that probably it's because the primary screen runs the tablet mode, while in the external one it runs DeX. FIX: This can be easily fixed (for now) by force-stop RDM and then start it up again. However I think it's worthwhile to report this to you. Please evaluate this bug and fix it if you consider it worth-fixing. Thanks!

Sometimes the button for creating a new entry is missing from the vault tab and reappears only on a refresh.

When fullscreen mode is used with dynamic resolution, current work area size and auto scale factor, the resizing of the window like split screen mode or free form window or when rotating a device or locking and unlocking it causes fullscreen mode to be reset - shows a bottom bar with sessions and the floating bar at the top. Video timestamps: 0:17 - screen lock and unlock - bars show up, screen is not resized, should instead be exactly the same as before locking the screen 0:34 - entering split screen (or free form window also) exits active RDP session and shows menu, should instead just resize the session accordingly to new window size, and keep previous fullscreen state (not show bottom bar and floating top bar), and not draw behind top black inset with system ui of a window (sometimes it doesn't, sometimes it does, should be always like in 0:44) 0:49 - resizing window should not reset fullscreen state, just resize the fullscreen to new working area. Now it shows bottom bar but doesn'tt show top floating button, when this bugged fullscreen / not fullscreen mode is present 1:20 - sometimes resizing window causes the cursor to become corrupted

Hello, I found a reproducible issue with the Android version of Remote Desktop Manager. Environment: App: Devolutions Remote Desktop Manager (Android) 2025.2.2.2 Device: Samsung Galaxy A14 5G Android: 15 RDP Server: Windows Server 2025 Datacenter, Build 26100.gt_release.240331-1435 (Test Mode) Steps to Reproduce: Start an RDP session (default resolution or manual resolution 1024×768 / 1920×1080). Tap the blue top toolbar → three-dot menu → “Fullscreen”. The app closes immediately. Observed Result: Default resolution → crash instantly. 1024×768 → crash within ~1 second. 1920×1080 → crash within 2–5 seconds. Expected Result: The RDP session should remain stable and continue running in fullscreen mode. Other RDP apps on the same device and server (e.g., Microsoft RD Client) work fine without this issue. Thank you.

Hi during a test I noticed that the Android app remote desktop crashes in these modes: 1) Closed any instances of the app and App launch containing approximately 865 records 2) delete a Entry folder whit With approximately 500 internal records, 3) After delete I immediately try to import a previous password-protected RDM backup to a file on the device .rdm and created shortly before testing, but after select the file from explorer resource, the application immediately closes. 4) I relaunch it, perform the same operation ( only restore backup. rdm ) , and everything works perfectly. The problem seems to only occur if I try to restore a .rdm backup immediately after performing a record delete operation. Pixel 10 pro xl whit Android 16 Some Adroid Debug info : 10-25 10:40:01.471 2094 2094 E libbinder.IPCThreadState: Binder transaction failure. id: 377569573, BR_*: 29201, error: -28 (No space left on device) // personal note: it's wrong space there is plenty of it 10-25 10:40:01.471 2094 2094 E JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 659896) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: FATAL EXCEPTION: main 10-25 10:40:01.473 2094 2094 E AndroidRuntime: Process: com.devolutions.remotedesktopmanager, PID: 2094 10-25 10:40:01.473 2094 2094 E AndroidRuntime: java.lang.RuntimeException: android.os.TransactionTooLargeException: data parcel size 659896 bytes 10-25 10:40:01.473 2094 2094 E AndroidRuntime: Bundle stats: 10-25 10:40:01.473 2094 2094 E AndroidRuntime: CONNECTION_DELETE_INFOS [size=638644] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: android:viewHierarchyState [size=1776] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: android:views [size=1724] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: androidx.lifecycle.BundlableSavedStateRegistry.key [size=17640] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: androidx.lifecycle.internal.SavedStateHandlesProvider [size=1108] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: android:support:activity-result [size=2856] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: KEY_COMPONENT_ACTIVITY_REGISTERED_KEYS [size=2236] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: android:support:fragments [size=13304] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: fragment_b81b43ee-b0e7-4080-bc08-3dbe258e34d2 [size=6796] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: viewState [size=4416] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: registryState [size=1388] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: androidx.lifecycle.BundlableSavedStateRegistry.key [size=1260] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: androidx.lifecycle.internal.SavedStateHandlesProvider [size=1128] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: fragment_55299676-9306-457f-a581-eb1d9580a475 [size=2936] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: registryState [size=1072] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: fragment_a713235b-fe04-4720-81c4-22a0c4d52bbb [size=2636] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: registryState [size=1316] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: androidx.lifecycle.BundlableSavedStateRegistry.key [size=1188] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: androidx.lifecycle.internal.SavedStateHandlesProvider [size=1056] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: PersistableBundle stats: 10-25 10:40:01.473 2094 2094 E AndroidRuntime: [null] 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.app.servertransaction.PendingTransactionActions$StopInfo.run(PendingTransactionActions.java:146) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:1041) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:103) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.os.Looper.dispatchMessage(Looper.java:315) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:251) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.os.Looper.loop(Looper.java:349) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:9041) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: Caused by: android.os.TransactionTooLargeException: data parcel size 659896 bytes 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.os.BinderProxy.transactNative(Native Method) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.os.BinderProxy.transact(BinderProxy.java:592) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.app.IActivityClientController$Stub$Proxy.activityStopped(IActivityClientController.java:1560) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.app.ActivityClient.activityStopped(ActivityClient.java:100) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: at android.app.servertransaction.PendingTransactionActions$StopInfo.run(PendingTransactionActions.java:135) 10-25 10:40:01.473 2094 2094 E AndroidRuntime: ... 9 more Best regards

Hello, On Android 16 on RDM version 2025.2.2.2 i cant use my ssh key files in the "File (local)" mode, but i can copy the key and paste them in the "Embedded data" and it's working. It just says it can't connect. Cheers

Hi, I've recently encountered an issue when using the keyboard with RDP (Microsoft Remote Desktop). When typing alphabet characters using the Samsung keyboard on Android, the characters are sent as Unicode, even though the "Send input as unicode" option is set to "No" under Local Resources in entry setting.

Hi, I'm using Remote Desktop Manager on both my Samsung S25U and my Google Pixel phone, and I'm having issues using the keyboard. When connecting to a Linux VNC server (TigerVNC), when I try to type keys with modifiers like Ctrl-C, Ctrl-X, Ctrl-D it doesn't work, it sends other kind of keys in its place (for example, in a terminal, if I type Ctrl-X, instead it presses Ctrl-Minus which is the shortcut to zoom out). But typing normal keys (without modifier) is fine. I can fix that problem by enabling the "legacy keyboard processing", and now Ctrl shortcuts are working again. But if I enable that option, then connecting to RDP is a problem: the keyboard layout is wrong (QWERTY instead of my usual AZERTY), even after changing the keyboard layout in RDM options. If I switch "legacy keyboard processing" back off, RDP works fine again. So I have to set that option in advance depending on the type of server I'm connecting to ;) I already tried the "keyboard layout compatibility mode" without success. Tell me what I should try next.

Hi, I'm using RDP for my scenario and enabled option "Use Pointer Capture" to avoid title bar popping up. When I'm selecting text (click and drag to select) with my external mouse, the selection was removed when left button was lifted (probably because an extra left click was sent). My device is Samsung Tab S8+, DeX mode with external monitor and bluetooth mouse/keyboard. Changing Long Press Delay time can alleviate this bug on certain apps, and disabling the option "Use Pointer Capture" will not cause this bug to happen. (But the annoying title bar will pop up in fullscreen) Any people with this bug as well? Thanks!

[image] The left lower side "1/2" key and the right side "123" key are not working. When touched them, nothing happended. Please, check not only the keys that I mentioned but also the entire keys.

After the last update I am having a small issue with my navigation Bar in Android. I have it enabled all the time as well as the legacy toolbar. So I have Quick Access for my system as well as the application buttons. After the update glitch at the moment I'm opening my gboard. The navigation bar becomes see trough as well as the application extends to so it's behind the navigation bar. Making it almost impossible to press any button from the legacy toolbar. After disabling My gboard it's going back to normal and it's not being blocked by the Navigation Bar anymore. I've also tried disabling The Navigation Bar in the settings. But then it still pops up as a see-through navigation bar when opening the gboard. Which is the normal function in Android.

When attempting to connect via RDP, there is a frequent issue where the session remains stuck on the login screen, or the mouse cursor moves but fails to progress beyond the login screen.

Hi, I wanted to try your RDP application to scan barcodes in warehouse, but the application does not recognize them. I am using a Cipherlab RK95. Is there something I should activate in settings or something? We are using Windows Server. Thanks.

Dear developer, thank you for your fantastic work of the app, it really helps me a lot. But I find that I can not type whitespace and numbers when I try to use bluetooth keyboard in a remote control session to macos (through ARD session) . I am sure the bluetooth keyboard is working fine as all characters can show up correctly in my Android phone.

Hey, First off, thanks for the great app, it's my new favorite remote desktop app with lots of easy working functions. There is a single (important) function that doesn't work properly when i'm connected with my remote desktop through the app. My Gboard app is working in a basic version, meaning I can only type without the additional assistance. The other functions: slide, settings, auto correct or gettiing suggestions aren't available. I've used other remote apps before, and another had the same issue. But they had an option to choose to have plain text app or with the added functions allowed. Tries it with different keyboard apps and tried many different settings, all without succes. Typing on a keyboard or phone without these options is almost impossible to do after we get used to having the assistances helping out. So would be great to hear if i'm searching in the wrong settings, or this is done on purpose?

the keyboard shortcut does not working correctly, please refer to the screen record for more detail RDM Version 2024.3.2.6

App version:2024.3.3.7 Android version: 14 Model: Xperia 1 V Step to reproduce: 1. Set "Always open the sessions in landscape mode" on in setting 2. Connect an RDP Connection when phone is in portrait mode 3. RDM said user logout when the session showing login page (welcome page)

for andriod mobile phone to use RDP connection, when enabling "always open the sessions in landscape mode" in app setting, if you don't set your mobile phone at auto switch between the landscape and portrait screen, say you lock it at portrait view, then it can not connect the destination server, always failed.

Hi Devolutions, when connecting via RDP my Android device to my Windows workstation the keys y and z are swapped. Only the two ones, all other keyboard keys send their correct symbol. Environment: Server (connected-to device): Windows 10, 2004, installation language German, loggedon UI German Client (connected-from device): Samsung Galaxy S10e or Samsung Tab A, both Android 10 with German UI App: RDM Android V2020.2.1.0 RDP-Settings in RDM: Local Resources > Keyboard: German (Germany), Send input as unicode: Default Tested alternatives/workarounds: a) installed second keyboard "English (United States), US-keyboard layout" on Windows PC. When switching to this keyboard within a RDP session Y and Z are on their right keyboard position AND all other keys are also like on a German keyboard (not in US-Keyboard layout! BTW: Same constellation directly working from console with a German keyboard -> US-keyboard is applied ";" below "ö", "/" below "-" caps, ...) b) Setting "Send input as unicode: True" in RDP-Connection property. Y and Z are correctly end to programs (keyboard layout on PC: German) BUT CTRL-Y and CTRL-Z are still swapped, meaning when I'm pressing CTRL-Z on the Android German Keyboard the PC is receiving CTRL-Y Can you fix this? Regards Markus

Hello! I installed your application(Android) only because of the feature of forwarding smart cards to RDP sessions. But when I try to connect to a server with smart card authentication, the server does not see any smart cards. Server based on Windows Server 2022 standard. It runs a certification center and clients connect using USB tokens (smart cards).