GPhoneholic - Android and GPhone News.

Unofficial coverage of the Android mobile OS and the GPhones that run it.

tmobile_logo.pngAmol Sharma at The Wall Street Journal published an analysis of T-Mobile’s Android phone strategy and overall plan to differentiate itself from the pack of massive American cell-phone companies.

[...] It is likely that T-Mobile will be the first U.S. carrier to bring a Google-powered cellphone to market. The two sides have been working together for several months to develop the specifications for a new device, which would be powered by the Google-backed Android open operating platform. The companies have declined to name the manufacturer of the phone, but most people in the industry suspect it is Taiwan’s HTC Corp. The effort puts T-Mobile ahead of Sprint Nextel Corp., the only other U.S. carrier among the 33 partners Google announced last week in its push for open operating platforms for cellphones.

[...]

As the discussions ramp up, the wireless carrier faces some challenges. It must ensure that the openness of the Android platform doesn’t compromise customers’ privacy or make their phones more susceptible to hacking and viruses. Android will make it possible for independent developers to create a range of new applications using information they normally don’t have access to, including a user’s geographic location and communications history. T-Mobile says it will screen third-party applications to protect customers’ security and privacy. [...] (Emphasis mine. -Alex)

If you remember, T-Mobile is a founding member of the Open Handset Alliance (the governing body for Android). It’s disappointing that T-Mobile will be “protecting” customers by screening third-party applications. The robust home-brew apps for Android are important for many of people, especially those who would buy one of the initial offerings thanks to T-Mobile. I really wish T-Mobile would reconsider their stance on screening applications, but I’m not optimistic. I’m more hopeful that we’ll be able to flash our GPhones to use whichever Android build we’d like. That would be our heaven.

[ Read:  T-Mobile Wagers Deal With Google Is Worth the Risk - Wall Street Journal ]

google-and-sun.pngStefano Mazzocchi takes an interesting look at how Google is able to skirt around Sun’s various licensing traps for different Java platforms:

[...] Google announced the release of their Android platform, which would be able to run Java applications on a mobile phone but it would also be released under the Apache License v2.

This raised more than one eyebrowse, and sure did make me raise mine: how did Google manage to get Sun to license off a platform that could very well kill their own?

Turns out, they didn’t: their move was even smarter than Sun’s.

Today Google released the Android code and I took a serious look at its internals… and found the solution for the licensing problem. It’s called Dalvik and it’s the new name of Sun’s worst nightmares. [...]

I’ll spoil it for you: Dalvik is the name of Google’s Java-compatible custom virtual machine that runs the applications for GPhones. Stefano’s post is definitely worth reading if you’re interested in the licensing aspect of Android.

Today the official Android Developers blog went live!android_logo.png

One of our goals in releasing the Android SDK is to unleash the creativity of application developers on the platform. We’d also like to get feedback early enough that we can make changes before the first Android-powered devices are available to the public. We plan to release updates to the SDK regularly which means that there will be additions and changes to the APIs and user experience — subscribe to this blog to stay up to date.

We’re really looking forward to seeing all the amazing applications that developers will create on an open mobile phone platform. In fact, you may even want to enter your application into the Android Developer Challenge — a USD$10 million challenge sponsored by Google to support and recognize developers who build great applications for the Android platform.

Sergey Brin and Steve Horowitz discuss the availability of the SDK, that it will be open source in the future, and demo applications on the Android platform.

[YouTube]

The “GPhones” shown in the demo vid come in smartphone and touch-screen varieties. They also utilize 3G data speeds which offer quicker load times and more bandwidth for mobile internet access. The browsers are built on the WebKit framework (the same one used in Safari, Symbian OS, and KDE’s Konqueror browser). The Google maps API is used heavily, including street view on the phone.

In addition to the cool Google app, they also show off a demo of Quake running on OpenGL. So I think it’s fair to say it runs doom! The SDK is releasing today, so we’ll have more info soon.

Android SDK releasing today.

Just a reminder: Today is the day we are supposed to see the guts of the Android OS.

From the Android developer’s page:

We will make available an early look at the Android™ SDK on November 12, 2007. We invite you to visit us again at this time to download the SDK.

We view Android as a “living” platform and look forward to working with the developer community to continuously enhance and enrich the platform.


The tech web is going crazy right now with the announcement this morning of the Google-led Open Handset Alliance and their Android mobile OS. Right now the OHA is 34 members strong. A handful of partners in the OHA (including executives from Google, HTC, T-Mobile, Motorola) just finished a conference call to announce the phone and take questions from the press. As we learn more from this call, we will keep you up-to-date.

It’s confirmed that the Linux kernel will be the base of the phone. Google will be applying the Apache open-source license to the SDK, which doesn’t have a “copyleft” clause in it. This means developers can release software under the license without having to disclose the source if they don’t want to. This obviously helps attract more big businesses to develop software for the phone.

