Read and accept the license agreement, then click Next.
@@ -330,18 +334,55 @@ your project and make any necessary changes to your code.
in Eclipse, changing the "build target" to one using the Android 1.5 platform,
and see where the ADT identifies errors in your code.
+
+Future-proof your apps
+
There have been several API additions made for this release, but there have been
very few actual API changes. Only a couple (relatively unused) elements
have been removed and a few have been deprecated, so your applications written with the
-Android 1.1 system library should work just fine.
-Your application will be at highest risk of breakage if it uses Android APIs
-that are not available in the public API documentation
-or if it explicitly depends on system bugs. For information
-about changes made to Android 1.5, refer to the following documents:
+Android 1.1 system library should work just fine. However,
+your application is more likely to encounter problems on Android 1.5
+if it performs any of the following:
+
+
+ - Uses internal APIs. That is, APIs that are not officially supported
+ and not available in the reference documentation. Any un-official APIs are always subject
+ to change (which is why they're un-official) and some have indeed changed.
+
+ - Directly manipulates system settings. There are some settings (such as
+ GPS, data roaming, bluetooth and others) that used to be writable by
+ applications but have been changed so that they can only be explicitly modified by the user
+ through the system settings. Refer to {@link android.provider.Settings.Secure}
+ to see which settings are now secured and cannot be directly changed by your application.
+
+ - Uses View hierarchies that are unreasonably deep (more than 10 or so levels) or
+ broad (more than 30 total). View hierarchies this big have always been troublesome, but
+ Android 1.5 is much more efficient at exposing this and your application may crash.
+
+ - Makes assumptions about the available hardware. With new support for soft keyboards,
+ not all devices will have full QWERTY keyboards on the hardware. So if your application
+ listens for special keypress events that only occur on a keypad, then your application
+ should degrade gracefully when there is no keyboard available.
+
+ - Performs its own layout orientation changes based on the acceletometer (or via other
+ sensors). Some devices running Android 1.5 will automatically rotate the orientation
+ (and all devices have the option to turn on auto-rotation), so if your application also
+ attempts to rotate the orientation, it can result in strange behavior. In addition, if your
+ application uses the accelerometer to detect shaking and you do not want to rotate the
+ orientation, then you should lock the current orientation with
+ android:screenOrientation.
+
+
+
+Please read our blog post on Future-Proofing
+Your Apps for more information on the issues mentioned above.
+
+For information
+about other changes made to Android 1.5, refer to the following documents: