Terms, Icons and Conventions

GSW ConnectBot – Admin Mode launcher Icon
GSW ConnectBot – Work Mode launcher Icon

Hand Pointer Icon – used when requested to “tap” or select a location on the screen with your finger, stylus, mouse, etc.

Hosts - Host is used when identifying the SSH or Telnet Server to establish a connection

Host Connection and Host Configuration are used interchangeably when referring to the “Configuration that provides GSW ConnectBot with the information to establish a connection to a Host”. Typically used to refer to the list in the Hosts Screen.

Sideloading – Installing an application package in APK format on the Android device.

Vertical Ellipses Icon

Figure 1: Overflow menu

On Window Operation System menu item navigation

Arrows or Pipes will be used

Start->Georgia SoftWorks Licensing and Deployment Server

Start|Georgia SoftWorks Licensing and Deployment Server

Overview

Thank you for purchasing the GSW ConnectBot.

GSW ConnectBot is a simple to use but a commercial grade Secure Shell (SSH) and Telnet client for Android. GSW ConnectBot is a feature rich client that both system administrators and users will appreciate. It is well suited to the demands of industrial environments.

When coupled with the GSW License and Deployment Server (LADS), Licensing is automatic, Zero Touch configuration is available, and you can spend more time working than administering. See page 97.

For the system administrator that has many devices to manage, the GSW ConnectBot comes with GSW LADS that manages licensing, configuration updates, software updates, and deployments. A light weight, easy-to-use tool that is a major time saver for the administrator as well as all the people working the devices.

Next to correct operation and usability, security is paramount. GSW ConnectBot is the most cryptographically secure, commercially supported SSH client for Android available. GSW set out to make sure the default security algorithms are current and considered safe via peer review. No propriety algorithms, no – non-safe algorithms. Don’t be the next headline about a security breach.

Obtaining GSW ConnectBot

GSW ConnectBot can be obtained from the Google Play Store or the Georgia SoftWorks web site. For upgrades you can also obtain from your local GSW LADS (page 97).

Figure 2: Where to obtain GSW ConnectBot

When first obtained and installed the GSW ConnectBot will operate in a fully functional 30-day trial mode.

Quick Start SSH Configuration

For those wanting to get started fast, here is a quick start step guide to get that first connection up.

Figure 3: SSH Quick Start

Note: Telnet is similar, just be sure to change the Protocol in the Host Configuration from SSH to Telnet.

Installation

Installation can be done directly from Google Play Store or by downloading from Georgia SoftWorks website. The figure below is an overview of the steps.

Figure 4: First time installation Android 8+

Figure 5: First time installation Android 7.x and lower

Installation from Google Play

To install from Google Play your device must have internet access.

• On your Android device, open Google Play Store.

• Search for GSW ConnectBot.

• Select GSW ConnectBot (free trial) – Telnet/SSH Client.

• Select Install.

Installation from Download

The GSW ConnectBot is a standard Android Package Kit (APK). Download GSWConnectBot.apk from the GSW website. If your device has a browser and internet access you can download and install on the device. Otherwise use another computer to download the APK and then copy the APK to the device and execute.

Once installed, configure the connections with the features desired. Please keep in mind that device settings may vary between Manufacturers and Android versions. GSW ConnectBot has been tested on multiple devices, and Android versions 4.4.2 through 11.00

Following are instructions on how to install GSW ConnectBot on your device. Installation is a simple process. To summarize:

· Enable Allow Unknown Sources

· Copy APK to Device

· Run APK installation

Example 1. Using a USB Connection

To begin, connect the device to your workstation via a USB cable. The device should appear in the Windows Explorer navigation pane.

Figure 6: Android device listed in Windows Explorer

Enable “Unknown Sources”

Android security requires that “Install Unknown Apps/Allow from this source” be enabled in order to sideload updates or write to local storage from some applications.

Android versions prior to version 8 used a global setting to control sideloading, and must be enabled prior to the installation of the application.

This became a per-application setting for Android versions 8 and higher, and the setting can only be changed after the application has been installed.

Each manufacturer's devices setting location can differ, please see devices manual for further instructions on sideloading. See generalized examples below.

Android Version 8 and higher

Permissions on Android versions 8+ are set on a per-application basis. Regardless of whether you install from the Google Play Store or sideload the APK from www.georgiasoftworks.com, you must enable “Unknown Sources” for the GSW ConnectBot application to be able to sideload GSW ConnectBot updates from GSW LADS, and other instances where GSW ConnectBot needs to write to internal storage of device. Not all manufacturer implementations are the same. Some will offer a popup menu to dynamically set/allow unknown sources, and some will emit a terse error message about the inability to write data. In most cases, this security setting can be found under the target application (GSW ConnectBot) in the “Apps” settings menu.

Example: Generalized example of popups to “allow from this source”.

Figure 7: Unknown Apps popup

Figure 8: App specific Allow from Source Setting

Figure 9: Enable App specific Allow from this source

Generalized terse messages that require enabling from unknown sources.

The example below with GSW ConnectBot shows permission error to write to the device. In the device settings, locate the App Info. Tap on the GSW ConnectBot and navigate to “Allow from this source” as shown in Figure 15.

Figure 10: Terse Alert Message Writing to SDCard

Figure 11: Locate GSW ConnectBot in the app Info. Opens GSW ConnectBot app settings

Figure 12: Tap Advanced

Figure 13: Tap Install unknown apps

Figure 14: Tap Allow from this source

Figure 15: Allow from this source is enabled

Android Versions Prior to 8

On the device, make sure that “Unknown Sources” is turned ON under “Security” menu in “Settings”. This allows applications to be installed from outside the Google Play Store. The name of the “Security” menu may vary from device to device.

Figure 16: Set Unknown Sources

Copy and Install APK to Device - Sideloading

Copy the GSW ConnectBot APK to the device using Windows Explorer, download or by whatever method you choose, preferably to the “Download” folder, as some device File Managers limit access to files at the root of storage. The name of the actual GSW ConnectBot APK is gsw-connectbot.apk or gsw-connectbot-version.apk, where version is the version number of the release.

Next, Tap the GSW ConnectBot APK shown in Figure 17 and the screen in Figure 18 is displayed.

Copy APK to the Device

Installation Screen

Figure 17: APK on device

Figure 18: Install screen

Next, tap the “INSTALL” button as shown below in Figure 18.

Installation continues and completes.

Figure 19: Installation progress bar

Figure 20: Installation complete

Tap “OPEN” to immediately begin configuration of GSW ConnectBot. The App will open into Administrative mode by default, as described in the next section.

Launching GSW ConnectBot

The GSW ConnectBot, built for commercial environments has administrator mode and a user (work) mode. This provides a clean and distinct division of roles where the worker can focus on their activities without concern for the administration details. The Administrative mode is a superset of Work mode, meaning the Administrator can do everything the Worker can do plus more.

Administrative mode includes:

· Licensing

· Creation/Deletion and configuration and use of connections

· Manage Pubkeys

· Background/Foreground color translation

· Locking the Work mode to an application.

The Work mode is used for:

· Launching preconfigured connections

· Updating the software

· Downloading configuration

· Licensing

The Administrator can preconfigure many connections to multiple host computers. Multiple connections can be active simultaneously and the user can easily navigate between connections. The Work mode is a restricted, lockable version for the end users that the administrator controls.

Work mode users can launch preconfigured connections created by the Administrator. This allows workers to use preconfigured connections reducing errors and saving time. Additionally, the Work mode user can be limited to running only GSW ConnectBot, using a process call “App Pinning”, which we will discuss later in this manual (page 89).

Note: When switching between Admin and Work Mode you must force stop the application, then launch the desired mode.

The launcher icon with the gear is the Administrator. The icon without the gear is for Work mode users which is a restricted, lockable version for end users.

GSW ConnectBot – Admin Launcher Icon

Figure 21: Admin and Work Modes

GSW ConnectBot – Work Launcher Icon

Table 1: Admin and Work Launcher Icons

Registration of the GSW ConnectBot License

The GSW ConnectBot will operate in a fully functional trial mode for 30 days. To enable permanent operation, a software license needs to be applied. Registering the software is the process to obtain and apply a valid license for the GSW ConnectBot.

There are two options available to license the GSW ConnectBot

· Fast Registration - Use the Georgia SoftWorks Licensing and Deployment Server (LADS) See page 18

· Manual Registration - Send product identification code to GSW and a serial number is returned and applied. See page 21

Registration - This entails sending a product identification code to GSW and we will return a Serial Number. Apply the serial number and this activates the license for GSW ConnectBot.

Check the License Status

To determine the status of your GSW ConnectBot license, navigate to the GSW ConnectBot Licensing screen.

Tap on the Admin Launcher Icon.

Tap on the overflow menu as shown in Figure 22.

The overflow menu opens. Now tap on Licensing as shown in Figure 23, and the licensing screen opens as shown in Figure 24

Figure 22: Hosts - More Options

Figure 23: Hosts - Licensing

Tap on Check License Info, followed by CONTINUE

Figure 24: Check License Info

Figure 25: Tap Continue to see License Info

The type of license assigned to GSW ConnectBot is dependent on the installation and registration process. The software can have three types of licenses:

· Trial - When installed via the Google Play store or an .apk from the GSW website, a fully functional 30 days trial license is installed. No registration is required.

· Permanent - The manual registration process installs a Permanent license. The permanent license never expires. Note: if the device is destroyed, factory reset, or the application is uninstalled, the license will be lost and a replacement license will need to be requested.

· Temporary - GSW LADS leases licenses to GSW ConnectBot clients. This leased license is termed temporary and will expire at a pre-set time, default of 3 days. GSW ConnectBot will automatically renew the lease and workflow will not be interrupted.

The GSW ConnectBot License information shows the license status, the registration process, the subscription expiration date and other relevant information to the license status.

Expiration date

Trial License: Date that the software will stop operating

Permanent: Not Set; the software will not stop operating

Temporary: The date that GSW LADS will renew the Lease for the license.

