We are running an application on a Microsoft Windows Server via RDP, the clients are running Android with thhe latest Devolutions Android App.
Currently when the client mobile phone looses WIFI connection, we get a screen saying it can not connect to the server any more. The only option is an OK button.
When you click this button you get back into the main menu where you can hit the play button and you will get re-connected to the RDP session (in case the WIFI became available in the meantime)
My question is: is there a possibility to configure the app, so it would reconnect to the RDP server as soon as the WIFI connection gets re-established? We could not find anything in the documentation and were not able to find a correct setting in the app.
We are only running this one application via RDP on this mobile phone, so it would be awesome if the user would have to initialize the first connection through a startscreen widget and after that not being bothered any more with the RDP client and connection issues.
Any help appreciated!
Hello,
Thank you for reporting this issue. Could you confirm whether notifications are enabled for RDM? Enabling notifications allows the foreground service to run, which helps maintain the connection while the app is in the background.
Also, is the “Automatically reconnect sessions” option enabled? You can find this setting under: Application menu > Settings > Sessions > More.
Regarding the home screen widget, it is supported; however, there is currently an issue that causes it to work only when the application is completely closed. We already have a ticket open to address this. In the meantime, if you’d like to use the widget to launch an RDP session from your home screen, you can do the following:
Best Regards,
Frederick Simard
Hello Frederick,
thanks for your reply.
Regrading your questions:
"Enable Notifications": this has always been enabled in the past, we have received notifications.
"Automatically reconnect sessions": was enabled as well
The home screen widget works as you explained: only if the software has been closed completely. This is fone for us so far.
Now for our main concern, the reconnect of the session:
We found that it works ~70% of the time that your software managed to re-connect (after WIFI connection is re-eastablised by Android)
In other cases there has been really strange behaviour: when we touched the screen, then it seemed that old / previously displayed UI screenshots randomly appeared on the screen.
We were able to fix this by disabling "Experience -> Persistent Bitmap Caching" (and then actually disabled everything else in that menu, except for 'Data compression', 'Reconnect' and 'Detect network automatically')
This made the whole thing work (at least in my imagination) a bit better, but still not a 100% reliable (reconnect is not always done automatically)
We turned on the debug log, but were not able to find a file or anything else with the logs. (Don't know if they would provide any more detail at all)
How could we get the debug log?
So we are still trying to find the correct or better reliable settings, but hasve not been succesful yet. Happy to receive more ideas
Hello,
Thank you for the additional details.
You can find the logs by tapping Tools > Private Storage Explorer > Logs. Once we receive the logs, we will analyze them and see whether we can find any additional information there.
Also, when the app is unable to reconnect automatically, it would be better to offer a Reconnect or Retry option instead of only showing an OK button. We will create a ticket for that.
Best Regards,
Frederick Simard
Hello,
thanks for taking care of the re-connect option. Any ETA when this will be available?
Currently I don't have access to a device regarding the logs, but as soon as we run into re-connect issues again, I will try to get my hands on them and post here.
Thanks
Hello,
We will start working on it very soon. No ETA has been established yet.
Best Regards,
Frederick Simard