Android 无法将apk文件从Eclipse Emulator安装到Notes II

Android 无法将apk文件从Eclipse Emulator安装到Notes II,android,eclipse,installation,Android,Eclipse,Installation,我对Android和Java完全陌生。我目前正在学习一门介绍Android和Eclipse的课程。我有个问题。一旦我构建了我的应用程序,我可以通过虚拟应用程序运行它,但我无法将它安装到我的Galaxy Note II手机上。我有调试,模拟和未知的来源允许。Eclipse可以看到我的手机。 另外,我可以通过资源管理器安装apk。我最近读到apk也应该签署。我该怎么做?其他人能帮我吗 [2013-12-10 18:44:47 - Awesome2a] ------------------------

我对Android和Java完全陌生。我目前正在学习一门介绍Android和Eclipse的课程。我有个问题。一旦我构建了我的应用程序,我可以通过虚拟应用程序运行它,但我无法将它安装到我的Galaxy Note II手机上。我有调试,模拟和未知的来源允许。Eclipse可以看到我的手机。 另外,我可以通过资源管理器安装apk。我最近读到apk也应该签署。我该怎么做?其他人能帮我吗

[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): !@Sync 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): !@Sync 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

我完全不知道。您能帮忙吗。

嗯,我怀疑项目设置或androidmanifest.xml文件有问题。在Eclipse的顶部栏中,您可以转到Run>RunConfigurations,翻转到Target选项卡并选择Always prompt为当前配置选择设备吗?只是为了确保它被部署到正确的设备上。假设这不能解决问题,你能发布android清单吗?另外,您是否正在使用任何库或是否有任何外部依赖项?

如果您转到

Project > Unset build automatically
然后呢,

Proyect > clean
Proyect > build project
然后,在project explorer中:

right click on project name > refresh
然后呢,

Proyect > clean
Proyect > build project

然后从设备上卸载您可能拥有的应用程序的任何版本,然后再次尝试安装

你能安装任何演示应用程序吗,或者它会给你这个错误吗?logcat与应用程序无关。您应该将会话筛选器设置为当前页面包。无论如何,在这种情况下,我想它不会说什么。卡洛斯,我试过你的方法,但结果还是一样。在发布的最后一个命令行中,我可以选择Build All、Build Project、Build Working set和Build Automatically。我应该选择哪一个?很抱歉,我已经背诵了,没有写完整的单词,选项是buildproject。建造一切也将是好的。如果您选择了任何其他选项,但该选项不起作用,则需要进一步操作。您的工作区中是否有引用的库?如果是这样:尝试从菜单“项目>清除并选择全部”中清除整个工作区,刷新相关项目,然后选择“项目生成全部”。此外,在安装之前,请从设备上卸载您可能拥有的任何版本的应用程序