GitLab: #908
Change-Id: I6894a86773918674732d51caf49823b220fba721

Change-Id: I4875e4d76f5da442eace0204052d536c65545d3f

Change-Id: If63f898c8b7c26cbe7ca0d3a8bc91d1196d92691

Adrien Béraud authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: Ib3795ac6c5ed5c8b3dce2d3343e95800657ebb2a

Else, it will avoid to sync other conversations.

Change-Id: I7554b88a6760557a0d4b36effddd5301c74938db

Change-Id: I725392df29e76a1dd36c7163f9defe6484573223

Adrien Béraud authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: I9238a317e93089a9ed618e02e7dd6da243d3dc3f

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: I80aebbc7cfe97b257571a13a07eff00dab0b2a2c

Change-Id: I32c4f19a14f1f18b5bfb6e0975d5ca6964d7297f

Change-Id: I5b663b0fa732517e25dca7f016c456dba9c8f3ab

Adrien Béraud authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: Ifea0a1ebd9cc36214b0532c01119333cd269f1a0

Change-Id: I33d2b5575afc78df2fd35b03e197b5d59a3a0bf7

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

If the repository is in the conversations directory but the contact
is removed, every time the daemon starts we will see this log because
getContactDetails() returns nothing for a removed contact

Change-Id: Id363c57e81417ba37bb2a52cc4348433658dae21

If a ContactRemoved event occured while some conversations were in
a syncing state, the conversations were removed.
This can cause random conversation deletion when importing a JAMS
account who already deleted itself as a contact.
The correct condition was just checked when the conversation is
already cloned.

Change-Id: I378f765480dcd92c7315579ba5c26a4ca50ddb23

This allow the JAMS server to know what is the correct
conversation to sync in 1:1
jami-jams#125

Change-Id: Icfd50c643ef5f4389e08825591f6d70347ee63d2

Andreas Traczyk authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: I0e142f271fa0db3c3d4af1e57919ef1f65beb8c2

Change-Id: I451c66a9b9a8f806daa82406ca24936d4345b068

Change-Id: I52b8397d1e8d9f984639890004ab6e70ae3f1d7b

Change-Id: I3beed7ff82d3bb5055b5c50e4c4e358d9eec8f67

Change-Id: Ib12708c9937663be24f0b3ce6eb0f0f846914c87

Change-Id: Ie445116f321e91e13239009b32318cd24cf3c6a7

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

In SIPCall, requestKeyFrame & setVideoOrientation are using
pjsip on the main thread. To avoid this, use the io thread as
it's io operations that should not be done on main thread.

Moreover, some operations from recorder were called from pjsip
but not retriggered, causing jami->pjsip->jami operations
called with lock that could be called from pjsip nor jami causing
potential deadlocks.

Finally, audioDecoder_/receiveThread_ should be protected in
AudioRtpSession.

This fixes crashes for ut_conference

GitLab: #900
GitLab: #901
GitLab: #902
Change-Id: I055b297d25bc417e685f4c31d6105e4f6dab52e6

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

Else, the mute state is ignored, causing the new member to be able
to listen from the host even if the host muted itself.

jami-client-android#1351
Change-Id: Ic0e4f7ac99fd945847f47c9e2e4573fa1d6a1b1a

Xavier Jouslin de Noray authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: I42922bdff891b572e0193f5e0fdf9050c9a81c3a

Change-Id: I7a5a0f1f1b97ec7681b15eaea535f400219c4cc9

Change-Id: I3f6ef655d88039e401ff00bcad5992db38357c69

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: I2f41093e1a5ef4ec31b5e3ba1c9a79c8b9e7826c

Nothing prevents setup() to be used while deleting onSuccessfulSetup_
So checking if (onSuccessfulSetup_) in setup() can cause a crash.
loop_.join() should prevent any call to onSuccessfulSetup_ and
any potential crash

Change-Id: I5fef00edbcc9701a3129a31b247472e62b6453d9

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

jami-client-qt#1354
Change-Id: I1153a1dfd3215b3fb03afe9b3ac4f39aad99fdf8

Adrien Béraud authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: I22b1b79a484b55701570db44dcd2c0387703ff9b

Adrien Béraud authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: I259a0ca7cdc7d98f89d93ecf37c362af16d9cf85

Alexander Lussier-Cullen authored 1 year ago and Adrien Béraud committed 1 year ago

Normally with 1440p or higher video, the upward bitrate adjustment can
take awhile to reach acceptable levels for the resolution. Starting
these at a higher bitrate will allow the adjustment to be made more
quickly. Also, the maximum bitrate of 6000kbps is potentially
insufficient for these higher resolutions, so this is also adjusted.

The constant values used for the bitrate and max bitrate calculation
are mostly arbitrary and simply fit what values seem to work best for
1440p and 4k video.

Change-Id: I746eeddae5ac8183039cb757bba881475b9e2907

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

737e2f11 introduces a regression
where "uri.crt" is replaced by "uri/crt", causing incorrect path
and breaking the vote system

Change-Id: Ibe5dff8335c2f989dc1de944c1cc538d4a7f6489

Change-Id: I4e87c32581695ca535cc431dfa8b8a1c64e06028

Change-Id: I85ce6b6b8596a755648b20ade3aabc314e4e259a

Change-Id: I1f0db645d5d84462825a1630430673ad8b8f50ff

Change-Id: Ia2f2eada788e6dd81e2442a0f384943ea3efa8ad

Change-Id: Ifc8e85cad40def55606591c4267a81b0a3d90951

Change-Id: I566a66b7405afe680bacd0e343ea7ac0901b912c

Change-Id: I4482ddabb8c6a7a22b2ed897a2294fab576efaa3