Again, on the subject of The Linux Guest System, installed on my Google Pixel C Tablet…
A standard behaviour which Android has, is to serve the request by apps to “Share” documents with other apps, but in a way that non-computing experts may not understand. When the user of an Android app taps on ‘Share’, a list of other apps normally displays, that are registered as being able to open the type of document that’s to be shared. From there, the user can select an app to share it with.
What is usually done behind the scenes is, that the app from which the document is to be shared creates a copy of the document which will be accessible to other apps, and then sends a URI to the app that the document is finally to be shared with. This URI tells the targeted app, which document is to be shared.
In certain cases, these URIs consist of URLs, but in such a way that Android can distinguish between different categories of URLs.
If what is to be shared is a VNC session, again, it’s a URI that specifies the local IP address (127.0.0.1), as well as the port number to connect to.
What I do not know is, when there is only one installed Android app, registered to be able to open a certain category of URI, whether Android nevertheless displays a list of available apps – which in this case would contain only one – so that the user can select the one available app. And this applied to VNC Viewers. What ‘UserLAnd’ was doing, was creating a VNC Session via Linux software, and then allowing a VNC Viewer to connect to that session, but not displaying the fact to me, that it was handing over the Android screen – not the VNC Session – to another app. Two possible things could have been happening:
- UserLAnd may just prefer the VNC Viewer that I had installed. It was the recommended viewer. Or,
- That VNC Viewer could simply be the only Android app I have installed, that can act as a VNC Viewer, for which reason the dialogue would be redundant, from Android, to ask me which VNC Viewer to use.
Either way, the transfer of the tablet’s screen was seamless, and led me directly into the VNC Session – that is, after I had entered my password for doing so.