Connecting your Android phone to your computer to use it as a mass storage device isn't new, and we've detailed how and why you'd want to do it. But in Froyo, it gets a little more friendly. Gone is the bland pop-up announcement that you're connecting your phone. Actually, it's still there, but first you get the friendly little robot you see above, explaining in plain English what you're about to do. Mount the phone, and he turns orange. Unmount, and it's back to green. A nice touch, and it makes it easy to see at a glance if you're connected.
(Find a cool new feature in Froyo and want to tell the world about it? E-mail us here and we'll make you famous!)
Phil, Mickey and Jerry are joined by TiPB.com editor Rene Ritchie to talk all about Google I/O, Froyo, Android 2.2, Flash, Google TV and the all-out war between Google and Apple. Listen in! (Note that we recorded this before we actually got Froyo on the Nexus One. What a difference a day makes!)
Here you go, folks, the down and dirty walkthrough with Froyo -- aka Android 2.2 -- on the Nexus One. Remember that there's a lot of back-end stuff that's been optimized, and we're really just starting to scratch the surface. But here's a quick look at some of the highlights of the latest version of our favorite operating system. Have at it!
Now we don't mean to cause any undue alarm here, but check out the live wallpaper on the Nexus One above. It doesn't reproduce perfectly in the picture, but there's definitely some major color banding going on, just like we saw with the photo gallery in Android 2.1, first with the Nexus One, and later with the Droid, as the gallery went from 24-bit to 16-bit. I've been using that wallpaper exclusively since it came out, and this is the first time I've seen this on the home screen.
In fact, the ol' picture of Mars does the exact same thing if you plop it up as the wallpaper. Now we're not coders, but there's a pretty good bet there's some ones and zeroes being shared here. If someone wants to learn us a thing or two about this one, we're all ears. In the meantime, sound off in the comments. Anybody else seeing this?
Stop. Do not pass go. Now that you have Froyo up and running on your Nexus One, it's time to take part in the Adobe Flash 10.1 beta. Just click here in your Android browser, install it, and start watching Flash video, playing Flash games and doing all that other stuff that Android and Flash do so well. Huzzah!
For those of you who are running rooted and ROM'd Nexus Ones with a custom recovery module -- either Amon Ra or ClockworkMod or the like -- it's now stupidly easy to upgrade to Android 2.2 Paul at MoDaCo did the legwork. All you have to do is download his patched (and already rooted) version of Froyo, slap it on your SD card, and apply it per usual through the Recovery. No muss, no fuss, and you'll even keep your current settings, and it's a hell of a lot easier than rolling back.
Let's all pause from the Froyo mania for a second and ponder the above picture, brought to us via Howard Forums. This purportedly is the Motorola Shadow, which kind of looks like a mashup between an HTC and Moto device, borrowing a number of stylings from the former.
That's about all we know at the moment, well, that and it's about time we saw some new hotness come out of Moto. Thanks to everybody who sent this in!
One thing that apparently already is working its way out in the open (unlike the mythical Nexus One Froyo update that's only reaching a blessed few) is the new crash report tool for Android applications. We got a look at this during the keynote on Thursday at Google IO, and it's a nice little feature. If an app crashes on you, tap the "Report" button. Then you can send your system data directly to the developer, so they can figure out what happened. You also can leave "Feedback." Try to keep that constructive, huh?
Developers then get the bug reports and can act on them. Below is what we see. Pretty cool, huh? I've got the report feature on the Droid and Nexus One, but not the Evo 4G thus far. Thanks, @macprv!
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.
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.