summaryrefslogtreecommitdiff
path: root/api/api.go
diff options
context:
space:
mode:
author Evan Laird <evanlaird@google.com> 2024-08-28 22:52:05 -0400
committer Evan Laird <evanlaird@google.com> 2024-08-29 13:30:49 -0400
commitdcfc485a0bdf6922639b8b3f7bc48e2d2db47b54 (patch)
tree461f6a6c67f5a351bc9401e4118efdb378ba63f0 /api/api.go
parentcdda826a42d72a269b3886d42d5b80bd13ff81dd (diff)
[mobile] Device-based emergency call capable
This is (yet another) departure from the legacy logic to answer the question "can the device make emergency calls". This is strictly separate from the calculation of a per-subscription understanding of emergency call capability. We listen for any SERVICE_STATE broadcasts that don't refer to a known subscription (this part is done by checking subId = -1, and assumes that -1 in this case means "device-based" rather than "carrier-based"). When that happens, we call the new telephony APIs for getting the number of slots, and subsequently querying each slot for its service state. If any service state for a given slot reports that it is capable of emergency calls, then the top-level connections repository reports it. And we can use that in our logic downstream (e.g. for satellite) Test: MobileConnectionsRepositoryTest Test: MobileIconsInteractorTest Bug: 346579914 Flag: NONE bugfix Change-Id: Id0f74df979fcd947e0fd856add9c38a764b56b3b
Diffstat (limited to 'api/api.go')
0 files changed, 0 insertions, 0 deletions