Невозможно запустить приложение com.bell.ship's clock / 10024 для трансляции Намерение: процесс плохой - PullRequest
2 голосов
/ 10 августа 2011

Я создал приложение, похожее на оповещение о тревоге, и все сразу работает нормально, но через некоторое время я обнаружил такую ​​ошибку. Невозможно запустить приложение com.bell.ship's clock / 10024 для широковещательной передачи.1001 *

logcat показан ниже.

08-10 19:00:24.350: DEBUG/dalvikvm(657): GC freed 2898 objects / 149328 bytes in 205ms
08-10 19:00:24.980: INFO/ActivityManager(64): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.bell.shipclock/.SplashScreen bnds=[3,138][77,217] }
08-10 19:00:25.970: INFO/ActivityManager(64): Displayed activity com.bell.shipclock/.SplashScreen: 833 ms (total 833 ms)
08-10 19:00:31.261: DEBUG/dalvikvm(142): GC freed 114 objects / 5248 bytes in 215ms
08-10 19:00:33.511: INFO/ActivityManager(64): Starting activity: Intent { cmp=com.bell.shipclock/.Home }
08-10 19:00:33.551: WARN/ActivityManager(64): Duplicate finish request for HistoryRecord{44da36f0 com.bell.shipclock/.SplashScreen}
08-10 19:00:34.631: INFO/ActivityManager(64): Displayed activity com.bell.shipclock/.Home: 1043 ms (total 1043 ms)
08-10 19:00:35.000: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:00:35.011: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:01:35.011: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:01:35.031: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:02:35.071: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:02:35.121: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:03:35.060: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:03:35.070: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:04:35.021: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:04:35.031: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:05:27.730: DEBUG/dalvikvm(657): GC freed 8964 objects / 439224 bytes in 260ms
08-10 19:05:35.010: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:05:35.023: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:06:35.051: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:06:35.061: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:07:35.050: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:07:35.061: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:08:35.035: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:08:35.053: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:09:35.071: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:09:35.090: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:10:34.050: DEBUG/dalvikvm(64): threadid=15: bogus mon 1+0>0; adjusting
08-10 19:10:35.050: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:10:35.070: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:11:35.071: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:11:35.090: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:12:15.870: DEBUG/dalvikvm(657): GC freed 12371 objects / 576528 bytes in 3495ms
08-10 19:12:17.961: DEBUG/dalvikvm(64): threadid=15: bogus mon 1+0>0; adjusting
08-10 19:12:35.011: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:12:35.032: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:13:02.470: DEBUG/dalvikvm(64): GC freed 12863 objects / 648880 bytes in 2315ms
08-10 19:13:35.046: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:13:35.061: WARN/ActivityManager(64): finishReceiver called but none active
08-10 19:14:35.081: WARN/ActivityManager(64): Unable to launch app com.bell.shipclock/10024 for broadcast Intent { flg=0x4 cmp=com.bell.shipclock/.AlarmReceive1 (has extras) }: process is bad
08-10 19:14:35.090: WARN/ActivityManager(64): finishReceiver called but none active

Я новый пользователь Android и никогда не вижу этой ошибки, как раньше.

Ответы [ 2 ]

2 голосов
/ 10 августа 2011

Может показаться, что вы вызываете finish() дважды для вашего заставки («Дублирующий запрос завершения для HistoryRecord {44da36f0 com.bell.shipclock / .SplashScreen}»). Выясните это, и, возможно, это решит ваши другие проблемы.

0 голосов
/ 17 февраля 2012

При использовании реального устройства единственное, что я обнаружил, чтобы это исправить:

  • Удалите приложение через Настройки -> Приложения.
  • Извлеките аккумулятор из телефона (используяменю Android «Выключение» не работает).
  • Снова включите устройство.
  • Снова установите APK, используя adb install.

См. мой ответ здесь для более подробной информации о том, что не сработало.

...