Tickets :: [#12741] EAS 14.x and ActiveSync on Android

6.0.0-alpha14

6/24/25

Summary	EAS 14.x and ActiveSync on Android
Queue	Synchronization
Queue Version	Git master
Type	Bug
State	Not A Bug
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	cne (at) ruhrverband (dot) de
Created	10/07/2013 (4278 days ago)
Due
Updated	10/16/2013 (4269 days ago)
Assigned	10/07/2013 (4278 days ago)
Resolved	10/08/2013 (4277 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/16/2013 10:45:50 AM	cne (at) ruhrverband (dot) de	Comment #13	Reply to this comment
This is very obscure. I go on testing with resetted Smartphones. [Show Quoted Text - 22 lines][Hide Quoted Text] Hi! Both the device log and the horde synclog show the event being added once. Looks like a bug in your client. We have the same problem f.e. on these devices: SAMSUNGGTI9300, SAMSUNGGTI9082 and SAMSUNGGTI9505. Phps. a Samsung bug? Perhaps it's related to the fact that the event spans midnight, utc? I don´t know. The time is okay for the two events on the Handy (GMT+2:00). Like it is on H5 (CEST). I can´t believe, we are alone with this problem. There are two installations of H5 (on CentOS6 with pear), two different databases, same problem with EAS14. I run a very similar setup - CentOS 6, pear Horde, AS 14.1. My Samsung S4 (GT-I9500) running 4.2.2 does not exhibit this behaviour.

10/16/2013 02:44:03 AM	simon (at) simonandkate (dot) net	Comment #12	Reply to this comment
[Show Quoted Text - 18 lines][Hide Quoted Text] Hi! Both the device log and the horde synclog show the event being added once. Looks like a bug in your client. We have the same problem f.e. on these devices: SAMSUNGGTI9300, SAMSUNGGTI9082 and SAMSUNGGTI9505. Phps. a Samsung bug? Perhaps it's related to the fact that the event spans midnight, utc? I don´t know. The time is okay for the two events on the Handy (GMT+2:00). Like it is on H5 (CEST). I can´t believe, we are alone with this problem. There are two installations of H5 (on CentOS6 with pear), two different databases, same problem with EAS14. I run a very similar setup - CentOS 6, pear Horde, AS 14.1. My Samsung S4 (GT-I9500) running 4.2.2 does not exhibit this behaviour.

10/10/2013 01:46:52 PM	cne (at) ruhrverband (dot) de	Comment #11	Reply to this comment
Do all events get doubled? Is there a pattern to those that do, to those that don't? Without some sort of information like this, it's unlikely I'll be able to help further since I can't reproduce. After the reset, everything looks good. After that, only new events get doubled. And this only after the first synchronisation. I just tested it on a HTC hero. Everything is fine.

10/09/2013 02:05:30 PM	Michael Rubinsky	Comment #10	Reply to this comment
Hi! Both the device log and the horde synclog show the event being added once. Looks like a bug in your client. We have the same problem f.e. on these devices: SAMSUNGGTI9300, SAMSUNGGTI9082 and SAMSUNGGTI9505. Phps. a Samsung bug? The only Samsung device I have is a Galaxy Nexus, which runs on a "pure" android ROM. This works fine for me with all versions of EAS, including 14.0 and 14.1. Perhaps it's related to the fact that the event spans midnight, utc? I don´t know. The time is okay for the two events on the Handy (GMT+2:00). Like it is on H5 (CEST). All times are sent as GMT to the device, so my point was that maybe since the GMT time of the event covers a date transition, this might be a trigger for the Samsung bug. Obviously just a guess as I can't look at ht proprietary source code of Samsung's implementation. I can´t believe, we are alone with this problem. There are two installations of H5 (on CentOS6 with pear), two different databases, same problem with EAS14. I don't see this issue on the 8 physical test devices I have, Outllook 2013, Windows 8 Mail, or any of the numerous third party clients I have available to test. Do all events get doubled? Is there a pattern to those that do, to those that don't? Without some sort of information like this, it's unlikely I'll be able to help further since I can't reproduce.

10/09/2013 10:31:33 AM	cne (at) ruhrverband (dot) de	Comment #9	Reply to this comment
I check it out with other devices to find out if it is a Samsung special.

10/09/2013 10:16:27 AM	cne (at) ruhrverband (dot) de	Comment #8	Reply to this comment
Hi! Both the device log and the horde synclog show the event being added once. Looks like a bug in your client. We have the same problem f.e. on these devices: SAMSUNGGTI9300, SAMSUNGGTI9082 and SAMSUNGGTI9505. Phps. a Samsung bug? Perhaps it's related to the fact that the event spans midnight, utc? I don´t know. The time is okay for the two events on the Handy (GMT+2:00). Like it is on H5 (CEST). I can´t believe, we are alone with this problem. There are two installations of H5 (on CentOS6 with pear), two different databases, same problem with EAS14.

10/08/2013 03:58:00 PM	Michael Rubinsky	Comment #7 State ⇒ Not A Bug	Reply to this comment
Both the device log and the horde synclog show the event being added once. Looks like a bug in your client. Perhaps it's related to the fact that the event spans midnight, utc?

10/08/2013 02:32:01 PM	cne (at) ruhrverband (dot) de	Comment #6 New Attachment: SEC-H5.txt.tar.gz	Reply to this comment
And from horde .. [Show Quoted Text - 14 lines][Hide Quoted Text] Is attached. (One user) This is the horde log. I need the sync log: To enable debugging, see instructions contained in the ActiveSync section of Horde's configuration. Also, see http://wiki.horde.org/ActiveSync for more details. Debugging should not be enabled on a production server, Attach/post only the portion of the log that directly deals with the problem reported (it may be simplest to clear the log file and then perform the event that causes the error).

10/08/2013 02:31:20 PM	cne (at) ruhrverband (dot) de	Comment #5 New Attachment: emaillog-Samsung.txt.tar.gz	Reply to this comment
Sorry. [Show Quoted Text - 12 lines][Hide Quoted Text] Is attached. (One user) This is the horde log. I need the sync log: To enable debugging, see instructions contained in the ActiveSync section of Horde's configuration. Also, see http://wiki.horde.org/ActiveSync for more details. Debugging should not be enabled on a production server, Attach/post only the portion of the log that directly deals with the problem reported (it may be simplest to clear the log file and then perform the event that causes the error).

10/07/2013 02:54:35 PM	Michael Rubinsky	Comment #4	Reply to this comment
Is attached. (One user) This is the horde log. I need the sync log: To enable debugging, see instructions contained in the ActiveSync section of Horde's configuration. Also, see http://wiki.horde.org/ActiveSync for more details. Debugging should not be enabled on a production server, Attach/post only the portion of the log that directly deals with the problem reported (it may be simplest to clear the log file and then perform the event that causes the error).

10/07/2013 02:43:56 PM	cne (at) ruhrverband (dot) de	Comment #3 New Attachment: horde.log.tar.gz	Reply to this comment
Hi Michael, Works fine here on my Samsung Galaxy Nexus. That are good news. So this might be no bug?! Would need to see a sync log during an attempt that results in the doubled entry. Is attached. (One user) For some Android Apps (like "Tasks & Notes" from UniqTec), EAS 14.x is necessary to sync Notes. It would be necessary for any app that syncs notes, as this wasn't added to the protocol until EAS 14. Nice information :)

10/07/2013 02:14:19 PM	Michael Rubinsky	Comment #2 State ⇒ Feedback Assigned to Michael Rubinsky	Reply to this comment
Works fine here on my Samsung Galaxy Nexus. Would need to see a sync log during an attempt that results in the doubled entry. For some Android Apps (like "Tasks & Notes" from UniqTec), EAS 14.x is necessary to sync Notes. It would be necessary for any app that syncs notes, as this wasn't added to the protocol until EAS 14.

10/07/2013 10:52:08 AM	cne (at) ruhrverband (dot) de	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ EAS 14.x and ActiveSync on Android Queue ⇒ Synchronization Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
Perhaps this is not a horde Problem?!: If there´s a new appointment in H5 and $conf[activesync][version] (EAS) is bigger than 12.1, the new appointments double on Samsung Android calendars after the first sync. New dates on the Android doesn´t sync. back to H5. Resetting ActiveSync devices on H5 deletes all double entries until the next sync. For some Android Apps (like "Tasks & Notes" from UniqTec), EAS 14.x is necessary to sync Notes.