Last checked and updated on 10 Jun 2026
What Is New in Android 1.1
Android 1.1 was a minor but practical update focused on refining the user experience and adding a few key features that users and developers were asking for. It built upon the initial 1.0 release by smoothing out rough edges. This update showed Google's commitment to iterating quickly based on early feedback.
| Category | Key Changes |
|---|---|
| New Features | Added details view for maps, longer in-call screen timeout, ability to save MMS attachments. |
| API Changes | New APIs for marquee in layouts, showing/hiding the IME (keyboard). |
| Bug Fixes & Improvements | Resolved issues with email notifications, calendar sync, and Gmail attachments. |
What user experience improvements were made?
The most noticeable changes were quality-of-life fixes for day-to-day phone use. The in-call screen would now stay on longer, preventing it from going dark while you were checking voicemail. You could finally save picture and video attachments from MMS messages directly to the device. For early adopters, these were huge usability wins that made the phone feel more complete.
Which new developer APIs were introduced?
Android 1.1 added a couple of handy APIs for app interfaces. The Marquee class allowed for scrolling text in a layout, useful for tickers or news headlines. More importantly, it introduced methods to programmatically show and hide the Input Method Editor (IME), giving developers control over the soft keyboard. This was a basic but crucial step for crafting better text input experiences.
How did Android 1.1 improve core apps?
Google's first-party apps received important stability patches. The update fixed a bug where the phone wouldn't always vibrate or ring for new email notifications. It also resolved problems with calendar events not syncing correctly and added support for viewing attachments in Gmail. These fixes were critical for making the core Android suite reliable for business users.
Was the Maps application updated?
Yes, the Maps application gained a highly requested feature: a details view. This allowed users to get more information about a searched location beyond just a pin on the map. While basic by today's standards, it was a significant step forward in making Android a capable navigation and local search device right out of the box.
FAQ
Does Android 1.1 have any breaking API changes?
No, it was a minor point release. The new APIs were additive, so apps built for 1.0 continued to work without modification on 1.1. This was a relief for early developers.
What was the most important bug fix in 1.1?
Fixing the email notification bug was huge. Before the update, users could miss important emails because the phone wouldn't alert them. This fix directly improved the reliability of the device for communication.
Why was the marquee API significant?
It provided a built-in, standardized way to create scrolling text. Before this, developers had to implement their own solutions, which could be inconsistent and inefficient. This API laid the groundwork for a common UI pattern.
Did Android 1.1 improve performance?
While not explicitly called out in release notes, numerous under-the-hood bug fixes and optimizations, especially in core apps like Calendar and Gmail, would have contributed to a smoother and more performant overall experience.
How did the IME API change app development?
Giving developers control over the soft keyboard was a game-changer for apps with forms or text fields. They could now dismiss the keyboard when it wasn't needed, creating a less intrusive and more user-friendly interface.