Skip to content
Commit 10158975 authored by Neil Fuller's avatar Neil Fuller Committed by Almaz Mingaleev
Browse files

Prepare to make time detection more configurable

Prepare to make time detection more configurable. This change introduces
an idea of origin ordering ("priority") so that different partners and
form factors can modify the previously hardcoded ordering of "telephony
(NITZ) first then network (NTP)".

This commit also modifies the name of the method used to trigger a time
detection cycle after a config change. It's possible partners may want
to make the priority originate from a setting rather than static config
(i.e. so the partner can pick between origins or origin orders). This
would involve more work than currently planned, but it is easy to make
the method name less specific.

Bug: 172230856
Test: treehugger
Test: atest TimeDetectorStrategyImplTest
Merged-In: Id1652be174b7503618e0b802dc7da4d00df4f248
Change-Id: Id1652be174b7503618e0b802dc7da4d00df4f248
parent 23b7c01b
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