Subscription until – The date that the subscription expires. The software will continue to operate with entitled versions. Versions released after the subscription date will not operate unless the subscription is renewed. In addition to access to free version upgrades, premium technical support is also included for the duration of the subscription.

Android_ID – This is an Android Identifier string

GSW CB Version – The GSW ConnectBot Version installed

GSW CB build date – The GSW ConnectBot build date.

Examples of the GSW ConnectBot licensing information are shown on the following pages.

If the software is operating using the Trial license the status will be similar as shown in Figure 26.

Trial Version

Trial Version Expired – No License

Figure 26: Free Trial License Found

Figure 27: Trial License Expired

Expired Trial or Expired subscription license status is show in Figure 27 and Figure 28.

Subscription Expired – New software version not allowed with expired subscription

Figure 28: Subscription Expired

When a permanent license is applied using a Manual registration, it will be displayed similar as shown in Figure 29

If the software was licensed via GSW LADS (License and Deployment Server) the License information will look as described in Figure 30.

Permanent License – Manual Registration

Temporary License – GSW LADS Registration

Figure 29: Permanent License - Manual Registration

The date that the subscription expires is shown as well.

Figure 30: Temporary License Applied

Free version updates and support are available through the “Subscription Until” date.

Registration by GSW Licensing and Deployment Server (LADS)

If you have the Georgia SoftWorks Licensing and Deployment Server (LADS) installed, obtaining a license for GSW ConnectBot is a breeze.

See your system administrator to determine if GSW LADS is installed or use the GSW ConnectBot Locate GSW LADS “button” to try and locate a GSW LADS.

To lease a license, GSW ConnectBot locates the GSW LADS and requests a license.

Navigate to the Georgia SoftWorks Licensing screen. Select “Use Georgia SoftWorks License Server” radio button and TAP “Continue” as shown in

Figure 31.

The screen in Figure 32 is opened.

Figure 31: Register Using GSW LADS

Figure 32: Automatically Locate GSW LADS

1. If the Host is not already populated then you must Locate GSW LADS. If it is populated then you can skip this step.

TAP “LOCATE GSW LADS” as shown in Figure 32 to locate the GSW License and Deployment Server. Notice that the Host does not need to be manually filled in unless GSW LADS cannot be located. Also, the default port 12574 should not be changed without a good reason.

When located, the screen is updated. The Host address of the GSW LADS server as shown in Figure 33. Note: Your host IP address will be different than the one displayed in the example.

2. TAP “GET LICENSE” as show in Figure 34

Figure 33: GSW LADS Server is Located

Figure 34: Get License for GSW LADS

If a license is available for distribution, GSW ConnectBot will be licensed. This is confirmed by GSW LADS that the product license has been retrieved. TAP “Continue” to finish licensing.

Figure 35: Product License retrieved from GSW LADS

Return License to License and Deployment Server (LADS)

If a device is being de-commissioned; return the license to GSW LADS so the license can be reused with another device. Navigate to Georgia SoftWorks Licensing and Deployment Server as described starting in

Figure 31.

Locate GSW LADS as shown in Figure 32 and Figure 33

TAP “Return License” (Figure 36)button to unregister the device and return the license to the pool to be distributed again.

Figure 36: Return GSW ConnectBot License from device

Figure 37: Notification that the License was successfully released.

Your license has been returned to GSW LADS. Please note that at this point GSW ConnectBot will no longer operate on this device.

Note 1: Only licenses obtained from GSW LADS may be returned to GSW LADS.

Note 2: Licenses are not portable between GSW LADS instances.

Manual Registration

In brief, the Manual registration entails creating a Product ID, sending it to GSW. GSW will use the Product Id to generate a device specific Serial number and send it to you. The Serial Number is used to apply a permanent license.

When GSW ConnectBot (version 2.8.010 and higher) generates the Product Id, it saves it in a file named “request.c2g”[1] and places it at the {root}/Android/data/com.gsw.connectbot/files.

Note: if using GSW ConnectBot version 2.7.067 or lower, the “request.c2g” file will store at the root of main storage.

That file is sent to GSW to generate and GSW sends a file back with the name “request.g2c”[2] that contains the serial number.

Step by step instructions follow.

Navigate to the Licensing screen to Manually register the software. This is described as shown in the “check the license status” on page 13.

Tap on Serial Number radio button as show in Figure 38, then tap on continue.

Permanent License – Manual Registration

Figure 38: Permanent License – Serial Number

Figure 39: Permanent License - Continue

The screen to create the Product ID is opened as show in Figure 40.

Example: Create Product ID

Step 1. Tap “CREATE PRODUCT ID” to generate a product id as shown Figure 40. A popup indicating that the creation of the product id was successful as shown

Create Product ID

Figure 40: Create Product ID

Figure 41: Allow access if needed

Figure 42: Close Dialog

The Product ID is displayed as shown in Figure 43. Additionally, a file “request.c2g” is created and placed in {root}/Android/data/com.gsw.connectbot/files when using GSW ConnectBot versions 2.8.010 and higher as shown in Figure 44.

Create Product ID
Figure 43: Product ID created	Figure 44: request.c2g placed in root/android/data/com.gsw.connectbot/files
Figure 45: Request .c2g placed in root - v2.7.067 and lower

Step 2. Copy the file “request.c2g” to a location either on the device or another computer where you can send it to GSW.

Step 3. Go to the GSW Support Page (preferred and fastest method) to initiate a registration ticket and attach the “request.c2g” file. You may need to move the file from the root of main storage to another folder (Download) to be able to copy it via USB or another method to make it available for sending to GSW.

A few alternate methods exist to send the Product ID to GSW to the 3 steps above.

· Alternatively email the file to registration@georgiasoftworks.com

· Copy and paste the Product ID from the Serial Number screen and send it to GSW as in Step 3 above. To copy the Product ID – Press and hold your finger on the Product ID, a Copy/Paste dialog will appear. Tap “Copy” to send the product ID to the Android clipboard, and paste it to a location where you can send it to GSW via the GSW Support Page or email as described above

Georgia SoftWorks will take the Product ID and generate a serial number that is device specific and send it back to you via the GSW Registration ticket system. Simply apply the Serial Number to activate the permanent license.

Apply Serial Number

GSW will return a “serial.g2c” file that contains the Serial Number to activate the permanent license.

Step 1: Copy this file to a folder on your device as shown using the Android file manager in Figure 46.

Figure 46: Copy serial.g2c to main storage root

Figure 47: Apply Serial Number from file

Step 2: Apply Serial Number from File

Navigate to Manual Serial Number screen (as shown in Figure 38 and Figure 39) and TAP on APPLY SERIAL NUMBER FROM FILE as shown in Figure 47.

The GSW ConnectBot file manager opens that allows you to navigate the folder locations on the device.

Go to the location you placed the serial.g2c file in step 1.

TAP on the file serial.g2c.

The screen that the Serial Number was successfully set is displayed as shown in Figure 49.

Figure 48: Locate the serial.g2c file

Figure 49: Serial Number Applied Successfully

Figure 50: All Done, Tap Continue

You license is now permanent. TAP Continue to launch the GSW ConnectBot.

Note: As an alternative to selecting a serial.g2c file, you can paste the Serial Number in the field “Paste serial number here” as shown in Figure 51. Once you paste it then Tap APPLY as shown in Figure 52

Figure 51: Paste Serial Number

Figure 52: Tap APPLY after pasting serial number

The serial number is applied and the license is permanent. Tap CONTINUE.

Update the GSW ConnectBot software

An important benefit of a GSW ConnectBot subscription is that it allows access to version upgrades at no cost. This is important to easily obtain new features that are introduced and problem resolutions that are rolled out.

Similar to licensing, updates can be obtained and installed either using the License and Deployment Server (LADS) or manually. GSW LADS make checking for updates and installation a breeze.

Administrator Mode or Work Mode can both perform software updates. Often it is easier for the user in Work mode perform the update rather than the system administration touching all the devices.

Figure 53: Admin Mode - Update software

Figure 54: Work Mode - Update Software

Updating Software by Licensing and Deployment Server (LADS)

Managing the GSW ConnectBot version can also be done from the server.

The administrator can place specific files on GSW LADS that allow GSW ConnectBot to get software updates (see page 109).

Note: Android 11 implemented new security changes that require modification of the GSW ConnectBot update procedure in certain situations. On Android 11, if upgrading GSW ConnectBot version 2.7.067 or earlier, the .apk file must be manually placed on the Android device (not in the GSW LADS folder).

GSW ConnectBot 2.8.010 and later is updated using the normal process.

When the GSW ConnectBot client checks for an update, if a newer version has been placed in that location, it will confirm that an update is available and ask if you wish to perform the update.

Tap on the Admin or Work Launcher Icon (below is in Admin mode).

1. Tap on the “over flow” menu in the upper right-hand corner of the client.

2. Select “Update” from the menu.

3. Tap “Use Georgia SoftWorks Licensing and Deployment Server”

4. Tap “CONTINUE”

5. Tap “CHECK FOR UPDATES”

Figure 55: Hosts - More Options - Update

Figure 56: Tap Update

Figure 57: Update TAP GSW LADS

Figure 58: TAP Continue

Figure 59: Check for Update

If the Host field (Figure 60) is not already populated then you must Locate the GSW LADS. If it is populated then you can skip this step.

Tap “LOCATE GSW LADS” as shown in Figure 61 to locate the GSW License and Deployment Server. Notice that the Host does not need to be manually filled in unless the GSW LADS cannot be located. Also, the default port 12574 should not be changed without a good reason.

Figure 60: Use GSW LADS Update Screen

Figure 61: Locate GSW LADS

6. If a different version of the GSW ConnectBot client is available the “Update Found!” message will be displayed as in Figure 62. (Go to step 8)

7. If no update is available, you will receive a message that “You are running the latest available version:” as shown in Figure 63. No need to go further (swipe right/or back button to go to host screen)

Figure 62: GSW LADS - Update Found

Figure 63: GSW LADS - running latest version

8. Click “OK”.

9. Click “Install Update”

10. A progress bar will be displayed to provide the status of the download.

