Lines Matching full:configuration
11 <li><a href="#define-configuration">Define Managed Configurations</a></li>
12 <li><a href="#check-configuration">Check Managed Configurations</a></li>
13 <li><a href="#listen-configuration">Listen for Managed Configuration Changes</a></li>
38 This guide shows how to implement managed configuration settings in
45 <strong>Note:</strong> For historical reasons, these configuration settings are known as
48 restrictions can actually implement a wide range of configuration options,
53 Remote Configuration Overview
57 Apps define the managed configuration options that can be remotely
59 changed by a managed configuration provider. If your app is running on an
61 can change your app's managed configuration.
67 enterprise administrator communicates configuration changes to the managed
68 configuration provider app. That app, in turn, changes the configurations on your app.
96 <h2 id="define-configuration">
101 Your app can support any managed configuration you want to define. You declare the
110 To define your app's remote configuration options, put the following element
125 one <code><restriction></code> child element for every configuration
131 managed configuration file. Your app is only allowed to have a
138 configuration schema to generate a remote console for IT
144 The managed configuration provider can query the app to find details
172 You use each configuration's <code>android:key</code> attribute to
173 read its value from a managed configuration bundle. For this reason,
174 each configuration must have a unique key string, and the string
192 each VPN server configuration in a bundle, with multiple bundles grouped
320 <h2 id="check-configuration">
326 configuration settings. Instead, you need to check what the managed
333 To find out the current configuration settings, your app uses a
343 <li>When the app is notified of a configuration change, as described in
344 <a href="#listen-configuration">Listen for Managed Configuration
362 current configuration settings by calling its
382 know the current configuration. Instead, you should call it once when your app
385 ACTION_APPLICATION_RESTRICTIONS_CHANGED} intent to find out if the configuration
387 <a href="#listen-configuration">Listen for Managed Configuration Changes</a>.
397 containing a key-value pair for each configuration that has been set. The
401 configuration settings with the standard {@link android.os.Bundle} methods for
409 contains one item for every configuration that has been explicitly set by a
411 configuration will be present in the bundle just because you defined a default
417 managed configuration settings. For example, if your app has a
418 configuration specifying whether it can download data over a
419 cellular connection, and you find that the configuration is set to
443 and cast as a {@link android.os.Bundle}. In this example, each VPN's configuration
467 // ...choose a VPN configuration or prompt user to select from list
470 <h2 id="listen-configuration">
471 Listen for Managed Configuration Changes
478 this intent so you can change the app's behavior when the configuration settings
499 // Get the current configuration bundle
502 // Check current configuration settings, change your app's UI and
511 about configuration changes when it is paused. Instead, you should unregister
514 <a href="#check-configuration">Check Managed Configurations</a>), then register
515 your broadcast receiver to make sure you're notified about configuration changes
