Search results

So shall it be. It will be an option on client side not to revert after mobile change until Remotly is closed on host.

We will figure some solution to this out. The easiest thing would be not reverting to host resolution after changing it from mobile client. Is that ok? This would be an option available in the PC app. "Do not revert to host resolution after remote change" or something like that. This way...

Another problem we have seen with instant resolution change after connection is that a LOT of games have problems with this.

Eventually we could switch does displays that have the same aspect but there are a lot of phones that have panoramic screens so they will never match.

We cannot switch to client resolution if the monitor connected to host has a different aspect ratio since the image will be corrupted (stretched).

So for example when I have a phone with 1920x1080 screen and a host with two monitors one is 16:9 3840x2160 and the other one 21:9 3840x1440 then these monitors would need to switch to 1920x1080 and 2560x1080???

Unfortunately it's harder than we thought. The problem is when there are more than one display monitors connected to the remote host :/ This list is updated when switching remote monitors with the "change monitor" button after connection since each monitor can have different resolutions. So for...

I think we will do it on option which will be visible under the "change desktop resolution" and it will be named "remember changed desktop resolution". It will be disabled by default.

Not so good on our side with GPU-P on Nvidia with latest drivers. Hardware acceleration dissapears on RTX 5000 series. We are working on this right now. Nvidia does not make any regression tests. What's interasting is that these problems are happening now when they are replacing humans with AI...

Ok. Now I get it. Currently the "change desktop resolution" is not stored and is a volatile setting. We will add it to stored settings but this is tricky as someone might change the display monitor connected to the host for another one not supporting the same resolution as the previous one. In...

Hmm... but this is already possible for connections to logged in hosts (not using Connection ID). You can set connection quality like framerate, streamed video resolution and bitrate for each host separately (using the settings cog next to device dropdown list),

There will be one more pre-release version that addresses the following problems: - Android app may hang when streamed video size is not supported by the device - Fixed cursor problem in lock/login screens - Another fix for Android 15

There are some known problems like entering picture-in-picture mode after pressing "recent apps" button. But only on some of devices. Some work ok. Going to picture-in-picture using the "home" button should always work.

And udpdated pre-release APK is available: https://downloads.mirillis.com/files/beta/remotly-release-v27_1.41-12Sep2025_01-01.apk If improves cursor scaling and fixes problems with Android 15

We have prepared a new pre-release version of Remotly client for Android: https://downloads.mirillis.com/files/beta/remotly-release-v27_1.41-12Sep2025_01-01.apk It should fix the "gigantic" cursor problem. It also fixes problems on Android 15 devices.

We will buy and test PIA in our labs. I will let you know if we replicate this.

You can always try another vendor (best to check a trial version if it works ok).

1060 with 4GB VRAM is a good machine, for sure supporting hardware mouse cursor overlay. Even very old computers do support this. But maybe there is something special with this computer.

You shoud never see the remote cursor in desktop mode. It is only shown in game mode. Local cursor is better as it introduces a "lag free" feeling for normal desktop activities (not gaming). There are situations when the cursor is included in the streamed video in desktop mode: 1. Host pc...

Mouse cursor is scaled along with the video. We will try to detach it from scaling.