1. Introducing Channels - a new way to chat with other Android users!
    Dismiss Notice

Alarm Clock gets killed

Last Updated:

  1. apolloFER

    apolloFER Well-Known Member This Topic's Starter

    Nov 22, 2009
    Likes Received:
    Hi everybody... A proud owner of Samsung Galaxy (Cupcake).

    Anyway, lately I've been having problems with the default Alarm Clock application. The problem is pretty well described here:
    [android-developers] Re: exit button - or not?: msg#01534 AndroidDevelopers
    Anyway, what happens is that Android acts as a task manager when memory gets tight. I've disabled my Advanced Task Manager to test this behaviour. When I start loading apps (Gmail, Browser, Camera...) and then check the task manager, I see these new apps have eaten up my memory and as a result, OS has killed my "Alarm Clock". This is quite disturbing since I always used my mobile as an alarm clock and I really like Android's alarm clock. And I don't want to be forced to check if my Alarm Clock process is running everytime I go to sleep.
    I haven't tried reseting the phone yet because of my apps and setting. I think I'll use My Backup Pro and save the settings and apps and then try reseting. But I've already reset my phone after a firmware upgrade.
    Any ideas how to fix this issue. I though about using a different alarm app, but the default integrates with Weather Widget (tap on the clock opens the alarm clock settings).

    P.S. I checked the log and here's the important part about alarm clock:
    Code (Text):
    1. 11-23 00:25:28.937 I/ActivityManager( 1052): Start proc com.almondmendoza.monBattery for service com.almondmendoza.monBattery/.BatteryService: pid=5140 uid=10042 gids={}
    2. 11-23 00:25:29.097 I/WindowManager( 1052): WIN DEATH: Window{4361aee0 com.android.alarmclock/com.android.alarmclock.AlarmClock paused=false}
    3. 11-23 00:25:29.107 I/ActivityManager( 1052): Process com.android.alarmclock (pid 4718) has died.


Share This Page