App crashed nach Einbinden von Werbung (Google Play Services)

Hallo,

meine App crashed nach Einbinden diesen Abschnitts auf einem Galaxy S1. In meinem Emulator funktioniert alles. Die Android Version auf dem Galaxy ist 2.2.1 und auf dem Emulator 4.2.2.

AdView adView = (AdView)this.findViewById(R.id.adView);
    AdRequest adRequest = new AdRequest.Builder().build();
    adView.loadAd(adRequest);

Google Play Services ist richtig eingebunden, ich habe das mehrmals überprüft. Ich kann mir nicht erklären woran der Fehler liegt, aber es muss an der Werbung liegen, denn wenn ich die ganze Werbegeschichte von Google rausnehme, läuft es auf dem Galaxy auch einwandfrei.

Hier ist das Logfile von meinem Emulator:

06-20 18:13:41.860: D/dalvikvm(1067): GC_FOR_ALLOC freed 97K, 5% free 3114K/3276K, paused 22ms, total 22ms
06-20 18:13:42.000: D/dalvikvm(1067): DexOpt: --- BEGIN 'ads-2111028853.jar' (bootstrap=0) ---
06-20 18:13:42.150: D/dalvikvm(1067): DexOpt: --- END 'ads-2111028853.jar' (success) ---
06-20 18:13:42.150: D/dalvikvm(1067): DEX prep '/data/data/de.chakuze.pokemonForWhatsapp/cache/ads-2111028853.jar': unzip in 1ms, rewrite 150ms
06-20 18:13:42.180: I/Ads(1067): Use AdRequest.Builder.addTestDevice("B3EEABB8EE11C2BE770B684D95219ECB" to get test ads on this device.
06-20 18:13:42.190: I/Ads(1067): Starting ad request.
06-20 18:13:42.240: V/WebViewChromium(1067): Binding Chromium to the background looper Looper (main, tid 1) {b2d5ba30}
06-20 18:13:42.250: I/chromium(1067): [INFO:library_loader_hooks.cc(112)] Chromium logging enabled: level = 0, default verbosity = 0
06-20 18:13:42.260: I/BrowserProcessMain(1067): Initializing chromium process, renderers=0
06-20 18:13:42.390: W/chromium(1067): [WARNING:proxy_service.cc(888)] PAC support disabled because there is no system implementation
06-20 18:13:42.420: E/chromium(1067): [ERROR:gl_surface_egl.cc(153)] No suitable EGL configs found.
06-20 18:13:42.420: E/chromium(1067): [ERROR:gl_surface_egl.cc(620)] GLSurfaceEGL::InitializeOneOff failed.
06-20 18:13:42.420: E/chromium(1067): [ERROR:gl_surface_egl.cc(153)] No suitable EGL configs found.
06-20 18:13:42.420: E/chromium(1067): [ERROR:gl_surface_egl.cc(620)] GLSurfaceEGL::InitializeOneOff failed.
06-20 18:13:42.430: E/chromium(1067): [ERROR:gpu_info_collector.cc(86)] gfx::GLSurface::InitializeOneOff() failed
06-20 18:13:42.750: D/dalvikvm(1067): GC_FOR_ALLOC freed 291K, 10% free 3337K/3692K, paused 20ms, total 21ms
06-20 18:13:43.030: D/dalvikvm(1067): GC_FOR_ALLOC freed 30K, 6% free 3705K/3912K, paused 17ms, total 18ms
06-20 18:13:43.300: I/Choreographer(1067): Skipped 112 frames! The application may be doing too much work on its main thread.
06-20 18:13:43.320: D/gralloc_goldfish(1067): Emulator without GPU emulation detected.
06-20 18:13:43.790: E/GooglePlayServicesUtil(1067): The Google Play services resources were not found. Check your project configuration to ensure that the resources are included.
06-20 18:13:44.070: E/GooglePlayServicesUtil(1067): The Google Play services resources were not found. Check your project configuration to ensure that the resources are included.
06-20 18:13:44.120: E/GooglePlayServicesUtil(1067): The Google Play services resources were not found. Check your project configuration to ensure that the resources are included.
06-20 18:13:50.750: D/dalvikvm(1067): GC_FOR_ALLOC freed 134K, 5% free 4067K/4276K, paused 24ms, total 25ms
06-20 18:13:50.780: I/Choreographer(1067): Skipped 60 frames! The application may be doing too much work on its main thread.
06-20 18:13:50.870: I/Choreographer(1067): Skipped 30 frames! The application may be doing too much work on its main thread.
06-20 18:13:50.930: I/Choreographer(1067): Skipped 32 frames! The application may be doing too much work on its main thread.
06-20 18:13:51.180: I/Choreographer(1067): Skipped 30 frames! The application may be doing too much work on its main thread.
06-20 18:13:51.280: I/Choreographer(1067): Skipped 59 frames! The application may be doing too much work on its main thread.
06-20 18:13:51.950: I/Choreographer(1067): Skipped 78 frames! The application may be doing too much work on its main thread.
06-20 18:13:53.180: I/chromium(1067): [INFO:simple_index_file.cc(397)] Simple Cache Index is being restored from disk.
06-20 18:13:54.580: W/View(1067): requestLayout() improperly called by android.widget.TextView{b2dec248 V.ED.... ......ID 25,20-78,37 #7f050051 app:id/txtItem} during layout: running second layout pass
06-20 18:13:54.950: I/Ads(1067): Scheduling ad refresh 60000 milliseconds from now.
06-20 18:13:54.950: I/Ads(1067): Ad finished loading.

Die Fehler von der GooglePlayServiceUtility sind vernachlässigbar (so steht es selbst bei google irgendwo) und das Banner wird ja auch korrekt angezeigt im Emulator.

Hat jemand eine Idee? Wäre wirklich top, wenn jemand weiß, wieso die App crashed.

Grüße

Nein, das hat was mit der Emulator Geschwindigkeit zu tun. Erst wenn etwa 300 Frames oder mehr geskipped werden, gibt es Probleme mit dem Code.

Niemand eine Idee, was das Problem hier sein könnte?