API Differences
See Also
diff --git a/docs/html/about/versions/nougat/android-7.0-samples.jd b/docs/html/about/versions/nougat/android-7.0-samples.jd index 98f7090bbb229..e283a7a22f83f 100644 --- a/docs/html/about/versions/nougat/android-7.0-samples.jd +++ b/docs/html/about/versions/nougat/android-7.0-samples.jd @@ -1,10 +1,11 @@ page.title=Android 7.0 Samples page.tags="Android 7.0", "nougat", "samples", "android" +meta.tags="android n", "Nougat", "android 7.0" page.image=images/cards/card-n-samples_2x.png @jd:body- The following code samples are provided for Android 7.0. To + Use the code samples below to learn about Android 7.0 capabilities and APIs. To download the samples in Android Studio, select the File > Import Samples menu option.
diff --git a/docs/html/about/versions/nougat/android-7.0-testing.jd b/docs/html/about/versions/nougat/android-7.0-testing.jd deleted file mode 100644 index f30382e0decc6..0000000000000 --- a/docs/html/about/versions/nougat/android-7.0-testing.jd +++ /dev/null @@ -1,190 +0,0 @@ -page.title=Android 7.0 Testing Guide -page.image=images/cards/card-n-guide_2x.png -meta.tags="preview", "testing" -page.tags="preview", "developer preview" - -@jd:body - -In this document
- -- Android 7.0 gives you an opportunity to ensure your apps work with the next - version of the platform. This preview includes a number of APIs and behavior changes that can - impact your app, as described in the API - Overview and Behavior Changes. In testing - your app with the preview, there are some specific system changes that you should focus on to - ensure that users have a good experience. -
- -- This guide describes the what and how to test preview features with your app. You should - prioritize testing of these specific preview features, due to their high potential impact on your - app's behavior: -
- - - -- For more information about how to set up devices or virtual devices with a preview system image - for testing, see Set up -the Android N SDK. -
- - -Testing Permissions
- -- The new Permissions model - changes the way that permissions are allocated to your app by the user. Instead of granting all - permissions during the install procedure, your app must ask the user for individual permissions - at runtime. For users this behavior provides more granular control over each app’s activities, as - well as better context for understanding why the app is requesting a specific permission. Users - can grant or revoke the permissions granted to an app individually at any time. This feature of - the preview is most likely to have an impact on your app's behavior and may prevent some of your - app features from working, or they may work in a degraded state. -
- -- This change affects all apps running on the new platform, even those not targeting the new - platform version. The platform provides a limited compatibility behavior for legacy apps, but you - should begin planning your app’s migration to the new permissions model now, with a goal of - publishing an updated version of your app at the official platform launch. -
- - -Test tips
- -- Use the following test tips to help you plan and execute testing of your app with the new - permissions behavior. -
- --
-
- Identify your app’s current permissions and the related code paths. -
- Test user flows across permission-protected services and data. -
- Test with various combinations of granted/revoked permission. -
- Use the {@code adb} tool to manage permssions from the command line:
-
-
-
- List permissions and status by group:
-
adb shell pm list permissions -d -g
-
- - Grant or revoke one or more permissions using the following syntax:
-adb shell pm [grant|revoke] <permission.name> ...
-
-
- - List permissions and status by group:
-
- Analyze your app for services that use permissions. -
Test strategy
- -- The permissions change affects the structure and design of your app, as well as - the user experience and flows you provide to users. You should assess your app’s current - permissions use and start planning for the new flows you want to offer. The official release of - the platform provides compatibility behavior, but you should plan on updating your app and not - rely on these behaviors. -
- -- Identify the permissions that your app actually needs and uses, and then find the various code - paths that use the permission-protected services. You can do this through a combination of - testing on the new platform and code analysis. In testing, you should focus on opting in to - runtime permissions by changing the app’s {@code targetSdkVersion} to the preview version. For - more information, see Set up -the Android N SDK. -
- -- Test with various combinations of permissions revoked and added, to highlight the user flows that - depend on permissions. Where a dependency is not obvious or logical you should consider - refactoring or compartmentalizing that flow to eliminate the dependency or make it clear why the - permission is needed. -
- -- For more information on the behavior of runtime permissions, testing, and best practices, see the - Permissions developer - preview page. -
- - -Testing Doze and App Standby
- -- The power saving features of Doze and App Standby limit the amount of background processing that - your app can perform when a device is in an idle state or while your app is not in focus. The - restrictions the system may impose on apps include limited or no network access, - suspended background tasks, suspended Notifications, ignored wake requests, and alarms. To ensure - that your app behaves properly with these power saving optimizations, you should test your app by - simulating these low power states. -
- -Testing your app with Doze
- -To test Doze with your app:
- --
-
- Configure a hardware device or virtual device with an Android N system image. -
- Connect the device to your development machine and install your app. -
- Run your app and leave it active. -
- Simulate the device going into Doze mode by running the following commands:
-
-
-$ adb shell dumpsys battery unplug -$ adb shell dumpsys deviceidle step -$ adb shell dumpsys deviceidle -h -
- -
- - Observe the behavior of your app when the device is re-activated. Make sure it - recovers gracefully when the device exits Doze. -
Testing apps with App Standby
- -To test the App Standby mode with your app:
- --
-
- Configure a hardware device or virtual device with an Android N system image. -
- Connect the device to your development machine and install your app. -
- Run your app and leave it active. -
- Simulate the app going into standby mode by running the following commands:
-
-
-$ adb shell am broadcast -a android.os.action.DISCHARGING -$ adb shell am set-idle <packageName> true -
- -
- - Simulate waking your app using the following command:
-
$ adb shell am set-idle <packageName> false
-
- - Observe the behavior of your app when it is woken. Make sure it recovers gracefully - from standby mode. In particular, you should check if your app's Notifications and background - jobs continue to function as expected. -
Auto Backup for Apps and Device-Specific Identifiers
- -If your app is persisting any device-specific identifiers, such as Google -Cloud Messaging registration ID, in internal storage, -make sure to follow best practices to exclude the storage -location from auto-backup, as described in Auto -Backup for Apps.
diff --git a/docs/html/about/versions/nougat/android-7.0.jd b/docs/html/about/versions/nougat/android-7.0.jd index 87c8d936c9ab1..1ca540c9c3891 100644 --- a/docs/html/about/versions/nougat/android-7.0.jd +++ b/docs/html/about/versions/nougat/android-7.0.jd @@ -1,6 +1,6 @@ -page.title=Android 7.0 APIs -meta.tags="Android 7.0", "android n", "Nougat" -page.tags="Android 7.0", "Nougat", "android n", "developer preview" +page.title=Android 7.0 for Developers +meta.tags="Nougat", "android n" +page.tags="Android 7.0", "Nougat", "android n" page.image=images/cards/card-n-apis_2x.png @jd:body @@ -52,16 +52,20 @@ page.image=images/cards/card-n-apis_2x.png
-Android 7.0
-(N)
-offers new features for users and app developers. This document provides
-an introduction to the most notable APIs. Make sure, also,
-to check out the
Make sure check out the
+
To learn more about +the consumer features of Android 7.0, visit www.android.com.
+Multi-window Support
diff --git a/docs/html/about/versions/nougat/index.jd b/docs/html/about/versions/nougat/index.jd index aaf7e92d55ab9..bb56d300291f6 100644 --- a/docs/html/about/versions/nougat/index.jd +++ b/docs/html/about/versions/nougat/index.jd @@ -1,4 +1,4 @@ -page.title=Android N Developer Preview +page.title=Android 7.0 Nougat page.tags="preview","developer" meta.tags="preview", "android" fullpage=true @@ -17,44 +17,44 @@ footer.hide=1 }) -Android 7.0 Nougat
- Android 7.0 Nougat brings a new crop of sweet features to your Android device. - Test your apps on Nexus and other devices. Support new system + Android 7.0 brings new features for performance, productivity, + and security. Test your apps with new system behaviors to save power and memory. - Extend your apps with multi-window UI, + Take advantage of multi-window UI, direct reply notifications and more.
- + Get started - +
+ {@docRoot}images/home/n-preview-hero_2x.png 2x" />
+ 
+ 