Release Notes

For the latest known issues, please ensure that you're viewing this page at: http://code.google.com/android/RELEASENOTES.html.

Version m5-rc15

Installation Notes

If you've already been developing using an m3 or earlier m5 version of the Android SDK, please see Upgrading the SDK for detailed instructions on how to make the transition to m5.

If you're installing the Android SDK for the first time, please see the instructions on Installing the SDK.

New Features

m5-rc15 does not introduce any new features.

Resolved Issues

• 1012640: Incorrect handling of BMP images.

Known Issues

Unless otherwise noted, Known Issues from m5-rc14 also apply to m5-rc15.

Version m5-rc14

Installation Notes

If you've already been developing using an m3 version of the Android SDK, please see Upgrading the SDK for detailed instructions on how to make the transition to m5-rc14.

If you're installing the Android SDK for the first time, please see the instructions on Installing the SDK.

New Features

Changes to the Android APIs introduced in m5-rc14 are summarized in this document.

In addition to changes in the Android APIs, m5-rc14 also introduces changes to the Android Developer Tools:

emulator

• The Android emulator now support SD card images up to 128 GB in size. The previous limit was 2 GB.

DDMS

• Support for managing multiple devices has been integrated into DDMS. This should make it easier to debug applications that are run on multiple device scenarios.

ADT

• ADT now attempts to connect a debugger to any application that shows up in the wait-for-debugger state, even if this application was not launched from Eclipse.
  
  The connection is actually established only if there exists a project in the Eclipse workspace that contains an AndroidManifest.xml declaring a package matching the name of the process. To force this connection from your code, use Debug.waitForDebugger(). Activities declaring that they require their own process through the "process" attribute with a value like ":someProcess" will be recognized and a debugger will be connected accordingly. This should make it easier to debug intent receivers, services, providers, and other activities not launched from the standard app launcher.
  
  
• ADT has launch modes for device target selection. Automatic mode will: 1) launch an emulator if no device is present, 2) automatically target the device if only one is connected, and 3) prompt the user if 2 or more are connected. Manual mode will always prompt the user.
  
  
• ADT also contains the same support for multiple devices that has been introduced into DDMS.

AIDL

• AIDL files that import and reuse types is now supported by activityCreator.py and ADT.

traceview

• The traceview tool is now included in the SDK.

Resolved Issues

The following Known Issues from m3-rc20 have been resolved:

• 917572: The activityCreator created incorrect IntelliJ scripts
• 917465: Unanswered incoming calls placed from the emulator console will result in an unfinished call UI if you press the call back button
• 917247: dmtracedump and traceview tools are not available in the SDK
• 912168: Extremely rapid or prolonged scrolling in the Maps application or MapsView will result in application errors
• 905852: adb emits warnings about deprecated API use on Mac OS X 10.5
• 905242: The Run dialog sometimes failed to show the Android Launcher
• 901122: The focus ring in the browser is sometimes incorrect
• 896274: On Windows, the emulator sometimes starts off-screen
• 778432: Icons for newly installed applications do not display

Known Issues

The following are known issues in m5-rc14:

• 1017312: The emulator window size has been reduced slightly, to allow it to be fully visible on smaller screens. This causes a slight clipping of the HVGA emulator skin but does not affect its function.
• 1021777: Setting a power requirement in a Criteria object passed to getBestProvider() will result in a value not being returned.
• 1025850: Emulator failing to launch from the Eclipse plugin due to wrong custom command line parameters do not report the error anywhere and silently fails.

Unless otherwise noted, Known Issues from m3-rc20a also apply to m5-rc14.

Version m3-rc37a

Version m3-rc37a and ADT 0.3.3 were released on December 14, 2007.

Installation Notes

ADT Plugin Upgrade Requires Re-Installation of Plugin

Because of changes in the ADT Plugin and other tools, you will need to uninstall your existing ADT Plugin and then re-install the new version (ADT 0.3.3). For complete information, see Upgrading the SDK.

New Features

Android Debug Bridge (ADB)

• Now supports multiple emulators on one host computer. Please note that you need to use the -data option when starting secondary emulators, to allow those instances to save their data across sessions. Also, DDMS does not yet support debugging on multiple emulators yet.

ADT Plugin for Eclipse

• Adds editor capabilities for working with Android manifest files, such as syntax highlighting and autocompletion. The editor capabilities require the Web Tools WST plugin for Eclipse, which is included in most Eclipse packages. Not having WST does not prevent the ADT plugin from working. If necessary, you can download and install WST from the Web Tools Project downloads page. To update directly from an Eclipse installation, you can add a remote update site with this URL: http://download.eclipse.org/webtools/updates . Note that installing WST on Eclipse 3.4 will require installing other packages, as detailed on the WTP downloads page.
• Now retries to launch the app on the emulator if it fails due to timing issues when the emulator is booting.
• Adds support for loading custom skins from the <SDK>/lib/images/skins/ directory. The Skin dropdown in the Emulator tab is now built from the content of the skins/ directory in order to support developer-made skins.
• Adds an Emulator control panel. This is a UI on top of the emulator console that allows you to change the state of the network and gsm connection, and to initiate incoming voice call. (This is also present in standalone DDMS.)
• Adds support for referenced projects. Android projects will add to the apk package any code from referenced projects.
• Eclipse console now warns if an .apk that is pushed to the device declares the same package as another already installed package.
• Java classes generated by the Eclipse plugin are now marked as derived automatically, so that Team plugins do not consider them as regular source.

