Installation and Upgrade Notes

If you've been developing an application using a previous SDK version and you want the application to run on Android-powered mobile devices, you must port the application to the Android 1.0 SDK. Please see Upgrading the SDK for detailed instructions on how to make the transition to this release. Be sure to wipe application user data (emulator option -wipe-data) when running your application on the Android 1.0 SDK emulator.


• SQLite is now included in the SDK package on all platforms. Other

• It is not possible to send MMS messages between emulator instances.

• In some cases, you may encounter problems when using the browser on an emulator started with the command-line option -http-proxy.

©• We regret to inform developers that Android 1.0 will not include support for dot-matrix printers.

• On the OSX platform, if you manually remove the ~/.android directory using rm -rf ~/.android, then try to run the emulator, it crashes. This happens because the emulator fails to create a new .android directory before attempting to create the child SDK1.0 directory. To work around this issue, manually create a new .android directory using mkdir ~/.android, then run the emulator. The emulator creates the SDK1.0 directory and starts normally.

• The final set of Intent patterns honored by Android 1.0 has not yet been fully documented. Documentation will be provided in future releases.

• In ADT Editor, you can add at most ten new resource values at a time, in a given res/values/*.xml, using the form in the Android Resources pane. If you add more than ten, the Android Resources pane will not display the attributes fields for the additional resource entries. To work around this problem, you can close the file in the editor and open it again, or you can edit the resource entries in the XML text mode.

• The emulator's battery-control commands (power <option>) are not working in this release.

0 0

Post a comment