| /frameworks/base/docs/html/training/enterprise/ |
| D | app-compatibility.jd | 27 <a href="{@docRoot}about/versions/android-5.0.html#Enterprise">managed
28 profiles</a>. A managed profile is controlled by an administrator, and the
35 reliably on a device with managed profiles. You don't need to do anything
37 practices become especially important on devices with managed profiles. This
48 set up <i>managed profiles</i>. If a device has a managed profile, the profile's
53 <p>If a device has a managed profile, there are implications for apps
64 managed profile. This restriction can also result in there being no handler for
65 some common intents on the managed profile.</li>
66 <li>Since the managed and unmanaged profiles have separate storage areas, a
75 <p>On a device with a managed profile, there are restrictions on whether intents
[all …]
|
| D | work-policy-ctrl.jd | 2 …Learn how to develop a Work Policy Controller to create and administer a managed profile on an emp…
72 restrictions to other apps running on the managed profile.
77 only profile on the device is the managed profile, under the enterprise's
114 user profile is called a <em>managed profile</em>, or a <em>work profile</em>
116 managed profile for work, the profile's settings are under the control of the
124 <p>To create a managed profile on a device that already has a personal profile,
125 first check that the device can support a managed profile, by seeing if the
133 // This device does not support native managed profiles!
137 <p>If the device supports managed profiles, create one by sending an intent with
174 <li>Creates a managed profile.
[all …]
|
| D | app-restrictions.jd | 31 a managed profile.</p>
63 provider. If your app is running on an enterprise device's managed
|
| /frameworks/base/core/java/android/app/trust/ |
| D | TrustManager.java | 122 public void onTrustManagedChanged(boolean managed, int userId) { in registerTrustListener()
123 mHandler.obtainMessage(MSG_TRUST_MANAGED_CHANGED, (managed ? 1 : 0), userId, in registerTrustListener()
|
| D | ITrustListener.aidl | 26 void onTrustManagedChanged(boolean managed, int userId); in onTrustManagedChanged() argument
|
| /frameworks/base/docs/html/google/play/billing/ |
| D | api.jd | 14 <li><a href="#managed">Managed In-app Products</a><li>
45 …admin.html">Administering In-app Billing</a>. The Version 3 API supports managed in-app products a…
46 <h3 id="managed">Managed In-app Products</h3>
47 …hat have their ownership information tracked and managed by Google Play. When a user purchases a m…
48 …managed items within your application. You would typically implement consumption for items that ca…
91 <p>In Version 3, all in-app products are managed. This means that the user's
|
| D | billing_overview.jd | 77 <li>All purchases are “managed” (that is, Google Play keeps track of the user's
108 — <em>managed in-app products</em> and <em>subscriptions</em>. Google Play
173 treated as managed products if you make a purchase request for these items using
|
| D | versions.jd | 41 <li>Purchasing and querying managed in-app items requires Google Play client
|
| /frameworks/base/packages/SystemUI/src/com/android/systemui/qs/ |
| D | QSFooter.java | 137 boolean managed = mSecurityController.hasProfileOwner(); in createDialog()
141 mDialog.setMessage(getMessage(deviceOwner, profileOwner, primaryVpn, profileVpn, managed)); in createDialog()
|
| /frameworks/base/docs/html-intl/intl/zh-cn/google/play/billing/ |
| D | api.jd | 13 <li><a href="#managed">托管的应用内商品</a><li>
43 <h3 id="managed">托管的应用内商品</h3>
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-5.0-changes.jd | 545 Device administrators can add a <em>managed profile</em> to a device. This
547 over the managed profile while leaving the user's personal profile, and its
555 managed profile. In this case, if an app fires an intent from the managed
557 suitable handler for the intent on the managed profile,
559 device administrator can restrict apps on the managed profile from accessing
560 the system's camera application. If your app is running on the managed profile
564 MediaStore.ACTION_IMAGE_CAPTURE}, and there is no app on the managed profile
586 fired by an app on the managed profile, the camera needs to be able to write the
587 image to a location where the managed profile's apps can read it.</p>
|
| D | android-5.0.jd | 738 initiate a managed provisioning process to add a copresent but separate
739 <em>managed profile</em> to a device, if the user has an existing personal account.
740 Apps that are associated with managed profiles appear alongside
741 non-managed apps in the user’s Launcher, recents screen, and notifications.</p>
743 <p>To start the managed provisioning process, send
749 enable this managed profile.</p>
751 <p>By default, only a small subset of apps are enabled in the managed profile.
752 You can install additional apps in the managed profile by calling
757 for the current user and any associated managed profiles. Your Launcher can make
758 the managed apps visually prominent by appending a work badge to the icon
[all …]
|
| /frameworks/base/docs/html/samples/new/ |
| D | index.jd | 345 <p>This sample demonstrates how to create a managed profile. You can also:</p>
349 managed profile.</li>
350 <li>Wipe all the data associated with the managed profile.</li>
353 <p class="note"><strong>Note:</strong> There can be only one managed profile on
|
| /frameworks/base/docs/html/training/basics/data-storage/ |
| D | index.jd | 39 <li>Using databases managed by SQLite</li>
|
| D | shared-preferences.jd | 34 managed by the framework and can be private or shared.</p>
|
| /frameworks/base/docs/html/guide/topics/ui/controls/ |
| D | checkbox.jd | 25 a set of checkbox options allows the user to select multiple items, each checkbox is managed
|
| /frameworks/base/docs/html/training/efficient-downloads/ |
| D | redundant_redundant.jd | 61 <p>Alternatively, you can use the managed / secure application cache. Note that this internal cache…
|
| /frameworks/base/docs/html/training/articles/ |
| D | perf-jni.jd | 32 <p>JNI is the Java Native Interface. It defines a way for managed code
72 started from managed code (using <code>Thread.start</code>),
384 set an exception pointer in the current thread. Upon returning to managed
699 buffer of raw data from both managed and native code. Common examples
704 access from managed code. On the native side, however, you're
708 raw data in the managed heap, but in others it will allocate a buffer
714 byte buffers, the storage is not allocated on the managed heap, and can
717 byte buffer access is implemented, accessing the data from managed code
|
| /frameworks/base/core/java/android/app/ |
| D | IApplicationThread.java | 121 void dumpHeap(boolean managed, String path, ParcelFileDescriptor fd) in dumpHeap() argument
|
| D | ApplicationThreadNative.java | 481 boolean managed = data.readInt() != 0; in onTransact()
485 dumpHeap(managed, path, fd); in onTransact()
1205 public void dumpHeap(boolean managed, String path, in dumpHeap() argument
1209 data.writeInt(managed ? 1 : 0); in dumpHeap()
|
| /frameworks/base/docs/html/google/play/billing/v2/ |
| D | api.jd | 67 the "managed per user account" product type, Google Play permanently stores the
70 purchased. If a user attempts to purchase a managed item that has already been
74 <p>The "managed" product type is useful if you are selling
100 <p>Subscriptions can only be sold using the "managed per user account" purchase
226 href="{@docRoot}google/play/billing/billing_admin.html#billing-purchase-type">managed
463 set to "managed per user account."</p>
|
| /frameworks/base/docs/html/guide/components/ |
| D | fragments.jd | 62 fragment transaction, you can also add it to a back stack that's managed by the
90 that's managed by the activity.</p>
177 incorporate a fragment dialog into the back stack of fragments managed by the activity,
181 <dd>Displays a list of items that are managed by an adapter (such as a {@link
404 android.app.FragmentTransaction}. You can also save each transaction to a back stack managed by the
426 to a back stack of fragment transactions. This back stack is managed by the activity and allows
683 that's managed by the system when it's stopped, by default (so that the user can navigate back
686 However, a fragment is placed into a back stack managed by the host activity only when you
|
| /frameworks/base/docs/html/google/play/licensing/ |
| D | licensing-reference.jd | 110 managed by an Obfuscator.</td>
284 {@code RETRY}. <p>The value is managed by the server, however a typical value would be 5
292 <p>The value is managed by the server, however a typical value would be "10" or
|
| /frameworks/base/docs/html/preview/ |
| D | api-overview.jd | 508 managed apps access to certificates without user interaction.</li>
544 of the managed primary user.</li>
557 for a managed profile, a personal profile, or both. For a Device Owner, the notifications are
560 an app from the managed profile has an activity in the foreground. Furthermore, if the device is
561 unlocked directly to the activity of an app in the managed profile, a toast is displayed notifying
|
| /frameworks/base/docs/html/training/improving-layouts/ |
| D | reusing-layouts.jd | 46 extracted, managed separately, then included in each layout. So while
|