January 27th, 2011The default ProGuard configuration, proguard.cfg, now ignores the following classes:
· classes that extend Preference
· classes that extend BackupAgentHelper
· Ant lib rules now allow you to override java.encoding, java.source, and java.target properties.
· The default encoding for the javac Ant task is now UTF-8.
· The LogCat view in DDMS now properly displays UTF-8 characters.
· The SDK Manager is more reliable on Windows. For details on the improvements, see the Android Tools Project Site.
· If you enabled snapshots for an AVD, they are automatically captured. The emulator also now restores to the state when it last closed almost instantly.
· Fixed the missing JAR file error that prevented draw9patch from running.
· Fixed the Windows launch scripts hierarchyviewer and ddms to support the new location of adb.
· Known issues with emulator performance: Because the Android emulator must simulate the ARM instruction set architecture on your computer, emulator performance is slow.
December 4th, 2009API related:
· Properly exposes CDMA-related constants in android.telephony.TelephonyManager: DATA_ACTIVITY_DORMANT, PHONE_TYPE_CDMA, NETWORK_TYPE_CDMA, NETWORK_TYPE_EVDO_0, NETWORK_TYPE_EVDO_A, and NETWORK_TYPE_1xRTT.
· Fixes bug so that Bitmap's density is now propagated through Parcelable.
· Fixes NinePatchDrawable to properly scale its reported padding for compatibility mode.
· Fixes TextView to properly compute styled font metrics based on the screen density.
· Updates kernel to 2.6.29, to match kernel on commercially available Android-powered devices.
· Adds new Ant build system with support for Emma instrumentation projects (code coverage).
· Fixes emulator skins to properly emulate d-pad in landscape mode.
· Fixes density rendering in the layout editor in ADT.
September 16th, 2009
· Emulator support for multiple screen sizes/densities, including new skins.
· Android SDK and AVD Manager, a graphical UI to let you manage your SDK and AVD environments more easily. The tool lets you create and manage your Android Virtual Devices and download new SDK packages (such as platform versions and add-ons) into your environment.
· Improved support for test packages in New Project Wizard
July 17th, 2009
· The Android 1.5 system delivered in the SDK (as library and system image) is the development counterpart to the Android 1.5 production system image, deployable to Android-powered handsets starting in May 2009. The system is fully compliant and includes no external libraries. This is the first version of the Android SDK that does not include the Maps external library.
· The Android 1.5 system delivers an updated version of the framework API. As with previous versions, the Android 1.5 API is assigned an integer identifier — 3 — that is stored in the system itself. This identifier, called the "API Level", allows the system to correctly determine whether an application is compatible with the system, prior to installing the application.
· Applications can reference a specific API Level value in their manifest files, to indicate the minimum version of the Android system required to run the application. To reference a minimum API Level, applications can add an android:minSdkVersion attribute in their manifest files. The value of the attribute is an integer corresponding to an API Level identifier. Prior to installing an application, the system then checks the value of android:minSdkVersion and allows the install only if the referenced integer is less than or equal to the API Level integer stored in the system itself.
· When you migrate your application to the new SDK, you will need to choose the platform version against which you will compile your application. In general, you should compile your application against the lowest possible version of the platform that your application can support. After you determine the lowest version, you should ensure that your application's manifest file defines the API Level of the lowest compatible platform version in the android:minSdkVersion attribute.
· After compiling your application, you should make sure to test it on the platform specified in the application's android:minSdkVersion attribute. To ensure forward-compatibility, you should also run the application on platforms using a higher API Level than that used by your application. To run your application against different platform versions in the emulator, you create an AVD for each platform version that you want to test. For more information about AVDs, see Android Virtual Devices. If you are using a physical device for testing, ensure that you know the API Level of the Android platform it runs.
· If you build an application using the Android 1.5 library and your application makes use of any APIs introduced in API Level 3, you must set the android:minSdkVersion attribute in the application's manifest to "3".
Specifically, you define the android:minSdkVersion attribute in a element as a child of in the manifest file. When set, the attribute looks like this:
· < manifest >
· < uses-sdk android:minSdkVersion="3" / >
· < /manifest >
· By setting android:minSdkVersion in this way, you ensure that users will only be able to install your application if their devices are running a compatible version of the Android platform. In turn, this ensures that your application will function properly on their devices. This is especially important if your application uses APIs or system features introduced in Android 1.5.
· If your application uses APIs introduced in Android 1.5 but does not declare < uses-sdk android:minSdkVersion="3" / >, then it will run properly on Android 1.5 devices but not on Android 1.0 devices. In the latter case, the application will crash at runtime when it tries to use the Android 1.5 APIs.
· Conversely, if your application does not use any new APIs introduced in Android 1.5, the application will in most cases function normally on devices running a later version of the platform. However, if you have published the application, you are strongly encouraged to install and test your application on the Android 1.5 system image included in the SDK. This will ensure a smooth transition for users, as they upgrade their devices to the new version of the Android platform.
· Finally, if your application does not use any new APIs introduced since Android 1.1, you can indicate general Android 1.1 compatibility by setting the attribute to "2". If your application does not use any new APIs introduced since Android 1.0, you can remove the attribute or set it to "1". However, before publishing your application, you must make sure to compile your application against the Android library that corresponds to the application's android:minSdkVeresion value.
· Framework for easier background/UI thread interaction
· New SlidingDrawer widget
· New HorizontalScrollview widget
· APIs for creating secure home screen AppWidgets. For information about how to use AppWidgets, see the Developer's Guide AppWidgets documentation. Also see Introducing home screen widgets and the AppWidget framework on the Android Developer's Blog.
· APIs for populating Live Folders with custom content.
· Raw audio recording and playback APIs
· Interactive MIDI playback engine
· Video recording APIs for developers (3GP format)
· Video and photo sharing Intents
· Media search Intent
Input Method framework:
· Input Method Service framework
· Text-prediction engine
· Ability to provide downloadable IMEs to users
Application-defined hardware requirements:
· Applications can now use a new element in their manifest files, to indicate to the Android system what hardware features they require in order to function properly. For example, an application might use the element to specify that it requires a physical keyboard or a particular navigation device, such as a trackball. Prior to installing the application, the Android system checks the attributes defined for the element and allows the installation to continue only if the required hardware is present.
Speech recognition framework:
· Support for using speech recognition libraries via Intent. See RecognizerIntent.
Miscellaneous API additions:
· LocationManager - Applications can get location change updates via Intent
· WebView - Touch start/end/move/cancel DOM event support
· Redesigned Sensor Manager APIs
· GLSurfaceView - convenience framework for creating OpenGL applications
· Broadcast Intent for app update install succeeded - for smoother app upgrade experience
April 28th, 2009
· Multiple versions of the Android platform are included (Android 1.1, Android 1.5). The tools are updated to let you deploy your application on any platform in the SDK, which helps you ensure forward-compitility and, if applicable, backward-compatibility.
· Introduces Android Virtual Devices — (AVD) configurations of options that you run in the emulator to better model actual devices. Each AVD gets its own dedicated storage area, making it much easier to work with multiple emulators that are running concurrently.
· Support for SDK add-ons, which extend the Android SDK to give you access to one or more external Android libraries and/or a customized (but compliant) system image that can run in the emulator.
· The new Eclipse ADT plugin (version 0.9.0) offers new Wizards to let you create projects targetted for specific Android configurations, generate XML resources (such as layouts, animations, and menus), generate alternate layouts, and export and sign your application for publishing.
· Improved JUnit support in ADT
· Easier profiling of performance
· Easier management of localized applications. You can now include or exclude locale resources when building your APK from a single Android project.
· A new tool called "android" replaces the activitycreator script.
September 29th, 2008
· Emulator now saves the user image in <android>/SDK1.0/
· Fixed EsounD-related freezes on Linux.
· Fixed the documentation in -help-audio. '-audio list' doesn't work, one needs to call -help-audio-out and -help-audio-in to get the list of valid audio backends.
· Fixed scrollwheel Dpad emulation in rotated mode. before that, using the scroll-wheel would always generated Dpad Up/Down events, even when in landscape mode.
· Several Obsolete command options were removed.
· Setting the network speed through the console or the -netspeed option will properly modify the connectivity icon on the device.
· Setting the GSM voice registration state to 'roaming' in the console will properly modify the voice icon on the device
· SQLite is now included in the SDK package on all platforms.