6e418b3ebbeb4c15971121d8b1ce326011799b69 - LeafOS-Project/android_frameworks_base

commit	6e418b3ebbeb4c15971121d8b1ce326011799b69	[log] [tgz]
author	Thomas Stuart <tjstuart@google.com>	Mon Feb 06 08:22:08 2023 -0800
committer	Thomas Stuart <tjstuart@google.com>	Fri Feb 10 18:08:52 2023 +0000
tree	3f9bfcf8a70319f533af28e9faa012eadd3d0737
parent	35b1662ea3a7b743daf00a019d134e9a725c301c [diff]

seperating callback changes

After some discussion amongst Telecom and an API council member, the
better design decision is to break up previous CallEventCallback into
two seperate callbacks.

The reason being, there is one set of callbacks that require the
client to complete a Consumer and another set of callbacks that only
provide event updates.

By making this change, the API surface becomes cleaner and should
eliminate some confusion.

bug: 268098087
Test: CTS
Change-Id: If5c46af9618be3720be203402bad9b583b3b2d06

core/api/current.txt[diff]
telecomm/java/android/telecom/CallControlCallback.java[Added - diff]
telecomm/java/android/telecom/CallEventCallback.java[diff]
telecomm/java/android/telecom/CallException.java[diff]
telecomm/java/android/telecom/TelecomManager.java[diff]
telecomm/java/com/android/internal/telecom/ClientTransactionalServiceWrapper.java[diff]
telecomm/java/com/android/internal/telecom/TransactionalCall.java[diff]

7 files changed