Log in or register to post comments

Camera image squashed (vertically) on Android 3.2

November 8, 2011 - 7:24am #1

Hi!

I'm using QCar frame markers in my android application and everything was working smothely on Android 3.1. Meanwhile I've updated my Motorola Xoom to Android 3.2. and the app, which was installed and had run previously to the update, still worked OK. The problem came after I reinstalled the app. Now, in some situations, like having a surface view on top of the Qcar glview, the camera image gets distorted vertically but keeping the full screen size.

I know that the QCar framework, on the app’s first run, gets some kind of device optimization parameters which are stored and the app won’t need to be connected to the Internet in subsequent runs (even after device reboot). So my guess is that these parameters change from one Android version to another Android version and that the 3.2 version parameters are causing this problem, as the app worked fine on the 3.2 Android while it still had the old parameters.

My question is: Is there some way of choosing or manipulate these parameters to a specific version? This app is very specific and it will only run on Motorola Xoom, so there’s no problem to keep these parameters static.
It would be great if someone could give me some kind of help on this as I’m really in a dead end and don’t know what else to do.

Thanks!

Re: Camera image squashed (vertically) on Android 3.2

November 10, 2011 - 8:00pm #6

Can you possibly send a copy of the app for us to test on our Xoom? You can send to

. If sending an APK you'll want to use a file sharing service, feel free to use ours (create an account with any email address): http://me2u.qualcomm.com

Thanks,

- Kim

Re: Camera image squashed (vertically) on Android 3.2

November 10, 2011 - 2:12am #5

The model and rest of version info:

Model Number: MZ604
Android Version: 3.2
Firmware configuration version: GAS_EMEA_UCAHUBLWFRTCOREEU_PO13
Kernel version: 2.6.36.3-00042-g3c1a41e / a7301c@il93lnxdroid47 #1
Build number: H.6.6-23

I was already aware of the surface overlapping issues in Android, though I did manage to do what I wanted, and it worked fine. Anyway, this is happening even if the surface view is whithin another activity.

Thanks again.

Re: Camera image squashed (vertically) on Android 3.2

November 9, 2011 - 4:41pm #4

Could you tell the model number for your Xoom? You should be able to find this under the Settings > About Phone menu.

Be careful about using multiple surface views in a single activity, Android does not guarantee the Z ordering.

http://groups.google.com/group/android-developers/browse_frm/thread/8396e87bf08399a4/2439894fa2d820c7?lnk=gst&q=multiple+surface+views#2439894fa2d820c7

- Kim

Re: Camera image squashed (vertically) on Android 3.2

November 9, 2011 - 2:33am #3

Hi Kim,

I have already fully uninstalled and reinstalled the app. Effectively it was right after my first complete reinstall of the app that the problem started.

Attached are two screenshots of the app, one working fine and the other with the distortion. As I said, the distortion starts after some other surface view (like a video player) is put on top - even if it is within another activity.

Also, when working correctly you can see the object on the marker (in this case it is a menu) and after the distortion the object is not shown anymore, though I know the marker is being correctly detected because if I press on where the menu should be, it still reacts. It seems like the camera capture resolution changes and also that the Z order gets changed...

It would be great if you could help.

Thanks

Re: Camera image squashed (vertically) on Android 3.2

November 8, 2011 - 6:47pm #2

There is no way to grab a specific version of the device parameters, and it shouldn't be necessary... This sounds like a bug, or a bad set of parameters for that device. We're looking into the issue, could you provide a screenshot of the error in the meanwhile?

Just to make sure, have you tried completely uninstalling and reinstalling the app since you've seen the issue?

- Kim

Log in or register to post comments