11. Once the download is complete, Android Security will ask for permission tap “Allow”

Figure 64: Install Update

Figure 65: May be prompted to allow access to photos

Figure 66: Update is downloading

12. A confirmation message will pop up asking if you wish to install the update.

13. Click “INSTALL” to proceed with the update.

14. When the download is complete, tap open to relaunch ConnectBot and connect to a session.

Figure 67: Install Update

Figure 68: Tap Open to launch

Updating Software by manually obtaining gsw-connectbot.apk

Note: Sideloading example on page 10

Copy the new version GSW ConnectBot APK to the device using Windows Explorer, download or by whatever method you choose, preferably to the “Download” folder, as some device File Managers limit access to files at the root of storage. The name of the actual GSW ConnectBot APK is gsw-connectbot.apk or gsw-connectbot-version.apk, where version is the version number of the release.

Figure 69: Select version to install

Figure 70: Tap install

The hosts configuration and licensing are not affected when the updated version of GSW ConnectBot has finished.

Updating Software by URL

URL Update allows you to update GSW ConnectBot directly from a web location. By default, the URL points to the GSW website[3]. You may also download the .apk and .json file and place them on your own intranet website for download.

Select “Update” from the overflow menu.

Figure 71: Tap the overflow menu

Figure 72: Tap Update

Figure 73: Select Use URL

Select “Use URL” then select “Continue”. The URL default is updating from the GSW Website. If using a website, type the URL in “URL:” field. Tap “Check for Updates” button (Figure 75).

Figure 74: Tap Continue

Figure 75: Tap Check For Updates

Figure 76: Update Found - Tap OK

Above images show tapping the “Check For Update” button. You will then see a message stating you are running the latest available version or “Update Found!” as shown in Figure 76. If update is found tap OK and you will then see the “Install Update” button highlighted (Figure 77).

Figure 77: Install Update button highlighted

Figure 78: You may a security prompt - tap Allow

Figure 79: Tap Install

Figure 80: Installed

Once the “Install Update” button has been tapped, you may or may not[4] receive an Android pop up asking for access to photos and media on device (Figure 78). If you do, select “Allow”. Then you will have the option to finish installation just follow prompts. After the update has been installed you can launch the GSW ConnectBot app and all host configurations remain the same.

GSW ConnectBot Host Configuration and Connections

The “Hosts List” screen displays all the configured connections and the connection status of each one. When using the System Admin icon , you can add, delete, and modify configurations as well as initiate connections. Unless noted otherwise, configuration description is by the System Administrator.

Multiple connections can be defined, each with a nickname and color-coded text for easy identification.

Additionally, you can have multiple connections running simultaneously and navigate back and forth between them by horizontal swiping and by the selection of tabs.

Open GSW ConnectBot App on your Android device.

Figure 81: Creating a Host

Create new Host Connection Configuration

Tap the plus sign button in the lower right corner to start a new host configuration.

The following screen is displayed (Figure 82):

Figure 82: Configuring a Host connection

Configuration Parameter and defaults are emboldened.

SAVE – Tap the plus sign to save the configuration

Protocol: Options are ssh, telnet and local. Local gives access to the local Android shell.

Username@hostname.port:

This is the username and hostname/IP address of the ssh host.

Entered in the format <username>@<hostname>

Automatic Logon: Click the check box to access Username and Password fields for Automatic Logon

Nickname: Nickname: Easy name to associate with the username/hostname on the ssh host configuration. This is displayed on the Hosts screen (Figure 83)

Color category: Color category: This is the color for the text displayed in the Hosts screen.

Font size (pt.): Font size does not need to be set unless the columns and rows of the Window size are set to zero

Window size: Adjust window size to match your server’s settings.

Default 80 Cols 25 Rows.

Allow scrollbars: Options: enabled / disabled. Enables scrolling when the Window size exceeds the display size. When enabled, Optional “Show Scroller Control” is displayed. It provides a widget that can be used to scroll vertical and horizontal.

Touch as mouse: Options: enabled / disabled. Enables touch as mouse events, if supported by hardware. Translates Touch events to Mouse Events for server.

Use pubkey authentication:

Options are: “Use any unlocked key”, “Do not use keys” and select one of the available public keys. Ignore this if using telnet as the protocol.

DEL Key: Options: Delete or Backspace

Encoding: Options: UTF8 / multiple options available.

Use SSH auth agent: Options: enabled / disabled. Handles subsequent SSH Auth.

Compression: Options: enabled / disabled. May help with slower networks.

Start Shell Session: Options: enabled / disabled. Disable to only use port forwards.

Stay connected: Options: enabled / disabled.

Try to reconnect to the host if disconnected.

Close on disconnect: Options: enabled / disabled.

Close immediately after a remote disconnect without prompting.

Post-login automation: Commands to run on remote server once authenticated.

AnswerBack: Enter an Answerback if needed by your application (see 53 for additional information when using GSW UTS).

Host Connection Operations

Configured Host Connections are displayed on the Hosts List screen.

Each connection has a status Icon, the Nickname and connection duration. By default, host connections are sorted alphanumerically.

Please notice the icons, the color of the text for each host connection and the nicknames. Each connection is customizable so that you can quickly recognize the connection by the nickname, the text color and the status.

Figure 83: Host Connection Screen Display

Icon	Status Description
	Connected
	Non-Connected
	Abnormal Disconnect

The time the connection has been in that status is displayed under the nickname.

From this screen, you can perform a variety of operations on the connections.

Initiate Connection

Tap a Host Configuration to initiate the connection

With an active connection, the overflow menus have the following options for the session.

Session Menu

When connected, the overflow menu provides the operations as shown in Figure 84 and described below.

Figure 84: Session overflow menu

· Disconnect - Closes the connection

· Port Forward - GSW ConnectBot provides basic port forward capability. This menu allows the configuration of port forwards.

· Screen Shot - Takes a screen shot of the activity on the device. Only 2-Taps. See Below.

· Show Keyboard - If the keyboard is hidden, it unhides or shows the keyboard.

· URL Scan - Scans host session screen for URLs. Any found are placed in a clickable list.

Users can tap on the list to request the operating system to open selected URL on the device.

· Force Size - NA, Do not use.

2-Tap Screenshot

The GSW ConnectBot allows for screenshots to be quickly captured as needed. The need for screenshots has been around for years. If an anomaly or application error occurs the worker may need help with a screen, but not at that instant.

Other offer screenshots, but there is a difference. Often complicated navigation is required to get to the screenshot command. GSW ConnectBot purposely designed screen shots to be quick and easy as to minimize work interruption. This allows the worker to grab the screen shot and continue working.

Figure 85: Tap 1 - Tap overflow menu

Figure 86: Tap 2 - Tap Screenshot

Figure 87: Success. This prompt can be disabled in the Global Settings.

Additionally, GSW ConnectBot can be configured to either store the images on the device or automatically send to GSW LADS where they can be viewed by the administrator at their convenience.

Administrators have easy access and are able to provide immediate support for devices in production from the comfort of their desk.

The worker simply taps the overflow menu and then taps “Screenshot” and boom - done! The image

is uploaded to LADS see 112.

Host Connection Menu

Figure 88: Host List - Long Press Menu

To access to the Host Connection menu, use a “Long Press” (Touch and Hold) on the specific Host connection. The result of the Long Press is a menu is displayed with the following options.

· Disconnect

· Edit Host

· Edit port forward,

· Edit auto response fields

· Delete host

· Security Info (only displays when connected to host).

Disconnect

Tap to Disconnect from the host

Edit Host

Tap to modify the Host Connection settings. You save the changes by Tapping Save Host, in the upper right hand of the screen.

Edit Port Forward

This allows editing of the Host Connection Port Forward settings.

Edit auto response fields

This allows editing of the auto responses fields. The administrator can preconfigure responses that GSW ConnectBot will insert when defined fields are recognized. For example, if the application prompts for the “Department Code”, the administration can preconfigure the “Department Code” so the user does not have to remember and enter the correct department code. The administrator defines the field to scan for, as well as the response when detected.

As many “Auto Response” fields can be configured as needed.

When Edit Auto Response Field is selected, a screen is displayed that shows all the auto responses configured (Figure 90). Tap plus to create the auto response field (Figure 90).

Nickname: This is an easy to remember nickname for this Auto Response.

Prompt: This is the text to scan for from the application.

Response: This is how you want the GSW ConnectBot to reply to the Prompt.

Use once checkbox: This determines if you only want the GSW ConnectBot to perform the auto response one time or if it should respond every time the Prompt appears.

Macros are a tremendous tool when coupled with Auto Response Fields. Please see page 95

Macros can be used to provide unique device information such as android id, mac address etc. Example: Auto Response

In the example below, each time a device is connected to the server, the application prompts for the assigned Device Identifier. Instead of the user having to remember the identifier for different devices, and entering it, the administrator can create an auto response and preconfigure each device with its identifier.

The nick name is DeviceID. The prompt from the application is ID. The response for this device is rcving-tm-fl-4

Figure 89: Create Auto-Response field

Figure 90: Edit Auto Response Field

Figure 91: Auto Response Field completed

This saves the User time, reduces errors in entry providing an easier user experience and more productive work shift. Then tap on Create Auto Response Field.

As shown in Figure 92, you will see the auto response with the Nick Name, Prompt and Response. You can add as many auto response fields as needed.

Figure 92: Auto Response created.

A long press on the Auto Response definition will allow you to edit or delete it.

If multiple prompts are required such as User Name/Password, you can use Escape sequences where appropriate in the response to move from field to field, etc.

Escape Sequence	Description
\a	Form feed
\b	Backslash
\e	ESC
\n	Newline
\r	Carriage return
\t	tab
\v	Vertical tab

Table 2: Escape sequences for Auto Response

Delete Host Connection

Tap to delete the Host Connection.

Security Information

This displays the current status of the SSH Security Algorithms in use. This will let you know the security level of the negotiated algorithms between GSW ConnectBot and the SSH Server.

Figure 93: Secure Algorithms

Graphical user interface, application

Description automatically generated

Figure 94: Un-Secure Algorithms

