The notes below provide descriptions of the new features and changes introduced with each release of Android Gateway. You are strongly encouraged to read about the relevant changes whenever you upgrade from an earlier version. Potential compatibility issues are highlighted in RED.
You can get the latest version of Android Gateway from the Eggplant downloads page.
Runs on: Windows 10, Windows 7. macOS 10.15, macOS 10.14, macOS 10.13, macOS 10.12.
Connects to: 4.1.1 and later.
Note: WebDriver functionality requires Android 5.0 (API level 21) and later on the device being tested.
5.6 (15 October 2019)
- Adds support for Android 10.
- Adds support for ADB 1.0.41.
- Checks for port conflicts of attached Android devices.
- Various bug fixes and improvements.
5.5.1 (6 September 2019)
- Improves handling of port conflicts.
- Potential conflicts now display in the UI.
- Device automation won't launch when ports are in conflict.
5.5 (25 June 2019)
- Adds support for Eggplant Functional to automatically determine element name, type, and image file name based on information from the object model.
- Adds support for the AppList function in Eggplant Functional.
- Help us improve Android Gateway! Leave the new Share Installation Details option enabled in Global Settings > Privacy Settings to provide operating system and application version information to Eggplant to help direct our future development efforts.
- Various bug fixes and improvements.
- WebDriver functionality requires Android 5.0 (API level 21) and later on the device being tested.
5.4 (11 March 2019)
- Adds Zero-conf (Bonjour) support. As Android Gateway launches, connected Android devices announce themselves and Eggplant Functional picks up that information and automatically add those devices to the Connection List.
- WebDriver is now supported on all platforms without the need to install any Appium components. Note that this functionality requires Android 4.3 (API level 18) or later.
5.2 (1 October 2018)
- Improves WebDriver support to work with an upcoming Eggplant Functional release.
- ADB commands now work against instances of Android Gateway that are not hosted on the same computer as Eggplant Functional.
- Improves readability of logs.
- Improved stability.
- Simplified configuration.
- Faster screenshots.
- Adds the ability to configure the waiting period after a device reboot.
- Fixes certain cases where on-device daemons could not be launched.
- Logs can now be cleared from the UI.
- Fixes mock location services.
- Fixes “eggSensor has stopped working” bug.
- Windows installer now shuts down Android Gateway daemons prior to upgrade.
5.0.2 (4 April 2018)
- Fixes a problem where connecting to a SUT would trigger a restart in some rare cases.
- Fixes a problem where the screen stops updating.
5.0 (18 January 2018)
- Adds Local Screenshots as a way to obtain screenshots from some LG G5 phones. Currently, this feature is available for Android Gateway on Mac only.
- Reduces the amount of log messages and changes their format. Debug messages don’t display in the UI, but can be saved into a file. Instructions for obtaining detailed log messages can be found at Resources > Troubleshooting > Get_AG_Logs.txt.
- Stops forwarding ports after SystemNative2 shuts down.
- The screen is no longer cut off in certain scenarios.
- Resolves an issue with connection sharing that caused rejections even when sharing was allowed.
- Other minor bug fixes and stability improvements.
4.2.3 (19 October 2017)
Adds the capability for users to choose how the VNC server deals with multiple clients. The server can be set up to always share a connection, never share a connection, or default to the Connection Preferences settings in Eggplant Functional.
A new log configuration file, LogConfig.txt, allows users to make changes to logs:
Logs can now be printed to stdout, saved to a file, or both.
The logging level can now be adjusted individually for each subsystem.
Adds the capability to configure the format of log files.
This file can be found in the Android Gateway Resources folder:
C:\Program Files (x86)\AndroidGateway\Resources\
- Resolves a problem with integration with Eggplant Manager.
4.2.2 (30 August 2017)
- Resolves a problem where the settings stored in config.txt were intermittently lost.
- Resolves a problem that led to conflicts between ADB versions.
4.2.1 (18 August 2017)
- Resolves crashes in Android Gateway when eggPlant Manager tries to connect.
4.2 (7 August 2017)
- Adds support for tight VNC encoding.
- Restarts Android Debug Bridge (ADB) when it becomes unresponsive.
- Adds three new options for SystemNative2 that control pixel ordering to support clients with different behaviors: --rgb-reverse, --rgb-straight, and --rgb-auto. These options are not necessary for most users and could create problems if used incorrectly.
- Moves Start menu item into the TestPlant folder on Windows.
- Fixes a deadlock that occurred when switching encoding types in the client while a connection is active.
- Other minor bug fixes and stability improvements.
4.1.2 (2 June 2017)
- Enables rotation on more devices.
4.1.1 (21 March 2017)
- Fixes a bug that required killing Android Debug Bridge (ADB) between launch attempts in some Windows environments.
- Fixes a problem with switching to Wi-Fi Mode on certain devices.
4.1 (9 March 2017)
- Added support for Windows 32-bit.
- Now runs from the Start Menu on Windows using the system's JRE.
- Missing wireless adb connections no longer slow down USB (or other wireless) adb connections.
- Fixed a problem that prevented working with some x86 emulators.
4.0 (8 February 2017)
- Fixed a bug that prevented installation of Android Gateway in an arbitrary directory on Windows.
- Android Gateway no longer hangs up when it encounters a non-authorized device.
- Fixed a problem that resulted in Android Gateway using too many ports on the system.
- Fixed an infinite loop problem that occurred while installing components. If the installation fails three times, Android Gateway will suggest disabling that component if it is not critical.
- On a Mac, copy and paste now work using the Command key.
- Other minor improvements and fixes.
- Added support for mock locations.
- Added support for ADB version 1.0.36.
- Android Gateway is now bundled with the latest version of JRE.
- Mac binaries are now signed.
- Passwords are now obscured in Android Gateway logs.
3.4 (12 October 2016)
- Support for eggPlant Manager 5.2.
3.3 (30 September 2016)
- Added a WiFi/USB menu to the GUI. From this menu, Android devices can be switched between Wi-Fi and USB modes. WiFi connections to Android devices can be launched from this menu.
- Added a checkbox to Device Settings > Screen Control tree that allows device rotation to be disabled. This is useful for Android devices that don’t support installation of the eggSensor support app.
- Added Custom Parameters to the Help menu. Selecting this brings up a window with a list of parameters that can be entered in the Custom Parameters box under Device Settings > Advanced.
- A bug was fixed that delayed Android Gateway start time in environments with slow internet connections.
3.2.1 (12 August 2016)
- Improvements to the interface. The settings tree has been reorganized, with device settings grouped into one subtree. This makes it clearer which settings correspond to a device, and which settings are global. Also, the appearance of the tree has improved.
- Home in global settings has been replaced by Logging, which makes the purpose of this field more intuitive. As before, the log files from individual devices are saved to
- Global settings are now saved to ~/.AndroidGateway/config.txt.
- Changes to the status message. The messages are more informative now.
- Android Gateway now can downgrade the components installed on the devices (eggSensor and eggBoard), which makes it easier to switch between older and newer versions of Android Gateway.
- A bug was fixed that caused typed letters to appear out of order in some situations.
- Other minor bug fixes.
3.1 (26 April 2016)
- New user interface. The tabs were removed, and the settings have been moved into a panel on the right and arranged into a tree; the settings displayed correspond to the device selected in the table on the left.
- Improvements have been made to make Android Gateway cope better with high-latency low-bandwidth networks.
- Support for x86 architecture was added. (We have tested x86, x86_64, armeabi, armeabi-v7a, and armeabi-v8). For x86 devices,
Compatibility modemust be enabled in the Screen Control section of Settings. We continue working to enhance mouse control for these devices.
- Android Gateway can now discover running emulators and connect to them.
- The logging system has been enhanced. Logs can be forwarded into a file. Also logging screen can be cleared by clicking a button in the menu, which is helpful for troubleshooting. Logs can be cleared or forwarded into a file after the service has started.
- Android Gateway now automatically finds suitable ports for devices that are discovered for the first time and have never been configured.
- Now Android Gateway automatically checks the user's port selection before starting a service on a device. If the same port is used by more than one device, Android Gateway informs the user of the problem.
- Added an option to the Help menu that opens a web browser pointed to online documentation.
3.0 (14 March 2016)
- Better support for multiple devices. Android Gateway detects multiple connected devices and displays their serial numbers and models in a table on the Service tab. Settings can be chosen separately for each phone. Settings changes are applied to the phone that is selected in the Service tab, and whose model is displayed in the title of the main window.
- Settings are saved to the phone. The settings are saved to a file on the phone each time the user starts the VNC service. The settings are also saved when the user quits Android Gateway by closing the Android Gateway window. Note, however, that the settings are not saved if you unplug the device, nor are they saved if you kill Android Gateway through shell or through Cmd+Q.
- New Autostart setting allows Android Gateway to automatically start the VNC service on this phone as soon as the phone is connected to the computer.
- Improved Logging with colored log messages: red is for error messages, orange is for warnings, green and blue are for informational messages. Some of the logging and error message that used to be hidden in the phone are now displayed in the logging window.
- Improved rotation for Android 6.0 devices. Some of the internal functionality that relates to capturing the screen has changed in Android 6.0, which has caused problems when doing rotation using the previous Android Gateway version. The new behavior has been taken into account, so rotation should now work with Android 6.0 devices.
- Screen scale setting has been removed from Android Gateway because eggPlant Functional always overrides this preference as soon as the connection is established. Screen scaling is still supported, but now there is only one place to set it—in eggPlant Functional—which will reduce confusion.
- Compatibility issues with eggPlant Functional. Additional functionality has been added to Android Gateway that should help you resolve any compatibility issues you might have with eggPlant Functional 16.01.
- Bug fixes and stability improvements.