From ff424377dff2896e8e7fd86b995f63888ae5cd2e Mon Sep 17 00:00:00 2001
From: Scott Rowe <scottrowe@google.com>
Date: Fri, 16 May 2014 10:54:04 -0700
Subject: [PATCH] cherrypick from klp-docs docs: b/14524668 remove ANDROID_ID
 Change-Id: I83d4389bb8322c2dbca10042e666fc9b75ea8a12

Change-Id: I2ee3cc1269fcd9b31f1f71fc5fc3cd8d62ebf31f
---
 docs/html/about/versions/android-4.2.jd | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/html/about/versions/android-4.2.jd b/docs/html/about/versions/android-4.2.jd
index 73d51c5577842..76acb8a013859 100644
--- a/docs/html/about/versions/android-4.2.jd
+++ b/docs/html/about/versions/android-4.2.jd
@@ -361,8 +361,7 @@ your server or use the registrations ID provided by <a
 href="{@docRoot}google/gcm/index.html">Google Cloud Messaging</a>.</p>
 
 <p>Beware that if your app requests one of the hardware device identifiers (such as the WiFi MAC
-address, the {@link android.os.Build#SERIAL} number, or the {@link
-android.provider.Settings.Secure#ANDROID_ID} number), they will provide the same value for each
+address or the {@link android.os.Build#SERIAL} number), they will provide the same value for each
 user because these identifiers are tied to the hardware and not the user. Not to mention the other
 problems these identifiers introduce as discussed in the <a
 href="http://android-developers.blogspot.com/2011/03/identifying-app-installations.html">Identifying