PDA

View Full Version : b881 and 885 - Alarm for recurring tasks is not set correctly on complete



MG111
04-05-2016, 12:22 AM
Hallo!

Since b881 and b885 there is again a problem with alarms for recurring tasks. After the update to b881 the very first occurrence of an alarm of a recurring task leads to the following scenario:

1.) alarm pops up (eg each 1. day of a month, alarm at that day 11 a.m.)
2.) task is being completed
3.) new task is set (eg 2016-05-01), but alarm is being set to the "old" day again (2016-04-01 11:00)

When editing the task series and simply set the alarm to 2016-05-01, the next time, everything works fine ...

Please fix this, as I have a lot of "old" recurring tasks ... completing should never lead to a new instance with an alarm time in the past, should it?

(BTW: http://www.dejaoffice.com/forums/showthread.php?3761-Build-726-recurring-tasks-alarms-still-not-correct&p=16726#post16726)

Michael

DJOCTO
04-06-2016, 09:14 AM
Programmer is looking at this today.

DJOCTO
04-06-2016, 03:07 PM
Programmer thinks this got fixed a couple days ago when we fixed the batch alarms. Give it a try on the beta.

MG111
04-07-2016, 12:45 AM
Programmer thinks this got fixed a couple days ago when we fixed the batch alarms. Give it a try on the beta.

Hm, I'm using b885.

BTW, there's wrong information on http://www.dejaoffice.com/androidapp/

Tap here to download
DejaOffice 3.2.28 (885) BETA
3/23/2016
^^^^^^

DejaOffice 3.2.28 (881) (04/01/16)
^^^


Michael

DJOCTO
04-07-2016, 08:01 AM
I'm not sure offhand but I think this will be DJO 4.1.1 (888) and higher.

MG111
04-07-2016, 08:17 AM
I'm not sure offhand but I think this will be DJO 4.1.1 (888) and higher.

Oh,

b885 = 3.2.28
b886
b887
b888 = 4.1.1

Confusing ... any great change which causes this big jump in the release number (3 --> 4)?

Michael

DJOCTO
04-11-2016, 11:05 AM
1. New UI - The default for the new UI will be in the next store release (4.1)

2. I hate .0 versions. So there will be no 4.0 version. So 4.1 is the first 4 release of DejaOffice. (Just as 1.1 was the first release... not 0.0)

MG111
04-11-2016, 11:50 PM
2. I hate .0 versions. So there will be no 4.0 version. So 4.1 is the first 4 release of DejaOffice. (Just as 1.1 was the first release... not 0.0)

http://www.amazon.com/Zero-Nothing-Young-Math-Books/dp/0690038291 :-)

DJOCTO
04-13-2016, 02:48 PM
Western society was doing fine before we got Arabic numerals. We invented the Dark Ages.

You'll notice we never have a .13 release either. Go figure. (Microsoft also avoided 13 in their internal versioning of Office).

Michael, can you verify that the alarm problem got fixed?

MG111
04-14-2016, 12:12 AM
Michael, can you verify that the alarm problem got fixed?

It seems so. But as it occurred only on the very first alarm after updating, I'm not sure, if there is still any "old" entry. I'll keep you updated.

Michael

MG111
09-02-2016, 01:53 AM
DJOCTO,

the problem occured again serveral (!) times with DejaOffice 4.1.7 (925).

I have some recurring task with a yearly pattern (eg go to dentist, etc). When I completed them today, the next instance in 2017 is being created correctly, except the alarm time, which is being set to 2016 ... :-(

Please have a look at this once again.

Michael

Cecil
09-02-2016, 05:28 AM
There seem to be other problems with 932. Last night alarm due at 22.00 failed to sound after I woke up the phone. It did sound at 6.35 this morning, probably when Marshmallow did one of its scheduled waking moments from Doze.


I have uninstalled 932 and put back 925, I will need to monitor alarm behaviour.

damjang
09-12-2016, 06:35 AM
If this can help I have 931 installed and an recurring alarm changed the sound to a file recorded that I have on internal sd, never chose that sound and also if I want change sound this sound is not listed.

DJOCTO
09-20-2016, 08:39 AM
I sent the issue with annual recurring task time to the programmer today.

MG111
12-23-2016, 06:49 AM
DJOCTO,

same problem again for SERVERAL tasks in the last few days (because the end of year is coming).

Eg "renew SSL certificate" start & alarm 2016-11-30, due 2016-12-31 --> finished today --> next instance 2017-11-30, due 2017-12-31, ALARM 2016-11-30 10:00 *grr*

Same "extend paper list", and so on.

Why isn't it possible, to implement ANY internal check, to avoid alarms being set in the past? This MUST be an error and DO should check, what's happening - maybe open a debug window for a screenshot or save a dump-file for this task ...

Merry x-mas! ;-)

Michael

MG111
02-09-2017, 06:00 AM
*bump* *bump*

MG111
02-22-2017, 10:09 PM
*bump* *bump*

Anyone from DO team reading?

DJOCTO
02-26-2017, 09:05 AM
I re-submitted this.

What helps the most is when the summary is in one post. I think the programmer gets lost trying to review the whole thread looking for an example of what is not right.

MG111
02-27-2017, 11:58 AM
I re-submitted this.

What helps the most is when the summary is in one post. I think the programmer gets lost trying to review the whole thread looking for an example of what is not right.

The very first post (still) describes the whole problem.

Michael

DJOCTO
03-02-2017, 10:25 AM
Ok. Let me try to put this in the style we need.

The style we need is a specific thing our developer can do to see the problem.


Since b881 and b885 there is again a problem with alarms for recurring tasks. After the update to b881 the very first occurrence of an alarm of a recurring task leads to the following scenario:

1.) alarm pops up (eg each 1. day of a month, alarm at that day 11 a.m.)
2.) task is being completed
3.) new task is set (eg 2016-05-01), but alarm is being set to the "old" day again (2016-04-01 11:00)

