mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-02-03 23:40:14 +08:00
Merge pull request #2670 from alim0x/master
[translated]The history of Android - 13
This commit is contained in:
Xingyu.Wang
commit
6e92b96e18
@ -1,104 +0,0 @@
|
||||
【translating】The history of Android
|
||||
================================================================================
|
||||
|
||||
|
||||
### Android 2.1, update 1—the start of an endless war ###
|
||||
|
||||
Google was a major launch partner for the first iPhone—the company provided Google Maps, Search, and YouTube for Apple’s mobile operating system. At the time, Google CEO Eric Schmidt was a member of Apple’s board of directors. In fact, during the original iPhone presentation, [Schmidt was the first person on stage][] after Steve Jobs, and he joked that the two companies were so close they could merge into “AppleGoo."
|
||||
|
||||
While Google was developing Android, the relationship between the two companies slowly became contentious. Still, Google largely kept Apple happy by keeping key iPhone features, like pinch zoom, out of Android. The Nexus One, though, was the first slate-style Android flagship without a keyboard, which gave the device the same form factor as the iPhone. Combined with the newer software and Google branding, this was the last straw for Apple. According to Walter Isaacson’s biography on Steve Jobs, after seeing the Nexus One in January 2010, the Apple CEO was furious, saying "I will spend my last dying breath if I need to, and I will spend every penny of Apple's $40 billion in the bank, to right this wrong... I'm going to destroy Android, because it's a stolen product. I'm willing to go thermonuclear war on this."
|
||||
|
||||
All of this happened behind closed doors, only coming out years after the Nexus One was released. The public first caught wind of this growing rift between Google and Apple when, a month after the release of Android 2.1, an update shipped for the Nexus One called “[2.1 update 1.][2]" The updated added one feature, something iOS long held over the head of Android: pinch-zoom.
|
||||
|
||||
While Android supported multi-touch APIs since version 2.0, the default operating system apps stayed clear of this useful feature at the behest of Jobs. After reconciliation meetings over the Nexus One failed, there was no longer a reason to keep pinch zoom out of Android. Google pushed all their chips into the middle of the table, hit the update button, and was finally “all-in" with Android.
|
||||
|
||||
With pinch zoom enabled in Google Maps, the Browser, and the Gallery, the Google-Apple smartphone war was on. In the coming years, the two companies would become bitter enemies. A month after the pinch zoom update, Apple went on the warpath, suing everyone and everything that used Android. HTC, Motorola, and Samsung were all brought to court, and some of them are still in court. Schmidt resigned from Apple’s board of directors. Google Maps and YouTube were kicked off of the iPhone, and Apple even started a rival mapping service. Today, the two players that were almost "AppleGoo" compete in smartphones, tablets, laptops, movies, TV shows, music, books, apps, e-mail, productivity software, browsers, personal assistants, cloud storage, mobile advertising, instant messaging, mapping, and set-top-boxes... and soon the two will be competing in car computers, wearables, mobile payments, and living room gaming.
|
||||
|
||||
### Android 2.2 Froyo—faster and Flash-ier ###
|
||||
|
||||
[Android 2.2][3] came out four months after the release of 2.1, in May 2010. Froyo featured major under-the-hood improvements for Android, all made in the name of speed. The biggest addition was just-in-time (JIT) compilation. JIT automatically converted java bytecode into native code at runtime, which led to drastic performance improvements across the board.
|
||||
|
||||
The Browser got a performance boost, too, thanks to the integration of the V8 javascript engine from Chrome. This was the first of many features the Android browser would borrow from Chrome, and eventually the stock browser would be completely replaced by a mobile version of Chrome. Until that day came, though, the Android team needed to ship a browser. Pulling in Chrome parts was an easy way to upgrade.
|
||||
|
||||
While Google was focusing on making its platform faster, Apple was making its platform bigger. Google's rival released the 10-inch iPad a month earlier, ushering in the modern era of tablets. While some large Froyo and Gingerbread tablets were released, Google's official response—Android 3.0 Honeycomb and the Motorola Xoom—would not arrive for nine months.
|
||||
|
||||
|
||||
Froyo added a two-icon dock at the bottom and universal search.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
The biggest change on the Froyo homescreen was the new dock at the bottom, which filled the previously empty space to the left and right of the app drawer with phone and browser icons. Both of these icons were custom-designed white versions of the stock icons, and they were not user-configurable.
|
||||
|
||||
The default layout removed all the icons, and it only stuck the new tips widget on the screen, which directed you to click on the launcher icon to access your apps. The Google Search widget gained a Google logo which doubled as a button. Tapping it would open the search interface and allow you to restrict a search by Web, apps, or contacts.
|
||||
|
||||
|
||||
The downloads page showing the “update all" button, the Flash app, a flash-powered site where anything is possible, and the “move to SD" button.
|
||||
Photo by [Ryan Paul][4]
|
||||
|
||||
Some of the best additions to Froyo were more download controls for the Android Market. There was now an “Update all" button pinned to the bottom of the Downloads page. Google also added an automatic updating feature, which would automatically install apps as long as the permissions hadn't changed; automatic updating was off by default, though.
|
||||
|
||||
The second picture shows Adobe Flash Player, which was exclusive to Froyo. The app plugged in to the browser and allowed for a “full Web" experience. In 2010, this meant pages heavy with Flash navigation and video. Flash was one of Android's big differentiators compared to the iPhone. Steve Jobs started a holy war against Flash, declaring it an obsolete, buggy piece of software, and Apple would not allow it on iOS. So Android picked up the Flash ball and ran with it, giving users the option of having a semi-workable implementation on Android.
|
||||
|
||||
At the time, Flash could bring even a desktop computer to its knees, so keeping it on all the time on a mobile phone delivered terrible performance. To fix this, Flash on Android's browser could be set to "on-demand"—Flash content would not load until users clicked on the Flash placeholder icon. Flash support would last on Android until 4.1, when Adobe gave up and killed the project. Ultimately Flash never really worked well on Android. The lack of Flash on the iPhone, the most popular mobile device, pushed the Internet to eventually dump the platform.
|
||||
|
||||
The last picture shows the newly added ability to move apps to the SD card, which, in an era when phones came with 512MB of internal storage, was sorely needed.
|
||||
|
||||
|
||||
The car app and camera app. The camera could now rotate.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
The camera app was finally updated to support portrait mode. The camera settings were moved out of the drawer and into a semi-transparent strip of buttons next to the shutter button and other controls. This new design seemed to take a lot of inspiration from the Cooliris Gallery app, with transparent, springy speech bubble popups. It was quite strange to see the high-tech Cooliris-style UI design grafted on to the leather-bound camera app—the aesthetics didn't match at all.
|
||||
|
||||
|
||||
The semi-broken Facebook app is a good example of the common 2x3 navigation page. Google Goggles was included but also broken.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Unlike the Facebook client included in Android 2.0 and 2.1, the 2.2 version still sort of works and can sign in to Facebook's servers. The Facebook app is a good example of Google's design guidelines for apps at the time, which suggested having a navigational page consisting of a 3x2 grid of icons as the main page of an app.
|
||||
|
||||
This was Google's first standardized attempt at getting navigational elements out of the menu button and onto the screen, where users could find them. This design was usable, but it added an extra roadblock between launching an app and using an app. Google would later realize that when users launch an app, it was a better idea to show them content instead of an interstitial navigational screen. In Facebook for instance, opening to the news feed would be much more appropriate. And later app designs would relegate navigation to a second-tier location—first as tabs at the top of the screen, and later Google would settle on the "Navigation Drawer," a slide-out panel containing all the locations in an app.
|
||||
|
||||
Also packed in with Froyo was Google Goggles, a visual search app which would try to identify the subject of a picture. It was useful for identifying works of art, landmarks, and barcodes, but not much else. These first two setup screens, along with the camera interface, are all that work in the app anymore. Today, you can't actually complete a search with a client this old. There wasn't much to see anyway; it was a camera interface that returned a search results page.
|
||||
|
||||
|
||||
The Twitter app, which was an animation-filled collaboration between Google and Twitter.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Froyo included the first Android Twitter app, which was actually a collaboration between Google and Twitter. At the time, a Twitter app was one of the big holes in Android's app lineup. Developers favored the iPhone, and with Apple's head start and stringent design requirements, the App Store's app selection was far superior to Android's. But Google needed a Twitter app, so it teamed up with the company to get the first version out the door.
|
||||
|
||||
This represented Google's newer design language, which meant it had an interstitial navigation page and a "tech-demo" approach to animations. The Twitter app was even more heavy-handed with animation effects than the Cooliris Gallery—everything moved all the time. The clouds at the top and bottom of every page continually scrolled at varying speeds, and the Twitter bird at the bottom flapped its wings and moved its head left and right.
|
||||
|
||||
The Twitter app actually featured an early precursor to the Action Bar, a persistent strip of top-aligned controls that was introduced in Android 3.0 . Along the top of every screen was a blue bar containing the Twitter logo and buttons like search, refresh, and compose tweet. The big difference between this and the later action bars was that the Twitter/Google design lacks an "Up" button in the top right corner, and it actually uses an entire second bar to show your current location within the app. In the second picture above, you can see a whole bar dedicated to the location label "Tweets" (and, of course, the continuously scrolling clouds). The Twitter logo in the second bar acted as another navigational element, sometimes showing additional drill down areas within the current section and sometimes showing the entire top-level shortcut group.
|
||||
|
||||
The 2.3 Tweet stream didn't look much different from what it does today, save for the hidden action buttons (reply, retweet, etc), which were all under the right-aligned arrow buttons. They popped up in a speech bubble menu that looked just like the navigational popup. The faux-action bar was doing serious work on the create tweet page. It housed the twitter logo, remaining character count, and buttons to attach a picture, take a picture, and a contact mention button.
|
||||
|
||||
The Twitter app even came with a pair of home screen widgets. The big one took up eight slots and gave you a compose bar, update button, one tweet, and left and right arrows to view more tweets. The little one showed a tweet and reply button. Tapping on the compose bar on the large widget immediately launched the main "Create Tweet," rendering the "update" button worthless.
|
||||
|
||||
|
||||
Google Talk and the new USB dialog.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Elsewhere, Google Talk (and the unpictured SMS app) changed from a dark theme to a light theme, which made both of them look a lot closer to the current, modern apps. The USB storage screen that popped up when you plugged into a computer changed from a simple dialog box to a full screen interface. Instead of a text-only design, the screen now had a mutant Android/USB-stick hybrid.
|
||||
|
||||
While Android 2.2 didn’t feature much in the way of user-facing features, a major UI overhaul was coming in the next two versions. Before all the UI work, though, Google wanted to revamp the core of Android. Android 2.2 accomplished that.
|
||||
|
||||
----------
|
||||
|
||||
|
||||
|
||||
[Ron Amadeo][a] / Ron is the Reviews Editor at Ars Technica, where he specializes in Android OS and Google products. He is always on the hunt for a new gadget and loves to rip things apart to see how they work.
|
||||
|
||||
[@RonAmadeo][t]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/13/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.youtube.com/watch?v=9hUIxyE2Ns8#t=3016
|
||||
[2]:http://arstechnica.com/gadgets/2010/02/googles-nexus-one-gets-multitouch/
|
||||
[3]:http://arstechnica.com/information-technology/2010/07/android-22-froyo/
|
||||
[4]:http://arstechnica.com/information-technology/2010/07/android-22-froyo/
|
||||
[a]:http://arstechnica.com/author/ronamadeo
|
||||
[t]:https://twitter.com/RonAmadeo
|
||||
@ -0,0 +1,104 @@
|
||||
安卓编年史
|
||||
================================================================================
|
||||
|
||||
|
||||
### Android 2.1, update 1——无尽战争的开端 ###
|
||||
|
||||
谷歌是第一代iPhone的主要合作伙伴——公司为苹果的移动操作系统提供了谷歌地图，搜索，以及Youtube。在那时，谷歌CEO埃里克·施密特是苹果的董事会成员之一。实际上，在最初的苹果发布会上，施密特是在史蒂夫·乔布斯[之后第一个登台的人][1]，他还开玩笑说两家公司如此接近，都可以合并成“AppleGoo”了。
|
||||
|
||||
当谷歌开发安卓的时候，两家公司间的关系慢慢变得充满争吵。然而，谷歌很大程度上还是通过拒iPhone关键特性于安卓门外，如双指缩放，来取悦苹果。尽管如此，Nexus One是第一部不带键盘的直板安卓旗舰机，设备被赋予了和iPhone相同的外观因素。Nexus One结合了新软件和谷歌的品牌，这是压倒苹果的最后一根稻草。根据沃尔特·艾萨克森为史蒂夫·乔布斯写的传记，2010年1月在看到了Nexus One之后，这个苹果的CEO震怒了，说道：“如果需要的话我会用尽最后一口气，以及花光苹果在银行里的400亿美元，来纠正这个错误……我要摧毁安卓，因为它完全是偷窃来的产品。我愿意为此进行核战争。”
|
||||
|
||||
所有的这些都在秘密地发生，仅在Nexus One发布后的几年后才公诸于众。公众们最早在安卓2.1——推送给Nexus One的一个称作“[2.1 update 1][2]”的更新，发布后一个月左右捕捉到谷歌和苹果间愈演愈烈的分歧气息。这个更新添加了一个功能，正是iOS一直居于安卓之上的功能：双指缩放。
|
||||
|
||||
尽管安卓从2.0版本开始就支持多点触控API了，默认的系统应用在乔布斯的命令下依然和这项实用的功能划清界限。在关于Nexus One的和解会议谈崩了之后，谷歌再也没有理由拒双指缩放于安卓门外了。谷歌给设备推送了更新，安卓终于补上了不足之处。
|
||||
|
||||
随着谷歌地图，浏览器以及相册中双指缩放的全面启用，谷歌和苹果的智能手机战争也就此拉开序幕。在接下来的几年中，两家公司会变成死敌。双指缩放更新的一个月后，苹果开始了他的征途，起诉了所有使用安卓的公司。HTC，摩托罗拉以及三星都被告上法庭，直到现在都还有一些诉讼还没解决。施密特辞去了苹果董事会的职务。谷歌地图和Youtube被从iPhone中移除，苹果甚至开始打造自己的地图服务。今天，这两位选手几乎是“AppleGoo”竞赛的唯一选手，涉及领域十分广：智能手机，平板，笔记本，电影，TV秀，音乐，书籍，应用，邮件，生产力工具，浏览器，个人助理，云存储，移动广告，即时通讯，地图以及机顶盒……以及不久他们将会在汽车智能，穿戴设备，移动支付，以及客厅娱乐等进行竞争。
|
||||
|
||||
### Android 2.2 Froyo——更快更华丽 ###
|
||||
|
||||
[安卓2.2][3]在2010年5月，也就是2.1发布后的四个月后亮相。Froyo（冻酸奶）的亮点主要是底层优化，只为更快的速度。Froyo最大的改变是增加了JIT编译。JIT自动在运行时将java字节码转换为原生码，这会给系统全面带来显著的性能改善。
|
||||
|
||||
浏览器同样得到了性能改善，这要感谢来自Chrome的V8 Javascript引擎的整合。这是安卓浏览器从Chrome借鉴的许多特性中的第一个，最终系统内置的浏览器会被移动版Chrome彻底替代掉。在那之前，安卓团队还是需要发布一个浏览器。从Chrome借鉴特性是条升级的捷径。
|
||||
|
||||
在谷歌专注于让它的平台更快的同时，苹果正在让它的平台更全面。谷歌的竞争对手在一个月前发布了10英寸的iPad，先行进入了平板时代。尽管有些搭载Froyo和Gingerbread的安卓平板发布，谷歌的官方回应——安卓3.0 Honeycomb（蜂巢）以及摩托罗拉Xoom——在9个月后才来到。
|
||||
|
||||
|
||||
Froyo底部添加了双图标停靠栏以及全局搜索。
|
||||
Ron Amadeo供图
|
||||
|
||||
Froyo主屏幕最大的变化是底部的新停靠栏，电话和浏览器图标填充了先前抽屉按钮左右的空白空间。这些新图标都是现有图标的定制白色版本，并且用户没办法自己设置图标。
|
||||
|
||||
默认布局移除了所有图标，屏幕上只留下一个使用提示小部件，引导你点击启动器图标以访问你的应用。谷歌搜索小部件得到了一个谷歌logo，同时也是个按钮。点击它可以打开一个搜索界面，你可以限制搜索范围在互联网，应用或是联系人之内。
|
||||
|
||||
|
||||
下载页面有了“更新所有”按钮，Flash应用，一个flash驱动的一切皆有可能的网站，以及“移动到SD”按钮。
|
||||
[Ryan Paul][4]供图
|
||||
|
||||
还有一些优秀的新功能加入了Froyo，安卓市场加入了更多的下载控制。有个新的“更新所有”按钮固定在了下载页面底部。谷歌还添加了自动更新特性，只要应用权限没有改变就能够自动安装应用；尽管如此，自动更新默认是关闭的。
|
||||
|
||||
第二张图展示了Adobe Flash播放器，它是Froyo独占的。这个应用作为插件加入了浏览器，让浏览器能够有“完整的网络”体验。在2010年，这意味着网页充满了Flash导航和视频。Flash是安卓相比于iPhone最大的不同之一。史蒂夫·乔布斯展开了一场对抗Flash的圣战，声称它是一个被淘汰的，充满bug的软件，并且苹果不会在iOS上允许它的存在。所以安卓接纳了Flash并且让它在安卓上运行，给予用户在安卓上拥有半可用的flash实现。
|
||||
|
||||
在那时，Flash甚至能够让桌面电脑崩溃，所以在移动设备上一直保持打开状态会带来可怕的体验。为了解决这个问题，安卓浏览器上的Flash可以设置为“按需打开”——除非用户点击Flash占位图标，否则不会加载Flash内容。对Flash的支持将会持续到安卓4.1，Adobe在那时放弃并且结束了这个项目。Flash归根到底从未在安卓上完美运行过。而Flash在iPhone这个最流行的移动设备上的缺失，推动了互联网最终放弃了这个平台。
|
||||
|
||||
最后一张图片显示的是新增的移动应用到SD卡功能，在那个手机只有512MB内置存储的时代，这个功能十分的必要的。
|
||||
|
||||
|
||||
驾驶模式应用。相机现在可以旋转了。
|
||||
Ron Amadeo供图
|
||||
|
||||
相机应用终于更新支持纵向模式了。相机设置被从抽屉中移出，变成一条半透明的按钮带，放在了快门按钮和其他控制键旁边。这个新设计看起来从Cooliris相册中获得了许多灵感，有着半透明，有弹性的聊天气泡弹出窗口。看到更现代的Cooliris风格UI设计被嫁接到皮革装饰的相机应用确实十分奇怪——从审美上来说一点都不搭。
|
||||
|
||||
|
||||
半残缺的Facebook应用是个常见的2x3导航页面的优秀范例。谷歌Goggles被包含了进来但同样是残缺的。
|
||||
Ron Amadeo供图
|
||||
|
||||
不像在安卓2.0和2.1中包含的Facebook客户端，2.2版本的仍然部分能够工作并且登陆Facebook服务器。Facebook应用是个谷歌那时候设计指南的优秀范例，它建议应用拥有一个含有3x2图标方阵的导航页并作为应用主页。
|
||||
|
||||
这是谷歌的第一个标准化尝试，将导航元素从菜单按钮里移到屏幕上，因为用户找不到它们。这个设计很实用，但它在打开应用和使用应用之间增加了额外的障碍。谷歌不久后湖意识到当用户打开一个应用，显示应用内容而不是中间导航页是个更好的主意。以Facebook为例，打开应用直接打开信息订阅会更合适。并且不久后应用设计将会把导航降级到二层位置——先是作为顶部的标签之一，后来谷歌放在了“导航抽屉”，一个含有应用所有功能位置的滑出式面板。
|
||||
|
||||
还有个预装到Froyo的是谷歌Goggles，一个视觉搜索应用，它会尝试辨别图片上的主体。它在辨别艺术品，地标以及条形码时很实用，但差不多也就这些了。最先的两个设置屏幕，以及相机界面，这是应用里唯一现在还能运行的了。由于客户端太旧了，实际上你如今并不能完成一个搜索。应用里也没什么太多可看的，也就一个会返回搜索结果页的相机界面而已。
|
||||
|
||||
|
||||
Twitter应用，一个充满动画的谷歌和Twitter的合作成果。
|
||||
Ron Amadeo供图
|
||||
|
||||
Froyo拥有第一个安卓Twitter应用，实际上它是谷歌和Twitter的合作成果。那时，一个Twitter应用是安卓应用阵容里的大缺憾。开发者们更偏爱iPhone，加上苹果占领先机和严格的设计要求，App Store里可选择的应用远比安卓的有优势。但是谷歌需要一个Twitter应用，所以它和Twitter合作组建团队让第一个版本问世。
|
||||
|
||||
这个应用代表了谷歌的新设计语言，这以为着它有个中间导航页以及对动画要求的“技术演示”。Twitter应用甚至比Cooliris相册用的动画效果还多——所有东西一直都在动。所有页面顶部和底部的云朵以不同速度持续滚动，底部的Twitter小鸟拍动它的翅膀并且左右移动它的头。
|
||||
|
||||
Twitter应用实际上有点Action Bar早期前身的特性，一条顶部对齐的连续控制条在安卓3.0中被引入。沿着所有屏幕的顶部有条拥有Twitter标志和像搜索，刷新和新tweet这样的按钮的蓝色横栏。它和后来的Action Bar之间大的区别在于Twitter/谷歌这里的设计的右上角缺少“上一级”按钮，实际上它在应用里用了完整的第二个栏位显示你当前所在位置。在上面的第二张图里，你可以看到整条带有“Tweets”标签的专用于显示位置的栏（当然，还有持续滚动的云朵）。第二个栏的Twitter标志扮演着另一个导航元素，有时候在当前部分显示额外的下拉区域，有时候显示整个顶级快捷方式集合。
|
||||
|
||||
2.3Tweet流看起来和今天的并没有什么不同，除了隐藏的操作按钮（回复，转推等），都在右对齐的箭头按钮里。它们弹出来是一个聊天气泡菜单，看起来就像导航弹窗。仿action bar在新tweet页面有重要作用。它安置着twitter标志，剩余字数统计，以及添加照片，拍照，以及提到联系人按钮。
|
||||
|
||||
Twitter应用甚至还有一对主屏幕小部件，大号的那个占据8格，给你新建栏，更新按钮，一条tweet，以及左右箭头来查看更多tweet。小号的显示一条tweet以及回复按钮。点击大号小部件的新建栏立即打开了“新Tweet”主窗口，这让“更新”按钮变得没有价值。
|
||||
|
||||
|
||||
Google Talk和新USB对话框。
|
||||
Ron Amadeo供图
|
||||
|
||||
其他部分，Google Talk（以及没有截图的短信应用）从暗色主题变成了浅色主题，这让它们看起来和现在的更接近现在的，更现代的应用。USB存储界面会在你设备接入电脑的时候从一个简单的对话框进入全屏界面。这个界面现在有个一个异形安卓机器人/USB闪存盘混合体，而不是之前的纯文字设计。
|
||||
|
||||
尽管安卓2.2在用户互动方式上没有什么新特性，但大的UI调整会在下两个版本到来。然而在所有的UI工作之前，谷歌希望先改进安卓的核心部分。
|
||||
|
||||
----------
|
||||
|
||||
|
||||
|
||||
[Ron Amadeo][a] / Ron是Ars Technica的评论编缉，专注于安卓系统和谷歌产品。他总是在追寻新鲜事物，还喜欢拆解事物看看它们到底是怎么运作的。
|
||||
|
||||
[@RonAmadeo][t]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/13/
|
||||
|
||||
译者：[alim0x](https://github.com/alim0x) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.youtube.com/watch?v=9hUIxyE2Ns8#t=3016
|
||||
[2]:http://arstechnica.com/gadgets/2010/02/googles-nexus-one-gets-multitouch/
|
||||
[3]:http://arstechnica.com/information-technology/2010/07/android-22-froyo/
|
||||
[4]:http://arstechnica.com/information-technology/2010/07/android-22-froyo/
|
||||
[a]:http://arstechnica.com/author/ronamadeo
|
||||
[t]:https://twitter.com/RonAmadeo
|
||||
Loading…
Reference in New Issue
Block a user