Recent content by hhspiny

a potential bug in 1.34 -- if an unauthorized client is connected and waiting for authorization, no other client can make connection.

It would be even better if a specific device(s) within an account is designated as the authorizing device, and shows a notification. or the authorization function can be centralized on the web portal. i.e. batch authorization for multiple hosts. if you have a group of hosts, and want to add...

I would vote for extending the inbound connection list to allow adding to authorized list. mobile phone works, but you need to be around. what if you need to authorize for someone else, and you don't want to do it right then, but rather to take care of it later, and in batch.

Right now, the authorized device is added only via the dialog box that pops up. this creates two problems 1. the dialog box disappears after a while 2. run in booter mode (i.e. no remotly instance in user account), the dialog box does not pop up at all. Suggestions, list the devices that have...

will test quickhost then once I can download the 1.34 version. maybe that also solves the occasional blank-screen.

Follow-up on remotly_boot.exe. with the 1.34 pre-release, which seems to behave the same as 1.33.1 Note, this is in windows 11 (not VM), installed with admin account, start with windows. but do NOT start remotely client in normal user account (i.e. normal user account still uses the admin...

to allow for controlling android device remotely.

client windows laptop, two finger scrolling on touchpad does not do anything on host. if this is not by design, can you add the function? making scrolling a lot easier.

It only consumes CPU when in remotely session. And killing it breaks the session.

beat the dead horse one last time. using the official 1.33. install w/o GPU-P (hence no crash), then enable GPU-P. remotly_boot.exe still sticks around preventing remotly.exe from starting and it is consuming decent CPU time . if manually kill remotly_boot.exe, remotly.exe start right away...

booter service does not start with GPU-P off (after installing with GPU-P on, but VM crashes, have to turn GPU-P off). once turn GPU-P back on, and boot up the VM, booter service starts. should be something about booter service interacting with GPU-P.

well, not sure if worth troubleshooting more as fresh installation does not have the problem. maybe related to being domain controller. or just unique with the specific VM I have. However, it would nice if you could fix the VM crashing right after installation while GPU-P is enabled. this...

To make sure we don't waste time for one-ff, I did a fresh install. Fresh VM installation of Win Srv 2022 without GPU-P. enable GPU-P and install AMD drive inside VM. reboot, and install remotly (run as admin). after installation, during UI loading, VM crashes. shut-down VM, disable GPU-P...

I am not aware there is difference between administrator and Administrator. aren't windows user name not case sensitive?

this is windows 11 (the hyper-v host)