If you do not have a Strong Security grade, you will want to look at any of the main security algorithms that does not have the Green Lock icon to determine what needs to be done (contact GSW Support).

Global Settings

The “Hosts List” Overflow menu (3 vertical dots) allow access to the GLOBAL GSW Connect Bot configuration settings.

Figure 95: Menu to access Global configuration

Figure 96: Accessing Settings

Additional settings are accessed by tapping the three vertical dots in the upper right-hand corner of the app and selecting “Settings”.

Figure 97: Select Settings

Additional settings are accessed by tapping the overflow menu (three vertical dots) in the upper right-hand corner of the app and selecting “Settings”.

The available settings are shown in the screen shots in Figure 98. The settings include:

· Remember keys in memory

· Persist connections

· Keep Wi-Fi active

· Backup pubkeys

· Emulation mode

· Scrollback size

· Rotation mode

· Auto hide title bar

· Full screen

· Page up/down gesture

· Volume keys change font size

· Keep screen awake

· Fast updates

· Collect Business Intelligence data

· Use GSW keyboards

· Use GSW keyboard skins

· Special keys always visible

· Shift+num are F-keys

· Hide soft keyboard

· Ctrl+num are F-keys

· Sticky modifiers

· Directory shortcuts

· Camera shortcut

· Bumpy arrows

· Audible bell

· Bell volume

· Vibrate on bell

· Background notifications

· Upload screenshots to GSW LADS

· Show screenshot message

In the list below the default value for setting is “Bolded”

Remember keys in memory

Keep unlocked keys in memory until backend service is terminated (enabled/disabled)

Persist connections

Force connections to stay connected while in background (enabled/disabled)

Keep Wi-Fi active

Prevent Wi-Fi from turning off while a session is still active (enabled/disabled)

Backup pubkeys

Keep back-ups of the private keys using Android’s backup mechanism(enabled/disabled)

Emulation mode

Terminal emulation mode to use for PTY connections (xterm-color, xterm-256color, xterm, vt100, ansi, screen)

Scrollback size

The number of lines indicating the size of the scrollback buffer to keep in memory for each console.

Rotation mode

Controls display in Portrait or Landscape based on device orientation. (Default[5], Force landscape, Force portrait, Automatic).

Auto hide title bar

Tap console to show the title bar and access menu (enabled/disabled) The entire session display is the console unless Mouse to Touch is enabled.

Full screen

Hide status bar while in console (enabled/disabled)

Page up/down gesture

Swipe the left third of the screen to send page up/down to the terminal (enabled/disabled)

Volume keys change font size

Font sizes can also be changed in per-host settings (enabled/disabled)

Keep Screen awake

Prevent the screen from turning off when working in a console (enabled/disabled)

Fast updates

Faster display, but some characters may not line up vertically (enabled/disabled)

Collect Business Intelligence data

Send Business Intelligence data to GSW LADS for storage and analysis (enabled/disabled)

Use GSW keyboards

Use Georgia Softworks keyboards instead of the default system keyboard in telnet/ssh sessions (enabled/disabled)

Use GSW keyboard skins

Use Georgia Softworks keyboard skins to modify the look of keyboards displayed in telnet/ssh sessions (enabled/disabled)

Special keys always visible

Special keys always visible (enabled/disabled)

Shift+num are F-keys

On hardware with keyboards, simultaneous press of [Shift & number] keys send F1-F10 (enabled/disabled)

Hide Soft Keyboard

Hide soft keyboard when host session starts (enabled/disabled)

Ctrl+num are F-Keys

On hardware with keyboards, simultaneous press of [Ctrl & number] keys send F1-F10 (enabled/disabled)

Sticky modifiers

Modifier keys remain enabled until another key is pressed (No, Only alt, Yes)

Directory shortcuts

Select how to use Alt for ‘/’ and Shift for Tab (Use right-side keys, Use left-side keys, Disable)

Camera shortcut

Select which shortcut to trigger when the camera button is pressed (Ctrl+A then Space, Ctrl+A, Esc, Esc+A, None)

Bumpy arrows

Vibrate when sending arrow keys. Useful for laggy connections. (enabled/disabled)

Audible Bell

Bell is audible (enabled/disabled)

Bell Volume

Set bell volume (A slider to set the bell volume)

Vibrate on bell

Vibrate on bell (enabled/disabled)

Background notification

Send a notification when a terminal running in the background sounds a bell (enabled/disabled)

Upload screenshots to GWS LADS

Upload screenshots to Georgia Softworks Licensing and Deployment Server, if available (enabled/disabled)

Show screenshot message

Show message when screenshot processing is completed (enabled/disabled)

Figure 98: Global Settings menu

Using Answerback with the GSW SSH/Telnet Server

Answerback allows the mobile client to pass a text string (up to 20 characters) to the SSH/Telnet server when requested.

The Answerback string is set in the GSW ConnectBot Host connection configuration.

This is the only configuration required on the client for answerback.

Figure 99: Answerback Settings

An enhanced method of obtaining the Answerback is available when using the GSW SSH/Telnet Server (UTS). The application running on the GSW UTS accesses the answerback value using the server-side environment variable gwtn_answerback.

This does not use any screen locations and the display is not impacted as with many Answerback solutions. An environment variable is much easier to read than a screen location.

Following is an example of how to configure the GSW UTS to obtain the Answerback from the GSW ConnectBot.

The Server-side configuration consists of a lightweight utility (answerback utility) and logon scripting (example below). When the GSW ConnectBot connects to the UTS, the logon script is executed and the answerback utility obtains the Answerback string from the GSW ConnectBot. It then inserts it in the environment variable gwtn_answerback for the application to access.

From the GSW UTS SSH/Telnet Server. –

1. Download and copy the gs_enq.exe, gs_enq64.exe files to a folder that the logon scripts can access. To download these utilities Click Here.

2. Set the user’s home directory to point to a folder where they can write a temporary file.

3. Edit the users Logon Script (c_start.bat or k_start.bat) and add the lines to retrieve the Answerback.

Modify the Logon script of the User to the following, making sure to change any environmental variables to match the User connection being queried. In this example, we are querying for the Answerback of RFUser.

Answerback Example Configuration

::========== Start of Logon Script=========

@echo off

set gwtn_color=1

set gwtn_graphics=1

set gwtn_term=1

set gwtn_home_dir=C:\GS_UTS\scripts\LocalUsers\RFuser

@if %gwtn_gsclnt%==1 goto :GSW

@set GWTN_ANSWERBACK=%GWTN_CLIENT_IP%

@c:\gs_uts\gs_enq.exe

@if errorlevel 1 goto :NOANSWERBACK

@set /P GWTN_ANSWERBACK=<ab%gwtn_agntpid%.txt

@del ab%gwtn_agntpid%.txt

@:NOANSWERBACK

@:GSW
<Launch your Application here, using GWTN_ANSWERBACK as a variable>

Example:
C:\hjs\adv\bin\telterm.exe 10.200.150.8 4700 %gwtn_answerback%

:: ============ Answerback stored in GWTN_ANSWERBACK.=========

Connect the user to the server using GSW ConnectBot. The Answerback in the GSW ConnectBot configuration should be returned within the connection shell.

Note:
On x64 systems gs_enq64.exe must be used instead of gs_enq.exe. After this block is executed the variable GWTN_ANSWERBACK is going to be set. Of course, c:\GS_UTS\ must be substituted with your own path.

SSH Configuration

GSW ConnectBot is the most secure commercially available SSH Client for Android.

The GSW ConnectBot is using the current SSH algorithms recognized as secure to ensure you have the best protection available. Algorithms that are not deemed safe are not used.

Configure a Host Connection Example 1

SSH with Password Authentication

Below we are going to show you how to configure the GSW ConnectBot client to make SSH connections using Password Authentication.

Open GSW ConnectBot App on your Android device.

Tap the blue plus sign button in the lower right corner to start a new host configuration.

Figure 100: Creating a Host

Configure these options to get a working connection:

1. Enter <user>@<IP address> and

2. Check “Automatic Logon

3. Enter your Username and Password (Host and Port Autofill).

4. Choose a nickname (not required).

5. Tap “Use pubkey authentication”. Select “Do not use keys”.

· You may also want to modify other items if necessary

· Select the Color of the text used on this Host Connection when displayed on the Hosts screen.

· The Font size does not need to be set unless the column and rows of the Window Size are set to zero.

· Adjust Window size to match your server’s settings.

· Confirm:

o “Start shell session” is on.

o “Stay connected” is on, to keep trying to reconnect if disconnected.

o Choose whether to close the session on disconnect.

Figure 101: Enter Host Information

Save host connection configuration

Tap the plus sign “+” in the upper right to save the connection.

Connect to the new configured connection

Tap on the connection to connect to your Georgia Softworks Universal Terminal Server.

Configure a Host Connection Example 2

SSH with Public/Private Key Authentication

Public/Private keys are an extremely secure and convenient method of logging on to the host. The following are instructions on setting up an SSH key pair for GSW ConnectBot

This example is the same as Example 1, with some configurations difference.

Here are the modified items for the SSH Public/Private Key Authentication.

You can configure these options to get a working connection.

1. Enter <user>@<IP address> and

2. Enter the nickname SAP Server as shown below.

3. Tap “Use pubkey authentication”. Select “Use any unlocked keys”.

4. Enable Use SSH auth agent

In this case, leave “Use pubkey authentication” set to the default which is “Use pubkey authentication”.

Tap the “plus sign” in the upper right corner to save the configuration for the host connection.

Figure 102: Saving the Connection

Using a Public/Private key pair

Configuring a public/private key pair consist of the following steps.

· Enter the configurable parameters for the Public/Private Keys

· Generate (using randomness)

· Unlock the Key

· Transfer the public key to the SSH server

· Install the public key on the SSH Server

Enter public/private key parameters

To enter the public key parameters, navigate to Manage Public Keys screen.

To navigate to the Manage Public Keys screen, tap on the three vertical dots in the upper right-hand corner and the Hosts Menu appears.

Figure 103: Host Screen for Key Generation

