Ranorex Help Center

How can we help you?

Troubleshooting

Troubleshooting Android USB connections

Troubleshooting Genymotion

For a general troubleshooting please find some  tips and tricks below.

Ranorex cannot find the Android USB connected device

Reason:

Ranorex is using the external ADB (Android Debug Bridge) tool to find all connected USB devices. If the ADB tool is not able to identify the USB connected devices, also Ranorex won't be able to do so. To check if a USB connection can be established, open any ADB tool from the command line (see note below). In the command window type "adb devices". If no device is listed, Ranorex also won't find the device since no specific USB driver is installed.


Note The ADB tool can be found in the sub-folder "Bin\RxEnv\Android\tools" of the Ranorex installation path (e.g. C:\Program Files (x86)\Ranorex 5.2).


Note To quickly open up a command window simply keep the SHIFT key pressed while clicking the menu item "Open command window here" in the context menu of Windows explorer.

List ADB devices from command line

List ADB devices from command line

Solution:

First the USB driver for the connected Android device needs to be downloaded. If you are using any  Google Nexus device, please open  this website and follow the instructions. For all other devices please visit the manufacturer's website and download the USB driver from there. A small list of different manufacturer OEM drivers can be found  here. After downloading the driver please follow instructions  here for the installation process.

The USB-Driver cannot be installed (unsigned driver)

Reason and Solution:

For Windows 8 or higher there might be problems with unsigned drivers. Please follow these instructions to disable the driver signature enforcement. Alternatively any tool can be used that installs the corresponding ADB driver (e.g. http://adbdriver.com/downloads/) for you.

The Genymotion device does not start

Problem:

Probably there is a problem with the Genymotion VM settings.

Solution:

Please visit the Genymotion FAQ and check whether your issue is described there. Alternatively the following steps could be done in order to fix the issue with the Genymotion VM settings:
  • Delete the VM Host-Only Ethernet Adapter
    • Open Oracle VM Virtual Box Manager -> File -> Network -> Host only Network
    • Delete the VirtualBox Host-Only Ethernet Adapter
  • Close the Oracle VM and restart Genymotion

The Genymotion device cannot be found by Ranorex when trying to add it as emulator

Reason:

Genymotion is technically an emulator but works differently from Google emulators.

Solution:

Use the USB or Network connection option to add any Genymotion emulator to the Ranorex known device list.

The Genymotion device cannot be found by Ranorex when using the USB connection option

Reason #1

Genymotion starts his own ADB process allowing to emulate a USB connection. That's why a Genymotion ADB process is required.

Solution

Restart the Genymotion emulator and check the Windows Task Manager for the status of the Genymotion ADB process.

Reason #2

The Genymotion process and the Ranorex ADB process are in conflict with each other.

Solution

First please make sure that Genymotion is running. Continue with opening the Windows Task Manager and with killing all ADB processes. Please navigate to any ADB tool on your hard disk (see note below) and open a command window (see another note below) with the current path. Type in "adb connect <IP>" whereas <IP> should be replaced by the Genymotion Emulators IP address. In order to list all currently available devices, open the Genymotion Shell and type "devices show".


Note The ADB tool can be found in the sub-folder "Bin\RxEnv\Android\tools" of the Ranorex installation path (e.g. C:\Program Files (x86)\Ranorex 5.2).


Note To quickly open up a command window simply keep the SHIFT key pressed while clicking the menu item "Open command window here" in the context menu of Windows explorer.

The Genymotion device with installed Ranorex service application cannot be found when using the network connection option

Reason:

The Genymotion emulator and Ranorex are not running in the same Network.

Solution:

In Genymotion please open the Ranorex Service application. Click on Details so that all available options are shown. Click on the presented IP address and change it to another one (the one that you are connected with).

The Ranorex RxBrowser gets closed when navigating to the website to automate

Reason:

Some Genymotion emulators have some issues with opening websites. To check whether Genymotion will work correctly with RxBrowser do the following steps:
  1. Start the Genymotion Emulator
  2. Start the default Genymotion/Android web browser
  3. With the default web browser navigate to the website that you want to automate with RxBrowser
If the website works correctly with the default web browser, then it will also work with RxBrowser. If you face any issues please find a "Solution" below.

Solution:

Try another Genymotion emulator or use one of these:
  • HTC One X – 4.1.1-API16
  • Sony Xperia Z – 4.3 – API18
  • Samsung Galaxy S5 – 4.4.4 – API19

General Troubleshooting on connections with Android devices

If you have connection problems try to consider following potential sources of error:

  • Make sure that the system under test (the mobile devices) and the machine running the tests (where Ranorex is installed) are in the same network.
    After changing Wi-Fi settings on the device, make sure to restart the device.
  • If you have more than one network interface configured on your android device, you can switch between them by touching the IP address in the service app and choosing the desired address.
  • Try to increase the Discovery Timeout at the 'Mobile' section in the 'Plugins' tab of general settings.
  • Try to find out more about the connection problem by moving your mouse over the device in 'Manage Devices' dialog.
Devices details

Devices details

  • If you have more than one device from the same model, make sure to set unique device names for these devices in the service app on the devices.
Set device name

Set device name