So here's the thing: TechCrunch's M.G. Siegler apparently awoke to an over-the-air update of Android 2.2 (Froyo) on his Nexus One. And immediately, everybody and their mother started posting "Froyo being pushed out to the Nexus One!" Thing is, only a scant few people seem to actually have gotten the update thus far. So maybe it's being pushed out, and maybe it's not. Let's all take a deep breath, m'kay?
If in fact it is on the way, we'll have the manual update location shortly, and we'll bring you the instructions, just like last time, so you don't have to wait on the OTA update.
For those of you who are running custom recover modules (such as Amon RA's or ClockworkMod, it's noted that you're going to have to go back to the stock recovery to update Froyo.
For what it's worth, I've rolled back my N1, and no update's come down yet. The fact that a tech journalist got an update certainly is a hell of a coincidence, but maybe I'm just jealous, huh? Anyhoo, sound off in our forums if you find out anything. And for the really adventurous, there's an entire thread at XDA Developers of people saying they don't have the update. [via TechCrunch]
We got our first look at the Samsung Galaxy S and its gorgeous (indoors, anyway) Super AMOLED screen at CTIA in March. And Sammy was showing it off again this week at Google IO. Not much else to say other than that. Same great screen. Same OK (we'll reserve judgment until we actually get to use it at length) Touchwiz 3.0 user interface. And we still want to get that Super AMOLED screen into the sunlight to test out the claim that it has 80 percent less reflectivity than its AMOLED cousins. Anyhoo, check it out again after the break.
There's a bit of a fuss going on at the moment about a slew of new HTC code names. Engadget spilled the beans about the Glacier, LED and Vision -- and that's about all we know. The Vision appears to be slated thus for for T-Mobile, but that could be the European variety as much as the U.S.
Then today Dutch site Tweakers.net snags the user agent of the Vision, which points to a QWERTY-keyboard device with a 480x800 screen, and it may well be a version of the Desire with a keyboard . (Though we'd expect more differentiation than that, and we can't help but think of that slider we recently saw go through the U.S. FCC.) Anyhoo, that could well point toward a proper slider Android device from HTC (look, the myTouch 3G Slide is nice and all, but ...) so we can all quit hacking Eclair atop our aging Touch Pro 2s. [via Engadget and Tweakers]
You guys want us to do an unboxing of the Sprint Evo 4G? Fine. We'll do an unboxing. And we'll do it live, in living color, with stereophonic sound. Maybe snakes will fly out. Maybe it'll be a gruesome scene. We don't know. We haven't actually looked yet (though we have a pretty good idea of what's in there). Anyhoo, check back tonight at 7 p.m. EDT, and we'll give you what you want.
Get a bunch of execs on stage -- Micrososoft, Google, Apple, whomever -- and people are going to try and cause trouble. Same goes for the Android team at Google IO. Asked to compare the Android "tactics and maneuvers" to the Mac-PC wars of the 1980s and '90s, we get another beautiful line from Andy Rubin (seen here at left).
"From my perspective, we're lovers, not fighters. So it's hard to describe it as a war. And you know the lover's munition? Open source."
Indeed. Look: From a business perspective, you have to consider your competitors. And Google does that better than many. But to think for a second that a major company continues to develop its entire mobile strategy in response to the iPhone is just ridiculous. (BlackBerry Storm notwithstanding, of course.) The iPhone woke up a lot of people, but it's not what keeps them up at night any more.
See here! There's the Bump contact-sharing Android application. And it's just like it sounds: Bump your phone against another with the app, and it shares the info. Oh, and see that iPhone cowering in the corner? It's there for a reason. You can now Bump from one platform to another, which has to be some crime against nature, right? Check it out after the break.
First things first, these screen shots are really easy to fake. Ridiculously easy. With that out of the way, it looks like a settings screen shot is showing a T-Mobile Motorola Cliq running Android 2.1. As in the 2.1 you guys hope and dream for. We know that Motorola has planned for the Cliq to get Android 2.1 in Q2 2010 sometime but as all Android users who've been waiting for 2.1 know, you never really know until the update is right there on your phone waiting to download. Maybe it's T-Mobile and Motorola testing it out? Or a rogue user finding a way to update himself. Hopefully it's coming soon. Because by the end of today, you guys will all be clamoring for 2.2. What a vicious cycle. [android community]
Good news, everyone! We found our first giveaway item for this week's podcast. (Here's another contender.) But you'll have to be there live to win. Join us at 7 p.m. EDT / 4 p.m. PDT at androidcentral.com/live for the Google IO wrap-up. And don't worry, we have more stuff to give away, too. See you there!
Yes that is a real picture, even though it's blurry as all get out. (Never claimed to be a photographer :P) No, I didn't get a magic OTA from Phil while he was at Google I/O, it's a 2.2 SDK emulator virtual machine ported over to run on the Nexus One. I'm not the only one doing such outlandish things either. It's mostly for the novelty, and now I can say I have FroYo on my Nexus. It crashes (a lot), not much works, and it's a real PITA to do, but for those who feel the need, links, instructions and a couple more pics are after the break.
Google I/O started off a little slow on Wednesday, but boy did Thursday take over, with the announcement of Android 2.2 -- Froyo -- and Google TV. Here's what we've posted thus far. And while we're headed home from San Francisco, we're not done with the news just yet. More to come.
"The web store as a direct distribution model is really a very small part of the overall Android strategy. With the Nexus One we had the objective of bringing to market a very technologically sophisticated phone, which we did, which really set a new bar for quality. And I think you've seen a lot of the phones in the market today, that have come to market in the past few months, have been influcing, in many ways ... by what the Nexus One was able to do.
"The web store was another element of the strategy. It was, in many ways, an experiment for us. ... Android was in a very different place six months ago. ... And today, we believe that the right thing to do from a distribution perspective is different from what it was a few months ago. And so we've chosen to double down on our partnerships ... we're focusing on building great technology -- being an Internet software company -- and working with our partners on distribution."
Andy Rubin followed up with a great explanation with what goes into working with carriers. Check it out after the break.
I'm pretty sure I could probably fly myself home after spending a few minutes with Laminar Research's X-Plane Android flight simulator (this is no mere "app"), which we toyed around with at Google IO. You have seven airplanes -- Piper Malibu, Beach King-Air, Eclipse Jet-500, Piaggio Avanti, Cirrus Vision, Cessna 172 and Columbia 400 -- from which you can choose, and it features custom terrain (no Google Earth here) and even shows where lift is affecting the aircraft. It's not available yet in the Android Market because they're waiting for a few technical issues (with the Market, not their app) to be resolved. But hopefully we'll see this soon. Check it out after the break. Anybody want to navigate for me?
First question out of the gate today for the Android leadership at Google IO was about everybody's favorite subject: fragmentation. And VP of engineering Andy Rubin put things in perspective:
Some of the press has called this "fragmentation," and that's probably the wrong word for this. The better word for it is "legacy." These phones and devices ... the iteration ... is incredibly fast.
And when we stop to think about it, we like that term. It's not all fire and brimstone like you guys are looking for, but it's the way it is.
Look, that's really not going to make a lot of you happy. But that's just the hard truth: These phones are progressing extremely fast. At some point yours will be old. At some point ours will be old. And we'll all have to live with that.
A small programming note, people: Due to our regularly scheduled Android Central Podcast falling smack in the middle of Google IO/cross-country travel, we're going to push it back a day this week. So, no podcast tonight. Instead, join us Friday at 7 p.m. EDT / 4 p.m. PDT as we wrap up all the week's Android news -- including Froyo and Flash -- and we might even have a few special treats to give away. We'll be at AndroidCentral.com/live. See you Friday!
Portions of this page are modifications based on work created and shared by the Android Open Source Project
and used according to terms described in the Creative Commons 2.5 Attribution License. AndroidCentral is an independent site
that is not affiliated with or endorsed by Google.