Emulator Console

• Now provides support for emulating inbound SMS messages. The ADT plugin and DDMS provide integrated access to this capability. For more information about how to emulate inbound SMS from the console, see SMS Emulation.

Emulator

• The default emulator skin has been changed to HVGA-P from QVGA-L. For information about emulator skins and how to load a specific skin when starting the emulator, see Using Emulator Skins.

Resolved Issues

907947

adb -version now returns a version number.

917462

Audio on Windows is fixed and is no longer 'choppy'.

Removed Manifest File Locking on Mac OS X

ADT plugin now uses a custom java editor for R.java/Manifest.java, to make those files non-editable. This is to replace the current locking mechanism which causes issues on Mac OS (preventing projects from being deleted). Note that your project must recompile at least once for the lock to be removed from the files.

The following known issues noted in m3-rc20 are now fixed:

• 890937: Emulator does not support non-qwerty keyboards.
• 894618: adb shell may fail to connect when used the first time.
• 896274: On Windows, the emulator window may start off-screen.
• 899949: The emulator may fail to start with -useaudio on some environments.
• 912619: Emulator console listens on non-local ports 5554-5584.
• 917399: On Windows, running multiple emulator consoles can result in unexpected behavior when simulating incoming telephone calls.

Known Issues

Unless otherwise noted, Known Issues from m3-rc22a also apply to m3-rc37a.

Version m3-rc22a

Version m3-rc22a and ADT 0.3.1 were released on November 16, 2007.

Resolved Issues

920067

The New Android Project wizard provided by ADT 0.3.1 now properly displays error messages when used with Eclipse 3.2 on Windows.

920045

The AndroidManifest.xml files generated by ADT 0.3.1 now include the XML element required for displaying the associated app in the "Applications" menu. If you have applications created with ADT 0.3.0, simply ensure that your AndroidManifest.xml file contains the following highlighted line:

...
    <intent-filter>
        <action android:value="android.intent.action.MAIN" />
        <category android:value="android.intent.category.LAUNCHER" />
    </intent-filter>
...

920098

ADT 0.3.1 is now compatible with Eclipse 3.4.

920282

Fixes a NullPointerException that is thrown in certain situations with the DDMS perspective in Eclipse.

918637

Address a keyboard lock-up issue when using adb on Mac OS X 10.4 and 10.5.

Known Issues

Unless otherwise noted, known issues from m3-rc20a also apply to m3-rc22a.

Version m3-rc20a

Known Issues

The following are known issues in m3-rc20a:

778432 - Resolved in m5

In certain circumstances, icons for newly installed applications do not display as expected.

890937 - Resolved in m3-rc37a

The emulator currently does not support non-QWERTY keyboards.

894618 - Resolved in m3-rc37a

The adb shell command may fail to connect when used for the first time.

896274 - Resolved in m5

On Windows, the emulator screen will sometimes show up off-screen when it is started. The workaround for this is to right-click on the emulator taskbar entry, select Move, and move the window using keyboard arrow keys

899949 - Resolved in m3-rc37a

The emulator may fail to start when using the -useaudio in some environments

901122 - Resolved in m5

The focus ring shown in the browser may sometimes not properly wrap links.

905242 - Resolved in m5

On Mac OS X 10.5, the Eclipse plugin's Run Dialog may sometimes fail to show the option to select the Android Launcher.

905852 - Resolved in m5

On Mac OS X 10.5, adb will emit warnings about deprecated API use when first used.

912168 - Resolved in m5

extremely rapid or prolonged scrolling in the Maps application or in a MapView will result in application errors.

912619 - Resolved in m3-rc37a

The emulator console listens for connections on ports 5554-5587. Future versions will only accept connections from localhost. It is recommend that you use a firewall to block external connections to those ports on your development machine.

912849

On Mac OS X 10.4, the emulator may hang if started in the background (i.e. ./emulator &).

914692

On Mac OS X 10.5, the emulator will emit warnings about deprecated API use when started from the command line.

917247 - Resolved in m5

The dmtracedump and traceview tools are not available in the SDK.

917399 - Resolved in m3-rc37a

On Windows, running multiple emulator consoles can result in unexpected behavior when simulating incoming telephone calls.

917465 - Resolved in m5

Unanswered incoming calls placed from the emulator console, will result in an unfinished call UI if you press the call back button.

917572 - Resolved in m5

Using activityCreator with the --ide intellij option creates IntelliJ scripts with incorrect documentation location specified. To correct, change value for the <JAVADOC> element in the generated .ipr file from file://.../docs/framework to file://.../docs/reference.

917579

On Ubuntu 7.10 (Gusty), the Eclipse package installed by the apt-get install eclipse command uses java-gcj by default. This configuration is not compatible with the Android Eclipse plugin (ADT) and will result in "Class not found" errors whenever you access an ADT feature.

The resolution for this issue is to install a Sun JDK

sudo update-java-alternatives --jre java-1.5.0-sun

and then configure Eclipse to use it by exporting the following environment variable:

export JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun

or by adding following to your .eclipse/eclipserc file:

JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun