Log in or register to post comments

Samsung Captivate it's not woking

February 26, 2011 - 9:09pm #1

sorry my poor English
hey Kim I don't understand

Yesterday,I got Samsung Captivate that supported on device lists.I try to work QCAR with Unity 3.2 (patched QCAR extension to work with Unity 3.2) My Captivate is android 2.1 Update 1. I made it follow Quick start" in AR Extension for Unity 3 heading.when I insert camera prefab this step tell me "you can run the application on a supported Android device and see the live video in the background." When I Build & run on my Captivate it's show popup message that "Old firmware detect! Your device is running an outdated firmware version......" when I tap OK button.It's show Unity Splash screen and close program.Why? (after I try to made until finish it's not work too)

in QCAR Unity 3.2 Compatibility Patch:
You can fix this by making the following modifications to TrackerScript.cs
(located in the Qualcomm Augmented Reality/Scripts folder):

// Add a global material
private Material clearMaterial;

Where is the correct line that I paste "private Material clearMaterial;"? sorry I'm a designer not hardcore programmer.

Re: Samsung Captivate it's not woking

March 8, 2011 - 5:48pm #19

i try to update Official OS again, it's not a custom Rom. Connected to the internet,too.

but, it's failed.

This Samsung model name is Galaxy S SHW-M110S..

but this model is korea version. it's Same Samsung Galaxy S..

but model name is different.. it's not in support list.

is it problem? Did you test this model??

sorry again, my poor english~^^; thanx

Re: Samsung Captivate it's not woking

March 8, 2011 - 6:00am #18

Let's do some basic debugging first. Exactly which Samsung model are you using? Make sure it is on the list of supported models. Have you updated it to Android OS 2.2? Be sure to get the official OS update, not a custom ROM off the internet. Finally, is it connected to the internet when you try running the QCAR application?

- Kim

Re: Samsung Captivate it's not woking

March 7, 2011 - 11:47pm #17

i have same this error... but i'm not solved..

I want test APK file,too. plz send to me. thnx .

Re: Samsung Captivate it's not woking

March 1, 2011 - 7:20pm #16

YAHOOO!!! Congratulation!!! I got it!
I try to update firmware again and I connect Wifi internet the first time.I immediately built & run again.It's show Unity Splash screen .I

wait a moment around 5-8 sec. and camera was worked!!!! Everything can work great.I'm very excite.Thank you Kim that you help me

so long time.Thank very much

finally,I have plan to work with QCAR in this summer.If I got new problem.Please help me again Kim.Thank

Re: Samsung Captivate it's not woking

March 1, 2011 - 3:02pm #15

Also, could you let us know what the model number of your device is? Thanks!

- Kim

Re: Samsung Captivate it's not woking

March 1, 2011 - 2:40pm #14

I sent you an email about the test APK file.

How did you update your Captivate to OS 2.2.1 in the first place? We didn't find an official update from Samsung. The DDMS error is strange, it's the sort of thing you might see in a custom kernel with logging disabled.

Make sure that you have the official Samsung OS update installed.

- Kim

Re: Samsung Captivate it's not woking

March 1, 2011 - 9:39am #13

Oh!! now I just downgrade my Captivate to 2.2 like you.something change when I build it.I use sample scene "QCAR-ImageTargets.unity" to tested. When I Build & run it show error message

"QCAR Initialzation Error
Network connection required to initialize camera settings. Please check your connection and restart the application.If you are still

experiencing problem,then your device may not be currently supported."

I'm very sure that my Captivate connected to Wifi internet.What's wrong?

///////////////////////////////////////////////////////
by the way,now I can run ddmc. It's show Dalvik Debug Monitor window.in log window have some text :

>"??-?? ??:??:??.???: INFO/(): Unable to open log device '/dev/log/main': No such file or directory
"

