Log in or register to post comments

Strange behaviour with some devices

July 1, 2011 - 8:02am #8

Hi all,

I designed an app with the Qualcomm SDK. It’s working on several devices (Samsung, LG, HTC) but I’ve got some an issue on all my Motorola devices (Droid, Droid X, 2 Global). On Motorola devices I need some time to restart the app 2 or 3 times.

I put the log in enclosed file.
Any idea will be welcomed! Thanks!

Hidden

Re: Strange behaviour with some devices

July 5, 2011 - 11:29am #7

Hello Hidden,

Can you please describe what is happening on the Motorola devices? Why does it require a restart? After restarting, does the app perform as expected?

Thank you,

-Peter

Re: Strange behaviour with some devices

July 6, 2011 - 1:20am #6

Hi Peter,

Thank you for your answer.

On Motorola devices, the first time it runs, the camera feed is not visible (black screen), the second time we also have the black screen but the camera feed shows up once a marker is put in front of the camera. The third time, it's fine.

When I've got this black screen, if I force the 3D to be displayed (even if there is no marker), I can see the 3D but not the video feed.

Also, sometime (again on Motorola) the camera feed is not updated and only displayed the last frame from a previous run. If the marker is on that frame, the 3D and animation will play, tracking off the static frame.

Any idea?

Re: Strange behaviour with some devices

July 6, 2011 - 6:44pm #5

Hello Hidden,

What version of the QCAR SDK are you using? Are you using Unity 3D with the Unity extension of Eclipse with the QCAR SDK ? Do the sample apps (ImageTargets, Virtual Buttons, etc. ) work on your Motorola Devices?

Thank you,

-Peter

Re: Strange behaviour with some devices

July 7, 2011 - 3:05am #4

Hi Peter,

I'm using the last SDK version without Unity.

The QCAR sample apps work on the devices. The AR is onl part of my app. If I try to run the AR part alone (like QCAR samples), it works directly.

The strange thing is that the problem seems to appear only on Motorola devices...

Re: Strange behaviour with some devices

July 7, 2011 - 8:11am #3

It appears to be to do with the phones orientation.

I noticed that when launching the app holding the phone landscape it works everytime. I have locked the screen to portrait for my main menu, and then when the user presses the launch button set the orientation to landscape.

The behavior I'm getting at the moment is:

Holding the phone landscape the app works fine and as expected.

Holding the phone portrait the app starts (which is better than before when it was usually just black) but then after a few seconds the camera freezes, though any 3D that was on screen continues to animate.

This only seems to happen on the Motorolas :confused:

Re: Strange behaviour with some devices

July 7, 2011 - 10:01am #2

Hello Hidden,

Can you post the code you are using to start the AR portion of your app?

You may want to try doing a full CameraDevice Init() just before starting your ar portion and a full CameraDevice deinit() when switching out of your AR portion of your app. Some devices are more sensitive to when the camera is Inited than others.

Thank you,

-Peter

Re: Strange behaviour with some devices

July 13, 2011 - 1:31am #1

Hi Peter,

Sorry for the delay. I found a temporary solution:

In the main java class which initialise QCAR, I force the phone’s orientation to Landscape with the method:
this.setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);

I can do it because all the Motorola phones I want to support are at least under android 2.2.

However, it's not a good solution for someone who would like to use it on android 2.1 (see comments for the method initApplication() in ImageTargets.java).

Hope it could help someone else.

Many thanks for your help Peter!

Hidden

Log in or register to post comments