[Syncevolution-issues] [Bug 2764] Calendar event alarm synchronization between N900 and Goosync

http://bugs.meego.com/show_bug.cgi?id=2764 --- Comment #5 from jjussi <meego(a)jjussi.com&gt; 2010-06-09 11:51:42 PDT --- GooSync writes: Stuart, Jun 09 16:30 (BST): Hi, The N900 events were sent to us with invalid alarm times (as stated in the replies to your bug report). These alarm times end up being set after the start time of the event. This is not supported in Google so your Google account is setting the alarm as close to the start time as it can (which is 0 minutes before the start time). This particular issue will need to be dealt with by syncEvolution as GooSync has no control over what the device sends to us. With regards to the Google events: the log files show that Google is providing us with the correct alarm information but, for some reason, GooSync is failing to send this information to the device. The only reason GooSync would not send this information to the device is if the sync code could not detect the supported alarm types in the devices DevInfo file. This is a file informing the server of what fields and data the device supports (including the alarm types). If this file doesn't contain any alarm information, or GooSync cannot correctly detect this information, the alarm data will not be sent to the device during the sync process. We have checked the DevInfo file provided by your device and the alarm types are listed but GooSync is unable to detect this. The development team are currently investigating why this may be happening. Once we have more information from the development team we will get back to you. --- Comment #6 from jjussi <meego(a)jjussi.com&gt; 2010-06-09 11:51:42 PDT --- GooSync writes: Stuart, Jun 09 16:30 (BST): Hi, The N900 events were sent to us with invalid alarm times (as stated in the replies to your bug report). These alarm times end up being set after the start time of the event. This is not supported in Google so your Google account is setting the alarm as close to the start time as it can (which is 0 minutes before the start time). This particular issue will need to be dealt with by syncEvolution as GooSync has no control over what the device sends to us. With regards to the Google events: the log files show that Google is providing us with the correct alarm information but, for some reason, GooSync is failing to send this information to the device. The only reason GooSync would not send this information to the device is if the sync code could not detect the supported alarm types in the devices DevInfo file. This is a file informing the server of what fields and data the device supports (including the alarm types). If this file doesn't contain any alarm information, or GooSync cannot correctly detect this information, the alarm data will not be sent to the device during the sync process. We have checked the DevInfo file provided by your device and the alarm types are listed but GooSync is unable to detect this. The development team are currently investigating why this may be happening. Once we have more information from the development team we will get back to you. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug.