無法從Eclipse模擬器安裝apk文件到Note II

我完全不熟悉Android和Java。我目前正在參加一門向我介紹Android和Eclipse的課程。我有問題。一旦我建立了我的應用程序，我就可以通過虛擬應用程序運行它，但我無法將其安裝到我的Galaxy Note II手機中。我有調試，模擬和未知來源允許。 Eclipse可以看到我的手機。另外，我可以通過資源管理器安裝apk。我最近讀到apk也應該簽名。我該如何做到這一點，其他人可以幫忙嗎？無法從Eclipse模擬器安裝apk文件到Note II

[2013-12-10 18:44:47 - Awesome2a] ------------------------------ 
[2013-12-10 18:44:47 - Awesome2a] Android Launch! 
[2013-12-10 18:44:48 - Awesome2a] adb is running normally. 
[2013-12-10 18:44:48 - Awesome2a] Performing myapp.awesome2a.MainActivity activity launch 
[2013-12-10 18:44:48 - Awesome2a] Automatic Target Mode: Unable to detect device compatibility. Please select a target device. 
[2013-12-10 18:45:14 - Awesome2a] Uploading Awesome2a.apk onto device '42f73302b863bf67' 
[2013-12-10 18:45:15 - Awesome2a] Installing Awesome2a.apk... 
[2013-12-10 18:45:16 - Awesome2a] Installation failed due to invalid APK file! 
[2013-12-10 18:45:16 - Awesome2a] Please check logcat output for more details. 
[2013-12-10 18:45:16 - Awesome2a] Launch canceled!

當我看看Logcat時，我會收到這些信息。

12-10 18:44:00.002: D/STATUSBAR-Clock(3084): onReceive() - ACTION_TIME_TICK 
12-10 18:44:00.007: D/STATUSBAR-Clock(3084): onReceive() - ACTION_TIME_TICK 
12-10 18:44:00.032: D/ClockAlarmWidgetService(5457): [ClockAlarmWidgetService] onReceive: action = android.intent.action.TIME_TICK 
12-10 18:44:00.032: E/ClockAlarmWidget(5457): [AlarmWidgetIdManager] getListItem() : itemIndex=0, widgetID:1 
12-10 18:44:00.032: E/ClockAlarmWidget(5457): [AlarmWidgetIdManager] getListItem() : ItemIndex exceed ListItemCount. itemIndex=1 
12-10 18:44:00.032: E/ClockAlarmWidget(5457): [AlarmWidgetIdManager] getListItem() : itemIndex=1, widgetID:1 
12-10 18:44:00.032: D/ClockAlarmWidget(5457): [ClockAlarmWidgetProvider] fillData() - itemIndex:0, listitemID: 0 
12-10 18:44:00.037: D/ClockAlarmDataProvider(5457): getAlarm() - too many same ID alarm data. nCount: 0 
12-10 18:44:00.042: D/ClockAlarmWidget(5457): alarmItem = null 
12-10 18:44:00.042: D/ClockWidget(2408): refreshTime() 
12-10 18:44:00.047: D/ClockWidget(2408): TTS Message = It is 6 : 44 PM, Tuesday, December 10 
12-10 18:44:05.727: E/MtpService(3505): In MTPAPP onReceive:android.intent.action.BATTERY_CHANGED 
12-10 18:44:05.727: E/MtpService(3505): battPlugged Type : 2 
12-10 18:44:05.727: D/BatteryService(2408): update start 
12-10 18:44:05.727: D/BatteryService(2408): level:100 scale:100 status:2 health:2 present:true voltage: 4326 temperature: 249 technology: Li-ion AC powered:false USB powered:true icon:17303211 invalid charger:0 
12-10 18:44:05.727: D/STATUSBAR-BatteryController(3084): onReceive() - ACTION_BATTERY_CHANGED 
12-10 18:44:05.727: D/STATUSBAR-BatteryController(3084): onReceive() - level:100 
12-10 18:44:05.727: D/STATUSBAR-BatteryController(3084): onReceive() - plugged:2 
12-10 18:44:05.727: D/STATUSBAR-BatteryController(3084): onReceive() - BATTERY_STATUS_CHARGING: 
12-10 18:44:05.732: D/STATUSBAR-PhoneStatusBar(3084): ACTION_BATTERY_CHANGED 
12-10 18:44:05.732: D/STATUSBAR-PhoneStatusBar(3084): NORMAL_BATTERY 
12-10 18:44:05.737: W/AlarmManager(2408): FACTORY_ON= 0 
12-10 18:44:23.687: E/Watchdog(2408): [email protected] 28 
12-10 18:44:29.682: E/WifiHW(2408): ##################### set firmware type 0 ##################### 
12-10 18:44:29.682: D/WifiStateMachine(2408): setWifiEnabled : WifiNative.setFwType(0) 
12-10 18:44:29.682: V/AlarmManager(2408): waitForAlarm result :4 
12-10 18:44:29.682: V/AlarmManager(2408): trigger ELAPSED_REALTIME_WAKEUP or RTC_WAKEUP 
12-10 18:44:29.682: D/WifiService(2408): startScan: false pid=3965, uid=10019 
12-10 18:44:29.687: W/AlarmManager(2408): FACTORY_ON= 0 
12-10 18:44:29.697: I/wpa_supplicant(3889): Scan requested (ret=0) - scan timeout 30 seconds 
12-10 18:44:29.762: W/AlarmManager(2408): FACTORY_ON= 0 
12-10 18:44:33.347: I/wpa_supplicant(3889): nl80211: Received scan results (9 BSSes) 
12-10 18:44:33.347: D/Tethering(2408): interfaceLinkStateChanged wlan0, true 
12-10 18:44:33.347: D/Tethering(2408): interfaceStatusChanged wlan0, true 
12-10 18:44:33.357: W/AlarmManager(2408): FACTORY_ON= 0 
12-10 18:44:33.377: D/dalvikvm(3965): GC_CONCURRENT freed 511K, 8% free 13209K/14343K, paused 1ms+1ms, total 14ms 
12-10 18:44:33.377: D/dalvikvm(3965): WAIT_FOR_CONCURRENT_GC blocked 8ms 
12-10 18:44:33.382: W/AlarmManager(2408): FACTORY_ON= 0 
12-10 18:44:33.412: E/WifiHW(2408): ##################### set firmware type 0 ##################### 
12-10 18:44:33.412: D/WifiStateMachine(2408): setWifiEnabled : WifiNative.setFwType(0) 
12-10 18:44:33.417: W/AlarmManager(2408): FACTORY_ON= 0 
12-10 18:44:33.467: I/GCoreUlr(3965): Successfully inserted location 
12-10 18:44:33.467: I/GCoreUlr(3965): Not calling LocationReportingService, hasMoved: false, elapsed millis: 780030, request: Phone 
12-10 18:44:34.682: V/AlarmManager(2408): waitForAlarm result :4 
12-10 18:44:41.742: D/BatteryService(2408): update start 
12-10 18:44:41.747: E/MtpService(3505): In MTPAPP onReceive:android.intent.action.BATTERY_CHANGED 
12-10 18:44:41.747: E/MtpService(3505): battPlugged Type : 2 
12-10 18:44:41.747: D/BatteryService(2408): level:100 scale:100 status:2 health:2 present:true voltage: 4326 temperature: 242 technology: Li-ion AC powered:false USB powered:true icon:17303211 invalid charger:0 
12-10 18:44:41.747: D/STATUSBAR-BatteryController(3084): onReceive() - ACTION_BATTERY_CHANGED 
12-10 18:44:41.747: D/STATUSBAR-BatteryController(3084): onReceive() - level:100 
12-10 18:44:41.747: D/STATUSBAR-BatteryController(3084): onReceive() - plugged:2 
12-10 18:44:41.747: D/STATUSBAR-BatteryController(3084): onReceive() - BATTERY_STATUS_CHARGING: 
12-10 18:44:41.762: W/AlarmManager(2408): FACTORY_ON= 0 
12-10 18:44:41.762: D/STATUSBAR-PhoneStatusBar(3084): ACTION_BATTERY_CHANGED 
12-10 18:44:41.762: D/STATUSBAR-PhoneStatusBar(3084): NORMAL_BATTERY 
12-10 18:44:41.777: D/dalvikvm(3965): GC_CONCURRENT freed 396K, 8% free 13201K/14343K, paused 12ms+1ms, total 27ms 
12-10 18:44:53.687: E/Watchdog(2408): [email protected] 29 
12-10 18:44:59.997: V/AlarmManager(2408): waitForAlarm result :8 
12-10 18:44:59.997: V/AlarmManager(2408): ClockReceiver onReceive() ACTION_TIME_TICK 
12-10 18:44:59.997: W/AlarmManager(2408): FACTORY_ON= 0

