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
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.
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
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
All the java code used to build the framework jar and run metalava
was previously defined in the toplevel Android.bp files. Move these
into the subdirs where the source actually lives.
This simplifies the rules themselves (no path and needless prefix) and
declutters the top level Android.bp.
Test: m
Change-Id: I97086e309eacb879d16facb8497d9940fa5ddaf6
For API version 31+, ensure that READ_PHONE_STATE is checked on
APIs that retrieve/notify the call state of the device.
Bug: 157233955
Test: atest CtsTelecomTestCases2 CtsTelephony2TestCases
Change-Id: I9f8674a3075d3e0f75ee4f41eefce328c0fa6b91
Complete plumbing for call quality reports to get to the CDS.
Test: Manual network testing.
Test: Modify CTS tests to cover these cases.
Bug: 163085177
Change-Id: I2bb68d29c4ad11cc8738c26cd69404fde4348843
The Telecom Call object is primarily a control object which allows
control of a call and receipt of events related to a call. The actual
properties and data pertaining to a call all exists in Call.Details...
except for the call state (RINGING,ACTIVE, HOLD, etc).
This CL moves the call state to the Call.Details class to remove this
one dangling property of the base Call class.
Test: Run Telecom CTS test suite.
Bug: 163085177
Change-Id: I59413d3e14d03b48263a5cb351fe4e9a553b578e
Keep DiagnosticAll in a deprecated form to maintain binary compatibility
with ongoing work in other repos.
Test: run CTS
Test: run unit tests
Fixes: 182241145
Change-Id: Ia14113bcce344bb589408b74eaab74d413de9e7e
1. Remove NETWORK_TYPE and AUDIO_CODEC constants in favor of existing
constants in TelephonyManager and Connection. Add API docs explaining
the simplifications of these two concepts.
2. Add more documentation on DiagnosticCall#sendDeviceToDeviceMessage
to explain the D2D protocol and the bandwidth challenges inherent.
3. Remove DiagnosticCall#getCallDetails.
4. Provide provision for developer-defined Executor in the
CallDiagnosticService; added docs there and in DiagnosticCall explaining
the threading model used.
Test: Ran CTS tests
Fixes: 182241145
Change-Id: Icb0d8a05add778a0cfcbe3448063cd9dcee3abc1
Docs updates:
* setCallExtraParcelable must take a framework-defined parcelable
* EXTRA_PICTURE_URI takes an android.net.Uri
* Remove redundant documentation on setCallComposerStatus
Fixes: 182510687
Test: docs only
Change-Id: I43f776cf8bcb72c4121515536a3790cf44bf1638
Propagate telephony disconnect causes and imsreasoninfo to Telecom for
propagation to CAllDiagnosticService.
Plumb through disconnect message override in CallDiagnosticService.
Test: Added new CTS test coverage for these APIs.
Test: Manual test with telecom test app; verify the disconnect message is
overridden.
Bug: 163085177
Change-Id: I0c6938f2d0a46d535ae201364193ef58e07ec488
Add an overrideable method in ConnectionService that gets called when
telecom binds, since onBind is final and it's unsafe to make not-final.
Bug: 181057509
Test: atest CtsTelecomTestCases
Change-Id: I80088185402789fec499b8659ca8b74bcec05748