When editing the task series and simply set the alarm to 2016-05-01, the next time, everything works fine ...

Please fix this, as I have a lot of "old" recurring tasks ... completing should never lead to a new instance with an alarm time in the past, should it?


DJOA-Tasks-Recurring-After first alarm, alarmtime fails to roll forward
1. Create a Task, Recurring, Daily for 5 minutes from now.
2. Let alarm ring
3. Complete task (From notification or from DJO App?)
NOTE: Task will now show for tomorrow
BUG: Alarm still shows for today
NOTE: Alarm should show for tomorrow at the same time as today.
NOTE: After the first time, it works ok.
NOTE: Problem started with B881 so try with prior build should work ok.

Does this sound right? I tried a test. I'll update this report with the results.

Results: I tried this. My alarm rang. I completed it from the notification. I looked at DejaTasks- the new instance is there with the right date on the alarm. I looked at DejaAlarms and it shows with the right date.

Might it be the problem only shows for monthly? Can you help edit my steps so I can see the problem. That's probably what the programmer is running into is that he can't see the problem.

MG111
03-03-2017, 06:40 AM
Ok. Let me try to put this in the style we need.

The style we need is a specific thing our developer can do to see the problem.



DJOA-Tasks-Recurring-After first alarm, alarmtime fails to roll forward
1. Create a Task, Recurring, Daily for 5 minutes from now.

The bug occurs (mostly) for yearly tasks. I had no problem with daily tasks.



2. Let alarm ring
3. Complete task (From notification or from DJO App?)

It does not matter.



NOTE: Task will now show for tomorrow
BUG: Alarm still shows for today

The alarm does not only show for today, but it is fired right now again and the notification pops up (again).

So alarm is set for today, 15 p.m.. Notification pops up. I complete it, new instance of task is being created with start/due next year, but alarm is being set to today, 15 p.m. and notification pops up. When completing, the next instance is being created with start/die the year after next year and alarm next year.



NOTE: Alarm should show for tomorrow at the same time as today.
NOTE: After the first time, it works ok.
NOTE: Problem started with B881 so try with prior build should work ok.

Does this sound right? I tried a test. I'll update this report with the results.

Results: I tried this. My alarm rang. I completed it from the notification. I looked at DejaTasks- the new instance is there with the right date on the alarm. I looked at DejaAlarms and it shows with the right date.

Might it be the problem only shows for monthly? Can you help edit my steps so I can see the problem. That's probably what the programmer is running into is that he can't see the problem.

Maybe you should try yearly recurring tasks. Create one, manually shift the date of the phone, wait for the alarm, complete the task and see, what happens. Then try to shift the date one more year ...

Michael

MG111
04-07-2017, 08:21 AM
*bump* *bump*