savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-03-30T15:45:42Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/917UPNP not working correctly when using Adguard2021-03-30T15:45:42ZChris OcelotUPNP not working correctly when using Adguard## Describe your environment
Please specify the following:
- Ring version: 20210226-01
- Device model: Oneplus 5T
- Android version: 10
- What build you are using: [Play Store]
## Steps to reproduce
- Can you reproduce the ...## Describe your environment
Please specify the following:
- Ring version: 20210226-01
- Device model: Oneplus 5T
- Android version: 10
- What build you are using: [Play Store]
## Steps to reproduce
- Can you reproduce the bug: [at will]
- Steps:
1. Download and install [Adguard](https://adguard.com/en/adguard-android/overview.html)
2. Use local VPN mode for Adguard.
3. Start Jami, enable UPNP
- Actual result: No UPNP port mapping created at all.
- Expected result: Jami creates UPNP port mapping.
- If Adguard is disabled, UPNP works as expected.
## Additional information
Openwrt debug log
```
Tue Mar 30 20:42:18 2021 daemon.info miniupnpd[10360]: HTTP REQUEST from [::ffff:192.168.1.137]:37384 : POST /ctl/IPConn (HTTP/1.1)
Tue Mar 30 20:42:18 2021 daemon.debug miniupnpd[10360]: Host: 192.168.1.1:5000
Tue Mar 30 20:42:18 2021 daemon.info miniupnpd[10360]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping
Tue Mar 30 20:42:18 2021 daemon.info miniupnpd[10360]: Client 192.168.1.137 tried to redirect port to 172.18.11.218
Tue Mar 30 20:42:18 2021 daemon.info miniupnpd[10360]: Returning UPnPError 718: ConflictInMappingEntry
```
So it seems that Jami is not able to recognize the correct local IP address, when the device is actually at 192.168.1.137, because of the presence of Adguard, Jami thinks 172.18.11.218 is local IP address.
I tried a debug app: [network utilities](https://play.google.com/store/apps/details?id=com.myprog.netutils)
It is able to correctly recognize the real IP address of the phone.https://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-daemon/-/issues/492libnatpmp is always used from contribs2023-05-05T19:02:06ZMaxim Cournoyerlibnatpmp is always used from contribsThe contrib build system relies on pkg-config to detect system libraries, as done here:
```
ifeq ($(call need_pkg,'libnatpmp'),)
PKGS_FOUND += natpmp
endif
```
This never marks natpmp as found, because libnatpmp doesn't install any pkg...The contrib build system relies on pkg-config to detect system libraries, as done here:
```
ifeq ($(call need_pkg,'libnatpmp'),)
PKGS_FOUND += natpmp
endif
```
This never marks natpmp as found, because libnatpmp doesn't install any pkg-config file (.pc), thus cannot be found via pkg-config.
Possible solution: Rather than reinvent the wheel in this contrib build system, perhaps we could use Autoconf as the configuration driver of the contribs build system, which is quite capable in this regard. It could return a list of targets needed from the contribs build system to be built, and add them as dependencies.https://git.jami.net/savoirfairelinux/jami-plugins/-/issues/17SDK: add dependsOn to preference structure2021-03-19T16:09:21ZAline Gondim SantosSDK: add dependsOn to preference structure"dependsOn" was added to preferences structure and is supported by the client-qt.
Plugins SDK should foresee this preference characteristic."dependsOn" was added to preferences structure and is supported by the client-qt.
Plugins SDK should foresee this preference characteristic.BacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/70Replace Statement database management with ORM such as Hibernate2021-03-17T20:17:11ZLarbi GharibReplace Statement database management with ORM such as HibernateAdrien BéraudGuillaume HellerLarbi GharibAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/126SIP account: could not detect audio only call2021-03-17T20:10:56ZKateryna KostiukSIP account: could not detect audio only callA video preview is showing for an incoming audio-only callA video preview is showing for an incoming audio-only callhttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/14Fancy hat plugin2021-04-14T15:08:13ZSébastien BlinFancy hat pluginCreate plugin to add accessories like hats, tiaras, glasses, wigs...Create plugin to add accessories like hats, tiaras, glasses, wigs...Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/907MIUI/Android's dark theme inverts my qr code image2021-03-15T17:55:08ZMIUI/Android's dark theme inverts my qr code imageWhen system option "dark mode" is enabled jami qr code becomes inverted no matter what theme is active as jami's option.
All dark theme's differences are:
1. three button backgrounds "QR code" "Share" "Link a new device" in "Account...When system option "dark mode" is enabled jami qr code becomes inverted no matter what theme is active as jami's option.
All dark theme's differences are:
1. three button backgrounds "QR code" "Share" "Link a new device" in "Account" tab,
2. in qr section there are qr image and "Share my QR" button,
3. in "conversations" tab in "About jami" the "credits" button background,
4. In account choosing menu, default profile pictures (only the "human" part), and in profile picture choosing dialog. The human part changes its color to black, while in chats those stay white
(Button backgrounds in 1, 2, 3 are white in jami's dark theme, and android's dark mode turns them to very dark color. But button text is still kind of readable because of blueish text color)
MIUI 12.0.1 Android 10https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/476No SIP registration due to bad network detection2021-03-15T14:53:10ZEnrico ScholzNo SIP registration due to bad network detectionjami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
*...jami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
```
<details>
<summary>Full Log</summary>
<pre>
$ ring.cx --debug
(jami-gnome:822803): GLib-DEBUG: 14:24:25.931: setenv()/putenv() are not thread-safe and should not be used after threads are created
** (jami-gnome:822803): DEBUG: 14:24:25.931: debug enabled
** Message: 14:24:25.933: Jami GNOME client version: development
** Message: 14:24:25.933: git ref: unknown
** (jami-gnome:822803): DEBUG: 14:24:25.933: enabling autostart
** (jami-gnome:822803): DEBUG: 14:24:25.933: checking /usr/share/jami-gnome/jami-gnome.desktop
(jami-gnome:822803): dconf-DEBUG: 14:24:25.933: watch_established: "/net/jami/JamiGnome/" (establishing: 1)
** (jami-gnome:822803): DEBUG: 14:24:25.934: '/home/ensc/.config/autostart/jami-gnome.desktop' is already a symlink to '/usr/share/jami-gnome/jami-gnome.desktop'
(jami-gnome:822803): dbind-WARNING **: 14:24:25.945: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de_DE
(jami-gnome:822803): GLib-GIO-DEBUG: 14:24:26.106: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): GLib-DEBUG: 14:24:26.178: unsetenv() is not thread-safe and should not be used after threads are created
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Connecting to session manager
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
Can't open file: "/home/ensc/.local/share/jami/606bab6fe62f6e4c/profile.vcf"
** (jami-gnome:822803): DEBUG: 14:24:26.254: notify server name: naughty, vendor: awesome, version: 3.5, spec: 1.0
(jami-gnome:822803): Gtk-WARNING **: 14:24:26.255: Child name 'calls' not found in GtkStack
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.257: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 1)
invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.GoaVolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer. (g-dbus-error-quark, 3)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.413: watch_fast: "/org/gtk/settings/file-chooser/" (establishing: 0, active: 0)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.414: watch_established: "/org/gtk/settings/file-chooser/" (establishing: 1)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.565: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 2)
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.585: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_notify: /net/jami/JamiGnome/show-main-window
(process:822825): GLib-GIO-DEBUG: 14:24:26.661: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: NetworkManager not running
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: _g_io_module_get_default: Found default implementation netlink (GNetworkMonitorNetlink) for ?gio-network-monitor?
(WebKitWebProcess:822824): dbind-WARNING **: 14:24:26.672: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
(jami-gnome:822803): dconf-DEBUG: 14:24:26.701: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_notify: /net/jami/JamiGnome/window-maximized
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
** (jami-gnome:822803): WARNING **: 14:24:26.718: no primary network connection detected, check network settings
(process:822825): GLib-GIO-DEBUG: 14:24:26.740: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-height
(WebKitWebProcess:822824): GLib-GIO-DEBUG: 14:24:26.796: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): Gdk-CRITICAL **: 14:24:26.880: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-height
</pre>
</details>
I am not using Gnome and network is managed manually (no NetworkManager)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/905Feature request screen overlay detector2021-03-18T01:49:46ZFeature request screen overlay detectorScreenshots can be taken with apps that can draw over the screen without root. This looks more important than current forbidding.
Clearer description
https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/905#note_27199
"Br...Screenshots can be taken with apps that can draw over the screen without root. This looks more important than current forbidding.
Clearer description
https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/905#note_27199
"Briar" has developed this feature, and it doesn't let you enter passwords or chat until you figure out how to stop some of listed apps that have permission.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/902Send image/videos form gallery - AndroidTV2021-03-08T18:59:39ZAmirhossein NaghshzanSend image/videos form gallery - AndroidTVCurrently, it is not possible to send a saved picture or video. We can only use the camera to take pictures/videos.Currently, it is not possible to send a saved picture or video. We can only use the camera to take pictures/videos.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/898Feature request first start prompt for disabling battery optimizations2021-03-08T11:26:32ZFeature request first start prompt for disabling battery optimizationsIt is a system's prompt for "Special app access >> Disable battery optimizations" . I know that "p≡p | Pretty Easy Privacy (pEp)" app requests it on first start, and that "Whatsapp" uses that feature too.It is a system's prompt for "Special app access >> Disable battery optimizations" . I know that "p≡p | Pretty Easy Privacy (pEp)" app requests it on first start, and that "Whatsapp" uses that feature too.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1204Feature request: Improve blocking function and add anti-spam mechanism2021-03-07T11:43:53Ztid liFeature request: Improve blocking function and add anti-spam mechanismChinese user, Android side, currently using version 20210226-01 on F-Droid.
Maybe I don't know how to use it well, I found some problems and didn't find a solution by myself. Here are some questions and suggestions. Hope it can help to ...Chinese user, Android side, currently using version 20210226-01 on F-Droid.
Maybe I don't know how to use it well, I found some problems and didn't find a solution by myself. Here are some questions and suggestions. Hope it can help to improve Jami
Questions
1. About the blocking function
First, the contacts still appear in the conversation list after blocking. Second, when testing, if a stranger wants to add me, the logic of this blocking feature is surprising - to block, you have to become a contact before blocking, if you delete the contact, then the blocking is useless. Third, the blocking list can not delete contacts. If you want to remove a contact from it, you can only choose to add each other. Fourth, blocking will also appear in other cases of invalid.
Reproduce some cases of the above: When account A clicks the block button on the request when account B adds it, account B will appear directly in the conversation list and Jami show that it has been added as a contact. The other invalidation is that once Account A has initiated the message, the chat between the two parties is unobstructed after that.
The strange logic of the above blocking function baffles me.
2. About contact requests
As far as I know, Jami doesn't seem to have any mechanism to block spam contact requests locally. As long as you know the account ID, you can add them. Every time an account is added, the account receives a contact request, and due to the strange logic of the blocking feature, these contacts will fill up the conversation list if you choose to block them.
3. About other features
First, when switching between multiple accounts on the account details page, there may be a situation where the small avatar does not correspond to the large avatar below, or even all the content does not correspond (still the content of the account before switching). Secondly, if I don't give Jami permission to take photos when I show the QR code on the account details page, Jami will be stuck there, and the button in the top right corner will keep blinking. I don't think it's necessary to get permission when I show the QR code.
Suggestions
1. About blocking function and blocking list
I hope to add a switch to control whether to show the blocked people in the conversation list. And the contacts in blocking list can be unblocked. Because if there are no two sides added, it is not necessary to add each other after unblocking a stranger.
2. About contact request
I hope to add an optional verification function when adding contacts, such as questions, etc. TOX's mechanism can also be referred to. And it would be nice to allow accounts to be set up so that they can only add other contact but can not be added. But most importantly, whatever spam prevention mechanism is used, I hope that requests for accounts that do not pass verification can be set to not show.
Thanks a lot for reading my tedious statement, I hope it will help to improve Jami.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1202Feature request: Allow exporting/importing of conversations2022-09-09T15:31:03ZJivan PalFeature request: Allow exporting/importing of conversationsThis is particularly pertinent to mobile (Android/iOS) users, where manually getting the files is not possible unless the device is rooted/jailbroken. For example, I am currently faced with no ability to export my conversations from my A...This is particularly pertinent to mobile (Android/iOS) users, where manually getting the files is not possible unless the device is rooted/jailbroken. For example, I am currently faced with no ability to export my conversations from my Android device, because it is not rooted.
Please add the ability to export/import conversations (optionally along with all associated media that is still on the device) directly from the client in a standardised format that is accepted by all clients. This would e.g. allow a user of a non-rooted Android device to export their conversations from within the app to their Downloads folder, back up that file, and then re-import the conversations into a new instance of the app on the same device or another, regardless of platform. This also improves UX compared to the current method of manually grabbing relevant files from an instance.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/463Replace Portaudio with WASAPI to support communication device enumeration and...2021-03-22T19:50:52ZAndreas TraczykReplace Portaudio with WASAPI to support communication device enumeration and output loopbackAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/67Expired session will editing2021-02-24T17:40:41ZLarbi GharibExpired session will editingStart new session
Start editing
After few minutes user experiences issuesStart new session
Start editing
After few minutes user experiences issueshttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/119Please, write clear release notes at the AppStore2021-02-22T16:17:44ZArtemy GavrelyukPlease, write clear release notes at the AppStoreHello. I've found out that last three or five versions of Jami at AppStore has the following release notes: "bug fixes". This is very unclear for the user, what was fixed exactly.
Please, use more clear release notes when you publish a ...Hello. I've found out that last three or five versions of Jami at AppStore has the following release notes: "bug fixes". This is very unclear for the user, what was fixed exactly.
Please, use more clear release notes when you publish a new version of Jami at AppStorehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1189Feature Request: Allow to capture multiple audio sources at the same time2022-09-09T15:02:29ZElysFeature Request: Allow to capture multiple audio sources at the same timeI would be great if you were able to capture the computer's internal audio with just one click (while screen sharing; if you want to share the system audio too). An option you have if you are using obs studio ("enable desktop audio").
S...I would be great if you were able to capture the computer's internal audio with just one click (while screen sharing; if you want to share the system audio too). An option you have if you are using obs studio ("enable desktop audio").
So you can watch videos with sound and music and others can hear the sound and music too (without using an external microphone).https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/892different video resolutions: video lag2023-11-01T13:12:36ZElysdifferent video resolutions: video lagVideo call (Android):
If two users use different video resolutions audio and video are out of sync. (the the delay is 5 seconds)
For example: (settings: video resolution)
Person 1: video resolution 720p
Person 2: video resolution 1080p
...Video call (Android):
If two users use different video resolutions audio and video are out of sync. (the the delay is 5 seconds)
For example: (settings: video resolution)
Person 1: video resolution 720p
Person 2: video resolution 1080p
All persons have to change the video resolution to for example 720p AND restart Jami.https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/112feature request: add share extension so we can share URLs, photos, etc. to Ja...2023-06-21T18:53:19ZNick Econopoulyfeature request: add share extension so we can share URLs, photos, etc. to Jami contacts from outside the appI think this is the iOS extension that would be needed: https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/Share.html
It would be nice to directly share a URL from my browser to a Jami contact.I think this is the iOS extension that would be needed: https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/Share.html
It would be nice to directly share a URL from my browser to a Jami contact.Alireza ToghianiAlireza Toghiani