When I build test.Nothing henpen!!! How to got message error log? (in adb logcat it's same effect)
///////////////////////////////////////////////////
I have some idea.Can you sent the application file that you work to me? I'll install your work app to test.If it work,it's mean my codes or something have some problem.

Re: Samsung Captivate it's not woking

March 1, 2011 - 8:50am #12

Make sure your device is connected to the internet the first time you try to run your QCAR application. The error message should tell you if you are not connected, but double check this just in case.

- Kim

Re: Samsung Captivate it's not woking

March 1, 2011 - 8:41am #11

Hmm, it sounds like you might not have Java installed. That's okay, you can also get the log on the command line, by running "adb logcat" from the /platform-tools folder.

- Kim

Re: Samsung Captivate it's not woking

March 1, 2011 - 7:42am #10

ok Now I try to run ddms.bat on cmd.Something problem It show "Unable to acces jarfile lib\archquery.jar
SWT folder '' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for your platform."

How to pass this step?

Re: Samsung Captivate it's not woking

March 1, 2011 - 7:04am #9

Could you send me the error message you are seeing? That would really help!

- Kim

Re: Samsung Captivate it's not woking

March 1, 2011 - 6:59am #8

My firmware version is 2.2.1 not 2.2 .Is it not work with 2.2.1?
Can you upgrade to 2.2.1 and test it again?

Re: Samsung Captivate it's not woking

March 1, 2011 - 6:07am #7

We upgraded a Samsung Captivate to OS 2.2 last night and tried this, and it seemed to work fine. Let's see if we can debug this issue.

First, start by running one of the sample applications (say ImageTargets). Be sure to add the QCAR Unity 3.2 Patch first.

Do you get a popup window with an error message when the application crashes? If so what does it say?

Next grab the device log. Go to your Android SDK folder and run the "ddms" application, located under the tools folder. Select your device, and clear the log (little icon, sheet of paper with a red X). Now run the application fresh, and then save the log using the save button in ddms. Send that file to

, and I'll take a look.

Thanks!

- Kim

Re: Samsung Captivate it's not woking

March 1, 2011 - 5:55am #6

Thank Kim.I'll wait your good news.

Re: Samsung Captivate it's not woking

February 28, 2011 - 12:12pm #5

Hopefully we'll have something in a matter of weeks, I'll keep you updated.

- Kim

Re: Samsung Captivate it's not woking

February 27, 2011 - 7:55pm #4

Hi Kim no good news for you and me.Last night I try to upgrade from 2.1 and now my Captivate is 2.2.1.Upgrade was perfect!

I try to test normal unity App.No popup message problem about old firmware version. It's great to run normal Unity App.And then I try to test QCAR unity with only ARCamera (QCAR Extension was patched).when finished build & run It show Unity splash screen and close.It's not work.

How long will I get some good news to work with QCAR? a month or year

sorry about my poor English gramma
Thank.

Re: Samsung Captivate it's not woking

February 27, 2011 - 8:08am #3

Thank you Kim .I try to upgrade to 2.2 at this night.I hope everything it's OK.I'll tell you tomorrow and I hope that It's good news for you & me.Thank for your help about line of code again.

Re: Samsung Captivate it's not woking

February 27, 2011 - 5:44am #2

Unfortunately the Samsung Galaxy S devices do not work with Unity if Android OS 2.1 is installed. You will need to upgrade your device to Android OS 2.2 for any Unity applications to run on it. You can double check this by running a simple Unity application without QCAR, you should see the same problem.

We haven't tested QCAR on the Galaxy S with 2.2 installed yet, so I cannot guarantee that it will work. I know that this is on the to-do list for the near future though, so if it doesn't work now hopefully it will soon. Please let us know if you have any problems after upgrading your device to Android 2.2.

As for this line of code:

private Material clearMaterial;

That simply goes anywhere in the class's global member space. Try placing it just after the following tag line:

#region CLASS_MEMBERS

You should see a bunch of other member variables declared after that point, this one can go with those.

- Kim

Log in or register to post comments