Introduction
Here’s a stat that puts 2009 smartphone market share in perspective: when Android 1.6 Donut shipped in September 2009, Android’s global market share was under 4%. Symbian held 47%, BlackBerry held 20%, and Apple’s iPhone OS had 15%. Google wasn’t just an underdog — they were barely registering.
Android 1.6 Donut was officially released on September 15, 2009.
Donut didn’t have the headline-grabbing features of Cupcake’s on-screen keyboard. What it did was refine the platform for the real world: CDMA network support (hello, Verizon and Sprint), multiple screen resolutions, and a significantly faster camera. It was the “boring but necessary” update that expanded Android’s addressable market from GSM carriers only to virtually every mobile network on the planet.
If Cupcake made Android feel like a real smartphone OS, Donut made it a phone OS that carriers actually wanted to sell.
Quick Facts
| Item | Value |
|---|---|
| Version | Android 1.6 |
| Codename | Donut |
| API Level | 4 |
| Release Date | September 15, 2009 |
| Linux Kernel | 2.6.29 |
| Initial Device | HTC Tattoo (Europe) / Motorola Devour (CDMA) |
| Previous Version | Android 1.5 Cupcake |
| Next Version | Android 2.0/2.1 Eclair |
What’s New
CDMA Network Support
This is the feature that made Donut strategically critical. Android 1.0 through 1.5 only supported GSM/UMTS networks — meaning no compatibility with Verizon, Sprint, or other CDMA2000 carriers, which represented roughly half the US market at the time.
Donut added full CDMA telephony stack support, enabling the first wave of Verizon Android phones. The Motorola Droid — the phone that would eventually put Android on the map — was in development during the Donut era and benefited directly from this work. Without CDMA support, Android would have been locked out of the US’s largest carrier at the time, and the platform’s trajectory would have looked very different.
Universal Search
Donut introduced the Quick Search Box (QSB), Android’s first system-wide search framework. Instead of opening individual apps to search their content, users could search contacts, apps, music, and the web from a single widget on the home screen.
The Quick Search Box API let third-party apps expose their content to system search — so a recipe app could make its database searchable without the user opening it. This was Android’s search-centric DNA showing through early. It was genuinely useful, if inconsistently implemented by developers.
Text-to-Speech Engine
Donut shipped Pico TTS, a multilingual text-to-speech engine that could read text aloud in English, French, German, Italian, and Spanish. Developers could call TextToSpeech.speak() from any app.
Voice navigation and Google Assistant were still years away, but Donut laid the TTS foundation. The engine was basic — robotic voices, no natural intonation — but it was the first step toward Android’s eventual voice-first capabilities.
Gesture Framework
Donut introduced GestureOverlayView and GestureLibrary, enabling apps to recognize custom touch gestures like circles, arrows, and checkmarks. Developers could record gesture patterns and trigger actions when users drew them on screen.
Gesture Builder, a system app, let users create their own gesture-to-action mappings. In practice, gesture-based navigation never became a mainstream interaction pattern, but the framework enabled early innovation in drawing and accessibility apps.
User Interface Changes
Donut refined but didn’t overhaul Cupcake’s UI:
- Updated Android Market: The Market got a visual refresh with categorized browsing, top-free and top-paid charts, and screenshots for app listings. This was critical — before Donut, the Market was a bare text list with zero discoverability.
- Battery usage screen: A new battery consumption monitor in Settings → About Phone → Battery Use showed which apps and hardware components were draining power. It was basic (no per-app breakdown yet), but users could finally see whether their screen or cell radio was the culprit.
- Camera and Gallery integration: The camera app now had a one-tap shortcut to jump directly into the Gallery, and deleting photos was faster.
- Expanded widget support: Third-party developers could now create widgets (Cupcake only supported system widgets). This opened the floodgates for weather widgets, news tickers, and custom clocks.
Performance Improvements
Donut’s performance work focused on areas users complained about most:
- Camera speed: Shot-to-shot latency dropped significantly. On the HTC Magic, the camera could capture consecutive photos roughly 28% faster than on Cupcake.
- Search indexing: The Quick Search Box pre-indexed contacts, apps, and music, making search results appear almost instantly.
- Kernel upgrade: Moving to Linux kernel 2.6.29 brought improved memory management and better power management for ARM processors.
Security Improvements
Donut’s security story was incremental:
- Expanded permission categories: New permissions for TTS engine access, gesture library storage, and CDMA telephony operations.
- VPN support: L2TP/IPSec VPN capabilities were added, though configuration remained manual and clunky.
The permission model was still install-time-only — apps declared what they wanted and you either accepted or cancelled the install. No granularity, no runtime toggling.
Developer Features
API Level 4 brought a modest but meaningful SDK expansion:
| API | Description |
|---|---|
android.speech.tts |
TextToSpeech class with multi-language Pico TTS engine |
android.gesture |
GestureOverlayView, GestureLibrary, and Gesture classes |
android.app.SearchManager |
Quick Search Box integration via SearchRecentSuggestionsProvider |
| WVGA display support | 800×480 resolution support added (previous max was HVGA 480×320) |
android.telephony.cdma |
CDMA telephony APIs |
The resolution support was quietly important. As Android phones moved from 320×480 to 480×800 and beyond, apps built on Cupcake’s hardcoded layouts broke. Donut’s density-independent pixel (dp) framework got its first real expansion to handle multiple screen sizes.
Google also released the Android SDK with Donut support for Windows, Mac, and Linux, lowering the barrier for hobbyist developers who couldn’t afford Macs (required for iPhone development).
Devices That Shipped With Android 1.6 Donut
- HTC Tattoo — The first Donut device, a budget phone with a 2.8-inch QVGA resistive touchscreen. It was cheap and not particularly good, but it proved Android could hit lower price points.
- Motorola Devour — A Verizon CDMA slider phone with an aluminum body and MOTOBLUR, Motorola’s social-media-focused skin.
- Samsung Moment — Sprint’s first Android phone, a CDMA slider with an AMOLED display and slide-out QWERTY keyboard.
- Sony Ericsson Xperia X10 — Announced during Donut’s lifecycle, though it shipped with 1.6 before an Eclair update.
Several Cupcake devices — including the HTC Magic and original Galaxy i7500 — received over-the-air Donut updates.
No Nexus or Pixel devices yet.
Comparison With Android 1.5 Cupcake
| Android 1.5 Cupcake | Android 1.6 Donut |
|---|---|
| GSM/UMTS only | GSM + CDMA2000 |
| No universal search | Quick Search Box with system-wide indexing |
| No TTS engine | Pico TTS (English, French, German, Italian, Spanish) |
| System widgets only | Third-party widget support |
| 320×480 max resolution | 800×480 (WVGA) support |
| Basic Android Market | Categorized Market with screenshots |
| No VPN support | L2TP/IPSec VPN |
| API Level 3 | API Level 4 |
Donut was an evolutionary update. No single feature was earth-shattering, but together they opened Android to new carriers, new screen sizes, and a more useful app ecosystem.
Legacy and Impact
Donut’s most lasting contribution was CDMA support. Without it, there’s no Verizon Droid, no Sprint Evo 4G, no US carrier diversity that made Android the dominant smartphone platform in America. If Google had waited until Eclair to add CDMA, the 6-month gap could have permanently ceded those carriers to BlackBerry and Windows Mobile.
The Quick Search Box was also quietly influential. It established the pattern — system search as a unified launcher — that Google Search on Android would later perfect. And third-party widgets, enabled here for the first time, turned the Android home screen into the customizable canvas that defined the platform’s identity versus iOS.
Adoption was still slow. The HTC Tattoo and Motorola Devour weren’t blockbusters. But Donut laid the plumbing for the Motorola Droid launch two months later, which ran Eclair and finally broke Android into the mainstream.
End of Support
- Android Market / Google Play: Market access for Donut devices was deprecated around 2011 as Google transitioned to Play Store.
- Google Play Services: Never compatible — Play Services requires Android 2.2+.
- Modern SSL/TLS: Donut’s WebKit and TLS stack cannot negotiate modern HTTPS (TLS 1.2+), meaning essentially zero websites load in the browser.
- Security: No patching infrastructure, no verified boot, no encryption. Purely a historical artifact.
Fun Facts
- Why “Donut”? The name continued Google’s alphabetical dessert theme. Internally, the team debated “Donut” versus “Doughnut” before going with the shorter spelling. The building 44 statue depicted a donut with an Android bugdroid emerging from the center hole.
- Easter egg: Tapping the Android version repeatedly showed a donut graphic — continuing the tradition Cupcake started.
- Development speed: Donut went from initial SDK release to shipping in about 5 months, demonstrating Google’s rapid iteration pace that would define Android’s early years.
- WVGA support hack: Early Donut builds had experimental 800×480 support that some reviewers enabled through build.prop edits before Google officially documented it.
Frequently Asked Questions
What API level is Android 1.6 Donut?
API Level 4.
Is Android 1.6 Donut still supported?
No. Support ended in 2011. No security updates, no Play Store access, no modern web compatibility.
Can Android 1.6 Donut run modern apps?
No. The minimum API level for modern Play Store apps is typically 21 or higher. Donut’s API Level 4 cannot install anything published in the last 12+ years.
Which US carriers got Android with Donut?
Verizon and Sprint got their first Android phones during the Donut era thanks to CDMA support. Previously, only T-Mobile (GSM) and AT&T (GSM, via HTC) carried Android devices.
Did Donut improve battery life?
Modestly. The battery usage screen helped users identify drain sources, and the 2.6.29 kernel included power management improvements, but Android battery life remained a frequent complaint until Project Volta in Lollipop.
Final Thoughts
Donut wasn’t the version you’d show off to convince someone to switch from an iPhone. It didn’t have a flashy UI redesign or a killer new feature for consumers to drool over.
What it had was CDMA support, a search framework, and third-party widgets — the kind of infrastructure upgrades that don’t make tech headlines but determine whether a platform lives or dies. By unlocking Verizon and Sprint, Donut tripled Android’s addressable carrier base in the US. By opening the widget API, it handed developers and OEMs a canvas they’d use to differentiate Android devices for the next decade.
It was a bridge release, and bridges don’t get statues. But without Donut, the Motorola Droid moment — and everything that followed — doesn’t happen.
Related Articles
- Android Version History (2008–Present)
- Android 1.5 Cupcake: Complete Guide
- Android 2.0/2.1 Eclair: Complete Guide
- Android API Level Chart
- Android Codenames Explained
- Evolution of Android User Interface
References
- Official Android 1.6 Platform Highlights (developer.android.com)
- Android Developers Blog: “Android 1.6 SDK is here” (September 2009)
- Android Open Source Project (AOSP) — android-1.6r1 tag
- HTC Tattoo / Motorola Devour product documentation
- CDMA2000 protocol support commit history (AOSP telephony stack)