Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content
Commit ccbfdb90 authored by Neil Fuller's avatar Neil Fuller
Browse files

Take into account obsoleted zone IDs

Android holds information about when a time zone stopped/will stop
being relevant. There are numerous countries that have simplified
their time zones over time. Zone IDs that differed in the past still
exist in the data even if they have the same rules past a point in
time. Android's "notUsedAfter" data indicates that point in time.

This change will allow time zone detection in future to take into
account the difference between countries that have settled on a single
effective zone, and those where there are multiple zones that happen
to share the same offset at a given time. The "single effective zone"
case is a stronger signal.

Specific examples include Germany, where the data tells us
that it has two zones but it has had one effective time zone since
1980. The US has multiple zones, and even two that share the same
offset for 6 months of the year (America/Denver & America/Phoenix).

The change will not affect the value of CountryResult.allZonesHaveSameOffset
which is the only signal used in the code right now.

Bug: 139928367
Test: atest com.android.internal.telephony.NitzStateMachineImplTest
Test: atest com.android.internal.telephony.TimeZoneLookupHelperTest
Change-Id: Idf16bfedb359e52657360dd4b60e81573bf74179
parent 8473fe54
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment