From 624439169bdcba34bd0700bb5e54132b755287a9 Mon Sep 17 00:00:00 2001 From: alim0x Date: Sun, 1 Jan 2017 23:34:00 +0800 Subject: [PATCH] [translated] 30 - The history of Android --- .../30 - The (updated) history of Android.md | 116 +++++++++--------- 1 file changed, 57 insertions(+), 59 deletions(-) rename {sources => translated}/talk/The history of Android/30 - The (updated) history of Android.md (57%) diff --git a/sources/talk/The history of Android/30 - The (updated) history of Android.md b/translated/talk/The history of Android/30 - The (updated) history of Android.md similarity index 57% rename from sources/talk/The history of Android/30 - The (updated) history of Android.md rename to translated/talk/The history of Android/30 - The (updated) history of Android.md index 361e7f0f49..c9408033a5 100644 --- a/sources/talk/The history of Android/30 - The (updated) history of Android.md +++ b/translated/talk/The history of Android/30 - The (updated) history of Android.md @@ -1,171 +1,169 @@ -alim0x translating - -The (updated) history of Android +安卓编年史 ============================================================ -> Follow the endless iterations from Android 0.5 to Android 7 and beyond. +> 让我们跟着安卓从 0.5 版本到 7 的无尽迭代来看看它的发展历史。 ### Android TV * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2016/10/IMG_0002-22-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2016/10/IMG_0002-22-150x150.jpg) ][2] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-172334-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-172334-150x150.png) ][3] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/play-store-2-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/play-store-2-150x150.png) ][4] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/search-2-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/search-2-150x150.png) ][5] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/search-1-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/search-1-150x150.png) ][6] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-150246-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-150246-150x150.png) ][7] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-1548581-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-1548581-150x150.png) ][8] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-170651-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-170651-150x150.png) ][9] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-174128-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2014/11/device-2014-10-31-174128-150x150.png) ][10] -November 2014 saw Android continue its march to take over everything with a screen as Google unveiled Android TV. A division inside the company had previously tried to take over the living room with Google TV during the Honeycomb era, but this was a total reboot of the idea directly from the Android team. Android TV took Android 5.0 Lollipop and gave it a Material Design interface purpose-built for the biggest screen in the house. For launch hardware, Google tapped Asus to build the "Nexus Player," an underpowered-but-versatile set top box. +2014 年 11 月谷歌公布了安卓 TV，安卓继续进行它带着一块屏幕征服一切的征程。这家公司里的一个部门之前在蜂巢时代尝试过用谷歌 TV 掌控客厅，但这次完全是来自安卓团队的新点子。安卓 TV 使用安卓 5.0 棒棒糖，并给了它一个为室内最大屏幕设计的 Material Design 界面。首发硬件谷歌选择了华硕来代工“Nexus Player”，这是一个配置不足但够用的机顶盒。 -Android TV was really about three things: video, music, and games. You controlled the TV with a tiny remote consisting only of a D-Pad with 4 buttons: Back, Home, Microphone, and Play/Pause. For games, Asus simply cloned the Xbox 360 controller, giving players a million buttons and a pair of analog sticks. +安卓 TV 专注于三样东西：视频，音乐，以及游戏。你可以用一个小遥控器控制电视，它只有四向方向键以及四个按钮，后退、主页、麦克风以及播放/暂停。至于游戏，华硕克隆了一个 Xbox 360 手柄，给了玩家一堆按键和一对摇杆。 -The interface was pretty simple. Large horizontally-scrolling media thumbnails occupied the screen, filling the TV with content from YouTube, Google Play, Netflix, Hulu, and other sources. Instead of soiling everything in an app, the thumbnails were actually "recommended" items from many different content sources. Below that you could directly access the apps and settings. +安卓 TV 的界面很简单。大幅的媒体略缩图占据了屏幕，可以横向滚动，这些媒体中有 Youtube、Google Play、Netflix、Hulu 以及其它来源。这些略缩图实际上是来自不同媒体源的“推荐”项目，它不是简单地将一个应用的内容填满屏幕。在那下面你可以直接访问应用和设置。 -The voice interface was great. You could ask Android TV to play whatever you wanted, instead of hunting it down through the GUI. You could also run clever search results on content, like "show me movies with Harrison Ford." And instead of app silos, every app could provide content to the indexing service. All these apps were housed in a TV-version of the Play Store. Developers specifically supporting Android TV devices also supported the Google cast protocol, allowing users to beam videos and music from their phones and tablets to the TV. +语音界面很赞。你可以告诉安卓 TV 播放任意你想要的内容，而不用通过图形界面去寻找。你还能在内容里获得更聪明的搜索结果，比如“显示和 Harrison Ford 有关的电影”。每个应用都可以给索引服务提供内容，而不是简单的应用集合。所有的这些应用都在 Play 商店有一个 TV 版本。开发者对安卓 TV 的特别支持还包括谷歌 cast 协议，允许用户从他们的手机和平板向电视投射视频和音乐。 ### Android 5.1 Lollipop * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/lock1-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/lock1-150x150.jpg) ][11] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/2015-03-14-17.33.58-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/2015-03-14-17.33.58-150x150.png) ][12] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/quick-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/quick-150x150.jpg) ][13] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/new-quick-panels-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/new-quick-panels-150x150.jpg) ][14] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/volumepress-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/volumepress-150x150.jpg) ][15] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/volumetouch-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/volumetouch-150x150.jpg) ][16] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/volumebell-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/volumebell-150x150.jpg) ][17] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/interrupts1-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/interrupts1-150x150.jpg) ][18] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/heads-up1-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/heads-up1-150x150.jpg) ][19] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/screen-pin-2-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/screen-pin-2-150x150.jpg) ][20] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/screen-pin-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/screen-pin-150x150.jpg) ][21] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/gif1-150x150.gif) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/gif1-150x150.gif) ][22] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/Untitled-1-150x150.gif) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/Untitled-1-150x150.gif) ][23] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/51-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/51-150x150.jpg) ][24] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/scrollbar-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/scrollbar-150x150.jpg) ][25] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/simcard-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/simcard-150x150.jpg) ][26] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/sip-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/sip-150x150.jpg) ][27] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/status-screen-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/status-screen-150x150.jpg) ][28] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/time-picker-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/time-picker-150x150.jpg) ][29] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/icons-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/icons-150x150.jpg) ][30] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/play-store-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/03/play-store-150x150.jpg) ][31] -Android 5.1 came out in March 2015 and was the tiniest of updates. The goal here was mainly to [fix encryption performance][43] on the Nexus 6, along with adding device protection and a few interface tweaks. +安卓 5.1 在 2015 年 3 月发布，这是安卓最小的更新。它的目的主要是[修复 Nexus 6 上的加密性能问题][43]，还添加了设备保护和一些小的界面调整。 -Device protection's only UI addition took the form of a new warning during setup. The feature offered to "Protect your device from reuse" if it was stolen. Once a lock screen was set, device protection would kick in, and could be triggered during a device wipe. If you wiped the phone the way an owner normally would—by unlocking the phone and picking "reset" from the settings—nothing would happen. If you wipe the phone through developer tools though, the device would demand that you "verify a previously-synced Google Account" during the next setup. +设备保护是唯一的新增界面，采用的是在开机设置显示新警告的形式。这个特性在设备被偷了之后“保护你的设备不被再次利用”。一旦设置了锁屏，设备保护就开始介入，并且会在擦除设备的时候被触发。如果你以机主正常的方式擦除设备——解锁手机并从设置选择“重置”——什么都不会发生。但如果你通过开发者工具擦除，设备会在下次开机设置的时候要求你“验证之前同步的谷歌账户”。 -The idea was that a developer would know the pervious Google credentials on the device, but a thief would not so they'd be stuck at setup. In practice this triggered [a cat and mouse game][44] of people finding exploits that get around device protection, and Google getting word of the bug and patching it. Software features added by OEM skins also introduced fun new bugs to get around device protection. +这个想法是基于开发者是会知道之前登录的谷歌帐号凭证的，但小偷就不知道了，他们会卡在设置这一步。在现实中这引发了[一个猫鼠游戏][44]，人们寻找漏洞来绕过设备保护，而谷歌知道了这个 bug 并修补它。OEM 定制也引入了一些有趣的 bug 来绕过设备保护。 -There was also a whole host of extremely minor UI changes that we have dutifully cataloged in the gallery, above. There's not much to say about them beyond the captions. +还有很多特别微小的界面改动，我们没法一一列在上面的图中。除了上面的图片描述之外没什么可说的了。 ### Android Auto * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2016/10/Android_Auto_The_right_information_for_the_road_ahead_-_YouTube_-_Google_Chrome_2016-10-29_19-49-56-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2016/10/Android_Auto_The_right_information_for_the_road_ahead_-_YouTube_-_Google_Chrome_2016-10-29_19-49-56-150x150.jpg) ][32] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2016/10/Android-Auto-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2016/10/Android-Auto-150x150.jpg) ][33] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-105548-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-105548-150x150.png) ][34] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-091514-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-091514-150x150.png) ][35] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-10-194221-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-10-194221-150x150.png) ][36] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-110323-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-110323-150x150.png) ][37] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-10-113659-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-10-113659-150x150.png) ][38] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-105654-150x150.png) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-105654-150x150.png) ][39] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-1117341-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/screendump-2015-07-09-1117341-150x150.jpg) ][40] * [ - ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/IMG_3594-150x150.jpg) + ![](https://cdn.arstechnica.net/wp-content/uploads/2015/07/IMG_3594-150x150.jpg) ][41] -Also in March 2015, Google launched "Android Auto," a new Android-inspired interface for car infotainment systems. Android Auto was Google's answer to Apple's CarPlay and worked much the same way. It wasn't a full operating system—it's a "casted" interface that runs on your phone and uses the car's built-in screen as an external monitor. Running Android Auto means having a compatible car, installing the Android Auto app on your phone (Android 5.0 and above), and hooking the phone up to the car with a USB cable. +同样是在 2015 年 3 月，谷歌发布了“安卓 Auto”，一个基于安卓界面的全新车载娱乐信息系统。安卓 Auto 是谷歌面对苹果的 CarPlay 交出的答卷，它们很多地方都很相似。安卓 Auto 不完全是个操作系统——它是一个运行在你手机上的“投射”界面，使用车载显示屏作为一块外置显示器。运行安卓 Auto 意味着拥有一款兼容的汽车，在手机上（安卓 5.0 及以上版本）安装了安卓 Auto 应用，并用 USB 线将手机连接到汽车。 -Android Auto brought Google's Material Design interface to your existing infotainment system, bringing top-tier software design to a platform that [typically struggles][45] with designing good software. Android Auto was a ground up redesign of the Android interface made specifically to comply with the myriad of infotainment regulations around the world. There was no tradition "home screen" full of app icons, instead Android's navigation bar was changed into an always-on app launcher (almost like a tabbed interface). +安卓 Auto 给你已有的车载系统带来了谷歌的 Material Design 界面，给这个[通常挣扎于]设计好软件的平台带来了顶级的软件设计。安卓 Auto 是个对安卓界面的完全重新设计，以遵循世界各地对车载系统无数的规定。它没有通常充满应用图标的“主屏”，安卓的导航栏也变为了一个常驻的应用启动器（几乎像是个标签页式的界面）。 -The paired down feature set only really had four sections, from left to right on the navigation bar: Google Maps, a dialer/contacts screen, the "home" section that was a hybrid of Google Now and a notification panel, and a music page. The last button was an "OEM" page that let you exit Android Auto and return to the stock infotainment system (it was also meant to eventually house custom car manufacturer features). There was Google's voice command system, which took the form of a microphone button on the top right of the screen. +算下来特性实际上只有四部分，导航栏从左到右是：谷歌地图，一个拨号/联系人界面，“主屏”部分混合了 Google Now 和一个通知面板，还有一个音乐页面。最后一个按钮是一个“OEM”页面，让你可以退出安卓 Auto，返回到自带的车载系统（这也是为了放置汽车制造商的定制特性）。安卓 Auto 还带有谷歌的语音命令系统，以一个麦克风按钮的形式显示在屏幕右上角。 -There wasn't much in the way of apps for Android Auto. Only two categories were allowed: music and messaging apps. Infotainment regulations meant customizing the UI wasn't really an option. Messaging apps had no interface and could just plug into the voice system, and music apps couldn't change the interface much, only tweaking the colors and iconography of Google's default "music app" template. What really mattered was delivering the music and messages though, and apps could do that. +安卓 Auto 的应用没有多少。它只允许两个类别的应用：音乐和信息应用。车载信息娱乐系统的规定意味着自定义界面不是个好选择。信息应用没有界面，并且可以接入语音系统，音乐应用也不会太多地改变界面，仅仅只是调整一下谷歌默认的“音乐应用”模板的颜色和图标。但实际上重要的是音乐和消息的送达，在不让驾驶员太多分心的情况下，一般的应用就没法使用了。 -Android Auto hasn't seen much in the way of updates after its initial launch, but it has seen a ton of car manufacturer support. In 2017, there will be [over 100][46] compatible vehicle models. +安卓 Auto 在它的最初发布之后就没看到多少更新了，但已经逐渐有很多汽车制造商支持了。到了 2017 年，将会有[超过 100][46] 款支持的汽车型号。 -------------------------------------------------------------------------------- 作者简介： -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. +Ron 是 Ars Technica 的评论编缉，专注于安卓系统和谷歌产品。他总是在追寻新鲜事物，还喜欢拆解事物看看它们到底是怎么运作的。 -------------------------------------------------------------------------------- @@ -173,7 +171,7 @@ Ron is the Reviews Editor at Ars Technica, where he specializes in Android OS an via: http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/30/ 作者：[RON AMADEO][a] -译者：[译者ID](https://github.com/译者ID) +译者：[alim0x](https://github.com/alim0x) 校对：[校对者ID](https://github.com/校对者ID) 本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出