Ensure docs clearly state that handle id should not contain PII.
Test: Docs only change.
Fixes: 192673156
Change-Id: I4a612876fa5e2aac2159928b4c6cfde253d7395a
This is used to work around a bug in the remote connection service API
where this property is not being passed through to Telecom.
Test: Use connection manager carrier and verify that VERSTAT is now
propagated to Telecom.
Bug: 192608283
Change-Id: Ie45e7c05d78623085cd2be32470a5870d243745c
When an existing connection is added to represent an IMS conference
participant, it is added with an associated parent conference specified.
This was NOT passed along to the connection manager via the
RemoteConnectionService API since there is no equivalent API present for
that operation. To work around this, we stash the parent conference's
ID into the connection extras. We will use that later so that Telecom
can know which conference is the parent of this call.
Also, removing restriction in RemoteConnectionService which would ignore
conferences with no children. This assumption was incorrect for VOLTE
conferences since they will start with no children. As a consequence we
would ALWAYS skip adding IMS conferences to the connection manager, which
would mean that it had no way of knowing about the conference that the
existing connections are associated with.
Test: Manual test with connection manager APIS on live network; make
conference and verify that the correct objects are being created wrapped
by the connection manager.
Bug: 188420526
Change-Id: Ie58afed7a3b7eeaa7e329e80479d273e4c50ec82
Change-Id: I4250f9459c7a1b82936583a10e93d049fdfb4c5d
This should ideally be a valid in terms of the reported camera
characteristics.
Test: Docs only change
Bug: 190804553
Change-Id: I35e0148e6e9d90d991b556e5c6db4bbd77ce39a0
There is a possibility of a call receiving a details update when it has
already been removed from the CallDiagnosticService. Handling this case
by just ignoring the details update (since it isn't relevant as the call
is now removed).
Also noted there were a number of places where access to the shared
maps was not synchronized as it should be.
Test: Run manual tests and note no more CDS crashes from SCONE app.
Fixes: 188939131
Change-Id: Ic1f96fd60a70432bef0daaa2e9729c66401ba4ac
Adds some clarifications for how UCE operates
in Android 12.
Bug: 188580687
Test: docs only change
Merged-In: I139455c286378ccfac876014656f8d3177bdba9d
Change-Id: I139455c286378ccfac876014656f8d3177bdba9d
Adds some clarifications for how UCE operates
in Android 12.
Fixes: 188580687
Test: docs only change
Change-Id: I139455c286378ccfac876014656f8d3177bdba9d
There's UnsupportedOperationException in RemoteConnectionManager which
means sometimes we can't find corresponding ConnectionService and we
can't find the root cause of this. Try to print more log if there's
RemoteException when we add ConnectionService.
Bug: 175466894
Test: Manual test
Change-Id: Ia34cf8777c17c3eb45476018125d9b92db391e28
Revert submission 1453740-replace_with_isEmergencyNumber
Reason for revert: <Telephony service may not up while calling this, causing failures.>
This also cherry picks ag/14444738
Change-Id: I5aa71917ce1b2abcdfcf78b8988d128982a6b3ec
Bug: 132703886
Bug: 181062609
Bug: 187720309
Merged-In: I5df03a61f55f863e17594aa3239433a5048a4890
When the RTT call was cleaned up, the "close()" method was not being
called. In practice I think the Dialer app never really stops RTT, but
the APIs (and test app) do allow it to be stopped mid-session. I'm
hypothesizing that is why we don't see this.
Test: Use Telecom test dialer to start and end RTT session. Observe no
strict mode violation.
Fixes: 186869727
Change-Id: Id474b493ac3fe39e97360f3ac326279fc9a9a5eb
Put a bound on the recursion in Session#toString
to ensure we do not accidently cause a Stack overflow
Bug: 186694546
AOSP: aosp/1691210
Test: atest TeleServiceTests
Change-Id: I52f44dd02d0d860d0894e9b84fded8cf5ff5a18e
Put a bound on the recursion in Session#toString
to ensure we do not accidently cause a Stack overflow
Bug: 186694546
Test: atest TeleServiceTests
Merged-In: I52f44dd02d0d860d0894e9b84fded8cf5ff5a18e
Change-Id: I52f44dd02d0d860d0894e9b84fded8cf5ff5a18e
This was left in place for Google3 compatibility during development; this
is no longer required as the usages have been cleaned up.
Test: Build / run CTS
Fixes: 186659702
Change-Id: Ib386c3f9912870b11b1a37863dccfa9d3b5cb7a9
When trying to write some connectionservice unit tests, it became clear
that the mAreAccountsInitialized precondition adds a LOT of overhead
and test scaffolding. It was easier to just be able to bypass that
in the unit tests.
Test: Added as part of unit test.
Bug: 178649879
Change-Id: Ibed3e69215dad59b252193f701508c18f43b59a2
