Trent's community posts

Thanks for the confirmation, Brandon!

Polina, many thanks to you and the devs for taking a look!  Luckily, I only rarely have the need to use the mobile app so little to no inconvenience for me!

I'm happy to install a beta version to test out a fix once the devs think they have it corrected!  Just let me know!

Thanks, Polina!  Let me know if there's any further info you need from my side:

Here are more details on the device:
Android Version: 11
Android security update: September 5, 2020
Google Play system update: September 1, 2020
Baseband version: g7150-00018-200701-B-6643937
Kernel version: 4.14.170-g501c771385ff-ab6716795 #1 Tue Jul 28 22:05:21 UTC 2020
Build number: RP1A.200720.011

As I mentioned, this is a Google Pixel 4a. The phone is less than a month old.  Admittedly, I did not try the RU app prior to allowing the phone to update from Android 10 so I cannot say if it's something specific to the hardware or the Android version.

Happy to perform any experiments that you would like!

I recently updated my Google Pixel 4a to Android 11 and see that the RU Android app now immediately closes upon launch. I tried force stopping, clearing cache, clearing user data and uninstalling/reinstalling.

It shows the logo momentarily and then immediately returns to the home screen.

Just wanted to open the discussion in case you were not aware or if there is something I can try for you!

Bob, be aware that if you are connecting to a host computer that has no physical mouse connected, the mobile apps do not locally render a virtual cursor.  A workaround is to enable "Mouse Keys" on the host computer as described in this post:

https://www.remoteutilities.com/support/forums/messages/forum7/message4490/940-cannot-see-mouse-cursor-on-the-remote-computer#message4490

Hope that helps you!  It did me!

Mark, be aware that if you are connecting to a host computer that has no physical mouse connected, the mobile apps do not locally render a virtual cursor.  A workaround is to enable "Mouse Keys" on the host computer as described in this post:

https://www.remoteutilities.com/support/forums/messages/forum7/message4490/940-cannot-see-mouse-cursor-on-the-remote-computer#message4490

Hope that helps you!  It did me!

Good morning, Polina.  Letting you know I have encountered this error twice more just recently.  I had the opportunity to try your suggestions and wanted to share my results:

The HKEY_CURRENT_USER\Software\Usoris\ folder did not exist in the registry.  I also did a search for "Remote Utilities" in the registry and found limited results that mainly were in things not related to application settings.

The %appdata%\Remote Utilities Agent\ folder did exist and had 2 subfolders.  I deleted the entire Remote Utilities Agent folder.

Still got the same error.

I again tried running the agent "as administrator" after making the suggested deletions, but still got the same error.

Any further suggestions?

Thanks, Polina!  Next time I have the need to login with that customer or if I encounter it again elsewhere I'll try those steps and will report back.  Luckily I've only seen this once so far.

Good morning!  I was just attempting to use the Run Only Agent with a customer and when they downloaded and ran the agent6.10.exe, they received the following message:

Application Error
Exception EOIeException in module rutserv.exe at 00151C47. The parameter is incorrect.

We tried running from different locations, run as administrator, "unblock" the file so it is not flagged as a downloaded file.  All still got the same error.  This is a fairly new Windows 10 Pro install.

Anyone else seen this?

Polina Krasnoborceva wrote:

Didn't see that mentioned in the release notes.

We mentioned it in the second paragraph of the release notes .

Ah!  Right you are.  For some reason I didn't connect that!

Thanks!

Safe to assume that the new "Keyboard" section under the "Remote Screen" section in the connection properties is a replacement to the old "Use Legacy keyboard input model" that used to be in the "Mode" area?

Didn't see that mentioned in the release notes.