tree 57bbd028c1e0b19ea955f62a1aed76bc1a219cc4
parent 2faa1dd0e90271262cd0012d38a1486f8da7efc8
author Neil Fuller <nfuller@google.com> 1568199516 +0000
committer Gerrit Code Review <noreply-gerritcodereview@google.com> 1568199516 +0000

Update git submodules

* Update frameworks/base from branch 'master'
  to 28b12c347c719e7b6f4584e141401ce9f7a2e23f
  - Merge "Track changes to CountryTimeZones API"
  - Track changes to CountryTimeZones API
    
    Track changes to CountryTimeZones.lookupByOffsetWithBias()
    API: the method now takes an extra argument: dstOffsetMillis,
    which is unused in this case.
    
    This commit also improves the parameter names to be more descriptive.
    
    Bug: 139091367
    Test: treehugger
    Change-Id: I2090965640bb389ea41bde460f380f9ea8a6b176
    

* Update frameworks/opt/telephony from branch 'master'
  to 4e5522ba8b444b65ffd5eba832cc705f1f2f704d
  - Merge "Track changes in libcore's API"
  - Track changes in libcore's API
    
    Track changes in libcore's API lookupByOffsetWithBias().
    
    The method args have been configured so that the behavior should
    stay the same for most cases. Only if the NITZ DST information is
    missing will there be a change, and it should mean better matching
    behavior. See the comment added in the code for more information.
    
    Bug: 139091367
    Bug: 140712361
    Test: treehugger
    Change-Id: I0b9ff076e1d60196477fab404578100eb89c548f
    

* Update libcore from branch 'master'
  to 1379ec47885885a1d66e0bb7b63a1cd6e064ca66
  - Merge "Combine two versions of lookupByOffsetWithBias()"
  - Combine two versions of lookupByOffsetWithBias()
    
    Combine two versions of CountryTimeZones.lookupByOffsetWithBias()
    into a single method. This takes the one marked deprecated that
    takes a boolean and the one that takes an Integer and provides a
    single method that can replace both.
    
    Originally, the intent was to move callers from the boolean version
    to the Integer version but this is likely impossible:
    1) The boolean version is used to provide a public API that takes
    a boolean. It is not reasonable to assume "is DST" means "add one
    hour" to create an Integer value.
    2) The Integer version is not necessarily superior: it makes the
    matching more exact but NITZ signals aren't necessarily correct
    so using this may have a negative affect on time zone detection.
    
    Historically, telephony couldn't tell the difference between
    "NITZ data says the time zone is not using DST" and "NITZ data
    says nothing about DST". This changed a couple of years ago
    when the telephony NitzData class was written. The new method more
    closely models the tri-state of NITZ's states: "local time is DST",
    "local time is not DST" and "No DST info available" with a Boolean.
    It still provides the "DST offset is X" and "DST offset is unknown"
    that was previously available with the Integer version.
    
    The tests associated with the two methods have also been combined,
    extended and changed to use arrays to try to improve readability /
    reduce cruft.
    
    Bug: 139091367
    Bug: 140712361
    Test: atest libcore.libcore.timezone.CountryTimeZonesTest
    Change-Id: I3257ebcb599455438272b24a597a622ecbe099a5