Username: acooper
Device: Dopod 838 Pro with Windows Mobile 5
Am based in Australia (GMT +10) and appear to have correct settings
loaded for both device and Goosync account. However all calendar
entries are appearing 10 hours earlier in my advice if loading from
Google Calendar. Entries loaded on Device appear 10 hours later in
Google Calendar. Other than that, syncing beautifully.
Have loaded a test entry on each of the device and Google calendar for
checking purposes. Any help to get what appears to be an excellent
tool up and running much appreciated.
Andrew
I've activated detailed logging for your account.
Please create some new test entries (if you've already synchronised
the others you made) and synchronise these with GooSync.
Once the sync is complete please let me know what the correct time of
each test entry was and also what time they appear at after the sync,
and I'll get the server log files checked.
On Jun 27, 8:07 pm, Stuart - GooSync Support
<stu.etche...@googlemail.com> wrote:
> Hi,
>
> I've activated detailed logging for your account.
>
> Please create some new test entries (if you've already synchronised
> the others you made) and synchronise these with GooSync.
>
> Once the sync is complete please let me know what the correct time of
> each test entry was and also what time they appear at after the sync,
> and I'll get the server log files checked.
>
> On Jun 27, 3:54 am, "acoo...@dstore.com" <acoo...@dstore.com> wrote:
>
> > Hi
>
> > Username: acooper
> > Device: Dopod 838 Pro with Windows Mobile 5
>
> > Am based in Australia (GMT+10) and appear to have correct settings
> > loaded for both device and Goosync account. However all calendar
> > entries are appearing10hours earlier in my advice if loading from
> > Google Calendar. Entries loaded on Device appear10hours later in
We've recently identified a problem on the Windows Mobile devices with
regards to the GMT +10 (Sydney) time zone.
Selecting this time zone causes the GooSync client to detect it as
just GMT and not GMT +10.
We're working with the client developers to determine whether this is
a bug in the GooSync client or a problem with the actual time zone
information on the device.
Once we have more information we will let our users know.
On Jul 19, 5:14 am, Stuart - GooSync Support