Log in or register to post comments

Supported Device

May 29, 2011 - 12:54am #1

I've tried to run the 1.0's sample on HTC Wildfire(G8). However, the sample doesn't work well. And there is no place to check whether Wildfire is supported for AR SDK. I can only find the information says the 1.0 version SDK supports all devices with Andorid 2.1 and above. So what's the root cause why Wildfire fails to run the samples, while Desire success.

Re: Supported Device

June 5, 2012 - 10:35am #23

Hello shalika,

All Android devices running Android 2.2 or higher and with an ARMv6 with VFP or better are supported.

Thank you,

-Peter

Re: Supported Device

June 4, 2012 - 11:03pm #22

Hi,

This link(to check supporting devices) is not working.

https://ar.qualcomm.at/qdevnet/support_file/download/Android/supported%20devices%20android/Supported_Device_Android.pdf

Thanks.

Re: Supported Device

March 25, 2012 - 6:10pm #21

I believe it should work for 2D use, but not 3D.

- Kim

Re: Supported Device

March 25, 2012 - 11:33am #20

Is HTC Evo 3D supported by sdk?

Re: Supported Device

March 18, 2012 - 6:04pm #19

Yes the Nexus S is supported.

- Kim

Re: Supported Device

March 17, 2012 - 4:03am #18

HI, I would like to ask if nexus s i9023 is supported by the sdk.

Re: Supported Device

December 1, 2011 - 9:55am #17

Hello loonerzoldick,

A chip that supports ARMv6 with a VFP is required to run QCAR. The HTC Wildfire has a 7225 Processor that does not meet these requirements.

Without knowing the exact model of your teammates phone I cannot say for sure but most of the LG Optimus phones have a minimum of a MSM 7227 processor.

Sorry for the inconvenience,

-Peter

Re: Supported Device

November 30, 2011 - 9:58pm #16

well I hope someone can solve this, you see, in LatinAmerica (I'm from Mexico) the name of the HTC Wildfire was changed to Desire A, so the id model is Desire A, when I tried to use a RUU to update my android OS it throw the message "id model error" I asked around and it seems it was due to the name change.

So because of that change in the id model, can that be the reason behind why can't I run any of the apps using QCAR? My teammate tested the examples on his lg optimus (whose proccessor has 600 MHz) and it ran smoothly.

So in short, does the QCAR API checks the id model of the cellphone it is installed to be sure if it's a supported device? If that's the case, can the development team include the name Desire A aka Wildfire?

Re: Supported Device

November 25, 2011 - 8:53am #15
ppreuss wrote:

Hello rbbrown1,

Please try your device again. It should work now as long as you have a network connection at first launch.

Thank you,

-Peter

Peter,

Success! I now have brother teapots hovering over my side by side targets - Copper and Sapphire. :) (One at a time of course.)

Did we push an update? Much thanks.
On to discovering object substitution and scaling limits.

richard

Re: Supported Device

November 22, 2011 - 4:37pm #14

Hello rbbrown1,

Please try your device again. It should work now as long as you have a network connection at first launch.

Thank you,

-Peter

Re: Supported Device

November 22, 2011 - 12:55pm #13

Hi,

I have the Samsung Galaxy Tab 10.1 SCH-I905 with 3.1 on it. I am trying to evaluate your software for a corporate research project and the Image Targets example project always gives the Device not Supported splash when I run on the Tab. I have WIFi on.

Do I need to be patient and wait for a soon to come update or do I need to go find an older development/test platform?

Thanks,

hopeful

Re: Supported Device

November 21, 2011 - 4:36pm #12

You can try but it probably won't work, I don't believe that device supports VFP (Vector Floating Point).

- Kim

Re: Supported Device

November 21, 2011 - 3:43pm #11

if I overclock my Wildfire to 800 MHz, will I be able to run the QCAR apps? or what can I do to test the apps?

Re: Sharp galapagos

June 17, 2011 - 1:45am #10

