0xRustlang
commented
6 months ago Alternative suggestion: #36 and #37
Open 0xRustlang opened 6 months ago
0xRustlang
commented
6 months ago Alternative suggestion: #36 and #37
RokeJulianLockhart
commented
6 months ago https://github.com/FossifyOrg/Clock/issues/30#issue-2201482754
Per https://source.android.com/docs/core/permissions/timezone-rules#timezone-apex and https://community.ntppool.org/t/daylight-saving-time/2830/4, it does indeed appear that < AOSP v10 devices need a DST override. However, since https://gs.statcounter.com/os-version-market-share/android/mobile-tablet/worldwide reports that < v10 is < 50% of the overall market share, I wonder whether this is worth the complexity. If it is, allow the user to utilize the system-provided data should they want to.
0xRustlang
commented
6 months ago Per https://source.android.com/docs/core/permissions/timezone-rules#timezone-apex and https://community.ntppool.org/t/daylight-saving-time/2830/4, it does indeed appear that < AOSP v10 devices need a DST override. However, since https://gs.statcounter.com/os-version-market-share/android/mobile-tablet/worldwide reports that < v10 is < 50% of the overall market share, I wonder whether this is worth the complexity. If it is, allow the user to utilize the system-provided data should they want to.
That's odd. I've seen many android < 13 devices that hasn't updated their Timezone.
BTW, How much statcounter is reliable? Because that's only one of many statistics providers for websites and its pixels or javascript codes isn't exist in many websites I think.
Thanks.
RokeJulianLockhart
commented
6 months ago https://github.com/FossifyOrg/Clock/issues/30#issuecomment-2032416132
@0xRustlang, I've no actionable information regarding the quality of StatCounter's statistics. I've been unable to locate any website with more (or even comparably) comprehensive data for this topic regardless.
Checklist
Feature description
Hello
In recent years, many countries including many ones in Europe had stopped switching to Daylight Saving Time (DST) A.K.A Summer Time.
Those who have old devices that won't get updates (and maybe use them as an alarm clock or other use cases) cannot force the phone to use a custom Time-Zone and if they set the Time manually, still that will be rationally irrelevant.
Let's say someone's phone in Netherlands will switch to summer time automatically (this will happen even if that person have set the time to not sync with NTP servers)
So, the Timezone of his phone will become "GMT + 2" instead of 1.
Then if that person changes the time manually, it will be rationally incorrect for websites and services and some time critical services.
Because their time zone is one hour ahead but their clock has been set manually to one hour less.
So they have no choice other than let the time of their phone change like previous years.
this can get resolved with using UTC mode but those that are in places that have half hour in their Timezone will have trouble as setting time based on UTC doesn't provide UTC + 1:30 and such.
There is another issue and that is because your app uses the database of the phone for World clock, it shows the clock of some other countries also incorrectly as the phone isn't updated to include their new DST stopping state.
Your clock app also shows the time incorrectly and also shows the World Clock also incorrectly.
If it is possible, please update and use an built-in database of DST usage so people can at least rely on your app for clock, alarm and World clock as they can't rely on their phone anymore.
Thank you so much. Regards.
Why do you want this feature?
Already wrote above.
Additional information
There is no fossify release yet so this is a SMT issue.