From 0a68693f79f963f89e81baa814c77b03cae7d611 Mon Sep 17 00:00:00 2001
From: David Friedman <dmail@google.com>
Date: Tue, 8 Mar 2016 15:01:40 -0800
Subject: [PATCH] Docs: Adding information on gotchas that devs need to know
 about in N

Change-Id: I9517dcf2738ed44d342c232e72f7bbabfca13eab
---
 docs/html/preview/behavior-changes.jd | 34 +++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd
index 1f8a74f86de32..db0d0cfea29e4 100644
--- a/docs/html/preview/behavior-changes.jd
+++ b/docs/html/preview/behavior-changes.jd
@@ -487,3 +487,37 @@ JavaVM::AttachCurrentThread from &lt;jni.h&gt;.
   been enabled on the device, this method returns a value of {@code null}.
   </li>
 </ul>
+
+<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.
+
+<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.
+</p>
+
+<p>
+Apps targeting N and above are not automatically killed on density changes;
+however, they may still respond poorly to configuration changes
+</p>
+</li>
+
+<li>
+Apps on Android N should be able to gracefully handle configuration changes,
+and should not crash on subsequent starts. You can verify app behavior
+by changing font size (<strong>Setting</strong> >
+<strong>Display</strong> > <strong>Font size</strong>), and then restoring
+the app from Recents.
+</li>
+</ul>
+