There's a few ways to auto correct for all just fine... for those it does affect. I'm just no app programmer.
I do that, but only because I am in timezone zero. What I am actually doing is not using daylight savings time, but here it is much easier to describe that as "using GMT". As long as you know it is not using DST then it is always accurate, even at 1:30AM on the days that DST starts/stops, and the description "using GMT" also makes sense when you cross a timezone border every day on your commute to work and back.
Not a programmer here either, but it's not as simple as you may think. In the more-or-less recent past a few States changed the date when they screwed with the clocks. GPS doesn't have that kind of signaling function and already-installed FW would be in error after that. There's at least 5 different days involved world-wide IIRC, and crossing a 'political border' like a US State line can go from DST to standard time as can national or time-zine borders. Cell phones have the capability since they always have some geo-location happening and a constant connection to a tower signal. Much the same for the internet. These have plenty of processor power and data space which dashcams less of, and dashcams lack that kind of real-time connectivity. You don't have to be a programmer to understand what things are capable of or how they work
If it was all done properly, then the camera would just use UTC, as mine does since I leave it on GMT+0, and the conversion from UTC time to displayed time would be done on display, so when playing on Dashcam Viewer, or on the mobile app, it would could give the local time for the place it is viewed in, or DST, or UTC, as configured in the device used to view it, and/or configured in the display app. Unfortunately it is not done that way, mainly because people like the time to be embedded in the video as part of the image, so it has to be converted live. This causes several problems, including the phone synchronising time incorrectly when the phone is set to DST and the camera set to standard time, even worse if you cross a border and your phone automatically adds an hour, then argues with the camera GPS time because the camera is now one timezone out - problems that would all be solved if the camera only used UTC!
Automatically displaying local time with DST correctly on any GPS device is not actually possible without an internet connection, since the governments of individual countries can and do occasionally change the rules on what time zones and DST to use, some countries like Australia even have half hour adjustments to timezones, and of course the timezone borders are not simple straight lines and also move occasionally, they can even have islands of one timezone within another timezone. Best to leave it to the display device, which quite likely does have an internet connection with access to the rules, or at least frequent updates... But that is not what the dashcam customers want!
Well, one way is a rebuild of the GPS for those that have them since a standard directional gps handles time updates just fine without internet. At least the few I've owned.
No worries, was just curious if the parking guard for you, if set to 12 hr. Defaults to 3 like it does for me, was not saying you had to leave it. But ya, I guess depending where some people live, times an issue for some while others it's not.
Could it be your phone putting it 1 hour out when you run the app and it does a time sync ? Is the default time zone on the phone also-4?
I suppose the current time zone shall be set to GMT-5 for Pennsylvania.
Please try to update the app version to the newest 3.2.1.
1) That in theory would fix the recorded time stamp but now affect live... and that's a bandaid more than a solution, it tech fixes nothing. But your supposing is wrong... tech speaking.
2) strike two, swing-and-a-miss availability for updates is only 3.2.0 on Android, there is no 3.2.1 available!
While I appreciate that, in terms of fixing at least one of the two things. I would prefer to wait until it's officially released on the Google Play store which I don't mind doing. But I am curious though did you guys just fix that bug or did you add more settings because it seems weird to also jump from 8 hours to 12 hours etc.