Android 2.0 source released, already ported to the G1
While Android 2.0 has been floating around on Motorola DROIDs for over a week now, one important chunk of it has been under lock-and-key: the source. Even amongst manufacturing partners, we're told, Google hasn't been completely open …
Context & Ripple Effects
Android 2.0 reached users first through Motorola's DROID while its source stayed closed — MobileCrunch reports that even manufacturing partners reportedly did not see all of it, though that account is unconfirmed. The gap mattered because back in July 2009 an Android team member had to clarify that Donut was not actually 2.0 and lacked multitouch, leaving the community unsure what 2.0 really contained.
The source drop closes that loop: within roughly a week of the DROID shipping, Google published the code and developers had already ported 2.0 to the original G1 — the same device line whose prototype leaked into the wild two years earlier. For a platform marketed on openness, holding the source back until after the flagship launch was itself the notable move.
First-order effects
- G1 owners and ROM builders gain an official path to Android 2.0 on hardware Motorola and HTC no longer prioritize, since the community port exists before most carriers have shipped any 2.0 update.
- Manufacturing partners such as Motorola lose their window of exclusive access to the codebase, putting every licensee on equal footing for building 2.0 devices.
Second-order effects
- Carrier and OEM update pipelines come under direct comparison with free community ports — if hobbyists put 2.0 on the G1 within days, buyers will ask why subsidized phones lag months behind, pressuring Motorola and carriers to accelerate rollouts.
- A faster public source cadence lowers the barrier for smaller OEMs and Asian manufacturers to ship current-version Android, compressing the differentiation that early-access partners previously enjoyed.
Third-order effects
- If Google keeps pairing each flagship hardware launch with a near-term source release, its real control point over the ecosystem becomes the timing and completeness of those drops rather than closed code — openness by schedule rather than secrecy.
- Legacy-hardware support structurally shifts to the community: devices dropped by carriers can live on through unofficial builds, splitting the installed base between vendor-sanctioned updates and self-maintained forks.
The trend: Android's competitive engine is becoming a repeatable cycle — ship the flagship phone first, release the source soon after, and let the community extend the platform onto older hardware faster than the vendors can.