+ Reply to Thread
Results 1 to 5 of 5

Thread: Missing alarms DJO ('Failed to find alarm' in logfile) ?

Hybrid View

  1. #1
    Senior Member
    Join Date
    Nov 2011
    Posts
    136

    Missing alarms DJO ('Failed to find alarm' in logfile) ?

    Anybody else experiencing missing alarms in DJO ? Seems to have become worse in the later beta's, not entirely sure. I did notice messages like 'Failed to find alarm' with a number in the logfiles which match the times the alarms should have gone off. Interesting is that the number it refers to seems to about an old alarm, well *I* find such things interesting anyway

    Problem seems to occur with both Tasks and Events, can't see much difference between those two.

    I do run Android5 but alarm issues did occur with 4.4 as well so that's probably not the cause?
    -Frans

    Samsung Galaxy s7, stock rom 8,0, not-rooted
    DJO 4.4.5 (1069) , CompanionLink 8018
    Outlook 2016 (32bit), sync via DejaCloud (native sync Contacts only)

  2. #2
    Senior Member DJOCTO's Avatar
    Join Date
    Apr 2010
    Posts
    2,210
    Frans, Please try the beta we posted today. I think the Alarms are more stable for Lollipop.

  3. #3
    Senior Member
    Join Date
    Nov 2011
    Posts
    136
    Quote Originally Posted by DJOCTO View Post
    Frans, Please try the beta we posted today. I think the Alarms are more stable for Lollipop.
    Will give that one a try, thanks!
    -Frans

    Samsung Galaxy s7, stock rom 8,0, not-rooted
    DJO 4.4.5 (1069) , CompanionLink 8018
    Outlook 2016 (32bit), sync via DejaCloud (native sync Contacts only)

  4. #4
    Senior Member
    Join Date
    Nov 2011
    Posts
    136
    Just missed another (event) alarm even on the newest beta
    What I'm seeing in logfile is that on the exact time the alarm should trigger an event is received for the OLD alarm. I'm wondering, what if anything happens when two android alarm events are scheduled for the same app for the exact same time? 'cos the new alarm does look to have been set ok, it's just the only an event for the old one is received?
    Hmmm.. on a succesfull alarm I notice (earlier in logfile) that that event triggered two 'onReceived' events, within the same second. One for the old event-id and one for the correct id, so one was dismissed but the 2nd correctly showed that alarm.

    For my missed event, only one event was received it seems, which was the old id which wasn't found
    Look;
    (can send you full file if you want)

    15828) 12-11 17:30:52 AlarmDatabase: addAlarm() succeeded (324658) Eten ouders di/do [2014-12-11 17:55:00]
    15864) 12-11 17:30:52 AlarmDatabase: removeAllAlarms41() removing AlarmID=324658
    15867) 12-11 17:30:52 AlarmDatabase: Event Alarm: Eten ouders di/do [2014-12-11 17:55:00] [ID=4187] [AlarmID=324658]

    I don't know why DJO recreates all those alarms but it looks like it removes them all and then creates the ones needed again, with new id's ? See below;

    15903) 12-11 17:30:57 AlarmDatabase: deleteAllAlarms() succeeded
    15904) 12-11 17:30:57 AlarmDatabase: addAlarm() succeeded (324677) Eten ouders di/do [2014-12-11 17:55:00]

    but it then receives a broadcast only for the old alarm-id (324658 vs 324677)?

    16186) 12-11 17:55:00 AlarmBroadcast: onReceive41()
    16187) 12-11 17:55:00 Log: onReceive41() START component: ComponentInfo{com.companionlink.clusbsync/com.companionlink.clusbsync.EventAlarm}, uri: content://com.companionlink.clusb/alarm/324658, action: actionAlarm, type: <no type>, categories: <no categories>, extras: (extraAlarmTime=1418316900000) (extraAlarmType=2) (extraAlarmID=324658) (extraAlarmPersistent=60000) (android.intent.extra.ALARM_COUNT=1) (extraAlarmCount=0)
    16188) 12-11 17:55:00 AlarmBroadcast: onReceive41() Failed to find alarm (ID=324658)
    16189) 12-11 17:55:00 AlarmBroadcast: Dismissing alarm notification (AlarmID=324658)
    ...
    Below is me manually tapping the scheduled event line in DejaToday, which shows the event-alarm window. Looks like 324677 was the correct alarm but for whatever reason no alarm-event was received for it?

    16211) 12-11 17:59:41 EventViewActivity: Activity opening due to alarm notification being tapped
    16214) 12-11 17:59:43 EventViewActivity: onDismissAlarm()324677
    16215) 12-11 17:59:43 AlarmBroadcast: Dismissing alarm notification (AlarmID=324677)
    16216) 12-11 17:59:43 AlarmDatabase: dismissEvent(324677, 4187, 870455) dbvalid = true
    16217) 12-11 17:59:43 AlarmDatabase: removeAlarm41() removing AlarmID=324677
    16218) 12-11 17:59:43 AlarmBroadcast: Dismissing alarm notification (AlarmID=324677)
    16219) 12-11 17:59:43 AlarmDatabase: deleteAlarm(324677) succeeded
    -Frans

    Samsung Galaxy s7, stock rom 8,0, not-rooted
    DJO 4.4.5 (1069) , CompanionLink 8018
    Outlook 2016 (32bit), sync via DejaCloud (native sync Contacts only)

  5. #5
    Senior Member
    Join Date
    Nov 2011
    Posts
    136
    Changed 'ring alarm' to 'ring in deja office' (it was 'ring in deja office and calendar') but that only seems to make it worse. Also changed alarm-style back to v2.0 as I prefer that.
    Missed two alarms today, one calendar and one task... sigh.

    Quick review of logfile for the most recent missed event showed this curious line;

    28806) 12-13 18:41:52 AlarmDatabase: addAlarm() succeeded (326058) Take1 [2014-12-13 17:40:00]

    now... is that an alarm being added over an hour *after* it is set to ring? (djo did add it prior to that as well, numerous times but this was the last line I found about this missed event)

    I *need* working alarms and so far reliability seems to go down instead of up
    -Frans

    Samsung Galaxy s7, stock rom 8,0, not-rooted
    DJO 4.4.5 (1069) , CompanionLink 8018
    Outlook 2016 (32bit), sync via DejaCloud (native sync Contacts only)

+ Reply to Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts