I've configured a virtual 4.4.2 (arm) Android Device in the AVD (Full Settings below) and need to use my webcam to test the camera.
The camera app starts and crashes instantly (Camera has stopped working).
I get the following log output:
10-28 05:43:41.220 370-548/system_process I/ActivityManager﹕ Start proc com.android.camera for activity com.android.camera/.Camera: pid=1136 uid=10030 gids={50030, 1028, 1015}
10-28 05:43:42.100 1136-1150/com.android.camera V/CameraHolder﹕ open camera 0
10-28 05:43:42.100 60-125/? E/CameraService﹕ CameraService::connect X (pid 1136) rejected (invalid cameraId 0).
10-28 05:43:42.110 1136-1150/com.android.camera W/CameraBase﹕ An error occurred while connecting to camera: 0
10-28 05:43:42.110 1136-1150/com.android.camera E/CameraHolder﹕ fail to connect Camera
java.lang.RuntimeException: Fail to connect to camera service
at android.hardware.Camera.native_setup(Native Method)
at android.hardware.Camera.<init>(Camera.java:351)
at android.hardware.Camera.open(Camera.java:310)
at com.android.camera.CameraHolder.open(CameraHolder.java:131)
at com.android.camera.Util.openCamera(Util.java:267)
at com.android.camera.Camera$4.run(Camera.java:1100)
at java.lang.Thread.run(Thread.java:841)
10-28 05:43:42.120 1136-1150/com.android.camera W/dalvikvm﹕ threadid=11: thread exiting with uncaught exception (group=0xb1ab5ba8)
10-28 05:43:42.120 1136-1150/com.android.camera E/AndroidRuntime﹕ FATAL EXCEPTION: Thread-87
Process: com.android.camera, PID: 1136
java.lang.RuntimeException: openCamera failed
at com.android.camera.Util.openCamera(Util.java:272)
at com.android.camera.Camera$4.run(Camera.java:1100)
at java.lang.Thread.run(Thread.java:841)
Caused by: com.android.camera.CameraHardwareException: java.lang.RuntimeException: Fail to connect to camera service
at com.android.camera.CameraHolder.open(CameraHolder.java:135)
at com.android.camera.Util.openCamera(Util.java:267)
at com.android.camera.Camera$4.run(Camera.java:1100)
at java.lang.Thread.run(Thread.java:841)
Caused by: java.lang.RuntimeException: Fail to connect to camera service
at android.hardware.Camera.native_setup(Native Method)
at android.hardware.Camera.<init>(Camera.java:351)
at android.hardware.Camera.open(Camera.java:310)
at com.android.camera.CameraHolder.open(CameraHolder.java:131)
at com.android.camera.Util.openCamera(Util.java:267)
at com.android.camera.Camera$4.run(Camera.java:1100)
at java.lang.Thread.run(Thread.java:841)
AVD-Settings:
Name: Samsung_Galaxy_S3_API_19
CPU/ABI: ARM (armeabi-v7a)
Path: D:\Users\rowi1de\.android\avd\Samsung_Galaxy_S3_API_19.avd
Target: Android 4.4.2 (API level 19)
Skin: galaxy_s3_blue
SD Card: D:\Users\rowi1de\.android\avd\Samsung_Galaxy_S3_API_19.avd\sdcard.img
Snapshot: no
hw.dPad: no
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: Samsung Galaxy S3
vm.heapSize: 64
skin.dynamic: no
hw.device.manufacturer: User
hw.gps: yes
hw.audioInput: yes
hw.cpu.model: cortex-a8
tag.id: default
hw.camera.back: webcam0
hw.mainKeys: yes
AvdId: Samsung_Galaxy_S3_API_19
hw.camera.front: none
hw.lcd.density: 320
runtime.scalefactor: auto
hw.gsmModem: yes
avd.ini.displayname: Samsung Galaxy S3 API 19
snapshot.present: no
hw.device.hash2: MD5:e6de262aae26d1ce2c8a8b656265afbc
hw.ramSize: 1536
hw.trackBall: no
hw.battery: yes
hw.camera: yes
hw.sdCard: yes
tag.display: Default
runtime.network.latency: none
hw.keyboard: yes
hw.touchScreen: yes
hw.sensors.proximity: yes
disk.dataPartition.size: 200M
hw.sensors.orientation: yes
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes
Any idea how to fix this?
Regards,
Robert
Use Genymotion for testing app it work like AVD and you can use Camera in Genymotion.
You can check on Link About Genymotion and features of Genymotion.
Click here
Related
My application is showing very strange behavior for a tablet device, it crashes as it launches (Lollipop - 5.1.1 Tablet device, without any meaningful logs) though it runs fine on mobile devices even including Lollipop - 5.0 phone device with almost same log report
minSdkVersion 19
targetSdkVersion 28
Log report
E/com.samsung.app: [AccuTab_Magagine]>>> UIMK:1376 [0:0] time : 17:31
E/Watchdog: !#Sync 2614 [07-31 17:31:00.264]
? E/AffinityControl: AffinityControl: registerfunction enter
? E/AffinityControl: AffinityControl: registerfunction enter
E/WindowState: getStack: Window{2bd3ac2f u0 d0 com.project.debug/com.screens.account_login.AccountLoginActivity} couldn't find taskId=500 Callers=com.android.server.wm.WindowState.getDisplayContent:1059 com.android.server.wm.WindowState.isDefaultDisplay:1778 com.android.server.wm.WindowState.getMultiWindowStyleLw:2363 com.android.internal.policy.impl.multiwindow.MultiPhoneWindowManager.shouldEnableLayoutInsetsBySoftInput:1505
E/Zygote: MountEmulatedStorage()
E/Zygote: v2
E/SELinux: [DEBUG] get_category: variable seinfo: default sensitivity: NULL, cateogry: NULL
com.switchsolutions.agricultureapplication.mobilink.debug E/StudioProfiler: Studio Profilers encountered an unexpected error. Consider reporting a bug, including logcat output below.
See also: https://developer.android.com/studio/report-bugs.html#studio-bugs
Failed to capture application
E/WindowState: getStack: Window{2bd3ac2f u0 d0 com.project.debug/com.screens.account_login.AccountLoginActivity} couldn't find taskId=500 Callers=com.android.server.wm.WindowState.getDisplayContent:1059 com.android.server.wm.WindowState.isDefaultDisplay:1778 com.android.server.wm.WindowState.getMultiWindowStyleLw:2363 com.android.internal.policy.impl.multiwindow.MultiPhoneWindowManager.shouldEnableLayoutInsetsBySoftInput:1505
E/android.os.Debug: ro.product_ship = true
E/android.os.Debug: ro.debug_level = 0x4f4c
I created an AVD with the properties below to emulate a customer's device. Each time I start it up, it gives the "Unfortunately, System UI stopped" dialog and, when dismissed, the "Unfortunately, Launcher stopped." dialog.
Tweaking the parameters (at least, those which don't alter the essential characteristics of the device) using advice from:
Android emulator error: "System UI has stopped"
Unfortunately System UI has stopped
Android 4.0 emulator always has a crashing Launcher?
https://daviddesmet.wordpress.com/2013/07/26/android-avd-unfortunately-system-ui-has-stopped/
results in the same outcome.
Variations tried
skin 320x320, 320x321
Google API / non Google API
heapsize 16, 32, 64, 128
mainkeys yes, no
keyboard yes, no
ncore 1, 2, 4
I'm eventually going to borrow a device but hope to get a head start on things before the project start date so would be extremely grateful to hear of any workarounds other than those already attempted.
config.ini
Name: 3.0_Motorola_MC3200_API_16
CPU/ABI: Google APIs Intel Atom (x86)
Path: C:\Users\me\.android\avd\3.0_Motorola_MC3200_API_16.avd
Target: google_apis [Google APIs] (API level 16)
Skin: 320x320
SD Card: C:\Users\me\.android\avd\3.0_Motorola_MC3200_API_16.avd\sdcard.img
hw.dPad: no
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: 3.0" Motorola MC3200
vm.heapSize: 128
skin.dynamic: yes
hw.device.manufacturer: User
hw.gps: no
hw.initialOrientation: Portrait
skin.path.backup: _no_skin
image.androidVersion.api: 16
hw.audioInput: yes
image.sysdir.1: system-images\android-16\google_apis\x86\
hw.keyboard.lid: yes
tag.id: google_apis
showDeviceFrame: no
hw.camera.back: emulated
hw.mainKeys: yes
AvdId: 3.0_Motorola_MC3200_API_16
hw.camera.front: emulated
hw.lcd.density: 160
avd.ini.displayname: 3.0 Motorola MC3200 API 16
hw.gpu.mode: auto
hw.device.hash2: MD5:799ea57969b556677321dbf45a563939
hw.ramSize: 1024
hw.trackBall: no
hw.battery: yes
hw.cpu.ncore: 4
hw.sdCard: yes
tag.display: Google APIs
runtime.network.latency: none
hw.keyboard: yes
hw.sensors.proximity: no
disk.dataPartition.size: 800M
hw.sensors.orientation: no
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes
Logcat extract: System UI stopped
01-23 12:31:05.364 1401-1453/system_process D/Tethering: MasterInitialState.processMessage what=3
01-23 12:31:11.584 1401-1414/system_process W/ActivityManager: Activity idle timeout for ActivityRecord{aedb9d20
com.android.launcher/com.android.launcher2.Launcher}
01-23 12:31:11.724 1401-1414/system_process W/ActivityManager: Launch timeout has expired, giving up wake lock!
01-23 12:31:12.234 1401-1414/system_process W/ActivityManager: Activity idle timeout for ActivityRecord{aedbcc68
com.android.launcher/com.android.launcher2.Launcher}
01-23 12:31:21.514 1401-1415/system_process W/ActivityManager: Timeout executing service: ServiceRecord{aedd3bc8 com.android.systemui/.SystemUIService}
01-23 12:31:21.514 1401-1415/system_process I/ActivityManager: Crashing app skipping ANR: ProcessRecord{aedd43e8 1462:com.android.systemui/u0a35}
Executing service com.android.systemui/.SystemUIService
01-23 12:31:21.584 1401-1414/system_process W/ActivityManager: Activity destroy timeout for ActivityRecord{aedb9d20
com.android.launcher/com.android.launcher2.Launcher}
01-23 12:31:31.704 1158-1584/? I/SurfaceFlinger: Boot is finished (31860 ms)
01-23 12:31:31.704 1401-1434/system_process W/WindowManager: ***** BOOT TIMEOUT: forcing display enabled
01-23 12:31:41.574 1401-1489/system_process E/ThrottleService: problem during onPollAlarm: java.lang.IllegalStateException: problem parsing stats:
java.io.FileNotFoundException: /proc/net/xt_qtaguid/iface_stat_all: open failed: ENOENT (No such file or directory)
Logcat extract: Launcher Stopped
01-23 12:29:01.332 1407-1527/system_process I/ActivityManager: Start proc com.android.launcher for activity
com.android.launcher/com.android.launcher2.Launcher: pid=1793 uid=10019 gids={1028}
01-23 12:29:01.342 1793-1793/com.android.launcher E/Trace: error opening trace file: Permission denied (13)
01-23 12:29:01.352 1793-1793/com.android.launcher I/ActivityThread: Pub com.android.launcher2.settings: com.android.launcher2.LauncherProvider
01-23 12:29:01.372 1793-1793/com.android.launcher W/ResourceType: Failure getting entry for 0x7f03000d (t=2 e=13) in package 0 (error -75)
01-23 12:29:01.372 1793-1793/com.android.launcher D/AndroidRuntime: Shutting down VM
01-23 12:29:01.372 1793-1793/com.android.launcher W/dalvikvm: threadid=1: thread exiting with uncaught exception (group=0xae6de228)
01-23 12:29:01.372 1793-1793/com.android.launcher E/AndroidRuntime: FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to start activity ComponentInfo
{com.android.launcher/com.android.launcher2.Launcher}: android.content.res.Resources$NotFoundException: Resource ID #0x7f03000d
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2059)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2084)
at android.app.ActivityThread.access$600(ActivityThread.java:130)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1195)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4745)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run
(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f03000d
at android.content.res.Resources.getValue(Resources.java:1013)
at android.content.res.Resources.loadXmlResourceParser(Resources.java:2103)
at android.content.res.Resources.getLayout(Resources.java:852)
at android.view.LayoutInflater.inflate(LayoutInflater.java:394)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.setContentView
(PhoneWindow.java:256)
at android.app.Activity.setContentView(Activity.java:1867)
at com.android.launcher2.Launcher.onCreate(Launcher.java:361)
at android.app.Activity.performCreate(Activity.java:5008)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2023)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2084)
at android.app.ActivityThread.access$600(ActivityThread.java:130)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1195)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4745)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run
(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
01-23 12:29:01.392 1793-1795/com.android.launcher D/dalvikvm: GC_CONCURRENT freed 232K, 6% free 6147K/6535K, paused 11ms+0ms, total 14ms
01-23 12:29:01.392 1407-1590/system_process W/ActivityManager: Force finishing activity com.android.launcher/com.android.launcher2.Launcher
Environment
Android Studio 2.2.3
Windows 7 x64
Updates
I have removed and reinstalled SDK and Android Studio.
I am able to replicate this on 2 development machines (so far) so would be useful to discover if anyone else experiences this behaviour for this config.
Its on an HTC Aria, running 2.2 (API 8)
https://en.wikipedia.org/wiki/HTC_Aria
The aria is an armv6 device that supports opengles 2
If you open up the latest Android Studio (im working on windows 7), then import the HelloGL2 sample, then simply try to run it on the above device, it will fail as soon as it tries to make a call into the native library.
Here is the log:
01-06 11:14:08.467 12771-12813/com.android.gl2jni D/dalvikvm: Trying to load lib /data/data/com.android.gl2jni/lib/libgl2jni.so 0x44c165d0
01-06 11:14:08.467 12771-12813/com.android.gl2jni I/dalvikvm: Unable to dlopen(/data/data/com.android.gl2jni/lib/libgl2jni.so): Cannot load library: link_image[1995]: failed to link libgl2jni.so
01-06 11:14:08.477 12771-12813/com.android.gl2jni W/dalvikvm: Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom/android/gl2jni/GL2JNILib;.<clinit>
01-06 11:14:08.497 12771-12813/com.android.gl2jni W/dalvikvm: threadid=8: thread exiting with uncaught exception (group=0x40028a00)
01-06 11:14:08.517 95-121/? I/ActivityManager: Displayed activity com.android.gl2jni/.GL2JNIActivity: 9823 ms (total 2027818 ms)
01-06 11:14:08.567 12771-12813/com.android.gl2jni E/AndroidRuntime: FATAL EXCEPTION: GLThread 9
java.lang.ExceptionInInitializerError
at com.android.gl2jni.GL2JNIView$Renderer.onSurfaceChanged(GL2JNIView.java:332)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1327)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1118)
Caused by: java.lang.UnsatisfiedLinkError: Library gl2jni not found
at java.lang.Runtime.loadLibrary(Runtime.java:461)
at java.lang.System.loadLibrary(System.java:557)
at com.android.gl2jni.GL2JNILib.<clinit>(GL2JNILib.java:24)
at com.android.gl2jni.GL2JNIView$Renderer.onSurfaceChanged(GL2JNIView.java:332)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1327)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1118)
01-06 11:14:08.607 95-164/? W/ActivityManager: Force finishing activity com.android.gl2jni/.GL2JNIActivity
This sample works on the 3 other devices i've tried (Galaxy s5, Galaxy J1, Nexus s)
The line: 'Unable to dlopen(/data/data/com.android.gl2jni/lib/libgl2jni.so): Cannot load library: link_image[1995]: failed to link libgl2jni.so' is probably key. I tried loading the library explicitly using system.loadlibrary, but the same problem happens on that call.
I think it might be something to do with the processor being armv6?
The sample is configured to do 'armeabi' though.
Friends
I am facing this issue since so long but i am able to get any kind of solution to get working camera in emulator. I have gone through all the answer of the SO but none helped me uptill now.
If i create any emulator with any api but in none of my emulator camera application does not work. So i am not able to test any of the application which contains camera functionality. I guess may be its happening because of the hardware configuration of my system. But i am not sure about it.
I do not know why this issue occurs. Please help me to solve and find out the reason for the issue.
Here is the error which i get whenever i starts camera in emulator.
12-21 00:04:58.100: E/CameraService(55): CameraService::connect X (pid 2604) rejected (invalid cameraId 0).
12-21 00:04:58.110: W/CameraBase(2604): An error occurred while connecting to camera: 0
12-21 00:04:58.110: E/CameraHolder(2604): fail to connect Camera
12-21 00:04:58.110: E/CameraHolder(2604): java.lang.RuntimeException: Fail to connect to camera service
12-21 00:04:58.110: E/CameraHolder(2604): at android.hardware.Camera.native_setup(Native Method)
12-21 00:04:58.110: E/CameraHolder(2604): at android.hardware.Camera.<init>(Camera.java:350)
12-21 00:04:58.110: E/CameraHolder(2604): at android.hardware.Camera.open(Camera.java:309)
12-21 00:04:58.110: E/CameraHolder(2604): at com.android.camera.CameraHolder.open(CameraHolder.java:131)
12-21 00:04:58.110: E/CameraHolder(2604): at com.android.camera.Util.openCamera(Util.java:267)
12-21 00:04:58.110: E/CameraHolder(2604): at com.android.camera.Camera$4.run(Camera.java:1100)
12-21 00:04:58.110: E/CameraHolder(2604): at java.lang.Thread.run(Thread.java:841)
12-21 00:04:58.110: W/dalvikvm(2604): threadid=11: thread exiting with uncaught exception (group=0xb4a29b90)
12-21 00:04:58.120: E/AndroidRuntime(2604): FATAL EXCEPTION: Thread-117
12-21 00:04:58.120: E/AndroidRuntime(2604): Process: com.android.camera, PID: 2604
12-21 00:04:58.120: E/AndroidRuntime(2604): java.lang.RuntimeException: openCamera failed
12-21 00:04:58.120: E/AndroidRuntime(2604): at com.android.camera.Util.openCamera(Util.java:272)
12-21 00:04:58.120: E/AndroidRuntime(2604): at com.android.camera.Camera$4.run(Camera.java:1100)
12-21 00:04:58.120: E/AndroidRuntime(2604): at java.lang.Thread.run(Thread.java:841)
12-21 00:04:58.120: E/AndroidRuntime(2604): Caused by: com.android.camera.CameraHardwareException: java.lang.RuntimeException: Fail to connect to camera service
12-21 00:04:58.120: E/AndroidRuntime(2604): at com.android.camera.CameraHolder.open(CameraHolder.java:135)
12-21 00:04:58.120: E/AndroidRuntime(2604): at com.android.camera.Util.openCamera(Util.java:267)
12-21 00:04:58.120: E/AndroidRuntime(2604): ... 2 more
12-21 00:04:58.120: E/AndroidRuntime(2604): Caused by: java.lang.RuntimeException: Fail to connect to camera service
12-21 00:04:58.120: E/AndroidRuntime(2604): at android.hardware.Camera.native_setup(Native Method)
12-21 00:04:58.120: E/AndroidRuntime(2604): at android.hardware.Camera.<init>(Camera.java:350)
12-21 00:04:58.120: E/AndroidRuntime(2604): at android.hardware.Camera.open(Camera.java:309)
12-21 00:04:58.120: E/AndroidRuntime(2604): at com.android.camera.CameraHolder.open(CameraHolder.java:131)
12-21 00:04:58.120: E/AndroidRuntime(2604): ... 3 more
Below are the options which i get while i am trying to edit emulator.
Thanks.
I have resolved my issue by changing the emulators "Back Camera" property to Emulated as shown in screenshot.
Open Tools->Android->AVD Manager then click edit for your virtual device.Click Show Advanced Settings on your virtual device configuration window.Then camera settings field is turned on,select Emulated Front and Back.That is it.
There is no declaration about Camera in limitation of Emulator in doc.
You can Enable camera in Emulator.But emulator wont show a realtime camera regardless.
As of Android SDK version 14, the emulator supports webcams to simulate a camera:
General notes - Added webcam support to Android 4.0 or later platforms
to emulate rear-facing cameras when one webcam is present, and to
emulate both rear-facing and front-facing cameras when two webcams are
present. Webcam suport is for Windows and Linux only. Mac support will
come in a later release.
I'm using Android Studio 3.1.1 in ubuntu 16.04 and had the same issue.
So after couple of days googling, finally solved my problem by myself.
The Solution was:
Edit the AVD and set the Emulated Performance/Graphics from Automatic to Software - GLES 1.1.
Changed the SD Card size to 256 MB.
Set only one of camera (e.g. Front) to webcam0 and other one to none or emulated.
Hope this helps others with the same problem.
JUST DO THIS
use emulated in both Front and back and then chage sdcard size
From the android documentation:
Emulator Limitations
No support for camera/video capture
In other words, no, you cannot access or preview the camera in the emulator.
Hi I am trying to run some sample openGl code on an emulator. I am new to Android development. It crashes on the emulator but not my device, a Samsung Galaxy Note phone N7000.
The AVD settings I tried were:
Target: Android 4.1 - API Level 16
CPU/ABI: ARM (armeabi-v7a)
SD Card: 32 MiB
Skin: Built-in : WGA800
Here are the errors on the console:
10-15 13:23:34.287: E/Trace(621): error opening trace file: No such file or directory (2)
10-15 13:23:34.848: D/libEGL(621): Emulator without GPU support detected. Fallback to software renderer.
10-15 13:23:34.878: D/libEGL(621): loaded /system/lib/egl/libGLES_android.so
10-15 13:23:34.947: D/gralloc_goldfish(621): Emulator without GPU emulation detected.
10-15 13:23:34.977: W/dalvikvm(621): threadid=11: thread exiting with uncaught exception (group=0x40a13300)
10-15 13:23:34.977: E/AndroidRuntime(621): FATAL EXCEPTION: GLThread 72
10-15 13:23:34.977: E/AndroidRuntime(621): java.lang.IllegalArgumentException: No configs match configSpec
10-15 13:23:34.977: E/AndroidRuntime(621): at android.opengl.GLSurfaceView$BaseConfigChooser.chooseConfig(GLSurfaceView.java:863)
10-15 13:23:34.977: E/AndroidRuntime(621): at android.opengl.GLSurfaceView$EglHelper.start(GLSurfaceView.java:1024)
10-15 13:23:34.977: E/AndroidRuntime(621): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1401)
10-15 13:23:34.977: E/AndroidRuntime(621): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1240)
10-15 13:23:35.377: I/Choreographer(621): Skipped 67 frames! The application may be doing too much work on its main thread.
10-15 13:23:36.658: I/Choreographer(621): Skipped 72 frames! The application may be doing too much work on its main thread.
Thanks
Bob
10-15 13:23:34.848: D/libEGL(621): Emulator without GPU support detected. Fallback to software renderer.
Just recreate or edit your emulator and be sure that under the hardware list you have
GPU Emulation set to Yes