Closed izivkov closed 1 year ago
I had noticed that the app was setting UTC time zone to an hour behind what it should be, when the local time was set to 'London'. I assume this is the same problem? (This was since the daylight saving change from BST to UTC at the end of October)
Yes, it is the same issue. If you are getting it from f-droid, they take a week or so to update. You can immediately get version 10.7 with the fix from the Google Play store, or build from source code.
On Mon., Nov. 6, 2023, 1:09 p.m. geebotron, @.***> wrote:
I had noticed that the app was setting UTC time zone to an hour behind what it should be, when the local time was set to 'London'. I assume this is the same problem?
— Reply to this email directly, view it on GitHub https://github.com/izivkov/CasioGShockSmartSync/issues/52#issuecomment-1795774558, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7M37U5MXMGTQAPKDCAQ2LYDERVXAVCNFSM6AAAAAA63POHHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJVG43TINJVHA . You are receiving this because you authored the thread.Message ID: @.***>
Haha, it's ok. I'll wait for the fix to hit the f-droid repo.
My brain can just about cope with the math involved to calculate the correct time, in the interim. 😌
@geebotron , BTW, let us know if it works for you after the update.
Thanks.
👍
Remember, on F-DROID is v10.8.
Regards
On Mon, Nov 6, 2023 at 4:04 PM geebotron @.***> wrote:
Haha, it's ok. I'll wait for the fix to hit the f-droid repo.
My brain can just about cope with the math involved to calculate the correct time, in the interim. 😌
— Reply to this email directly, view it on GitHub https://github.com/izivkov/CasioGShockSmartSync/issues/52#issuecomment-1796430847, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7M37TQROB6NHWJUZN3DVLYDFGFPAVCNFSM6AAAAAA63POHHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJWGQZTAOBUG4 . You are receiving this because you authored the thread.Message ID: @.***>
@geebotron
The app is on F-DROID now. It is labelled v10.7, but this version addresses this issue.
Yes, this version appears to correct the problem. Thanks.
Ah... Spoke too soon... The 'short press' on the lower left button seems to have lost its function to set the time in then new version. There seems to be a connection to the watch, but the watch never replies with 'ok' and the time is unaltered. The main settings page in the app pushes the time to the watch correctly, though.
@geebotron
OK, I fixed it and will be available shortly as version 11 on both F-DROID and the play store.
In the last week I made some massive changes to the library which this project uses, to improve performance further. I missed a couple of things.
Thanks for your feedback.
This has been fixed.
The issue has been fixed in version 10.7 (v10.8 on F-Droid). Apologies for any inconvinces.