savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-08-24T15:54:14Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1353volume output too low (and speaker mode doesn't change anything)2023-08-24T15:54:14ZMaxim Cournoyervolume output too low (and speaker mode doesn't change anything)
Please specify the following:
- Jami version: 20230818-01
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. P...
Please specify the following:
- Jami version: 20230818-01
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Place video call from GNU/Linux client (but probably doesn't matter)
2. Receive video call on Android client
...
- Actual result: Volume is barely audible.
- Expected result: Volume should be loud, when volume is maxed out and speaker mode is on.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1352Google TV 12 doesn't pick up sound from mic when making videocalls to other d...2023-09-03T02:48:34ZRichard BranchesGoogle TV 12 doesn't pick up sound from mic when making videocalls to other devicesDevices involved in the test:
Onn 2023 with Google TV 12.
Homatics Box R 4K Plus with Android TV 11.
When I make videocalls from my Google TV device with Android 12 to my Windows 10 computer or to my Android TV device with Android 11,...Devices involved in the test:
Onn 2023 with Google TV 12.
Homatics Box R 4K Plus with Android TV 11.
When I make videocalls from my Google TV device with Android 12 to my Windows 10 computer or to my Android TV device with Android 11, the microphone from the webcam connected to the Google TV device with Android 12 doesn't pick up any sounds, it's completely mute, however, when I make videocalls from the Windows 10 computer or from the Android TV device with Android 11 to the Google TV device with Android 12, the microphone picks all sounds correctly.
Please specify the following:
- Jami version: 20230818-01
- Device model: Onn 2023, Homatics Box R 4K Plus
- Android version: Android 11, Android 12 and Windows 10.
- What build you are using: Play Storehttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1295Jami is unable to use the local area network without a network connection2024-01-19T20:13:44Zsession 21Jami is unable to use the local area network without a network connectionWhen only the local LAN is connected, devices cannot communicate with each other.
Because Jami seems to have to be connected to the internet to use it. If there is no internet, Jami will prompt 'No network connection'.
This situation s...When only the local LAN is connected, devices cannot communicate with each other.
Because Jami seems to have to be connected to the internet to use it. If there is no internet, Jami will prompt 'No network connection'.
This situation should be easily reproducible, but I am still willing to provide relevant records if gentlemen need them.
I think that if it can be compatible with a local area network, not just the internet, it may allow Jami to have similar functions as Briar, and Jami can make voice and video calls, which is a great feature of Jami.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1233Calls to Android client is not workable (private JAMI network)2023-07-26T13:49:31ZAleksey KvasnikovCalls to Android client is not workable (private JAMI network)We roll-out JAMI in the network without Internet access. Network have 5 IP subnets. In 2 subnets we have Windows 10 with JAMI clients, in 2 subnets we have Android phones with JAMI clients, installed from Google Play. In the last subnet ...We roll-out JAMI in the network without Internet access. Network have 5 IP subnets. In 2 subnets we have Windows 10 with JAMI clients, in 2 subnets we have Android phones with JAMI clients, installed from Google Play. In the last subnet we have Debian 11 server with dhtnode installed from APT package. We use this dhtnode as a bootstrap for all clients. All other settings disabled. For Android we disable push notifications and allow JAMI to run in background.
Between Windows clients everything works OK - we can call, send messages and files. Between Windows and Android we can send messages and files. Call from Android to Windows work fine (video and audio). In case if we call from Windows to Android, Android client cannot pickup call. We press button, but no effect. Telephone coninue ringing. If we disconnect call from Windows side - no effect, Android continue ringing. After some time ringing stops, but app not working and suggest to return to ongoing call. If I close app, it will not help - still suggesting to return to ongoing call. Only after phone restart JAMI app become workable. I collect two log files in Android app in the moment, when call from Windows was received and I cannot pickup call.
Jami version 20230310-01
Phone - Samsung A32
Android 13
Windows 10 19045.2728
Jami version 202303031415
I should mention what we try 3-4 different phones and 2-3 different Androids client for JAMI. Problem exactly same.
Also exactly same problem arise when we call between two Android phones.
[log_20230407_125847_4077836806239187095.log](/uploads/ee71c0f0d2c056db93ceed01b38d0800/log_20230407_125847_4077836806239187095.log)
[log_20230407_133601_2759086551447336315.log](/uploads/f5dba07503e2dac5e3ff091d99958e0f/log_20230407_133601_2759086551447336315.log)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1217Switch Between Portrait and Landscape Orientation does not work if you share ...2024-01-10T16:18:31ZElysSwitch Between Portrait and Landscape Orientation does not work if you share your screen immediately; 180° does generally not workSteps to reproduce:
2 devices (Android and Android)
or
Android and Windows 10
Android smartphone:
1)make a video call
you can see the your face
2)Rotate the smartphone
The other person (B) can see Person A in landscape (horizontal) m...Steps to reproduce:
2 devices (Android and Android)
or
Android and Windows 10
Android smartphone:
1)make a video call
you can see the your face
2)Rotate the smartphone
The other person (B) can see Person A in landscape (horizontal) mode (other device)
3)Now if you - Person A - start to share your screen Person B can see the screen in landscape (horizontal) mode [**Windows 10**: Here **crash** https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/536]
**BUT**
If you make a video call and share your screen immediately and rotate the screen, Person B only sees the screen horizontal BUT in portrait mode! [same issue using Jami,Windows 10]
Example:
![ScreenshotNOautorotate](/uploads/e949197ad9e27adc1837719f0f5efd55/ScreenshotNOautorotate.jpg)
Device B can have **Windows AND Android OS**
Auto rotate works if I start call horizontally!https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1129Issue if you add a participant to a video call2024-02-15T09:09:34ZElysIssue if you add a participant to a video callAndroid: 20220906-01
Windows 10: 202209300958
Steps to reproduce:
Android: You have only one own account ("myusername1") with contacts like "myusername2" and "myusername3"<br>
Windows 10: You have multiple own accounts ("myusername2")...Android: 20220906-01
Windows 10: 202209300958
Steps to reproduce:
Android: You have only one own account ("myusername1") with contacts like "myusername2" and "myusername3"<br>
Windows 10: You have multiple own accounts ("myusername2") but always the same contact ("myusername3")
1. Make a video call Android ("myusername1") -> Windows 10 ("myusername2")
2. Android: You can view the video of the Windows 10 user
3. Android: Add participant (Windows 10 contact: "myusername3")
4. Android: All videos are gone; you just view your own video preview
5. Windows 10: You can actually see three videos but all are black
Windows 10: If you want to view most of the videos (again) you have to select another own (second) account and return to your other (first) account to view the video again.
Sometimes you will be able to view the video on Android again.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1104Jami doesn't show any notification for incoming calls on TV2023-08-15T18:40:12ZRichard BranchesJami doesn't show any notification for incoming calls on TVWhen a call or videocall is incoming, I only hear the ringtone but no notification appears and when I open the app, the call gets disconnected immediately.
This happens on Android 11 whether on the Android TV UI or the Google TV UI.When a call or videocall is incoming, I only hear the ringtone but no notification appears and when I open the app, the call gets disconnected immediately.
This happens on Android 11 whether on the Android TV UI or the Google TV UI.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1094High mobile data consumption2023-07-08T07:41:39ZBruno KleinertHigh mobile data consumptionHi,
I experienced high and excessive mobile data consumption on a Samsung and a Huawei device.
Jami was used on both devices for about 3 hours. Less than 15 text messages were exchanged between both devices. On both devices the 'share ...Hi,
I experienced high and excessive mobile data consumption on a Samsung and a Huawei device.
Jami was used on both devices for about 3 hours. Less than 15 text messages were exchanged between both devices. On both devices the 'share location for 1 hour' function was enabled twice.
The Samsung device moved often between outside locations with good mobile network reception and underground locations with poor mobile network reception (I used the metro a few times). The Huawei device remained outside with permanent good mobile network reception.
On both devices, Jami was used without WiFi for the first time.
Samsung:
* Galaxy A52 with Android 12
* Jami 'Taranis 20220311-01', installed via F-Droid
* DHT Proxy function enabled
Huawei:
* Jami, version unknown, installed most likely via Google Play Store
* DHT Proxy function setting unknown
After 3 hours, the devices showed the following data consumptions:
* 340MB on the Samsung device
* 9,5GB (It's indeed Gigabytes) on the Huawei device
Can I provide any other information from the Samsung device that helps to track this issue down?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1092Cannot connect to android phone to start call2022-04-12T14:37:04ZAnjandev MomiCannot connect to android phone to start callCall receiver (call them Alice) that I cannot connect to is running android 12 on a Samsung Galaxy S20 FE. Alice never gets notification of incoming call.
I ran 2 tests:
1. From my Alpine Linux desktop to Alice's phone
[AnjanLinux.lo...Call receiver (call them Alice) that I cannot connect to is running android 12 on a Samsung Galaxy S20 FE. Alice never gets notification of incoming call.
I ran 2 tests:
1. From my Alpine Linux desktop to Alice's phone
[AnjanLinux.log](/uploads/a1e3e8390ec9c6f32faa14dbb45be43c/AnjanLinux.log)
[call_alice_recievingLinux.log](/uploads/a8ac18b78cb84a552ded0127bc971202/call_alice_recievingLinux.log)
2. From my Android phone (moto g stylus) to Alice's phone
[Anjanandroid.log](/uploads/e5058d61ab93e18a434004771c987fdf/Anjanandroid.log)
[call_alice.log](/uploads/8ed3abcca46cfac2f464e55d6b9b5c47/call_alice.log)
Im using the flatpak version on my desktop and we are both using the latest version from f-droid on our phones.
I can reproduce this bug at will.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1065Media Change - use requestMediaChange instead of deprecated APIs2024-03-05T19:33:48ZMohamed ChibaniMedia Change - use requestMediaChange instead of deprecated APIsrequestMediaChange API allows modifying many attributes of the media (add new media, mute media, change source, ...). This API must be used instead of the deprecated APIs such muteMedia and switchInput.requestMediaChange API allows modifying many attributes of the media (add new media, mute media, change source, ...). This API must be used instead of the deprecated APIs such muteMedia and switchInput.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999Incoming call is displayed to user after it has immediately failed (for a few...2023-10-29T19:53:06ZElysIncoming call is displayed to user after it has immediately failed (for a few times) / or you hear the call ringing without viewing any notificationUpdate: You can get the call without any noticiation but you'll hear the ringing forever: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_45879
Update: https://git.jami.net/savoirfairelinux/jami-client-androi...Update: You can get the call without any noticiation but you'll hear the ringing forever: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_45879
Update: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_44908
Always reproduced!
---
using newest version of Jami Android 20221107-01 and Jami 202211101600 Windows 10
I was able to reproduce again (sameuseraccount (Android) -\> sameuseraccount (Windows 10)).
Reproduced if two devices use **different networks AND** if two devices use the **same WLAN**
I think if you make a call useraccount 1 -\> useraccount 2 even if the green dot of your own contact in the contact list on Windows 10 is not visible the Android version will still "remember" the call and as soon as the green dot is visible (on Windows 10) the call will succeed.
EDIT: **Maybe you have to make a call successfully before (Android -\> Windows 10) and then JUST exit Windows 10 to reproduce.**
EDIT: I think I now know why and how it fails?
1. Make a call before you can view the green dot of your contact (?)
2. Make a call shortly before you can view the green dot of your contact (?) / or as soon as you would see the green dot
3. The other peer should receive the call after ten seconds (but you'll never know)?
Sometimes you have to exit Jami (just) on the smartphone a couple of times (over 20 times?) to reproduce?
Just reproduced a couple of times again:
**DISABLE "run in background"**
Steps to reproduce (You actually just have to exit ONE device; NOT BOTH, but I think you have to enable TURN, even if you use the same network) (See: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_38603)
---
EDIT: I was also able to reproduce **Android -\> Windows 10** (**sameuseraccount -\> sameuseraccount**); different network
(The Windows 10 user and the Android user have themselves already in the contact list)
Steps to reproduce:
1. Android: Open Jami and keep Jami running (more than 30 seconds)
2. Now the Windows 10 user opens Jami
3. As soon as the Windows 10 user opens Jami, (BEFORE the green dot of the Android user is visible on Windows 10) the Android user makes one call (Android -\> Windows 10), quickly a second call and maybe you also need a third call - they will all immediately fail
4. Now wait for a few seconds or even longer (nobody does anything; meanwhile the Windows 10 views the green dot of the Android user)
5. The Windows 10 user will receive a call (but the Android user will never notice)
I think you can't reproduce if the green dot is not gone- for example if just the Windows 10 user exits Jami but as soon as he opens Jami again the green dot is already there? In that case I wasn't able to reproduce I think ...
---
**Android \<-\> Android**
1. Open Jami and quickly make a first call (maybe even before I can see the green dot ?? (Can't tell because of issue https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/994) - it will immediately fail
2. Now after a few seconds (or even just one second) make the second call - it will immediately fail
3. Now wait
4. Now the Android tablet will receive a call after 10 seconds or more (but the smartphone user will never be able to view the call)
I had a few possibilities:
- Sometimes you don't reproduce?
- Sometimes the other device just gets one call (2 calls failed)
- Sometimes the other device gets both two calls (2 calls failed)
- Sometimes you need to make a third call (after a few seconds) and the other device will receive the third call AND the second call
---
Option B:
Another option how to reproduce this issue:
EDIT: I think I was even able to reproduce even if you make a call after you can view the green dot of the Android contact but BEFORE the green dot of your own account refreshes again.
1. Just open Jami on Android (never exit; keep Jami running at least 30 seconds; Maybe you've already closed Jami on Windows 10)
2. Now the Windows 10 user opens Jami
3. Make a call Android -\> Windows 10 (before the Windows 10 user can view the green dot of the Android contact): It will immediately fail
4. Make a second call Android -\> Windows 10 (before the Windows 10 user can view the green dot of the Android contact): It will try to connect; However (just) the Android user now stops the call ("connecting" \[although this time it might would work\])
5. Now the Android user makes another call - it will immediately fail (again)
6. Maybe the Android user makes again another call - immediately fail (Sometimes it it will show "connecting" again and the call might successfully work)
7. Maybe all peers need to wait a few seconds
8. Now just the Windows 10 user will receive a call - the Android user will never noticehttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1630Links not clickable2024-03-28T00:05:08ZPierre NicolasLinks not clickable## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Send a link
2. Click on the link
- Actual result: Nothing happens
...## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Send a link
2. Click on the link
- Actual result: Nothing happens
- Expected result: Should open web browser.
## Additional information
![image](/uploads/1f7a069536e03e0f421c4d5e84cdf5e0/image.png)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1629First back press close conversation instead of settings2024-03-28T00:05:08ZPierre NicolasFirst back press close conversation instead of settings## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Actual result: The conversation is closed at my first click
- Expected result: It sho...## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Actual result: The conversation is closed at my first click
- Expected result: It should close the settings page.
## Additional information
![Screen_recording_20240315_105829](/uploads/58aa1e8b141426437ee7ddfedb775b04/Screen_recording_20240315_105829.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1400Nothing happens when I tap "DOWNLOAD"2023-10-14T09:34:23ZannaNothing happens when I tap "DOWNLOAD"![Screenshot](/uploads/6dc4550e2e7701c0b5ef6851c9a92dd7/Screenshot.png)
Incidentally, it's a file that was originally sent to my desktop client even before I exported Jami to my Android device.
Eleutheria - 20231006-01![Screenshot](/uploads/6dc4550e2e7701c0b5ef6851c9a92dd7/Screenshot.png)
Incidentally, it's a file that was originally sent to my desktop client even before I exported Jami to my Android device.
Eleutheria - 20231006-01https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1399Crashes when scrolling or fast scrolling in Contact Details > Documents2023-10-11T12:53:46ZannaCrashes when scrolling or fast scrolling in Contact Details > DocumentsWhen scrolling or fast scrolling in Contact details > Documents, either the crash "Jami keeps stopping" occurs or the window crashes so that I find myself back in the chat.
Reminds me a bit of https://git.jami.net/savoirfairelinux/jami-...When scrolling or fast scrolling in Contact details > Documents, either the crash "Jami keeps stopping" occurs or the window crashes so that I find myself back in the chat.
Reminds me a bit of https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1254
Eleutheria - 20231006-01https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1385Jami will still run in background for a few seconds/minutes or even longer if...2024-01-08T16:59:32ZElysJami will still run in background for a few seconds/minutes or even longer if you exitusing the newest beta version of Jami
and Android 13
Go to advanced settings:
You've always
* disabled "Start Jami on startup",
* disabled "Run in background"
* optional: disable "Push notifications"
Steps to reproduce:
* After you...using the newest beta version of Jami
and Android 13
Go to advanced settings:
You've always
* disabled "Start Jami on startup",
* disabled "Run in background"
* optional: disable "Push notifications"
Steps to reproduce:
* After you've rebooted your phone you might have to make a call once (Desktop -\> Android)
* After you've used Jami exit Jami on Android (but the desktop user (same account) will never exit)
* Even after a few seconds or even minutes you can still call the Android user (Call: samecontact -\> samecontact) - Jami will open the Android app - but this might not be always the case - sometimes calls will immediately fail - sometimes the Android user will receive the call
Expected: Shouldn't the Android user never receive any call anymore?
If you don't use the same user account (username1 \<-\> username1) but a different (username2 -\> username1) Jami on desktop will receive an invitation of username2 and the account username1 will now have username2 twice in the contact list?
---
Even if you exit the desktop app and open Jami on desktop again still same behaviour - Maybe related: https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1352
Two more things:
* Maybe this happens if you are using the same Jami account on multiple devices
* Maybe this also / or only happens if you exit during a file transfer?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1355Horrible video decoding artifacts (sender: GNU/Linux, receiver: Android)2024-01-10T17:22:54ZMaxim CournoyerHorrible video decoding artifacts (sender: GNU/Linux, receiver: Android)## Describe your environment
Please specify the following:
- Jami version: 20230818.01
- Device model: Galaxy Tab S2
- Android version: Android 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bu...## Describe your environment
Please specify the following:
- Jami version: 20230818.01
- Device model: Galaxy Tab S2
- Android version: Android 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Place a video call from GNU/Linux to Android client. Make some movements to more easily trigger the problem.
2. Observe the video quality received on the Android client.
- Actual result: Video quality is abysmal, with the caller at points hardly discernible (see images).
- Expected result: Received video should be free of serious artifacts and have a decent quality.
## Additional information
The sender video is from a Logitech G920 camera and hardware acceleration is in effect (Radeon R9 290 with amdgpu driver), in case this matters.
![Screenshot_20230806-125331.png](/uploads/eaf9e213b21d91811b3d7c14a3ecea28/Screenshot_20230806-125331.png)
![Screenshot_20230806-125639.png](/uploads/7d27e3b9fbaaa5726839789ce0161992/Screenshot_20230806-125639.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1340RTP Port Range Configuration in SIP Account gets to Defaults every time you r...2023-07-26T16:04:27Zdenn0nRTP Port Range Configuration in SIP Account gets to Defaults every time you restar the appEvery time you restart the app the RTP PORT configuration reset to he default Minimun 16384 and Maximum 32766
and I had to disconnect the Account restart the app reconfigure the Port Range and then reconnect the account to the change wo...Every time you restart the app the RTP PORT configuration reset to he default Minimun 16384 and Maximum 32766
and I had to disconnect the Account restart the app reconfigure the Port Range and then reconnect the account to the change works if you don't do in the correct order you get a connection error
## Describe your environment
Please specify the following:
Jami version: 20230502-01
Device model: Xiaomi Merlin mt6768
Android version: 11
Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:Create an SIP Account
1. Configure RTP Port Range and any other configuration The Sip Account needs
2. Reboot the Movil Or Restart the Jami App
...
- Actual result: the Rtp Port Range it's Change to the defaults Minimun 16384 and Maximum 32766
- Expected result: Keeps the Configuration
## Additional information
I Had test this on other devices whit same result !Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1338Jami for Android sends 1080p, 1440p and 4K video streams with a 4:3 aspect ra...2023-07-24T19:57:07ZRichard BranchesJami for Android sends 1080p, 1440p and 4K video streams with a 4:3 aspect ratio when using the front cameraPlease specify the following:
* Jami version: 20230714-01
* Device model: Moto G32
* Android version: Android 12.
* What build you are using: Play Store.
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Ope...Please specify the following:
* Jami version: 20230714-01
* Device model: Moto G32
* Android version: Android 12.
* What build you are using: Play Store.
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami app
2. Select a contact
3. Hit the videocall button
4. The videocall starts with no problem on both ends
- Actual result: 1080p, 1440p and 4K video streams are sent with a 4:3 aspect ratio when using the front camera, however, they are sent with the 16:9 aspect ratio when using the rear camera.
- Expected result: Looks like the Jami app must detect what resolutions the front camera supports and what resolutions the rear camera supports and display them in two separate settings, it appears the front camera only supports up to 1080p but I can't confirm it, but if the front camera also support 1440p and 4K, then the aspect ratio for both should be 16:9, otherwise, they should remain hidden.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1319UI glitch when selecting contacts for new swarm2023-07-12T18:05:40ZPierre NicolasUI glitch when selecting contacts for new swarm## Describe your environment
- Jami version:
- Device model: Samsung-T720
- Android version: 20230710-01
- What build you are using: own 575fc884dfb95e46ae9a8bad5e7bf15f7c5b6b2f
## Additional information
![random_bottomsheeti...## Describe your environment
- Jami version:
- Device model: Samsung-T720
- Android version: 20230710-01
- What build you are using: own 575fc884dfb95e46ae9a8bad5e7bf15f7c5b6b2f
## Additional information
![random_bottomsheetidalog](/uploads/4649284b55634abcda16abce10ab9972/random_bottomsheetidalog.mp4)