We at GPhoneholic have long been suspicious that the long-rumored “GPhone” will not necessarily be a branded Google handset in the traditional sense. Google’s bread-and-butter is in software. The Android announcement confirms that Google is working primarily on making the phone’s software while partnering with 33 other companies to help them accomplish a full spectrum of Android deployment. Right now there is no official “GPhone”, but rather the beginning of perhaps hundreds of GPhones manufactured and developed by the OHA.

We can expect to see the first Android-based phones in the second half of 2008. The SDK will be available starting November 12th, 2007, which is just one week away at the time of this writing.

Android will apparently include a robust HTML browser. And we shouldn’t expect to see it driven by Google adsense ads at any level other than the website a user may be visiting. Of course, this is still up to the individual carriers, since they have full control over what goes into the Android OS that they roll into their phones.

The minimum requirements for an Android-based phone are somewhere near a 200MHz ARM9 processor. Screen sizes can be either large or small, and keyboards can either be traditional 1-9 or QWERTY styles. And of course, there’s no reason why Android won’t work with the new 700 MHz frequency spectrum which will be up for grabs next year.

The UI is said to be very slick. Hopefully we’ll see a preview of what it looks like on November 12th.

Check out this video from Google on the announcement of Android:

This is a very exciting time for us at GPhoneholic. We’ve been covering Google mobile phone rumors for over 2 months here, and now it looks like the “GPhone” is finally going to become well-known with the public. I imagine we’ll be covering Android news much like a Windows Mobile or iPhone blog would for their respective operating systems of choice. Is this name of our blog still relevant? I’d say it’s good enough for now. Of course, we’re always open to suggestions.

UBS analyst Benjamin Schachter relays word from his colleague in Taiwan, fellow UBS analyst Arthur Hseih, that Google will be shipping approximately 50,000 GPhones on HTC hardware by the end of the year. The only catch is that these are apparently reserved for software developers.

“These initial phones are not going to be for sale,” Benjamin Schachter, one of the analysts who worked on the report, said in a phone call earlier today. “These are going to be available for developers only to understand how the software works.” [Source: CNN/Fortune]

GrandCentral.comWe have a grip of GrandCentral invitations for all of you readers out there! GrandCentral is a free (during beta, at least) service for attaching multiple devices to the same phone number, along with a killer voicemail system. I’m not going to go into detail in this post, but it’s worth mentioning that GrandCentral is apparently the “Hottest Mobile App Ever.” How can you argue with that? Think switching to GrandCentral as the first part of your transplant to the GPhone.

Write to us in the comments for this post if you’d like to receive an invitation to GrandCentral. Also, we’d love to hear from you on what you want in future postings on GPhoneholic. Your opinion means a lot to us.

Keep watching GPhoneholic this week. We’ll show you how switch only your voicemail to GrandCentral (so you could continue to use your current cellphone number). Nobody who calls you will ever have to even know that you switched any services.

Link: The GPhone Timeline.

Search Engine Land has been running a great GPhone timeline covering important events relating to Google’s various inroads to the phone industry. Sadly, –as of this writing– the timeline hasn’t been updated past August 28th, 2007. Still, it’s definitely a fantastic primer for anyone making attempt to catch up on what’s happened so far.

google_heart_jaiku.pngLast week Google bought Jaiku.com. Jaiku, which is similar to Twitter, allows people to stay connected online, wherever they may be in the real world.

Jaiku’s main goal is to bring people closer together by enabling them to share their activity streams. An activity stream is a log of everyday things as they happen: your status messages, recommendations, events you’re attending, photos you’ve taken - anything you post directly to Jaiku or add using Web feeds. We offer a way to connect with the people you care about by sharing your activities with them on the Web, IM, and SMS - as well as through a slew of cool third-party applications built by other developers using our API. [Jaiku | About Jaiku]

Of course, Jaiku seems to fit well into Google’s grand plan for the GPhone. Jaiku has already shown itself to be strong in the ways of mobile connectivity:

The most powerful instrument of social peripheral vision is your mobile phone. We’ve put in a special effort to create Jaiku Mobile, a live phonebook that displays the activity streams, availability, and location of your Jaiku contacts right in your phone contact list. We modestly believe it is the best solution out there for seeing what your friends are up to. Currently Jaiku Mobile is available for phones based on the Nokia S60 software platform (see the list of compatible devices). [Jaiku | About Jaiku]

As with most Google acquisitions and product launches, registration for Jaiku is now by invite-only. Luckily, I signed up for Jaiku right after the initial launch of the service back in early April of this year. Right now we have 10 invites available, so the first 10 people who request one in the comments will receive an invitation. First post, first serve. So hurry while they still last!

« Previous Entries