标签：
Along with new features and capabilities, Android 6.0 (API level 23) includes a variety of system changes and API behavior changes. This document highlights some of the key changes that you should understand and account for in your apps.
If you have previously published an app for Android, be aware that these changes in the platform affect your app.
包括Android 6.0（API等级23）新的特性和功能，各种制度变迁和API行为更改。本文主要介绍了一些你应该了解的重要变化。
如果您发布了以前版本的Android应用，请注意这些变化对您应用程序的影响。
This release introduces a new permissions model, where users can now directly manage app permissions at runtime. This model gives users improved visibility and control over permissions, while streamlining the installation and auto-update processes for app developers. Users can grant or revoke permissions individually for installed apps.
On your apps that target Android 6.0 (API level 23) or higher, make sure to check for and request permissions at runtime. To determine if your app has been granted a permission, call the new checkSelfPermission() method. To request a permission, call the new requestPermissions() method. Even if your app is not targeting Android 6.0 (API level 23), you should test your app under the new permissions model.
For details on supporting the new permissions model in your app, see Working with System Permissions. For tips on how to assess the impact on your app, see Permissions Best Practices.
这个版本引入了新的权限管理模块，用户现在可以直接管理运行时应用程序的权限。这种模式为用户提供了更好的可视性和权限控制，同时简化了应用程序开发人员安装和自动更新过程。用户可以单独授予或撤销安装的应用程序的权限。
在您的目标版本6.0（API级别23）或更高的Android应用程序中，请务必在运行时检查并请求的权限。要确定您的应用程序是否已被授予了某个权限，可以调用新的checkSelfPermission（）方法。要请求权限，调用新的requestPermissions（）方法。即使您的应用程序没有针对Android6.0（API等级23），你也应该测试下的新权限管理模块。
为了在你的应用程序的详细信息中支持新的权限管理模块，请参阅Working with System Permissions.有关如何评估对你的应用程序的影响，请参 Permissions Best Practices。
This release introduces new power-saving optimizations for idle devices and apps. These features affect all apps so make sure to test your apps in these new modes.
To learn more about these power-saving changes, see Optimizing for Doze and App Standby.
这个版本引入了对闲置设备和应用程序新的节能优化。这些功能会影响所有的应用程序，所以确保你的应用程序已测试这些新的模式。
打盹：如果在一段时间内一个用户拔掉一个设备并使其静止的，而其屏幕关闭，装置会进入打盹模式（试图保持系统处于睡眠状态）。在这种模式下，设备周期性地短时间恢复正常操作，使得应用程序可以同步，并且系统可以执行任何挂起的操作。
App待机：App待机允许系统来确定当用户不积极地使用某个应用时这个应用处于空闲状态。当用户不操作某个应用一定时间后，系统会做出此确定。如果设备拔出后，系统将关闭网络访问，并暂停其认为空闲的应用程序的同步和工作。
要了解更多有关这些节能的变化，请参阅优化了打盹和App待机。
（unplugs a device 的具体意义不确定，这个和google 云有关？）
Android 6.0 release removes support for the Apache HTTP client. If your app is using this client and targets Android 2.3 (API level 9) or higher, use the HttpURLConnection class instead. This API is more efficient because it reduces network use through transparent compression and response caching, and minimizes power consumption. To continue using the Apache HTTP APIs, you must first declare the following compile-time dependency in your build.gradle file:
android {
useLibrary ‘org.apache.http.legacy‘
}
就是移除了对Apache HTTP client建议用HttpURLConnection，如果非得用自己把库引进去（在SDK的平台23可选文件夹下有）
Android is moving away from OpenSSL to the BoringSSL library. If you’re using the Android NDK in your app, don‘t link against cryptographic libraries that are not a part of the NDK API, such as libcrypto.so and libssl.so. These libraries are not public APIs, and may change or break without notice across releases and devices. In addition, you may expose yourself to security vulnerabilities. Instead, modify your native code to call the Java cryptography APIs via JNI or to statically link against a cryptography library of your choice.
不用OpenSSL用BoringSSL了。后面是关于libcrypto.so 和 libssl.soNDK的事，就不翻译了
To provide users with greater data protection, starting in this release, Android removes programmatic access to the device’s local hardware identifier for apps using the Wi-Fi and Bluetooth APIs. The WifiInfo.getMacAddress() and theBluetoothAdapter.getAddress() methods now return a constant value of 02:00:00:00:00:00.
To access the hardware identifiers of nearby external devices via Bluetooth and Wi-Fi scans, your app must now have theACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION permissions:
Note: When a device running Android 6.0 (API level 23) initiates a background Wi-Fi or Bluetooth scan, the operation is visible to external devices as originating from a randomized MAC address.
为了给用户提供更好的数据保护，从此版本起，Android删除了使用Wi-Fi和蓝牙访问设备的本地硬件标识的代码。WifiInfo.getMacAddress（）和theBluetoothAdapter.getAddress（）方法现在返回常量02：00：00：00：00：00。
要通过蓝牙和Wi-Fi扫描访问附近外部设备的硬件标识符，你的应用程序现在必须拥有ACCESS_FINE_LOCATION或ACCESS_COARSE_LOCATION权限：
WifiManager.getScanResults（）
BluetoothDevice.ACTION_FOUND
BluetoothLeScanner.startScan（）
注意：当运行Android6.0（API等级23）的设备启动后台Wi-Fi或蓝牙扫描，此操作对外部设备来说是一个可见的随机的MAC地址。
This release removes the Notification.setLatestEventInfo() method. Use the Notification.Builder class instead to construct notifications. To update a notification repeatedly, reuse the Notification.Builder instance. Call the build() method to get updated Notification instances.
The adb shell dumpsys notification command no longer prints out your notification text. Use the adb shell dumpsys notification --noredact command instead to print out the text in a notification object.
删除了 Notification.setLatestEventInfo()方法 用Notification.Builder来创建和重用（更新）通知
用 adb shell dumpsys notification --noredact 打印通知
Setting the volume directly or muting specific streams via the AudioManager class is no longer supported. ThesetStreamSolo() method is deprecated, and you should call the requestAudioFocus() method instead. Similarly, thesetStreamMute() method is deprecated; instead, call the adjustStreamVolume() method and pass in the direction value ADJUST_MUTE or ADJUST_UNMUTE.
通过AudioManager类直接调整音量或静音不再支持。 setStreamSolo（）方法已过时，您应该调用requestAudioFocus（）方法。同样，setStreamMute（）方法已过时;应该调用adjustStreamVolume（）方法并传递的方向值ADJUST_MUTE或ADJUST_UNMUTE。
When users select text in your app, you can now display text selection actions such as Cut, Copy, and Paste in afloating toolbar. The user interaction implementation is similar to that for the contextual action bar, as described inEnabling the contextual action mode for individual views.
To implement a floating toolbar for text selection, make the following changes in your existing apps:
View or Activity object, change yourActionMode calls from startActionMode(Callback)to startActionMode(Callback, ActionMode.TYPE_FLOATING).ActionMode.Callback and make it extendActionMode.Callback2 instead.onGetContentRect() method to provide the coordinates of the content Rect object (such as a text selection rectangle) in the view.invalidateContentRect() method.If you are using Android Support Library revision 22.2, be aware that floating toolbars are not backward-compatible and appcompat takes control over ActionMode objects by default. This prevents floating toolbars from being displayed. To enable ActionMode support in anAppCompatActivity, call getDelegate(), then callsetHandleNativeActionModesEnabled() on the returned AppCompatDelegate object and set the input parameter tofalse. This call returns control of ActionMode objects to the framework. In devices running Android 6.0 (API level 23), that allows the framework to support ActionBar or floating toolbar modes, while on devices running Android 5.1 (API level 22) or lower, only the ActionBar modes are supported.
当用户在应用程序中选择文本，你现在可以显示文本选择操作，如剪切，复制，在一个悬浮的工具栏中。用户交互实现类似于对上下文动作栏的实现，详见Enabling the contextual action mode for individual views.
为了实现文本选择的浮动工具栏，您现有的应用程序中请进行以下更改：
1.在您的View or Activity对象，改变你的ActionMode回调，从startActionMode（Callback）到startActionMode(Callback, ActionMode.TYPE_FLOATING).
2.把你现有的实现ActionMode.Callback的类改为继承extendActionMode.Callback2。
3.重写onGetContentRect（）方法来提供内容的矩形对象在视图中的坐标（如文本选择矩形）。
4.如果矩形定位不再有效，并且这是唯一被无效的组件，请调用theinvalidateContentRect（）方法。
如果您使用的是 Android Support Library revision 22.2，要知道，浮动工具栏不向后兼容和appcompat接管默认ActionMode对象的控制权。这可以防止漂浮被显示的工具栏。要启用anAppCompatActivity ActionMode支持，请调用getDelegate（），然后调用setHandleNativeActionModesEnabled（）返回AppCompatDelegate对象上，并设置输入参数为false。此调用返回控制ActionMode对象的框架。在运行Android 6.0（API等级23）的设备中，允许此框架来支持动作条或浮动工具栏模式，而在运行Android 5.1（API级别22）或更低的设备，只有对 ActionBar 的支持。
This release removes support for global bookmarks. The android.provider.Browser.getAllBookmarks() andandroid.provider.Browser.saveBookmark() methods are now removed. Likewise, the READ_HISTORY_BOOKMARKS andWRITE_HISTORY_BOOKMARKS permissions are removed. If your app targets Android 6.0 (API level 23) or higher, don‘t access bookmarks from the global provider or use the bookmark permissions. Instead, your app should store bookmarks data internally.
此版本删除了对全局书签的支持。该android.provider.Browser.getAllBookmarks（）和android.provider.Browser.saveBookmark（）方法现在已被删除。同样地，READ_HISTORY_BOOKMARKS 和WRITE_HISTORY_BOOKMARKS权限被除去。如果您的应用目标Android6.0（API级别23）或更高，不要访问全局书签provider或使用书签权限。相反，您的应用程序应该在内部存储书签数据。
With this release, the Android Keystore provider no longer supports DSA. ECDSA is still supported.
Keys which do not require encryption at rest will no longer be deleted when secure lock screen is disabled or reset (for example, by the user or a Device Administrator). Keys which require encryption at rest will be deleted during these events.
在此版本中，Android的密钥库提供程序不再支持DSA。ECDSA仍然支持。
当锁屏被禁用或复位（例如，由用户或设备管理员）按键，不需要加密的其余部分将不再被删除。其余需要加密的密钥将被删除。
This release introduces the following behavior changes to the Wi-Fi and networking APIs.
WifiConfiguration objects only if you created these objects. You are not permitted to modify or delete WifiConfiguration objects created by the user or by other apps.enableNetwork() with thedisableAllOthers=true setting, the device disconnected from other networks such as cellular data. In This release, the device no longer disconnects from such other networks. If your app’s targetSdkVersion is “20” or lower, it is pinned to the selected Wi-Fi network. If your app’s targetSdkVersion is “21” or higher, use the multinetwork APIs (such as openConnection(), bindSocket(), and the new bindProcessToNetwork() method) to ensure that its network traffic is sent on the selected network.这个版本引入了对无线网络连接和网络API的更改如下：
In This release, the model for accessing shared resources in the camera service has been changed from the previous “first come, first serve” access model to an access model where high-priority processes are favored. Changes to the service behavior include:
Camera API, this results in onError() being called for the evicted client. In the Camera2API, it results in onDisconnected() being called for the evicted client.在此版本中，该模型用于访问共享资源的相机业务已经从之前的“先来先服务”的访问模式，其中高优先级进程所青睐??的访问模式。更改为：
The ART runtime now properly implements access rules for the newInstance() method. This change fixes a problem where Dalvik was checking access rules incorrectly in previous versions. If your app uses the newInstance() method and you want to override access checks, call the setAccessible() method with the input parameter set to true. If your app uses the v7 appcompat library or the v7 recyclerview library, you must update your app to use to the latest versions of these libraries. Otherwise, make sure that any custom classes referenced from XML are updated so that their class constructors are accessible.
This release updates the behavior of the dynamic linker. The dynamic linker now understands the difference between a library’s soname and its path ( public bug 6670), and search by soname is now implemented. Apps which previously worked that have bad DT_NEEDED entries (usually absolute paths on the build machine’s file system) may fail when loaded.
The dlopen(3) RTLD_LOCAL flag is now correctly implemented. Note that RTLD_LOCAL is the default, so calls todlopen(3) that didn’t explicitly use RTLD_LOCAL will be affected (unless your app explicitly used RTLD_GLOBAL). WithRTLD_LOCAL, symbols will not be made available to libraries loaded by later calls to dlopen(3) (as opposed to being referenced by DT_NEEDED entries).
On previous versions of Android, if your app requested the system to load a shared library with text relocations, the system displayed a warning but still allowed the library to be loaded. Beginning in this release, the system rejects this library if your app‘s target SDK version is 23 or higher. To help you detect if a library failed to load, your app should log the dlopen(3) failure, and include the problem description text that the dlerror(3) call returns. To learn more about handling text relocations, see this guide.
ART runtime现在可以正确地实现访问规则中的newInstance（）方法。这修复了此前一个bug。如果你的应用程序使用newInstance（）方法，并要覆盖访问检查，调用setAccessible（）方法的输入参数设置为true。如果你的应用程序使用V7 appcompat库或V7 recyclerview库，您必须更新您的应用程序使用这些库的最新版本。否则，请确保从XML引用的任何自定义类已更新，这样它们的类的构造函数可以访问。
此版本更新动态链接程序的行为。动态链接器现在明白库的SONAME和它的路径的区别，而且通过 soname搜索现已实现。装载时有坏DT_NEEDED项（通常是在build机器的文件系统上的绝对路径），这在以前的应用程序中可能会失败。
dlopen（3）RTLD_LOCAL标志现在可以正确实施。需要注意的是RTLD_LOCAL是默认的，所以调用todlopen（3）没有明确使用RTLD_LOCAL会受到影响（除非你的应用程序明确使用RTLD_GLOBAL）。 WithRTLD_LOCAL，符号将不被提供给由以后的调用加载到dlopen（3）（而不是由DT_NEEDED条目被引用）库。
在Android的早期版本中，如果您的应用程序请求系统来加载有文本重定位的共享库，系统将显示一个警告，但仍允许加载。在这个版本开始，系统将拒绝加载这个库，如果你的应用程序的目标SDK版本为23或更高。为了帮助您检测一个库加载失败，您的应用程序应该记录的dlopen（3）故障，包括问题的描述文本的dlerror（3）回调。要了解更多关于处理文本重定位，请参阅guide
The platform now performs stricter validation of APKs. An APK is considered corrupt if a file is declared in the manifest but not present in the APK itself. An APK must be re-signed if any of the contents are removed.
平台现在执行的APK更严格的验证。如果一个文件在manifest 中声明，但没有出现在APK本身，此APK会被认为是冲突的。如果任何的内容被删除一个APK必须重新签名。
Device connections through the USB port are now set to charge-only mode by default. To access the device and its content over a USB connection, users must explicitly grant permission for such interactions. If your app supports user interactions with the device over a USB port, take into consideration that the interaction must be explicitly enabled.
通过USB端口的设备连接现在设置在默认情况下被设置为仅充电模式。要访问设备，并对其内容通过USB连接，用户必须明确地给这种操作许可。如果您的应用程序允许用户通过USB端口和设备交互，此交互必须显式启用。
This release includes the following behavior changes for Android for Work:
此版本包括Android的以下行为变化for Work：
setCrossProfileCallerIdDisabled() to true hides the work profile contacts in the Google Dialer Call Log. Work contacts can be displayed along with personal contacts to devices over Bluetooth only if you setsetBluetoothContactSharingDisabled() to false. By default, it is set to true.addNetwork() method) are now removed if that work profile is deleted.WIFI_DEVICE_OWNER_CONFIGS_LOCKDOWN is non-zero. The user can still create and modify their own Wi-Fi configurations. Active Device Owners have the privilege of editing or removing any Wi-Fi configurations, including those not created by them.DevicePolicyManager API behaviors:
setCameraDisabled() method affects the camera for the calling user only; calling it from the managed profile doesn’t affect camera apps running on the primary user.setKeyguardDisabledFeatures() method is now available for Profile Owners, as well as to Device Owners.KEYGUARD_DISABLE_TRUST_AGENTS and KEYGUARD_DISABLE_FINGERPRINT, which affect the keyguard settings for the profile’s parent user.KEYGUARD_DISABLE_UNREDACTED_NOTIFICATIONS, which only affects notifications generated by applications in the managed profile.createAndInitializeUser() and createUser() methods have been deprecated.setScreenCaptureDisabled() method now also blocks the assist structure when an app of the given user is in the foreground.EXTRA_PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM now defaults to SHA-256. SHA-1 is still supported for backwards compatibility but will be removed in future. EXTRA_PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUMnow only accepts SHA-256.EXTRA_PROVISIONING_RESET_PROTECTION_PARAMETERS is removed so NFC bump provisioning cannot programmatically unlock a factory reset protected device.EXTRA_PROVISIONING_ADMIN_EXTRAS_BUNDLE extra to pass data to the device owner app during NFC provisioning of the managed device.DevicePolicyManager permission APIs don‘t affect pre-M apps.ACTION_PROVISION_MANAGED_PROFILE or ACTION_PROVISION_MANAGED_DEVICE intent, the system now returns aRESULT_CANCELED result code.android.app.usage.NetworkUsageStats class has been renamed NetworkStats.setGlobalSettings():
BLUETOOTH_ONDEVELOPMENT_SETTINGS_ENABLEDMODE_RINGERNETWORK_PREFERENCEWIFI_ONsetGlobalSettings():
工作接触的个人背景。在谷歌拨号呼叫日志现在显示的工作接触，当用户查看过去的电话。设置setCrossProfileCallerIdDisabled（）为true隐藏在谷歌拨号呼叫记录的工作轮廓接触。工作的联系人只能与您setsetBluetoothContactSharingDisabled个人接触到设备通过蓝牙（）为false一起显示。默认情况下，它被设置为true。
Wi-Fi配置去除：无线网络配置，通过配置文件所有者增加（例如，通过调用theaddNetwork（）方法），如果该工作文件被删除，现在删除。
Wi-Fi配置锁定：通过积极的设备所有者创建的任何Wi-Fi配置不能再进行修改或删除用户如果WIFI_DEVICE_OWNER_CONFIGS_LOCKDOWN不为零。用户仍然可以创建和修改自己的无线网络配置。有源器件业主编辑的特权或删除任何Wi-Fi配置，包括那些不是由他们创建的。
下载工作策略控制器通过谷歌帐户另外：当需要通过工作方针控制器（WPC）的应用程序管理一个谷歌帐户添加到一个设备上的受控环境之外，添加帐户流程现在提示安装相应的WPC用户。这种行为也适用于通过设置>帐户与初始设备设置向导添加帐户。
更改特定DevicePolicyManager API的行为：
调用setCameraDisabled（）方法会影响相机仅主叫用户;从管理的个人资料调用它不会影响主用户运行相机应用程序。
此外，setKeyguardDisabledFeatures（）方法现在可用于资料业主，以及对设备的用户。
一个业主的个人资料可以设置这些键盘锁的限制：
KEYGUARD_DISABLE_TRUST_AGENTS和KEYGUARD_DISABLE_FINGERPRINT，从而影响该配置文件的父用户的键盘锁设置。
KEYGUARD_DISABLE_UNREDACTED_NOTIFICATIONS，受影响的只是通过在管理配置文件的应用程序生成的通知。
该createAndInitializeUser（）和的createUser（）方法已被弃用。
该setScreenCaptureDisabled（）方法现在也阻止辅助结构，当给定用户的应用程序是在前台。
EXTRA_PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM现在默认SHA-256。 SHA-1仍然支持向后兼容性，但会在将来被移除。 EXTRA_PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUMnow只接受的SHA-256。
它存在在Android 6.0（API等级23）设备初始化的API，现在删除。
EXTRA_PROVISIONING_RESET_PROTECTION_PARAMETERS被删除，因此NFC凹凸供应不能以编程方式解锁恢复出厂设置保护装置。
现在，您可以使用EXTRA_PROVISIONING_ADMIN_EXTRAS_BUNDLE额外的过程中被管理设备的NFC配置数据传递给设备所有者的应用程序。
的Andr??oid为工作API是对于M运行权限优化，包括工作型材，辅助层及其它。新DevicePolicyManager权限的API不影响预-M的应用程序。
当用户退了出来，通过anACTION_PROVISION_MANAGED_PROFILE或ACTION_PROVISION_MANAGED_DEVICE意图发起的设置流程的同步部分，该系统现在返回aRESULT_CANCELED结果代码。
更改为其他API：
数据用途：android.app.usage.NetworkUsageStats类已更名为NetworkStats。
更改全局设置：
这些设置可以不再经由setGlobalSettings设置（）：
BLUETOOTH_ON
DEVELOPMENT_SETTINGS_ENABLED
MODE_RINGER
NETWORK_PREFERENCE
WIFI_ON
这些全局设置，现在可以通过setGlobalSettings设置（）：
WIFI_DEVICE_OWNER_CONFIGS_LOCKDOWN
（这个Work不知道是干什么的...）
【译】Android 6.0 Changes （机翻加轻微人工校对）
标签：
原文地址：http://www.cnblogs.com/iknownothing/p/4931972.html
