What Is New in Android 2.2
Android 2.2 Froyo brought significant speed improvements and a suite of new developer APIs. This release focused on performance, enterprise features, and cloud-to-device messaging.
| Category | Key Changes |
|---|---|
| Performance | JIT compilation, V8 JavaScript engine, faster performance |
| Enterprise | Device policy management, Exchange support, remote wipe |
| APIs | Cloud-to-device messaging, USB tethering, Android Cloud to Device Messaging |
| Media | Flash support, high-DPI screens, camera improvements |
| Browser | JavaScript V8 engine, faster page loading |
How did Android 2.2 improve performance?
The Dalvik VM got a massive speed boost from a new Just-In-Time (JIT) compiler. This made everything from app startup to complex computations feel noticeably faster.
The browser integrated the V8 JavaScript engine, which dramatically improved the performance of web applications. In practice, this meant web apps like Gmail ran nearly as fast as native applications.
What new developer APIs were introduced?
Cloud to Device Messaging (C2DM) was a standout addition, providing a framework for servers to send lightweight messages to apps. This was the precursor to Google Cloud Messaging and allowed for better push notification systems.
New APIs also enabled apps to request USB tethering and Wi-Fi hotspot functionality. Developers gained more control over the camera with new APIs for managing focus, zoom, and flash modes.
What enterprise features were added?
Android finally became a serious contender for business use. The Android Device Administration API allowed developers to create apps that could enforce password policies, remotely wipe devices, and lock handsets.
Built-in support for Microsoft Exchange calendars and contacts was a big deal for corporate adoption. This meant devices could sync natively with corporate servers without third-party apps.
How did media handling change?
Adobe Flash Player support was a major selling point, allowing browsers to play Flash content. This mattered because it closed a perceived gap between mobile and desktop browsing experiences at the time.
The framework added better support for high-DPI screens, future-proofing apps for upcoming devices. Camera apps could now use new APIs to control picture quality and capture parameters more precisely.
FAQ
Was the JIT compiler enabled for all apps automatically?
Yes, the JIT was a runtime feature
of the Dalvik VM. All existing and new apps benefited from it immediately without requiring recompilation or
target SDK changes.
What happened to C2DM after Android 2.2?
Cloud to Device Messaging was eventually deprecated
and replaced by Google Cloud Messaging (GCM), which itself was later replaced by Firebase Cloud Messaging (FCM).
Did USB tethering require root access?
No, one of the key advances was that apps could now
programmatically enable USB tethering through new APIs without requiring root privileges on the device.
Could any app use the Device Administration API?
Yes, but the user had to explicitly enable
the device admin privileges for that app through a system dialog, giving them full control over what policies
were enforced.
Was Flash support available on all Android 2.2 devices?
No, Flash required hardware
acceleration support from the device manufacturer. While many devices supported it, some lower-end hardware
couldn't run the Flash plugin effectively.