mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
[translated] 29 - The history of Android
This commit is contained in:
alim0x
parent
4f6e52f329
commit
d6cfce7847
@ -1,227 +0,0 @@
|
|||||||
alim0x translating
|
|
||||||
|
|
||||||
The (updated) history of Android
|
|
||||||
============================================================
|
|
||||||
|
|
||||||
### Follow the endless iterations from Android 0.5 to Android 7 and beyond.
|
|
||||||
|
|
||||||
|
|
||||||
Google Search was literally everywhere in Lollipop. A new "always-on voice recognition" feature allowed users to say "OK Google" at any time, from any screen, even when the display was off. The Google app was still Google's primary home screen, a feature which debuted in KitKat. The search bar was now present on the new recent apps screen, too.
|
|
||||||
|
|
||||||
Google Now was still the left-most home screen page, but now a Material Design revamp gave it headers with big bold colors and redesigned typography.
|
|
||||||
|
|
||||||
* [
|
|
||||||
|
|
||||||
][1]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][2]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][3]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][4]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][5]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][6]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][7]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][8]
|
|
||||||
|
|
||||||
The Play Store followed a similar path to other Lollipop apps. There was a huge visual refresh with bold colors, new typography, and a fresh layout. It's rare that there's any additional functionality here, just a new coat of paint on everything.
|
|
||||||
|
|
||||||
The Navigation panel for the Play Store could now actually be used for navigation, with entries for each section of the Play Store. Lollipop also typically did away with the overflow button in the action bar, instead deciding to go with a single action button (usually search) and dumping every extra option in the navigation bar. This gave users a single place to look for items instead of having to hunt through two different menus.
|
|
||||||
|
|
||||||
Also new in Lollipop apps was the ability to make the status bar transparent. This allowed the action bar color to bleed right through the status bar, making the bar only slightly darker than the surrounding UI. Some interfaces even used a full-bleed hero image at the top of the screen, which would show through the status bar.
|
|
||||||
|
|
||||||
[
|
|
||||||
|
|
||||||
][38]
|
|
||||||
|
|
||||||
|
|
||||||
Google Calendar was completely re-written, gaining lots of new design touches and losing lots of features. You could no longer pinch zoom to adjust the time scale of views, month view was gone on phones, and week view regressed from a seven-day view to five days. Google would spend the next few versions re-adding some of these features after users complained. "Google Calendar" also doubled down on the "Google" by removing the ability to add third-party accounts directly in the app. Non-Google accounts would now need to be added via Gmail.
|
|
||||||
|
|
||||||
It did look nice, though. In some views, the start of each month came with a header picture, just like a real paper calendar. Events with locations attached showed pictures from those locations. For instance, my "flight to San Francisco" displayed the Golden Gate Bridge. Google Calendar would also pull events out of Gmail and display them right on your calendar.
|
|
||||||
|
|
||||||
* [
|
|
||||||
|
|
||||||
][9]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][10]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][11]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][12]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][13]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][14]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][15]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][16]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][17]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][18]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][19]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][20]
|
|
||||||
|
|
||||||
Other apps all fell under pretty much the same description: not much in the way of new functionality, but big redesigns swapped out the greys of KitKat with bold, bright colors. Hangouts gained the ability to receive Google Voice SMSes, and the clock got a background color that changes with the time of day.
|
|
||||||
|
|
||||||
#### Job Scheduler whips the app ecosystem into shape
|
|
||||||
|
|
||||||
Google decided to focus on battery savings with Lollipop in a project it called "Project Volta." Google started creating more battery tracking tools for itself and developers, starting with the "Battery Historian." This python script took all of Android's battery logging data and spun it into a readable, interactive graph. With its new diagnostic equipment, Google flagged background tasks as a big consumer of battery.
|
|
||||||
|
|
||||||
At I/O 2014, the company noted that enabling airplane mode and turning off the screen allowed an Android phone to run in standby for a month. However, if users enabled everything and started using the device, they wouldn't get through a single day. The takeaway was that if you could just get everything to stop doing stuff, your battery would do a lot better.
|
|
||||||
|
|
||||||
As such, the company created a new API called "JobScheduler," the new traffic cop for background tasks on Android. Before Job Scheduler, every single app was responsible for its background processing, which meant every app would individually wake up the processor and modem, check for connectivity, organize databases, download updates, and upload logs. Everything had its own individual timer, so your phone would be woken up a lot. With JobScheduler, background tasks get batched up from an unorganized free-for-all into an orderly background processing window.
|
|
||||||
|
|
||||||
JobScheduler lets apps specify conditions that their task needs (general connectivity, Wi-Fi, plugged into a wall outlet, etc), and it will send an announcement when those conditions are met. It's like the difference between push e-mail and checking for e-mail every five minutes... but with task requirements. Google also started pushing a "lazier" approach to background tasks. If something can wait until the device is on Wi-Fi, plugged-in, and idle, it should wait until then. You can see the results of this today when, on Wi-Fi, you can plug in an Android phone and only _then_ will it start downloading app updates. You don't instantly need to download app updates; it's best to wait until the user has unlimited power and data.
|
|
||||||
|
|
||||||
#### Device setup gets future-proofed
|
|
||||||
|
|
||||||
* [
|
|
||||||
|
|
||||||
][21]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][22]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][23]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][24]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][25]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][26]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][27]
|
|
||||||
|
|
||||||
Setup was overhauled to not just confirm to the Material Design guidelines, but it was also "future-proofed" so that it can handle any new login and authentication schemes Google cooks up in the future. Remember, part of the entire reasoning for writing "The History of Android" is that older versions of Android don't work anymore. Over the years, Google has upgraded its authentication schemes to use better encryption and two-factor authentication, but adding these new login requirements breaks compatibility with older clients. Lots of Android features require access to Google's cloud infrastructure, so when you can't log in, things like Gmail for Android 1.0 just don't work.
|
|
||||||
|
|
||||||
In Lollipop, setup works much like it did before for the first few screens. You get a "welcome to Android screen" and options to set up cellular and Wi-Fi connectivity. Immediately after this screen, things changed though. As soon as Lollipop hit the internet, it pinged Google's servers to "check for updates." These weren't updates to the OS or to apps, but updates to the setup process about to run. After Android downloaded the newest version of setup, _then_ it asked you to log in with your Google account.
|
|
||||||
|
|
||||||
The benefit of this is evident when trying to log into Lollipop and Kitkat today. Thanks to the updatable setup flow, the "2014" Lollipop OS can handle 2016 improvements, like Google's new "[tap to sign in][39]" 2FA method. KitKat chokes, but luckily it has a "web-browser sign-in" that can handle 2FA.
|
|
||||||
|
|
||||||
Lollipop setup even takes the extreme stance of putting your Google e-mail and password on separate pages. [Google hates passwords][40] and has come up with several [experimental ways][41] to log into Google without one. If your account is setup to not have a password, Lollipop can just skip the password page. If you have a 2FA setup that uses a code, setup can slip the appropriate "enter 2FA code" page into the setup flow. Every piece of signing in is on a single page, so the setup flow is modular. Pages can be added and removed as needed.
|
|
||||||
|
|
||||||
Setup also gave users control over app restoration. Android was doing some kind of data restoration previously to this, but it was impossible to understand because it just picked one of your devices without any user input and started restoring things. A new screen in the setup flow let users see their collection of device profiles in the cloud and pick the appropriate one. You could also choose which apps to restore from that backup. This backup was apps, your home screen layout, and a few minor settings like Wi-Fi hotspots. It wasn't a full app data backup.
|
|
||||||
|
|
||||||
#### Settings
|
|
||||||
|
|
||||||
|
|
||||||
* [
|
|
||||||
|
|
||||||
][28]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][29]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][30]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][31]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][32]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][33]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][34]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][35]
|
|
||||||
|
|
||||||
Setting swapped from a dark theme to a light one. Along with a new look, it got a handy search function. Every screen gave the user access to a magnifying glass, which let them more easily hunt down that elusive option.
|
|
||||||
|
|
||||||
There were a few settings related to Project Volta. "Network Restrictions" allowed users to flag a Wi-Fi connection as metered, which would allow JobScheduler to avoid it for background processing. Also as part of Volta, a "Battery Saver" mode was added. This would limit background tasks and throttle down the CPU, which gave you a long lasting but very sluggish device.
|
|
||||||
|
|
||||||
Multi-user support has been in Android tablets for a while, but Lollipop finally brought it down to Android phones. The settings screen added a new "users" page that let you add additional account or start up a "Guest" account. Guest accounts were temporary—they could be wiped out with a single tap. And unlike a normal account, it didn't try to download every app associated with your account, since it was destined to be wiped out soon.
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
作者简介：
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
via: http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/
|
|
||||||
|
|
||||||
作者：[RON AMADEO][a]
|
|
||||||
译者：[译者ID](https://github.com/译者ID)
|
|
||||||
校对：[校对者ID](https://github.com/校对者ID)
|
|
||||||
|
|
||||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
|
||||||
|
|
||||||
[a]: http://arstechnica.com/author/ronamadeo
|
|
||||||
[1]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[2]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[3]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[4]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[5]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[6]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[7]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[8]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[9]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[10]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[11]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[12]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[13]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[14]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[15]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[16]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[17]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[18]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[19]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[20]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[21]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[22]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[23]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[24]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[25]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[26]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[27]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[28]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[29]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[30]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[31]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[32]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[33]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[34]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[35]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
|
||||||
[36]:https://cdn.arstechnica.net/wp-content/uploads/2016/10/2-1.jpg
|
|
||||||
[37]:http://arstechnica.com/author/ronamadeo/
|
|
||||||
[38]:https://cdn.arstechnica.net/wp-content/uploads/2016/10/2-1.jpg
|
|
||||||
[39]:http://arstechnica.com/gadgets/2016/06/googles-new-two-factor-authentication-system-tap-yes-to-log-in/
|
|
||||||
[40]:https://www.theguardian.com/technology/2016/may/24/google-passwords-android
|
|
||||||
[41]:http://www.androidpolice.com/2015/12/22/google-appears-to-be-testing-a-new-way-to-log-into-your-account-on-other-devices-with-just-your-phone-no-password-needed/
|
|
||||||
@ -0,0 +1,225 @@
|
|||||||
|
安卓编年史
|
||||||
|
============================================================
|
||||||
|
|
||||||
|
### 让我们跟着安卓从 0.5 版本到 7 的无尽迭代来看看它的发展历史。
|
||||||
|
|
||||||
|
|
||||||
|
毫不夸张地说，谷歌搜索在棒棒糖中无处不在。“持续开启语音识别”这项特性让用户可以在任何界面随时说出“OK Google”，即时是在息屏状态也没有问题。谷歌应用依然是谷歌的首要主屏，这项特性是自奇巧时引入的。现在搜索栏也会显示在新的最近应用界面。
|
||||||
|
|
||||||
|
Google Now 依然是最左侧的主屏，但现在 Material Design 对它进行了大翻新，给了它一个色彩大胆的头部以及重新设计的排版。
|
||||||
|
|
||||||
|
* [
|
||||||
|
|
||||||
|
][1]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][2]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][3]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][4]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][5]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][6]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][7]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][8]
|
||||||
|
|
||||||
|
Play 商店遵从了和其它棒棒糖应用相似的轨迹。它在视觉上焕然疑一新，大胆的色彩，新排版，还有一个全新的布局。通常这里不会有什么新增功能，就只是给一切换件新马甲。
|
||||||
|
|
||||||
|
Play 商店的导航面板现在真的可以用于导航了，每个分类有各自的入口。棒棒糖也不再在操作栏放“更多”按钮了，取而代之的是一个独立的操作按钮（通常是搜索），并且去掉了导航栏中多余的选项。这给了用户一个单独的地方来查找项目，而不用在两个菜单中寻找搜索的地方。
|
||||||
|
|
||||||
|
棒棒糖还给了应用让状态栏透明的能力。这让操作栏的颜色可以渗透到状态栏，让它只比周围的界面暗一点点。一些界面甚至在顶部使用了全幅英雄图片，同时显示到了状态栏上。
|
||||||
|
|
||||||
|
[
|
||||||
|
|
||||||
|
][38]
|
||||||
|
|
||||||
|
|
||||||
|
谷歌日历完全重写了，获得了很多新设计，也失去了很多特性。你不再能够双指缩放来调整时间视图，月份视图也从手机上消失了，周视图从七天退化成了五天的视图。在用户抱怨之后，谷歌将会花费接下来几个版本的时间来重新添加回这里面的一些特性。“谷歌日历”还加强了“谷歌”部分，去除了直接在应用内添加第三方账户的能力。非谷歌账户现在需要从 Gamil 来添加。
|
||||||
|
|
||||||
|
尽管如此，它看起来还是很棒。在一些视图上，月份开头带有头图，就像是真实的纸质日历。带有地点的事件会附带显示来自那个地点的照片。举个例子，我的“去往旧金山”会显示金门大桥。谷歌日历还会从 Gamil 获取事件并在你的日历中显示。
|
||||||
|
|
||||||
|
* [
|
||||||
|
|
||||||
|
][9]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][10]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][11]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][12]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][13]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][14]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][15]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][16]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][17]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][18]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][19]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][20]
|
||||||
|
|
||||||
|
其它应用都可以套用基本相同的描述：功能上没有太多新鲜的，但新设计换掉了奇巧中的灰色以大胆，明亮的色彩。环聊获得了收取 Google Voice 信息的能力，时钟应用的背景颜色会随着每天时间的变化而改变。
|
||||||
|
|
||||||
|
#### 任务调度器鞭策应用生态成型
|
||||||
|
|
||||||
|
谷歌决定在棒棒糖中实施“伏特计划（Project Volta）”，关注电量使用问题。谷歌从“电池史学家（Battery Historian）”开始，为自己和开发者创建了更多的电池追踪工具。这个 python 脚本获取所有的安卓电量日志数据，并转换成可读，交互式的图表。在这个新诊断工具的帮助下，谷歌将后台任务标记为主要的耗电大户。
|
||||||
|
|
||||||
|
在 2014 年的 I/O 大会上，这家公司注意到启用飞行模式并关闭屏幕可以让安卓手机待机将近一个月。但是，如果用户全部启用并使用设备，它们没法坚持一整天。结论就是如果你能让一切都停止活动，你的电池表现就能好得多。
|
||||||
|
|
||||||
|
因此，谷歌创建了一个新 API，称作“JobScheduler（任务调度器）”，这是个新的针对安卓后台任务的警察。在任务调度器出现之前，每个单独的应用为它自己的后台进程负责，这意味着每个应用会独立唤醒处理器和调制解调器，检查连通性、组织数据库、下载更新以及上传日志。所有东西都有它自己独立的定时器，所以你的手机会一直被唤醒。有了任务调度器，后台任务从无组织的混乱，转变为统一的批处理，有有序的后台进程处理窗口。
|
||||||
|
|
||||||
|
任务调度器可以让应用指定它们的任务所需的条件（连通性、Wi-Fi、接入电源等等），它会在那些条件满足的时候发送一条通知。这就像是推送邮件和每五分钟检查一次邮件的区别……但是带上任务需求的。谷歌还开始给后台任务推进一个“懒”实现。如果一些事情可以推迟到设备处于 Wi-Fi，接入电源以及待机状态，那它就应该等到那时候执行。你现在可以看到这一策略的成果，在 Wi-Fi 下，你可以将安卓手机接入电源，并且只有在_这种条件下_它才会开始下载应用更新。你通常不需要立即下载应用更新，最好的时候是等到用户有无限的电源和网络的时候进行。
|
||||||
|
|
||||||
|
#### 开机设置获得面向未来的新设计
|
||||||
|
|
||||||
|
* [
|
||||||
|
|
||||||
|
][21]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][22]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][23]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][24]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][25]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][26]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][27]
|
||||||
|
|
||||||
|
开机设置经过了大翻新，它不止是为了跟上 Material Design 指南，还是“面向未来”的，这样不管未来谷歌采用什么新的登录和验证方案，它都能够适应。记住，写“安卓编年史”的部分原因就是一些旧版安卓已经不再能工作了。这些年来，谷歌已经为用户升级了更佳加密的验证方案以及二次验证，但添加这些新的登录要求破坏了旧客户端的兼容性。很多安卓特性要求访问谷歌云设施，所以你没法登录的话，像安卓 1.0 的 Gmail 这样的就没法工作了。
|
||||||
|
|
||||||
|
在棒棒糖中，开机设置工作的前几个界面和之前的很像。你可以看到“欢迎使用安卓界面”以及一些设置数据和 Wi-Fi 连接的选项。但在这个界面之后就有了变化。一旦棒棒糖连接到了互联网，它会连接到谷歌的服务器来“检查更新”。这并不是检查系统或应用的更新，是在检查即将执行的设置工作的更新。安卓下载了最新版本的设置，_然后_它会要求你登录你的谷歌账户。
|
||||||
|
|
||||||
|
在今天登录进棒棒糖和奇巧的时候这个好处很明显。有可以可升级的设置流程，“2014”的棒棒糖系统可以适应 2016 的改进，像是谷歌新的“[触碰登录][39]”双重认证。奇巧在这就卡住了，但幸运的是它有个“浏览器登录”可以解决双重认证的问题。
|
||||||
|
|
||||||
|
棒棒糖的开机设置对将你的谷歌账户和密码放在单独的页面持极端立场。[谷歌讨厌密码][40]并提供了一些[实验性的方式][40]来不用单独页面登录到谷歌。如果你的账户设置为不使用密码，棒棒糖可以跳过密码页面。如果你设置了双重认证，设置页面就会进入到“输入双因素码”的设置流程。每个登录部分都是在单独的一个页面，所以设置流程是模块化的。页面可以随要求添加或移除。
|
||||||
|
|
||||||
|
开机设置还给了用户对应用还原的控制。安卓在这之前也提供了一些数据还原，但那是无法理解的，因为它仅仅只是在没有任何用户输入的情况下选择你的一台设备并开始恢复。开机设置流程中的一个新界面让用户可以看到在云端的设备配置集合，并选择合适的那个。你还可以选择要从那个备份还原的应用。备份有应用，你的主屏布局，以及一些小设置如 Wi-Fi 热点。它不是完全的应用数据备份。
|
||||||
|
|
||||||
|
#### 设置
|
||||||
|
|
||||||
|
|
||||||
|
* [
|
||||||
|
|
||||||
|
][28]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][29]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][30]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][31]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][32]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][33]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][34]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][35]
|
||||||
|
|
||||||
|
设置从暗色主题切换到了亮色。除了新外观，它还有方便的搜索功能。每个界面用户都能访问放大镜，让他们可以更容易地找到难找的选项。
|
||||||
|
|
||||||
|
这里有一些和伏特计划有关的额设置。“网络限制”允许用户将一个 Wi-Fi 连接标记为计费的，让任务调度器处理后台处理时避免使用它。同时作为伏特计划的一部分，添加了一个“节电模式”。它会限制后台任务并限制 CPU 性能，给你更长的续航但更慢的设备。
|
||||||
|
|
||||||
|
多用户支持已经出现在安卓平板中有一段时间了，但棒棒糖终于将它带到了安卓手机上。设置界面添加了一个新的“用户”页面，让你添加额外的账户或设置一个“访客”账户。访客账户是临时的——它们可以一次点击轻松删除。它不会像正常账户那样尝试下载关联到你账户的每个应用，因为它注定要在不久后被删除。
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
作者简介：
|
||||||
|
|
||||||
|
Ron 是 Ars Technica 的评论编缉，专注于安卓系统和谷歌产品。他总是在追寻新鲜事物，还喜欢拆解事物看看它们到底是怎么运作的。
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/
|
||||||
|
|
||||||
|
作者：[RON AMADEO][a]
|
||||||
|
译者：[alim0x](https://github.com/alim0x)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: http://arstechnica.com/author/ronamadeo
|
||||||
|
[1]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[2]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[3]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[4]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[5]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[6]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[7]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[8]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[9]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[10]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[11]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[12]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[13]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[14]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[15]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[16]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[17]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[18]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[19]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[20]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[21]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[22]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[23]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[24]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[25]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[26]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[27]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[28]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[29]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[30]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[31]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[32]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[33]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[34]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[35]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/29/#
|
||||||
|
[36]:https://cdn.arstechnica.net/wp-content/uploads/2016/10/2-1.jpg
|
||||||
|
[37]:http://arstechnica.com/author/ronamadeo/
|
||||||
|
[38]:https://cdn.arstechnica.net/wp-content/uploads/2016/10/2-1.jpg
|
||||||
|
[39]:http://arstechnica.com/gadgets/2016/06/googles-new-two-factor-authentication-system-tap-yes-to-log-in/
|
||||||
|
[40]:https://www.theguardian.com/technology/2016/may/24/google-passwords-android
|
||||||
|
[41]:http://www.androidpolice.com/2015/12/22/google-appears-to-be-testing-a-new-way-to-log-into-your-account-on-other-devices-with-just-your-phone-no-password-needed/
|
||||||
Loading…
Reference in New Issue
Block a user