| /frameworks/base/docs/html/training/improving-layouts/ |
| D | index.jd | 60 This lesson shows how you can improve your layout's initialization performance by loading
|
| D | optimizing-layout.jd | 38 layouts. However, each widget and layout you add to your application requires initialization,
|
| /frameworks/base/docs/html/training/custom-views/ |
| D | optimizing-view.jd | 39 would cause a stutter. Allocate objects during initialization, or between animations. Never make an
|
| D | custom-drawing.jd | 108 objects require expensive initialization. Creating drawing objects within your {@link
|
| /frameworks/base/docs/html/tools/testing/ |
| D | contentprovider_testing.jd | 120 feature of this class is its initialization, which creates the isolated test environment.
123 The initialization is done in the constructor for {@link android.test.ProviderTestCase2}, which
|
| D | service_testing.jd | 85 {@link android.test.ServiceTestCase} defers initialization of the test environment until you
|
| /frameworks/base/docs/html/training/displaying-bitmaps/ |
| D | cache-bitmap.jd | 218 mDiskCacheStarting = false; // Finished initialization
294 the cache is accessed before initialization. To address this, in the above implementation, a lock
|
| /frameworks/base/docs/html/tools/studio/ |
| D | studio-config.jd | 91 repositories, Gradle initialization and synchronization, and Android Studio version updates.</p>
|
| /frameworks/base/docs/html/training/multiple-apks/ |
| D | texture.jd | 155 your application initialization in one place, so that each individual APK doesn’t have to
157 initialization procedures that don’t change much from APK to APK.</p>
|
| D | api.jd | 195 your application initialization in one place, so that each individual APK doesn’t have to
197 initialization procedures that don’t change much from APK to APK.</p>
|
| D | screensize.jd | 175 your application initialization in one place, so that each individual APK doesn’t have to
177 initialization procedures that don’t change much from APK to APK.</p>
|
| D | multiple.jd | 224 your application initialization in one place, so that each individual APK doesn’t have to
226 initialization procedures that don’t change much from APK to APK.</p>
|
| /frameworks/base/docs/html/training/id-auth/ |
| D | custom_auth.jd | 133 activity needs any special initialization parameters, you can attach them to the
|
| /frameworks/base/docs/html/ndk/samples/ |
| D | sample_teapot.jd | 350 initialization. They do this outside of the activity lifecycle, since the
|
| /frameworks/base/docs/html/ndk/guides/ |
| D | ndk-gdb.jd | 184 <td><p>This option tells {@code ndk-gdb} to run the GDB initialization commands found in
|
| /frameworks/base/docs/html/training/activity-testing/ |
| D | activity-basic-testing.jd | 76 the code for test initialization and clean up separate from the tests methods.
|
| /frameworks/base/docs/html/training/testing/unit-testing/ |
| D | local-unit-tests.jd | 183 runner to validate that your usage of the framework is correct and simplifies the initialization of
|
| /frameworks/base/docs/html/training/contacts-provider/ |
| D | retrieve-details.jd | 199 * and the Fragment's UI is ready. Put final initialization
|
| D | retrieve-names.jd | 415 retrieval. Do the initialization in
|
| /frameworks/base/docs/html/sdk/installing/ |
| D | migrate.jd | 143 initialization and synchronization, and Android Studio version updates. For more information,
|
| /frameworks/base/services/core/java/com/android/server/content/ |
| D | SyncStorageEngine.java | 408 boolean initialization; field in SyncStorageEngine.SyncHistoryItem
1320 item.initialization = op.isInitialization(); in insertStartSyncEvent()
|
| /frameworks/base/docs/html/training/sync-adapters/ |
| D | running-sync-adapter.jd | 161 * app initialization has already created the account.
|
| /frameworks/base/docs/html/training/wearables/watch-faces/ |
| D | drawing.jd | 32 service implementations described here (such as initialization and device features detection)
|
| /frameworks/base/docs/html/training/articles/ |
| D | smp.jd | 1099 /* initialization complete, publish */
1148 /* initialization complete */
1339 <code>sGoodies = goods</code> might be observed before the initialization of the
1382 71 (“Use lazy initialization judiciously”) in Josh Bloch’s <em>Effective Java,
|
| /frameworks/base/docs/html/guide/topics/providers/ |
| D | content-provider-creating.jd | 559 onCreate()}. Defer initialization tasks until they are actually needed.
637 onCreate()} when it starts up the provider. You should perform only fast-running initialization
|