MOTODEV Studio for Android v1.0 Release Notes

Microsoft Windows

• Microsoft Windows XP Professional Version 2002 with Service Pack 3
• Java™ Runtime Environment (JRE) 6.0 Update 13
• Intel® Core™ 2 Duo CPU, 2.33 GHz
• 2 GB RAM
• Over 1.5 GB of free disk space (needed to install both MOTODEV Studio for Android and the Android™ SDK and plug-ins from Google; MOTODEV Studio itself only needs 150 MB)

Mac OS X

• Mac OS X version 10.5.7
• Java 2 Runtime Environment, Standard Edition 5.0 32-bit
• Intel Core 2 Duo CPU, 2.4 GHz
• 4 GB RAM
• Over 1.5 GB of free disk space (needed to install both MOTODEV Studio for Android and the Android SDK and plug-ins from Google; MOTODEV Studio itself only needs 150 MB)

Ubuntu Linux

• Ubuntu Linux version 9.0.4
• GNOME version 2.26.1
• Java™ Runtime Environment (JRE) 6.0 Update 14 32-bit
• Intel Core 2 Duo CPU, 2.4 GHz
• 2 GB RAM
• Over 1.5 GB of free disk space (needed to install both MOTODEV Studio for Android and the Android SDK and plug-ins from Google; MOTODEV Studio itself only needs 150 MB)

Fedora Linux

• Fedora Linux version 11
• KDE version 4.2.2
• Java™ Runtime Environment (JRE) 6.0 Update 14 32-bit
• Intel Core 2 Duo CPU, 2.4 GHz
• 2 GB RAM
• Over 1.5 GB of free disk space (needed to install both MOTODEV Studio for Android and the Android SDK and plug-ins from Google; MOTODEV Studio itself only needs 150 MB)

Features

• Based on the following technologies:
  • Eclipse Galileo 3.5.0
  • Eclipse Java Development Tools (JDT) 3.5.0
  • Google Android Development Toolkit (ADT) 0.9.3
• Uses an existing install of, or guides you through the download and install of, the Google “Donut” SDK 1.6, which includes:
  
  • Android emulator with system image
  • Interface and JAR files
  • Documentation
  • Google USB drivers for Windows
  • Samples
• Supports app development for the Android 1.5 and Android 1.6 platforms
• Single-click installer
• Create four essential classes simply and easily: Broadcast Receiver, Content Provider, Service, and Activity (see File > New)
• Easily create projects based upon Android samples
• Using "snippets," add often-used code from templates for more stable and better performing applications
• Create and import certificates to sign applications
• Easily create and manage AVDs (Android Virtual Devices), and set AVD startup options using the Device Management view
• Emulator is integrated into the IDE
• Debug and run applications on connected Motorola handsets
• Easily launch an ADB shell or Emulator Console
• Create customized launch configurations, accessible through Run As > Run Configurations.
• Includes context-sensitive help and integrated documentation
• MOTODEV Studio perspective displays the most common development views
• View and edit SQLite databases on developer handsets and emulated devices using the MOTODEV Database perspective
• Easily create and manage localized strings files using the Localization Files Editor
• The RSS Feeds view includes feeds from Motorola related to Android app development and marketing
• The MOTODEV Web Resources view contains links to MOTODEV Studio release notes and other helpful web resources
   

MOTODEV Studio for Android Installation and Update Issues

• The MOTODEV Studio for Android installer determines which (if any) JVM is installed on your computer. If it finds more than one, it displays to the user only the first one found, which may or may not be the one that is actually used by MOTODEV Studio.
• MOTODEV Studio for Android is built on top of a 32-bit version of Eclipse; it does not run on a 64-bit JVM. If your default JVM is 64-bit, you will need to install a 32-bit JVM and use that when launching MOTODEV Studio for Android.
• On Linux hosts, after installation the desktop shortcut may appear with the wrong icon. This happens because the shortcut was created without execute permission. Either grant the shortcut execute permission, or try to launch MOTODEV Studio for Android using the shortcut and, if asked, indicate that you trust the shortcut.
• When you are on a network that requires proxy authentication, MOTODEV Studio updates will only occur if the proxy information (including username and password) are manually set for both HTTP and HTTPS connections (in Preferences, under General > Network Connections). This also affects the download and install of the Android SDK during the installation process. If during installation you are asked if you want to change the connection preferences, do so. Change the active provider to "Manual" and provide host, port, user, and password values for both the HTTP and HTTPS schemes.
• MOTODEV Studio doesn't always prompt you to restart after an update (Help > Check for Updates). After any such update you should always restart MOTODEV Studio, whether or not you are prompted to do so.