我完全沒有線索。你能幫我嗎。

來源

2013-12-10 Le0n0920

你可以安裝任何演示應用程序，還是它會給你帶來這個錯誤？ – raydowe

logcat與該應用無關。您已將會話過濾器設置爲當前的pagackage。無論如何，在這種情況下，我想它不會說什麼。 –

嗯，我會懷疑項目設置或androidmanifest.xml文件有問題。在Eclipse的頂部欄中，您可以轉到運行>運行配置，翻到「目標」選項卡並選擇「始終提示選擇設備」以獲取當前配置？只是爲了確保它被部署到正確的設備。假設沒有解決它，你可以發佈Android清單？另外，你使用任何庫還是你有任何外部依賴？

來源

2013-12-11 00:10:28 Cogentleman

<？xml version =「1.0」encoding =「utf-8」？> <使用-SDK 機器人：的minSdkVersion = 「8」機器人：targetSdkVersion = 「19」/> – Le0n0920

<應用機器人：allowBackup = 「真」機器人：圖標= 「@繪製/ ic_launcher」機器人：標籤= 「@串/ APP_NAME」機器人：主題= 「@風格/ AppTheme」> <活動機器人：名稱= 「myapp.awesome2a.MainActivity」 android：label =「@ string/app_name」> – Le0n0920

請參閱上面的android清單。 – Le0n0920

Usualy如果你去

Project > Unset build automatically

然後，

Proyect > clean

，然後在項目資源管理器：

right click on project name > refresh

然後，

Proyect > build project

然後從設備上卸載您可能擁有的任何應用程序版本，然後嘗試重新安裝。

來源

2013-12-11 01:17:41

卡洛斯，我試過你的方式，我仍然得到相同的結果。在發佈的最後一個命令行上，我可以選擇Build All，Build Project，Build Working set和Build Automatically。我應該選擇哪一個？ – Le0n0920

抱歉，我已經告訴過你了，並沒有寫出完整的單詞，選項是建立項目。建設一切也將是好的。如果您選擇了其他任何方式，那麼該方法無效，您需要走得更遠。你有沒有任何參考庫也在你的工作區？如果是這樣的話：嘗試從菜單項目清除整個工作區>清除並選擇全部，刷新涉及的項目，並選擇項目構建全部 –

另外，在安裝之前，從設備上卸載任何版本的應用程序， –

無法從Eclipse模擬器安裝apk文件到Note II

回答

相關問題