Sorry, I did a "reload" sync - no difference. I also put some new entries in Gcal and did a sync - still no difference.
I also did a slow sync - again no difference. I then did the formal "exit" of Goosync client, change/reset zone process again followed by a slow sync but no difference in sync outcome... Hope there is some solution... Regards, Don On Jul 17, 8:53 pm, Stuart - GooSync Support <[EMAIL PROTECTED]> wrote: > Hi, > > I've checked the GooSync "sync time" issue and it appears to be a bug > in the client that doesn't show the correct sync time if you select > the GMT +10 time zone. I'll forward this to the client developer so > they can investigate. > > With regards to the actual sync: do new entries synchronise to the > device correctly? Any events that have already synchronised > incorrectly may not be corrected by changing the time zone for the > GooSync client. You would need to force the events back down to the > device so that the GooSync client can save them using the correct time > zone. > > The easiest way to do this is to perform a reload device > synchronisation. Please note that this will remove all entries from > the device first before re-sending the Google data. Therefore if your > device contains more recent information this should not be performed. > > If you are unable to perform a reload then a slow sync should be > sufficient. > > On Jul 17, 11:05 am, Don <[EMAIL PROTECTED]> wrote: > > > Hi Stuart, thanks for your suggestion - it seemed a possibility but > > was not the cause of my problem. > > > I exited as you suggested, then did a soft reset, then set zone to +1 > > GMT, confirmed, then set it back to +10, then resynced. > > > Same result, unfortunately. > > > The client screen shows the sync time as -1 GMT - any clues from that > > fact? > > > Any other suggestions? Does my log file provide any clues? > > > Hope there is some solution... > > > Regards, Don > > > Don > > > On Jul 17, 12:33 am, Stuart - GooSync Support > > > <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > We have seen problems with the GooSync client retaining "old" time > > > zone information if these details are changed while the client is > > > still running in memory (i.e. the client was not shut down using the > > > Exit option in the menu). > > > > I suggest closing down the client (select Exit from the client menu) > > > and then change your time zone again (you may need to change it to > > > something other than your native time zone and then select the correct > > > one again to ensure the settings are recognised correctly). > > > > Once done start the GooSync client again and sync once more. > > > > On Jul 13, 6:04 am, Don <[EMAIL PROTECTED]> wrote: > > > > > Have a HP 6828 WM5 which was working fine with GooSync until I had to > > > > do a "hard reset" necessitating resinstallation of the Goosync > > > > client. My syncs are now out by 10hrs - the timezone difference for > > > > Oz. > > > > > - I have installed the MS daylight saving patch > > > > - deleted and reselected the HP 6828 from my account > > > > - double checked my timezone on my PC, on 6828, in Google, and in > > > > Goosync > > > > > Syncs are 10hrs out and interestingly, the sync time shown in the > > > > Goosync client screen is also out by 11Hrs. > > > > > Any ideas please? > > > > > Login is DonSweeney > > > > > Don --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GooSync" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/goosync?hl=en -~----------~----~----~----~------~----~------~--~---
