Dynamic resolution not working
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.
output.mp4
All Comments (7)
Hi,
Thank you for the detailed feedback. We will investigate the issue.
Best Regards,
Nicolas Dufour
Hello,
We investigated the issue and found that a regression made the Dynamic Resolution feature less reliable. We also identified a problem with the Force Dynamic Resolution setting. A fix has been implemented and will be entering testing very soon.
Regarding DPI scaling, there is an option you can enable to achieve the same behavior as the Windows app. You can find it under Session Settings > Auto scale factor (in the same location as the Force Dynamic Resolution setting).
We are aware that the Windows app applies resolution and DPI settings simultaneously when the Match this device option is enabled. While we initially implemented the behavior the same way, we received feedback from users who preferred having these options separated, as it provides greater flexibility and customization.
Best Regards,
Frederick Simard
You are right, I didn't see the DPI setting before. Good to know it's there. It would be good to ask a user when they change to "Dynamic Resolution" mode, if they also want to apply Android default DPI scaling by enabling "Auto scale factor". It could redirect to a page with DPI settings. It would fix the issue of not knowing it exists.
Hello,
Our next release will include a fix for the reliability issue you encountered when using Dynamic Resolution.
Regarding the DPI settings, we have created a ticket to make this feature clearer and easier to use in combination with Dynamic Resolution.
Best Regards,
Frederick Simard
Tested 2025.3.3.2 and the settings now work as I expected them to. In another bug report I specified a bug with connection using play button, so I tested it with quick connect feature. There is a UI bug with quick connect feature also. When I connect through it a modal with a spinner and a text "Opening connection" appears. After that the RDP session is opened and visible/ usable normally, but after two consecutive swipe backs to exit rdp and go back to vault screen, the modal is still visible, it is never destroyed. only closing the app from recents makes it go away, because it blocks access to any other UI element with black fullscreen backdrop.
Hello,
Thank you for reporting this issue, we were able to reproduce.
We will investigate and get back to you as soon as possible.
Best Regards,
Frederick Simard
I've just updated to 2026.1.0.25, and all the mentioned issues, seam to be fixed, thanks!