hi , my first post here , I tried to run the sample app on the site. but when I run the project on my nexus s it shows the unity3d logo and stays about 3 seconds and then go to the main menu of my device . I think there's something with the minimum api level . it's mentioned in the site that in the player settings , the "minimum api level" should be 7 or android 2.1 or eclair . but I don't see "minimum api level" on my player settings . there's just an "Api compatibility level" which only has ".Net 2.0" and ".Net 2.0 subnet" options.
I should mention that I have unity 3.2
anyone can help me with this?
thanks
- Sort Posts
- 7 replies
- Last post
unity app doesn't work on my device
October 3, 2011 - 10:06am #8
Re: unity app doesn't work on my device
October 4, 2011 - 3:02pm #6
I set the minimum api level to 7 and on another try to 10 , I connected my device to internet and I'm trying to build the imagetarget sample but it doesn't work . when I build and run the application the unity logo appears on my device and then after about 3 seconds it goes to the main menu of my phone . I exactly did the instruction on the imagetarget sample . should I also do anything on the publish settings? I mean keystore password or something?
thanks
Re: unity app doesn't work on my device
October 5, 2011 - 1:52pm #5
Re: unity app doesn't work on my device
October 5, 2011 - 6:21pm #4
mojtaba -
Could you get the runtime log using the DDMS tool and attach it here? DDMS is located in the "tools" directory of the Android SDK. You can also get the log by running "adb logcat" from a terminal, assuming the Android sdk is on your system path.
ina -
Can you elaborate on the Android issue? Are the targets tracking sometimes or not at all? We'll discuss the iOS issue in your other thread.
- Kim
Re: unity app doesn't work on my device
October 6, 2011 - 3:01am #3
Hi
I'm having a similar problem, the app immediately closes down. I first tried the simple app test as described in the SDK setup using the Unity Extension, and when that failed, I created a very basic scene (just a normal camera, light and a cube) that I know works, and then purely imported the base qcar unity package. As soon as I build and run with that included, then it has the same behaviour (presumably due to the manifest file including the qualcomm activities.
- Phone: Sone Ericsson X10 mini pro, running Android 2.1 - update1
- Unity 3.4.1f5
- DDMS Output:
10-06 10:48:48.407: DEBUG/dalvikvm(3741): GC freed 96 objects / 3776 bytes in 143ms
10-06 10:48:49.847: INFO/ActivityManager(1181): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.FuzzyLogic.AndroidTest/com.qualcomm.QCARUnityPlayer.QCARPlayerProxyActivity }
10-06 10:48:49.917: INFO/ActivityManager(1181): Start proc com.FuzzyLogic.AndroidTest for activity com.FuzzyLogic.AndroidTest/com.qualcomm.QCARUnityPlayer.QCARPlayerProxyActivity: pid=7976 uid=10083 gids={3003, 1006}
10-06 10:48:49.957: INFO/dalvikvm(7976): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38)
10-06 10:48:49.987: INFO/dalvikvm(7976): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=56)
10-06 10:48:50.387: INFO/ActivityManager(1181): Starting activity: Intent { flg=0x10000 cmp=com.FuzzyLogic.AndroidTest/com.qualcomm.QCARUnityPlayer.QCARPlayerActivity (has extras) }
10-06 10:48:50.397: DEBUG/dalvikvm(7976): Trying to load lib /data/data/com.FuzzyLogic.AndroidTest/lib/libQCAR.so 0x45680370
10-06 10:48:50.407: DEBUG/dalvikvm(7976): Added shared lib /data/data/com.FuzzyLogic.AndroidTest/lib/libQCAR.so 0x45680370
10-06 10:48:50.508: INFO/DEBUG(7901): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-06 10:48:50.508: INFO/DEBUG(7901): Build fingerprint: 'SEMC/U20i_1238-0199/U20i/delta:2.1-update1/2.0.A.0.504/-AFA:user/release-keys'
10-06 10:48:50.508: INFO/DEBUG(7901): pid: 7976, tid: 7976 >>> com.FuzzyLogic.AndroidTest <<<
10-06 10:48:50.508: INFO/DEBUG(7901): signal 4 (SIGILL), fault addr 81021000
10-06 10:48:50.508: INFO/DEBUG(7901): r0 0000ab00 r1 00000000 r2 8114e210 r3 81020fdc
10-06 10:48:50.508: INFO/DEBUG(7901): r4 00140da0 r5 ad07ff50 r6 0000bda8 r7 00140d30
10-06 10:48:50.508: INFO/DEBUG(7901): r8 ad00f3c0 r9 0000bda8 10 4186ec14 fp 00000000
10-06 10:48:50.508: INFO/DEBUG(7901): ip ad08000c sp be90e870 lr ad03cea7 pc 81021000 cpsr 20000010
10-06 10:48:50.547: INFO/DEBUG(7901): #00 pc 00021000 /data/data/com.FuzzyLogic.AndroidTest/lib/libQCAR.so
10-06 10:48:50.547: INFO/DEBUG(7901): #01 pc 0003cea4 /system/lib/libdvm.so
10-06 10:48:50.547: INFO/DEBUG(7901): #02 pc 0005452a /system/lib/libdvm.so
10-06 10:48:50.547: INFO/DEBUG(7901): #03 pc 00013f48 /system/lib/libdvm.so
10-06 10:48:50.547: INFO/DEBUG(7901): #04 pc 00019848 /system/lib/libdvm.so
10-06 10:48:50.547: INFO/DEBUG(7901): #05 pc 00018d1c /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #06 pc 0004da90 /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #07 pc 0004dac2 /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #08 pc 000585f2 /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #09 pc 00013520 /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #10 pc 00019848 /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #11 pc 00018d1c /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #12 pc 0004d77c /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #13 pc 00055234 /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #14 pc 00013f48 /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #15 pc 00019848 /system/lib/libdvm.so
10-06 10:48:50.557: INFO/DEBUG(7901): #16 pc 00018d1c /system/lib/libdvm.so
10-06 10:48:50.567: INFO/DEBUG(7901): #17 pc 0004da90 /system/lib/libdvm.so
10-06 10:48:50.567: INFO/DEBUG(7901): #18 pc 0003a6ec /system/lib/libdvm.so
10-06 10:48:50.567: INFO/DEBUG(7901): #19 pc 0002990c /system/lib/libandroid_runtime.so
10-06 10:48:50.567: INFO/DEBUG(7901): #20 pc 0002a5f0 /system/lib/libandroid_runtime.so
10-06 10:48:50.567: INFO/DEBUG(7901): #21 pc 00008cae /system/bin/app_process
10-06 10:48:50.567: INFO/DEBUG(7901): #22 pc 0000c2d6 /system/lib/libc.so
10-06 10:48:50.567: INFO/DEBUG(7901): #23 pc b00018ac /system/bin/linker
10-06 10:48:50.567: INFO/DEBUG(7901): code around pc:
10-06 10:48:50.567: INFO/DEBUG(7901): 81020ff0 e3a01000 e5820004 e58d1004 0a000007
10-06 10:48:50.567: INFO/DEBUG(7901): 81021000 e3002004 e5903000 e3402001 e28d1004
10-06 10:48:50.567: INFO/DEBUG(7901): code around lr:
10-06 10:48:50.577: INFO/DEBUG(7901): ad03ce94 90094b26 58ea20db 9b030081 21005850
10-06 10:48:50.577: INFO/DEBUG(7901): ad03cea4 99094798 1c309003 ff5af003 4b209906
10-06 10:48:50.577: INFO/DEBUG(7901): ad03ceb4 66f19a03 d013429a 429a3b02 3304d010
10-06 10:48:50.577: INFO/DEBUG(7901): stack:
10-06 10:48:50.577: INFO/DEBUG(7901): be90e830 ad06ae14 /system/lib/libdvm.so
10-06 10:48:50.577: INFO/DEBUG(7901): be90e834 00000000
10-06 10:48:50.577: INFO/DEBUG(7901): be90e838 000000f0
10-06 10:48:50.577: INFO/DEBUG(7901): be90e83c b00004f3 /system/bin/linker
10-06 10:48:50.577: INFO/DEBUG(7901): be90e840 00000000
10-06 10:48:50.577: INFO/DEBUG(7901): be90e844 b000f448 /system/bin/linker
10-06 10:48:50.577: INFO/DEBUG(7901): be90e848 00000000
10-06 10:48:50.577: INFO/DEBUG(7901): be90e84c b0003208 /system/bin/linker
10-06 10:48:50.577: INFO/DEBUG(7901): be90e850 b0017f18
10-06 10:48:50.577: INFO/DEBUG(7901): be90e854 81020fdc /data/data/com.FuzzyLogic.AndroidTest/lib/libQCAR.so
10-06 10:48:50.577: INFO/DEBUG(7901): be90e858 00008ad0 /system/bin/app_process
10-06 10:48:50.577: INFO/DEBUG(7901): be90e85c 00140d30 [heap]
10-06 10:48:50.577: INFO/DEBUG(7901): be90e860 ad00f3c0 /system/lib/libdvm.so
10-06 10:48:50.577: INFO/DEBUG(7901): be90e864 b0001c85 /system/bin/linker
10-06 10:48:50.577: INFO/DEBUG(7901): be90e868 df002777
10-06 10:48:50.577: INFO/DEBUG(7901): be90e86c e3a070ad
10-06 10:48:50.577: INFO/DEBUG(7901): #00 be90e870 00140da0 [heap]
10-06 10:48:50.577: INFO/DEBUG(7901): be90e874 00000000
10-06 10:48:50.577: INFO/DEBUG(7901): be90e878 00140da0 [heap]
10-06 10:48:50.577: INFO/DEBUG(7901): be90e87c ad03cea7 /system/lib/libdvm.so
10-06 10:48:50.587: INFO/DEBUG(7901): #01 be90e880 45680370 /mspace/dalvik-heap/2 (deleted)
10-06 10:48:50.587: INFO/DEBUG(7901): be90e884 ad040d81 /system/lib/libdvm.so
10-06 10:48:50.587: INFO/DEBUG(7901): be90e888 4187fbbc /dalvik-LinearAlloc (deleted)
10-06 10:48:50.587: INFO/DEBUG(7901): be90e88c 81020fdc /data/data/com.FuzzyLogic.AndroidTest/lib/libQCAR.so
10-06 10:48:50.587: INFO/DEBUG(7901): be90e890 45680370 /mspace/dalvik-heap/2 (deleted)
10-06 10:48:50.587: INFO/DEBUG(7901): be90e894 ad065ad4 /system/lib/libdvm.so
10-06 10:48:50.587: INFO/DEBUG(7901): be90e898 00000000
10-06 10:48:50.587: INFO/DEBUG(7901): be90e89c 00140dac [heap]
10-06 10:48:50.587: INFO/DEBUG(7901): be90e8a0 00140db0 [heap]
10-06 10:48:50.587: INFO/DEBUG(7901): be90e8a4 00000001
10-06 10:48:50.587: INFO/DEBUG(7901): be90e8a8 4186ec28
10-06 10:48:50.587: INFO/DEBUG(7901): be90e8ac be90e918 [stack]
10-06 10:48:50.587: INFO/DEBUG(7901): be90e8b0 00140d30 [heap]
10-06 10:48:50.587: INFO/DEBUG(7901): be90e8b4 45680370 /mspace/dalvik-heap/2 (deleted)
10-06 10:48:50.587: INFO/DEBUG(7901): be90e8b8 4005d038 /mspace/dalvik-heap/zygote/0 (deleted)
10-06 10:48:50.587: INFO/DEBUG(7901): be90e8bc ad05452f /system/lib/libdvm.so
10-06 10:48:50.887: DEBUG/Zygote(1093): Process 7976 terminated by signal (4)
10-06 10:48:50.897: INFO/ActivityManager(1181): Process com.FuzzyLogic.AndroidTest (pid 7976) has died.
10-06 10:48:50.897: INFO/UsageStats(1181): Unexpected resume of com.sonyericsson.homescreen while already resumed in com.FuzzyLogic.AndroidTest
10-06 10:48:50.937: WARN/InputManagerService(1181): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@45841b68
10-06 10:48:51.367: DEBUG/iddd-events(1112): Registering event com.sonyericsson.idd.probe.android.devicemonitor::ApplicationCrash with 4299 bytes payload.
Re: unity app doesn't work on my device
October 6, 2011 - 2:01pm #2
Mine's working fine now , I did some things which I'm not sure which one fixed it .
- I closed and restarted unity
- I set the minimum API to 7
- point the ARcamera no where
- kill as many apps on your phone as you can using 'task killer'
- make sure your device is connected to the internet
Version 1.0.6 of the QCAR Unity Extension should still work with Unity 3.2. Make sure your device is connected to the internet before running the app. Try running one of the sample applications (e.g. ImageTargets), or grab the InitializationErrorHandler from the sample and attach it to your ARCamera. You can also check the runtime logs using the DDMS tool that comes with Android.
- Kim