Figure 104: Manage Pubkeys menu item

The first time a key is added, the Generate screen opens. If you already have key(s) on the device then the Pubkeys screen will open with a list of available keys. If keys are present, tap on the “+” plus sign to add a new key.

The Generate screen allows you to enter the key parameters such key type, number of bits, etc.

· Enter a nickname for the key pair.

· Select the type of key you would like to generate. RSA is the default.

· Select the encryption strength. Anything less than 2048 is not recommended.

· Enter a password for your key pair [optional, but recommended].

· Check Load key on start.

Figure 105: Create SSH Key Pair

Generate the Key with Randomness

Tap “Generate”

Generate randomness by moving your finger around the field, the percentage will increase as shown in Figure 107

Figure 106: Generate Randomness for Keys

Figure 107: Generate Randomness until 100%

Once randomness reaches 100%, the key pair is created

The Pubkeys screen is opened as shown below:

Unlock Key

Tap the key to unlock it. This makes it available for connections to use. If you set a password, you will be asked to enter it to unlock.

Figure 108: Unlocking a Key Pair

Transfer the key to the SSH Server

Transferring the Key to the SSH server is easy using common techniques.

On the Pubkeys screen:

1. Press and hold the key to access the options menu.

2. Select “Load key on start” (if it is not checked)

3. Tap “Copy public key”. This will copy the public key to your device’s clipboard.

4. Paste the contents of the public key into a text file.

5. Use whatever method you wish to copy the file created to the Georgia SoftWorks Universal Terminal Server.

6. When utilizing GSW LADS to manage the Host Configurations (113), the public key(s) is/are exported as part of the uploaded configuration. C:\Program Files (x86)\Georgia SoftWorks\Georgia SoftWorks Licensing and Deployment Server\files\configs\upload\<your config tag>\pubkeys

Now, configure the Host (public) key on the GSW server.

Figure 109: Copy Public Key

Configuring the Host (Public) key on a GSW UTS SSH Server

On the Georgia Softworks UTS server, go to Start > All Programs > Georgia Softworks UTS > Certificate Mapping Tool for GSW SSH Shield.

1. Copy the public key from the text file that you created in the previous step.

2. Expand Public Key Mapping, and select 1-to-1. Next click Add.

3. Click Enable this mapping and paste the clip board data into the Public key area. Fill out the rest of the fields below.

Figure 110: Certificate Mapping Tool

4. Click “Enable this mapping” and paste the public key you created using GSW ConnectBot into the Public key area. Fill out the rest of the fields.

Figure 111: Installing Public Key

5. Click OK, and click Apply. You should now see the mapping you created.

Figure 112: Key Installed

6. The changes will not take effect until the Georgia SoftWorks SSH
Shield service is restarted. Click YES to restart SSH (all current connections will be dropped) or NO if you intend to restart later.

Figure 113: Restart SSH Service

Once the UTS server has restarted, you may test the GSW ConnectBot SSH connection.

Creating a Public Private Key Pair for Distribution to Multiple Clients

Generate a Key Pair using PuTTY

1. Download PuTTY Terminal Emulator Package HERE.

2. Open PuTTYgen (included as part of the PuTTY terminal emulator package).

Figure 114: Open PuTTYgen

3. Click the “Generate” button and move mouse over the blank area to generate randomness.

Figure 115: Generate Randomness

4. Key is created.

Figure 116: Enter Passphrase

5. From the top menu bar, select “Conversions” then “Export OpenSSH Key”.

6. Name and save the key.

7. Click “Save Public Key” name and save on server.

8. Using direct USB connection or USB flash drive, copy the OpenSSH key to the Android device in the “Downloads” folder.

a. If using a USB flash drive, connect, go to “Settings”, “Storage and USB”.

b. Select Flash Drive.

c. Select file – Long press.

d. Tap three dots menu.

e. Select “copy To”.

f. Copy to “Downloads”.

g. Go back to “Storage and USB”

h. Eject flash drive.

Installing Private Key to GSW ConnectBot Android Client

9. Launch GSW ConnectBot – Admin Mode (Icon with gear).

Figure 117: GSW ConnectBot Admin Icon

10. Tap overflow menu in the upper right.

Figure 118: Tap "overflow menu"

11. Select “Manage Pubkeys”.

Figure 119: Manage Pubkeys

12. Tap folder icon in the upper right.

Figure 120: Select Folder Icon

13. Navigate to “Downloads”.

Figure 121: Navigate to Downloads

14. Select key, this will import key into GSW ConnectBot.

Figure 122: Select Key

15. Tap the key and enter passphrase, set in PuTTYgen (step 4), to unlock it.

Figure 123: Tap Key and Enter Passphrase

16. Press and hold the key to access the options menu.

17. Select “Load key on start” (if it is not checked).

Figure 124: Access the Options Menu

Adding the Public Key to the GSW UTS Server using the GSW SSH Shield Certificate Mapping Tool

18. On the Georgia Softworks UTS server, go to Start > All Programs > Georgia Softworks UTS > Certificate Mapping Tool for GSW SSH Shield.

Figure 125: GSW Certificate Mapping Tool

19. Locate the Public Key from step 6, open with text editor and copy contents from below the “Comment” line and above the “END” line.

20. Expand Public Key Mapping, and select 1-to-1. Next click Add.

21. Click Enable this mapping, copy and paste the Public Key data into the Public key area. Fill out the rest of the fields below.

Figure 126: Enable Mapping

22. Click OK, and click Apply. Created mapping will now be displayed.

Figure 127: Created Mappings

23. The changes will not take effect until the Georgia SoftWorks SSH
Shield service is restarted. Click YES to restart SSH (all current connections will be dropped) or NO if you intend to restart later.

Figure 128: Restart the SSH Shield

Once the SSH Shield service has restarted, you may test the GSW ConnectBot SSH connection.

24. Save host connection configuraiton

Tap the plus sign “+” in the upper right to save the connection.

25. Connect to the new configured connection

Tap on the connection to connect to your Georgia Softworks Universal Terminal Server.

Telnet Configuration

The following guide will show how to configure the GSW ConnectBot client to make Telnet connections using Password Authentication.

Open the GSW ConnectBot App on the Android device.

Configure a Telnet Host Connection

Tap the blue plus sign button in the lower right corner to start a new host configuration.

Figure 129: Creating a Host

A new Host Connection Configuration screen is displayed as shown in Figure 130.

SSH is the default protocol, Tap protocol and select Telnet.

Figure 130: Defining a Telnet Host

Configure these options to get a working connection.

1. Tap the down arrow next to the “hostname:port” field Enter <IP address>

If an alternate port is used for Telnet, specify it here (ex: <IP address>:567)

Otherwise leave it as the default Telnet port, 23.

2. Choose a nickname: Shipping Dock.

Other options may be modified if necessary.

Select the Color of the text used on this Host Connection when displayed on the Hosts screen.

The Font size does not need to be set unless the column and rows of the Window Size are set to zero.

Adjust Window size to match the server’s settings.

Telnet will not use public/private keys. The “Use pubkey authentication” field may be ignored.

Tap the DEL Key to specify the key use to send a “delete” message. Choices are “Delete” and “Backspace”.

Figure 131: Enter Configuration Information

Choose the encoding, UTF-8 is the default.

Ignore “Use SSH auth agent”, as this is a Telnet connection.

Compression not used with Telnet.

Make sure “Start shell session” is on.

Make sure “Stay connected” is on, to keep trying to reconnect, if disconnected.

Choose whether to close the session on disconnect.

Enter any Post-login commands as required, commands in user’s logon script is a better option.

Figure 132: Connection Settings

Figure 133: Saving the Connection

Enter an Answerback if required by th application.

As discussed in the “Host Connection Menu” section, additional settings (under “Additional Settings”) can be found by tapping the three vertical dots in the upper right-hand corner of the app and selecting “Settings”.

Managing Host Configuration with the GSW LADS

Once the host(s) have been configured on the Android device, the configuration may be uploaded to the GSW LADS. This will allow other devices to download a duplicate configuration.

For example, if there are three different types of devices or work areas (truck mount, shipping, etc.), and various quantities of each. Configure each host and upload the configurations to the GSW LADS. The next time a similar unit is needed, simply connect that device to the GSW LADS and download the saved configuration. This is a huge time saver.

Uploading an Existing Configuration

Once one instance of a device has been configured, simply “clone” the configuration to other devices, by doing the following.

1. Click on the “three dot” menu in the upper right-hand corner of the client.

2. Select “Upload configuration” from the menu.

3. Tap “LOCATE GSW LADS”

4. Name the Tag, for example: Truck Mount, Shipping, etc.

5. Tap “UPLOAD CONFIGURATION”. A folder will be created in the “Upload” folder with the name used when naming the Tag, in this case “Truck Mount”.

Figure 134: Tap Upload configuration from the overflow menu

Figure 135: Locate GSW LADS

6. Progress bar will appear

7. GSW LADS will confirm successful upload of configuration.

Figure 136: Upload Configuration

Figure 137: Upload Complete

8. On the server, navigate to C:\Program Files (x86)\Georgia SoftWorks\Georgia SoftWorks Licensing and Development Server\files\configs\upload

9. Copy your uploaded configuration[6] to C:\Program Files (x86)\Georgia SoftWorks\ Georgia SoftWorks\Georgia SoftWorks Licensing and Development Server\files\configs\download

Figure 138: Copy upload configuration to download folder

Hint: Access the “Config Files” location using shortcut from the Windows Start Menu[7]

Figure 139: GSW LADS Config File shortcut

10. Now the uploaded configuration is accessible and can be downloaded to another device.

Downloading an existing configuration

1. Click on the “overflow menu” in the upper right-hand corner of the client.

2. Tap “Download configuration” from the menu.

3. Tap “LOCATE GSW LADS”.

4. Select the uploaded configuration to install on the current device from the tag list.

5. Tap “DOWNLOAD CONFIGURATION”.

Figure 140: Tap Download Configuration

Figure 141: Select Configuration

6. Progress bar will appear.

7. GSW LADS will confirm successful download of configuration.

