Lines Matching full:your
48 running your client app. Integrating photos is only a small part of your
57 <p>If an essential function of your application is taking pictures, then restrict
59 that your application depends on having a camera, put a <a
61 <uses-feature>}</a> tag in your manifest file:</p>
71 <p>If your application uses, but does not require a camera in order to function, instead set {@code
73 camera to download your application. It's then your responsibility to check for the availability
76 If a camera is not available, you should then disable your camera features.</p>
84 and some code to handle the image data when focus returns to your activity.</p>
105 your app will crash. So as long as the result is not null, it's safe to use the intent. </p>
111 <p>If the simple feat of taking a photo is not the culmination of your app's
160 <p>However, if you'd like the photos to remain private to your app only, you can instead use the
180 when the user uninstalls your app.</p>
248 FileProvider}. In your app's manifest, add a provider to your application:
284 <code>com.example.package.name</code> with the actual package name of your
291 <p>When you create a photo through an intent, you should know where your image is located, because
293 your photo accessible is to make it accessible from the system's Media Provider.</p>
295 <p class="note"><strong>Note:</strong> If you saved your photo to the directory provided by
297 scanner cannot access the files because they are private to your app.</p>
299 <p>The following example method demonstrates how to invoke the system's media scanner to add your
317 you find your application running out of memory after displaying just a few
