Hi, just for confirmation on the last point, if you run the ImageTargets sample, do you see the same issue ?

Hello,

I'm wondering if anyone found the solution to this problem? I am now experiencing the same problem. My app works fine on my droid DNA, but when testing it with a Sony Tablet S, I get the same problem of the camera reporting (0,0) size. In response to the previous questions:

1) How repeatable is this?
Very. The qcar app will run fine the first time when launched from Eclipse. Then on the second run, the app hangs with this error:

03-30 15:55:03.500: E/AR(12503): VideoBackgroundConfig with screen size of zero received, skipping config step

2) Does it occur when launching from Eclipse? If so, are you hooking up the debugger?
Yes, but I'm not running the debugger right now.

3) Does it occur when resuming from the main application list or from the recent app list?
No, only seems to happen when installing & running a fresh copy from eclipse.

4) Does your app load a lot of content at startup?
I don't think so. It's using 1 multitarget and 3 textures and creates vertices & normals on the fly.

5) Can you reproduce the issue with the sample applications?
Yes. Also note that once i get this error, i can't even load the basic android camera app. it gives me the error "Cannot start Camera. Restart this device."

Hi Kim,

Took me a while but I managed to re-create this error with my app on a Xoom.

And to answer your questions.

1) Not very

2) This an app installed from Eclipse but launched via Android system (app is not signed if that makes a difference.)

3) For me this happened not while resuming but re-launching through onCreate()

4) It does a few server calls but nothing to intensive

5) Have not tried yet.

I'll email you shortly.

Thanks again for the report. A few questions:

1) How repeatable is this?

2) Does it occur when launching from Eclipse? If so, are you hooking up the debugger?

3) Does it occur when resuming from the main application list or from the recent app list?

4) Does your app load a lot of content at startup?

5) Can you reproduce the issue with the sample applications?

So far I'm not able to reproduce the issue with our samples on this device, but they are relatively light weight. If you can send an apk to

I'll try with your app. Please use a file sharing service (e.g. http://me2u.qualcomm.com).

Thanks,

- Kim

I've seen this too actually.

When I use an QCAR app for a while (pausing and resuming) eventually the camera instance gets lost and no others app can use it.

After this situation, I cannot use also my device's camera application .

The log is;

03-31 12:07:52.000: I/IMAGE_TARGETS(6420): Successfully loaded and activated data set.
03-31 12:07:52.000: D/QCAR(6420): LoadTrackerTask::onPostExecute: execution successful
03-31 12:07:52.010: D/dalvikvm(6420): GC_CONCURRENT freed 737K, 12% free 8868K/10055K, paused 1ms+2ms
03-31 12:07:52.030: D/dalvikvm(6420): GC_EXPLICIT freed 23K, 13% free 8844K/10055K, paused 2ms+2ms
03-31 12:07:52.500: I/IMAGE_TARGETS(6420): Java_us_mron_Covie_ImageTargets_startCamera
03-31 12:07:52.500: V/NvOmxCamera(88): int android::HAL_getNumberOfCameras() ++
03-31 12:07:52.500: V/NvOmxCamera(88): int android::HAL_getNumberOfCameras() --
03-31 12:07:52.500: V/NvOmxCamera(88): int android::HAL_getCameraInfo(int, camera_info*) ++
03-31 12:07:52.500: V/NvOmxCamera(88): int android::HAL_getCameraInfo(int, camera_info*) --
03-31 12:07:52.500: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:52.760: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:53.010: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:53.270: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:53.540: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:53.790: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:54.040: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:54.300: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:54.560: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:54.820: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:55.060: W/CameraService(88): CameraService::connect X (pid 6420) rejected (camera 0 is still busy).
03-31 12:07:55.060: I/IMAGE_TARGETS(6420): Java_us_mron_Covie_ImageTargets_setProjectionMatrix
03-31 12:07:55.100: D/libEGL(6420): loaded /system/lib/egl/libEGL_tegra.so
03-31 12:07:55.120: D/libEGL(6420): loaded /system/lib/egl/libGLESv1_CM_tegra.so
03-31 12:07:55.140: D/libEGL(6420): loaded /system/lib/egl/libGLESv2_tegra.so
03-31 12:07:55.140: I/QCAR(6420): Creating OpenGL ES 2.0 context
03-31 12:07:55.150: D/QCAR(6420): GLRenderer::onSurfaceCreated
03-31 12:07:55.150: I/IMAGE_TARGETS(6420): Java_us_mron_Covie_ImageTargetsRenderer_initRendering
03-31 12:07:55.150: D/QCAR(6420): GLRenderer::onSurfaceChanged
03-31 12:07:55.150: I/IMAGE_TARGETS(6420): Java_us_mron_Covie_ImageTargetsRenderer_updateRendering
03-31 12:07:55.150: I/IMAGE_TARGETS(6420): Correcting rendering background size to handle missmatch between screen and video aspect ratios.
03-31 12:07:55.150: I/IMAGE_TARGETS(6420): Configure Video Background : Video (0,0), Screen (1280,752), mSize (0,752)
03-31 12:07:55.180: I/ActivityManager(168): No longer want com.ted.android (pid 6119): hidden #16

It doesn't occur every time. When it occurs I'll do that.

Is the model number "Transformer TF101" (Settings > System > About tablet)? I'm testing on this device now and not seeing any issues. Are you connected to the internet?

Please provide the full log for a run when the camera stays black. If it's too big to attach here you can send to

. Thanks!

- Kim