Peter Cai 437002d189 ConnectionService: handle disconnected state correctly ... onDisconnect() will only be called when the user manually requests a disconnect. When the call is disconnected by the rtp connection itself, the call won't be cleaned up and the system will be stuck in an in-call state. Handle this correctly by moving the clean-up code to a close() function, and calling that function instead when we disconnect. Note that we cannot call the cleanup routine destroy() from the onStateChanged() function, because it seems that this triggers a deadlock somewhere down the line, probably in the calling account-related telephony code. Doing a close() function mirrors what is done in the default TelephonyConnection implementation for RIL-based calls.		2022-03-12 23:29:14 -05:00
..
cheogram	ConnectionService: handle disconnected state correctly	2022-03-12 23:29:14 -05:00
conversations	pulled translations from transifex	2022-03-07 08:42:40 +01:00
conversationsFree/java/eu/siacs/conversations/utils	use installreferrer libray instead of broadcast listener	2020-01-11 11:08:09 +01:00
conversationsPlaystore/java/eu/siacs/conversations/utils	validate install referrer beforing accepting it as xmpp uri	2020-06-18 10:15:51 +02:00
free/java/eu/siacs/conversations/services	bump appcompat, migrate to emoji2 and get rid of emoji flavor	2022-02-23 10:37:03 +01:00
main	ConnectionService: Dialer UI integration for incoming calls	2022-03-12 12:50:29 -05:00
playstore	bump appcompat, migrate to emoji2 and get rid of emoji flavor	2022-02-23 10:37:03 +01:00
quicksy	pulled translations from transifex	2022-02-09 12:17:29 +01:00
quicksyFree/java/eu/siacs/conversations/utils	automatically receive Quicksy SMS. fixes #3962	2021-01-19 15:45:43 +01:00
quicksyPlaystore/java/eu/siacs/conversations/utils	automatically receive Quicksy SMS. fixes #3962	2021-01-19 15:45:43 +01:00