五陵年少金市东，银鞍白马渡春风。这篇文章主要讲述Android 6.0 Changes相关的知识，希望能为你提供帮助。




【Android 6.0 Changes】
Android 6.0 变化    Android 6.0 ChangesIn this document

1. 执行时权限
   Runtime Permissions
2. Doze and App Standby
3. 阿帕奇 HTTPClient 移除
4. Apache HTTP Client Removal
5. OpenSSL 的分支 BoringSSL
6. BoringSSL
7. 訪问硬件标识
8. Access  to  Hardware Identifiers
9. 通知
10. Notifications
11. 音频管理变化
12. AudioManager Changes
13. 文本选择
14. Text Selection
15. 浏览器书签变化
16. Browser Bookmark Changes
17. Android 密钥库变化
18. android Keystore Changes
19. Wi-Fi 和网络变化
20. Wi-Fi and Networking Changes
21. 像机服务变化
22. Camera Service Changes
23. 执行时变化
24. Runtime
25. APK 校验
26. APK Validation
27. USB 连接
28. USB Connection
29. Android 使用变化
30. Android for Work Changes

API Differences

1. API level 22  to  23 ?

See Also

1. Android 6.0 API Overview

伴随着新特性和功能，Android 6.0 （API level 23）包括了各种各样的系统变化和 API 行为变化。本文突出一些关键的变化，这些变化在你的应用中须要考虑到和处理。

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.
假设你先前公布过 Android 应用。就要了解这个平台影响你的应用的一些变化。

If you have previously published an app for Android, be aware that these changes in the platform affect your app.
执行时权限Runtime PermissionsThis 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.
Doze and App StandbyThis 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.

• Doze: If a user unplugs a device and leaves it stationary, with its screen off, for a period of time, the device goes intoDoze  mode, where it attempts to keep the system in a sleep state. In this mode, devices periodically resume normal operations for brief periods of time so that app syncing can occur and the system can perform any pending operations.
• App Standby: App Standby allows the system to determine that an app is idle when the user is not actively using it. The system makes this determination  when the user does not touch the app for a certain period of time. If the device is unplugged, the system disables network access and suspends syncs and jobs for the apps it deems idle.

To learn more about these power-saving changes, see  Optimizing for Doze and App Standby.
Apache HTTP Client RemovalAndroid 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‘ }

BoringSSLAndroid 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.
Access  to  Hardware IdentifierTo 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:

• WifiManager.getScanResults()
• BluetoothDevice.ACTION_FOUND
• BluetoothLeScanner.startScan()

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.
NotificationsThis 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 thebuild()  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.
AudioManager ChangesSetting 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  valueADJUST_MUTE  or  ADJUST_UNMUTE.
Text Selection
文章图片
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:

1. In your  View  or  Activity  object, change yourActionMode  calls from  startActionMode(Callback)to  startActionMode(Callback, ActionMode.TYPE_FLOATING).
2. Take your existing implementation  ofActionMode.Callback  and make it extendActionMode.Callback2  instead.
3. Override the  onGetContentRect()  method to provide the coordinates of the content  Rect  object (such as a text selection  rectangle) in the view.
4. If the rectangle positioning is no longer valid, and this is the  only element to be invalidated, call theinvalidateContentRect()  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 call  setHandleNativeActionModesEnabled()  on  the returnedAppCompatDelegate  object and set the input parameter  to  false. 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.
Browser Bookmark ChangesThis 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 Keystore ChangesWith 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 (forexample, by the user or a Device Administrator). Keys which require encryption at rest will be deleted during these events.
Wi-Fi and Networking ChangesThis release introduces the following behavior changes to the Wi-Fi and networking APIs.

• Your apps can now change the state of  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.
• Previously, if an app forced the device to connect to a specific Wi-Fi network by using  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.

Camera Service ChangesIn 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:

• Access to camera subsystem resources, including opening and configuring a camera device, is awarded based on the “priority” of the client application process. Application processes with user-visible or foreground activities are generally given a higher-priority, making camera resource acquisition and use more dependable.
• Active camera clients for lower priority apps may be “evicted” when a higher priority application  attempts to use the camera. In the deprecated  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.
• On devices with appropriate camera hardware, separate application processes are able to independently open and use separate camera devices simultaneously. However, multi-process use cases, where simultaneous access causes significant degradation of performance or capabilities of any of the open camera devices, are now detected and disallowed by the camera service. This change may result in “evictions” for lower priority clients even when no other app is directly attempting to access the same camera device.
• Changing the current user causes active camera clients in apps owned by the previous user account to be evicted. Access to the camera is limited to user profiles owned by the current device user. In practice, this means that a “Guest” account, for  example, will not be able to leave running processes that use the camera subsystem when the user has switched to a different account.