Project Creation Issues

• When creating a new project using Android Project Using Studio for Android, the AndroidManifest.xml file sets the application and activity labels to "APPLICATION_NAME". They should be "@string/app_name". Edit your newly created project's manifest file and change the application and activity labels to a value more appropriate for your application. Typically you will change them to "@string/app_name" and then specify the text of the label in your project's res/values/strings.xml file.
• When creating a new Android project, if you clear the Use default location option you will be unable to specify a project location within your workspace. To create a project within the current workspace leave Use default location selected. Otherwise, specify a location outside of the current workspace.
• During project creation, if you specify a path in which the parent folder doesn’t exist, an error is displayed. For example, if you specify the path C:\temp\projects\myproject and the projects directory doesn’t exist, you will encounter this problem. Ensure that the project's parent folder exists before creating a project in it.
• In the New Project wizard, as you edit the Project Name field the Project Location field is automatically generated. Sometimes, this field is not generated as expected.

Localization Files Editor Issues

• If you move the mouse out of the comment window area while editing a comment, the comment window simply disappears.
• When “Highlight Changes” is enabled, cells that have only had their comments changed are not highlighted.
• Undo/redo does not work for changes to comments.
• The Localization Files Editor does not notice when a file being edited is changed using an editor outside of MOTODEV Studio for Android (such as Notepad). It does notice when changes are made from another editor, such as a text editor or XML editor, within MOTODEV Studio.

Issues while Installing, Running, or Debugging Apps

• When working with the 1.6 SDK, sometimes an error message appears when installing a package:

  Error executing the operation. Execution results: - exec '/system/bin/sh' failed: Bad address (14)

  If you try again, it should work.
• When running applications on a version 1.6 target, sometimes the following error occurs:

  Waiting 3 seconds before next attempt.
  ActivityManager: Error: Activityclass {XXX} does not exist.

  If you get this error, clean the project and re-run your application.
• If there is a handset and one or more AVDs online when you launch or debug an application using MOTODEV Studio for Android, you will be presented with the standard ADT device chooser dialog asking you to select a target device. Simply select the desired target again.
• At this time, you cannot reliably debug on a remote device through DeviceAnywhere Studio. Motorola is actively working on this issue with Mobile Complete and hopes to have a resolution soon.
• If you use a method such as waitForDebugger() from the Android SDK's Debug class, when you run that application a new debug configuration will be automatically created and a debug session will start using this configuration. This new configuration will be listed among the other debug configurations, and can be used for subsequent debugging sessions.

Emulator Issues

• Within MOTODEV Studio, emulator device names are case-sensitive. If you start an emulator from the command line and the AVD name you supply doesn’t exactly match the device name shown in MOTODEV Studio, MOTODEV Studio will not recognize the running instance.
• The Other field in the Emulator Properties Startup Options is not validated in any way. In particular, if you supply the –avd option and specify an emulator instance other than the one that is to be launched, when you launch the emulator it will never complete the startup process. Ensure that any options you enter into this field are correct, and do not use the –avd option.
• On occasion the Android emulator stalls during start up. Note that when launching the emulator for the first time the launch can take quite a while. If it takes more than ten minutes or so, however, the emulator has likely stalled. Stop the emulator and try again.
• If the emulator is not running when you launch or debug an application targeted to the emulator, MOTODEV Studio starts the emulator and deploys the application to it. On rare occasions, however, the emulator isn’t started and nothing seems to happen. This occurs when the emulator process is unable to connect to the ADB port. Although the emulator process is running, ADT does not recognize it and therefore neither does MOTODEV Studio for Android. Stop the emulator and try again.
• If you provide a timeout value that is too large, you'll see an error message that indicates that the value must be a positive integer. Provide a smaller timeout value.
• While the emulator is in use, your computer's CPU usage can reach a high value.
• The ADB shell console feature does not yet support commands such as CTRL-C to interrupt process execution. If the process that is executing depends on a command like this to stop, it cannot be stopped unless the ADB shell section is killed by stopping the emulator or disconnecting the phone.
• On rare occasions, when working with a single emulator instance and multiple ADB shells, an exception may be thrown when the emulator is stopped: “request rejected: device not found java.io.IOException: device (emulator-5556) request rejected: device not found”.
• While quickly alternating between multiple emulators, you may see the following message: “Device rejected command: cannot bind socket java.io.IOException”.
• Sometimes the following error message is shown in the logcat view when stopping an emulator instance: “Stop request rejected: device not found”. This may occur because there are pending commands to be executed on the emulator, and the emulator was stopped before they could be executed.

