Peter Cai 3ee45952fc set in-call UI active in the connecting state ... Currently, if the "CONNECTING" stage of a Jingle call takes a significant amount of time (say, a second), then there will be a window where the call is already accepted but the ringing UI is still showing. This 1) is confusing; 2) allows the user to accept a call twice, which will cause a crash. Unfortunately, there is no native equivalent to the "CONNECTING" state. The only sane choice here seems to be showing the in-call UI even if the call is still connecting.		2022-04-21 17:14:14 -04:00
..
androidTest	Screenshot add contact options speeddial	2022-03-14 15:24:56 -05:00
cheogram	set in-call UI active in the connecting state	2022-04-21 17:14:14 -04:00
conversations	remove footnote hint in translations	2022-03-26 08:43:25 +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	Make Sopranica bookmark deleteable.	2022-04-20 09:34:56 -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
cheogramPlaystore	Some fixes for playstore build	2022-03-14 13:21:17 -05:00