DeviceAnywhere Enterprise. Android Setup Guide

Transcription

1 DeviceAnywhere Enterprise Android Setup Guide

2 DeviceAnywhere Enterprise Android Setup Guide Test Center Enterprise 5.2 SP3 Test Center Enterprise Automation 5.2 January 2012 Copyright Notice Copyright Keynote Systems, Inc. All rights reserved. THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED AS IS WITHOUT ANY EXPRESS REPRESENTATIONS OF WARRANTIES. IN ADDITION, KEYNOTE DISCLAIMS ALL IMPLIED REPRESENTATIONS AND WARRANTIES, INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT OF THIRD PARTY INTELLECTURAL PROPERTY RIGHTS. All text and figures included in this publication are the exclusive property of Keynote and may not be copied, reproduced, or used in any way without the express permission in writing of Keynote. Information in this document is subject to change without notice and does not represent a commitment on the part of Keynote. Keynote may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents except as expressly provided in any written license agreement from Keynote. The trademarks or registered trademarks of Keynote Systems, Inc. in the United States and other countries include Keynote, DataPulse, CustomerScope, Keynote Customer Experience Rankings, Perspective, Keynote Red Alert, Keynote WebEffective, The Internet Performance Authority, MyKeynote, SIGOS, SITE, keynote The Mobile & Internet Performance Authority, Keynote FlexUse, Keynote DeviceAnywhere, DeviceAnywhere, Keynote DemoAnywhere, Keynote MonitorAnywhere. All related trademarks, trade names, logos, characters, design and trade dress are trademarks or registered trademarks of Keynote Systems, Inc. in the United States and other countries and may not be used without written permission. All other trademarks are the property of their respective owners. Please forward any comments or suggestions regarding this document to Keynote Support. Keynote Systems, Inc. 777 Mariners Island Blvd. San Mateo, CA ii Keynote Confidential

3 Android Setup Guide DeviceAnywhere Enterprise Contents About This Document... 5 Document Outline... 5 Typographical Conventions... 6 Contacting Support... 6 Additional Documentation Prerequisites Hardware Software System Requirements for the Ensemble Server System Requirements for DeviceAnywhere Studio Android Emulator Prerequisites Creating an Emulator Instance Before Installing the DeviceAnywhere Android Agent DeviceAnywhere Android Agent Installation OTA Installation Installation Using ADB Onboarding Your Android Device Adding Your Android Device/AVD Running and Setting Up the DeviceAnywhere Agent Onboarding (Attaching) the Device to the Server Appendix: Preparing for Bluetooth Connectivity Keynote Confidential iii

4

5 Android Setup Guide DeviceAnywhere Enterprise About This Document This document is intended for customers who manage their own devices, use local devices, or run emulator instances and describes how to set up software-integrated Android devices and emulator instances in the Keynote DeviceAnywhere mobile test environment. This document describes how to connect Keynote DeviceAnywhere Direct to Device Software and Software Plus Android devices to the Ensemble Server. With the Direct-to-Device Software and Software Plus device interaction technologies, you can control and interact with mobile devices by simply plugging them into the USB port of your computer. You can also communicate with and controls mobile devices wirelessly using Wi-Fi. Additionally, this document also covers how to set up an Android emulator instances for use with the Keynote DeviceAnywhere mobile testing platform. In this document, you will learn how to prepare your Android device (or emulator instance) for communication via USB cable or Wi-Fi. In order to control device input and view device output in the DeviceAnywhere Studio client application, you must attach, or onboard, the device/emulator instance to your Ensemble Server. The onboarding process is run from DeviceAnywhere Studio. IMPORTANT The DeviceAnywhere Agent (application) for Android includes the capability for connecting your device to the Ensemble Server using Bluetooth, and this document covers instructions for Bluetooth connectivity. However, this functionality is best applied to specific use cases contact your Keynote DeviceAnywhere Technical Account Manager (TAM) at for information. If your testing does not require Bluetooth connectivity, we recommend you use USB cable or Wi-Fi instead. Document Outline In this document: Prerequisites provides information on hardware and software prerequisites for onboarding your Android device to the Ensemble Server. Android Emulator covers the prerequisites for and the process of running the Android emulator to create an emulator instance. Before Installing the DeviceAnywhere Android Agent contains information on software installation/configuration requirements in order to install the DeviceAnywhere Agent on your Android device. DeviceAnywhere Android Agent Installation explains the simple procedures for installing/upgrading the DeviceAnywhere Agent on your Android device. Onboarding Your Android Device describes how to add a device from DeviceAnywhere Studio, configure the DeviceAnywhere Agent on the device for a particular connection type, and finish up the onboarding process in DeviceAnywhere Studio. The appendix Preparing for Bluetooth Connectivity contains information on setting up Bluetooth connectivity between your Android device and the Ensemble Server. Read this chapter if connecting to the device via Bluetooth. Keynote Confidential 5

