Stay organized with collections Save and categorize content based on your preferences.
Starting from Google Mobile Ads (GMA) SDK version 21.0.0, you can enable optimized SDK initialization and ad loading to improve the overall responsiveness of ads and help prevent "Application Not Responding" (ANR) errors on your app. This guide outlines the changes you need to make to enable these optimizations.
RequirementsThere are two optimization flags available: OPTIMIZE_INITIALIZATION and OPTIMIZE_AD_LOADING. Once they're turned on, the initialization and ad loading tasks that require extended processing time are offloaded to background threads.
Follow the instructions below to add the corresponding <meta-data> tags in your app's AndroidManifest.xml file and turn on the flags. Note that you can turn on one or both options in the same app.
OPTIMIZE_INITIALIZATION and OPTIMIZE_AD_LOADING flags are set to true by default. In versions prior to 24.0.0, these flags are set to false by default.
The best way to optimize initialization is to call MobileAds.initialize() on a background thread, as described in the Get Started guide. If you are already doing so, you don't need to enable this flag.
If you must call the method on the main thread, enabling the flag below will move some of the initialization tasks to the background thread.
<manifest>
...
<application>
...
<meta-data
android:name="com.google.android.gms.ads.flag.OPTIMIZE_INITIALIZATION"
android:value="true"/>
</application>
</manifest>
The flag below optimizes ad load calls for all ad formats:
<manifest>
...
<application>
...
<meta-data
android:name="com.google.android.gms.ads.flag.OPTIMIZE_AD_LOADING"
android:value="true"/>
</application>
</manifest>
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-10 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-10 UTC."],[[["Starting with Google Mobile Ads SDK version 21.0.0, new optimization features enhance ad responsiveness and reduce \"Application Not Responding\" errors."],["Two optimization flags, `OPTIMIZE_INITIALIZATION` and `OPTIMIZE_AD_LOADING`, offload time-consuming tasks to background threads."],["You can enable either or both flags in your app's `AndroidManifest.xml` to optimize SDK initialization and ad loading."],["The `OPTIMIZE_INITIALIZATION` flag is most effective when `MobileAds.initialize()` is called on the main thread; otherwise, background initialization is already recommended."],["The `OPTIMIZE_AD_LOADING` flag enhances ad loading for all ad formats by shifting processing to background threads."]]],["To optimize Google Mobile Ads SDK, enable `OPTIMIZE_INITIALIZATION` and/or `OPTIMIZE_AD_LOADING` flags in your `AndroidManifest.xml`. These flags move time-consuming initialization and ad loading tasks to background threads, improving app responsiveness and preventing ANR errors. Add `\u003cmeta-data\u003e` tags within the `\u003capplication\u003e` tag, setting the desired flag's value to \"true.\" SDK version 21.0.0 or higher is required, with both flags being false by default.\n"]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3