|Left mouse click||Single tap|
|Left mouse double click||Double tap|
|Right mouse click||Touch, hold for at least 1 second without moving, or tap with two fingers. When tapping with two fingers, the click is registered at the location of the last finger touching.|
|Performing a drag operation||Touch, release, touch, drag, release. It is similar to a double click, only on the second click don't release your finger but drag instead and release only then done with dragging. For right button dragging touch with two fingers.|
|Scrolling||Stroke with two fingers in a vertical/horizontal direction.|
|Toggle software keyboard||Press Menu, select Keyboard or single tap with three fingers.|
|Shift, Ctl, Alt, Win , Esc, Ins, Arrow Up/Down/Left/Right, Del, Home, End, PgUp, PgDn, PrtScn, Pause keys, functional keys||Menu > Keyboard. Please note that the keys Shift, Ctl, Alt, Win are "sticky" and will be released after any other key is touched.|
|Edit server parameters||Long press on the server in the list and select Edit.|
|Remove server||Long press on the server in the list and select Remove.|
|Set master password||Press Menu, select Settings, select Master Password. All pre-existing passwords are also encrypted when the master password is set.|
|Use a non-default IP port||Specify server address as [address]:[port number].|
Touch interface can work in two different modes: touchpad mode (default) and touchscreen mode. The mode can be changed in the application settings by editing the Touchpad mode check-box.
This is a default mode and it behaves similar to a touchpad on a laptop computer. It allows precise positioning of a cursor without losing its track. To position a cursor, move it by stroking the touch screen in the desired direction. If the device screen is smaller than the remote desktop, the device screen is behaving like a viewport. The viewport is being moved relatively to the remote desktop screen so that the cursor is staying approximately in the middle area of the device screen until the viewport reaches an edge of the remote desktop, then the cursor is moved relatively to the device screen.
It behaves like a regular touchscreen. The mouse pointer is positioned at the location touched by the user. If the device screen is smaller than the remote desktop, the device screen works like a viewport and can be moved by stroking the touch screen in the desired direction.
The trackball on the device behaves similar to a desktop trackball, it just moves a cursor on a remote desktop. Click on the trackball results in left mouse click.
Keyboard layout setting
Keyboard layout can be changed by editing Keyboard Layout field. It is generally should be selected to match the keyboard layout used on the remote computer. There is a special keyboard layout named Unicode, which can be used with any keyboard layout on the remote computer, because it sends all input as Unicode characters. Unicode input is supported by Windows Remote Desktop servers starting with Windows 2000. The important difference between Unicode layout and the language specific layouts is that the language specific layouts allow sending key combinations which include a character, e.g. Ctrl-C, Ctrl-V. When a language specific keyboard layout is set, all characters which can be typed on a physical keyboard without using Shift and also capital letters are not sent as Unicode characters, but instead are mapped to a key on a keyboard according to the selected keyboard layout and their scan-code is sent.
Windows specific keys
Windows specific keys, not available on the device, are implemented in a soft keyboard, which can be brought up using Menu > Keyboard. Please note that the modifier keys Shift, Ctl, Alt, Win are "sticky", that is touching one of these keys will result in the corresponding key been pressed and staying down on the remote desktop, which is indicated by a green light coming up on the key in the soft keyboard. The subsequent touching of the key will release the corresponding key on the remote desktop. It also will be released when any other non-modifier key is pressed. A key combination can be sent to a remote desktop by touching a modifier key or keys and touching regular key on a device hardware keyboard or soft keyboard.
Srolling can be initiated by stroking two fingers in a vertical or horizontal direction. Vertical scrolling in a remote session is implemented by sending mouse wheel rotation events. Horizontal scrolling is implemented by sending left/right arrow key presses.
The Xtralogic RDP client provides secure storage for server passwords, when master password is set. While the master password is being set, all previously stored passwords, if any, are encrypted. When the master password is set, it can be deleted with an option to delete all existing passwords, or to keep the existing passwords by storing them as clear text (not recommended).
Software keyboard auto-activation
The Xtralogic RDC supports automatic activation of a software keyboard. The software keyboard is activated when user clicks on a text field. This feature requires free Xtralogic RDC Companion application to be installed and running on a remote computer. The software keyboard auto-activation is enabled by default and can be disabled in application settings (Menu > Settings).
Remote Desktop Gateway
The Remote Desktop Gateway or RD Gateway (formerly Terminal Services Gateway or TS gateway) can tunnel Remote Desktop Protocol sessions using an HTTPS channel through a network firewall. It is a configurable feature of Windows Server 2008 (or later). One RD Gateway can be used to allow secure access to multiple Remote Desktop servers. It is usually used on corporate networks and configured by the network administrator. To access a Remote Desktop server behind an RD Gateway, first, save an RD Gateway settings by going to Menu > Manage Gateways. The user name and password are optional, and do not need to be specified if you use the Remote Desktop server credentials to connect to the RD Gateway, which is the usual scenario. Once an RD Gateway settings are saved, it can be selected on the Advanced tab of a Remote Desktop server settings in the Gateway field. Leave the "Use server credentials for gateway" checkbox checked to use the server credentials to connect to the RD Gateway. If the credentials are not saved you will be prompted for them each time you connect.
Sound redirection options can be selected in the Advanced tab of server settings on a server by server basis. Sound quality controls are located in application settings (Menu->Settings) and apply to all servers. When choosing sound quality, keep in mind that higher quality requires more bandwidth. If required bandwidth is not available on wireless network, sound will be played with interruptions. Also, using stereo versus mono sound consumes twice as much of the network bandwidth.
Microphone redirection from the client to a remote computer can be enabled in the Advanced tab of server settings on a server by server basis by editing the Enable microphone redirection mode check-box.
On some Windows 7 editions the audio recording in a remote desktop session is disabled by default and can be enabled only by editing the registry. The HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fDisableAudioCapture registry value(type REG_DWORD) has to be set to 0.
For more information see Microsoft Support article Configure Audio Recording Redirection in Windows 7.
Flash memory card redirection
The flash memory card can be made available as disk in the remote session, that is will be visible for reading and writing in the Windows Explorer running on the remote computer. It is disabled by default and can be enabled in the Advanced tab of server settings on a server by server basis.
Text can be copied/pasted between a phone and a remote session. To copy text from phone to a remote computer, long press on a text field on the phone and
choose Select Text from the menu. Select text in the text field and long press again. Choose Copy in the menu.
Start the Xtralogic RDC and connect to the remote computer. Once the connection is established,
the text in the phone keyboard will be sent to the remote computer's clipboard and available for a paste operation.
To copy text from the remote computer to the phone, in the remote desktop session copy text into the clipboard and close the connection. Start an application on the phone where you need to paste the text, e.g. compose an email. Long press on a text field and choose Paste.
If you purchased the application on the Google Android Market, the application is relying on the Google Android Market License Verification service to make sure it is licensed for use on the device. The licensing status is obtained through the Android Market application and cached for the next 24 hours. There has to be an Internet connection (over WiFi or cellular data network) when the application runs for the first time, so that the licensing status can be initially verified. After the licensing status is initially verified, the application can be used for one week without Internet connection. After one week the Internet connection will be required to verify the licensing status.
Importing server settings
The Xtralogic RDC supports importing server settings from a standard Microsoft Windows .rdp file. To import copy the .rdp file to the SD card and in the app go to Menu > "Import from .rdp".
The app also allows importing multiple server settings at a time from an XML file. To import copy the XML file to the SD card and go to Menu > "Import from XML". The XML file is using attribute names similar to .rdp file keywords, except if a keyword contains spaces, they are replaced with "-". Attribute values are the same as in .rdp file.
In addition to the .rdp file keywords, the XML file may contain attributes specific to Xtralogic RDC:
0 - negotitate, up to SSL with NLA
1 - RDP Security
2 - SSL
|xtr-use-server-creds-for-gateway||bool||1||0 - false
1 - true
Input locale, should match input locale used on the remote server
66561 - Arabic
4105 - Canadian French
69641 - Canadian Multilingual Standard
1029 - Czech
1030 - Danish
1043 - Dutch
1035 - Finish
1036 - French
1031 - German
1037 - Hebrew
1040 - Italian
1041 - Japanese
1042 - Korean
1044 - Norwegian
1046 - Portuguese (Brazilian ABNT)
1049 - Russian
1034 - Spanish
1053 - Swedish
1055 - Turkish Q
2057 - United Kingdom
1033 - US
Switch left and right mouse buttons
0 - false
1 - true
Please note that the server password can't be imported from password parameter in .rdp file because it is stored their in an encrypted form.
Example of an XML file:
<?xml version="1.0" encoding="UTF-8"?> <servers> <server full-address="18.104.22.168" server-port="3389" username="alice" domain="wonderland" desktopwidth="1024" desktopheight="800" session-bpp="24" audiomode="0" connect-to-console="0" compression="1" disable-cursor-setting="0" disable-full-window-drag="0" disable-menu-anims="0" disable-themes="0" disable-wallpaper="0" allow-font-smoothing="0" redirectdrives="1" redirectclipboard="1" alternate-shell="c:\test\a.exe" shell-working-directory="c:\test" gatewayusagemethod="1" gatewayhostname="acme.com" xtr-description="Test server 1" xtr-security-layer="0" xtr-use-server-creds-for-gateway="1" xtr-input-locale="1033" xtr-switch-mouse-buttons="0" xtr-password="Password1" /> </servers>
The easiest way to configure access to a RemoteApp program is to import an .rdp file created by the RemoteApp server administrator for a particular RemoteApp program. See the Importing server settings section on how to import an .rdp file.
The RemoteApp configuration can also be entered manually. On the Advanced tab of server settings, tick off the "Connect to RemoteApp program" checkbox. After that free additional fields will become available. The first one, "RemoteApp program name" is required. In that field, enter the RemoteApp program alias, prefixed by two '|' characters, e.g. if the program alias is calc, enter ||calc. The remote program alias can be found in a RemoteApp program properties in the RemoteApp Manager.
Please note that RD Web Access is not currently supported.
Simple Connect makes it easier to establish a connection when a remote computer is behind some kind of a network address translating (NAT) gateway, such as a home network router or corporate firewall. Without Simple Connect, before such connection can be established, port forwarding needs to be configured on the NAT gateway. This requires some degree of network knowledge or might not even be possible on corporate network. Simple Connect eliminates the need for configuring port forwarding.
Simple Connect relies on Google Talk infrastructure to establish network connections between the Xtralogic RDP client and the remote RDP server. In most cases the connection is established directly between the client and the remote server and the Google Talk infrastructure is used only for the connection negotiation, meaning that the data traffic flows directly without going through the Google Talk servers. In rare cases of complex network configurations the direct connection can't be negotiated and the data traffic is relayed through the Google Talk servers. Please note that the RDP traffic is encrypted using SSL or standard RDP encryption protocol and is not visible to the Google relay server.
In order to make a server available to Simple Connect, the Xtralogic RDC Companion application has to be installed on the server, configured with Google account email address and password, and logged in. The same Google account has to be used in the Simple Connect settings in the Xtralogic RDP client. Any Google account can be used with Simple Connect. A pre-requisite for using Simple Connect is outgoing network connectivity on the TCP port 5222, which can be verified by using a Google Talk client (e.g. Gtalk app) on both client and server. Another pre-requisite is outgoing network connectivity on TCP port 443 (SSL port), which can be verified by connecting to a https://www.google.com URL using a Web browser. Both of this ports are normally allowed even on corporate networks. Since Simple Connect requires the same network connectivity as Google Talk, for more information see Required ports to use Google Talk.
Once the Xtralogic RDC Companion is connected to the Google infrastructure, the corresponding entry will appear in the server list in the Xtralogic RDP client connected with the same Google account. This entry will automatically disappear from the list once the Xtralogic RDC Companion is disconnected on the remote computer, unless it is edited and saved, for example to add RDP login name and password. Once saved, it will remain in the list even if Xtralogic RDC Companion is disconnected on the remote computer.
If 2-step verification is configured for a Google account being used with Simple Connect, an application specific password will need to be generated and used with Simple Connect. This is the same as what would need to be done for a standalone Google Talk client. For more information on signing in using application-specific passwords with 2-step verification see Google support article Signing in using application-specific passwords.
Xtralogic Simple Connect is not affiliated with or endorsed by Google, Inc.