If you can send us a project that reproduces the issue we'll take a look. Also higher resolution images of the view hierarchies above would be helpful.

Please send to

. You'll want to use a file sharing service for any code, here's one option: http://me2u.qualcomm.com

- Kim

Kim,

Thank you for all of your help and input so far. I really appreciate it. I'm not sure the issue we're having and the other problems described are the same, as they all deal with switching to a different activity, while the issue we're having with the Razr is on first load, without any activity switching. I suppose it could be a different manifestation of the same issue, and/or due to a race condition. But either way, limiting the set of devices to 3.0+ isn't really an option (besides, it works on every other sub 3.0 device we've tried).

If there is any guidance you might be able to provide on how to troubleshoot this further and hone in on the issue, we'd greatly appreciate it.

Thanks!

See this thread, especially the last few posts about inserting a delay in onResume: http://ar.qualcomm.at/node/2001561

Unfortunately the Z-ordering of multiple surfaces is an Android problem. They've resolved it as of Honeycomb, so if it's really an issue you can limit the set of devices.

Our sample apps shouldn't experience this issue on the first run (although they may on consecutive runs). If it is a race condition then it might have everything to do with the timing of resource loading, etc. You may want to try inserting that delay, or loading your resources after the views are in place.

Thanks,

- Kim

Any further ideas on this, ksiva?

I tried moving the GLView up to the same parent as the CameraSurface, but then the GLView is below the CameraSurface (preventing any rendered models from showing), and any other Views I add over top lose their layout and become full-screen.

Thanks,
Daniel

Good idea, I gave it a shot, but it doesn't appear to make a difference. The CameraSurface is still overshadowing everything.

Out of curiosity, after responding to this post (http://ar.qualcomm.at/node/2002004) I'm wondering if this is an issue with running using the debugger. Could you try the same thing using "Run" rather than "Debug" in Eclipse?

Thanks,

- Kim

The issue definitely happens on first run. I'm honestly not sure about consecutive runs, I don't have that phone on me at the moment to test with, I'd be happy to return with more data once I do, if it is helpful.

The phone is currently running Android 2.3.6, but was running 2.3.5 and had the same issue (we upgraded, seeing if that made a difference). Thank you for pointing out the release notes...If I'm reading it correctly, that issue appears to happen only on subsequent runs, when other applications have been launched over top of Vuforia. Our issue shows up immediately, the first run, without any other apps being launched. They could be related, though.

This may be an issue that is mentioned in the release notes:

Quote:

On certain devices, the video preview rendering and the rendering layer order may be mismatched after another application overlays the QCAR rendering window. Apps may optionally destroy the Android activity with a call to Activity.finish() in your main Activity‟s onPause() and may reinitialize it onResume(). This no longer happens on devices running Honeycomb or above.

Are you seeing the issue on the first run of the app, or only on consecutive runs?

Also what Android OS version is the device running? It sounds like the Razr should be getting an ICS update soon, if it hasn't already. I'd be curious if the issue is resolved with an update.

Thanks,

- Kim