AdMob initialize delay and error.

[Gian Marco]

I'm using Admob in my app but I got this problem:

When I initialize AdMob even without ads I got 1,5 seconds of delay (app freeze).

This is where the delay come from:

 MobileAds.initialize(getApplicationContext(), "ca-app-pub-123");

Also when I initialize I got this error in my Log:

W/ResourcesManager: Asset path '/system/framework/com.android.media.remotedisplay.jar' does not exist or contains no resources.

W/ResourcesManager: Asset path '/system/framework/com.android.location.provider.jar' does not exist or contains no resources.

W/art: Long monitor contention event with owner method=java.lang.Class dalvik.system.DexFile.defineClassNative(java.lang.String, java.lang.ClassLoader, long) from DexFile.java:4294967294 waiters=0 for 388ms

W/art: Long monitor contention event with owner method=java.lang.Class dalvik.system.DexFile.defineClassNative(java.lang.String, java.lang.ClassLoader, long) from DexFile.java:4294967294 waiters=1 for 389ms

I still can run ads correctly but this delay and errors are really annoying, someone know how can I fix that? 

The delay and error go away if I take off that line of code.....

[Ivan Bautista (Mobile Ads SDK Team)]

Hi Gian,

I tried running an app with just the initialization of Mobile Ads SDK (MobileAds.initialize) without displaying or requesting any ads as you've stated and didn't encounter any of the warning logs you've specified nor the app freeze. Can you try with our sample app and see if you can replicate the app freeze and the warning logs? 

If you're not able to replicate the issue with our sample app, can you provide us a miniature sample project of your implementation where you can replicate the issue?

Best Regards,

Ivan Bautista

Mobile Ads SDK Team