Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: Fixes to Behavior Changes page for N-Preview

Browse Source 
Change-Id: I77cd81e8fd7feb559e49d3d7a7673e7febc5a5c7
This commit is contained in:
David Friedman
2016-03-09 02:20:34 -08:00
parent 3b100bd94d
commit 10594f3cb3
1 changed files with 9 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/html/preview/behavior-changes.jd
View File

@@ -523,24 +523,21 @@ JavaVM::AttachCurrentThread from <jni.h>.
<h2 id="other">Other important points</h2>
<ul>
<li>On Android N, apps should be able to gracefully handle an out-of-memory
condition, or they might crash when the user changes display size and then
restores the app from Recents.</li>
<li>
Apps running on Android N but targeting lower API levels must be able to
gracefully handle their process being killed; they should
not crash on subsequent launches.
<li>When an app is running on Android N, but targets a lower API level,
and the user changes display size, the app process is killed. The app
must be able to gracefully handle this scenario. Otherwise, it crashes
when the user restores it from Recents.
<p>
You can diagnose this behavior by causing an identical crash
when killing the app manually via DDMS or automatically in a low-
or out-of-memory condition.
You should test your app to ensure
that this behavior does not occur.
You can do so by causing an identical crash
when killing the app manually via DDMS.
</p>
<p>
Apps targeting N and above are not automatically killed on density changes;
however, they may still respond poorly to configuration changes
however, they may still respond poorly to configuration changes.
</p>
</li>