Introduction
The iPhone 4 cost $599 at launch. The Samsung Galaxy S running Android 2.2 Froyo cost $199 on contract — and for the first time, the cheaper phone was faster.
Android 2.2 Froyo was officially released on May 20, 2010.
Froyo was the performance release Android desperately needed. A new Dalvik JIT compiler delivered 2–5× speed improvements in CPU-bound applications. Enterprise features expanded. The browser got a V8 JavaScript engine. And critically, Froyo introduced USB tethering and Wi-Fi hotspot — features carriers grudgingly accepted because Android was now too big to refuse.
Froyo was also the version that brought Android to the masses. The Samsung Galaxy S shipped with 2.2 (after an update from 2.1), sold over 24 million units across its variants, and made Android the best-selling smartphone platform globally by Q4 2010.
Quick Facts
| Item | Value |
|---|---|
| Version | Android 2.2 |
| Codename | Froyo (Frozen Yogurt) |
| API Level | 8 |
| Release Date | May 20, 2010 |
| Linux Kernel | 2.6.32 |
| Initial Device | Nexus One (OTA update) |
| Previous Version | Android 2.0/2.1 Eclair |
| Next Version | Android 2.3 Gingerbread |
What’s New
Dalvik JIT Compiler (2–5× Speed Improvement)
This was the headliner. The Dalvik Virtual Machine — which runs every Android app — switched from a pure interpreter to a Just-In-Time (JIT) compiler. In practical terms, CPU-bound code executed 2–5× faster than on Eclair, and memory usage dropped because the JIT could optimize instruction sequences at runtime.
Google demonstrated this at I/O 2010 with a side-by-side benchmark: a CPU-intensive Linpack benchmark that ran at 6–7 MFLOPS on Eclair hit 37–40 MFLOPS on Froyo on the exact same Nexus One hardware. That’s the kind of performance gain you normally get from new silicon, not a software update.
App launch times, list scrolling, and browser page rendering all improved noticeably. Android finally felt competitive with iPhone OS in responsiveness, and on Snapdragon or Hummingbird chips, sometimes faster.
USB Tethering and Wi-Fi Hotspot
Froyo turned any compatible Android phone into a portable Wi-Fi hotspot. You could share your 3G data connection with up to 8 devices over Wi-Fi, or connect a single device via USB tethering.
Carriers hated this. AT&T, Verizon, and others had been charging $20–30/month for “mobile hotspot” add-ons on BlackBerry and Windows Mobile devices. Froyo baked the feature into AOSP for free, and carriers couldn’t strip it from Nexus devices.
In practice, some carrier-branded phones (especially AT&T) had hotspot functionality disabled or hidden behind carrier billing checks. But the Nexus One and developer community didn’t care — custom ROMs and root access re-enabled it, and carriers eventually gave up fighting.
Cloud-to-Device Messaging (C2DM)
Froyo introduced Google’s first push notification system, a precursor to Google Cloud Messaging and Firebase Cloud Messaging. C2DM allowed servers to push lightweight messages to Android devices without the phone polling constantly — saving battery and delivering near-instant notifications.
It was limited to 1024 bytes per message and required a Google account on the device. Reliability was inconsistent in early builds, but the architecture established Android’s push framework that billions of apps depend on today.
Adobe Flash Player 10.1
Froyo shipped with full Flash Player 10.1 integration in the browser. Google went all-in on Flash as a differentiator — Adobe’s CEO Shyam Gaur appeared on stage at Google I/O 2010 to demo Flash games and video running in the Android browser.
Steve Jobs’ “Thoughts on Flash” essay had been published just weeks earlier. Android having Flash while iPhone didn’t became a prominent marketing point, even if the actual experience remained mediocre. Flash content drained battery, caused browser crashes, and was never optimized for touch interaction. Adobe discontinued mobile Flash two years later.
Apps on SD Card
Froyo allowed apps to be moved to external SD storage, freeing up the painfully limited internal storage on phones like the HTC Desire (512 MB ROM, with only ~150 MB available for apps). Developers had to opt-in by setting android:installLocation="auto" in their manifest, but once enabled, users could shift large apps — games, offline maps — to SD with one tap in Settings → Applications → Manage Applications.
User Interface Changes
- New launcher: The home screen dock got three persistent shortcuts (Phone, App Drawer, Browser) with a slightly redesigned visual style.
- Improved Gallery: The 3D Gallery app introduced in Eclair got smoother animations and better performance on lower-end GPUs.
- Camera enhancements: On-screen zoom controls and LED flash support for video recording.
- Updated settings: The Settings app got a cleaner layout and new sections for tethering, portable hotspot, and apps management.
- Exchange improvements: Calendar sync got better reliability, and auto-discovery simplified Exchange server setup by detecting server settings from just an email address and password.
Performance Improvements
Froyo’s JIT compiler was the star, but it wasn’t the only optimization:
- V8 JavaScript engine: The browser’s WebKit engine upgraded to a V8-based JavaScript runtime, dramatically improving Gmail, Google Docs, and other web app performance. JS benchmarks ran 2–3× faster than Eclair’s browser.
- Memory optimizations: Dalvik’s garbage collector was tuned for lower pause times, reducing jank during scrolling and animations.
- Kernel upgrade: Linux 2.6.32 brought better CPU scheduler, improved power management, and better memory reclaim for low-RAM scenarios.
- Faster cold launches: Apps stored on SD launched slower than internal storage (due to SD I/O latency), but internally stored apps cold-launched faster than on Eclair.
The Samsung Galaxy S (1 GHz Hummingbird, 512 MB RAM) running Froyo was, by real-world benchmarks, one of the first Android phones that felt genuinely fast rather than “fast for Android.”
Security Improvements
- Device policy API expansion: IT admins could now enforce device encryption, minimum password complexity, and maximum failed login attempts (with automatic wipe after threshold).
- SSL improvements: The browser gained support for newer cipher suites and SSL certificate validation warnings.
- Remote device management: Google introduced the Android Device Policy app, enabling enterprise-style management without Exchange servers.
Security was improving incrementally, but Froyo still lacked verified boot, runtime permissions, or file-based encryption. If you lost a Froyo phone, the remote wipe was your only real protection — and that required the device to be connected to the internet.
Developer Features
API Level 8 brought substantial new capabilities:
| API | Description |
|---|---|
android.app.backup | Cloud backup to Google servers for app data and settings |
android.hardware.usb | USB accessory mode — phones could connect to external USB devices |
android.webkit.WebView | V8 JavaScript engine in WebView, HTML5 enhancements |
android.telephony | CDMA signal strength, network type detection improvements |
| OpenGL ES 2.0 | Full OpenGL ES 2.0 support for shader-based 3D graphics |
PackageManager.installLocation | Apps on SD card support |
android.net.wifi.WifiManager | Wi-Fi hotspot management APIs |
OpenGL ES 2.0 support was the sleeper hit. It enabled programmable shaders, normal mapping, and GPU-accelerated visual effects that transformed Android gaming. Games like Riptide GP, Dead Trigger, and Asphalt 6 pushed Android GPUs harder than any previous mobile title, and they did it through Froyo’s ES 2.0 APIs.
Devices That Shipped With Android 2.2 Froyo
- Samsung Galaxy S (i9000) — Samsung’s first flagship Android phone. 4-inch Super AMOLED, 1 GHz Hummingbird, 512 MB RAM. Launched on Eclair, updated to Froyo. Sold 24+ million units across carrier variants (Vibrant, Captivate, Fascinate, Epic 4G).
- HTC Desire HD — 4.3-inch LCD, aluminum unibody, 768 MB RAM. Huge screen for 2010, ran Froyo with HTC Sense.
- HTC EVO 4G (Sprint) — First 4G WiMAX smartphone in the US. 4.3-inch display, front-facing camera, kickstand. Launched on Eclair, received Froyo update.
- Motorola Droid X (Verizon) — 4.3-inch display, 8 MP camera, TI OMAP 3630 processor. Motorola’s answer to the HTC EVO.
- Nexus One — Received Froyo as an OTA update on day one. Remained the reference platform for developers.
Comparison With Android 2.1 Eclair
| Android 2.1 Eclair | Android 2.2 Froyo |
|---|---|
| Dalvik interpreter | Dalvik JIT compiler (2–5× faster) |
| No mobile hotspot | Wi-Fi hotspot + USB tethering |
| No push notifications | Cloud-to-Device Messaging (C2DM) |
| Apps internal only | Apps can move to SD card |
| Flash plugin (limited) | Full Flash 10.1 in browser |
| WebKit JS engine | V8 JavaScript engine |
| No cloud backup | Cloud backup API |
| OpenGL ES 1.x | OpenGL ES 2.0 |
| API Level 5–7 | API Level 8 |
Froyo was Android’s “polish and accelerate” release. It took Eclair’s foundation and made it faster, more capable, and more practical for real-world use. The JIT compiler alone made Froyo feel like a new phone on existing hardware — and the hotspot, SD card apps, and cloud backup made daily use significantly better.
Legacy and Impact
Froyo was the tipping point. It powered the Samsung Galaxy S, which outsold every individual iPhone model in 2010 except the iPhone 4. It ran on the EVO 4G, which gave Sprint a reason to exist in the smartphone era. And it turned the Nexus One from a niche developer device into a genuinely fast, capable daily driver.
The JIT compiler also established a pattern: Google could ship performance improvements through software that felt like hardware upgrades. This became a recurring theme through Project Butter (Jelly Bean), ART (Lollipop), and beyond.
Froyo’s Wi-Fi hotspot and USB tethering were also quietly revolutionary. Carriers lost control of a $20–30/month revenue stream they’d enjoyed for years, and users got a feature they’d been demanding since the first 3G smartphone. The fact that some carriers blocked it only fueled the custom ROM community, which became a defining subculture of the Android world.
By the time Gingerbread arrived in December 2010, Froyo had pushed Android past 33% global smartphone market share — more than double what it had when Eclair launched a year earlier.
End of Support
- Google Play Store: Froyo access to Play Store ended around 2017 when Google enforced minimum API Level 14 (Android 4.0) requirements for app submissions. Existing apps continued working until server-side deprecations cut them off.
- Google Play Services: Play Services 10.0 (2016) was the last major version to support Froyo.
- Android Market: The original Android Market was retired in favor of Play Store on Froyo devices in 2012.
- C2DM shut down: Google Cloud Messaging replaced C2DM in 2012, and C2DM servers were permanently shut down in 2015.
Froyo devices cannot connect to the modern internet in any meaningful way. TLS 1.2+ is required everywhere, and Froyo’s TLS stack is stuck on 1.0.
Fun Facts
- “Froyo” origin: Short for “frozen yogurt.” Google’s dessert naming convention was now fully established as a media expectation. The Building 44 statue was a frozen yogurt cup with Android bugdroid as the spoon.
- Easter egg: The Froyo easter egg showed a frozen yogurt graphic, continuing the tradition. Tapping it launched no interactive mini-game — those would appear later.
- I/O 2010 flash storage demo: At Google I/O 2010, the Froyo announcement included a demo where Vic Gundotra and the Android team plugged a USB flash drive directly into a Motorola Droid running Froyo — the first public demo of USB host mode on a phone.
- Galaxy S marketing: Samsung spent an estimated $100 million marketing the Galaxy S line in 2010, more than any Android OEM had ever spent. The campaign included a massive Times Square launch event and carrier-specific variants (Vibrant, Captivate, Fascinate, Epic 4G) that fragmented the user experience but maximized carrier shelf space.
Frequently Asked Questions
What API level is Android 2.2 Froyo?
API Level 8.
Could Froyo really make old phones faster?
Yes. The Dalvik JIT compiler delivered measurable 2–5× performance improvements on existing hardware. The Nexus One felt significantly faster running Froyo than Eclair, and benchmarks confirmed the difference.
Did Froyo support Wi-Fi hotspot for free?
Technically yes — Froyo included hotspot functionality in AOSP. However, some carrier-branded devices (especially AT&T models) removed or restricted hotspot access, requiring a carrier add-on plan. Nexus and custom ROM users could enable it without carrier restrictions.
Is Android 2.2 Froyo still supported?
No. Google ended all support by 2017. No security updates, no Play Store, and C2DM push notifications are permanently unavailable.
What was the best Froyo phone?
The Samsung Galaxy S i9000. Its 4-inch Super AMOLED display, 1 GHz Hummingbird SoC, and 24 million unit sales made it the definitive Froyo device. The Nexus One was better for developers; the Galaxy S was better for everyone else.
Final Thoughts
Froyo was the moment Android stopped making excuses for its performance. The JIT compiler was an engineering achievement that genuinely improved millions of devices without requiring new hardware. The Wi-Fi hotspot was a power move against carrier upselling. And the Galaxy S proved that an Android phone could outsell any non-iPhone device on the market.
It wasn’t a visual overhaul — the UI still looked like Eclair with minor tweaks. It wasn’t a security revolution — the permission model remained install-time-only and encryption was optional. But Froyo made Android good enough, fast enough, and capable enough that consumers stopped asking “should I get an Android?” and started asking “which Android?”
That shift in consumer perception was more valuable than any single feature.
Related Articles
- Android Version History (2008–Present)
- Android 2.0/2.1 Eclair: Complete Guide
- Android 2.3 Gingerbread: Complete Guide
- Android API Level Chart
- Samsung Galaxy S Retrospective
- The Rise and Fall of Adobe Flash on Mobile
References
- Official Android 2.2 Platform Highlights (developer.android.com)
- Android Developers Blog: “Android 2.2 and developers goodies” (May 2010)
- Google I/O 2010 keynote, Vic Gundotra presentation
- Android Open Source Project (AOSP) — android-2.2_r1 tag
- Dalvik JIT compiler technical documentation
- Samsung Galaxy S (i9000) product specifications
- Gartner Q4 2010 worldwide smartphone sales report