From 26a8090a09bce05398cc52581ea4a5cf05d28d59 Mon Sep 17 00:00:00 2001 From: Andrew Solovay Date: Fri, 20 Mar 2015 11:44:33 -0700 Subject: cherrypick from lmp-docs docs: Listening for restrictions-changed Original Change-Id: I19c7150a9f36de226d00ad6d8db0e9210d5d135d Per bug 19848206, it turns out that APPLICATION_RESTRICTIONS_CHANGED is only sent to dynamically-declared listeners, *not* to listeners declared in the manifest. Updated doc to note this. (The code snippet already showed how to dynamically declare a listener.) See first comment for doc stage location. bug: 19848206 Change-Id: I6dc5f39dc6eed71cf2e303564ea906be3832d8a4 --- docs/html/training/enterprise/app-restrictions.jd | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) (limited to 'docs/html/training') diff --git a/docs/html/training/enterprise/app-restrictions.jd b/docs/html/training/enterprise/app-restrictions.jd index fc5dfcc..dd2c2c0 100644 --- a/docs/html/training/enterprise/app-restrictions.jd +++ b/docs/html/training/enterprise/app-restrictions.jd @@ -316,8 +316,18 @@ if (!appCanUseCellular) { {@link android.content.Intent#ACTION_APPLICATION_RESTRICTIONS_CHANGED ACTION_APPLICATION_RESTRICTIONS_CHANGED} intent. Your app has to listen for this intent so you can change the app's behavior when the restriction settings - change. The following code shows how to dynamically register a broadcast - receiver for this intent: + change.

+ +

+ Note: The {@link + android.content.Intent#ACTION_APPLICATION_RESTRICTIONS_CHANGED + ACTION_APPLICATION_RESTRICTIONS_CHANGED} intent is sent only to listeners + that are dynamically registered, not to listeners that are declared + in the app manifest. +

+

+ The following code shows how to dynamically register a broadcast receiver for + this intent:

IntentFilter restrictionsFilter =
-- 
cgit v1.1