savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-04-19T13:28:58Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/299Swarm: remove a user from the conversation2021-04-19T13:28:58ZSébastien BlinSwarm: remove a user from the conversation+ Implement https://git.jami.net/savoirfairelinux/ring-project/wikis/Group-chat-feature-(design-draft)#remove-a-device-from-a-conversation
+ Add tests+ Implement https://git.jami.net/savoirfairelinux/ring-project/wikis/Group-chat-feature-(design-draft)#remove-a-device-from-a-conversation
+ Add testsSwarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/298Swarm: Remove a device from the conversation2022-07-13T17:35:28ZSébastien BlinSwarm: Remove a device from the conversation+ Implement https://git.jami.net/savoirfairelinux/ring-project/wikis/Group-chat-feature-(design-draft)#remove-a-device-from-a-conversation
+ Add tests+ Implement https://git.jami.net/savoirfairelinux/ring-project/wikis/Group-chat-feature-(design-draft)#remove-a-device-from-a-conversation
+ Add testsSwarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/297Swarm: implement DRT (after first version)2023-04-28T19:42:53ZSébastien BlinSwarm: implement DRT (after first version)https://git.jami.net/savoirfairelinux/ring-project/wikis/Group-chat-feature-(design-draft)#drt-name-will-change
# In progress
+ add tests for mobile DRT
+ Client: remove limit of 8 participants
+ Test in real environment
# TODO:
+ D...https://git.jami.net/savoirfairelinux/ring-project/wikis/Group-chat-feature-(design-draft)#drt-name-will-change
# In progress
+ add tests for mobile DRT
+ Client: remove limit of 8 participants
+ Test in real environment
# TODO:
+ Debug last locks
+ Cleanup code
+ Finish last tests
+ Document on docs.jami.netSwarm-chatSébastien BlinFadi ShehadehSébastien Blin2023-02-28https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/296Swarm: see for file transfers (NEEDS DESIGN)2021-06-12T11:37:07ZSébastien BlinSwarm: see for file transfers (NEEDS DESIGN)Swarm-chatSébastien BlinAdrien BéraudSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/295Swarm: add a test for sending a message to multiple participants at once2021-06-12T11:37:27ZSébastien BlinSwarm: add a test for sending a message to multiple participants at onceScenario:
Alice creates a conversation with 8 members
Then sends a messages
All devices should receives the whole conversationScenario:
Alice creates a conversation with 8 members
Then sends a messages
All devices should receives the whole conversationSwarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/294Swarm: default branch should not be "master" but "main"2021-02-19T17:12:18ZSébastien BlinSwarm: default branch should not be "master" but "main"Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/293Swarm: multi-device management2020-09-18T19:50:25ZSébastien BlinSwarm: multi-device managementhttps://git.jami.net/savoirfairelinux/ring-project/wikis/technical/6.2.-Sync-Protocol
Related patch: https://review.jami.net/c/ring-daemon/+/15584https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/6.2.-Sync-Protocol
Related patch: https://review.jami.net/c/ring-daemon/+/15584Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/292Swarm: Fix build on jenkins2020-12-23T19:37:25ZSébastien BlinSwarm: Fix build on jenkinsPatches are not building for nowPatches are not building for nowSwarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/291Swarm: redo code for gitserver2021-04-19T14:20:32ZSébastien BlinSwarm: redo code for gitserverThis commit is ugly
# TODO
+ [x] Remove ioPool and only use callbacks
+ [x] Support shutdown
+ [ ] Multiple want and improve negotiation
+ [ ] Recheck answerToWantOrder();
+ [ ] Support depth request (https://github.com/git/git/blo...This commit is ugly
# TODO
+ [x] Remove ioPool and only use callbacks
+ [x] Support shutdown
+ [ ] Multiple want and improve negotiation
+ [ ] Recheck answerToWantOrder();
+ [ ] Support depth request (https://github.com/git/git/blob/master/Documentation/technical/pack-protocol.txt#L256)Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/66code smell: ClientWrapper wraps wrappers and should be removed2020-09-17T16:18:06ZAndreas Traczykcode smell: ClientWrapper wraps wrappers and should be removedAlso, adapter classes should wrap and provision observables for data like:
- current account id
- selected conversation id
- account list size
- ...
This will remove the need for QML functions currently forcing UI updates.Also, adapter classes should wrap and provision observables for data like:
- current account id
- selected conversation id
- account list size
- ...
This will remove the need for QML functions currently forcing UI updates.Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/290[Maybe fixed/To check]ICE/TURN - Investigate why relay candidates are most of...2021-02-15T17:07:51ZMohamed Chibani[Maybe fixed/To check]ICE/TURN - Investigate why relay candidates are most often selectedIt has been observed in many environments when TURN relay is enabled, that the ICE negotiation will frequently result in relay candidates (TURN) being selected while server-reflexive or peer-reflexive candidates should have been selected...It has been observed in many environments when TURN relay is enabled, that the ICE negotiation will frequently result in relay candidates (TURN) being selected while server-reflexive or peer-reflexive candidates should have been selected instead. Typically, when the "connectivity checks" succeed for both relay and reflexive candidates, the reflexive candidates should be selected because of their higher priority.
Note that in the current version, the "Aggressive nomination" is used to optimize the connection time (see [RFC5245](https://tools.ietf.org/html/rfc5245#section-8.1.1.2) for more details). This may have a major impact on the selected pair. Still, we need to know if this is the only cause or if other factors are involved. We also need to know if we can improve it.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1074Android - Audio is not automatically routed to headsets when plugged2023-05-31T13:31:14ZMohamed ChibaniAndroid - Audio is not automatically routed to headsets when pluggedOn Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.On Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.Backloghttps://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/37Android - Audio is not automatically routed to headsets when plugged2022-02-03T18:27:04ZMohamed ChibaniAndroid - Audio is not automatically routed to headsets when pluggedOn Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.On Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.Backloghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/796Android - Audio is not automatically routed to headsets when plugged2021-12-29T21:11:09ZMohamed ChibaniAndroid - Audio is not automatically routed to headsets when pluggedOn Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.On Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/289Android - Audio does not automatically routed to headsets when plugged2020-09-04T18:41:35ZMohamed ChibaniAndroid - Audio does not automatically routed to headsets when pluggedOn Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.On Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/65Wizard view: no way to exit the main wizard without creating an account or re...2020-09-04T13:53:59ZAndreas TraczykWizard view: no way to exit the main wizard without creating an account or restarting the app.The first page is missing an exit/back button.The first page is missing an exit/back button.Itération 21Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/64Wizard view: some back buttons are shown with an incorrect size2020-09-22T12:59:23ZSébastien BlinWizard view: some back buttons are shown with an incorrect size+ In import from backup, it should take the full width
+ In import from device, it should take the full width
+ In create SIP account, it should take the full width+ In import from backup, it should take the full width
+ In import from device, it should take the full width
+ In create SIP account, it should take the full widthItération 21Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/63Wizard view (welcome page) should have a back button when some accounts alrea...2021-02-04T13:56:28ZSébastien BlinWizard view (welcome page) should have a back button when some accounts already exists?Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/62Make application borderless and re-add close/minimize/maximize buttons2024-02-21T22:05:01ZSébastien BlinMake application borderless and re-add close/minimize/maximize buttonsAll is in the titleAll is in the titleLaterÉdouard DenomméeAndreas TraczykÉdouard Denomméehttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/795Pictures and Video are not always send when i click the camera icon2021-08-19T20:37:53ZMarinus SavoritiasPictures and Video are not always send when i click the camera icon## Describe your environment
Please specify the following:
- Ring version: 20200810
- Device model: Fairphone 3
- Android version: Android 9.0 /e/ with MicroG
- What build you are using: F-droid
## Steps to reproduce
- Can ...## Describe your environment
Please specify the following:
- Ring version: 20200810
- Device model: Fairphone 3
- Android version: Android 9.0 /e/ with MicroG
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. Click the camera icon and be redirected to the default open camera
2. Take a picture and return automatically to the app
...
- Actual result: Nothing happens
- Expected result: The picture or the video gets sent as a message