6 DeviceAnywhere Enterprise Android Setup Guide Typographical Conventions The table below describes the typographical conventions used in Keynote DeviceAnywhere documentation. Style Element Examples Blue Links and addresses, cross-references The Document Outline section describes the structure of this manual. Bold User interface elements such as menu items Click My Devices in the Test Center Enterprise view of DeviceAnywhere Studio. Monospace Commands, code output, filenames, directories Right-click the project s step groups directory. Monospace bold User input In a command window, type adb killserver. Italic Document titles and emphasis Refer to the Enterprise Installation Guide for instructions on setting up server infrastructure. Contacting Support If you have any comments or suggestions regarding this document, contact Keynote DeviceAnywhere support for enterprise customers at mcsupport@deviceanywhere.com. You may also send your inquiries about Keynote DeviceAnywhere product demonstrations and consulting services to this address. Customers can find additional support information at Additional Documentation You can find additional information in the following documents (available at Enterprise Installation Guide TCE Automation User Guide TCE Automation Release Notes Test Center Enterprise Interactive User Guide (available at In addition, you can access documentation from the Help menu in the DeviceAnywhere Studio. 6 Keynote Confidential

7 Android Setup Guide DeviceAnywhere Enterprise 1 Prerequisites This section lists the hardware and software prerequisites for connecting to software-integrated Android devices (devices that use Keynote DeviceAnywhere Direct-to-Device Software and Software Plus technologies). This document assumes that you are familiar with interacting with mobile devices in DeviceAnywhere Studio. 1.1 Hardware Hardware requirements include: One USB port and USB cable per mobile device on the computer hosting the Ensemble Server this is required if connecting the device via USB cable. It is also required when connecting an Android device that has not been rooted to the Ensemble Server via Wi-Fi. (The USB cable is required in this case to configure and launch the DeviceAnywhere Agent background process.) Android mobile device(s) please inform your Keynote DeviceAnywhere TAM about the device(s) you intend to test on so we can ensure that a device profile XML file (see software requirements below) can be created for it. NOTE Only USB cable and Wi-Fi connection methods are supported on Android 1.6. Bluetooth connectivity to the Ensemble Server is only supported on Android 2.x or higher devices. Wi-Fi gear (router, access points, etc.) and setup if connecting the device via Wi-Fi (See Before Installing the DeviceAnywhere Android Agent for pointers on Wi-Fi configuration.) Bluetooth dongle(s), if connecting to the device via Bluetooth One USB port per Bluetooth dongle if connecting to devices via Bluetooth (see also System Requirements for the DeviceAnywhere Ensemble Server below) 1.2 Software Software requirements are: A Keynote DeviceAnywhere account assigned the System Admin role (required for onboarding devices) If you require an account, please contact your system administrator or DeviceAnywhere TAM at mcsupport@deviceanywhere.com. Ensemble Server (Team or Individual), pointing to a fully operational Keynote DeviceAnywhere test environment (including Access Server, SQL Server, and other components) Refer to System Requirements for the Ensemble Server below for minimum installation requirements. For detailed installation instructions, refer to the Enterprise Installation Guide. NOTES The Individual Ensemble Server license supports only one server, one client, and two devices concurrently attached to the server. Both server and client are installed on the same machine. Remote access to devices requires Team Ensemble Server. Keynote Confidential 7

8 DeviceAnywhere Enterprise Android Setup Guide DeviceAnywhere Studio client software, pointing to a fully operational DeviceAnywhere test environment Refer to System Requirements for DeviceAnywhere Studio below for minimum installation requirements. NOTE Individual Ensemble Server and DeviceAnywhere Studio software may be installed on the same machine. Android SDK installed on the Ensemble Server (required for running the Android emulator) see Android Emulator for details about SDK components that must be installed. Device profile XML files, procured from Keynote DeviceAnywhere, for the mobile devices you wish to test please contact your Keynote DeviceAnywhere TAM before you update device firmware or install custom components as this might entail changes to the device profile XML file. A limited number of XML files are available for and define the Android emulator instances supported in this release. See Android Emulator for details. The DeviceAnywhere Agent for Android devices, DAAgent.apk (available at your Keynote DeviceAnywhere TAM will provide the exact version of the Agent you must download. Appropriate licensing for the DeviceAnywhere product modules you wish to use USB drivers for your Android devices (available from device vendor Web sites) NOTES The Java Runtime Environment (JRE) v1.6 and Android Debug Bridge (ADB) tool are provided by Keynote DeviceAnywhere and are automatically installed with the Ensemble Server. For optimal performance, we recommend that you uninstall or deactivate any previously installed version of ADB from your Ensemble Server machine. See Before Installing the DeviceAnywhere Android Agent for details. Components of the Keynote DeviceAnywhere test environment require a network connection to communicate with each other System Requirements for the Ensemble Server Minimum system requirements are as follows: 2 GHz dual core processor (Pentium 4) 2 GB RAM At least 10 GB available hard disk space One USB port and USB cable per device connected to the Ensemble Server One USB port per Bluetooth dongle if connecting to devices via Bluetooth Supported operating systems (32 bit): Windows XP SP2, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008 NOTE The Ensemble Server is compatible with the 64 bit version of Windows 7. 8 Keynote Confidential

9 Android Setup Guide DeviceAnywhere Enterprise System Requirements for DeviceAnywhere Studio Minimum system requirements are as follows: 2 GHz dual core processor (Pentium 4) 2 GB RAM At least 10 GB available hard disk space Monitor with at least 1024x768 screen resolution Optional: Audio card for sound input/output Supported operating systems: Windows XP SP2, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Mac OS NOTES You must install JDK v1.5 or later for Mac. Both 32- and 64-bit processing is supported on Windows. In order to begin testing on your Android device, you must: 1 Perform preliminary software installation and configuration steps. If necessary, set up your Android emulator instances. 2 Install the DeviceAnywhere Agent on your Android device. 3 Onboard the device to the Ensemble Server. Keynote Confidential 9

10 DeviceAnywhere Enterprise Android Setup Guide 2 Android Emulator The 5.2 release of Test Center Enterprise Automation enables you to run the Android emulator to create emulator instances, or Android virtual devices, for use in DeviceAnywhere Studio. In this release, emulator instances with the same performance profile as the following devices are supported: Google Nexus One G1/ADP1 (HTC) Motorola Xoom An emulator instance might not look like or resemble the device it is based on in every aspect. However, the emulator instance shares the following key parameters with the device it is based on: OS version Screen size and resolution RAM These parameters are specified in the device profile XML files provided by Keynote DeviceAnywhere for the devices listed above. You can onboard and perform tests on emulator instances in the same way that you would on real devices. NOTES USB cable is the only connection method supported for emulator instances (see Onboarding Your Android Device). Some hardware operations are not supported on AVDs. For example, you can use the Ctrl + F11 key combination to toggle between vertical orientation and rotating an AVD left in DeviceAnywhere Studio. However, while the screen is rotated, the skin is not. An emulator instance counts as one device when determining the maximum number of devices that can be attached to an Ensemble Server. A typical Ensemble Server supports up to six devices or up to four smart devices, with no more than one tablet. 2.1 Prerequisites In order to create and use an Android emulator instance in DeviceAnywhere Studio, you require: The Android SDK, installed on the Ensemble Server NOTES For optimal performance, we recommend that you uninstall or deactivate the ADB instance provided with the Android SDK (see Before Installing the DeviceAnywhere Android Agent). You might need to do this each time you update the SDK. ADB is not required for creating an emulator instance. Device profile XML file for the base device currently, emulator instances based on the Google Nexus One, G1/ADP1, or Motorola Xoom are supported. The corresponding XML file must be copied 10 Keynote Confidential

11 Android Setup Guide DeviceAnywhere Enterprise to the smartphonexmls directory of your DeviceAnywhere Studio installation before onboarding the emulator instance see Before Installing the DeviceAnywhere Android Agent. XML file names are listed below: Google Nexus One Emulator_Unbranded_KDA003_(Nexus_One )_2.3.4_SOFTWARE_ _5.2TA_ xml G1/ADP1 Emulator_Unbranded_KDA002_(ADP1 )_1.6_SOFTWARE_ _5.2TA_ xml Motorola Xoom Emulator_Unbranded_KDA004_(XOOM )_3.2_SOFTWARE_ _5.2TA_ xml In the SDK Manager, for the API level corresponding to each Android OS version you want to emulate, be sure to the select and install the following components: SDK Platform and Google APIs by Google Inc. While both options provide support for the API level, the latter option provides support for Google proprietary applications in your emulator instance. The image below highlights the SDK Platform and Google APIs by Google Inc. options for API levels 13 and 14. Figure 2-1 SDK Components to Download in SDK Manager Keynote Confidential 11

12 DeviceAnywhere Enterprise Android Setup Guide NOTE The API levels supported for DeviceAnywhere Studio emulator instances are 4 (OS version 1.6), 10 (OS version 2.3), and 13 (OS version 3.2). 2.2 Creating an Emulator Instance In order to create an emulator instance: 1 Open the Android SDK Manager. For example, on Windows 7, choose Programs from the Start menu and then Android SDK Tools > SDK Manager. 2 Open the Android Virtual Device Manager: Tools > Manage AVDs. Any existing emulator instances are listed in the window that opens. 12 Keynote Confidential

13 Android Setup Guide DeviceAnywhere Enterprise 3 Click New to set up a new emulator instance. 4 Enter a Name for your AVD. The table below shows selections you must make for each of the supported emulator instance types: Base Device Model API Level 1 Resolution 2 Google Nexus One API level 10 (OS version 2.3) 800 x 480 G1 API level 4 (OS version 1.6) 320 x 240 (change from default to HVGA) Motorola Xoom API level 13 (OS version 3.2) 1280 x 800 The image below shows the Target drop-down list choices for API levels 3 and 4. 1 Select any of the two choices that appear for each API level in the Target drop-down list. You need to have downloaded the SDK Platform and Google APIs by Google Inc. SDK component for the corresponding options to appear in the Target drop-down list see Prerequisites in this chapter. 2 The default choice in the Built-in (Skin) radio button is correct for Google Nexus One (API level 10) and Motorola Xoom (API level 13). For AVDs based on the G1, change the default choice to HVGA. Keynote Confidential 13

14 DeviceAnywhere Enterprise Android Setup Guide The image below shows the resolution selection for an AVD based on the G1. 14 Keynote Confidential

15 Android Setup Guide DeviceAnywhere Enterprise 5 Click Create AVD when done configuring your emulator instance. It is now listed in the Android Virtual Device Manager. 6 To run your emulator instance, select it from the Android Virtual Device Manager and click Start. 7 Enter your launch options and click Launch. NOTE If you select Scale display to real size and your Ensemble Server s resolution is lower than that of the emulator instance, it will appear larger than life in DeviceAnywhere Studio. Your emulator instance is opened in a separate window. Keynote Confidential 15

16 DeviceAnywhere Enterprise Android Setup Guide 8 Proceed with relevant prerequisites for installing the DeviceAnywhere Agent, installing the DeviceAnywhere Agent, and onboarding your AVD. IMPORTANT AVD serial numbers do not stay constant, and this can cause problems during the onboarding process. AVDs are assigned serial numbers in the order in which they are started. If you have two AVDs, A and B, they are assigned sequential serial numbers of the format emulator-xxxx. If you shut down AVD A after onboarding it and start up a third AVD C, it is assigned the serial number originally allotted to A. When onboarding C, you will encounter problems as its serial number is associated with AVD A in DeviceAnywhere Studio. To avoid this problem, make sure to start AVDs up in the same order. This ensures that serial numbers stay associated with the same AVDs. Alternatively, you can offboard an AVD from DeviceAnywhere Studio when you shut it down to release its serial number. To check your AVD s serial number, run the adb devices command from the ADB directory. 16 Keynote Confidential

17 Android Setup Guide DeviceAnywhere Enterprise 3 Before Installing the DeviceAnywhere Android Agent This chapter explains the software installation/configuration steps that you must perform before installing the DeviceAnywhere Agent on your Android device/emulator instance. As part of your Keynote DeviceAnywhere test environment setup, you must: Install the device profile XML file(s) provided by Keynote DeviceAnywhere and any required USB drivers for your mobile device. In addition, we recommend that you uninstall or deactivate any previously installed version of ADB on your Ensemble Server machine. On your device, enable USB debugging, connect your device by USB cable, and select an appropriate USB connectivity mode. Prepare for connectivity by USB cable, Wi-Fi, or Bluetooth. Perform these steps in the order described below: 1 Copy the device profile XML file (e.g., Droid_v2-2.xml) to the smartphonexmls directory of your DeviceAnywhere Studio installation. The default location is: Windows XP: C:\Documents and Settings\<user>\Local Settings\ Application Data\DeviceAnywhere\smartphoneXMLs Windows Vista and later: C:\Users\<user>\AppData\Local\DeviceAnywhere\ smartphonexmls NOTE Users with older installations of DeviceAnywhere Studio might see this folder located at C:\Program Files\DeviceAnywhere\DeviceAnywhereStudio\smartphoneXMLs. If you do not have a device profile XML file, please contact your system administrator or DeviceAnywhere TAM (mcsupport@deviceanywhere.com). 2 Enable USB debugging on your device to ensure that it is able to connect to ADB: Settings > Applications > Development > USB debugging Most devices display a caution icon in the notification bar when USB debugging has been enabled (two examples are highlighted in the image below). When you drag down the notification bar, many devices display a notification in the Ongoing section. USB debugging should automatically be enabled in emulator instances. Keynote Confidential 17

18 DeviceAnywhere Enterprise Android Setup Guide 3 The ADB tool is provided by keynote DeviceAnywhere and is installed automatically with the Ensemble Server at the following default location: C:\Program Files\DeviceAnywhere\ EnsembleServer\adb\adb.exe. For optimal performance, we recommend that you uninstall or deactivate any previously installed version of ADB from your Ensemble Server machine (located in the Android SDK s tools or platform-tools directories). Alternatively, you can replace it with the ADB tool provided by DeviceAnywhere. NOTE If you choose to retain a previously installed version of ADB, we strongly recommend that you issue an adb kill-server command from the installation directory before starting up the Ensemble Server. The ADB tool shipped with the Android SDK has several known issues and can cause instability during prolonged interaction with devices. 4 Download any required USB drivers for your Android device onto the Ensemble Server (not applicable to emulator instances). Consult the Android developer resource page for OEM USB drivers at Also consult your device vendor s Web site. NOTES Device drivers for Google-branded devices can be downloaded as part of the Android SDK. Device drivers are not actually installed until you connect the device. 5 Connect your Android device via USB cable to the Ensemble Server. This is required for connectivity via USB cable, and for devices that are not rooted, for connectivity via other methods as well. (The USB cable is required in this case to configure and launch the DeviceAnywhere Agent background process.) 6 Step through any device driver installation screens that appear. Some drivers are automatically installed when you connect the device. To check if you require a driver, open up the Windows Device Manager (right-click My Computer > Manage > Device Manager). If your device is listed under Other devices, you will need to download and install a device driver. NOTE Emulator instances do not appear in the Windows Device Manager. 7 Ensure that your device is not connected to the Ensemble Server as a USB mass storage device (not applicable to emulator instances); the Android OS must retain control of the device SD card for the DeviceAnywhere Agent to function properly. If your device is mounted as mass storage when you connect it by USB cable to the Ensemble Server, you might see the following Windows notification: Your device will also be listed in Windows Explorer as a removable disk with a drive number: 18 Keynote Confidential

19 Android Setup Guide DeviceAnywhere Enterprise When your device is connected to the Ensemble Server by USB cable, the notification bar displays the USB icon. To disable USB mass storage mode: On some devices, you can specify USB connectivity mode from the USB connection notification. i Drag down the notification bar at the top of the device screen. You should see a USB connection notification in the Ongoing section (see the examples in the image below). ii Click the notification to open up USB connectivity options. iii Select the Charge Only option. On some devices, you must navigate to the Settings menu to specify USB connectivity mode, e.g., Settings > Connect to PC > Default connection type > Charge only. When your device is correctly set up to connect via USB, you will be able to see total and available SD card memory from Settings > SD card and phone storage settings. Keynote Confidential 19

20 DeviceAnywhere Enterprise Android Setup Guide 8 Check that your device is correctly recognized by the Ensemble Server: a b Open a command window and navigate to the ADB installation directory (the default installation location is C:\Program Files\DeviceAnywhere\EnsembleServer\adb\adb.exe). Enter the following command: adb devices You should see your device s Android serial number followed by the word device in the command output. Emulator instance serial numbers are of the format emulator-xxxx. c If you do not see your device s serial number listed: i ii Enter the command adb kill server from the same directory. Re-enter the adb devices command. d If you are still unable to see your device s serial number in the command output: i ii Disconnect all other Android devices from the Ensemble Server. Check the Windows Device Manager (right-click My Computer > Manage > Device Manager). Your device should be listed as an Android Phone or an ADB Interface. 20 Keynote Confidential

21 Android Setup Guide DeviceAnywhere Enterprise NOTE Additionally, you can unplug and reconnect the device USB cable, or turn off USB debugging and turn it back on to check and ensure your device s connectivity to the Ensemble Server. 9 Prepare for connectivity: If connecting by USB cable, ensure that your device is connected by USB cable to the Ensemble Server. If connecting by Wi-Fi: i ii Ensure that the Ensemble Server has a fixed IP address on the internal network. Ensure that the Ensemble Server does not sit behind the Wi-Fi router. iii Ensure that Wi-Fi is enabled on your device (Settings > Wireless & networks > Wi-Fi), and connect to an available network. iv If your phone is not rooted, connect it by USB cable to the Ensemble Server. If connecting by Bluetooth, see the appendix Preparing for Bluetooth Connectivity. When done with all prerequisites, proceed with installing the DeviceAnywhere Agent on your device. Keynote Confidential 21

22 DeviceAnywhere Enterprise Android Setup Guide 4 DeviceAnywhere Android Agent Installation The DeviceAnywhere Agent enables you to access and control the device remotely. This section describes the simple procedure for installing the DeviceAnywhere Agent on an Android device. You can the DeviceAnywhere Agent on an emulator instance over the air as well as using ADB. 4.1 OTA Installation To install or upgrade the DeviceAnywhere Agent on your Android device/emulator instance: 1 Ensure that you are able to install non-market applications: Navigate to Settings > Applications. Ensure that Unknown sources is checked. NOTE If your device does not have this setting, you will need to install the DeviceAnywhere Agent using ADB. Skip to Installation Using ADB below. 2 Using a browser on your device, navigate to Your Keynote DeviceAnywhere TAM will provide the exact version of the Agent you must download. 3 Select the DAAgent.apk file and click to download it to your device. This is the DeviceAnywhere Agent. 4 Select the DAAgent.apk file in your Downloads directory. (On some devices, this can be found in the application tray. On other devices, the Downloads directory can be found in your browser s menu options (Browser application > Menu button > More > Downloads.) 22 Keynote Confidential

23 Android Setup Guide DeviceAnywhere Enterprise 5 Click Install. This installs the DeviceAnywhere Agent on your device. 6 Click Done when the application has been installed. 7 If performing an Agent upgrade, restart the device. If this is not possible, restart the DeviceAnywhere Agent (Menu button > Restart Agent). Keynote Confidential 23

24 DeviceAnywhere Enterprise Android Setup Guide When the installation is complete, the DeviceAnywhere Agent icon is displayed in the application tray. You can now onboard the device to the Ensemble Server. 4.2 Installation Using ADB If your device does not have a setting to enable installing applications from non-market sources, you must install the DeviceAnywhere Agent using the ADB tool installed with the Ensemble Server. Check if you can install non-market applications: Navigate to Settings > Applications. If you are not able to select the Unknown sources option, follow the procedure below to install the DeviceAnywhere Agent. You can also use ADB to install the DeviceAnywhere Agent on emulator instances. 1 Navigate to and select the DAAgent.apk file your DeviceAnywhere TAM will provide the exact version of the Agent to select. 2 Copy the DAAgent.apk file to the ADB installation directory on the Ensemble Server the default path is C:\Program Files\DeviceAnywhere\EnsembleServer\adb\. 3 Ensure that your device is connected by USB cable to the Ensemble Server. 24 Keynote Confidential

25 Android Setup Guide DeviceAnywhere Enterprise 4 Check that your device is recognized navigate to the Windows Device Manager (right-click My Computer > Manage > Device Manager). Your device should be listed as an ADB-connected Android device. NOTE Emulator instances are not listed in the Windows Device Manager. 5 Open a command window and run the following command from the ADB directory to install or upgrade the DeviceAnywhere Agent: adb install r DAAgent.apk If there is more than one Android device connected to the Ensemble Server, specify the device on which to install the DeviceAnywhere Agent: adb s <DeviceSerialNumber> install r DAAgent.apk 6 If performing an Agent upgrade, restart the device. If this is not possible, restart the DeviceAnywhere Agent (Menu button > Restart Agent). The DeviceAnywhere Agent should now be displayed as an application on your device. Keynote Confidential 25

26 DeviceAnywhere Enterprise Android Setup Guide 5 Onboarding Your Android Device Once you have met all prerequisites (including preparing for Bluetooth connectivity, if necessary), you can onboard your device or emulator instance to the Ensemble Server. To onboard the device/emulator instance, you must: 1 Add your device/avd from DeviceAnywhere Studio. 2 Set up the DeviceAnywhere Agent to connect via USB cable, Wi-Fi, or Bluetooth. 3 Attach your device to the DeviceAnywhere Ensemble Server to complete the onboarding process. It is best to complete the onboarding process one device at a time to facilitate any troubleshooting steps. 5.1 Adding Your Android Device/AVD 1 From DeviceAnywhere Studio, navigate to the Device Manager view in the left sidebar and click Add device. The Add device window lists all device profile XML files that can be found in your DeviceAnywhere Studio installation. If you do not see your device XML file in this list, check to make sure that you have copied it to the smartphonexmls directory of your DeviceAnywhere Studio installation. The default location is: Windows XP: C:\Documents and Settings\<user>\Local Settings\ Application Data\DeviceAnywhere\smartphoneXMLs Windows Vista and later: C:\Users\<user>\AppData\Local\DeviceAnywhere\ smartphonexmls 2 From the left pane, select the Android device you wish to add and click Next. 26 Keynote Confidential

27 Android Setup Guide DeviceAnywhere Enterprise 3 Enter a name of your choice for the device, e.g., Test Nexus S, and click Next. 4 DeviceAnywhere Studio confirms that the device has been successfully added. Click Finish. Your device is now listed as offline in the Device Manager view of DeviceAnywhere Studio. NOTE If you uncheck Onboard device now, you can resume the onboarding process later by rightclicking your device in the Device Manager view and selecting Onboard Device. To continue with the onboarding process, you must run and set up the DeviceAnywhere Agent on your Android device. 5.2 Running and Setting Up the DeviceAnywhere Agent On your Android device, you must start up the DeviceAnywhere Agent and set it up for connecting to the Ensemble Server using USB cable, Wi-Fi, or Bluetooth. Keynote Confidential 27

28 DeviceAnywhere Enterprise Android Setup Guide NOTE if your device is already onboard and you want to change your connection type, unplug the USB cable if it is not required, and skip to step 2 below. 1 Start the DeviceAnywhere Agent on your device by clicking the DeviceAnywhere Agent icon on your home screen. 2 To set up the DeviceAnywhere Agent, choose Menu button > Setup. This displays the Agent setup screen. 3 Choose a connection type and specify any connection parameters. To connect via USB cable: NOTE USB cable is the only connection method supported for emulator instances. a Select USB Cable from the Connection type drop-down list. 28 Keynote Confidential

29 Android Setup Guide DeviceAnywhere Enterprise To connect via Wi-Fi (not supported for emulator instances): a b c Select Wi-Fi from the Connection type drop-down list. Enter the Hostname or IP address of the Ensemble Server. Leave the default connection Port as is (7890). This should match the default port on the Ensemble Server. To connect via Bluetooth (not supported for emulator instances): a Select Bluetooth from the Connection type drop-down list. b In the Bluetooth MAC field, enter the MAC address of the Bluetooth adapter on the Ensemble Server (see Preparing for Bluetooth Connectivity). NOTE Although Bluetooth connectivity to the Ensemble Server is supported (on Android 2.x or higher devices), this functionality is best applied to specific use cases contact your Keynote DeviceAnywhere TAM for information. If your testing does not require Bluetooth connectivity, we recommend you use USB cable or Wi-Fi instead. Keynote Confidential 29

30 DeviceAnywhere Enterprise Android Setup Guide 2 Restart the DeviceAnywhere Agent (Menu button > Restart Agent). 5.3 Onboarding (Attaching) the Device to the Server Continue to the onboarding procedure in DeviceAnywhere Studio: 1 If you need to, initiate the onboarding wizard by right- clicking your device in the Device Manager view and selecting Onboard Device. 2 Select the IP address or hostname of the Ensemble Server you are onboarding the device to. 3 Select a connection method. This must match the connection method selected in the DeviceAnywhere Agent. You can only select the USB Cable option for emulator instances. NOTE Connecting to the Ensemble Server via USB Cable or Wi-Fi should satisfy most testing needs; you should not need to use the other connectivity options. 30 Keynote Confidential

31 Android Setup Guide DeviceAnywhere Enterprise 4 Ensure that your device is ready to connect to the server and click Next. 5 Select the serial number for your device and click Next. (The list only displays Android devices that have not been onboarded yet.) If your device does not appear in the list: a b c Open a command window and navigate to the ADB installation directory (the default installation location is C:\Program Files\DeviceAnywhere\EnsembleServer\adb\). Enter the command adb kill-server. Enter the command adb devices. You should see your device s Android serial number followed by the word device in the command output. Emulator serial numbers are of the format emulator-xxxx. Keynote Confidential 31

32 DeviceAnywhere Enterprise Android Setup Guide IMPORTANT AVD serial numbers do not stay constant, and this can cause problems during the onboarding process. AVDs are assigned serial numbers in the order in which they are started. If you have two AVDs, A and B, they are assigned sequential serial numbers of the format emulator-xxxx. If you shut down AVD A after onboarding it and start up a third AVD C, it is assigned the serial number originally allotted to A. When onboarding C, you will encounter problems as its serial number is associated with AVD A in DeviceAnywhere Studio. To avoid this problem, make sure to start AVDs up in the same order. This ensures that serial numbers stay associated with the same AVDs. Alternatively, you can offboard an AVD from DeviceAnywhere Studio when you shut it down to release its serial number. If there are several serial numbers in the list and you are unsure which one to pick, disconnect all other Android devices from the Ensemble Server. Your device serial number should now be the only one listed. If you are unable to unplug other Android devices, follow the steps below to identify your device: a b c d Open a command window and navigate to the ADB installation directory (the default location is C:\Program Files\DeviceAnywhere\EnsembleServer\adb\). Enter the command adb devices. Note the serial numbers of the devices in the command output. From the same directory, enter the following command for each serial number: adb s <DeviceSerialNumber> shell getprop ro.product.model The command output matches the serial number to the device model. Repeat this command till you have successfully identified your device. 6 Click Finish to complete the onboarding procedure. 32 Keynote Confidential

33 Android Setup Guide DeviceAnywhere Enterprise Your device is now listed in Device Manager view of DeviceAnywhere Studio with green device control status icons. The device is also listed in the On Board Devices package in the Test Center view. Acquire the device to begin testing. Keynote Confidential 33

34 DeviceAnywhere Enterprise Android Setup Guide Appendix: Preparing for Bluetooth Connectivity You can connect Android devices to the Ensemble Server via Bluetooth. You must prepare for Bluetooth connectivity by inserting a Bluetooth dongle into a USB port on the Ensemble Server, procuring the MAC address of the Bluetooth adapter, enabling Bluetooth on the device, and pairing it with the server. NOTE Keynote DeviceAnywhere supports a maximum two devices connected per dongle. To set up Bluetooth connectivity (you must be able to view and access the Ensemble Server for this procedure): 1 Insert a Bluetooth dongle into a USB port on the Ensemble Server. Windows should automatically install a device driver; alternatively, use the software that came with the dongle to install a driver. 2 Make a note of the MAC address of the Bluetooth adapter you will require this when configuring the DeviceAnywhere Agent to connect to the Ensemble Server: a Right-click the Bluetooth icon in the notification area of the Windows Taskbar to open up a context menu. Select Open Settings > Hardware > Generic Bluetooth Radio > Properties. You can also access this menu from the Windows Device Manager: Right-click My Computer > Manage > Device Manager > Bluetooth Radios > Generic Bluetooth Radio > Properties. b From the Advanced tab, note the MAC address of the Bluetooth adapter (highlighted in the image below). 3 Enable Bluetooth on your Android device (Settings > Wireless & networks > Bluetooth). 4 Ensure that your device is discoverable (Settings > Wireless & networks > Bluetooth settings > Discoverable). 34 Keynote Confidential

35 Android Setup Guide DeviceAnywhere Enterprise 5 Pair your Android device with the Ensemble Server: a b Right-click the Bluetooth icon in the notification area of the Windows Taskbar and select Add a Device. Select your device from the list displayed and click Next. The Ensemble Server indicates that it is connecting to the device and displays a pair code. 6 On your Android device, ensure that you see the same pair code and click Pair. 7 On your Ensemble Server, select Next. Keynote Confidential 35

36 DeviceAnywhere Enterprise Android Setup Guide The Ensemble Server indicates that the device has been successfully paired. Your device is now listed as a Bluetooth device under Devices and Printers. 8 If your device is not rooted, connect it by USB cable to the Ensemble Server. 9 Proceed with installing the DeviceAnywhere Agent and onboarding your device to DeviceAnywhere Studio. 36 Keynote Confidential