Figure 142: Tap download configuration

Figure 143: Configuration download in progress

Figure 144: Configuration download successful

Client Lockdown

Client Lockdown limits a user to the specific application. This prevents the Worker from modifying the connection or accessing other applications.

Installation of GSW ConnectBot results in creation of two user icons. There is an Administrator launcher and a Work launcher.

The Icon without the gear is for companies using the client in restricted production and or screen lockout mode.

Using the icon with the gear enters administrative mode. The intent is that the administrator will preconfigure hosts, public/private key etc.

The administrator will then open the Work mode icon and pin the app.

Figure 145: Two Modes of Connection

Lockdown (Pinning the app) on Android 7.0+

An administrator can limit a worker to the GSW ConnectBot by using Android screen pinning. The process varies slightly with different versions and devices.

To Pin (lockdown) GSW ConnectBot app, perform the following steps configuration:

Performed by administrator

· Create Hosts

· Enable “Pin Window”

· Enable “Ask for Pin before Unpinning”

· Pin the App

Create one or more hosts.

This is described in the section Create new Host Connection Configuration

Figure 146: Create Host(s)

Enable Pin Window.

Enable Pin Window allows the application to be “pinned” such that that it is the only application available to the Worker.

To enable Pin Window, navigate to Settings->Lock screen and security->other security settings.

From the Android home screen, tap “Settings”. On the example device, the home screen and settings look as shown in Figure 147.

The settings screen opens as shown on the right in Figure 148.

Figure 147: Settings Icon

Figure 148: Tap Security Setting

Tap on the “Security” setting. The name of this setting may vary between Android devices.

The Other Security Settings screen contains the “Pin Windows” configuration item.

In “Pin Windows” field, tap the switch icon to turn this feature on.

Figure 149: Pin Windows Option

The Pin windows option is now enabled.

Enable “Ask for Pin before Unpinning”

Enabling “Asking for the Pin” requires the PIN for the device be entered to exit the application. If you don’t enable “Ask for Pin before unpinning”, the worker can exit the application simply by pressing common key sequences.

Tap on the Pin windows field to display the “Ask for Pin before unpinning” option.

Figure 150: Ask for PIN before unpinning

Now Exit Settings.

The last step is to Pin the Window.

Pin the Window

With GSW ConnectBot, Android Work App open, press the “Recent” button on the home screen.

Tap the “Pin” Icon in the bottom right corner of the GSW ConnectBot App Card.

Note: If the pin icon in the bottom right corner is not visible, move the window up to display the pin icon.

Figure 151: Pinning the Window

Unpin the Window

To Unpin an App, press both the “Back” and “Recent” buttons simultaneously.

Enter PIN to complete unpinning.

To maintain security of the device, only the Administrator should have the PIN, otherwise the end user would have full access to the device and file system.

Admin mode vs Work mode

Figure 152 shows the GSW ConnectBot screen in Administrator Mode.

Notice the full menu options available.

Figure 152: GSW ConnectBot - Admin Mode

Figure 153: GSW ConnectBot Work Mode

Figure 153 shows the GSW ConnectBot screen in Work mode.

Notice the menu is restricted to “Sort by color”, “Update” and “Download configuration”.

No administrative functions are enabled in Work Mode.

NOTE: GSW ConnectBot must be Forced Closed to switch between Admin and Work modes.

Device Telemetry Data Variables

When using the GSW ConnectBot with GSW UTS, useful device information is available for applications to provide a better experience for users.

These provide “smarter” applications the capability to make changes based on the device that they are connected. This includes knowing the display size, the IP Address of the device and much more.

The data is available on the device as Macros and on the UTS as environment variables.

Macros

This data is available to use in the Host Connection configuration in items such as AutoResponse Fields (see page 45) and Answerback (see page 53).

Macro Syntax: ${macroname}

Data Name Macro Syntax Evaluates to: (in our example)

build_device ${build_device} river

build_display ${build_display} PPOS29.114-134-10

build_hardware ${build_hardware} qcom

build_host ${build_host} ilclbld158

build_id ${build_id} PPOS29.114-134-10

build_manufacturer ${build_manufacturer} Motorola

build_model ${build_model} moto g(7)

build_product ${build_product} river

build_serial ${build_serial} UNKNOWN

display_density ${display_density} xxhdpi

display_dimensions ${display_dimensions} 2016x1080

gswcb_build_type ${gswcb_build_type} release

gswcb_version ${gswcb_version} 2.7.016

network_clnt_side_ip ${network_clnt_side_ip} 192.168.1.157

network_mac ${network_mac} 24-46-C8-0C-E8-61

status_code ${status_code} 0

version_codename ${version_codename} REL

version _release ${version_release} 9

version_sdk ${version_sdk} 28

version_security_patch ${version_security_patch} 2020-02-01

Environment Variables

These variables are passed to the server so the application or the logon script running on the server can take advantage of this information.

For example: The application running on the server can look at the size of the screen and, based on the screen size, may launch a different application profile which was built for that particular screen size. For example, the application screen size might be 16x20 or 16x50. The application, invoked by the logon script, will be able to make an intelligent determination of the size of screen from environment variables and send the appropriate screen size to the device. The goal is to match the resolution. Avoid sending a very detailed screen when a particular android device has very limited resolution.

Example of Environment Variable[8]

gwtncl_build_device=river

gwtncl_build_display=PPOS29.114-134-10

gwtncl_build_hardware=qcom

gwtncl_build_host=ilclbld158

gwtncl_build_id=PPOS29.114-134-10

gwtncl_build_manufacturer=Motorola

gwtncl_build_model=moto g(7)

gwtncl_build_product=river

gwtncl_build_Serial=UNKNOWN

gwtncl_ display_density=xxhdpi

gwtncl_ display_dimensions=2016x1080

gwtncl_gswcb_build_type=release

gwtncl_gswcb_version=2.7.016

gwtncl_network_clnt_side_ip=192.168.1.157

gwtncl_network_mac=24-46-C8-0C-E8-61

gwtncl_status_code=0

gwtncl_version_codename=REL

gwtncl_version_release=9

gwtncl_version_sdk=28

gwtncl_version_security_patch=2020-02-01

GSW Licensing and Deployment Server (GSW LADS) for Windows

GSW LADS is a lightweight intuitive mobile device management system that takes care of most mobile device administrative needs without the expense or complexity and large footprint so common with many mobile device management systems.

Figure 154: LADS components

GSW LADS provides several capabilities for GSW ConnectBot

· Status and Management tools

· GSW LADS is the central repository for all of the GSW ConnectBot configurations, licensing data, software upgrades, Public/Private keys, custom keyboards, Business Intelligence, saved screen shots and more.

GSW LADS features are listed below.

· Manage Licensing

· Zero-Touch Configuration to Multiple Devices

· Upload/Download Device Configurations

· Manage Updates to Client Software

· Public/Private Key Import/Export

· Business Intelligence

· Custom Keyboards

· Rapid 2-Tap Screen Shot/Automatic Upload to GSW LADS

Installing the Georgia SoftWorks Licensing and Deployment Server

GSW LADS is installed on a Windows Operating System computer that the devices running GSW ConnectBot are able to access. Installation is simple and described below.

1. Download the Georgia SoftWorks LADS setup program here. GSW LADS can be installed on any modern Windows OS and must reside on the same LAN as the GSW ConnectBot devices that are being licensed. Once licensed, the device is portable to other networks.

Figure 155: GSW LADS setup program

2. User Account Control Dialog.

Often you will get a UAC prompt. Select Yes

Figure 156: User Account Control Dialog

3. Double click the executable. You will see the initial setup dialog. Let it run until finished.

Figure 157: Setup progress bar

4. Select “Next” on the following dialog, to move to location dialog.

Figure 158: Welcome

5. Select “Next” on the following dialog, to move to folder dialog

Figure 159: Installation Location

6. Select “Next” on the following dialogs to move to Setup Complete Dialog.

Figure 160: Install folder

7. Select Finish to complete GSW LADS installation.

Figure 161: Setup Complete

Setup is now complete. Please license GSW LADS with Georgia SoftWorks, using the registration process to activate the software.

Registering the Georgia SoftWorks Licensing and Deployment Server

Overview:

To run the GSW Licensing and Deployment Server, you must first register the software. This entails just a few steps that involve obtaining the Product ID and other registration information and providing this information to Georgia SoftWorks so a Serial Number can be generated. The Serial Number is sent back to you and when applied it activates the GSW LADS software.

These are the steps to register and activate the GSW LADS.

1. From the Start Menu, select

Georgia SoftWorks Licensing and Deployment Server -> Registration.

You may get a UAC prompt. Select Yes.

Figure 162: LADS Registration UAC dialog

2. The registration tool dialog for GSW LADS appears.

The registration software automatically fills in the Product Information fields as shown below.

Figure 163: GSW LADS registration tool opens

Please complete the “Customer Information”, the “Purchased From”, “Application software” in the form as shown. Also enter the number of GSW ConnectBot licenses requested as shown in Figure 164.

Figure 164: Registration Tool with completed information

Save the file using the “Save to file…” button.

You may close the Registration program at this time.

The registration information must be provided to Georgia SoftWorks to obtain the Serial Number. Several methods are available for your convenience.

Please use option “a” if possible.

a. Go to https://www.georgiasoftworks.net/support_gsw/open.php to submit a support ticket for Registration. Complete necessary fields and attach the file you saved in the previous step.

This is the preferred method – Fastest Response time.

b. Email the file to registration@georgiasoftworks.com. A support ticket will be opened and you will receive instructions how to proceed with the registration.

c. Print the information and Fax it to Georgia SoftWorks – 706.265.1020

3. Once Georgia SoftWorks receives the information, a Serial Number will be generated and sent back to you.

Open the registration program again.

Please copy the Serial Number and paste it into the Registration information field in the Registration tool.

The easiest method to copy the serial number is to highlight the returned Serial number and

copy (ctrl-c) it. Then position the mouse in the Serial Number Field in the Registration Information box and paste (ctrl-v).

Figure 165: Registration Tool - Serial Number Entered

