Hubbry Logo
Android Dev PhoneAndroid Dev PhoneMain
Open search
Android Dev Phone
Community hub
Android Dev Phone
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Android Dev Phone
Android Dev Phone
Android Dev Phone
View on Wikipedia
from Wikipedia

The Android Dev Phone (ADP) was a series of SIM-unlocked and bootloader unlocked Android devices designed for advanced developers. While developers can use regular consumer devices purchased at retail to test and use their apps, some developers may choose not to use a retail device, preferring an unlocked or no-contract device.

The Google Nexus series was the de facto successor of Android Development Phones,[1] with the Google Pixel series coming after.

Android Dev Phone 1

[edit]

On December 5, 2008, Google announced the Android Dev Phone 1, a version of the HTC Dream.[2] The Android Dev Phone 1 was a SIM-unlocked and bootloader unlocked device that was designed for advanced developers. The device shipped with Android 1.0. It was possible to use any SIM in the device and one could flash custom Android builds that would work with the unlocked bootloader.[3] Unlike the bootloader on retail devices, the bootloader on the Android Dev Phone 1 did not enforce signed system images. The Android Dev Phone 1 also appealed to developers who live outside T-Mobile geographies. The device itself cost $399 (USD) (including free shipping in the US).[4] Google stated that "The Android Dev Phone 1 devices are not intended for non-developer end-users. Because the device can be configured with system software not provided by or supported by Google or any other company, end-users operate these devices at their own risk."[3][5]

System access and copy protection

[edit]

Applications developed for distribution on Google Play allow the developer to enable copy protection which prevents the end user from copying the application from the phone. Because the Android Dev Phone allows unrestricted access to the OS, this copy protection is disabled. If the developer enables copy protection on their application, then the application does not appear on Google Play for the Dev Phone.[6]

Availability

[edit]

The device was available for purchase in 19 international markets, including United States, United Kingdom, Germany, Japan, India, Canada, France, Taiwan, Spain, Australia, Singapore, Switzerland, Netherlands, Austria, Sweden, Finland, Poland, Egypt and Hungary.[3]

Hardware specifications

[edit]

Android Dev Phone 2

[edit]

The Android Dev Phone 2 was a hardware unlocked version of the HTC Magic.[7][8] The Android Dev Phone 2 was a SIM-unlocked and bootloader unlocked device that was designed for advanced developers. The device shipped with Android 1.6. It was possible to use any SIM in the device and one could flash custom Android builds that would work with the unlocked bootloader. Unlike the bootloader on retail devices, the bootloader on the Android Dev Phone 2 does not enforce signed system images. The Android Dev Phone 2 should also appealed to developers who live outside T-Mobile geographies. The device itself cost $399 (USD) (including free shipping in the US)."[5]

Availability

[edit]

The device is available for purchase in 21 international markets, including United States, United Kingdom, Germany, Japan, India, Canada, France, Taiwan, Spain, Australia, Singapore, Switzerland, Netherlands, New Zealand, Austria, Sweden, Estonia, Finland, Poland, Egypt and Hungary.[9]

Hardware specifications

[edit]

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Android Dev Phone

View on Grokipedia
from Grokipedia
The Android Dev Phone (ADP) was a series of SIM-unlocked and bootloader-unlocked smartphones developed and distributed by Google in the late 2000s to enable software developers to test applications, debug code, and modify the Android operating system on physical hardware without carrier restrictions. The first model, known as the ADP1 or Android Dev Phone 1, was an unlocked variant of the HTC Dream (also released as the T-Mobile G1), launched and made available to developers in late 2008 for approximately $399, running initial versions of Android such as 1.0 and 1.1. This device featured a sliding QWERTY keyboard, a 3.2-inch touchscreen, and 3G connectivity, serving as an essential tool for early Android ecosystem growth by allowing direct sideloading of apps and custom ROMs. The ADP2, or Android Dev Phone 2, followed in 2009 as an unlocked version of the HTC Magic (also called the Google Ion in some markets), equipped with Android 1.5 (Cupcake) and upgradable to 1.6 (Donut), a 3-inch touchscreen, and improved hardware like 192 MB of RAM for enhanced development testing. These devices were not intended for general consumers but were pivotal in fostering the open-source Android community, paving the way for subsequent reference devices like the Nexus series, and highlighting Google's commitment to developer accessibility in the platform's formative years.

