On the Android Developers Blog it is announced that Android SDK 1.1 release 1 is now available to download.
This is follows closely to what has been released as RC33 to current G1 phone users.
Resolved Issues
AlarmClock alert now plays audio/vibe directly, rather than through AlarmManager. AlarmClock alert starts playing audio/vibe in its IntentReceiver, rather than on activity start. These changes should prevent alarms from being blocked by modal dialogs.
Fixes to device sleep.
Single tap no longer opens the in-call dialpad; users now need to touch and drag it.
Fixes a bug causing approximately 1 in 25 outbound messages to freeze up the IMAP connection (to a Gmail based server) when transferred to the Sent folder.
Removes automatic account setup entries that were broken or not testable. Adds minor fixes to a few of the remaining entries. Makes improvements to warning dialogs used for a few special cases.
Changes default mail checking interval to every 15 minutes (instead of defaulting to “never”).
Fixes password-quoting bugs in IMAP, so that users can include special characters in passwords (e.g. spaces).
Fixes various errors in auto and manual account setup
Improves reporting for various connection errors, making it easier for the user to diagnose failed account setups.
Fixes new-mail notifications for POP3 accounts.
Ensures proper auto-checking of accounts marked as “never check”.
Now displays date and time using user preference (e.g. 24 hr vs. AM/PM).
Now shows cc: in message view.
Improves recovery from POP3 connection failures.
POP3 parser rules loosened, so the application can work with non-compliant email servers.
Removes green CALL button as a shortcut for “add a new call”.
New Features
Maps: Adds details and reviews when a user does a search on Maps and clicks on a business to view it’s details.
Dialer: In-call screen timeout default is now longer when using the speakerphone.
Dialer: Adds a “Show dialpad” / “Hide dialpad” item to the in-call menu, to make it easier to discover the DTMF dialpad.
This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.
No comments yet.