savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-05-23T22:12:11Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/689audio devices list not updated when adding/removing a device2023-05-23T22:12:11ZKateryna Kostiukaudio devices list not updated when adding/removing a deviceSteps:
- open media settings
- plugin a new device
- open list of audio input/output devices. A new device not added to the listSteps:
- open media settings
- plugin a new device
- open list of audio input/output devices. A new device not added to the listKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1403Mediademuxer: buffer can increase2022-02-16T21:47:04ZSébastien BlinMediademuxer: buffer can increaseIn MediaDemuxer::decode():
`av_read_frame` only return one frame of the video buffer. However, if the CPU is too slow to decode (should not happen, but still), frames can just be stored and the video buffer can increase with a big maxim...In MediaDemuxer::decode():
`av_read_frame` only return one frame of the video buffer. However, if the CPU is too slow to decode (should not happen, but still), frames can just be stored and the video buffer can increase with a big maximum.
This should never happen. If the video buffer gets too big, the video will have a big delay.
But we also should not hide other problems. So, potential solution:
Check the size of the internal video buffer and log if too big before flushing.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/723Mediademuxer: buffer can increase2022-02-16T21:47:04ZSébastien BlinMediademuxer: buffer can increaseIn MediaDemuxer::decode():
`av_read_frame` only return one frame of the video buffer. However, if the CPU is too slow to decode (should not happen, but still), frames can just be stored and the video buffer can increase with a big maxim...In MediaDemuxer::decode():
`av_read_frame` only return one frame of the video buffer. However, if the CPU is too slow to decode (should not happen, but still), frames can just be stored and the video buffer can increase with a big maximum.
This should never happen. If the video buffer gets too big, the video will have a big delay.
But we also should not hide other problems. So, potential solution:
Check the size of the internal video buffer and log if too big before flushing.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1295Conference: Host should be able to mute video & mic2023-05-26T13:59:31ZSébastien BlinConference: Host should be able to mute video & micBackloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/685Swarm: add swarm details page2022-03-23T22:01:50ZSébastien BlinSwarm: add swarm details page![group-settings](/uploads/5a0642c5098a06514a5737ec40589a10/group-settings.png)![group-settings](/uploads/5a0642c5098a06514a5737ec40589a10/group-settings.png)Swarm-chathttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1400[Feature request] Show difference between call failed / declined and coloured...2023-12-06T20:33:10ZElys[Feature request] Show difference between call failed / declined and coloured iconsAs far as I know it is not possible for the receiver of the call to know WHY a call failed?
You just get "Outgoing call failed" and I never get a message like "Call Declined" if the other person declines the call. So if there is no way ...As far as I know it is not possible for the receiver of the call to know WHY a call failed?
You just get "Outgoing call failed" and I never get a message like "Call Declined" if the other person declines the call. So if there is no way to get a message like "Call Declined" this would be a feature request.
However, it would be great if the person who makes a call can choose if the receiver should get a "Call failed" or "Call Declined".
If you use the Android version of Jami you also have icons. It would be great if these icon have different colors (failed, declined, etc.)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1397startup / multiple accounts / only the selected one logs in2023-05-05T19:28:49ZArne Wörnerstartup / multiple accounts / only the selected one logs inI have 7 phone numbers, that are routed to 3 SIP accounts (serious, funny, bankrupt company from the present yellow pages) in jami-qt that have pairwise different ringtones, so that I know, if it is a fun call or my mom.
But:
After star...I have 7 phone numbers, that are routed to 3 SIP accounts (serious, funny, bankrupt company from the present yellow pages) in jami-qt that have pairwise different ringtones, so that I know, if it is a fun call or my mom.
But:
After startup just the last used account has a green dot, while the others have an orange dot.
Workaround:
Disable&Re-enable the accounts with an orange dot.
Can u do it automatically without much effort?
Or should i better play with the source code myself?
Or is it a feature?https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/670Swarm: Add swarm creation into the UI2022-05-13T14:55:46ZSébastien BlinSwarm: Add swarm creation into the UI![create-group0](/uploads/3a632484fbac3e6313dffa2a7605e1c9/create-group0.png)
![create-group1](/uploads/bb76dae1c886bc5cd83e6ce6cc840252/create-group1.png)![create-group0](/uploads/3a632484fbac3e6313dffa2a7605e1c9/create-group0.png)
![create-group1](/uploads/bb76dae1c886bc5cd83e6ce6cc840252/create-group1.png)Swarm-chathttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/705Split JamiAccount: rewrite setAccountDetails.2022-11-26T22:41:27ZSébastien BlinSplit JamiAccount: rewrite setAccountDetails.Account's config should be in a separated class
setAccountDetails should only change what is in the map, not all settings.Account's config should be in a separated class
setAccountDetails should only change what is in the map, not all settings.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1388Outgoing call fails if you immediately start a video call after you see the g...2023-04-14T12:59:34ZElysOutgoing call fails if you immediately start a video call after you see the green dot / or after screen timeout (Android)Related to https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/846
>If you start Jami (Windows 10; you wait until the green dot of Person B is visible) and you immediately start a video call you get connected but it takes...Related to https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/846
>If you start Jami (Windows 10; you wait until the green dot of Person B is visible) and you immediately start a video call you get connected but it takes some time and then the outgoing call fails.
>(turn enabled both sides)
So you start a video call as soon as both apps are opened and you can see both persons are shown online.
(This test: same user account -> same user account)
> Windows 10: After you see the green dot of the account of the person you want to call and you NOT immediately call the other person but wait for 30 seconds there's hardly any connection problem.
both situations:
Call:
Windows 10 -> Android
Android -> Windows 10https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/693Provide parameters for pulseaudio's echo-cancel-module2022-12-30T20:58:13ZAmin BandaliProvide parameters for pulseaudio's echo-cancel-moduleWe currently don't set any additional arguments for pulseaudio's echo canceller module:
https://git.jami.net/savoirfairelinux/ring-daemon/-/blob/504e54608267a257e14acc84daea236b1fd4f85a/src/media/audio/pulseaudio/audiostream.cpp#L59
V...We currently don't set any additional arguments for pulseaudio's echo canceller module:
https://git.jami.net/savoirfairelinux/ring-daemon/-/blob/504e54608267a257e14acc84daea236b1fd4f85a/src/media/audio/pulseaudio/audiostream.cpp#L59
Various GNU/Linux distributions such as Debian and its derivatives don't load the echo canceller module in `/etc/pulseaudio/default.pa` at all or with any additional parameters, so we can't rely on that.
We should look into providing additional arguments -- like the ones below -- ourselves when creating the pulseaudio stream.
For reference: example of loading the echo canceller module with additional arguments in a pulseaudio config file (thanks @atraczyk):
```
load-module module-echo-cancel use_volume_sharing=1 use_master_format=1 aec_method=webrtc aec_args="digital_gain_control=1 experimental_agc=1 analog_gain_control=0 noise_suppression=1 voice_detection=1 extended_filter=1" source_name=echoCancel_source sink_name=echoCancel_sink
```https://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-client-android/-/issues/1073Wrong microphone used for audio and video call2022-02-03T18:25:23Zring userWrong microphone used for audio and video call- Jami Version: Live Free or Die 20190602-01 (from F-Droid)
- Android Version: LineageOS 16 (Android 9), no GApps
- Smartphone: Samsung Galaxy S5 (klte)
If I make or receive an audio or video call, I have to talk loud and close to the m...- Jami Version: Live Free or Die 20190602-01 (from F-Droid)
- Android Version: LineageOS 16 (Android 9), no GApps
- Smartphone: Samsung Galaxy S5 (klte)
If I make or receive an audio or video call, I have to talk loud and close to the microphone at the top of my smartphone. I didn't even notice there is a second microphone at that place before.
I would expect to be able to use the mike at the button of my phone.
In a normal call without Jami I can use the "normal" microphone at the button.
Another problem is, that during an video call I have to speak directly into that micro. If I'm looking at the video stream, I'm too far away from the mike so the other user can't hear me.
Settings:
- Mobile Data: enabled (but not used for the tests)
- HD-Video: enabled
- Hardware-Acceleration: enabled
- Use system contacts: disabled
- Normal phone calls via Jami: disabled
- Start Jami while booting: enabled
- Run Jami in background: enabledBackloghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1072Overview: LocationSharing2022-12-30T20:57:52ZMaxime CalletOverview: LocationSharing## Android location sharing
This issue wants to regroup in one all the known bugs and features request available. This is done to give a general overview on how the sharing location feature must be improved and give a better global visi...## Android location sharing
This issue wants to regroup in one all the known bugs and features request available. This is done to give a general overview on how the sharing location feature must be improved and give a better global visibility to team members and users.
## Current bugs
- [x] Fix cross platform location sharing (ios/android)
- [ ] Location sharing does not always show when you open the conversation and you have to click on the notification¨
- [ ] ...
- [ ] ...
## Features request pool
- [ ] the Map should be contained in a card like a message or a link [#960](https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/960)
- [ ] ...
- [ ] ...Adrien BéraudKateryna KostiukAmirhossein NaghshzanMaxime CalletMehdi GhayourAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1069Bluetooth: add control accessibility with bluetooth2023-05-05T19:16:12ZMaxime CalletBluetooth: add control accessibility with bluetoothadd control for:
- accept call, refuse call & end call
- volume up & downadd control for:
- accept call, refuse call & end call
- volume up & downAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/667Allow, if required, conversations/contacts side pane pane to be hidden2022-02-04T04:05:12ZovariAllow, if required, conversations/contacts side pane pane to be hidden(title was: `Full window` buttons)
Related to #546?
Please see FreeTube image at:
https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/546#note_33793
Arrow icons at:
https://review.jami.net/c/jami-client-qt/+/21022
* ![View_F...(title was: `Full window` buttons)
Related to #546?
Please see FreeTube image at:
https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/546#note_33793
Arrow icons at:
https://review.jami.net/c/jami-client-qt/+/21022
* ![View_Full_Window_button](/uploads/cab48be2650ef438d0d9bbdccd754742/View_Full_Window_button.png) `View full window`
* ![Close_Full_Window_button](/uploads/0362633928279f7fb9e31d2b120936e8/Close_Full_Window_button.png) `Exit full window`
Mock up with full screen buttons added like:<br>
![Layout](/uploads/86c56bc200959a41822743adf42c0475/Layout.png)
If Jami is in `full screen` ![View_Full_Screen_button](/uploads/7843cc32d41ee2db278270b2663903e7/View_Full_Screen_button.png) or `full window` ![View_Full_Window_button](/uploads/4a55a0fba00e99a569d6d9fa00589cc8/View_Full_Window_button.png) then the button to show in the mockup above would be `Exit full screen` ![Close_Full_Screen_button](/uploads/547eea0a67311cb22a2f8862b604b9c0/Close_Full_Screen_button.png) or `Exit full window` ![Close_Full_Window_button](/uploads/932fc46a2c4cef7cf425bdffeb049d0b/Close_Full_Window_button.png), respectively
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/665Keyboard shortcuts table is ugly2022-11-04T19:14:12ZSébastien BlinKeyboard shortcuts table is uglyRedo this UI, also add a button in the welcome page to open this window (actually only accessible via F10)Redo this UI, also add a button in the welcome page to open this window (actually only accessible via F10)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1385[Feature request] Completely disable audio and/or video calls (for all users)...2024-01-12T19:30:20ZElys[Feature request] Completely disable audio and/or video calls (for all users) [per (own) user account]all supported os
It would be great if you were able to disable audio or video calls only for all users (using just one / two buttons [Settings per account] ).
This would be useful if you only want to communicating via text (chat). Espe...all supported os
It would be great if you were able to disable audio or video calls only for all users (using just one / two buttons [Settings per account] ).
This would be useful if you only want to communicating via text (chat). Especially as soon as group chat will be available.
And of course having the option to disable the possibility to send attachments.
Example: https://threema.ch/en/faq/calls_disable
So once you disabled video calls using the account settings of your user account you are not able to make calls anymore and/or no people can call you.
Or you have the following options [user settings]:
* Disable audio-only calls from all users
* Disable video calls from all users (maybe allow participants to show their screen [screenshare] but not their webcam(s))
* Disable audio-only calls from all users and your own user account
* Disable video calls from all users and your own user account
If someone tries to call you he should get a message like "This user doesn't allow audio/ video calls".
However, since Jami allows multiple user accounts at the same time you should be able to make and receive calls using another own account.
It's similar to: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1280 (but in this case this setting should apply to all users that try to call you)
And it should be possible to still add Contact-specific settings.
Similar: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1349https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/655URL protocol: respond to `jami:` URI scheme2022-11-10T08:41:55ZAndreas TraczykURL protocol: respond to `jami:` URI schemeThis functionality was lost on Windows when migrating to the WiX installer.
1. Re-implement the install-time registry entry creation.
2. Implement URI handling.This functionality was lost on Windows when migrating to the WiX installer.
1. Re-implement the install-time registry entry creation.
2. Implement URI handling.Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/302Certain audio input devices not recognized + unexpected aggregate device beha...2023-05-05T19:44:04ZQ GLCertain audio input devices not recognized + unexpected aggregate device behaviorJami version 2.10 (20211215) running on macOS Catalina 10.15.7
After reading https://forum.jami.net/t/mac-audio-input-selection/1191, I made some calls using the computer's built-in microphone, [Soundflower](https://github.com/mattingal...Jami version 2.10 (20211215) running on macOS Catalina 10.15.7
After reading https://forum.jami.net/t/mac-audio-input-selection/1191, I made some calls using the computer's built-in microphone, [Soundflower](https://github.com/mattingalls/Soundflower), a USB microphone, and some aggregate devices made in Audio MIDI Setup, all of which work as expected in Audacity, Quicktime, and Chromium.
- Jami recognized the built-in and USB microphones, and they worked fine individually.
- Jami didn't recognize Soundflower or any aggregate device that included it.
- Jami recognized a built-in+USB aggregate device, but when it was selected, only the input from the built-in microphone was used. I deleted the device, recreated it, and tried again, and that time only the input from the USB microphone was used. Tried again, and it was back to only the built-in microphone. I couldn't find a pattern.
In all cases, the input volume sliders in System Preferences affected all devices normally.
I'm pretty new to this, so please let me know if there's anything else I should provide.