Background

Development History

Android Inc. was founded in October 2003 in , by , Rich Miner, Nick Sears, and Chris White, with the initial goal of developing software for digital cameras before shifting focus to mobile devices. In August 2005, acquired Android Inc. for an estimated $50 million, integrating the team into its efforts to create an open mobile platform. On November 5, 2007, Google announced the formation of the (OHA), a consortium of 34 technology and mobile industry leaders including HTC, , , and carriers like , aimed at accelerating innovation in mobile devices through an open-source platform called Android. The OHA's launch included the release of the first beta, enabling developers to begin building applications for the emerging ecosystem. Following the commercial debut of the (T-Mobile G1) in October 2008 with Android 1.0, Google introduced initial developer preview devices to support advanced app testing and customization. On December 5, 2008, Google announced the Android Dev Phone 1 (ADP1), a SIM-unlocked and bootloader-unlocked variant of the , available exclusively to registered Android Market developers for $399. The ADP1 shipped in December 2008 running Android 1.0, an early version characterized by its beta-like stability and limited features, such as basic multitasking and no native app market integration beyond developer tools. In May 2009, released the Android Dev Phone 2 (ADP2), a developer edition of the HTC Magic, also SIM- and bootloader-unlocked, priced at $399 and initially available to attendees of 2009 before broader developer sales in select international markets. The ADP2 launched with Android 1.5 (), which introduced refinements like on-screen keyboards and video recording, though it retained a beta nature with ongoing bug fixes and API expansions to facilitate broader developer experimentation ahead of Android 1.6 (Donut).

Purpose and Features

The Android Dev Phone (ADP) series was designed exclusively for advanced developers, providing access to real hardware for testing Android applications without the limitations imposed by carrier-specific software or restrictions. This allowed developers to experiment with app functionality in a production-like environment, free from the bloatware and network dependencies often found on consumer devices. Key features of the ADP emphasized openness and customization, including SIM-unlocking for use on any compatible network and bootloader-unlocking to enable full system modifications. These attributes supported the installation of custom ROMs, kernel tweaks, and other low-level alterations essential for thorough development and . Additionally, the devices did not enforce signed system images, permitting the deployment of unsigned applications and direct system-level changes that would be restricted on standard retail phones. Copy protection mechanisms were disabled on ADP devices, facilitating unrestricted of apps and access to content from the Android Market (now ) without the barriers typical of protected consumer ecosystems. This setup was particularly valuable for testing app distribution and compatibility across diverse scenarios. The devices ran early versions of Android, such as 1.0 and 1.6, aligning with the platform's initial development phases. Users operated ADP devices at their own risk, as Google provided no official support, warranties, or customer service for hardware or software issues arising from modifications. This hands-off approach underscored the experimental nature of the platform, intended solely for technical exploration rather than everyday consumer use.

Android Dev Phone 1

Release and Availability

The Android Dev Phone 1 (ADP1) was released in December 2008 as a SIM-unlocked and bootloader-unlocked variant of the (also known as the G1 in some markets), designed specifically for Android developers. It was made available for purchase at $399 USD exclusively through the Android Market developer portal, requiring a one-time $25 developer registration fee and initial verification under a (NDA) to ensure access was limited to qualified developers. This NDA requirement was later relaxed, broadening access while maintaining focus on development use. The device was shipped to multiple countries, including the , , , , , , and France, to support global developer testing of early Android applications. It launched with Android 1.0, providing an open platform for apps and custom modifications without carrier limitations.

Hardware Specifications