Click Register.

Figure 166: Registration Successful

After a successful GSW LADS registration, restart the Georgia SoftWorks gswlads service in Microsoft Services. GSW LADS will now distribute licenses for GSW ConnectBot software, up to the number of purchased activations.

GSW LADS Operation

After installation, GSW LADS will run as a Microsoft Windows Service.

GSW ConnectBot will automatically discover LADS on the network. Two other options are available for specifying the IP address of GSW LADS:

1. Enter the IP address of the GSW LADS server on the device. (See page 18)

2. Modify and transfer the xml configuration file to the device running GSW ConnectBot.

At times the system administrator may want to define configuration information for the device to ensure specific parameters are used by GSW ConnectBot. This is accomplished using the config.xml file. See below.

GSW ConnectBot LADS XML Configuration File

The GSW LADS XML configuration file (name: config.xml). A template of the xml file is located in LADS directory default path:

C:\Program Files (x86)\Georgia SoftWorks\Georgia SoftWorks Licensing and Deployment Server\files\com.gsw.connectbot\files\config.xml

This xml file allows specification of information that GSW ConnectBot will use instead of discovery or requiring manual entry at the device.

· IP Address of the GSW LADS server

· Port number on the GSW LADS server

· Name of specific configuration file to use

· Auto Erase

The format of the XML files is as follows and should be placed on the device in the following location:

{root[9]}/Android/data/com.gsw.connectbot/files

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">

<!--

This file should be placed in /{root}/Android/data/com.gsw.connectbot/files

-->

<entry key="lads_ip">lads_ip_address</entry>

<entry key="lads_config">Name of configuration to download</entry>

<entry key="auto_erase">false</entry>

</properties>

LADS IP ADDRESS: <entry key="lads_ip">lads_ip_address</entry>

Example: <entry key="lads_ip">192.168.77.1</entry>

LADS PORT: <entry key="lads_port">lads_port_number</entry>

Example: <entry key="lads_port">12574</entry>

LADS Config file: <entry key="lads_config">Name of configuration to download</entry>

Example: <entry key="lads_config">trunkmount-charlie</entry>

LADS IP ADDRESS: <entry key="auto_erase">[true|false]</entry>

Example: <entry key="auto_erase">true</entry>

This is provided for completeness. You may want to return to discovery of LADS instead of using the config.xml file. You set this to “true” if you want the config.xml file automatically be deleted after being used.

Manage Licensing

GSW LADS makes the licensing of GSW ConnectBot on devices automatic and virtually effortless. Instead of having to manually license each individual GSW ConnectBot, the launch of each instance of GSW ConnectBot will automatically request a license from GSW LADS. If a license is available, it is provided to GSW ConnectBot. If a license is not available the user is alerted to this condition and should contact the system administrator.

The GSW License Manager displays the total number of GSW ConnectBot licenses registered as well as the number that have not been assigned.

Navigate to the GSW LADS License Manager

Start | GSW License and Deployment Server | License Manager

Below is the GSW License Manager dialog.

Figure 167: GSW License Manager tool

The GSW License manager provides a quick method for the administrator to:

· View how many GSW ConnectBot licenses are registered with GSW LADS - Total licenses

· View how many GSW ConnectBot licenses are available for assignment – Available licenses

· Manually release a GSW ConnectBot license from GSW LADS

If a device is being retired or replaced, the best practice is to return the license from GSW ConnectBot ( as described on page 20). The released license will be available to assign to a new device.

GSW LADS manages a GSW ConnectBot License Lease for each GSW ConnectBot assigned a license. Since the License has a timeframe lease it is designated as a “Temporary” license. When the GSW ConnectBot License Lease expires, a new lease is acquired. This automatically recovers the licenses from inactive devices, making them available to be assigned to GSW ConnectBots in use.

If a device is lost, or destroyed and the GSW ConnectBot license has not been released, GSW LADS will make the license available to other devices after the license lease expires. The default is 3 days.

The value can be changed if needed for your particular environment.

The registry contains the License Lease value which is the number of days for the License Lease.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Georgia SoftWorks\gswlads\Parameters\dwLicenseLeaseDuration

Default: 3 days

If you do not want to have Leased Licensing then set the value to 0.

If the license is needed before that time, the administrator can use the GSW LADS License Manager utility to release the license so it can be assigned to other devices. To open the GSW LADS License Manager:

Start Button|Georgia SoftWorks Licensing and Deployment Server|License Manager

Figure 168: Release License - Notice Available License Count

Figure 169: Enter Android ID, Click Release License

Figure 170: License Released Confirmation

Figure 171: Release License - Notice Available License Count Incremented

Enter the Android ID of the GSW ConnectBot to release from the missing or destroyed device.

Click “Release License”. The available license count is incremented to reflect the license returned as shown in Figure 171.

LADS Table Utility

To use the Release License feature of the License Manager, the Android ID must be known. Often system administrators have the devices inventoried, so the Android ID may already be known. If not, then GSW LADS utility LADSTbl.exe can help the system administrator identify the Android ID of the GSW ConnectBot on the missing/destroyed etc. device.

The tool is located in the GSW LADS installation folder.

Figure 172: LADSTble.exe folder

Open a command shell (as Administrator), navigate to the folder above and type:

LADSTbl.exe

A table will be created that shows the Android ID, the IP address and the last times GSW LADS recognized the GSW ConnectBot as active. An example is shown in Figure 173.

Figure 173: Output of LADSTbl.exe utility

Usually, that will be enough information to identify the Android ID of the GSW ConnectBot to release.
Manage Software Updates to GSW ConnectBot

GSW ConnectBot may be updated from GSW LADS on your intranet by placing the updated software in a specific GSW LADS folder and then follow the standard updating instructions (page 30).

Figure 174: GSW LADS - Software Updates

Copy the GSW ConnectBot installation files to the folder %gsw_lads_root%\files.

Specifically, the following files:

· output.json

· gsw-connectbot-z.zz.zzz.apk (where the “z’s” refer to the version number)

Example: gsw-connectbot-2.8.010.apk

You can obtain the files from the Georgia SoftWorks ConnectBot webpage by downloading the GSW ConnectBot Software .zip file and place both the .apk and .json file with corresponding versions into the GSW LADS “files” folder as shown in Figure 175.

Then on the GSW ConnectBot client follow instructions on Updating Software by Licensing and Deployment Server (LADS) on page 30.

Figure 175: Apk and .json located in the GSW LADS files folder

Upload / Download GSW ConnectBot Configuration

This is a very important feature, as it saves time and reduces errors by allowing configuration and testing of a single device before deployment to all devices.

GSW LADS allows for upload and download of host configurations once host(s) has/have been configured and tested on the GSW ConnectBot. Typically, the administrator will create host(s) on one device and upload to the GSW LADS. Once uploaded the configuration is moved from the “Upload” to the “Download” folder[10]. Next, simply download the configuration to other GSW ConnectBot devices.

Figure 176: GSW LADS Config Upload/Download folders

Figure 177: Easy access to the Config Files via Windows Start Menu

Zero Touch Configuration

Zero touch means the administrator does not have to touch any of the multitude of devices to deploy configurations. Only a single device has to be configured and saved to GSW LADS. On all the other devices, when GSW ConnectBot is launched for the first time, they will automatically obtain the configuration from GSW LADS. This immensely simplifies configuration and deployment.

Zero Touch configuration allows automatic deployment of a designated default GSW ConnectBot configuration. A GSW ConnectBot can be configured and tested fully on a single device. Once the device has been successfully tested, the configuration can be uploaded and mass deployed to any number of GSW ConnectBots, as soon as the application is launched on a device.

Once configuration and testing are completed

1. In the Hosts List overflow menu select “Upload Configuration”

2. Change Tag: to “Default”

3. Tap “Upload Configuration, Upload in Progress will show on screen

4. Then a message will appear once upload is successful, Tap OK

Figure 178: Hosts List - Select Upload Configuration

Figure 179: Set Tag field to "Default"

Figure 180: Tap Upload Configuration

Figure 181: Upload Progress bar

Figure 182: Uploaded Successfully

5. Move the uploaded “Default” Folder to the “Download” folder as described in Upload / Download GSW ConnectBot Configuration on page 110

6. Now launch GSW ConnectBot on other devices, if on the same network it will automatically find GSW LADS, retrieve available license, and “Default” configuration will be downloaded

7. Start using GSW ConnectBot!

Rapid 2-Tap Screen Shot Upload to GSW LADS

The 2-Tap screen shot as described on the Host Connection Operation section on page 43, can automatically send the screen shot to GSW LADS so they can easily be reviewed later[11]. Images are time stamped and associated with the device that took the screen shots.

A folder will be created and labeled as the devices MAC Address, and each screenshot is date/time stamped making it extremely easy for administrator to identify.

Figure 183: GSW LADS Screen Shot storage location

Figure 184: Examples of stored Screen shots

Public/Private Key Import/Export

From GSW ConnectBot you can import and export Public SSH keys, for Server configuration, and Private SSH keys, for many-to-one client configuration.

From the “Hosts” screen, select the “overflow” menu and tap “Manage Pubkeys”

Figure 185: Public/Private Hosts screen

Figure 186: Public/Private Key - Manage Pubkeys

From the “Pubkeys” screen, long press on the key you wish to import / export. Select “Copy public key” or Copy private key from the menu displayed. This will place the contents of the Public or Private key on the clipboard of the Android device. Then, paste the contents to a text document or e-mail, for installation on a client or server.

Figure 187: Pubkeys - Right Click on Key

To import the client key to a device, paste the client key into a text file and copy to the Android device. Use the “folder” icon on the “Pubkeys “screen to navigate to the location of the file and click to install.

To use the public key, copy the contents of the public key file created into the GSW UTS Certificate Mapping Tool.

When configuration is uploaded to GSW LADS, the Public and Private SSH keys are included. When a configuration is downloaded to another device, the private key will be installed. The Public key can be located in the GSW LADS file structure at:

C:\Program Files (x86)\Georgia SoftWorks\Georgia SoftWorks Licensing and Deployment Server\files\configs

