savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-01-03T02:01:58Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/916samsung galaxy j3 prime: Video and sound become choppy and call drops2022-01-03T02:01:58ZMaxim Cournoyersamsung galaxy j3 prime: Video and sound become choppy and call dropsBug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20210315-01
- Device model: Samsung Galaxy J3 (SM-J327W)
- Android version: 8.1.0
- On the Samsung Galaxy J3: Play Stor...Bug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20210315-01
- Device model: Samsung Galaxy J3 (SM-J327W)
- Android version: 8.1.0
- On the Samsung Galaxy J3: Play Store; on the other device: Tried with Play store (20210315-01) or jami-gnome built from the latest sources on GNU/Linux
## Steps to reproduce
- Can you reproduce the bug: With one of my contacts though which is using a SM-J327W device, it always occur on her side (their Jami app crashes after a while). I couldn't reproduce using a SM-J320W8 (a different, but close model).
- Steps:
1. Call Jami on a Samsung Galaxy J3 SM-J327W
1. The call originally proceeds normally, with good video and audio and a decent framerate (~15 fps on both ends).
1. After 2-5 minutes of call, the video and audio sent from the Galaxy J3 device becomes choppy, with the framerate dropping to near zero (0.09 fps) and eventually the call dropping.
- Actual result: The call drops after a while.
- Expected result: The video and audio should remain fluid, and the call should not drop even after a prolonged period of time.
## Additional information
The phone specs are available from https://www.phonearena.com/phones/Samsung-Galaxy-J3-Prime_id10506. It has the following processor and GPU:
- CPU: Quad-core, 1400 MHz, ARM Cortex-A53, 64-bit, 28 nm
- GPU: Adreno 308
- RAM: 1.5 GiBhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/642Screen sharing > Frames per second > Add 240 option2022-01-03T21:05:55ZovariScreen sharing > Frames per second > Add 240 option> The gamers out there are more likely to be interested in Samsung's new Odyssey Neo G8, a smaller entry than the company's well-known Odyssey G9 and Neo G9 , but with the same 1000R curve. The display's panel supports 4K resolution, a 2...> The gamers out there are more likely to be interested in Samsung's new Odyssey Neo G8, a smaller entry than the company's well-known Odyssey G9 and Neo G9 , but with the same 1000R curve. The display's panel supports 4K resolution, a 240hz refresh rate, and a 1ms response time. Samsung claims this is the first time all three of these high-end features have come together in a single package.
https://www.zdnet.com/article/samsung-debuts-trio-of-high-end-displays-ahead-of-ces-2022/
Does `a 240hz refresh rate` mean frames per second? If so, can `240` please be added to `Settings` > `Audio/Video` > `Screen sharing` > `Frames per second` drop-down?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1050Question about improvements2022-01-04T09:36:52ZSkretch1974Question about improvementsHello. In the process of testing the latest version of Android, we found some problems with the Xiaomi Poco F3 phone.
## Bug
* When the switch is set to automatically download the program when the phone is restarted, the program start...Hello. In the process of testing the latest version of Android, we found some problems with the Xiaomi Poco F3 phone.
## Bug
* When the switch is set to automatically download the program when the phone is restarted, the program starts, but it is impossible to get through or receive a message until you open the window of the program itself.
This is not always convenient, especially when there is a need to restart the phone, and the user may forget to enter the program and minimize it to the background.
## Features request:
1) Add the ability to activate the Ptt function and automatically play voice messages when they are received
> it is necessary for this function to provide a more convenient button on the smartphone screen.
>
> Ptt will allow operation on low-speed Internet networks, as well as through TOR (Orbot) or similar networks
2) you also need to add low-speed voice codecs (Melpe1200 (2400), Codec2, (Silk))
3) make an automatic Jitter buffer for voice communication via TOR ( Orbot), this will significantly increase the privacy of the application as a whole.
Thank you.
> Hello. In the process of testing the latest version of Android, we found some problems with the Xiaomi Poco F3 phone, when the switch is set to automatically download the program when the phone is restarted, the program starts, but it is impossible to get through or receive a message until you open the window of the program itself. This is not always convenient, especially when there is a need to restart the phone, and the user may forget to enter the program and minimize it to the background. Also, if necessary, add the ability to activate the Ptt function and automatically play voice messages when they are received; it is also necessary for this function to provide a more convenient button on the smartphone screen. Ptt will allow operation on low-speed Internet networks, as well as through TOR (Orbot) or similar networks, you also need to add low-speed voice codecs (Melpe1200 (2400), Codec2, (Silk)), and make an automatic Jitter buffer for voice communication via TOR ( Orbot), this will significantly increase the privacy of the application as a whole. Thank you.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1375Maximize when ringing.2022-01-05T14:53:31ZJorge L. CorreaMaximize when ringing.Hi, when my headphone are connected to the computer all sounds go to it. But, not always I'm with it in my ears. When someone call me I'm losing some call because I can't hear the audio notification. So, I think it will be very useful if...Hi, when my headphone are connected to the computer all sounds go to it. But, not always I'm with it in my ears. When someone call me I'm losing some call because I can't hear the audio notification. So, I think it will be very useful if we could configure something like auto maximize the application when receiving a call. Or, some type of visual notification.
I'm using on KDE.
Thank you!https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1057Succesful account setup and message history sync but unable to send/receive n...2022-01-06T01:13:04ZJamagrammaticSuccesful account setup and message history sync but unable to send/receive new messages - Android F-droid/Aurora Store CalyxOSI set up Jami on a new device and can sync previous messages but am unable to send/receive new messages.
I'm running Taranis 20211210-01 from the Aurora Store on a Google Pixel 5a running degoogled CalyxOS 2.11.0. I've also tried with ...I set up Jami on a new device and can sync previous messages but am unable to send/receive new messages.
I'm running Taranis 20211210-01 from the Aurora Store on a Google Pixel 5a running degoogled CalyxOS 2.11.0. I've also tried with the latest F-Droid version.
I've tried toggling various server settings which does not appear to help.
I'm using a VPN which I've also tried toggling on and off to no apparent effect.
I've enabled all permissions for Jami.
There are other issues that seem to indicate partial connectivity.
I have Taranis running on other devices, with same or similar setup (VPN etc) including Android (both with and without Google Play services), iOS and Windows 10 that are sending/receiving fine from the same Jami account.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1312Broken dbus interface2022-01-09T16:55:38ZalzxBroken dbus interfacehello there
I use Jami everyday, as VoIP client on Debian (still on Buster, previous stable version).
In time I even wrote some bash crontab scripts for automating stuff (reliably stopping vlc if there is an incoming call, answering a c...hello there
I use Jami everyday, as VoIP client on Debian (still on Buster, previous stable version).
In time I even wrote some bash crontab scripts for automating stuff (reliably stopping vlc if there is an incoming call, answering a call with a global KDE shortcut, etc). They use `dbus-monitor` and `qdbus`, it's awesome.<br>
**Unfortunately with `20210929` and later versions, the needed dbus interface is broken. I had to revert to `20210916`** to make my scripts work again.
Examples:
- this command
```
dbus-monitor --profile --address "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" "type='signal',sender='cx.ring.Ring',path='/cx/ring/Ring/CallManager',interface='cx.ring.Ring.CallManager'"
```
monitors the arrival of the signal `incomingCallWithMedia` in a crontab job of mine. Basically, when Jami rings as a phone. Now nothing is returned.
- this command
```
qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" --literal cx.ring.Ring /cx/ring/Ring/CallManager cx.ring.Ring.CallManager.accept $(qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" --literal cx.ring.Ring /cx/ring/Ring/CallManager cx.ring.Ring.CallManager.getCallList | sed "s/{/{\"number\":/g" | jq -r '.number')
```
answers the current incoming call on a bash script, useful for a global shortcut on the keyboard. Now it does nothing.
- after getting the current account string, e.g. `2**************4` , via the (still working) one-liner
```
jamiidstring="$(qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" cx.ring.Ring /cx/ring/Ring/ConfigurationManager cx.ring.Ring.ConfigurationManager.getAccountList)"
```
I can tell if there is a problem connecting to my Asterisk server via the commands
```
qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" --literal cx.ring.Ring /cx/ring/Ring/ConfigurationManager cx.ring.Ring.ConfigurationManager.getVolatileAccountDetails $jamiidstring | sed "s/\(\[\|\]\)//g;s/Argument: a{ss} //g;s/ = / : /g" | jq '."Account.registrationCode"'
```
and
```
qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" --literal cx.ring.Ring /cx/ring/Ring/ConfigurationManager cx.ring.Ring.ConfigurationManager.getVolatileAccountDetails $jamiidstring | sed "s/\(\[\|\]\)//g;s/Argument: a{ss} //g;s/ = / : /g" | jq '."Account.registrationStatus"' | grep -P "\"REGISTERED"
```
In normal conditions, they return `"200"` and `"REGISTERED"`, now `"0"` and `"UNREGISTERED"` or `"ERROR_GENERIC"`. But I can still make and receive calls without problems.
As a **workaround**, I've installed the previous working version, mentioned above, with
```
mkdir -p /tmp/jamitmp; cd /tmp/jamitmp
cp /var/cache/apt/archives/jami*20210916*.deb .
sudo apt-get remove jami jami-qt jami-libclient jami-daemon
sudo dpkg -i *.deb
sudo apt-mark hold jami jami-qt jami-libclient jami-daemon
cd -;
```
But I won't be able to upgrade to future Jami packages until the dbus interface is fixed.<br>
As a temporary solution is provided, this isn't a high priority bug, but there is clearly some bad regression in the code somewhere.<br>
I'd like to add that these code lines are part of my own personal scripts so normally other humans don't see them otherwise they won't call anymore, which defeats the porpouse of automating Jami-related actions. I'm sorry if they or I appear disturbing in nature.<br>
Thank you for reading, I hope this can be fixed.<br>
Have a nice day Jami devs.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/61Handle layout options for translations2022-01-11T21:24:50ZMehdi GhayourHandle layout options for translationshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1058Contact screen overlaps with notification bar2022-01-13T14:19:12ZAltonsContact screen overlaps with notification bar
## Describe your environment
Please specify the following:
- Ring version: Taranis 20211210-01
- Device model: Samsung Galaxy Core Prime
- Android version: 5
- What build you are using: F-droid
## Steps to reproduce
- Can y...
## Describe your environment
Please specify the following:
- Ring version: Taranis 20211210-01
- Device model: Samsung Galaxy Core Prime
- Android version: 5
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
2. Open a conversation
3. Tap on the contact symbol, to open the contact view
- Actual result: the contact screen overlaps with the notification area!
- Expected result: Like all other screens, this window should start under the notification area.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/683Notification stuck on 'Syncing data...', SIP account cannot connect2022-01-13T14:51:36ZMaxim CournoyerNotification stuck on 'Syncing data...', SIP account cannot connectUsing the F-Droid build 20191208-01, I sometime get a 'Syncing data...' notification that won't go away. This seems to cause problems such the inability to connect to a SIP account or to connect.
Force stopping Jami (from the Android m...Using the F-Droid build 20191208-01, I sometime get a 'Syncing data...' notification that won't go away. This seems to cause problems such the inability to connect to a SIP account or to connect.
Force stopping Jami (from the Android menu) and restarting it resolves the issue. Attempting to disconnect and reconnect the problematic SIP account from the UI doesn't work. The spin wheel keeps spinning even after unchecking the SIP account enable checkbox.
Perhaps related messages, grabbed using logcat on the Android device:
```
01-01 10:33:41.517 17143 17143 I AEE/AED : pid: 10717, tid: 10741, name: Thread-1601 >>> cx.ring <<<
01-01 10:33:41.578 17143 17143 I AEE/AED : #00 pc 000000000047f068 /data/app/cx.ring-2/lib/arm64/libring.so
01-01 10:33:41.578 17143 17143 I AEE/AED : #01 pc 000000000048450c /data/app/cx.ring-2/lib/arm64/libring.so
01-01 10:33:41.578 17143 17143 I AEE/AED : #02 pc 000000000069afa4 /data/app/cx.ring-2/lib/arm64/libring.so (pj_timer_heap_poll+220)
01-01 15:03:29.114 20589 20589 I AEE/AED : pid: 17147, tid: 17167, name: DRing >>> cx.ring <<<
01-01 15:03:29.156 20589 20589 I AEE/AED : #00 pc 000000000047f068 /data/app/cx.ring-2/lib/arm64/libring.so
01-01 15:03:29.156 20589 20589 I AEE/AED : #01 pc 000000000048450c /data/app/cx.ring-2/lib/arm64/libring.so
01-01 15:03:29.156 20589 20589 I AEE/AED : #02 pc 000000000069afa4 /data/app/cx.ring-2/lib/arm64/libring.so (pj_timer_heap_poll+220)
01-03 08:22:27.362 6623 6645 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x50 in tid 6645 (Thread-1814)
01-03 08:22:27.387 11456 11456 I AEE/AED : pid: 6623, tid: 6645, name: Thread-1814 >>> cx.ring <<<
01-03 08:22:27.439 11456 11456 I AEE/AED : #00 pc 000000000047f068 /data/app/cx.ring-2/lib/arm64/libring.so
01-03 08:22:27.440 11456 11456 I AEE/AED : #01 pc 000000000048450c /data/app/cx.ring-2/lib/arm64/libring.so
01-03 08:22:27.440 11456 11456 I AEE/AED : #02 pc 000000000069afa4 /data/app/cx.ring-2/lib/arm64/libring.so (pj_timer_heap_poll+220)
01-03 18:04:45.254 22497 22497 I AEE/AED : pid: 11459, tid: 11478, name: Thread-2144 >>> cx.ring <<<
01-03 18:04:45.307 22497 22497 I AEE/AED : #00 pc 000000000047f068 /data/app/cx.ring-2/lib/arm64/libring.so
01-03 18:04:45.307 22497 22497 I AEE/AED : #01 pc 000000000048450c /data/app/cx.ring-2/lib/arm64/libring.so
01-03 18:04:45.307 22497 22497 I AEE/AED : #02 pc 000000000069afa4 /data/app/cx.ring-2/lib/arm64/libring.so (pj_timer_heap_poll+220)
01-04 12:16:00.324 2594 3571 I InputMethodManagerService: Disable input method client, pid=662
01-04 12:16:00.662 430 7775 I BufferQueueProducer: [StatusBar](this:0x7f72bcac00,id:24,api:1,p:2936,c:430) connect(P): api=1 producer=(2936:com.android.systemui) producerControlledByApp=true
01-04 12:16:01.126 662 662 V PhoneWindow: DecorView setVisiblity: visibility = 4 ,Parent =android.view.ViewRootImpl@b16369c, this =com.android.internal.policy.PhoneWindow$DecorView{6562469 I.E...... R......D 0,0-1080,1920}
```
After attempting to manually disable than re-enable the SIP account in the "Manage accounts" view:
```
01-04 12:18:54.585 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.22 dur=1013.15 max=49.31 min=6.48
01-04 12:18:55.597 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.30 dur=1011.56 max=21.44 min=12.40
01-04 12:18:55.936 662 852 D ConnectivityManager.CallbackHandler: CM callback handler got msg 524294
01-04 12:18:56.608 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=58.34 dur=1011.32 max=66.76 min=5.61
01-04 12:18:57.620 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.25 dur=1012.47 max=21.36 min=14.01
01-04 12:18:58.634 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.17 dur=1013.87 max=20.53 min=12.81
01-04 12:18:58.976 662 852 D ConnectivityManager.CallbackHandler: CM callback handler got msg 524294
01-04 12:18:59.645 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.36 dur=1010.87 max=53.90 min=4.04
01-04 12:18:59.656 662 675 D libdring: Saving Configuration to XDG directory /data/user/0/cx.ring/app_config/dring.yml
01-04 12:18:59.663 662 675 D libdring: doRegister montreal6.voip.ms
01-04 12:18:59.663 662 675 D libdring: try to resolve 'montreal6.voip.ms' (port: 0)
01-04 12:18:59.663 662 675 D libc-netbsd: [getaddrinfo]: caller process=cx.ring
01-04 12:18:59.663 662 675 D libc-netbsd: getaddrinfo( app_uid:10209
01-04 12:18:59.663 662 675 D libc-netbsd: getaddrinfo() uid prop:
01-04 12:18:59.663 662 675 D libc-netbsd: getaddrinfo() getuid():10209
01-04 12:18:59.663 662 675 D libc-netbsd: [getaddrinfo]: mtk ai_addrlen=0; ai_canonname=(null); ai_flags=0; ai_family=0
01-04 12:18:59.664 662 675 D libc-netbsd: [NET] android_getaddrinfo_proxy get netid:0
01-04 12:18:59.693 662 675 D libc-netbsd: [NET] android_getaddrinfo_proxy-, success
01-04 12:18:59.693 662 675 D libc-netbsd: getaddrinfo: montreal6.voip.ms get result from proxy gai_error = 0
01-04 12:18:59.694 662 675 W libdring: Creating transport
01-04 12:18:59.694 662 675 W libdring: Recycling transport 0.0.0.0:0
01-04 12:18:59.694 662 675 D libdring: SipTransport@0x7f592b7618 {tr=0x7f5927f028 {rc=24}}
01-04 12:19:00.653 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.53 dur=1007.77 max=22.99 min=11.45
01-04 12:19:01.664 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.33 dur=1011.09 max=19.29 min=13.68
01-04 12:19:02.677 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.21 dur=1013.09 max=20.21 min=9.99
01-04 12:19:03.363 2098 2326 I MAL-Daemon: ( mdfx_event_do_statistic, 153) mdfx_event_do_statistic(): [STATISTIC] TID = 2326 has used 705266208 bytes!!
01-04 12:19:03.692 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.12 dur=1014.95 max=33.42 min=13.22
01-04 12:19:04.704 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.30 dur=1011.66 max=26.93 min=5.98
01-04 12:19:05.714 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.41 dur=1009.93 max=47.09 min=7.84
01-04 12:19:06.726 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.26 dur=1012.21 max=21.78 min=10.73
01-04 12:19:07.433 2594 2853 W SensorService: D/Accel(x, y, z, t) = ( -0.2, -0.0, 9.8, 307568594ms), calendar = 1578158347, sys_time = 307568662ms
01-04 12:19:07.740 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.16 dur=1014.00 max=36.33 min=5.61
01-04 12:19:08.752 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.25 dur=1012.48 max=21.44 min=13.35
01-04 12:19:09.763 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.36 dur=1010.67 max=21.88 min=13.64
01-04 12:19:10.775 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=58.28 dur=1012.29 max=47.37 min=4.18
01-04 12:19:11.787 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.28 dur=1011.87 max=36.05 min=8.68
01-04 12:19:12.799 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.28 dur=1011.88 max=18.26 min=15.04
01-04 12:19:13.043 2594 2694 D AutomaticBrightnessController: calculateAmbientLux: totalWeight=3.2805E7, newAmbientLux=63.74662
01-04 12:19:13.811 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.25 dur=1012.38 max=20.72 min=14.29
01-04 12:19:14.823 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.28 dur=1012.00 max=22.17 min=12.24
01-04 12:19:15.832 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.49 dur=1008.37 max=38.72 min=4.86
01-04 12:19:16.846 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.14 dur=1014.31 max=22.63 min=12.72
01-04 12:19:17.859 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.20 dur=1013.36 max=31.71 min=7.78
01-04 12:19:18.871 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.29 dur=1011.85 max=20.26 min=13.25
01-04 12:19:19.883 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.31 dur=1011.49 max=19.19 min=13.23
01-04 12:19:20.893 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.39 dur=1010.22 max=39.22 min=3.21
01-04 12:19:21.906 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.19 dur=1013.42 max=34.93 min=4.71
01-04 12:19:22.919 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.26 dur=1012.23 max=17.26 min=15.69
01-04 12:19:23.931 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.24 dur=1012.56 max=23.24 min=11.76
01-04 12:19:24.942 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.33 dur=1011.14 max=18.33 min=14.57
01-04 12:19:25.954 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.32 dur=1011.53 max=37.02 min=6.48
01-04 12:19:26.966 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.30 dur=1011.68 max=25.04 min=11.50
01-04 12:19:27.978 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.23 dur=1012.83 max=23.44 min=10.30
01-04 12:19:28.990 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.31 dur=1011.48 max=32.25 min=6.71
01-04 12:19:30.008 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=58.92 dur=1018.27 max=46.05 min=8.78
01-04 12:19:31.014 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.66 dur=1005.57 max=19.47 min=11.28
01-04 12:19:32.026 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.26 dur=1012.42 max=32.25 min=12.94
01-04 12:19:33.037 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.37 dur=1010.56 max=32.00 min=7.15
01-04 12:19:34.049 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.25 dur=1012.43 max=20.62 min=13.72
01-04 12:19:34.662 2151 2151 I thermal_repeater: select timeout
01-04 12:19:35.063 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.17 dur=1014.11 max=44.30 min=6.58
01-04 12:19:35.662 2594 2853 W SensorService: D/Accel(x, y, z, t) = ( -0.2, -0.0, 9.8, 307596833ms), calendar = 1578158375, sys_time = 307596891ms
01-04 12:19:36.076 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.27 dur=1012.35 max=45.08 min=6.19
01-04 12:19:37.086 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.37 dur=1010.53 max=47.00 min=6.62
01-04 12:19:38.098 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.30 dur=1011.58 max=19.05 min=14.56
01-04 12:19:39.110 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.28 dur=1011.93 max=18.62 min=14.25
01-04 12:19:40.121 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.33 dur=1011.12 max=20.49 min=13.39
01-04 12:19:41.134 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.21 dur=1013.13 max=38.62 min=6.01
01-04 12:19:42.144 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.36 dur=1010.52 max=30.85 min=5.53
01-04 12:19:43.157 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.23 dur=1012.81 max=18.32 min=14.85
01-04 12:19:44.168 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.36 dur=1010.71 max=32.25 min=12.62
01-04 12:19:44.287 662 852 D ConnectivityManager.CallbackHandler: CM callback handler got msg 524294
01-04 12:19:45.180 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=58.29 dur=1012.13 max=39.34 min=4.16
01-04 12:19:46.193 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.24 dur=1012.76 max=46.63 min=7.15
01-04 12:19:47.206 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.18 dur=1013.62 max=22.08 min=13.48
01-04 12:19:48.217 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.39 dur=1010.12 max=31.50 min=3.50
01-04 12:19:49.228 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.31 dur=1011.45 max=34.12 min=6.42
01-04 12:19:50.240 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.26 dur=1012.23 max=18.88 min=13.90
01-04 12:19:51.253 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.26 dur=1012.42 max=46.73 min=8.07
01-04 12:19:52.264 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.29 dur=1011.71 max=18.18 min=13.82
01-04 12:19:53.282 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.94 dur=1017.66 max=21.47 min=13.55
01-04 12:19:53.316 662 852 D ConnectivityManager.CallbackHandler: CM callback handler got msg 524294
01-04 12:19:54.288 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.63 dur=1006.13 max=22.89 min=12.78
01-04 12:19:55.301 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.19 dur=1013.38 max=20.31 min=14.10
01-04 12:19:56.311 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.42 dur=1009.75 max=50.45 min=5.30
01-04 12:19:57.325 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.20 dur=1013.37 max=29.67 min=9.70
01-04 12:19:58.336 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.31 dur=1011.47 max=19.26 min=14.67
01-04 12:19:59.344 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.52 dur=1008.01 max=20.83 min=8.39
01-04 12:19:59.370 662 852 D ConnectivityManager.CallbackHandler: CM callback handler got msg 524294
01-04 12:20:00.345 430 1230 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=57.94 dur=1000.95 max=57.02 min=5.69
01-04 12:20:01.355 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=59.39 dur=1010.19 max=48.18 min=6.43
01-04 12:20:02.366 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.33 dur=1011.13 max=28.15 min=7.81
01-04 12:20:03.379 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.22 dur=1012.94 max=20.91 min=13.10
01-04 12:20:04.391 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.30 dur=1011.59 max=18.34 min=14.77
01-04 12:20:05.405 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.13 dur=1014.55 max=20.00 min=13.56
01-04 12:20:06.414 430 522 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.50 dur=1008.33 max=22.72 min=10.56
01-04 12:20:07.427 430 1264 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.18 dur=1013.60 max=22.40 min=12.84
01-04 12:20:08.427 662 852 D ConnectivityManager.CallbackHandler: CM callback handler got msg 524294
01-04 12:20:08.430 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=58.86 dur=1002.46 max=32.02 min=11.19
01-04 12:20:09.088 2594 2694 D AutomaticBrightnessController: updateAmbientLux: Scheduling ambient lux update for 171526622171526622 (in 1999 ms)
01-04 12:20:09.434 430 7775 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.76 dur=1003.96 max=32.16 min=4.16
01-04 12:20:10.446 430 524 I BufferQueueProducer: [cx.ring/cx.ring.client.HomeActivity](this:0x7f71109400,id:1904,api:1,p:662,c:430) queueBuffer: fps=60.28 dur=1011.92 max=33.12 min=6.56
```https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1041two jami settings don't work in android2022-01-16T10:33:40Zhigol higoltwo jami settings don't work in androidHow to report a bug
-------------------
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update...How to report a bug
-------------------
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue instead of creating new one.
Bug report form
---------------
## Describe your environment
Please specify the following:
- Ring version:
- Device model:
- Android version:
- What build you are using: [jami.net | F-droid | Play Store | App store | your own (please specify commit id + ring daemon version or commit id)...]
## Steps to reproduce
- Can you reproduce the bug: [at will | occasionally | not at all]
- Steps:
1.
2.
...
- Actual result:
- Expected result:
## Additional informationhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/44Include source packages in Jami's apt repository2022-01-18T16:35:35ZMason HockInclude source packages in Jami's apt repositoryHi. I am a Trisquel contributor, and https://git.jami.net/savoirfairelinux/jami-packaging/issues/39 was recently brought to my attention. It would be nice to include the latest version of Jami in our backports repository. We currently...Hi. I am a Trisquel contributor, and https://git.jami.net/savoirfairelinux/jami-packaging/issues/39 was recently brought to my attention. It would be nice to include the latest version of Jami in our backports repository. We currently backport Jami from later versions of Ubuntu than our upstream, but since Jami is in Ubuntu's Universe repository these packages do not receive security updates. It would be preferable to include the version of Jami packaged for Ubuntu in your own apt repositories. We sometimes do this with packages from developers who provide their own apt repositories.
However, we require source packages to do this, and it looks like Jami's apt repositories only include binary packages. Would it be possible to also include source packages? I'm not sure whether you build your binary packages from source packages and simply don't upload the source packages, or whether you create binary packages directly. If it's the former, would you consider uploading your source packages? If it's the latter, would you consider creating source packages for Jami? Using `debian/*` from Debian Sid's source package for Jami might be a good starting point.Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/242Video encoding - Dynamically change the resolution of the encoded frames2022-01-18T22:20:21ZMohamed ChibaniVideo encoding - Dynamically change the resolution of the encoded framesBacklogMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/960Send Location Button Instead Creates Pop-up Map2022-02-03T18:24:00ZBurnTorSend Location Button Instead Creates Pop-up Map- Ring Version: Maloya 20210521-01
- Device Model: OUKITEL WP6
- Android Version: 10
- Google Play Store Version
Expected Action: When the send location button is clicked, it sends a preview image of a map that can be clicked to open th...- Ring Version: Maloya 20210521-01
- Device Model: OUKITEL WP6
- Android Version: 10
- Google Play Store Version
Expected Action: When the send location button is clicked, it sends a preview image of a map that can be clicked to open this map larger, along with 3 links. 1) A geo link for desktop clients, 2) A Google maps link for android devices and 3) An iMaps link for Apple devices.
Actual Action: Just pops up an obstructive map over both users chat dialogs from both ends, covering half the messages and allowing no option to get any directions to the other person of their geo location at all.https://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-daemon/-/issues/700UPnP - Make port ranges configurable2022-02-03T20:29:33ZMohamed ChibaniUPnP - Make port ranges configurableThe port ranges (TCP and UDP) used by upnp to port mapping allocation must be configurable (currently they are hard-coded).
A new API must be added to allow a user to set the ranges for both UDP and TCP ports. If not set, default values ...The port ranges (TCP and UDP) used by upnp to port mapping allocation must be configurable (currently they are hard-coded).
A new API must be added to allow a user to set the ranges for both UDP and TCP ports. If not set, default values be used.
Might be related to https://git.jami.net/savoirfairelinux/ring-daemon/-/issues/417Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/701Recheck all APIs2022-02-03T20:34:22ZSébastien BlinRecheck all APIs+ Remove unnecessary APIs
+ Homogeneize file naming
+ definitions URI/ids
+ Split ConfigurationManager+ Remove unnecessary APIs
+ Homogeneize file naming
+ definitions URI/ids
+ Split ConfigurationManagerBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/710Hardware acceleration - Daemon must compile if RING_ACCEL is not defined2022-02-03T20:48:13ZMohamed ChibaniHardware acceleration - Daemon must compile if RING_ACCEL is not definedUndefining RING_ACCEL fails the compilation of the daemon in many places.
Also, compilation check must use #if RING_ACCEL instead of #ifdef, because in Daemon configuration, a feature is disabled by setting it's macro to 0 (so still defi...Undefining RING_ACCEL fails the compilation of the daemon in many places.
Also, compilation check must use #if RING_ACCEL instead of #ifdef, because in Daemon configuration, a feature is disabled by setting it's macro to 0 (so still defined).Backloghttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/160Custom OpenDHT bootstrap server2022-02-03T21:48:10ZArtemy GavrelyukCustom OpenDHT bootstrap serverI haven't find an option to use a custom OpenDHT bootstrap server. Seems like it's absent like a custom TURN-server (jami-client-ios#60). It could be great to have both of them. In my case it could help to investigate huge lags in messag...I haven't find an option to use a custom OpenDHT bootstrap server. Seems like it's absent like a custom TURN-server (jami-client-ios#60). It could be great to have both of them. In my case it could help to investigate huge lags in message delivery.Backloghttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/6Maintain a RPM Fusion package2022-02-04T10:38:17ZNokia808Maintain a RPM Fusion packageHi. I would like to suggest on Ring team to make their Fedora official package, available in Fedora official repositories instead of being - as the current case now - available on repositories of Ring project itself.
This could be trul...Hi. I would like to suggest on Ring team to make their Fedora official package, available in Fedora official repositories instead of being - as the current case now - available on repositories of Ring project itself.
This could be truly applied for Ubuntu & Debian also.
I mean official Ring packagers team use official repositories of Ubuntu, Debian & Fedora directly to post their official Ring packages. This will be better, isn't it ?
Related: https://git.jami.net/savoirfairelinux/jami-packaging/issues/8Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1390[Feature request] Mute All Participants in One Click / Disable all Participan...2022-02-04T22:32:30ZElys[Feature request] Mute All Participants in One Click / Disable all Participants VideoAs far as I know moderators can mute/unmute participants but is it possible to mute all participants in one click?
So just moderators are able to use their microphone ?
Example: https://chrome.google.com/webstore/detail/mute-all-on-meet...As far as I know moderators can mute/unmute participants but is it possible to mute all participants in one click?
So just moderators are able to use their microphone ?
Example: https://chrome.google.com/webstore/detail/mute-all-on-meet/adjoknoacleghaejlggocbakidkoifle?ucbcb=1
And it would be great if moderators were able to disable all participants video (so they can't use their camera anymore, but for example they are able to share their screen)? - By just using one general button.
And moderators should be able to enable individual webcams of the participants again. (Similar: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1349)