Daylight-saving changes can alter the local clock while the underlying programme instant remains well defined by its timezone information. A fixed manual EPG shift may work for part of the year and become wrong after the clock change. Use the correct named device timezone and review any old manual offsets.
Distinguish a timezone from a fixed offset
A named timezone can carry daylight-saving rules; a fixed UTC offset cannot describe every seasonal change by itself. A device configured to the wrong region may show the current clock correctly for a while and still handle a future transition incorrectly.
Inspect dates on both sides of the change
Compare guide entries before and after the transition. If only the later entries move, the source may have generated future listings using an inappropriate offset. Keep the affected dates in the support report.
Avoid correcting the clock to fix one app
Changing the whole device clock can affect certificates, reminders and other applications. A guide-specific problem should be addressed at the guide or player setting when possible. Restore the correct system time before further diagnosis.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
A manual +1-hour correction made in winter can become unnecessary in summer. Leaving it enabled may produce a guide that is one hour ahead after the seasonal change.
Questions about this topic
Can a correct clock coexist with a wrong timezone setting?
Yes, especially before the next seasonal transition.
Should I alter the system date for one guide?
No. Keep system time accurate and investigate the guide handling.
