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

cherrypick from lmp-docs docs: Listening for restrictions-changed

Browse Source 
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
This commit is contained in:
Andrew Solovay
2015-03-20 11:44:33 -07:00
parent 92ae292e86
commit 26a8090a09
1 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/html/training/enterprise/app-restrictions.jd
View File

@@ -316,8 +316,18 @@ if (!appCanUseCellular) {
{@link android.content.Intent#ACTION_APPLICATION_RESTRICTIONS_CHANGED {@link android.content.Intent#ACTION_APPLICATION_RESTRICTIONS_CHANGED
ACTION_APPLICATION_RESTRICTIONS_CHANGED} intent. Your app has to listen for 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 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 change.</p>
receiver for this intent:
<p class="note">
<strong>Note:</strong> The {@link
android.content.Intent#ACTION_APPLICATION_RESTRICTIONS_CHANGED
ACTION_APPLICATION_RESTRICTIONS_CHANGED} intent is sent only to listeners
that are dynamically registered, <em>not</em> to listeners that are declared
in the app manifest.
</p>
<p>
The following code shows how to dynamically register a broadcast receiver for
this intent:
</p> </p>
<pre>IntentFilter restrictionsFilter = <pre>IntentFilter restrictionsFilter =