savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2020-04-03T20:56:43Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/663Video conferences issues2020-04-03T20:56:43ZSébastien BlinVideo conferences issues# Done (but need some clean)
+ LRC: manage joining calls from different accounts (https://review.jami.net/c/ring-lrc/+/12141)
+ LRC: Send signals for joinParticipant + joinConference (https://review.jami.net/c/ring-lrc/+/12141)
+ Client...# Done (but need some clean)
+ LRC: manage joining calls from different accounts (https://review.jami.net/c/ring-lrc/+/12141)
+ LRC: Send signals for joinParticipant + joinConference (https://review.jami.net/c/ring-lrc/+/12141)
+ Client gnome: add widget to add someone to the conference (https://review.jami.net/c/ring-client-gnome/+/12140)
+ Client gnome: fix renderer id issues (https://review.jami.net/c/ring-client-gnome/+/12140)
+ LRC + clients: Invite non in call contact to conference (WIP sblin + atraczyk, https://review.jami.net/c/ring-client-gnome/+/12140)
+ daemon: Remove pause from daemon (WIP atraczyk + sblin. Bug: remove participant is bugguy https://review.jami.net/c/ring-daemon/+/11312)
+ Android: video not shown
+ Daemon: join conferences broken
+ Daemon: video on the other side can froze
# In progress
# Todo
+ Client gnome: redo bar at the bottom of a call
+ LRC: create item for video conference? Wait for group chats to improve this?
Iteration 17 (Video conferences stabilization)Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/215Conferencing Problem2019-11-21T15:57:12ZRobert MathewsConferencing ProblemWish to inform that conferencing two parties in a audio conference has not been possible. I am using Mac OSX 10.11.6 and Jami -- Version 1 (20190902). **I have tried to follow directions, as it has appeared on jami.net.** The instruc...Wish to inform that conferencing two parties in a audio conference has not been possible. I am using Mac OSX 10.11.6 and Jami -- Version 1 (20190902). **I have tried to follow directions, as it has appeared on jami.net.** The instruction that I am referring to, was, to begin one call, and another, and to drag one participant into another, and thereby joining the two. **However, this is not possible. NOTHING is dragable...**
Could you recommend a fix? Is there something that I am not doing particularly? A hint to the solution will be helpful.
Thank you.Iteration 17 (Video conferences stabilization)Kateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/614No option to resend pictures on Android2021-08-20T21:09:03Zring userNo option to resend pictures on Android- Ring version: Live Free or Die - 20190602-01
- Device model: Samsung Galaxy S5 to Manjaro Linux (Arch based)
- Android version: Android 9/LineageOS 16 (no GApps) to "Live Free or Die" build 2019-07-01 19:46:10 UTC
- What build ...- Ring version: Live Free or Die - 20190602-01
- Device model: Samsung Galaxy S5 to Manjaro Linux (Arch based)
- Android version: Android 9/LineageOS 16 (no GApps) to "Live Free or Die" build 2019-07-01 19:46:10 UTC
- What build you are using: F-Droid to Manjaro/Arch build
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Requirements: Two accounts, one on Linux, one on Android, are already connected
2. Open the conversation on Android
3. Send a picture while Linux is offline
4. Wait. You will get the error message "Unjoinable peer" below the picture
5. Switching Linux online
6. Wait
7. Picture is not resend automatically
8. Try to resend manually (Click on picture, long click on picture to open menu etc.
- Actual result:
1. No option for resending available on Android (Linux has such an option in a poorly noticeable three-point-menu beside a not send picture)
- Expected result:
2. Automatically retry when other peer is online or at least an easy accessable option for retrying for Android. IMHO best solution would be a resend/retry-button directly below the picture.Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/613Wrong microphone used for audio and video call2021-12-29T21:27:04Zring 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/136[API ready]Swarm: support request for resending a file transfer2021-06-12T11:37:55ZSébastien Blin[API ready]Swarm: support request for resending a file transfer+ The daemon should store a link or the file in private datas to retrieve it
+ A peer in a conversation is able to re-ask for a file transfer
+ when downloaded sha3sum must be checked.+ The daemon should store a link or the file in private datas to retrieve it
+ A peer in a conversation is able to re-ask for a file transfer
+ when downloaded sha3sum must be checked.Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/127p2p file transfer: there is no public ip in ICE msg2019-08-12T13:53:00ZSébastien Blinp2p file transfer: there is no public ip in ICE msgall is in the title, the public ip is missing, so the negotiation via TURN doesn't work during the ICE negotiation (only when fallbacking)all is in the title, the public ip is missing, so the negotiation via TURN doesn't work during the ICE negotiation (only when fallbacking)Iteration 12Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/641“‘Jami’ can’t be opened because Apple cannot check it for malicious software.”2019-07-06T12:25:50Z“‘Jami’ can’t be opened because Apple cannot check it for malicious software.”Can’t open Jami on macOS 10.15 public beta 1. I get the below message:
> **“Jami” can’t be opened because Apple cannot check it for malicious software.**
>
> This software needs to be updated. Contact the developer for more information...Can’t open Jami on macOS 10.15 public beta 1. I get the below message:
> **“Jami” can’t be opened because Apple cannot check it for malicious software.**
>
> This software needs to be updated. Contact the developer for more information.
>
> Firefox downloaded this file today at 14:32 from **jami.net**.Iteration 11Kateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/595account import: ringtone not working2023-04-24T15:58:59ZAdrien Béraudaccount import: ringtone not workingLaterAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/594account import: enable push notifications if enabled in the app2019-07-15T13:27:54ZAdrien Béraudaccount import: enable push notifications if enabled in the appIteration 11Rayan OsseiranRayan Osseiranhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/593Feature Request: Update VCard Occasionally2020-10-27T19:41:42ZvindicatorrFeature Request: Update VCard OccasionallyBug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20190629-01
- Device model: LG-Volt LS740
- Android version: 6.0 LineageOS 13
- What build you are using: Play St...Bug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20190629-01
- Device model: LG-Volt LS740
- Android version: 6.0 LineageOS 13
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Create an account in Gnome
2. Create an account on Android
3. Add contact on Android (used QR code)
4. Accept request in Gnome
- Actual result: For my peer contact's identity, all I get is "ring:XXXXX..."
- Expected result: I see my peer contact's username instead of "ring:XXXXX..."
## Additional information
I figured I'd just bring this back up since it hasn't been addressed/dealt-with in quite some time. Something I had brought up in IRC and the ML.
*I know it currently is only sent with calls* That's why I'm calling this a feature request since it's currently behaving as it was programmed to, hence "not a bug".
My suggestion: When the application is started for any client, it initially seeks out the peers by sending a timestamp for sender's vcard as well as the timestamp for each peer's vcard.
Each peer compares the timestamp they have for the sender's vcard with what the sender just sent. If it's older, the peer responds back with the timestamp for THEIR OWN vcard as well as a request for the sender's updated vcard.
If the vcard they have for the sender is already up to date, they just return their vcard if it's newer than the timestamp the sender sent to them regarding the peer's vcard timestamp, otherwise they just send an ack (EDIT0).
That's only for when the application is started.
If a client makes a change to their vcard, they automatically send out the update to each peer.
It's my belief that with this methodology, the vcard will always remain up to date.
Again, it's the only thing that's been keeping me from getting my F&F to use this as their IM. Other than that, even though I haven't taken the testing much further, it's getting nicer and nicer and the latest test resulted in NO lost messages, which used to be another huge issue.
The easier option to implement before going with a vcard revamp is adding a superseding field like nickname that a client can set for each peer.
That way, the vcard will still be viewable, yet the history will always show the nickname if it's set.
EDIT0: Correct my thought.Swarm-chathttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/592Turn screen off during audio calls2019-06-26T15:00:55ZAdrien BéraudTurn screen off during audio callsMake sure screen properly turns off during audio calls when putting the phone against the ear.Make sure screen properly turns off during audio calls when putting the phone against the ear.Iteration 10Rayan OsseiranRayan Osseiranhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/123Fix DTMF (win + multiple bips on some calls + stay focused)2019-07-17T19:40:53ZSébastien BlinFix DTMF (win + multiple bips on some calls + stay focused)Iteration 10Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/121ipv4<->ipv4 (no TURN) call hang (connecting)2019-07-17T13:37:22ZSébastien Blinipv4<->ipv4 (no TURN) call hang (connecting)Iteration 10Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/628[Feature] : show username availability status in account creationg2019-07-18T18:12:55ZMohamed Amine Younes Bouacida[Feature] : show username availability status in account creationgCurrently when we want to create an account, we have a feedback only when there is an error.
We need to show that the username is available
Also show an error message when the request for the username availability fails.Currently when we want to create an account, we have a feedback only when there is an error.
We need to show that the username is available
Also show an error message when the request for the username availability fails.Iteration 10Mohamed Amine Younes BouacidaMohamed Amine Younes Bouacidahttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/112peer discovery: fix connnectivity2023-09-29T09:56:17ZAdrien Béraudpeer discovery: fix connnectivityLaterAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/107UPnP: IGD discovery doesn't work when using WiFi + Ethernet2019-07-08T17:50:15ZSébastien BlinUPnP: IGD discovery doesn't work when using WiFi + EthernetHow to reproduce:
1. Add a log for `UPNP_DISCOVERY_SEARCH_RESULT` (`upnp_context.cpp:951`)
2. Using only WiFi (UPnP available), launch the daemon, the log is printed
3. Using WiFi + Eth, launch the daemon, the log is not be printed.How to reproduce:
1. Add a log for `UPNP_DISCOVERY_SEARCH_RESULT` (`upnp_context.cpp:951`)
2. Using only WiFi (UPnP available), launch the daemon, the log is printed
3. Using WiFi + Eth, launch the daemon, the log is not be printed.Iteration 10Eden AbitbolEden Abitbolhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/573android: sometimes the phone still not wake up2021-02-05T15:19:56ZSébastien Blinandroid: sometimes the phone still not wake upLaterSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/103Calls negotiate TCP + UDP and use TCP if the negotiation succeed.2019-07-17T13:36:59ZSébastien BlinCalls negotiate TCP + UDP and use TCP if the negotiation succeed.Iteration 10Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/203macos: use hardware accelerated video encoding/decoding/display2023-05-05T19:44:16ZAdrien Béraudmacos: use hardware accelerated video encoding/decoding/displayIteration 12Kateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1008Idle: Major memory leak2019-04-23T18:23:32ZSébastien BlinIdle: Major memory leakTo investigate, but the client is eating memoryTo investigate, but the client is eating memoryIteration 5Sébastien BlinSébastien Blin