The Android Dev Phone 1 (ADP1) was based on the platform, featuring a sliding keyboard and a form factor optimized for early Android development, including app and OS customization on physical hardware. Its prioritized for developers, with a for navigation and support for extended testing sessions. The display was a 3.2-inch with a resolution of 320 × 480 pixels and a pixel density of approximately 180 ppi, suitable for prototyping touch interfaces in initial Android versions. It included a MSM7201A at 528 MHz, 192 MB of RAM, and 256 MB of internal storage, expandable via microSD card up to 8 GB for storing test apps, logs, and custom builds. This setup allowed handling of basic multitasking in early Android environments. For imaging and connectivity, the ADP1 had a 3.2-megapixel rear camera with no or flash, adequate for testing camera APIs; a 3.5 mm headphone jack; and a mini-USB port for charging and transfer. The build measured 117.7 × 55.7 × 17.1 mm and weighed 158 g, with a sliding mechanism for the keyboard. Power came from a removable 1150 mAh Li-Ion battery, offering up to 5.5 hours of talk time or 290 hours standby. Connectivity supported GSM/GPRS/EDGE on quad-band (850/900/1800/1900 MHz), HSDPA up to 7.2 Mbit/s on 2100 MHz, 2.0, 802.11 b/g, and A-GPS for location services development. The ADP1 shipped with Android 1.0 software, tailored for its hardware.
CategorySpecification Details
Display3.2-inch , , 320 × 480 pixels, ~180 ppi
Processor & Memory MSM7201A @ 528 MHz, 192 MB RAM, 256 MB internal storage + microSD (up to 8 GB)
Camera & Ports3.2 MP rear (/flash), no front camera; 3.5 mm jack, mini-USB
Build & Battery117.7 × 55.7 × 17.1 mm, 158 g; 1150 mAh removable Li-Ion
Connectivity/GPRS/EDGE (850/900/1800/1900 MHz), HSDPA (7.2 Mbit/s), 2.0, 802.11 b/g, A-GPS

Software and System Access

The Android Dev Phone 1 (ADP1) shipped with Android 1.0 (API level 1) as its initial operating system, offering developers a foundational platform to test core features like the browser, , and basic touch interactions on unlocked hardware. An official update to Android 1.1 was released in March 2009, adding support for paid apps in the Android Market, video recording, and improved search functionality to facilitate more advanced app development. Further upgrades to Android 1.6 (Donut) were possible via official firmware or manual flashing, introducing multi-resolution support, better text selection, and battery indicators for enhanced optimization testing. Key to its developer focus was the unlocked , enabling installation of custom ROMs, recoveries, and system modifications without barriers. It included full (ADB) and support for , log monitoring, and rooting directly from a host computer, streamlining workflows for early Android ecosystem building. Copy protection was disabled, allowing and testing of unsigned apps freely, with unrestricted access to the Android Market for beta downloads and previews. This openness supported prototyping of apps requiring system-level access or custom permissions, setting it apart from locked consumer variants like the T-Mobile G1. The ADP1's software emphasized foundational APIs for sensors, multimedia, and connectivity, with Android 1.1 refinements improving mock location support and browser rendering for web app development. Updates addressed bugs in and stability, while firmware extended viability for testing newer features. These elements made the ADP1 a crucial tool for the initial growth of Android's open-source .

Android Dev Phone 2

Release and Availability

The Android Dev Phone 2 (ADP2) was announced at the conference on May 27, 2009, where it was distributed free of charge to all attendees as the Google Ion, a developer-focused variant of the HTC Magic hardware. This initial release provided early access to Android 1.5 for testing and development purposes. General availability for purchase began on November 13, 2009, priced at $399 USD, and was accessible exclusively through the Android Market developer portal following account registration and verification. Unlike the Android Dev Phone 1, which initially required a (NDA) for access, the ADP2 offered broader developer access without such restrictions, though limited to verified developer accounts. The device was shipped to 21 countries, including the , , , , , and , facilitating global developer participation. The initial software version was Android 1.6 Donut, which included features like improved search and UI refinements.

