Intel Integrated Native Developer Experience (INDE): IDE Integration for Android* 1.5.8 Overview IDE Integration for Android provides productivity-oriented design, coding, and debugging tools for applications targeting Android* on ARM* and Intel architecture devices, including smartphones and tablets. The tools are compatible with Android Studio*, Microsoft* Visual Studio* and Eclipse* and support popular Android SDKs including the Android Native Development Kit (NDK). New Features Added in 1.5.8 Visual Studio Plugins o Android SDK Manager o AVD Manager o LogCat monitoring (Device or emulator) o ADB Shell (connected device) o Java language support (3 rd Party) Visual Studio Templates o Native Activity Project Visual Studio Build System o Support for GCC 4.9 (32 & 64 bit) o Support for Android SDK API 21 o Additional NDK C++ lib support Android Studio Templates o Native Activity Project Separate Android SDK install for Android Studio Android SDK with API 21 and Atom(32 & 64 bit) images preloaded for Visual Studio Added in 1.5.7 Updated Intel Hardware Accelerated Execution Manager (Intel HAXM) to 1.1.1
Components IDE Integration for Android provides the user the opportunity to select their favorite development environment components to install for native Android* development in an Eclipse*, Microsoft* Visual Studio* or Android Studio* IDE. Below is a list of tools that IDE Integration for Android may install. Component Version Android Studio* 1.0.1 Intel INDE Plug-in for Android Studio* 1.2 Android ADT 23.0.2 Android SDK 21 Eclipse 4.2 Android NDK r10d Intel Hardware Accelerated Execution Manager (Intel HAXM) 1.1.1 Apache Ant* 1.9.4 Intel INDE Plug-in for Eclipse* 1.2 Intel INDE Plug-in for Visual Studio* 2012 & 2013 1.2
System Requirements Hardware: Host: System with Intel Core processor and Intel microarchitecture code name Sandy Bridge or later. Device: Intel architecture or ARM architecture Software: JDK 1.7 64-Bit for Android Studio and Eclipse JDK 1.7 32-bit for Visual Studio* Microsoft*.NET 4.5 Microsoft* Windows* 7, Microsoft Windows 8 or Microsoft Windows 8.1 Microsoft* Visual Studio* Community/Professional/Ultimate/Team 2012 or 2013 Contents Depending on the installation options chosen, IDE Integration for Android will create the following directories and/or shortcuts: <install-folder> <install-folder>\android-ndk-r10d <install-folder>\android-sdk-windows <install-folder>\adt <install-folder>\ant <install-folder>\docs <install-folder>\ndk <install-folder>\ndk32 <install-folder>\sdk <install-folder>\android-studio C:\Intel\INDE\IDEintegration by default Native Development Kit Android Software Development Kit Android Development Tools Ant build tool License and Release Notes Shortcut for Native Development Kit 64-bit host/32-bit target Native Development Kit 32-bit host/32-bit target Shortcut for Android Software Development Kit Android Studio General Notes If you receive an "exceeds memory limit" while launching an AVD it is because the AVD's RAM Memory Option exceeds the Intel HAXM Memory Reservation set during install. You can decrease the AVD's RAM Memory option in the AVD configuration tool. Uninstall can be found under the name Intel INDE IDE Integration for Android During Modify, if you select to remove a required component (e.g. NDK) the Setup will ask for the PATH to an already installed component. At the end of the setup you may see an error about uninstalling the component.
IDE Integration for Android has been validated to work with the Android NDK version r10d. Android Studio Environment Notes Two native project activity templates are included to help jump start native code projects. To create a new native project: 1. Create a New Project in Android Studio. Do not use underscores (_) in the Application Name or Company Domain. Doing so will cause runtime errors. 2. Select Android C++ Native Activity Project or Android JNI Activity Project Things to note about the native activity project templates If these projects are absent from the activity selection window of the new project wizard, restart Android Studio. In some instances, Android Studio will not load the 3 rd party wizards upon first launch of the application. The Android JNI Activity Project support creates a simple java based project that calls a native library via the JNI layer. The native library is compiled with the Android NDK and linked into the application The Android C++ Native Activity project demonstrates the NDK s Native Activity project. The project s main entry point is contained within the native library. This type of project is suited towards game development. Eclipse Environment Notes Users may see the following error when launching the Android Virtual Device Manager within Eclipse: PANIC: Missing arch-specific emulator program: /Applications/Intel/INDE/IDEIntegration/ADT/sdk//tools/emulator-x86_64 This issue can be resolved by launching the Android SDK Manager and updating the Android SDK Tools to the latest version. To use Eclipse for x86_64 application targets, these workarounds need to be applied: 1. The ABI chooser dropdown does not contain a x86_64 choice. Manually editing the projects Application.Mk, generally found under JNI project directory, and setting ABI=x86_64 is a workaround for this issue. The ABI
chooser dialog is only visible when an Android project is selected in the Package Explorer, Project Explorer, or Resource Navigator. 2. Run the Android SDK Manager and download the latest Android SDK Tools available. Many issues with pre-installed Android Virtual devices not running can be resolved by using the Android Virtual Device Manager to create a virtual device that is tailored to the user development machine s configuration. Changing from default workspace requires manually setting up the path to the Android NDK. Use Window->Preferences->Android->NDK to manually set the path to the correct location. If you modify your initial installation to point to a different ADT (through the modify option of the installer), you will need to migrate your configuration files (plugins/dropins, workspace settings, etc.) to the new ADT. Creating a new project may also create an appcompat project. This is known to cause build issues. To work around them, either refresh the appcompat project to resolve the errors, or set the minimum API to 14 or greater to avoid creating the appcompat project. More information can be found at http://stackoverflow.com/questions/22256746/eclipse-adt-project-name-appcompat-v 7-being-created-after-creating-every-new. When creating a new x86 Native Android project: 1. Ensure the desired minimum API level is installed using the SDK Manager 2. It is recommended that you set the Run -> Run Configuration -> Target to automatically select the x86 emulator. 3. Select Run Run As Android Application once to run it. Visual Studio Environment Notes If Microsoft Visual Studio Community/Professional/Ultimate/Team 2012 or 2013 is not found then the Visual Studio Development Environment will not be enabled as an install option. If the Visual Studio Plugins were installed, then a new project can be started by following these steps in an open instance of Visual Studio.
1. Select File New Project. 2. Select Installed Visual C++ Android. 3. Select Android JNI Activity Project or Android C++ Native Activity Project An Android JNI Activity Project or Android C++ Native Activity Project can be configured to compile for the ARM platform by doing the following: 1. Right-click the project name in the Solution Explorer, and choose Properties. 2. Click the General tab in the Property Pages window. 3. Choose the desired ARM toolset from the pull-down menu next to the Platform Toolset property. 4. Choose the desired ARM architecture from the pull-down menu next to the Target Architecture property. 5. Click Ok. Visual Studio requires the use of the 32-bit JDK. In some cases, the following error may occur when compiling within Visual Studio: Error: No suitable Java Found. In order to properly use the Android Developer This error is caused by the Android SDK expecting to find a 64-bit JDK on the client machine instead of the required 32-bit JDK. More information on this issue can be found here: http://stackoverflow.com/questions/3052743/android-create-call-fails-in-windows-7-mi ssing-jdk A suitable workaround for this issue is to modify the detection scheme of the Android SDK by editing the %ANDROID_SDK_ROOT%\tools\find_java.bat.. set arch_ext=32 Add this line to find_java.bat rem Check we have a valid Java.exe in the path. The return code will rem be 0 if the command worked or 1 if the exec failed (program not found). for /f "delims=" %%a in ('"%~dps0\find_java%arch_ext%.exe" -s') do set java_exe=%%a if not defined java_exe goto :CheckFailed.. If, while building the Microsoft Visual Studio x86 Native Project or Native Activity project, you encounter this error:
1>AntBuild: 1> Envvar: JAVA_HOME is set to 'C:\Program Files\Java\jdk1.7.0_21' 1> Envvar: JAVA_OPTS is set to '' 1> D:\Android\apache-ant-1.9.0\bin\ant.bat debug 1> The system cannot execute the specified program. Install the x86 version of the Java JDK, and set your JAVA_HOME environment variable to the x86 version. The x86 version is installed into the Program Files or Program Files (x86) directory, depending on the Windows version installed. If you encounter this error: Error <#> error : Could not create the Java Virtual Machine. c:\<ant path>\antbuild <Project Name> Error <#> error : A fatal exception has occurred. Program will exit. c:\<ant path>\antbuild <Project Name> Set the '_JAVA_OPTIONS' environment variable to '-Xmx128M' Legal Information INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information. The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current
characterized errata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or by visiting Intel's Web Site. Intel, the Intel logo, Intel Core, are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.