I have a sharp galapagos 003sH(3D mobile) device with me.I deployed my AR application on this device,it works perfectly fine.But it looks same as how it looks on any other 2d phone.To use the 3d capability of this device what should i do??? Does anyone have idea about this??

Re: Supported Device

June 3, 2011 - 12:11pm #9

On Further investigation, the HTC Wildfire uses an MSM7225 running at 528 Mhz which is below the minimum specs for supporting AR. A device with an MSM7227 chip or better is the minimum hardware requirement to run our SDK.

Sorry for the inconvenience,

-Peter

Re: Supported Device

June 3, 2011 - 11:02am #8

Please make sure your device has a connection to the Internet before running the application for the first time. Let me know if works.

Thank you,

-Peter

Re: Supported Device

June 3, 2011 - 6:28am #7

Hi.
I have a problem with runing sample apps on HTC Wildfire.

When opening app ( for example ImageTargets ) welcome screen shows up and just after that popup with information: "Failed to initialize QCAR because this device is not supported".

I have Wildfire with Android v2.2

Thanks in advance.

Re: Supported Device

May 31, 2011 - 12:53pm #6

Make sure your device is connected to the internet the first time you run the app, and let me know if that helps.

My best advice for getting started with AR is to dive into our sample code and make changes, see what it can do. Refer to the Dev Guide and the API often. There aren't that many resources out there for AR development (that I know of) given how new all this is. My philosophy is typically learn by doing, code is meant to be played with!

Be sure to let us know if you're stumped by anything, we're here to help :)

- Kim

Re: Supported Device

May 31, 2011 - 8:47am #5
ksiva wrote:

Are the samples running at all on the Wildfire, or are they crashing on startup? If they are crashing, can you provide the Android log output? Open the DDMS perspective in Eclipse to view the log.

The list of Supported Devices includes those that we have explicitly tested and optimized for. Other Android 2.1, 2.2, and 2.3 devices are supported, but the samples may run poorly on devices with older/slower processors.

- Kim

Yeah, they had crashed in the startup, and prompted the message corresponds to the value QCAR.INIT_CANNOT_DOWNLOAD_DEVICE_SETTINGS. Sorry, I haven't the log output right now.

BTW, Kim, I'm a student interested in AR but with little AR experience. As a veteran in this area, could you give me some advices or resources to learn these things please. Thanks :)

Re: Supported Device

May 30, 2011 - 6:20am #4

Are the samples running at all on the Wildfire, or are they crashing on startup? If they are crashing, can you provide the Android log output? Open the DDMS perspective in Eclipse to view the log.

The list of Supported Devices includes those that we have explicitly tested and optimized for. Other Android 2.1, 2.2, and 2.3 devices are supported, but the samples may run poorly on devices with older/slower processors.

- Kim

Re: Supported Device

May 29, 2011 - 9:22am #3
Tyro wrote:

https://ar.qualcomm.com/qdevnet/support_file/download/supported%20devices/Supported_Devices.pdf

Wildfire has a 600 MHz processor vs the Desire's 1 GHz Snapdragon processor. That's why you're going to see a significant difference in performance. Try running the Wildfire w/ only the essentials running to reduce the background processor load.

Tyro, thanks for your comments. But the file you mention is a partial list of the supported devices. We still can't figure out whether SDK can run in any devices with Andorid 2.1 and above. And actually, I can't run the sample in Wildfire instead of running a low-performance sample. Still the same processor issue in my case?

BTW, as you suggest a possible way to run the sample, could you please show me some more specific steps. Thanks a lot. :)

Re: Supported Device

May 29, 2011 - 7:36am #2

https://ar.qualcomm.com/qdevnet/support_file/download/supported%20devices/Supported_Devices.pdf

Wildfire has a 600 MHz processor vs the Desire's 1 GHz Snapdragon processor. That's why you're going to see a significant difference in performance. Try running the Wildfire w/ only the essentials running to reduce the background processor load.

Log in or register to post comments