We just went through all of this back with Cupcake/Android 1.5 a few months ago, but since some people seem to be screwing it up again, let’s take this once more, from the top, with feeling:
Tasty treats are not releases. Donut is not Android 2.0.
Donut, Eclair, and Flan – Rubin Talks Future of Android
Andy Rubin, or, The Man, as we like to call him around here, was speaking at a T-Mobile and Google media event earlier today where the Google VP of engineering was talking about the future of Android and where the focus will be.รย The future beyond Cupcake that is Donut, Eclair, and Flan.รย Yup… Flan.
Two More Android Updates Slated for 2009
We’ve seen two updates to Android in the first half of the year. Get ready for another pair over the next 6 months. According to Mobile Crunch, we’ll be seeing a minor update and a major update before the year is out.
We saw a minor in the upgrade from 1.0 to 1.1 and the major update was 1.1 to 1.5 (Cupcake). It’s widely assumed that the next major update will be Donut (2.0).
HTC Announces Hero with Flash Support, 3.5mm Headphone Jack
Announced in mid-2009, the HTC Hero marked a pivotal moment for both HTC and Android. At a time when Googleโs mobile operating system was still finding its identity, HTC stepped forward with a device that didnโt just run Android, it reshaped it.
Following the earlier HTC Dream (also known as the T-Mobile G1) and the HTC Magic, the Hero introduced a bold new software layer called HTC Sense. Originally rumored under the codename โRosie,โ Sense became HTCโs defining interface for years to come, signaling that Android manufacturers could build distinctive user experiences on top of Googleโs core platform.
In many ways, the Hero was less about raw hardware leaps and more about personality. It was one of the first Android phones to feel intentionally designed rather than merely assembled.
Key Specs & Features
At launch in 2009, these specifications placed the Hero squarely in the upper tier of Android devices:
- Display: 3.2-inch touchscreen
- Resolution: 320 ร 480 (HVGA)
- Processor: 528 MHz Qualcomm MSM7200A
- Memory: 512MB ROM, 288MB RAM
- Camera: 5-megapixel rear camera
- Battery: 1350 mAh removable battery
- Connectivity: Quad-band GSM/EDGE, Wi-Fi, GPS, digital compass
- Storage Expansion: microSD card slot
- Audio: 3.5mm headphone jack
- Software: Android (initially 1.5 Cupcake) with HTC Sense UI
- Browser Support: Integrated Adobe Flash Lite support
While modest by modern standards, these specs were competitive in 2009. A 5MP camera was considered strong for the time, and the inclusion of a standard 3.5mm headphone jack was a welcome move in an era when proprietary connectors were common.
The Hero also featured a distinctive curved โchinโ design and, notably, a Teflon coating on its exterior. HTC promoted this as a way to reduce fingerprints and improve durability. It was an unusual materials choice that reflected a growing emphasis on industrial design in smartphones.
HTC Sense: A Turning Point
The real headline feature was HTC Sense. Instead of the relatively plain Android interface seen on early devices, Sense layered in:
- Customizable home screen widgets
- A redesigned lock screen and launcher
- Social networking integration
- Profile-based layouts that could shift widgets depending on context
The idea of switching between user profiles, such as a work-focused layout and a personal, social-centric one, felt forward-thinking at a time when Androidโs customization tools were still basic.
Sense would go on to define HTCโs brand for nearly a decade. It influenced how other manufacturers approached Android skins and helped normalize the concept of heavy UI customization on Android devices.
Why It Mattered
In 2009, Android was competing against Appleโs iPhone OS and a still-relevant BlackBerry ecosystem. Hardware differentiation was limited, and software polish mattered more than ever.
The HTC Hero demonstrated that Android was flexible enough to support deep customization. It helped establish a key truth about the platform: manufacturers could create their own identity without abandoning Googleโs ecosystem.
The device also reinforced several trends that would define smartphones for years:
- Larger touchscreens replacing physical keyboards
- Removable batteries and expandable storage
- Increasing emphasis on camera performance
- Social media integration baked into the operating system
At a time when under 300MB of RAM was typical and app ecosystems were still developing, the Hero felt ambitious.
Looking Back
Compared to todayโs smartphones, the Heroโs 528 MHz processor and HVGA display seem almost quaint. Modern devices ship with multi-core processors thousands of times more powerful and displays exceeding 2K resolution. Yet in 2009, the Hero represented progress.
Its industrial design stood out, its software felt fresh, and its emphasis on customization foreshadowed much of what Android would become.
More than just another early Android handset, the HTC Hero helped define how manufacturers would build on Googleโs foundation. It was a reminder that Androidโs strength was not uniformity, but adaptability.
It’s Official, myTouch 3G Due in August
After months of speculation, T-Mobile formally introduced the myTouch 3G, the successor to the HTC G1 and one of the early flagship devices in the growing Android ecosystem. The handset was slated for release in early August, priced at $200 with a two-year service agreement.
Arriving less than a year after the debut of the G1, the myTouch 3G represented a refinement of Googleโs first-generation Android hardware and signaled T-Mobileโs continued commitment to the platform.
Overview
The myTouch 3G retained much of the internal foundation established by the G1 but adopted a sleeker, more contemporary design. Unlike the G1โs sliding physical keyboard and angular profile, the myTouch 3G emphasized a slimmer, touch-centric form factor.
Available in black, white, and merlot, the device aimed to broaden Androidโs appeal at a time when competition from the Palm Pre and Appleโs iPhone 3GS was intensifying.
Key Specifications
Final specifications for the myTouch 3G included:
- 3.2-inch capacitive touchscreen display
- 3.2-megapixel rear camera
- Android 1.5 (Cupcake)
- UMTS/HSPA connectivity
- Wi-Fi 802.11 b/g support
T-Mobile also indicated improved battery performance, promising approximately one additional hour of talk time compared to the G1.
While the core hardware shared similarities with its predecessor, the updated design was intended to make Android devices feel more mainstream and competitive in the rapidly evolving smartphone market of 2009.
Exclusive Software: Sherpa
Alongside the hardware announcement, T-Mobile introduced a new application called Sherpa, described as exclusive to the myTouch 3G at launch.
Sherpa was positioned as a personalized recommendation engine that learned from user behavior over time. By analyzing habits and preferences, the app would suggest nearby shops, restaurants, and other points of interest. For example, frequent searches for specific fast-food chains could prompt recommendations for similar establishments.
At a time when contextual, location-based services were still emerging, Sherpa reflected early efforts to make smartphones more adaptive and personalized.
Availability
Existing T-Mobile customers were given the opportunity to pre-order the myTouch 3G beginning July 8, ahead of its early August retail availability.
Why It Mattered
The myTouch 3G marked an important step in Androidโs early evolution. With Android 1.5 introducing refinements such as on-screen keyboards and improved performance, hardware like the myTouch 3G helped move the platform beyond its experimental phase.
By delivering a more polished design while maintaining competitive pricing, T-Mobile positioned the myTouch 3G as a viable alternative in a market increasingly defined by touch-driven smartphones. It represented Androidโs push toward broader consumer adoption during a formative moment in mobile history.
CNET Interviews Andy Rubin – “It Will Change the Game”
During Androidโs early ascent, the mobile industry was still fragmented and dominated by tightly controlled platforms. Smartphones were evolving quickly, netbooks were gaining attention, and in-car systems and set-top boxes were beginning to edge into the conversation. In that environment, an in-depth interview with Andy Rubin offered a clear look at how Google envisioned Androidโs role in shaping the future of connected devices.
At the time, Rubin was serving as Googleโs director of mobile platforms. He had previously co-founded Danger, best known for the Sidekick, and later co-founded Android when it was still an independent startup. His perspective carried weight not only because of his leadership role, but because Android itself had yet to prove its long-term viability against established competitors.
Competing in a Rapidly Shifting Market
When the interview was conducted, Appleโs iPhone was redefining consumer expectations for smartphones, and Palmโs webOS was positioning itself as an innovative alternative. Android was still in its formative stages, competing not just on hardware but on philosophy.
Reflecting on Palmโs webOS and the iPhone, Rubin said:
โYou can have spurts of innovation. You can nail the enterprise, nail certain interface techniques, or you can nail the Web-in-the-handset business, but you canโt do everything. Youโre always going to be in some niche. What weโre talking about is getting out of a niche and giving people access to the Internet in the way they expect the Internet to be accessed. I donโt want to create some derivative of the Internet.โ
At a time when many platforms were optimized for specific use cases or tightly controlled ecosystems, Rubin emphasized scale and openness. The goal was not to refine a single experience to perfection, but to build a foundation capable of reaching beyond niche segments.
A Platform, Not Just a Phone
One of the more forward-looking aspects of the interview centered on Androidโs potential beyond smartphones. Rubin referenced the longstanding software ideal of โwrite once, run everywhereโ and suggested that Android could finally bring that idea into practical reality.
โRemember people used to trumpet โwrite once, run everywhereโ? Well, I think weโre actually there. When we start talking about the possibility of exploring things like netbooks and car navigation systems, you have potentially different processor architectures. You have Intel, you have ARM, set-top boxes have MIPS. We have all sorts of different processor architectures, and the guys who are steeped in legacy have trouble addressing those markets with a single solution. I actually think Android is the potential single solution that can address all those markets. Itโs new, itโs revolutionary. It will change the game.โ
At the time, Androidโs expansion into cars, TVs, and other connected devices was largely theoretical. The broader industry had yet to fully embrace multi-device ecosystems. Still, Rubinโs comments made it clear that Google saw Android not as a phone OS, but as a scalable software layer adaptable across hardware categories.
Why There Was No โGphoneโ
Early speculation about a Google-branded phone was widespread. Rubin addressed the idea directly, explaining why Googleโs focus was on the platform rather than a single flagship device.
โItโs funny. If you build one phone, Iโd much rather be the guy who creates a platform capable of running on multiple companiesโ phones than focusing on a single product. A single product is eventually going to have limitations. Even two products will have limitations. But if itโs a hundred products, now weโre getting somewhere. Thatโs the scale at which Google thinks people want to access information.โ
This perspective underscored Googleโs strategic priorities at the time: broad distribution and manufacturer partnerships over vertical integration. Long before Google introduced its own Pixel hardware line, the emphasis was on enabling a wide ecosystem of devices from multiple vendors.
Why It Matters
Looking back, the interview captures a pivotal moment in mobile computing. Android had not yet secured its dominant position, and the outcome of the platform wars was far from certain. Rubinโs comments reveal a deliberate focus on openness, cross-device scalability, and long-term reach rather than short-term product wins.
Many of the platform decisions that shaped Androidโs evolution were already embedded in this early philosophy. The commitment to running across different processor architectures, supporting diverse hardware partners, and expanding beyond phones was not an afterthought. It was foundational.
Revisiting these remarks provides a clear snapshot of Androidโs original ambitions and the strategic thinking that guided its early development.
G1 and Cupcake – What’s the Deal?
Current G1 owners are licking their chops at the prospect of getting some much desired updates to their Android phones.ร Features like video recording, stereo Bluetooth, and an on-screen keyboard are the only things missing from an otherwise robust OS.ร But will the G1 ever see the icing from cupcake’s features?ร Ask around and you’re likely to get varying answers.
Here’s what we’ve pieced together so far.
Cupcake is a different version, or image of Android.ร Carriers and handset makers are free to take whatever is available from Android and bend it to their liking.ร If the hardware you have doesn’t support stereo Bluetooth, then obviously the device won’t either.ร No software is going to override the hardware and get it to do something it can’t.
The image of Android that was used for the G1 was built by Google, HTC, and T-Mobile.ร The updates for Android, including the cupcake stuff, don’t need to involve HTC or T-Mobile.ร Developers from all over are chipping in to make Android a more full software platform.
According to Engadget Mobile, HTC told them today that at some point in the future, the fixes and updates from cupcake will be sent to G1 owners in an over the air (OTA) push.ร Further, they claim that HTC is not too involved in the decision as to when it happens, leaving it up to Google and T-Mobile to figure out.
It might be a while before that happens though, based on some information we’ve had sent our way.
I have been following the Google group of the developers on the cupcake and its a piece of garbage as it is now. One person there put it on his G1 and when he recorded video it crashed and froze up constantly. They now say there needs to be a new radio firmware update before it ever works on the G1 and no such work is being done on this…The G1 contains a significant number of proprietary applications, drivers, etcรขโฌยฆ that arenรขโฌโขt part of the core Android Open-Source Project.
The three companies involved in bringing the G1 together all had a say in what the device looked and felt like.ร The phone was built by taking a pre-released version of Android and tweaking and molding it.ร The version of Android we see on the G1 will probably never make its way to another handset.ร That’s one of the first things we learned about the platform.ร Carriers and end users have the ability to change things to their liking. While the G1 is more Google and less T-Mobile, the Sprint phone might be branded to around the carrier’s identity and services.
It’s a very likely scenario that the cupcake Android is what will get used for the Samsung, Hauwei, and other handsets.ร It’s possible that they are using the new “master branch” of Android as they build their first devices.ร We’re already almost two weeks removed since the cupcake stuff became merged into the master branch.
Maybe Sprint is a little more involved in inner circle of things and knew what was coming.ร They claim to be ready to drop an Android handset when the timing is right.ร As an outsider looking in, the first reaction is to think that no time is like the present for the ailing carrier.ร Perhaps they’ve got the hardware ready to go and have been waiting for the updates, patches, and fixes.ร Rather than looking for the right date on a calendar, they are working to get a more recent version of Android to play nice with their hardware.
As we get further from the release of the G1, the words to describe the hardware get less mixed.ร After months of reading reviews and different takes on the device, the general consensus is that while the phone is good, Android is great.ร As we look towards the next few handsets that will run Android, we get increasingly excited at the prospects of prettier devices with an even better operating system.
EDITOR UPDATE: I’ve noticed some negative feedback regarding this article from other sources.ร I’d like to point out that nowhere in this article did the writer state that the G1 would not get the update.ร In fact, the best I see is that he said it might be a while.ร Further, he didn’t claim that our email tip was gospel.ร It was simply from someone who followed the Google group, wanting to share with us.
I’m glad to see any attention to the piece that we get, even if it is to correct things that are not true.ร The team of guys who help contribute to AndroidGuys is comprised mainly of fans.ร There are various amounts of industry background and writing experience here.ร While sometimes I’d like to step in an edit posts before publishing, I tend to let my guys get beat up a little by our readers before I make changes.
Thanks to everyone who has read and/or commented on the piece! Have a Happy New Year!
Scott Webster
Google Staff Receives Dream Phones for Holiday Bonus, Called DogFood
Dogfood.ร Ever heard that term?
It’s the idea behind a lot of Google’s services.ร Basically, when a company eats its own dog food, they are confident enough in their product or service to have their entire team use it.ร Its helpful if you are a tech related company as many on your team can help find bugs as well as give feedback and insight into the future developments.ร That’s exactly what happened this year for Google staffers.
Rather than getting any sort of monetary bonus at the end of the year, they are getting Dream handsets.ร Yep, everybody gets a new phone, Oprah style.ร “You get a Dream phone!ร You get a Dream phone!”
What’s the difference between a Dream and the T-Mobile G1?
Shipping these special edition phones in such a short time frame (they were designed especially for Googlers with a รขโฌหdroidรขโฌโข on the back) and making sure they would work anywhere in the world was no small feat. So a big thank you to the Android and Legal teams for making this happen. While these phones do not have SIM cards, they are unlocked so they can be used with the network provider of your choice. Plus – thanks to more fancy footwork from the Android team – theyรขโฌโขll work immediately as WiFi devices!
Our guess is that it’s either exactly like the Dev Phone 1, or very close to it.ร We’ve seen stories where Googlers get thousands of dollars as year-end bonus, so this might be a slap in the face to some of them.ร Worth roughly $400, this would be a welcome freebie to a lot of us tech bloggers and developers.
Google’s hopes are that by dogfooding this handset, some savvy, proficient geek types come up with the next big ideas for Android and the platform benefits.
“Cupcake” Update to Android Sees Video Recording, Stereo Bluetooth, On-Screen Keyboard and Much More!
This is the type of Android enhancements we’re talking about! A major update is coming in the first quarter of 2009 to Android and it’s not all bugs and security fixes. Code named “cupcake”, we’re looking at some much needed/wanted stuff like stereo Bluetooth, video recording, and on-screen keyboards.
Not confined to just the G1, these updates are coming in the form of a “development branch” and not a “release”.ร At some point, possible January, it will be merged into the “master branch” so we’re hoping to see a nice little update notification sometime in the coming weeks.
While some of these changes are obvious to users, others will be less apparent. There’s still going to be the requisite bug fixes that people don’t detect. And in the middle are changes like having your music player fade in after hanging up a call, rather than going full-on and tactile feedback with the security password. Oh, and the phone’s screen won’t time out so quickly during calls!
The web browser will see nice changes with the newest core of Webkit, support for new Javascript features, and copy/paste. We’re also excited to see the ability to save attachments from MMS as well as the soft-keyboard feature. Pounding out one-handed texts and emails are getting closer!
There’s still one big thing we’d really like to see, especially when more quality apps hit the market… Install apps and run them from the SD card. Some of us might take that one enhancement over all the others if we were given the choice.
You Tell Us
What features are you most excited about with Cupcake? What’s still missing from your list, anything?
34 Weeks of OHA #31
I’m kinda breaking the rules this week by presenting two OHA members in one profile. By titling this colomn 34 Weeks of OHA, I’m implying that there will be 34 articles, one for each OHA member, over the space of 34 weeks.
I’m deviating from this rule for a few reasons. First, the two companies I’m profiling this week not only fall right next to each other on the alphabet, they’re also similair in that they’re both European, they serve adjacent countries, and they’re both so inherently uninteresting that trying to space them out over two articles would try the patience of everyone involved. Second, I’ve already blown the whole 34 weeks thing by skipping so many weeks that we’re already pushing one year; this is something of an attempt at catching up. Third, it’s my frickin’ article and my freakin’ rules and I’ll break those rules as I see fit; if you don’t like it go get your own article (you’ll probably do a better job at it than I do, anyway.)
Company Name: Telefรยณnica and Telecom Italia
How the OHA site classifies them: Mobile Operators
What the OHA site says about them:
Telefรยณnica – Telefรยณnica is one of the largest telecommunication companies in the world, providing communication, information and entertainment solutions, with presence in Europe, Africa and Latin America and with more than 212 million clients of fixed and mobile services.
Telecom Italia – Supplying 34.3 mobile lines, around 23 million landlines and 7.3 million broadband clients, Telecom Italia is a Italy’s leading ICT enterprise with a significant international presence in Europe and South America. The Group trades through pre-eminent brands Telecom Italia, Alice, TIM, La7, MTV Italia, APCom and Olivetti in fixed-line and mobile telecommunications, Internet and media, office & system solutions.
What they do:
They’re mobile carriers. Thankfully, they’re the last carriers I’ll have to profile for this damned column.
Let’s start with Telefรยณnica. They’re Spanish. In fact, until the opening of the market in 1997 they were the only telecom operator in Spain, which is a pretty cushy gig if you can get it. They still control 75% of the market in Spain.
They’ve spread: the Czech Republic and Slovakia; Italy; their 2006 acquisition of O2 brought them into Germany and the UK; they have a presence throughout Latin and South America. They have even begun penetrating into Africa and China. All this Spanish-Empire-style activity has made them the third-largest telco in the world, helped them do fifty billion Euros worth of sales in 2006, and brought them their share of controversy–monopolistic and allegedly unethical practices have made Telefรยณnica the target of governments the world over.
Telefรยณnica has their fingers I’m all the traditional telco pies: landline, broadband, and, of course, mobile.
Telecom Italia are Italian. They’re the product of the merger of several Italian telecom companies they’re neither ad big or as far-reaching as Telefรยณnica, although they do have a presence in several European and South American countries.
What they bring to OHA and Android:
Penetration. There’s really not that much exciting about either player. They only thing they really bring is reach, further coverage for Android.
There’s nothing wrong with that, it just doesn’t make for a very good article. Sorry.
The one interesting point of note here is that they both have significant penetration into South America, which is kind of always forgotten about. There’s a lot of people down there (at least, that’s what I’m told). Significantly, Google’s Orkut owns the Social space in Brazil, and getting an Android handset into that country would, I’m sure, be a boon for them.
And now, for lack of anything lese to say, I’m going to leave you with a couple of bits from the OHA quotes page.
“Telefรยณnica strives to bring the best of the web to our customers, wherever they are. We are pleased to be a part of the Open Handset Alliance, which we believe will enable new and innovative services to be launched on a robust and open platform. We look forward to delivering customized phones based on this platform for our customers.”
— Adrรยญan Garcรยญa Nevado, Corporate Commercial Director of Telefรยณnica S.A.“Telecom Italia is already focused on the mobile Internet framework and services and strongly believes that it will be the key successful approach for future revenues. In this scenario the Open Handset Alliance represents an important initiative for Telecom Italia and for all its members to work together and to speed up the development process of a new open OS for mobile Internet services.”
— Riccardo Jelmini, Executive Vice President, VAS Domestic Mobile Services of Telecom Italia