Google I/O 2012 was held at Moscone Center in San Francisco for 3 days – June 27-29, 2012. Here is the Google I/O Day 1 keynote full transcript…
Introducing Speaker: Ladies and gentlemen, please welcome Senior Vice President, Vic Gundotra.
Vic Gundotra – SVP
Well, hello, everybody. Hello. On behalf of Google, let me extend our warmest welcome to all of you. To the over 6,000 people here at the Moscone Center in San Francisco, welcome. And to our Google I/O viewing parties that are happening all around the world, over 350 different parties with over 30,000 in attendance, welcome.
And finally, let me also welcome the over 1 million people who will be watching this event live stream on YouTube.
Welcome to Google I/O. This is our fifth year, and we’re going to make this Google I/O incredibly special. Our teams have worked very hard to put on something really great for you. And we still have some surprises left. At the end of the day, however, it’s not just about the hard work our teams have done. This conference is really about you – developers.
When you think back over the last five years, things like Google Chrome or Android were in their infancy. We owe, in no small measure, the success of our efforts due to your support. Thank you. Thank you for betting with Google, and thank you for supporting us. Thank you for spending three days of your life here at the Google I/O conference. We hope you’re going to absolutely love it.
Now one small favor to ask, please. f you have a hot spot, please turn the hot spot off, as it’s going to greatly increase our chances of having a successful set of demos. With that, let’s get this started.
Please join me in welcoming director of Android product management, Hugo Barra.
Hugo Barra – Director, Android product management
All right. Good morning, everyone. And welcome to the Android keynote at I/O 2012. Last year on this stage, we talked about momentum, mobile, and more. Momentum, accelerating of Android across the world. Mobile, everything we’re doing to innovate on smartphones and tablets. And more, extending the Android ecosystem well beyond the typical mobile device. This year, we’re continuing with the same three themes and picking up right where we left off.
Let’s start with momentum. Last year right here, we announced that Android had crossed the mark of 100 million devices. 100 million was a huge milestone for us back then. It’s been a pretty busy year, and I’m thrilled to announce our latest milestone. Ready?
400 million Android devices.
400 million is a pretty huge number, but we’re definitely not slowing down. Last year right here, we announced that we were seeing 400,000 new Android devices activated every day. Well, today, 1 million new Android devices are activated every single day. That’s about 12 new Android devices every second of every day. Thank you.
More devices in the hands of more people in a truly global phenomenon. Take a look at this chart. What you see here is a heat map representation of the growth in Android devices throughout the world over the last year. Places like Japan, South Korea, and France grew between 200% and 300% in these 12 months.
But what’s even more impressive is that the developing world is adopting Android at an even faster pace. Very large markets, like Brazil, India, Thailand, and Indonesia, all grew around 500% over the last year alone. Really, really exciting. And we’re continuing to build and innovate just as fast in the Android team.
Today, we want to share with you what we’ve been working on since we launched Ice Cream Sandwich late last year. I’d like to introduce you to our newest release. You guys ready for this?
Android 4.1 Jelly Bean.
Jelly Bean builds upon what we created with Ice Cream Sandwich. We want things to be simple, beautiful, and really smart. There are a few things about Jelly Bean we wanted to cover today. Project Butter, a performance-focused effort that went deep into the guts of the platform. We’ll then talk to you about a number of delightful improvements that we’ve made throughout the entire system. And finally, we’ll show you the new Google Search experience on Android.
To tell you about Project Butter, please welcome Android engineering director, Dave Burke.
Dave Burke – Android engineering director
Thanks, Hugo. Our brain’s visual cortex is especially sensitive to the physics of motion. It notices delays of as little as 10 milliseconds. So with Jelly Bean, we put a lot of effort into making the user interface fast, fluid, and smooth. This is the project that we call Project Butter.
The first thing we did was improve the system frame rate and make it consistent. We took the display refresh signal, called vSync, and extended it to drive the entire Android framework at 60 frames per second. That’s one heartbeat about every 16 milliseconds. And now everything runs in lockstep, application rendering, touchscreen processing, screen composition, and display refresh.
In Jelly Bean, we also introduced triple buffering in the graphics pipeline. And this allows the GPU, the CPU, and display to all run in parallel without waiting on each other. The result is a more consistent rendering framework, and everything feels a lot smoother. Scrolling, paging, animations, they’re all buttery smooth.
Next, we focused on improving touch experience by solving two problems. The first problem is that touch events are reported independently of screen update. In Jelly Bean, we now actually anticipate where your finger will be at the time of screen refresh and use that position to draw the display. This results in a more reactive and uniform touch response.
The second problem relates to how devices conserve power. They actually dial the CPU back to a lower frequency when there’s not much activity in the system, and if you interact with the system in that state, it can potentially take 10s of milliseconds for the CPU to ramp up and respond. And this can lead to a sluggish UI.
So in Jelly Bean, we introduced the concept of Touch Input Boost. Now when you interact with the screen, we’ll instantly ramp the CPU up. It’s literally putting the full power of the CPU at your fingertips.
Now, one of our goals when we started to work in Jelly Bean was to be able to measure and improve interactive performance in a scientific way. So we created a new tool called Systrace. And Systrace collects data directly from the Linux kernel and uses that to produce an overall picture of what the system is doing. The data is represented as a group of vertically stacked time series graphs. And in this particular application example, you can see that there’s a rendering interruption that’s much longer than 16 milliseconds. And this results in dropped frames.
When you look at the data, it’s pretty easy to correlate that with the database interruption here. So you know what to fix. Systrace comes with the Jelly Bean SDK. And it’s a really useful tool for device manufacturers and for you guys to optimize the performance of your application.
So how noticeable are these changes in practice? Well, we got out a high-speed camera to compare a stock device running Ice Cream Sandwich against a device running the latest Jelly Bean. Let’s take a look.
So this is a really sophisticated camera capable of capturing 4 million pixels at a rate of up to 300 frames per second. Device on the left is running Ice Cream Sandwich. Device on the right, Jelly Bean. So let’s take a look at the launcher animation. So the Jelly Bean device has a much higher frame rate. It feels a lot smoother.