Alarm Klock: FORCE CLOSE [IllegalArgumentException] when using Notification Bar to reopen Alarm Klock

[ECHRSON]

Hi Kraig,

Despite adding Alarm Klock to the "ignore list" in my App/task killer
(ES Task manager) I am experiencing Force Closes when I open the app
from the drop down "Notification bar". Sometimes I get the Force Close
once the alaram has "gone off" and the application is about to be
dismissed (and then showing the Home screen OR returning to Locked/
Standby screen).

I have used this app for 6+ months on Samsung Galaxy Spica running
Android 2.1 with out a single Force Close.
(Also here I used ER Task Manager with Alarm Klock added to the
"ignore list", fyi...)

Now I have a Samsung Galaxy S runnning Android 2.2 and I are getting
this behavior quite often.

I hope this will help you making this great app even better.

BR,
Christian, Sweden

LOGCAT:
=======================================
01-27 10:13:06.873: INFO/Ringtone(11127): Temp URI for media play
is : content://media/internal/audio/media/29
01-27 10:13:06.873: INFO/Ringtone(11127): it is a valid Media DB
URI : content://media/internal/audio/media/29
01-27 10:13:06.877: INFO/Ringtone(11127): The actual path is:/system/
media/audio/alarms/Good_Morning.ogg
01-27 10:13:06.877: INFO/Ringtone(11127): openMediaPlayer() isMidFile:
false
01-27 10:13:07.018: DEBUG/AndroidRuntime(11127): Shutting down VM
01-27 10:13:07.018: WARN/dalvikvm(11127): threadid=1: thread exiting
with uncaught exception (group=0x4001d7d0)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): FATAL EXCEPTION: main
01-27 10:13:07.034: ERROR/AndroidRuntime(11127):
java.lang.IllegalArgumentException: Service not registered:
com.angrydoughnuts.android.alarmclock.NotificationServiceBinder
$1@48080518
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
android.app.ActivityThread
$PackageInfo.forgetServiceDispatcher(ActivityThread.java:1074)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
android.app.ContextImpl.unbindService(ContextImpl.java:969)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
android.content.ContextWrapper.unbindService(ContextWrapper.java:352)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
com.angrydoughnuts.android.alarmclock.NotificationServiceBinder.unbind(NotificationServiceBinder.java:
45)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
com.angrydoughnuts.android.alarmclock.ActivityAlarmClock
$6$1.run(ActivityAlarmClock.java:161)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
android.os.Handler.handleCallback(Handler.java:587)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
android.os.Handler.dispatchMessage(Handler.java:92)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
android.os.Looper.loop(Looper.java:123)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
android.app.ActivityThread.main(ActivityThread.java:4627)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
java.lang.reflect.Method.invokeNative(Native Method)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
java.lang.reflect.Method.invoke(Method.java:521)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
com.android.internal.os.ZygoteInit
$MethodAndArgsCaller.run(ZygoteInit.java:871)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:629)
01-27 10:13:07.034: ERROR/AndroidRuntime(11127): at
dalvik.system.NativeStart.main(Native Method)
01-27 10:13:07.053: INFO/(2472): dumpmesg > /data/log/
dumpstate_app_error.log
01-27 10:13:07.053: WARN/ActivityManager(2472): Force finishing
activity com.angrydoughnuts.android.alarmclock/.ActivityAlarmClock
01-27 10:13:07.088: INFO/dumpstate(11709): begin
01-27 10:13:09.600: WARN/PowerManagerService(2472): Timer 0x3->0x3|0x0
01-27 10:13:22.420: DEBUG/VoldCmdListener(2357): asec list
01-27 10:13:22.424: DEBUG/VoldCmdListener(2357):
CommandListener::AsecCmd::runCommand -> com.rovio.angrybirds-1
01-27 10:13:23.918: INFO/dumpstate(11709): done
01-27 10:13:24.100: WARN/ActivityManager(2472): Activity pause timeout
for HistoryRecord{48592c58
com.angrydoughnuts.android.alarmclock/.ActivityAlarmClock}
01-27 10:13:24.245: WARN/ActivityManager(2472): Launch timeout has
expired, giving up wake lock!
01-27 10:13:24.245: WARN/ActivityManager(2472): Activity idle timeout
for HistoryRecord{48592c58
com.angrydoughnuts.android.alarmclock/.ActivityAlarmClock}
01-27 10:13:24.323: INFO/DBG_WSS_DM(11041): [wssTelephonyData.java
Line:131] getInstance PHONE_TYPE_GSM
01-27 10:13:26.370: VERBOSE/InputDevice(2472): ID[0]=0(0) Dn(0=>1)
01-27 10:13:26.374: VERBOSE/WindowManager(2472): Dsptch >
Window{483f0d70 Tyvärr! paused=false}
01-27 10:13:26.588: DEBUG/BatteryService(2472): update start
01-27 10:13:26.596: DEBUG/BatteryService(2472): updateBattery level:63
scale:100 status:2 health:2 present:true voltage: 3958 temperature:
300 technology: Li-ion AC powered:false USB powered:true icon:17302171
01-27 10:13:26.608: INFO/StatusBarPolicy(2472): BAT. status:2 health:2
01-27 10:13:26.719: VERBOSE/WindowManager(2472): Dsptch >
Window{483f0d70 Tyvärr! paused=false}
01-27 10:13:26.719: VERBOSE/InputDevice(2472): ID[0]=0(0) Up(1=>0)
01-27 10:13:26.725: INFO/Process(11127): Sending signal. PID: 11127
SIG: 9
01-27 10:13:26.745: WARN/InputManagerService(2472): Window already
focused, ignoring focus gain of:
com.android.internal.view.IInputMethodClient$Stub$Proxy@483f1218
01-27 10:13:26.850: INFO/ActivityManager(2472): Process
com.angrydoughnuts.android.alarmclock (pid 11127) has died.
01-27 10:13:26.850: WARN/ActivityManager(2472): Scheduling restart of
crashed service
com.angrydoughnuts.android.alarmclock/.AlarmClockService in 5000ms
01-27 10:13:26.854: INFO/WindowManager(2472): WIN DEATH:
Window{483497c8 com.angrydoughnuts.android.alarmclock/
com.angrydoughnuts.android.alarmclock.ActivityAlarmClock paused=false}
01-27 10:13:29.721: WARN/PowerManagerService(2472): Timer 0x3->0x3|0x0
01-27 10:13:31.780: DEBUG/dalvikvm(6879): GC_EXPLICIT freed 2254
objects / 753104 bytes in 178ms
01-27 10:13:31.784: DEBUG/NativeCrypto(6879): Freeing OpenSSL session
01-27 10:13:31.877: INFO/ActivityManager(2472): Start proc
com.angrydoughnuts.android.alarmclock for service
com.angrydoughnuts.android.alarmclock/.AlarmClockService: pid=11730
uid=10095 gids={}
01-27 10:13:32.038: INFO/global(2472): Default buffer size used in
BufferedInputStream constructor. It would be better to be explicit if
an 8k buffer is required.
01-27 10:13:32.065: INFO/global(2472): Default buffer size used in
BufferedInputStream constructor. It would be better to be explicit if
an 8k buffer is required.
01-27 10:13:34.252: WARN/ActivityManager(2472): Activity destroy
timeout for HistoryRecord{48592c58
com.angrydoughnuts.android.alarmclock/.ActivityAlarmClock}

=======================================

[Craig G]

It looks like your ringtones database may have been corrupted. Did
you recently (re)install a bunch of ringtones? You can try resetting
the tone that you chose as your wakeup sound in the alarm klock app.
This will reset the URI that alarm klock uses to access the ring tone
to whatever the new location of the media file is. The app is
supposed to fall back to a well-known sound if the primary alert isn't
available, but it looks like this is more complicated than a simple
'file not found' error...

Let me know if that helps,
Craig

> Window{483f0d70 Tyvärr! paused=false}

> 01-27 10:13:26.588: DEBUG/BatteryService(2472): update start
> 01-27 10:13:26.596: DEBUG/BatteryService(2472): updateBattery level:63
> scale:100 status:2 health:2 present:true voltage: 3958 temperature:
> 300 technology: Li-ion AC powered:false USB powered:true icon:17302171
> 01-27 10:13:26.608: INFO/StatusBarPolicy(2472): BAT. status:2 health:2
> 01-27 10:13:26.719: VERBOSE/WindowManager(2472): Dsptch >

> Window{483f0d70 Tyvärr! paused=false}