Connect Android Devices

Filter by IDE
Select the Progress AppBuilder client you are currently using for development.

IDE

To connect your Android device in AppBuilder, you need to configure your system and device first. You need to install the latest USB device drivers on your system and configure your Android device for development. You can connect devices running Android 4.0 and later.

After you have launched a native iOS or Android device emulator (including Genymotion), while the emulator is running, AppBuilder recognizes and treats it as a connected device.

You cannot publish application packages created with the Build, Build and deploy, Build <app_name> in Cloud and Build <app_name> and Deploy operations to Google Play.

Procedure

In-Browser

This operation is not available in the in-browser client. You cannot connect devices in the in-browser client.

Windows

Connect Android Physical Devices

  1. Download and install the latest USB drivers for your device.
    USB drivers are available from the device manufacturers or as part of the Android SDK.
    The latest USB drivers may not always be in the SDK and you might want to check with the device manufacturer for the latest driver.
  2. Configure your device for USB debugging.
    On Android 3.x and earlier devices, go to SettingsApplicationsDevelopment and verify that USB debugging is selected.
    On Android 4.x devices, go to SettingsDeveloper options and verify that USB debugging is selected.
  3. Connect your device to your system via USB cable.
  4. Run the classic Windows desktop client and open the code for your app.
  5. In the status bar, click Show Mobile Devices and verify that AppBuilder lists your connected device.

If you cannot enable USB debugging because Android does not show Developer options in the Settings menu, you need to manually enable Developer options for your phone.

  1. On your device, go to SettingsAbout phone.
  2. Locate Build number and tap it seven times.
    On the third tap Android starts showing a notification that you are now a few steps away from being a developer. On the seventh tap Android show the following notification: You are now a developer!

If your device does not appear in the list, you might need to disconnect it from your system and perform the following additional steps. If this does not solve your problem, see Troubleshooting or visit our forums.

  • (Optional) Enable installing applications from unknown sources on your device.
    On Android 3.x and earlier devices, go to Settings -> Applications and verify that Unknown sources is selected.
    On Android 4.x devices, go to Settings -> Security -> Device administration and verify that Unknown sources is selected.
  • (Optional) On Android 4.x devices, change the USB connection mode.
    On an Android device without additional OEM customizations, go to Settings -> Storage and tap and hold USB connection in the top right corner of the screen. Select a different USB connection mode than the currently selected.
    If you cannot find the USB connection button in Settings -> Storage, browse for this setting in the Settings menu and its submenus.
  • (Optional) Verify that Windows sees the device as a development device and not a USB storage device.
    You need to connect the device to your system first.
  • (Optional) Use the Android debugging bridge to see if the device is listed for AppBuilder to use.
    You need to connect the device to your system first.
    1. Open a command prompt and navigate to: %LOCALAPPDATA%\Temp\1\adb
      Alternate paths: %LOCALAPPDATA%\Temp\adb
    2. or if you have installed the ADT bundle, full_path_to_the_adt_bundle\sdk\platform-tools
    3. Type adb devices and press Enter.
      This displays the list of connected Android devices that AppBuilder can connect to.

Connect Android Virtual Devices

  1. In the top menu bar, select RunNative Emulator.
  2. Select Android and click Next.
  3. If you do not see Next, you need to configure the native emulator.
    1. Download and install the Android SDK.
    2. Verify that you have added the following Android SDK directories to the PATH environment variable:
      • platform-tools
      • tools
    3. If you have already installed the Android SDK and AppBuilder cannot locate the installed SDK automatically, click Browse and provide the location where the SDK is installed.
    4. Click Next.
  4. (Optional) Click AVD Manager to create new virtual devices.
  5. Select a virtual device from the list and click Launch Emulator.
  6. Wait for the emulator to load.
  7. In the status bar, click Show Mobile Devices and verify that AppBuilder lists your connected devices.

Visual Studio

Connect Android Physical Devices

  1. Download and install the latest USB drivers for your device.
    USB drivers are available from the device manufacturers or as part of the Android SDK.
    The latest USB drivers may not always be in the SDK and you might want to check with the device manufacturer for the latest driver.
  2. Configure your device for USB debugging.
    On Android 3.x and earlier devices, go to SettingsApplicationsDevelopment and verify that USB debugging is selected.
    On Android 4.x devices, go to SettingsDeveloper options and verify that USB debugging is selected.
  3. Connect your device to your system via USB cable.
  4. Run Microsoft Visual Studio and open the code for your app.
  5. In the top menu bar, click AppBuilderDevices List and verify that AppBuilder lists your connected device.

If you cannot enable USB debugging because Android does not show Developer options in the Settings menu, you need to manually enable Developer options for your phone.

  1. On your device, go to SettingsAbout phone.
  2. Locate Build number and tap it seven times.
    On the third tap Android starts showing a notification that you are now a few steps away from being a developer. On the seventh tap Android show the following notification: You are now a developer!