RuntimeThe 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  classconstructors 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 (id=6670" class="external-link" style="color: rgb(3, 155, 229); text-decoration: none; padding-right: 16px; background: url(http://developer.android.com/assets/images/styles/open_new_page.png) 100% 50% no-repeat; ">  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.
APK ValidationThe 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.
USB ConnectionDevice 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.
Android for Work ChangesThis release includes the following behavior changes for Android for Work:

• Work contacts in personal  contexts.  The Google Dialer Call Log now displays work contacts when the user views past calls. Setting  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.
• Wi-Fi configuration removal:  Wi-Fi configurations added by a Profile Owner (for example, through calls to theaddNetwork()  method) are now removed if that work profile is deleted.
• Wi-Fi configuration lockdown:  Any Wi-Fi configuration created by an active Device Owner can no longer be modified or deleted by the user if  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.
• Download Work Policy Controller via Google account  addition:  When a Google account that requires management via a Work Policy Controller (WPC) app is  added to a device outside of a managed context, the  add  account flow now prompts the user to install the appropriate WPC. This behavior also applies to accounts  added via  Settings > Accountsand in the initial device setup wizard.
• Changes  to  specific  DevicePolicyManager  API behaviors:
  • Calling the  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.
  • In  addition, the  setKeyguardDisabledFeatures()  method is now available for Profile Owners, as well as  to  Device Owners.
  • A Profile Owner can set these keyguard restrictions:
    • 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.
  • The  createAndInitializeUser()  and  createUser()  methods have been deprecated.
  • The  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.
  • Device initializer APIs  which  existed in the Android 6.0 (API level 23) are now removed.
  • EXTRA_PROVISIONING_RESET_PROTECTION_PARAMETERS  is removed so NFC bump provisioning cannot programmatically unlock a factory reset protected device.
  • You can now use the  EXTRA_PROVISIONING_ADMIN_EXTRAS_BUNDLE  extra to pass data to the device owner app during NFC provisioning of the managed device.
  • Android for Work APIs are optimized for M runtime permissions, including Work profiles, assist layer, and others. New  DevicePolicyManager  permission APIs don‘t affect pre-M apps.
  • When users back out of the synchronous part of the setup flow initiated through anACTION_PROVISION_MANAGED_PROFILE  or  ACTION_PROVISION_MANAGED_DEVICE  intent, the system now returns aRESULT_CANCELED  result code.
• Changes  to  other APIs:
  • Data Usage: The  android.app.usage.NetworkUsageStats  class  has been renamed  NetworkStats.
• Changes  to  global settings:
  • These settings can no longer be set via  setGlobalSettings():
    • BLUETOOTH_ON
    • DEVELOPMENT_SETTINGS_ENABLED
    • MODE_RINGER
    • NETWORK_PREFERENCE
    • WIFI_ON
  • These global settings can now be set via  setGlobalSettings():
    • WIFI_DEVICE_OWNER_CONFIGS_LOCKDOWN

推荐阅读

• 

  炒生菜的做法_炒生菜怎么做好吃
• 

  公众号多条菜单怎么弄，微信公众号怎么设置多个菜单
• 

  被追尾对方逃逸怎么处理
• 

  申请最便宜的国外ip服务器，最便宜的国外vps
• 

  刨花板和实木颗粒板哪个好
• 

  衣服去甲醛是水洗还是暴晒好 刚买的衣服怎么去甲醛
• 

  丑苹果有什么营养价值
• 

  牛蒡茶能代替牛蒡根吗 牛蒡根可以代替牛蒡茶吗
• 

  洗衣液一次用多少？一升洗衣液等于多少斤？
• 

  乾隆是嘉庆杀的吗
• 

  海贼王里面的一只兔子
• 

  可达性分析算法与Java引用类型
• 

  几何画板利用第二定义画椭圆 几何画板使用椭圆第二定义绘制椭圆的操作方法
• 

  电脑象棋，在电脑上怎样玩象棋残局在那里能玩
• 

  石斛山药酒——补肾养阴健脾胃
• 

  佳能ixus
• 

  庭院驱蚊灯哪个牌子效果好？庭院驱蚊灯十大品牌排行
• 

  林内热水器故障代码12是什么 林内热水器故障代码16
• 

  糯米糍粑要煎几分钟能熟 糯米糍要煮多久才熟
• 

  西安北大街国美第一次购2300

• android深入之设计模式托付模式
• 万里征程——Windows App开发控件大集合1
• 开源的图像滤镜库----for Android
• Sqoop与Hadoop生态系统的集成
• Sqoop安装
• Sqoop导入
• Sqoop导出
• Sqoop教程
• RDBMS与HBase的区别