The file is named pubkeys.xml

The contents of this file can be installed on the GSW SSH Server using the Certificate Mapping Tool.

Custom Keyboards

Custom keyboards can be designed with specific keys, rows, sizes , skins etc. All aspects of the keyboard can match the requirements of your environment. Custom keyboards are highly desirable to reduce input error and increase overall efficiency of the input process. From hacker’s keyboards to keyboards specific to the manufacturing floor’s application, custom keyboards make input easier and increase accuracy.

Standard GSW Keyboards

Standard custom keyboards are applied to all screens displayed. If there are multiple keyboards, swipe between them, or use the navigation arrows to switch between the keyboards, as shown below.

Graphical user interface, text, application

Description automatically generated

Figure 188: Swipe - Qwerty Customer Keyboard

A screenshot of a computer

Description automatically generated with medium confidence

Figure 189: Swipe - Special Characters Customer Keyboard

Keyboards are a part of the configuration that GSW ConnectBot downloads from GSW LADS. In %gsw_lads_root%\files\configs\download , there is a keyboards directory in each of the configurations. By default, the keyboards directory contains GSW keyboards (*.xml files) in both portrait and landscape for qwerty, special keys and symbols. Each time GSW ConnectBot downloads a configuration from GSW LADS, keyboard xml files are transferred between GSW ConnectBot and GSW LADS.

The keyboards directory can also contain custom keyboards. Custom keyboards must follow the GSW Keyboard XML Properties specification, which closely follows the Android keyboard specification. Examples are the included default keyboards. Note: Do not modify the default keyboards! Make a copy of the existing keyboards, rename and edit. A custom keyboard should have both _portrait and _landscape versions. The file naming convention is: [description]_[landscape|portrait].xml . Example: qwerty_landscape.xml and qwerty_portrait.xml .

The layout of the Custom Keyboards can be specified two ways:

1. Modify the keyboard definition file as per specification. Contact GSW Support.

2. Call GSW to contact one of our keyboard specialists.

Business Intelligence (BI)

GSW LADS can collect information (Android IP, MAC Address, other…) that is sent from GSW ConnectBot clients and produced by GSW LADS. The collected information can be gathered, processed and used to guide management on the use and overall operational efficiency.

Below you will see examples of how Business Intelligence can be used when collected. BI Data is continuously output to a text file (csv format) or fed to a PowerShell script if provided, and can be used to visually show live data.

There is a clear separation of the data collection and the presentation, which provide the user with ability to use the data in any way needed. This is in contrast to fixed/canned reports available to customers using other vendors’ products. As an example, with the use of PowerShell scripts, the BI data can be easily fed to websites and databases.

· Watch live picks happen, keep track of battery life of devices

· License usage, Items Picked

· Productivity of workers, etc.

Figure 190: BI example charts

Figure 191: More BI example charts

Screen Recognition / Custom Keyboard association

GSW ConnectBot has the capability to recognize screens based on their unique screen content. This provides data that can be used for associating custom keyboards, optimized for particular screens, as well as gathering information used in our Business Intelligence (BI) feature (see page 117).

GSW ConnectBot uses an SQLite database that can be used to switch to a custom keyboard when a pattern of characters on the screen is recognized. Custom keyboards can present a specific keyboard that addresses the inputs of each individual screen.

The ability to present only the options that the user needs in a more user-friendly format increases usability and reduces input errors.

For example, if an application screen only presents 5 options, a custom keyboard consisting of 5 enlarged special keys can be invoked for this particular screen.

Figure 192: Screen Recognition/Custom Keyboards

Many ERP applications (warehouse, logistics, manufacturing, etc.), consist of a set of screens with strictly defined input of just a few options. GSW Screen Recognition has the ability to identify these screens. Custom Keyboards as well as Business Intelligence build on this capability.

A lightweight version of screen recognition is text recognition, which is used in GSW ConnectBot Auto Response fields as well. See page 48.

Custom GSW Keyboards

An incredible way to reduce errors and increase productivity is to have custom keyboards for the most common tasks.

For example, if you often need just the number 0-9 Cancel and OK buttons, you can have a custom keyboard built with just those keys. The keys can be larger than normal accommodating large hands in difficult environments (like freezers) and making it quicker to find the number you are looking for.

For example, in the display below a numeric passcode is needed.

Figure 193: Numeric Only Keys - Customer Keyboard

Numeric Data entry is needed.

Larger than normal Numeric keys and ONLY the keys needed. 0-9, Cancel and OK.

This is another example where there are five choices in an option group selection.

Figure 194: Five Key Only - Custom Keyboard

The option from the option group to the left can be selected much quicker by having only the keys necessary.

Only 5 keys are needed to accommodate the option group above.

If you are motivated regarding making your operations as efficient as possible, GSW can help you create Keyboards that are optimized for the screen and automatically associate it with the screen when displayed.

Please contact GSW about creating custom keyboards for your environment. GSW and some advanced resellers can create custom keyboards at an affordable fee basis, that will allow your team to be more productive and make less errors.

GSW Standard Keyboards

Georgia SoftWorks includes GSW Standard Keyboards that are preferred by many due to:

· Ease of viewing

· Handle to move keyboard

· Ability to anchor keyboard

· On/Off indicators

· Quick swapping keyboards and skins

· User controlled keyboard transparency

Below is some of the legend of special keys on the GSW Keyboards.

Figure 195: GSW Keyboard Special Key Definition

1. Keyboard handle. Press handle and move keyboard to desired location.

2. These are on/off indicators for sticky keys.

3. Hides the keyboard. To Show, go to Host Screen top 3-dot (overflow) menu as show in Figure 196 and select Show Keyboard as shown in Figure 197.

Figure 196: 3 dot, overflow menu for show keyboard

Figure 197: Select Show Keyboard

4. a. Go left in the circular buffer of currently available keyboards.

b. Go right in the circular buffer of currently available keyboards

Can also swipe on the keyboard.

5. You can control the opacity/transparency of the keyboard. Often is it useful to be able to see the background of the screen through the keyboard.

a. Keyboard opacity – up (can also swipe up)

b. Keyboard opacity – down (can also swipe down)

6. Shows the keyboards name

7. Change the keyboards skin to the next one in the circular buffer of available skins

8. Reset the keyboards position to the default position

GSW ConnectBot comes with three default portrait keyboards and three landscape keyboards.

· QWERTY

· SPECIAL KEYS

· SYMBOLS / NUMERIC

They are shown below – first in portrait mode and following in landscape.

Portrait Keyboard Images	Keyboard	Skin
Figure 198: Qwerty keyboard – Black-Green skin	Qwerty keyboard	Black Green Skin
Figure 199: Special Keys keyboard – Stone Skin	Special Keys keyboard	Stone Skin
Figure 200: Numeric keyboard - Stone skin	Symbols/Numeric keyboard	Stone Skin

The GSW ConnectBot Landscape Keyboards are placed to the right edge of the screen making it easier to see the rest of the screen.

Figure 201: Landscape Symbols/Numeric Keyboard Anchored to Right Edge

Landscape Keyboard Images

Keyboard

Skin

Figure 202: Landscape – Alpha Numeric keyboard – Yellow – Black skin

Alpha Numeric keyboard.

Note: Name says Qwerty but is not a qwerty

Yellow Black Skin

Figure 203: Landscape Special Keys keyboard – Stone Skin

Special Keys keyboard

Stone Skin

Figure 204: Landscape Symbols/Numeric keyboard - Stone skin

Symbols/Numeric keyboard

Stone Skin

Below is a variety of the GSW Keyboards and skins so you can get an idea of flexibility of keyboard looks available.

Keyboard Image	Keyboard	Skin
Figure 205: QWERTY keyboard – Vista Sky Blue skin	Qwerty keyboard	Vista Sky Blue
Figure 206: QWERTY keyboard – Black Green Skin	Qwerty keyboard	Vista Black Green
Figure 207: QWERTY keyboard - Black White skin	Qwerty keyboard	Vista Black White
Figure 208: QWERTY keyboard - Black Yellow skin	Qwerty keyboard	Vista Black Yellow

Figure 209: QWERTY keyboard - Cinnamon skin		Qwerty keyboard			Vista Sangria
Figure 210: Function keyboard – Stone White skin		Function Keyboard			Stone White
Figure 211: QWERTY keyboard – Vista Amber skin		Qwerty keyboard			Vista Amber
Figure 212: QWERTY keyboard – Vista Green skin		Qwerty keyboard			Vista Green
Figure 213: Numeric keyboard – Stone skin	Numeric Keyboard			Stone Skin
Figure 214: QWERTY keyboard – Android Green skin	Qwerty keyboard			Android Green
Figure 215: QWERTY keyboard – Plum Crazy skin	Qwerty keyboard			Plum Crazy
Figure 216: Qwerty keyboard – White Stone skin	Qwerty keyboard			White Stone
Figure 217: QWERTY keyboard – Caution Yellow skin			Qwerty keyboard			Caution Yellow

Technical Support

When you have a question, please not hesitate to contact GSW using the preferred support method – the GSW Support Ticket system.

Georgia SoftWorks ticket system (http://www.georgiasoftworks.com/support_ost/index.php)

If you are unable to use our ticket system, below is our telephone number.

Call +1 706.265.1018. EST, M-F 8:00 a.m. to 5:30 p.m. and have your Product ID ready.

[1] TIP – The suffix “c2g” stands for “Customer to Georgia SoftWorks”.

[2] TIP – The suffix “g2c” stands for “Georgia SoftWorks to Customer”

[3] The device must have internet access to update from external locations.

[4] Depending on Android version and particular device

[5] The option “Default” is the default display format (Portrait / Landscape / Automatic) of the specific device.

[6] In step 4 of this example we named the configuration “Truck Mount”, so select the folder.

[7] Config file shortcut was added with GSW LADS ver 1.40

[8] Variables are dependant upon device capabilities.

[10] This step is a safety measure to prevent accidental configuration placement of a configuration in the downloads folder.

[11] The configuration to enable / disable automatically sending the images to GSW LADS is described on page 57.