APK, Android 4.0 öykünücüsüne yüklenemedi

Önceki tüm SDK-s apk'de iyi çalışıyor. 4.0 üzerinde test çalıştı. Tüm son güncellemeleri eclipse'den indirdi. Ve ne aldım

...

[2011-10-28 11:39:34 - breath-trainer] Android Launch!
[2011-10-28 11:39:34 - breath-trainer] adb is running normally.
[2011-10-28 11:39:34 - breath-trainer] Performing com.breath.ui.activity.BreathTrainerActivity activity launch
[2011-10-28 11:39:37 - breath-trainer] Launching a new emulator with Virtual Device '4.0_api_14_SUKA'
[2011-10-28 11:39:38 - breath-trainer] New emulator found: emulator-5554
[2011-10-28 11:39:38 - breath-trainer] Waiting for HOME ('android.process.acore') to be launched...
[2011-10-28 11:40:30 - breath-trainer] HOME is up on device 'emulator-5554'
[2011-10-28 11:40:30 - breath-trainer] Uploading breath-trainer.apk onto device 'emulator-5554'
[2011-10-28 11:40:31 - breath-trainer] Installing breath-trainer.apk...
[2011-10-28 11:40:56 - breath-trainer] Success!
[2011-10-28 11:40:56 - breath-trainer] Failed to install breath-trainer.apk on device 'emulator-5554': device not found
[2011-10-28 11:40:56 - breath-trainer] com.android.ddmlib.InstallException: device not found
[2011-10-28 11:40:56 - breath-trainer] Launch canceled!

Ayrıca LogCat'ta StrictMode ilkesi ihlali ve en küçük olanı ile ilgili birçok istisna vardır:

10-28 11:40:51.711: A/NetworkStats(74): problem reading network stats
10-28 11:40:51.711: A/NetworkStats(74): java.lang.IllegalStateException: problem parsing line: null
10-28 11:40:51.711: A/NetworkStats(74):     at com.android.internal.net.NetworkStatsFactory.readNetworkStatsDetail(NetworkStatsFactory.java:313)
10-28 11:40:51.711: A/NetworkStats(74):     at com.android.server.NetworkManagementService.getNetworkStatsUidDetail(NetworkManagementService.java:1223)
10-28 11:40:51.711: A/NetworkStats(74):     at com.android.server.net.NetworkStatsService.performPollLocked(NetworkStatsService.java:810)
10-28 11:40:51.711: A/NetworkStats(74):     at com.android.server.net.NetworkStatsService.updateIfacesLocked(NetworkStatsService.java:721)
10-28 11:40:51.711: A/NetworkStats(74):     at com.android.server.net.NetworkStatsService.updateIfaces(NetworkStatsService.java:699)
10-28 11:40:51.711: A/NetworkStats(74):     at com.android.server.net.NetworkStatsService.access$000(NetworkStatsService.java:128)
10-28 11:40:51.711: A/NetworkStats(74):     at com.android.server.net.NetworkStatsService$8.handleMessage(NetworkStatsService.java:1546)
10-28 11:40:51.711: A/NetworkStats(74):     at android.os.Handler.dispatchMessage(Handler.java:95)
10-28 11:40:51.711: A/NetworkStats(74):     at android.os.Looper.loop(Looper.java:137)
10-28 11:40:51.711: A/NetworkStats(74):     at android.os.HandlerThread.run(HandlerThread.java:60)
10-28 11:40:51.711: A/NetworkStats(74): Caused by: java.io.FileNotFoundException: /proc/net/xt_qtaguid/stats: open failed: ENOENT (No such file or directory)
10-28 11:40:51.711: A/NetworkStats(74):     at libcore.io.IoBridge.open(IoBridge.java:406)
10-28 11:40:51.711: A/NetworkStats(74):     at java.io.FileInputStream.(FileInputStream.java:78)
10-28 11:40:51.711: A/NetworkStats(74):     at java.io.FileReader.(FileReader.java:42)
10-28 11:40:51.711: A/NetworkStats(74):     at com.android.internal.net.NetworkStatsFactory.readNetworkStatsDetail(NetworkStatsFactory.java:272)
10-28 11:40:51.711: A/NetworkStats(74):     ... 9 more
10-28 11:40:51.711: A/NetworkStats(74): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
10-28 11:40:51.711: A/NetworkStats(74):     at libcore.io.Posix.open(Native Method)
10-28 11:40:51.711: A/NetworkStats(74):     at libcore.io.BlockGuardOs.open(BlockGuardOs.java:98)
10-28 11:40:51.711: A/NetworkStats(74):     at libcore.io.IoBridge.open(IoBridge.java:390)
10-28 11:40:51.711: A/NetworkStats(74):     ... 12 more

Bazı fikirler?

2
Maalesef, soru yazarken metin iyi biçimleniyor ...
katma yazar whatswrong, kaynak

3 cevap

'emülatör-5554': cihaz bulunamadı

Sanal Cihaz '4.0_api_14_SUKA'

2 Teori:

1.- The emulator is an api 14 (Android 4.0) and the emulator is out of space: Try this --> Android 4.0 emulator - out of space error

2.- Bazen Eclipse ile emülatör arasındaki bağlantı kaybolur. Emülatörü kapatın ve tekrar açın.

2
katma
Teşekkür ederim! İlk nokta yardım etti!
katma yazar whatswrong, kaynak

Bu problemi yaşadım. Neden olduğunu açıklayamıyorum ama nasıl çalıştığımı anlatabilirim. Bu mesajı aldığımda, ICS emülatörü hala görünüyordu. Uygulamam yüklendi ve uygulamalara gidip onu seçerek başlatılabilir. Benim için büyük sorun, logcat artık çalışmıyordu. Çalışan emülatör için tekrar çalışmaya başlamak için komut satırından aşağıdakileri yaparım: (çevresel değişkenlerinizin ayarlandığı varsayılarak) 1) "adb" girin 2) "adb kill-server" yazınız 3) "adb start-server" yazınız 4) uygulamayı yeniden başlatın ve çalışan emülatörü hedefleyin

I hope that works for you as it did for me. I'd love it if someone could actually explain this problem properly. From the research I've done, it looks like it's related to Strict Mode or some kind of timeout. Someone else suggested that I update the timeout setting for adb in eclipse. This didn't work for me, but it might help someone else: Eclipse > Preferences > Android > DDMS - then set the ADB connection timeout to something higher than the time it takes for you system to start ICS.

2
katma

Bu asıl sorun değil, cihazımda çalıştırıyorum aynı hatayı aldım ama ICS çalışır: P

0
katma
Evet, tutarsız çalışır :(
katma yazar whatswrong, kaynak