Hardware Specifications

The Android Dev Phone 2 (ADP2) was built on the HTC Magic platform, incorporating a compact form factor designed for developer testing and early Android app experimentation. Its hardware emphasized portability and basic multimedia capabilities, with refinements over the original Android Dev Phone 1 (ADP1) including a slimmer profile, reduced weight, and enhanced battery life to support prolonged development sessions without frequent recharging. These improvements made the ADP2 more practical for on-the-go use compared to the bulkier ADP1. The display featured a 3.0-inch resistive touchscreen with a resolution of 320 × 480 pixels and a pixel density of 192 ppi, providing adequate clarity for interface prototyping and touch-based interactions typical in early Android development. Under the hood, it utilized a MSM7200A single-core processor running at 528 MHz, paired with 288 MB of RAM for multitasking and 512 MB of internal storage, expandable via microSD card up to 16 GB to accommodate custom ROMs, apps, and debug data. This configuration represented a step up in memory from the ADP1's 192 MB RAM and 256 MB storage, enabling smoother handling of beta software builds. For imaging and peripherals, the ADP2 included a 3.2-megapixel rear camera with but lacking a flash or front-facing option, suitable for basic testing of camera APIs; it also offered a 3.5 mm headphone jack for audio output and a micro-USB port for connectivity and charging. The device's physical build measured 113 × 56.4 × 13.65 mm and weighed 118 g, making it noticeably lighter and thinner than the ADP1's 117.5 × 56 × 16 mm and 155 g design. Power was provided by a removable 1340 mAh Li-Ion battery, which offered better endurance than the ADP1's 1150 mAh unit, with typical usage lasting up to 450 minutes (7.5 hours) of talk time or 660 hours standby (450 hours for ). Connectivity options were geared toward global developer accessibility, supporting GSM/GPRS/EDGE on quad-band frequencies (850/900/1800/1900 MHz), HSDPA download speeds up to 7.2 Mbit/s, Bluetooth 2.0 + EDR for wireless peripherals, 802.11 b/g for network testing, and integrated GPS for location-based app development. The ADP2 shipped with Android 1.5/1.6 software, optimized for its hardware profile.
CategorySpecification Details
Display3.0-inch TFT LCD, resistive touchscreen, 320 × 480 pixels, 192 ppi
Processor & MemoryQualcomm MSM7200A @ 528 MHz, 288 MB RAM, 512 MB internal storage + microSD (up to 16 GB)
Camera & Ports3.2 MP rear (autofocus, no flash), no front camera; 3.5 mm jack, micro-USB
Build & Battery113 × 56.4 × 13.65 mm, 118 g; 1340 mAh removable Li-Ion
ConnectivityGSM/GPRS/EDGE (850/900/1800/1900 MHz), HSDPA (7.2 Mbit/s), Bluetooth 2.0 + EDR, Wi-Fi 802.11 b/g, GPS

Software and System Access

