And by "Google Phone" we don't simply mean another Android handset. We're talking about Google-branded hardware running a version of Android we haven't yet seen.

Over the next few weeks, Google Phones (most probably in early, prototype form) will flood the Mountain View campus. They'll don large LCDs while running a new version of Android—either Flan or the version of Android beyond it—which our source spotted running on Google's handset as well as a laptop. (Whatever the software was, it most certainly wasn't Chrome OS, we were assured.)

But maybe the most intriguing bit is what someone said to our source offhandedly, that the current Android, the we all know and love, is not the "real" Android. So what makes for a "real" version of Android?

Our best guess is an Android OS with Google Voice at its heart.

We've heard rumors like this before, but this time there are a few distinct elements that seem credible, maybe even enough to make us rethink our previous position. We're basing this all on Michael Arrington's sources—his article is a bit vague, but points to an outsider-made but Google-dictated device, sort of like how Microsoft's first Zune was actually made by Toshiba—and in the case of the Google Phone, there are a couple options for the possible manufacturer. The obvious choice is HTC, who's been the major hardware manufacturer of Android devices, but TechCrunch hears that the source of the hardware will be Korean, not Taiwanese, which likely points to either Samsung or LG.

Samsung has a long-standing relationship with Apple, supplying tons of parts for the iPhone, so maybe LG would step up to the plate and develop this phantom device. LG's no stranger to Android, but has been a minor player up to this point—maybe they've been working on this mysterious Google Phone in the meantime, which is supposedly aiming for an early 2010 release.

Right now, we don't know much of anything, so we're reaching out to you guys—if you've heard anything about a possible Google Phone, please shoot us an email. [TechCrunch]

Apparently, Android app developers could produce programs that needed a higher screen resolution than what the Agora was destined to have. That meant back to the drawing board for the Kogan team—unless they wanted apps to not work on their phone.

Anyone who pre-ordered an Agora will have their money refunded in full. Hopefully for all our friends down under, it won't take too long for Kogan to find a solution to this regrettable problem. [Gizmodo Australia]

Kogan Agora to be delayed

Melbourne, AUSTRALIA, 16th January 2009 - Kogan Technologies' Agora phone will be delayed indefinitely due to potential future interoperability issues.

Kogan Technologies founder Ruslan Kogan said the phone will undergo a significant redesign in order to ensure its compatibility with all future Android applications.

"The Agora reached a very late stage of development, manufacturing had commenced and we were within days of shipping the product to customers. But it now seems certain the current Agora specifications will limit its compatibility or interoperability in the near future," Ruslan Kogan said.

"One potential issue is that developers may create applications for the Android operating system at a higher resolution and screen size than the Agora provides in its current form.

"I am sorry for this delay, but in the interests of proving the best possible product at the best possible price, I cannot disappoint my customers by supplying a product that I am aware will shortly have significant limitations.

"My priority is to release a phone that will do justice to the Kogan brand and offer great value to our customers. Since the design of the Agora, the Android community has been growing quickly, with new developers setting out their objectives to create a host of feature-rich applications. I now believe that in order to access all the Android platform has to offer, the Agora must be redesigned.

"The Kogan team is already hard at work designing a new phone that will be better suited to the needs of Android application developers and our customers."

All customers who pre-ordered the Agora will receive a full refund.

Ruslan Kogan will continue to blog about and discuss the redevelopment of the Agora at www.kogan.com.au/blog

The OPhone is roughly 1mm bigger than the original iPhone in all dimensions, measuring in at 115.84x61.57x12.03mm. Besides the volume rocker, the OPhone also has its microSD slot on the left side. According to the China bloggers, it'll support microSD cards of up to 16GB.

The phone from the other side. This is supposed to be a dedicated camera button, which I guess makes the OPhone more comfortable to take landscape photos with.

Here's the butt of all three phones. As you can see, the OPhone's placed its headphone jack on its bottom. Also residing down there is the microUSB slot for charging and PC synchronizing. I wonder if that placement choice will render it incompatible with certain speaker docking systems.

On the backside is a removable battery, as well as a flash for the 5MP camera— two things it has on the iPhone. Assuming everything works like it's supposed to, this will be a serious contender to the iPhone and other smartphones. Guess we'll see Q1 next year. Merry Christmas from here in Asia! [Sina Blog]

After spending a week using the G1, I can say it's a good start, and a clear indication of good Android developments to come. But the phone itself has some serious problems with accessibility and usability, issues that no number of third-party apps are going to be able to solve. Here's what I loved and hated about the T-Mobile G1.

The Hardware
Body: The body was made by HTC, a Taiwanese company that makes Windows Mobile devices for Motorola, Palm and its own line. This phone is built just like those. The back is classic matted and grip-friendly HTC. The swivel-flip feels almost exactly like earlier HTC phones, only it extends out and then back in again, revealing the keyboard underneath. This motion gives a satisfying snap when opened, though it might be too loud in a quiet office.

Keyboard: It's got numerous problems. First, it's set so that the raised section on the right, with scroller ball and home and menu keys, is always in your way when you're trying to type. This is annoying, even after you figure out how to work around it. The individual keys aren't raised high enough over the body for easy touch typing, though at least the keyboard is backlit, in case you're texting in the dark. The space and backspace key are tinier than we'd like. And it's even more awkward than normal to type while charging the phone, because the miniUSB cable is in the way.

Buttons: There are five face buttons on the device—call, home, back, power/end and menu—and they're all fairly straightforward. Hit home to bring you back to the home screen, menu to bring up a popup menu in your current app, and power/end button to lock your phone or hang up your call. That last part takes the most getting used to, since you're naturally going to want to use the red power button to quit apps or end tasks, but all that does is lock your phone.

Trackball: It feels great, better than on the BlackBerry Pearl, and it clicks down solidly. Still, switching between the trackball and the touchscreen can get awkward.

Screen: The touchscreen is bright, renders text clearly and is, on the whole, pretty great. It uses capacitive touch, like the iPhone, so you use your fingertip, not a stylus, to poke around. There are cases when screen presses don't register properly—they're not too often, but often enough to be noticeable.

Battery: A full charge lasts about a day, mainly because push Gmail grabs the internet every time the account receives an email, and mine receives plenty. Couple that with 3G data browsing and app usage—which you're most likely going to be doing a lot of—and you'll need to get used to a mid-day charge at work. Thankfully charging from near empty to near full takes only about two hours.

Wi-Fi: The Wi-Fi range seems slightly to be on par with comparable smartphones (HTC's Windows Mobile phones, iPhone), showing just about as many Wi-Fi hotspots in my house as the other ones did.

3G: I got noticeably decent browsing speeds, with an actual test registering 433kbps. This, of course, is only the case if your city has 3G access at all, since T-Mobile's only just starting to roll out their network.

Camera: It's passable and on par with previous HTC efforts. It does have autofocus, but other than that there's nothing spectacular with the G1's camera.

GPS: GPS is actually off by default, which produces a very inaccurate location when you try and find yourself on Google Maps. You'll have to switch this on manually.

Other Issues: It's hard to fathom why HTC left out a 3.5mm headphone jack in 2008, same for USB mass storage mode for Windows or Mac. Really? You have to pop out that microSD card and use a card reader every time you want to load a ringtone or a song or a photo or a video? Seriously? Apologies, there actually IS a USB mass storage mode, but you have to use the bundled HTC proprietary mini USB cable. Any old mini USB cable won't do! But yes, it's possible. Also, when the screen is flipped open, it's tilted down about three degrees—really annoying to certain people who like clean lines.

Operating System and Usability
Calling: Making phone calls on this thing works well. Call quality is good, but the screen annoyingly times out after about 10 seconds. If you want to power on the screen again, you have to hit the menu key or the "call" key, which takes you to the dialpad. It may just be that we punch in our credit card numbers or find contacts during a call more often than most people, but always having to bring up the screen again is a pain. And pressing the power/end button, which you'd think would power up the screen, actually just hangs up the call. Annoying. But as for the actually making calls part? No complaints from us.

Texting: Texts are arranged per contact in threads, and works well enough since texting is so simple. No cockups here.

Stability: The one word I'd use to describe the Android operating system is "solid". It's been my main device for a week, and I've yet to see the entire OS hang or freeze (haven't had to reboot yet). Individual apps have crashed or frozen, but Android handles this spectacularly well by using the PC paradigm where you can choose to Force Quit a frozen app or wait for it to unstick itself. This way, very little can take down the entire phone under everyday use. (Buggy hardcore apps that snake deep into core functions could probably succeed.)

Background Apps: Multitasking is one thing Android does really well. Apps can run in the background, receiving data and continuing to "exist," even though you don't see them. The OS handles memory management for you invisibly, giving processes a lower CPU priority and taking away their RAM when other programs need it. For now, examples are simple, like opening a browser, then a bunch of other apps, then returning to the browser. You can use four or five apps before before the browser has to re-fetch data on the web page. Presumably, programmers will soon make more impressive use of the background processing power.

Window Shade: Google's most unique multitasking helper is the notification window shade, which serves as an infodump of all incoming emails, messages, IMs and missed calls. Tapping a notification will take you to its corresponding app. No matter what app you're in, the shade drops smoothly into place when you pull it down, dragging your finger from the top. (Just opposite the window shade is the pull-up app menu. If you run out of room on your three desktop screens, you'll be visiting here for lesser used programs.)

Long Clicks: One convention that's used often—but not consistently—is the long press. Long presses are a mix between right clicking and playing the lottery. Hold down an area of the screen—you may see a menu pop up or you may get absolutely nothing. Long click on the main screen and it asks you which app shortcut you want to move to your desktop. Long click on the text message screen and you'll be prompted to delete or view a thread. Long click on Google Maps or a page in the browser, however, and nothing happens.

Interface: As we have observed, the UI suffers from general usability issues such as inconsistent actions or surprisingly unclickable regions like the browser's URL bar or the home screen's clock. But when you use it, you realize it is kinda pretty. Like the window shade, many of the transparencies, transitions, fade-ins, fade-outs, popups and other UI elements are slick, and definitely win out in aesthetics over smartphones like Windows Mobile. Compared to the iPhone, it still loses, but this comes down to a lack of multitouch capability—on the G1, for instance, you zoom by clicking + and - magnifier buttons. Like I said, it's definitely a solid OS, but it also needs some real work by some UI experts to make it easier to pick up and play with.

Apps
Contacts: Phone contacts sync nicely with Google's Gmail contacts—great if you use Gmail, and an extra place to backup your contacts if you don't. You can even scroll through them fast by dragging a bar on the right. The problem though is that the quick-scroll dragger is hyper-sensitive, and holding your finger still in one place can make the phone jitter between letters. Each contact has a default phone number displayed under his name—when you tap a contact it feels like you're dialing his number, even though you're just pulling up details.

Mail: There are actually two mail programs on the G1: Mail and Gmail. Mail lets you manage five accounts, while Gmail makes you tie your phone to just one account. But Gmail is one of the best apps on the phone, giving you 90% of the desktop features you use on a day-to-day basis. Archiving, labeling, reporting spam, deleting and starring are super easy and sync to webmail almost instantly. The best part of this Gmail implementation is that it's push the only push Gmail on any mobile device (Helio's phones also have it). T-Mobile failed to mention its cool keyboard shortcuts—I had to fiddle to figure out that you can hit "r" for reply or "a" to reply all. (Surely there are more.) A dumb flaw is that it won't auto-complete names when you start with someone's last name. I have to sort through 10 Brians to find Lam's address, when I should be able to just type Lam and have this be smart enough to figure out who I mean.

Marketplace: The Marketplace is divided into Games and Applications, with sub-categories such as Lifestyle, Productivity, Shopping and Tools. Downloading and installing apps are pretty much 1-click, like the iPhone App Store, and most apps launch just fine. However, since most developers don't have an actual Android phone to test their apps on, a lot of programs will be sluggish or even crash-prone in the first few weeks. Expect this to be fixed soon.

IM: The IM app is a very good client that supports AIM, Google Talk, Windows Live (MSN), and Yahoo. It's intuitive, works well with the keyboard and even offers background notification—unlike iPhone—so you can switch to other apps but still get incoming messages delivered to you via the top status bar.

Browser: The G1 browser, like Chrome on the desktop, is based on WebKit, the open source browser engine that also powers Safari and Mobile Safari. This means it's pretty damn good. That said, the lack of multitouch gestures in Android's version makes zooming a pain. It doesn't have Flash support (YouTube gets forwarded to the YouTube app) and it doesn't auto-zoom to maximize the column you want to read in your display. It can, however, remember your password for logins, like a desktop browser does.

Google Maps: Gmaps has most of what you'll find in the desktop version, including Satellite, Traffic and Street View. Once you turn on GPS, the phone's fairly decent at locating where you are even indoors, and Compass View is a gimmick that works sometimes and doesn't work other times—but then again, spinning around like an idiot makes you look like an idiot all the time.

Music Player: It's no iPod, but the G1's built-in music player gets the job done decently. It fits in fairly well with the rest of the Android experience, but we're definitely looking at third-party apps like TuneWiki to pick up the slack here. That's not to say the Music app is bad—it's perfectly fine. It's just not great.

Third-Party Apps: Some of the more promising apps like Tunes Remote, TuneWiki and Video Player aren't as fleshed out and stable as we like. Tunes Remote lags and crashes a lot, TuneWiki can't find our music and Video Player only supports a handful of codecs. We expect these all to be fixed soon. Other apps like AccuWeather, Barcode Scanner and Pac-Man work just fine despite being developed on the Android emulator. We're looking forward to good things here.

Verdict
The G1 phone and the Android operating system are not finished products. There are only three working Google Apps here—Gmail, Maps and Calendar—while Google Docs, Google News, Google Reader, Google Shopping, Google Images, Google Video, Blogger and Picasa are nowhere to be found. What's the deal?

We have high hopes for third-party coders to fill in gaps Google intentionally or unintentionally left in this OS. There's already a video player, and we're sure VLC will try and port some kind of version over. But your question is not whether the phone will be great down the line, it's whether or not it's good enough for you to buy it now.

The answer depends most on who you are. Despite all the UI quirks and bad design decisions, it's still better than other smartphone OSes out there. It's not perfect, but for people who like tinkering, its cons are outweighed by its pros such as Gmail and the Marketplace. Hopefully Android updates and more ports of Google apps will augment not just future phones but this one too. This isn't something you're going to give your mom for Christmas, but if you're an adventuresome gadget guy with some money to spend ($179) on a totally new, pretty exciting venture, then why not?

Android: iPhone's Refugee Camp
While Android's open approach undoubtedly led some developers to pick it over the iPhone from the start, Apple's byzantine approval process and perhaps anti-competitive protection of its own apps—Podcaster and MailWrangler being two of the most prominent—have definitely driven some devs into Android's open arms, or at least made them stare longingly at it.

One such dev was the maker of the ridiculously popular Instictiv Shuffle app for jailbroken iPhones. Currently, iPhone apps aren't allowed to touch a user's music or iTunes functionality in any way. Instinctiv CEO Justin Smithline told us that "the minute we found out about the restrictions of the SDK...we started up an Android effort." Nevertheless it was clear in our interview that they loved the iPhone platform, using the word "amazing" more than once to talk about it.

Free But Not Equal
One of the original dustups around Android was that the 50 finalists in the Android Developer Challenge received early, privileged access to SDK updates that the rest of the developer community didn't get. While it makes sense that Google would want to fast-track Android's potential killer apps in time for the launch, it also goes against Android's atmosphere of openness.

It seems like there is some favoritism—whether it's toward specific devs or just toward the best apps is uncertain. TuneWiki is a finalist and one of Android's 10 most exciting apps. Amidst complaints about the lack of updates to Android's SDK until the recent 0.9 release and Google's secrecy, TuneWiki CEO Amnon Sarig told us that "I cannot say good enough things to say how [Google] treated us. They gave us whatever we wanted. They want us to succeed."

Since TuneWiki looks like it'll be a fantastic app, it's hard to argue with this—why shouldn't Google devote the most resources to the best and brightest, the stuff that'll make its platform shine? Logically, it should, given how much of the platform's success ultimately lies in the hands of developers. Depending on how you see Android's raison d'tre, that might be deeply troubling philosophically, on the other hand.

Nuts and Bolts
One thing that every developer we talked to pretty much agreed about is that coding for Android is not exactly warm robotic apple pie. While it's commonly assumed that Android development is done using run-of-the-mill Java, the developer of BreadCrumbz—a very cool image-based navigation app that's one of the 50 finalists, told us that the Android framework is actually "very different" from a regular Java stack, so that even "experienced Java developers still need to learn." TuneWiki's devs agreed that there's a learning curve, but both said that since it's still Java at the end of the day, it's a short one.

Instinctiv was more down on Android Java, compared to iPhone OS X, when it came to porting their app. When we talked to them before the release of the 0.9 SDK, they said that "Android is a mobile OS unlike the iPhone system, which is really kind of a desktop OS." Because of Java, they lamented that it'll be hard for Instinctiv Shuffle to do any really heavy lifting without bogging the system down, so they didn't think they'll be able to make it "as personalized" as the admittedly outlawed iPhone version.

Access to hardware appears to be much better than with the iPhone SDK, even though BreadCrumbz's Amos Yoffe says that Android "doesn't let you access the hardware directly, you go through Java APIs which are abstracted from the hardware." He still says that it's "pretty good." TuneWiki devs raved that "Android doesn't sandbox you like Apple does, so you have more flexibility." Apps run in the background just fine, battery drain issues aside. And conversely to this freedom, security policies and threats should be interesting (and maybe terrifying for nail-biter types) to watch develop, though at the start, Android seems to strike a good balance between security and freedom (insert current events political joke here).

Flexibility is a huge thing for Android. One of its strongest points—that it's going to run on a ton of phones with a rainbow of specs—might also prove to be one of its weak points, and perhaps the biggest challenge for developers. TuneWiki's Sarig said that since the Dev challenge only provided them with a single set of specs, no one's had to deal with the issue yet. It's definitely looming, however.

He admits that they're going to "have to scale back for less powerful handsets," though he doesn't know to what extent, since no one's seen the pile-of-rusted-bolts end of the Android hardware scale. BreadCrumbz's Yoffe says that "it's a bit early to say" if performance variance between handsets will be an issue, no one will really know "until we get our hands on real Android hardware." The G1's hodgepodge of interface methods—touchscreen, QWERTY and trackball—perhaps not so coincidentally gives developers a chance to experiment with multiple ways to interact with their app using a single device, though having to account for them all necessarily adds layers of complexity and consideration to creating apps.

Android vs. iPhone: The Final Battle
Pandora CTO Tom Conrad, who famously said "I need Android like I need a hole in the head," actually takes a more measured approach to the platform war. He told us that "Generally, when I look at Android and the challenges we faced bringing Pandora to handsets," it doesn't seem to solve them. "It just adds another one to the mix."

Critical for Android's success is an easy-to-use app store and the killer apps to stock it. Conrad noted that while Pandora had been on a number of low-end phones for over two years, within 24 hours, their iPhone app had surpassed all of those users combined. They are currently taking a wait-and-see approach with Android, though he stressed that "absolutely, we want Pandora to be everywhere there are listeners." TuneWiki similarly wants to achieve multi-platform ubiquity, though they're much more juiced about both the iPhone and Android, saying, "We love them both."

Whoever wins, it looks like the carriers will lose. Every dev agreed that the iPhone sparked a revolution that is changing the way US carriers operate. Android is a part of that now, and the two, even locked in competition, will push that revolution further. In that sense, at least, we all win something.

Let's start with the obvious: No Exchange server means no corporate push email. This didn't catch us off guard, as there were rumors that the G1 would launch without it. However, we were surprised by the sheepish looks on the Google executives' faces when reporters pressed the matter. "We expect this to be solved by third-party developers," was all that they said. Yes, it is true that some very nice mobile email management has come from third parties such as Good (now owned by Motorola). But the fact that the Android team isn't spearheading the integration of push email means it doesn't think of enterprise apps as a priority.

Jump from there to the lack of desktop syncing. I am with all the people who like the fact that mail and calendar data syncs over the air (for "free")—it is a great consumer service. But if you can't connect to an exchange server and desktop ActiveSync to Outlook is out of the question too, well, that means hordes of suit-wearers will simply have to say "no" to this device.

As if that wasn't enough of an ix-nay for IT buyers, Android's security issues are pretty significant. Because of the open-source nature of the OS, programmers have access to core functionality they wouldn't be able to access when dealing with platforms such as BlackBerry, Windows Mobile or the iPhone's OS X. True, like Windows Vista, the system is designed to ask you to grant new applications permission for each and every capability that an app desires, as you can see above. But it's easy to say yes to things you wouldn't necessarily understand. Is it bad that an app I don't know well can "modify global animation speed"? Honestly, I don't know.

Update: What we meant was open, not open source, as in more freely accessing parts of the hardware that apps don't necessarily need to access. An example would be a rogue flashlight app that you happened to grant permission to access your microphone, and it theoretically records your conversation with your coworkers.

More importantly, apps with that kind of access can easily muck up the rest of the system, like so much crapware on a new PC. An app full of weird conflicts doesn't have to be malicious to be disastrous. The Android Market is a place to get Android apps, but Android apps will be available from any source, and you'll be able to install them directly. It's good news for tinkerers who know what they're doing, and it does support the free-market approach for distributing software, but it could easily lead to brickage of company property.

IT pros look for certain security features too, such as the ability to remotely wipe a lost or stolen phone's memory, or to establish a virtual private network. Trusting third party apps for this isn't a problem on paper, though shopping for, vetting and deploying competing applications as they're developed could easily create as many problems as they're supposed to solve.

The trouble with leaving core features to third-party developers is that it often leads to nasty blame games. Microsoft has gotten in the most trouble in the past when it launched software platforms—a good example would be the PlaysForSure music DRM—then refused to take responsibility when third-party developers failed to implement it successfully for users. It's a built-in cop-out, and that may work for daring nerds with extra cash and a disdain for status-quo devices, but it doesn't work for mass-market consumers, and it certainly doesn't work for the most skittish buyers of all, corporate IT dudes. Sorry Google—I for one would like to see a little more stewardship, and an acknowledgment that if Apple can implement Exchange, VPN and other corporate goodies, well, you got no excuse.

We just got an early hands on with T-Mobile's G1 Android and yes, it does look as nice as it does in the photos. The screen is fantastic, and it's actually not as chunky as it looks, but it's definitely not iPhone-skinny. You can see the Sizemodo here, and we'll have even more details and a more in-depth hands-on in a bit. UPDATE: Updating hands-on impressions live, right now. UPDATE 2: Now with full video walkthrough and even more impressions.

In your hand the G1 feels good. Solid and all-plastic, but not nearly as clunky as the blurrycam photos showed. Getting used to the controls takes a little bit—babies can't pick up and instantly know their way around, like on the iPhone. Control wise, it suffers from a bit of schizophrenia—with a trackball, touchscreen, candybar mode and flip-out QWERTY, there's a lot going on at once. What's nice is that it seems to not lock you in to anyone type of control interface—scrolling with trackball and touching work at the same time in many apps.

Physically, the flip-out LCD feels solid and springy. Keyboard keys are small, spongy and a bit recessed, so it's hard to touch type right off by the feel of the keys. The touchscreen is better than we had hoped—far better than the HTC Touch's slow-to-respond screen. Scrolling is smooth at times, clunky at others, depending on the app. It's not multitouch, so it uses a "long press" UI element quite a bit—like to drag an app from the pop-out menu to the desktop—but since the touch is fairly responsive, it works pretty well.

You use the menu button a lot, more than we'd like. For instance, in the browser, our instinct—kind of biased one, admittedly—is to touch the top of the screen to pop up the URL. Here, you've gotta press menu. Same with any other app, to do pretty much anything. It also pulls the Palm move of having the home button be separate from the power/lock button, so if you push the red button instinctively to kill an app, you're just going to lock your phone.

Browsing: It may just be that we're not comfortable with it yet, but the browsing is kind of cludgy. Again, control is an issue - lots of UI to fight through. Scrolling and zooming around a rendered page is a bit jerky as well, but on par with Opera Mini and similar mobile browsers. The touch zoom buttons don't work as intuitively or respond as tightly as they should. Even though they're both based on Webkit, it's not as smooth as multitouch Safari, yet. Scrolling around web pages with the trackball is definitely smoother and more intuitive, immediately, than using the touch screen.

Google Apps: We didn't have a Gmail account loaded, so we couldn't see incoming messages, but the app looks minimalistic and was snappy. Text input is with the QWERTY keyboard, as it is with every app right now. It's kinda subdued, missing the colorful bubbly design of the Gmail Mobile app for other phones. Interestingly, there is a Google Talk service active within the IM app, even though we had heard from the Android Devs that GTalk was not making it into the first version of the software.

Maps is top-notch—we found our location within a few seconds indoors on Manhattan's far east side with combines GPS and cell-tower. It's incredibly optimized, perhaps the smoothest app experience we've had yet. And Compass View, which uses accelerometers to predict where you're pointing the phone to scroll around Street View accordingly, is rad—augmented reality, here we come.

There is no native Docs app in the first release.

Android Market: Android Market appears to be fully functional—we grabbed Pac Man and installed it over the air with 3G. Overall it seems like a very, very similar experience to the App Store—downloads once under way get kicked to your notification tray for progress, and they appear in your main app pull-out drawer when finished. Pac-Man started up immediately.

Here we grab Pac-Man:

Apps in the Background: Background apps are handled with a system-wide pull-down notifications drawer in the upper left corner. When we received an IM while in another app, the sender's name blinked and we could pull it down to view. Downloading apps also appear in the notifications tray.

Multitasking is handled in an interesting way - apps never truly "quit." According to Dan Morrill, one of Google's Android software guys, it seems In most cases, the actual GUI app that you interact with on the phone (say to view your IMs) runs independently of code at a deeper, service level. That way, you don't have to be running the GUI for an app to still have it function. A task manager shows you the six most recent apps, but beyond that, the system handles which apps quit and which ones stay open entirely by itself, based on memory usage needs.

Headphone Jack: Yeah, there isn't one. You'll have to use a USB adapter. Which isn't included. Sigh.

Music App: Not the prettiest. Integrates cover art nicely if it's there and gets the job done with sorting by album, artist, playlist—the usual. Speaker is nice and loud for when you don't have your USB adapter. All music and media has to be side-loaded and read off an SD card, and it'll have a 1GB one included.

Amazon MP3 Store: The interface is extremely well designed, and incredibly easy to use, just as good as iTunes Wi-Fi store on our first impression. It's tied to your Amazon account, so you can buy with 1-click. You have to be connected to Wi-Fi to download it on the spot, but you can buy anytime. We actually tried to grab a song with our account, but ran into the SD card problem (as you can see in the gallery). Add in some over-3G-downloading, and it'd be golden.

Dev Tools: Befitting an Linux device, the shipping G1 will feature a debug mode that, when tied to a PC via USB, allows for plenty of tinkering with apps. Security layers prevent you from futzing with the core code and application and service data, but if you have privileges, you can develop directly on the phone.

Another interesting feature is ability to install applications from a non-Android Market source. That means that it will be possible to download full applications directly from developers and install them independently from the Market. Core security again blocks apps that violate terms of services (VoIP or Amazon MP3 downloads over 3G are both confirmed no-nos), but awesome to see that the software is so accessible without any prior approval.

1. It's open! The single best thing about Android is that's a modern mobile phone OS that's also almost completely open, unlike some other locked down mobile OSes. (There are a few restrictions in accessing the hardware for security reasons.) It's based on Linux, and once Google has released Android, most of it will be totally open source, so it'll be incredibly easy to dive into its guts and mess around, which will help build a robust developer community, along with all of the other benefits of using open software. Most of its other awesome traits grow out of its openness, actually.

2. We'll keep the Steve references to a minimum here, but Android will accelerate the process that the iPhone helped kickstart last year—the gradual devolution of carriers to open, dumb pipes. Before, carriers controlled every single facet of what a phone could and could not do. They still do to an extent, and it's not completely "anything goes" on the iPhone and Android, but together they have and will make the mobile landscape change far more rapidly than before. As Opera CEO Jon von Tetzchner told me a few days ago, just a few years ago, carriers thought that the idea of full internet access was ridiculous, not to mention dangerous, threatening the obscenely lucrative business they have set up around minuscule bits of data like text messages, crappy "web portals" and ringtones. Android phones will be constantly connected and totally revolve around the internet, incessantly sucking down ever cheaper data—a carrier's worst nightmare not so long ago.

3. You'll have tons of hardware options. Android's designed to be versatile, so lots of manufacturers will be putting it on lots of phones—ones with QWERTY keyboards, touchscreens, T9, outrageously spec'd out phones, as well as ones that are kinda crappy in the spec department, actually. But this also provides a common platform for developers, making it easy to put their apps on millions of phones. It's the benefit of any OS that runs on a lot of hardware—like Windows or Linux, etc. Of course, this is also the Windows Mobile argument against all of the other proprietary OSes like Palm and BlackBerry.

4. There's even more potential for amazing apps than the iPhone, because developers are almost completely unencumbered by arbitrary rules and restrictions. So awesome apps like Podcaster or Instictiv Shuffle won't be mercilessly killed for not fitting into a tightly controlled framework or navigating a byzantine approval process.

5. It'll have the best Google apps experience of any mobile device, and play super nicely with Gmail, Gcal, Maps and everything else Google puts out. Or at least it damn well better, since you know, it's Google's baby. Simple, direct syncing with Gcal is tops in our list, since doing it on the iPhone requires sacrificing a goat while chanting from a book covered in the skin of baby unicorns.

Bonus reason: Not an iPhone. And our software geek sister Lifehacker has some more too.

1. Google can see into your soul. If you've ever been wary about how much Google knows about you, how are you going to feel when they're all over your cellphone? While a lot of the reason Android came to be was just to get people really using the internet on their phone (because when people use the internet, they use Google), we won't be surprised to see contextualized local ads, kind of like the sidebar ones you see offering you a date from hot local girls in Brooklyn or whatever hovel you're holed up in. But this will be hot girls just around the corner, since the phone will know where you're at.

2. It's not on the US's two biggest carriers, AT&T or Verizon. Statistically speaking, you've got one of them. But so far only the two runts of the majors, Sprint and T-Mobile are going to have Android phones. T-Mobile's 3G network is pathetically tiny compared to the other three, and well, Sprint's the only carrier actively losing subscribers, if that tells you anything. It's possible we'll see some Android action on Verizon's mythical open network though.

3. Buuut, carriers still have the right to gimp Android to their liking, precisely because of its Apache licensing. So a Sprint Android phone could have its built-in "store" stocked only with, say, Yahoo! apps—or no store at all. In Verizon's hands, the UI could still look like it fell in a bucket of gaudy red paint.

4. Android is designed to run on a ton of different of hardware—phones with and without touchscreens, with and without QWERTY keyboards, phones with amazing specs, crappy phones, and everything in between. While this is a strong point as mentioned above, it could also be a point of suckiness. That means there won't be a consistent Android experience, and it'll depend heavily on the device you're using. Devs told us that you'll likely see different versions of their apps, so that on weakass phones, you'll have more diluted apps, which might be an issue for people picking up a cheap Android phone expecting to do everything a more expensive one will.

5. Relying too much on developers to fill in features could result in a phone that's not quite totally seamless and consumer-grade across the board. For instance, from what we've seen in the SDK, there's not a built-in, Google-made media player. It's rumored that the excellent TuneWiki will be Android's default player, which is great, but doing this for too many key features could make things a bit bumpy, since you're talking several developers instead of just one.

Bonus reason: It's not an iPhone.

The reporter noted that “The trio of Google execs also used the opportunity to talk about the inroads the company is making with its own branded mobile phone as a replacement for the iPhone.” [That appears to be a mix-up by the reporter, with Sergey and Larry actually talking about not producing their own phone, according to Reuters's Ken Li's notes in SAI.]

But, TechCrunch does have its own source, who "swears" that the Ammunition Design Group "is designing the Gphone and that it is a seriously beautiful device." They've worked with companies like Palm, Hewlett-Packard, Dell Computer and Logitech in the past (a phone they designed for Sprint is pictured above). Not a confirmation by any means, but TechCrunch usually has decent info—so take that for what it's worth.

The more probable explanation for any sort of design work on a handset for Google is that they could be prototypes for marketing or other promotion—no one can make the call whether it's for production yet. [Tech Crunch and Mediaweek via BGR, Silicon Alley Insider]

Assuming that the phone really is in production and will be delayed until 2009, that leaves the question of whether the Android platform as a whole will be delayed, since many other manufacturers besides Google are planning their own phones. Krakow's source doesn't say, which probably means it's still on track. Either that, or horribly, horribly delayed and the guy doesn't want to induce a panic. [The Street]

Update: Google spokesdudes say that the Android platform is a-okay.

We're still on track to announce Android-powered phones this year. Some of our partners are publicly stating that they plan to ship Android phones in the fourth quarter.

Well, the HTC handset is around five inches long and 3 inches wide with a keypad that either slides or swivels out to make emailing, note-taking and writing Web addresses easy. The Internet is navigated via controls below the screen. So, that's just like a generic HTC phone, then.

The source of the current leak, described as "a person close to the situation" (ha!) claims that the handset will be available around the end of the year, although HTC is staying schtumm on the matter. "We cannot comment on this product," their rep said.

HTC will be facing competition from Samsung. The Korean electronics giant is, apparently, wetting its knickers to get its Google phone out before that of HTC. [Yahoo!]