无法从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

回答

相关问题