The Android Dev Phone 2 (ADP2) shipped with Android 1.5 Cupcake (API level 3) as its initial operating system, providing developers with a stable platform for testing applications on a touch-enabled device. This version introduced key features like on-screen keyboards, widgets, and improved video recording, enabling early experimentation with user interface elements and multimedia integration. Developers could upgrade to Android 1.6 Donut via official over-the-air updates or manual flashing, which added support for multiple screen resolutions, a quick search widget, and battery usage indicators to enhance device management and app optimization. The upgrade also expanded API capabilities for handling diverse hardware configurations, making it easier to develop apps compatible across varying form factors. A hallmark of the ADP2's design was its unlocked , allowing developers to install custom recoveries, flash alternative ROMs, and perform low-level modifications without restrictions. Full support for (ADB) and tools was included out of the box, facilitating seamless debugging, logcat monitoring, and system-level tweaks directly from a connected computer. This configuration empowered developers to the device, sideload test builds, and iterate rapidly on , distinguishing the ADP2 from consumer variants of the HTC . Copy protection mechanisms were disabled on the ADP2, enabling the installation and testing of unsigned applications without certification hurdles. This allowed unrestricted access to the full Store (then Android Market) for downloading developer previews and beta apps, bypassing the typical signature verification that limited experimentation on locked devices. Such openness was essential for prototyping apps that interfaced with system services or required elevated permissions. Compared to the original Android Dev Phone 1, the ADP2 offered enhanced developer tools, particularly through refined APIs for sensors and processing. Android 1.6 introduced better support for and proximity sensors, along with improved media frameworks for handling audio and video streams, enabling more sophisticated applications like location-based services and richer content playback. These advancements reduced compatibility issues and accelerated development workflows for hardware-intensive features. Subsequent updates to the ADP2 addressed key bugs and refined core functionalities. Improvements to speech-to-text recognition enhanced accuracy in voice input for apps, while stereo (A2DP) support was stabilized for reliable audio streaming to wireless headsets. Additionally, HTML5 video playback received optimizations for smoother rendering in the browser, benefiting web app developers testing embedded media. These fixes, delivered through Google-maintained , ensured the device remained a viable testing platform post-launch. The unlocked further enabled these software enhancements by allowing community-driven patches alongside official releases.

Legacy and Impact

Transition to Successor Devices

The Android Dev Phone (ADP) series concluded after the release of the ADP2 in May 2009, as shifted focus from exclusively developer-targeted hardware to devices that balanced advanced technical access with broader consumer appeal. This transition reflected 's evolving to expand Android's reach beyond niche developer tools, prioritizing scalable production and market integration while preserving core developer functionalities like unlocked bootloaders. The ADP lineage was directly succeeded by the Google Nexus series, beginning with the , which was launched in January 2010 and positioned by as the new official developer device in August 2010. Unlike the ADP's limited distribution through developer programs, the Nexus One introduced carrier variants alongside an unlocked option, enabling developers to flash custom ROMs and access system-level modifications similar to its predecessors. The Nexus devices delivered a pure Android experience, free from manufacturer customizations like those on the HTC-built ADPs, and served as reference implementations for the Android Open Source Project (AOSP), fostering app development and testing on stock software. This evolution culminated in the launch of the series in October 2016, which fully replaced the line and continued emphasizing developer-friendly attributes. Pixel devices retained features such as official factory images for easy reflashing and seamless AOSP compatibility, allowing developers to deploy and debug applications on hardware closely aligned with production Android builds. The series marked a refined hybrid model, where high-end consumer hardware—featuring advanced cameras, Tensor processors, and extended software support—coexisted with tools for customization, further democratizing access to Android's core ecosystem. Overall, the progression from ADP to and represented a strategic pivot from developer-exclusive devices to inclusive platforms that accelerated Android's growth, enabling millions of users and creators to engage with unmodified OS versions while supporting the platform's expansion into mainstream markets.

Role in Android Ecosystem

The Android Dev Phones (ADP1 and ADP2) served a critical function in the nascent Android by supplying developers with SIM-unlocked and bootloader-unlocked production hardware, facilitating real-device testing of applications and system modifications. This access was essential for validating app performance and compatibility in actual usage scenarios, contributing to the swift maturation of the platform following the Android Market's debut on , 2008. Although the ADP1 entered sale in December 2008 at $399 with free shipping restricted to the , it enabled post-launch refinements that bolstered the ecosystem's stability and encouraged third-party app development. By providing hardware without carrier restrictions or enforced software signatures, the ADP series promoted open-source engagement, allowing developers to experiment with and submit feedback that shaped the Android Open Source Project (AOSP). This unlocked environment directly supported contributions to core Android components, as developers could flash experimental builds and identify issues in a controlled yet realistic setting. The devices also underscored gaps in early developer tooling, prompting iterative upgrades to the —such as improved debugging features—and emulator functionalities to simulate hardware more accurately when physical devices were scarce. With production limited to a small scale and availability confined to select markets like the , , , , and , the ADP's reach was constrained, yet it proved invaluable for beta testing foundational Android 1.x elements, including search enhancements and market integration in version 1.1 updates. High pricing—nearly double the $179 subsidized cost of the carrier-locked G1—and logistical barriers like US-only shipping drew criticism for hindering broader developer participation. Despite these drawbacks, the ADP established a blueprint for developer-centric devices, leaving a lasting imprint on contemporary rooting practices and custom ROM development, where remains a cornerstone of community-driven innovation.