If your device does not appear in the list, you might need to disconnect it from your system and perform the following additional steps. If this does not solve your problem, see Troubleshooting or visit our forums.

  • (Optional) Enable installing applications from unknown sources on your device.
    On Android 3.x and earlier devices, go to Settings -> Applications and verify that Unknown sources is selected.
    On Android 4.x devices, go to Settings -> Security -> Device administration and verify that Unknown sources is selected.
  • (Optional) On Android 4.x devices, change the USB connection mode.
    On an Android device without additional OEM customizations, go to Settings -> Storage and tap and hold USB connection in the top right corner of the screen. Select a different USB connection mode than the currently selected.
    If you cannot find the USB connection button in Settings -> Storage, browse for this setting in the Settings menu and its submenus.
  • (Optional) Verify that Windows sees the device as a development device and not a USB storage device.
    You need to connect the device to your system first.
  • (Optional) Use the Android debugging bridge to see if the device is listed for AppBuilder to use.
    You need to connect the device to your system first.
    1. Open a command prompt and navigate to: %LOCALAPPDATA%\Temp\1\adb
      Alternate paths: %LOCALAPPDATA%\Temp\adb
    2. or if you have installed the ADT bundle, full_path_to_the_adt_bundle\sdk\platform-tools
    3. Type adb devices and press Enter.
      This displays the list of connected Android devices that AppBuilder can connect to.

Connect Android Virtual Devices

  1. In the top menu bar, select AppBuilderRun Native Emulator.
  2. Select Android and click Next.
  3. If you do not see Next, you need to configure the native emulator.
    1. Download and install the Android SDK.
    2. Verify that you have added the following Android SDK directories to the PATH environment variable:
      • platform-tools
      • tools
    3. If you have already installed the Android SDK and AppBuilder cannot locate the installed SDK automatically, click Browse and provide the location where the SDK is installed.
    4. Click Next.
  4. (Optional) Click AVD Manager to create new virtual devices.
  5. Select a virtual device from the list and click Launch Emulator.
  6. Wait for the emulator to load.
  7. In the top menu bar, click AppBuilderDevices List and verify that AppBuilder lists your connected devices.

CLI

Connect Android Physical Devices

  1. Download and install the latest USB drivers for your device.
    USB drivers are available from the device manufacturers or as part of the Android SDK.
    The latest USB drivers may not always be in the SDK and you might want to check with the device manufacturer for the latest driver.
  2. Configure your device for USB debugging.
    On Android 3.x and earlier devices, go to SettingsApplicationsDevelopment and verify that USB debugging is selected.
    On Android 4.x devices, go to SettingsDeveloper options and verify that USB debugging is selected.
  3. Run the command prompt.
  4. Connect your device to your system via USB cable.
  5. Run the following command to list connected Android devices.

    appbuilder device android
    

If you cannot enable USB debugging because Android does not show Developer options in the Settings menu, you need to manually enable Developer options for your phone.

  1. On your device, go to SettingsAbout phone.
  2. Locate Build number and tap it seven times.
    On the third tap Android starts showing a notification that you are now a few steps away from being a developer. On the seventh tap Android show the following notification: You are now a developer!

If your device does not appear in the list, you might need to disconnect it from your system and perform the following additional steps. If this does not solve your problem, see Troubleshooting or visit our forums.

  • (Optional) Enable installing applications from unknown sources on your device.
    On Android 3.x and earlier devices, go to Settings -> Applications and verify that Unknown sources is selected.
    On Android 4.x devices, go to Settings -> Security -> Device administration and verify that Unknown sources is selected.
  • (Optional) On Android 4.x devices, change the USB connection mode.
    On an Android device without additional OEM customizations, go to Settings -> Storage and tap and hold USB connection in the top right corner of the screen. Select a different USB connection mode than the currently selected.
    If you cannot find the USB connection button in Settings -> Storage, browse for this setting in the Settings menu and its submenus.
  • (Optional) Verify that Windows sees the device as a development device and not a USB storage device.
    You need to connect the device to your system first.
  • (Optional) Use the Android debugging bridge to see if the device is listed for AppBuilder to use.
    You need to connect the device to your system first.
    1. Open a command prompt and navigate to: %LOCALAPPDATA%\Temp\1\adb
      Alternate paths: %LOCALAPPDATA%\Temp\adb
    2. or if you have installed the ADT bundle, full_path_to_the_adt_bundle\sdk\platform-tools
    3. Type adb devices and press Enter.
      This displays the list of connected Android devices that AppBuilder can connect to.

Connect Android Virtual Devices

  1. To run your app in the Android emulator from the Android SDK, run the following command.

    appbuilder emulate android --avd <Name>
    

    Where <Name> is the name of the Android virtual device, as listed by android list avd. You can specify only one virtual device at a time.
    If you do not set the --avd option, the command-line interface launches the default virtual device or runs your app in a currently running virtual device, if any.

    The command-line interface launches the selected virtual device, if not running. If the selected virtual device is already running, the command-line interface deploys your app in it.

  2. To run your app in Genymotion, run the following command.

    appbuilder emulate android --geny <Name>
    

    Where <Name> is the name of the Genymotion virtual device, as listed by genyshell -c "devices list". You can specify only one virtual device at a time.
    If you do not set the --geny option, the command-line interface launches the default Android virtual device or runs your app in a currently running virtual device, if any.

    The command-line interface launches the selected virtual device, if not running. If the selected virtual device is already running, the command-line interface deploys your app in it.

  3. Wait for the emulator to load.
  4. (Optional) Repeat Steps 1-3 for any additional Android virtual devices on which you want to run your app.

Next Steps

Continue development.

See Also

Start a free trial Request a demo
Contact us: +1-888-365-2779
sales@telerik.com
Copyright © 2016-2017, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.