MOTODEV Database Explorer Issues

• The menu displayed when right-clicking the database node contains some options that are only applicable for the Data Tools perspective: they don’t work when using the MOTODEV Database perspective, and can create problems if used. The options that should be avoided are: Rename, Duplicate, and Save Offline.
• If you close the MOTODEV Database Explorer view while you have an open table, the message “widget is disposed” may be displayed.
• On some occasions with 1.6 targets, the emulator crashes while loading databases.
• The MOTODEV Database Explorer does not refresh itself automatically: you must click Refresh to re-synchronize this view with the file system.
• On rare occasions, while working with a connected a handset, a “widget disposed” message is displayed while trying to save an edited value.
• If a table has a data type not supported by the table editor, an exception will be raised when the editor opens the table. For instance, this problem occurs with the IMAGES and VIDEOS tables from the com.android.providers.media application.
• BLOB fields are displayed as text.

Other Issues

• In our testing with the 1.6 SDK we noticed a lot of instability with 1.6 targets. Using the 1.6 SDK with 1.5 targets seems to reduce this instability.
• On Microsoft Windows, MOTODEV Studio for Android has a MOTODEV menu item and a corresponding toolbar button that allow you to launch DeviceAnywhere Studio. For this release, you cannot reliably interact with a remote device through DeviceAnywhere while MOTODEV Studio for Android is running. Before launching DeviceAnywhere Studio (from your host operating system), ensure that neither MOTODEV Studio for Android nor the adb daemon is running.
• If you run the Activity, Service, Broadcast Receiver, or Content Provider wizards while Manifest.xml is opened, a warning is shown ("No grammar constraints (DTD or XML schema) detected for the document") and all file content is highlighted. Close and reopen the manifest file to resolve this issue.
• When collecting log files (Help > Collect Log Files), if you specify a folder to which you do not have write access the error message that is displayed is somewhat misleading. It displays “Cannot create zip file”—which is technically true—but the solution to the problem is to fix the folder permissions or choose a folder for which you do have write access.
• MOTODEV Studio for Android includes a mechanism that by default is used to store all passwords (such as your MOTODEV password). On Linux, if you want to improve the security of your passwords, disable this mechanism: from the MOTODEV Studio Preferences dialog select General > Security > Secure Storage. In the Master password providers section, deselect the Java Password Provider and select the UI Prompt provider (if it is not already selected).
• On Ubuntu hosts, the preview of the last snippet of the GPS group does not appear. A blank area appears instead.
• When on a network that requires proxy authentication, you may need to supply your username and password for each connection being opened, even if you have specified them on the preferences page. The RSS/Atom Feed view, for instance, can require you to enter your username and password up to four times in a row when the view is first opened (or when MOTODEV Studio is started with this view visible).
• If a web page contains errors, for each error the Eclipse internal editor may cause an error dialog to appear asking if you want to debug the page. If the errors do not prevent the page from being rendered, you can answer “no” to each and the page will appear normally. If there are multiple errors, this can be somewhat annoying, however. Instead, you may want to alter your MOTODEV Studio preferences so that it renders such pages using an external web browser. 

ECCN 5D002.a: In accordance with United States Export Administration Regulations (EAR), and specifically the Commerce Control List (CCL), this item has been classified 5D002.a. Export or re-export of this commodity and compliance with the U.S. Export Administration Regulations is ultimately the responsibility of the exporter. For more detailed information related to export or re-export of this item, please consult the EAR at http://www.access.gpo.gov/bis/ear/ear_data.html.

Copyright © 2009, Motorola, Inc. All rights reserved.