References

  1. https://www.androidauthority.com/google-phones-nexus-pixel-history-3260339/
  2. https://www.androidpolice.com/2010/07/29/meet-andy-androids-history-in-a-nutshell/
  3. https://phandroid.com/2009/11/13/android-dev-phone-2-adp2-is-the-google-ion/
  4. https://www.androidauthority.com/history-nexus-smartphone-line-536352/
  5. https://www.wired.com/2016/02/android-inventor-andy-rubin-playground-artificial-intelligence/
  6. https://www.cnet.com/culture/google-buys-android/
  7. https://www.openhandsetalliance.com/press_110507.html
  8. https://googleblog.blogspot.com/2007/11/wheres-my-gphone.html
  9. https://www.eweek.com/mobile/google-releases-sim-unlocked-android-phone-for-399/
  10. https://www.engadget.com/2008-12-05-sim-hardware-unlocked-android-dev-phone-1-surfaces-for-399.html
  11. https://www.engadget.com/2009-05-05-htc-magic-now-available-in-europe-as-android-dev-phone-2-for-4.html
  12. https://www.engadget.com/2009-05-27-google-i-o-attendees-getting-free-unlocked-htc-magic-with-us-3g.html
  13. https://android-developers.googleblog.com/2009/03/software-update-available-for-android.html
  14. https://www.zdnet.com/article/google-launches-sim-unlocked-android-phone/
  15. https://arstechnica.com/uncategorized/2008/12/google-introduces-developer-g1-phones/
  16. https://phandroid.com/2008/12/06/unlocked-t-mobile-g1-courtesy-of-google/
  17. https://www.linux.com/news/android-powered-g1-phone-enticing-platform-app-developers/
  18. https://www.telecoms.com/mobile-devices/google-launches-unlocked-version-of-android-phone
  19. https://www.fierce-network.com/wireless/google-releases-unlocked-g1-for-developers
  20. https://www.gsmarena.com/htc_dream-2665.php
  21. https://arstechnica.com/gadgets/2009/03/android-11-available-for-dev-phones/
  22. https://www.endpointdev.com/blog/2009/05/google-io-2009-day-1/
  23. https://www.gsmarena.com/htc_magic-2714.php
  24. https://www.cnet.com/tech/mobile/android-1-5-sdk-whats-new-cupcake/
  25. https://www.informationweek.com/it-leadership/android-1-6-donut-revealed-by-google
  26. https://www.zdnet.com/home-and-office/networking/whats-new-in-android-1-6-donut-part-2-developer-features/
  27. https://www.pcworld.com/article/519742/android_donut_a_treat_for_developers.html
  28. https://www.androidpolice.com/2010/08/06/the-nexus-one-is-deadlong-live-the-nexus-one-google-crowns-nexus-one-android-developer-phone-3/
  29. https://googleblog.blogspot.com/2010/01/our-new-approach-to-buying-mobile-phone.html
  30. https://www.engadget.com/2010-08-05-nexus-one-lives-on-as-googles-official-developer-phone.html
  31. https://source.android.com/docs/core/architecture/bootloader/locking_unlocking
  32. https://developers.google.com/android/images
  33. https://developer.android.com/about/versions/16
  34. https://www.androidauthority.com/android-market-sixteen-years-3492940/
  35. https://developer.android.com/sdk/android-1.1.html
  36. https://www.t-mobile.com/news/press/t-mobile-unveils-the-t-mobile-g1-the-first-phone-powered-by
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.