2015-06-20 130 views
2

我在Unity中创建了一个只有一个立方体和定向照明的测试场景。当安装在AVD应用的只是名称是显示器,显示了什么?应用程序无法在Android上启动并强行关闭

我无法弄清楚什么是错误..或者什么让我的应用程序停止运行

AVD设置是使用的是
目标:4.0.3 API等级15
皮肤:HVGA
RAM:512 VM:32
内部存储:200MB
SDCARD:2GB

AVD Screenshort

I/AndroidRuntime( 474): NOTE: attach of thread 'Binder Thread #3' failed  
D/AndroidRuntime( 549):  
D/AndroidRuntime( 549): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<  
D/AndroidRuntime( 549): CheckJNI is ON  
D/AndroidRuntime( 549): Calling main entry com.android.commands.am.Am  
I/ActivityManager( 77): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.asdasd.cd/com.unity3d.player.UnityPlayerNativeActivity} from pid 549  
D/PermissionCache( 36): checking android.permission.READ_FRAME_BUFFER for uid=1000 => granted (22624 us)  
W/WindowManager( 77): Failure taking screenshot for (130x195) to layer 21005  
D/AndroidRuntime( 549): Shutting down VM  
D/dalvikvm( 549): GC_CONCURRENT freed 99K, 77% free 480K/2048K, paused 0ms+1ms  
I/AndroidRuntime( 549): NOTE: attach of thread 'Binder Thread #3' failed  
I/ActivityManager( 77): Start proc com.asdasd.cd for activity com.asdasd.cd/com.unity3d.player.UnityPlayerNativeActivity: pid=559 uid=10041 gids={}  
W/NetworkManagementSocketTagger( 77): setKernelCountSet(10041, 1) failed with errno -2 
I/dalvikvm( 77): Jit: resizing JitTable from 4096 to 8192  
I/ARMAssembler( 36): generated scanline__00000077:03515104_00009002_00000000 [127 ipp] (149 ins) at [0x413fba80:0x413fbcd4] in 869530 ns  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
D/dalvikvm( 559): Trying to load lib /mnt/asec/com.asdasd.cd-2/lib/libmain.so 0x41023f78  
D/dalvikvm( 559): Added shared lib /mnt/asec/com.asdasd.cd-2/lib/libmain.so 0x41023f78  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3 
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3 
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
I/Process ( 77): Sending signal. PID: 559 SIG: 3  
I/dalvikvm( 559): threadid=3: reacting to signal 3  
I/dalvikvm( 559): Wrote stack traces to '/data/anr/traces.txt'  
W/ActivityManager( 77): Launch timeout has expired, giving up wake lock!  
W/ActivityManager( 77): Activity idle timeout for ActivityRecord{411e1ab0 com.asdasd.cd/com.unity3d.player.UnityPlayerNativeActivity}  
D/dalvikvm( 77): GC_CONCURRENT freed 294K, 11% free 8687K/9671K, paused 5ms+7ms  
D/dalvikvm( 160): GC_CONCURRENT freed 436K, 8% free 6992K/7559K, paused 4ms+4ms 

在Android设备上安装应用程序等等类似的行为,并产生相同的类似的日志

I/ActivityManager( 289): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.asdasd.cd/com.unity3d.player.UnityPlayerNativeActivity bnds=[12,433][125,592]} from pid 546 
I/ActivityManager( 289): Start proc com.asdasd.cd for activity com.asdasd.cd/com.unity3d.player.UnityPlayerNativeActivity: pid=4268 uid=10130 gids={} 
W/ResourceType( 289): Skipping entry 0x7f040010 in package table 0 because it is not complex! 
W/ResourceType( 289): Skipping entry 0x7f04003d in package table 0 because it is not complex! 
D/dalvikvm(4268): Trying to load lib /mnt/asec/com.asdasd.cd-1/lib/libmain.so 0x2bde3080 
D/dalvikvm(4268): Added shared lib /mnt/asec/com.asdasd.cd-1/lib/libmain.so 0x2bde3080 
D/SurfaceFlinger( 136): Release buffer at 0xcddd0 
W/ActivityManager( 289): Launch timeout has expired, giving up wake lock! 
W/ActivityManager( 289): Activity idle timeout for ActivityRecord{2c57c1e8 com.asdasd.cd/com.unity3d.player.UnityPlayerNativeActivity} 
+0

外貌就像您的应用程序中的ANR一样。请检查。 – 7383

回答

0

的游戏更好地使用genymotion不使用AVD不支持EGL渲染和搭载Android 4.4版本使用达尔维克而不是艺术...... 希望你明白我的观点。

+0

你可否请详细说明一下.. –

+0

在手机上安装时显示类似的行为,即它停止在第一个屏幕有应用程序的标题...我的手机运行Android 4.0和统一设置设置为最低api水平15(android 4.0.3) –

+0

实际设备中的错误报告是什么? – NilayDani

0

最后我的应用程序的工作..:!d问题是通过更新和应用最新的补丁团结4.6.6p1解决..这消除了错误的旧版本。希望这将有助于有类似的问题有人

相关问题