Editor's note: We used Cover It Live for this event, so if you missed the live blog, you can still replay it in the embedded component below. Replaying the event will give you all the live updates along with commentary from our readers and a few CNET editors. For those of you who just want the updates, we've included them in regular text here. To get the key points from today's announcements, you can check out our summary of what got announced,.
Google's Android Day managed to get upstaged by another announcement: Google TV.
Earlier today, we provided the live coverage below of the second day of Google I/O earlier on Thursday. As expected the keynote focused heavily on Google's smartphone operating system, with references to Adobe's Flash player and shots at Apple's strategy galore. But Google TV--an Android adaptation that puts regular television and the Web in one user interface--stole the show, complete with support from some of the consumer electronics industry's biggest players.
8:23 a.m.: Welcome back! Day 2 of Google I/O is almost ready to begin, as the Running of the Geeks takes over the third floor of the Moscone Center. It's expected to be all Android, all the time, and I think it's safe to confirm those Smart TV rumors: Intel CEO Paul Otellini is front and center.
8:28 a.m.: The place is amazingly full for an 8:30 a.m. event after the conference party the night before. Your comments are flying in fast and furious, hang on a moment as Josh gets up and running. To answer a few questions, it's not clear whether 2.2 will be available today, perhaps for the N1, but carriers tend to control the pace of the updates for other phones.
8:29 a.m.: Josh manages to get our Sprint card software up and running on his Mac, but only after Boot Camping to Windows. "Windows 1, Mac 0," Josh says, kicking off the first fanboy battle of the day.
8:34 a.m. (Stephen Shankland): Danny Sullivan from Search Engine Land says Eric Schmidt is at the keynote. Schmidt would have to be there given Otellini's attendance, otherwise there would be a protocol parity violation and the universe would implode.
8:35 a.m.: Lights going down...
8:36 a.m.: Vic Gundotra comes back out, hoping people enjoyed the party last night. 24,000 people watched the stream on YouTube yesterday, Vic says. He's going to start with a story: his first day at Google.
8:37 a.m.: That first day, Vic met Andy Rubin, the head of the Android project. At that point Android was a secret, Vic says, and after Andy's pitch Vic expressed skepticism: why does the world need another operating system? Andy's response? 1. It's critically important to provide a free open-source operating system, so hardware makers can build whatever they want.
8:38 a.m.: 2.: Rubin said that if Google didn't act, "we faced a draconian future, where one man, one carrier, one device would be our future," Vic says, with a picture of George Orwell's 1984 book. The clear allusion is to Apple and Steve Jobs, and developers respond with a healthy cheer.
8:39 a.m.: Vic says Android partners have made over 60 compatible devices, although he doesn't say anything about how fragmented those different devices might be. 21 companies are making Android devices in 48 countries on 59 carriers.
8:40 a.m.: Last year, Android partners were selling 30,000 units a day. In February, they were selling 60,000 a day. As of this point, 100,000 Android phones are being activated a day. Android is now second in U.S. smartphone sales, second only to RIM. According to AdMob, Android phones are first in Web usage.
8:42 a.m. (Stephen Shankland): I'll be interested to see Android incursions into feature phone market, not just iPhone-class devices.
8:42 a.m.: Vic says that Android users have navigated over 1 billion miles, although I'm not sure how they know that. "There are some who say people don't use Google search on smartphones," Vic said, in the second shot at Steve Jobs in 10 minutes. People are searching on smartphones with Google, Vic says.
8:42 a.m.: So how will Google and its partners keep this going? With 20 demos! Seriously, 20?
8:43 a.m.: Vic officially announces Android 2.2, code-named Froyo. It has five pillars that we're about to run through.
8:45 a.m.: Speed is the first. Android is built on the Dalvik virtual machine. "We have big dreams for Android, and part of those dreams means Android will go to new places with new chip architectures," Vic says, 15 feet away from Intel CEO Paul Otellini. Froyo will ship with a just-in-time compiler that will speed up application performance by 2x to 5x, Vic says. They're about to demo a game, running on the same hardware but with one phone on Froyo, and one on Eclair. The Froyo phone can maintain 40 frames a second because of the compiler.
8:46 a.m.: The second area is the enterprise: and those people want specific features, Vic said. There are 20 new enterprise features, and one of them is Exchange-friendly technology: auto-discovery, security polices, and GAL lookup. These phones are also getting remote wipe.
8:47 a.m.: Developers will have new services to use: such as an application data backup API. Android backs up applications when moving to a new phone, but not the data. Froyo will allow developers to move data with new applications.
8:49 a.m.: Shot number 3 at Apple: Google announces a cloud-to-messaging API that "is not designed to compromise" for the lack of multitasking. Vic demos the API, showing how a desktop in Google Maps can send directions to his phone with an "Android intent." That's not a text: it kicks the device into navigation mode automatically once it receives that intent. The crowd likes it.
8:49 a.m. (Josh Lowensohn): Did Vic just say "boom"? I've heard that on another company's keynotes...
8:49 a.m.: "That's how you do a cloud-to-device API," Vic says. He brings up another example where you can send an article you're reading on your desktop to your phone, which automatically brings up the article on your phone without having to press any other keys. "We can't wait to see what you're going to do with this API."
8:50 a.m. (Stephen Shankland): Cloud-to-device messaging API in Android reminds me of WebSockets in HTML land. I wonder if it's related. It'll certainly help once Chrome OS arrives.
8:50 a.m.: "You're going to love this," Vic says: Tethering and portable hotspot.
8:51 a.m. (Josh Lowensohn): It's fitting they're demoing this with an iPad.
8:51 a.m.: "You should be able, at the platform level, to enable tethering." Android devices will be portable hotspots, and we're getting a demo: a Nexus One enabled as a hotspot.
8:52 a.m.: Now we're moving onto the browser. The most popular thing people use smartphones for? Phone calls, text messages, and Web browsing. That means Android has to constantly improve the browser, and Google has improved the performance by 2x to 3x: Froyo is getting the V8 technology from Chrome.
8:53 a.m.: Demo time: A Froyo machine, an Eclair machine, and an iPad. Guess which one is going to look bad. They are running benchmarking tests on all three machines. They start the iPad first, just for kicks, and believe it or not, its browser is slower than the Android machines.
8:53 a.m.: This keynote so far is one big running joke at Apple's expense.
8:54 a.m. (Josh Lowensohn): Which means we're probably never going to see Google Nav on the iPhone...
8:55 a.m. (Stephen Shankland): I wonder when Google will brand the Android browser as Chrome, like Apple did from the start with Safari on iPhone. Google is usually pretty smart about brand equity.
8:55 a.m.: "Froyo has the world's fastest mobile browser," Vic says. They're working on ways to get more capabilities that are usually reserved for native applications and get those into Web applications, like the camera or accelerometer. Google will demo some of the more advanced browser features not available in Froyo. They demo a Web maps application that can rotate with the accelerometer.
8:55 a.m. (Josh Lowensohn): Funny you should say that Stephen, b/c the current Android browser icon looks like Mozilla's minefield.
8:56 a.m. (Stephen Shankland): I wanted that orientation feature in the Nexus One I was navigating with two days ago. Had to hold the phone backwards when I was walking around.
8:56 a.m.: What about uploading pictures to Google Buzz through the camera? The demo gods fail Vic this time, but the idea is to let Web applications access the camera.
8:57 a.m.: Mobile devices should be platforms on which people use voice input more often, simply because of the limited input options. Demo time again, as Google demonstrates the voice search capability with a long query: Pictures of Barack Obama with the French president at the G8 summit. It works, as Vic channels Steve with a "Boom!"
8:58 a.m. (Josh Lowensohn): Voice search in Froyo looks like it starts up a bit faster, and Google has made the whole interface much larger and finger friendly.
8:59 a.m.: Voice recognition is coming in more and more languages, but the next step is understanding human intentions, Vic says. "Call 5th floor restaurant," for example, triggers the dialer. Google manages to get the Buzz Web app running again briefly before it crashes, returning again to the speech capabilities. As with the camera and accelerometer, Google wants to make it so Web apps can access the voice recognition software, demoing an English to French translation service.
9:00 a.m.: Vic formally announces support for Flash 10.1, in the least surprising development of the day. "Turns out people on the Internet use Flash."
9:01 a.m.: Vic relates a story about how his daughter couldn't access her favorite Nickelodeon site because it runs in Flash, but she could on Vic's Android device. "This is what openness means."
9:02 a.m. (Stephen Shankland): Note that just as Google is supporting Flash Player 10.1 in Android--no announcement of actually building it in--Adobe is adding support for Google's VP8 code into Flash Player in the next year. The two companies are very buddy-buddy these days.
9:02 a.m.: We're now moving onto the Android Market. Users are installing more than 40 apps on Android devices, Vic says, and users want to search within apps and move to removable storage. The search function on the Android home page can now search applications as well, finding a Safeway transaction within the Mint Android application by typing "safe."
9:04 a.m. (Stephen Shankland): The YouTube stream is working for me and some others--might be a local issue.
9:04 a.m.: People want to move apps to the SD card, Vic says. Froyo will allow this to happen in a secure way, and in a way where the user doesn't have to worry about it. Back to demos: Matt the demo guy moves Need for Speed from the device to the SD card, where it can still be launched and played.
9:05 a.m.: Updating applications has been improved, which developers like. "I'm kind of embarrassed you felt you had to clap there," Vic says. Android developers will now be able to set their applications to update automatically.
9:06 a.m. (Stephen Shankland): The auto-update idea is very Googley. Chrome updates itself with no user intervention, as do Chrome extensions. Google likes it: says it's just like with Web apps.
9:06 a.m.: Matt the demo guy starts an app called "Crashes" which, well, crashes. It's an error-reporting exercise to demonstrate how error-reporting will now work for Android developers: they'll get the stack trace of a bug that lets them know exactly what went wrong. Developers really like that one.
9:08 a.m.: So what's next for the Android Market? They are showing off an Android Market that's PC browser-based, where you can browse, add reviews, and link your Android devices with your account. The market shows you all your Android devices associated with the account, and lets you download apps right from the store. Shot number 93,984 of the morning at Apple involves the App Store purchase process and the need to connect your iPhone directly to your Mac or PC. Android devices will now be able to download applications over the air directly from the PC or Mac.
9:08 a.m. (Stephen Shankland): Tom--you missed a couple. It was Apple potshot No. 93,986.
9:08 a.m.: What's next for the Market? MUSIC. Android devices can now purchase and download music from the Android Market, over the air.
9:09 a.m. (Josh Lowensohn): And the upcoming version of Android Marketplace on the Web will finally get a search box!
9:09 a.m. (Stephen Shankland): Basically, Google is working to reproduce iTunes abilities with just a browser, no iTunes.
9:10 a.m.: What about people who already built iTunes libraries? Google is planning to let users run software on their home systems to let non-DRM music run on Android devices. They're demoing an iTunes library, but first they have to hang up the demo call that really called the restaurant. "Magically" all your music is available to your device but with a catch: as a stream.
9:10 a.m. (Josh Lowensohn): This is legitimately awesome--as long as you have an Internet connection.
9:11 a.m.: Now, we're going to talk about advertising. "It turns out that we know a little bit about advertising," Vic says.
9:12 a.m.: Google has been providing advertising for 10 years, and in order to provide a healthy ad ecosystem, and you need advertisers. "We're not working with a handful of partners and charging them a million dollars," Vic says. Google says you need flexible advertising formats, and that advertising needs to be measured.
9:13 a.m.: "It turns out that we have some tools you might have heard of," Vic says, reminding people that Google has AdSense and DoubleClick. Google is also open to innovation in advertising, he says. iAd clearly has Google's attention.
9:15 a.m.: Google is currently running a beta project: AdSense for Mobile Ads. Ads are tricky in mobile devices because the screen is small, although you can do tricks like hooking up directly to the Android marketplace, banner ads, text ads, and new for today: expandable ad format. "Users would like to stay within the context of the application they are using," Vic says, consciously or unconsciously echoing Steve Jobs' iAd presentation a month ago.
9:16 a.m. (Stephen Shankland): By the way, the official Google blog post on Android 2.2 aka Froyo now is live: http://android-developers.blogspot.com/2010/05/android-22-and-developers-goodies.html
9:16 a.m. (Josh Lowensohn): Looking at this video ad with a player, it looks like the Froyo update adds a quality selector button to the YouTube player. That's a nice touch, as you currently have to toggle a two-level-deep contextual menu to switch between low- and high-quality levels.
9:17 a.m.: Vic is trying to make the point that different advertisers will need different ad formats. He's demoing the click-to-call option that Google has been using for a while. They're now showing the expandable format, which can incorporate Maps, call to click, or other formats right within the application without having to launch the browser. Vic also shows off how DoubleClick can allow developers to serve "the most relevant ad to the user: sometimes from Google, sometimes not."
9:18 a.m.: More information on the new Google Ads can be found at google.com/mobileads. Developers are getting into the beta project, and will get a $100 credit for setting up ads in their applications.
9:19 a.m.: Now, we're onto devices, highlighting the newly released Sprint HTC Evo 4G. We're running down the spec list, highlighting the screen size and 4G network, the kickstand, and the 8MP camera.
9:19 a.m.: Google is giving away Sprint Evos to everybody at the conference. They like that.
9:20 a.m.: "Those of you who are watching on YouTube, I'm sorry. Remember to register next year," he says.
9:21 a.m.: "Thank you for supporting Android," Vic says. "Thank you for voting on the side of openness and choice. It's halftime, Vic says, and we're about to see where Google is going next for Android. Rishi Chandra, project lead for "a new initiative," comes up on stage. "I'm going to introduce you to Google TV: a new platform that we believe will change the future of television."
9:22 a.m.: First, however, Google has to tell us why TV sucks today. Americans spend 5 hours a day in front of the television, and advertisers spend $70 billion on television advertising. Worldwide, 4 billion people watch television.
9:22 a.m. (Josh Lowensohn): @Scott, nope--no date was given. Yet.
9:23 a.m.: "People just love television. TV just works." It's a pretty brainless exercise, as we all know, and the basic format of television hasn't really changed over the years. But more and more people are getting entertainment from mobile devices and PCs, based on their connections to the Web.
9:24 a.m. (Stephen Shankland): @Scott from Google blog: "Android 2.2 will be here soon, and some devices will get the update in the coming weeks. I invite application developers to download the new SDK and tools and test your applications today."
9:25 a.m.: The Web hasn't really made it to the TV, Chandra said. The PC industry has certainly tried over the years, but it just hasn't happened. So you're left with awkward compromises: a family huddled around a laptop, for example. "Video should be consumed on the biggest and brightest screen in your house. And that's your TV." He notes that many people have tried to make this work, but there's three reasons why it hasn't worked.
9:25 a.m.: 1. They try to dumb down the Web for TV. You're essentially re-creating the Web: "It's WAP all over again," Chandra says, eliciting knowing groans from the mobile-oriented audience.
9:26 a.m.: 2. These systems are closed, and 3. they make you choose between TV and Web, toggling the "input" button. "If you give a user a choice between Web and TV, they're going to choose TV: it's the experience they know."
9:27 a.m.: Google's strategy is to make TV and the Web better, and the plan is Google TV. The tagline: Where TV meets Web, and Web meets TV.
9:27 a.m.: Google's pitch is to improve findability, give more control over what you watch, make existing content more interesting, and make your TV more than a TV. Demo time.
9:29 a.m. (Josh Lowensohn): I was sold at better search. I am having bad flashbacks of trying to use my Comcast box's search tool to find a show.
9:29 a.m.: Vincent Dureau, technical director for the project, is going to lead the demo. They flip on NBC Bay Area, flipping through a bunch of channels. So far, nothing big, but Googlers are using a special remote control: you'll need a special remote to use this, adding to your living room collection of 26 remotes.
9:31 a.m.: TV Guide is the tried and true program-discovery method, but Google wanted to make the process more like the Web. They're adding a search box to Google TV, bringing good old Google search to television. Vincent's wireless keyboard isn't working, and he switches to another backup television? While we wait, we're watching Will Farrell funnel beer.
9:32 a.m.: Finally, it comes up. A search bar drops down from the top of the screen, resembling the Android search bar. It can search both television and the Web, Chandra says, trying a test query for MSNBC. That brings up television listings for MSNBC as well as Web searches generated by that term.
9:34 a.m. (Stephen Shankland): I've yet to see a keyboard control that looks like it would fit into the classic living-room entertainment milieu.
9:34 a.m.: You can search for specific shows, and link the service to your DVR to search that as well. Another demo attempt is derailed by the connectivity issues that surfaced during yesterday's keynote, and tension is building. Finally, Google manages to find a working box, only to lose connectivity again.
9:37 a.m.: Vincent has to move around to try and get a better signal. He's using a wireless keyboard that seems to be the main problem, in that this place is lit up like a Christmas tree with wireless signals. Unfortunately for Google, we're getting a sense of why television is called "a vast wasteland," as the Today Show moves between bizarre Nicholas Cage quotes and Octomom updates.
9:37 a.m.: Google is asking attendees to turn off their cell phones, as the interference has ground this demonstration to a halt. Awkward.
9:37 a.m. (Stephen Shankland): There ought to be some company that offers keynote demo rehearsal stress testing. They could have a giant box that spews out 2.4GHz radio noise and charge $1,000 an hour. Maybe a big unshielded microwave oven.
9:38 a.m. (Josh Lowensohn): Google TV search was pulling up apps too. Maybe this will be tied into the Chrome Apps store unveiled yesterday?
9:38 a.m.: Finally, the search box comes back up on the screen, as an embarrassed Chandra resumes the demo. The search box pulls up content from both the TV and the Web, showing that episodes of House are available on Fox, USA, and Hulu.
9:39 a.m. (Stephen Shankland): @Josh, well, they did say bringing the Web to TV... An app store would be handy for YouTube pay-per-view.
9:40 a.m.: "To a user, it doesn't really matter where I get my favorite content." They select a specific episode of House, which gives the user the choice of recording a future airing of that show or watching it on Amazon Video or Hulu. If you pick Amazon video, it takes you directly to Amazon where you can play the trailer or download episodes. While that happens in the background, the episode starts playing as it appears on the TV.
9:42 a.m. (Josh Lowensohn): Interface looks a bit like Windows Media Center. Just sayin'.
9:42 a.m.: The idea is to avoid having to switch manually between "TV mode" and "Web mode." You can also browse for content within the Google TV software, bringing up your Netflix queue, for example. It brings up your instant queue and suggestions. This isn't new to anybody using set-top boxes connected to the Internet, but the difference with Google's pitch is that you didn't have to switch the input to your Xbox or other device.
9:43 a.m.: There's a ton of video on the Internet, Chandra says, everything from YouTube cat videos to ESPN highlights. Google TV users can browse to YouTube.com, and play any video available there. Switching sites and switching channels is basically the same process, he says. Video content is "unlimited," he says, and can be very personalized.
9:44 a.m. (Stephen Shankland): That volume control slider in the YouTube-on-TV demo looked exactly like the volume control slider on my Android phone.
9:44 a.m. (Josh Lowensohn): That's Windows Media Center...look familiar?
9:45 a.m.: Chandra's two-year-old son watches Sesame Street, but he only likes Elmo. Chandra can search for Elmo clips that he has bookmarked, or directly from Sesame Street's site. He brings up Elmo's "Alphabet Rap." "How can you not love Elmo?" Chandra wonders.
9:47 a.m.: "I just created my own episode of Sesame Street," he says. Upon switching back to TV, ironic Today Show clips continue to play, highlighting Pakistan's decision to block Google's budding rival, Facebook. The search box can also find archived clips, such as "2010 State of the Union." Within the search box, you can get video results, text results, and find the video directly from Whitehouse.gov. "I can access the content I want to whenever I want," says Chandra, who must not like watching sports live on television.
9:48 a.m. (Stephen Shankland): This Web-on-the-TV demo seems like a good opportunity to talk about Flash support. Even if Web developers take Steve Jobs' memo to heart and ditch Flash tomorrow, there's a lot of Flash-hosted video out there on the Web today.
9:48 a.m.: The search box provides a way to link the big-screen TV with the reams of Web content: "a million channels." Chandra says he's actually a sports nut, meaning he's maybe about to address the licensing issues inherent in sports television consumption.
9:50 a.m.: He simulates the Suns-Lakers game from last night and shows how you can do a picture-in-picture view that layers Web content such as box scores or fantasy sports data on the same screen. "This has totally transformed how I watch sports," Chandra says. Other companies have tried to offer these kinds of sports-related widgets on the past on televisions, namely Intel and Microsoft's ill-fated Viiv and Windows Media Center projects.
9:51 a.m.: It's more than just video: the TV would also be good for music, games, and social-networking sites. Chandra goes back to the Google TV Home screen and brings up bookmarks, which can be used to bookmark channels or Web sites, side by side. He heads over to Flickr.
9:52 a.m.: The best photo viewer in your house is your big screen TV, he says. That's only possible now, however, since you can access any Web site from your TV with Google TV. You can get Facebook games, too, or Pandora. Or shopping sites. Or...
9:53 a.m. (Stephen Shankland): Logitech's statement on Google TV partnership: http://www.logitech.com/google/GoogleTV "We'll be providing the full product details for our Google TV companion box later this fall....We're creating a system that includes a companion box--an external device that connects to your TV through an HDMI port--and an intuitive controller that's been designed to take full advantage of everything the Google TV platform offers."
9:53 a.m.: "We can now create an experience which is the most comprehensive, personalized, and accessible entertainment experience out there." So far, no details on partners, availability, pricing, or system requirements, or, everything you need to know to make a purchase decision.
9:55 a.m.: Vincent gets into the hardware: there are going to be TV sets, Blu-ray players, and set-top boxes. They will work with existing cable and satellite boxes, he says. There are four specs: Wi-Fi and Ethernet, HDMI connectors, an I/R sensor, and a "strong processor." There will also be a GPU, but no specifics yet.
9:56 a.m. (Stephen Shankland): This sounds like pretty high-end hardware to me. In other words, not cheap.
9:56 a.m.: Google TV input devices will be required: a keyboard and a pointing device. However, you'll also be able to use your Android phone as a remote control. You can connect over Wi-Fi, and you can use voice search to search your television.
9:57 a.m. (Josh Lowensohn): The voice search feature will be nice for people who don't want to have a keyboard sitting around in their living room. Not so useful for channel surfing though.
9:58 a.m.: Different people in the house can connect multiple remotes, therefore, to the same Google TV box, which seems like a divorce catalyst just waiting to happen. You can find videos on your Android devices and push them directly to the TV, as Chandra shows us a clip of Conan O'Brien's recent visit to the Googleplex.
9:58 a.m.: Developers will be able to build their own applications and devices through an API, Vincent says.
9:59 a.m.: On the software side, Google TV runs on Android 2.1, and Google will upgrade over time. The browser, as might be expected, is Google Chrome. And the other component? Flash 10.1.
10:00 a.m. (Stephen Shankland): What happens when the TV audio track commands your Android phone to change TV channels? New idea for advertisers. :)
10:02 a.m.: By using Android, that means you'll be able to run Android apps on your television. The search box can also find applications through the Android Market, putting the mobile version on the Google TV screen. You can then search within the Android market and open applications like Pandora, running the mobile app on the TV. One interesting note: the application does not expand to fill the screen, meaning that Google has just introduced another possible fragmentation screen for Android apps.
10:03 a.m. (Stephen Shankland): Official blog post about Google TV: http://googleblog.blogspot.com/2010/05/announcing-google-tv-tv-meets-web-web.html
10:04 a.m.: Brittany Bohnet comes up to demonstrate the desktop-based Android market, and how you can purchase applications for Google TV through the market. She downloads a Twitter app, and the app appears on the applications screen of Google TV.
10:05 a.m.: Developers now have other ways to get their applications out there, and will have two application frameworks for Google TV: Web apps and Android apps. An SDK won't be available until after the products ship, a date Google has still not outlined.
10:05 a.m. (Josh Lowensohn): This news would seem to bode well for Android tablets, yes? Big, widescreen displays with easy-to-click buttons.
10:07 a.m.: Many applications and sites will run on Google TV as-is, but Google plans to show developers how to optimize their sites for Google TV. Google will also release APIs for Google TV applications. YouTube is getting in on the act, having designed a version of its site called YouTube Leanback, a way to make YouTube easier to see at the "10-foot" experience that those in the biz call the TV experience.
10:08 a.m. (Josh Lowensohn): I wonder if they'll push this over to game consoles, as they've already had a living room version of YouTube available for a while: http://news.cnet.com/youtube-launches-tv-friendly-site-for-consoles/
10:08 a.m. (Stephen Shankland): Google says this about Google TV availabilty on the blog: "These devices will go on sale this fall, and will be available at Best Buy stores nationwide."
10:09 a.m.: You can get recommendations from friends, and suggestions from YouTube. It's also sorted by default channels, and you can customize channels. Before, you had to give up control of your experience, but this service allows you to put more control over the full-screen experience. Expect to hear more about that in several weeks.
10:10 a.m.: The NBA has developed a site for Google TV. NBA.com created a new user experience for the Google TV product. They show off highlights of the Suns-Lakers game from last night, so we'll get to see who the Celtics will eventually steamroll in the finals.
10:12 a.m.: You can also set your DVR to record Game 3 of that series through the application, although they can't show us that because they're trying to do everything wireless, and believe it or not, it's hard to get 5,000 people to turn off the multiple wireless devices they have in their pockets.
10:13 a.m.: Brittany is back to show off how Google Listen will work on the Google TV devices, although, because of the wireless issues, it's not working. It finally arrives: it's a podcast RSS reader that will now have videos in it as well, and has therefore been renamed "Google Listen and Watch."
10:16 a.m.: "Live HD video podcast right on your television." This lets you sync subscriptions across devices, and you can search within the Listen app from the search bar for specific podcasts. Another application was developed by an engineer who moved to Google recently but who's wife doesn't speak English, so she doesn't understand American television. So he created a Google Translate application for Google TV, sort of a combination of the Google Translate service and the auto-captions recently introduced in YouTube.
10:19 a.m.: Chandra comes back on stage to talk about "partners and timelines." This idea has a lot of potential, he says, because the TV experience has been closed and fragmented. This could help create a new category of devices that are open to developers and users. "Our goal is to have the same impact on the TV experience that the smartphone had on the mobile experience."
10:19 a.m.: The Google TV program will be open-sourced into Android and Chrome streams, he said.
10:20 a.m.: Google has partnered to deliver three Google TV devices: The first is from Sony, as reported over the last few weeks. They're going to launch a line of TVs and Blu-ray players. Logitech is also on board, launching a "companion box" to integrated Google TV with your current system, and Logitech being Logitech, they'll create peripherals. And Intel's Atom chipset is the power.
10:20 a.m.: Coming in fall 2010.
10:21 a.m.: Google has also extended its partnership with Dish Network for this project. Dish subscribers will have an enhanced version of this service. Best Buy, as Shankland noted above, will distribute the devices.
10:22 a.m.: Developers can start optimizing their sites now, but the SDKs won't be available until "early 2011" and the open-source part won't happen until later in that year.
10:22 a.m.: Eric Schmidt, CEO of Google, finally makes an appearance.
10:23 a.m. (Josh Lowensohn): Chairs are coming out, too. This is going to be a panel.
10:24 a.m.: 20 year ago, Schmidt heard pitches for electronic television. 10 years ago, PC companies tried to integrate this, he said. "We've been waiting a long, long time to make this happen." It took a lot of things to make this happen, such as the development of the Web, fast processors, and other technology. It's been harder to marry old technology and new technology than the new tech guys thought, Schmidt said.
10:25 a.m.: Schmidt brings up Paul Otellini, CEO of Intel and a Google board member. Also here are Sir Howard Stringer, CEO of Sony; Jerry Quindlen, CEO of Logitech; Charlie Ergen, CEO of Dish Network; and Brian Dunn, CEO of Best Buy. Last but not least, Shantanu Narayen,CEO of Adobe. That's a panel of heavy hitters.
10:27 a.m.: Schmidt asks Otellini why the Atom processor is so cool (basically). Otellini says that the chip is actually a separate version of Atom, with specialized circuitry for television devices, like HD video encoding and decoding. So it's not just a Netbook motherboard we're talking about. Otellini said this was one of the uses that Intel had in mind for Atom all along.
10:28 a.m.: Schmidt jokes with Narayen about the recent tiff between Apple and Adobe, asking him why Flash is so important. Narayen says that it's all about engaging experiences on the Web, and it's all about getting that content and applications to any device. "This is about trying to create family harmony," he says.
10:30 a.m.: Schmidt's channeling his inner Charlie Rose here, moving on to ask Narayen if there's anything special in Flash 10.1 that makes this possible. Narayen says Adobe tweaked the product to improve battery life.
10:31 a.m.: Stringer is next: Schmidt wonders if people are going to go out and buy new televisions because of this? Stringer calls it "thrilling," confirming that he'll have televisions out and ready for the holiday season.
10:33 a.m.: Stringer points out that Sony Ericcson "dominates" in Japan, prompting Schmidt to remind Stringer not to use the word "dominant," but rather "significant market share," as Schmidt and Otellini dissolve into giggles.
10:35 a.m.: This is basically an advertisement for Google TV partners, giving them a chance to highlight their technology. Logitech's Quindlen talks up their plans to deliver peripherals and boxes, allowing Google TV users to get up and running quickly.
10:35 a.m. (Stephen Shankland): I find it curious that Google believes both in the easy, passive version of TV with YouTube LeanBack but also the interface-heavy modes controlled by a keyboard, search, configuration.
10:38 a.m.: Dish Network's CEO thinks this service will attract more subscribers, and also increase the amount of time they spend using that service. He lets slip that Google has been working on Google TV for several years, dating back to the early days of Google's partnership with Dish on TV advertising.
10:41 a.m.: Schmidt gives Best Buy a nod as the "surviving" big-box retailer. Dunn notes that the holiday season provides a ton of Best Buy's profits, saying that Best Buy has an internal slogan that "this is the most important holiday season of all time," which they trot out every year.
10:45 a.m.: Stringer notes that beyond the set of partners being feted on stage, third-party developers will be able to create even more. Schmidt picks up on that, urging developers in attendance to build the things that Google and its partners can't envision. This is a chance to change the way that people experience television, he says.
10:46 a.m.: We're now getting a commercial for OnStar as the show wraps up. That will do it for Day 2 of Google I/O, but we are certainly not done digesting the Android 2.2 and Google TV announcements, and check back throughout the day for ongoing coverage. Thanks for hanging out again with us this morning, and thanks for reading CNET.
Editors' note: The initial, bare-bones version of this story was posted May 19 at 3:43 p.m. PDT.