Lines Matching refs:on
29 where company-specific apps and data are running on a user's device, while still
33 reliably on a device with managed profiles. You don't need to do anything
35 practices become especially important on devices with managed profiles. This
43 emails and contacts) are on a device the enterprise does not control. </p>
52 running on the device, no matter which profile the app is running under:</p>
57 app running on profile fires an intent, there is no handler for the intent on
61 <li>The profile administrator can limit which system apps are available on the
63 some common intents on the managed profile.</li>
65 file URI that is valid on one profile is not valid on the other. Any
66 intent fired on one profile might be handled on the other (depending on profile
73 <p>On a device with a managed profile, there are restrictions on whether intents
75 off, it is handled on the same profile where it is fired. If there is no handler
76 for the intent <em>on that profile</em>, the intent is not handled and the app
78 intent on the other profile.</p>
94 because there is a handler on the current profile, or because the intent is
95 allowed to cross to a handler on the other profile. (For more information about
135 absolute path of the file on the device's storage. However, because the
137 that is valid on one profile is not valid on the other. This situation
139 attach a file URI to an intent, and the intent is handled on the other profile,
147 ID with other apps (even on the other profile). The recipient can use the
172 catch problems that would cause your app to fail on a device with
173 managed profiles. In particular, testing on a managed-profile device is a good
176 on.</p>
180 which you can use to set up a managed profile on an Android device that runs
187 <li>Specify which default apps are available on the managed
196 managed profile, the app is installed on both the managed and the unmanaged
203 the camera app), try disabling that default app on the managed profile, and
210 when there is a suitable handler on the app's profile, and when there is not.
217 there is a suitable handler on the other profile (the profile the app is not
218 running on)</li>
221 is a suitable handler on the app's profile</li>
224 is no suitable handler for map intents on the device's profile</li>
230 both when it is handled on the app's profile, and when it crosses between
235 <h3 id="testing_tips">Testing on managed profiles: Tips and tricks</h3>
237 <p>There are a few tricks that you may find helpful in testing on a
242 <li>As noted, when you side-load an app on a managed profile device, it is
243 installed on both profiles. If you wish, you can delete the app from one profile
244 and leave it on the other.</li>
254 <li>To find the active users on a device, use the adb package manager's
262 <p>For example, to find the users on a device, you would run this command:</p>