X
Business

Google revs up Android with 1.1 SDK, but developers might want to hold off installing it

Google released the Android 1.1 SDK release 1 yesterday, hot on the heels of the RC33 update that has been rolling out to US T-Mobile G1 owners over the past few days. However, I recommend that developers not install this new SDK right away. The reason is that programs you build with it may not be compatible with phones running the Android 1.0 system image, even if you don't use any of the new features...
Written by Ed Burnette, Contributor
androidsmallimage.jpg
Google released the Android 1.1 SDK release 1 yesterday, hot on the heels of the RC33 update that has been rolling out to US T-Mobile G1 owners over the past few days. Interestingly, the update is not available for the Google-branded Android Developer Phone 1 yet, but according to Google's Dan Morrill, that is "coming soon".

I recommend that developers not install this new SDK right away. The reason is that programs you build with it may not be compatible with phones running the Android 1.0 system image, even if you don't use any of the new features.

Once you are sure that all your users have the 1.1 system image, then follow these steps:

  1. Upgrade your SDK to 1.1_r1 (or later).
  2. Change your Android.manifest file to specify minSdkVersion="2".
  3. Rebuild your project.
  4. Test on a phone with the 1.1 image (such as a G1 with the RC33 update).

By changing the minSdkVersion number you will prevent your program from accidentally being installed on an old image where it may not work. It's better that it just not install than run the risk of failing in unexpected ways.

The API changes are minor and it's very unlikely you will need them. Even Google suggests:

If you are sure your application is not using Android 1.1 APIs and has no need to use them, you might find it easier to keep working in the Android 1.0 SDK, rather than migrating to the Android 1.1 SDK and having to do additional testing.

Resources:

Editorial standards