savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-09-24T07:42:42Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/663Eternal Damnation: No Way to Unblock Contact2022-09-24T07:42:42ZEternal Damnation: No Way to Unblock Contact- Ring version: 2019-08-24-01
- Device model: Samsung Tablet S2
- Android version: 8.1 / LineageOS 15.1-20190228
- Jami-Version from F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Establish...- Ring version: 2019-08-24-01
- Device model: Samsung Tablet S2
- Android version: 8.1 / LineageOS 15.1-20190228
- Jami-Version from F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Establish a Jami contact.
2. Use "Block Contact" function.
- Actual result: Blocked contact is removed from contact list. There seems to be no
"Unblock contact" function available.
- Expected result: Blocked contact shall remain in contact list with a "blocked" indicator (e.g. https://upload.wikimedia.org/wikipedia/commons/1/11/Norwegian-road-sign-302.0.svg). Blocked contacts shall have an obvious and reliable un-block function.
![300px-Norwegian-road-sign-302.0.svg](/uploads/fd9bf4a056bae4b84184c2833b8cf369/300px-Norwegian-road-sign-302.0.svg.png)
## Additional information
This is a serious issue if blocking was done by accident. If a patched Jami version cannot be produced quickly there should be at least a documented workaround for this problem soon.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/174Moving from one wifi to another during a call freeze the video2024-01-06T10:28:00ZSébastien BlinMoving from one wifi to another during a call freeze the videoAudio is still working, but not the control channel nor video channel
If possible, the video should come back, be renegotiated or the call closed. (timeout between media packets?)Audio is still working, but not the control channel nor video channel
If possible, the video should come back, be renegotiated or the call closed. (timeout between media packets?)https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/27deb pkgs: automated tests2020-01-27T21:59:00ZFredy Pulidodeb pkgs: automated testsWe want an automated test stage in our CI (Jenkins) that ensures that packages we publish can be properly installed and in the case of the one-click-install ensure that the repository is added and works when using apt update / upgrade
D...We want an automated test stage in our CI (Jenkins) that ensures that packages we publish can be properly installed and in the case of the one-click-install ensure that the repository is added and works when using apt update / upgrade
Definition of done:
When we run the internal packaging CI job for a Debian/Ubuntu package we will get a QA stage where a container will be used to install Jami.
This job must to verify at least items in this wiki page: https://git.jami.net/savoirfairelinux/jami-packaging/wikis/Test-Suite
We have this WIP in Gerrit: https://review.jami.net/c/ring-project/+/12869https://git.jami.net/savoirfairelinux/jami-project/-/issues/727messaging: save/restore draft messages2020-01-09T21:37:44Zannamessaging: save/restore draft messagesI have just discovered https://review.jami.net/c/ring-client-windows/+/13055.
And I wonder if the function could make sense or be understood differently.
My idea: I want to quit Jami and there is still an unsent message open, if I agre...I have just discovered https://review.jami.net/c/ring-client-windows/+/13055.
And I wonder if the function could make sense or be understood differently.
My idea: I want to quit Jami and there is still an unsent message open, if I agree to the client suggestion, it will be saved as a draft and I can write it the next time I use Jami or finish it and then send it. The other option for users would be to discard the message when closing Jami. Of course, saving the draft message would have to be local and encrypted, as already discussed in other issues.
After a restart it would be nice if Jami asks me to continue with the open message draft.
An implementation could probably be realized for all systems and clients.
https://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-client-android/-/issues/670Screenshots missing in f-droid2023-04-07T20:14:09ZScreenshots missing in f-droidCurrently, there are no screenshots of the app on the [f-droid page](https://f-droid.org/en/packages/cx.ring/).
I think you should add some (more = better), up-to-date ones.
People should see what the app looks like and what the feature...Currently, there are no screenshots of the app on the [f-droid page](https://f-droid.org/en/packages/cx.ring/).
I think you should add some (more = better), up-to-date ones.
People should see what the app looks like and what the features there are :)
https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/56Appimage or static build?2023-02-05T02:33:29ZdsAppimage or static build?Could you please provide app image or statically build executable for the Jami? To cover wider range of linux distributions?Could you please provide app image or statically build executable for the Jami? To cover wider range of linux distributions?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/675Jami asked for password when trying to revoke a device inspite the account ha...2020-10-01T13:22:24ZNokia808Jami asked for password when trying to revoke a device inspite the account has no password !Hi. I have Jami account created on my Android device. I linked it to my PC with flatpak package from FlatHub since a long time when flatpak was almost useless (no even IM communications possible at that time). Then I removed flatpak beca...Hi. I have Jami account created on my Android device. I linked it to my PC with flatpak package from FlatHub since a long time when flatpak was almost useless (no even IM communications possible at that time). Then I removed flatpak because it was totally useless. When I removed it, I removed also the user data folder of Jami flatpak also, so that when I will re-install flatpak again it will not remember any data.
Few days ago, I re-installed Jami flatpak. I start it & it launched finally to me WITHOUT ANY ACCOUNT. I used my Android to re-link my account (that already created on Android). Before that I tried to revoke the OLD LINKAGE for my PC that still appeared on my Android. But when I tried this it asked me to enter a password to confirm this inspite the fact that my account has NO password set yet! So, I tried to make new link for same PC & I did that okay.
But now, on my PC flatpak Jami, my account that created on Android show only 2 linked devices: my mobile & my PC (which is correct display). But when I view it on my Android version of Jami, it show 3 devices: my android device, my PC (old linkage), & my PC (new linkage)!!
How, my Android client asked me for password to revoke a device inspite that my account has no password? I tried to see what is the behaviour of flatpak client when I try to revoke device & it did not ask me for password.
------
By the way, when revoke a device, can we re-add it again ?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/677name server setting is missing2023-04-07T20:27:55ZGuillaume Hellername server setting is missingthe name server address can not be changed from the Android advanced settingsthe name server address can not be changed from the Android advanced settingshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/679Please making "Push notifications" disabled by default2019-12-30T18:30:36ZNokia808Please making "Push notifications" disabled by defaultHi. I noticed that "Push notifications" option is enabled by default on Android version. I understand that this feature needed by many users, but since it is a centralized option it is undermine the decentralized nature of Jami & counter...Hi. I noticed that "Push notifications" option is enabled by default on Android version. I understand that this feature needed by many users, but since it is a centralized option it is undermine the decentralized nature of Jami & counter-count with decentralization, I suggest on you to make this feature disabled by default.
The user who like it can enable it manually. Also, it is nice to make warning message appearing when user try to enable this feature saying "Warning! This feature is centralized, opposing the decentralized nature of Jami. Do you like to continue?"
This way, user will be oriented about what she/he do ...https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/694ffmpeg: add G711, G729 codecs (SIP)2022-07-06T00:18:18Zovariffmpeg: add G711, G729 codecs (SIP)Please add the following codecs to Jami:
* [G.711a](https://en.wikipedia.org/wiki/G.711)
* [G.711u](https://en.wikipedia.org/wiki/G.711)
* [G.729a](https://en.wikipedia.org/wiki/G.729)
What do you think?
Thank you
> MyNetFone uses th...Please add the following codecs to Jami:
* [G.711a](https://en.wikipedia.org/wiki/G.711)
* [G.711u](https://en.wikipedia.org/wiki/G.711)
* [G.729a](https://en.wikipedia.org/wiki/G.729)
What do you think?
Thank you
> MyNetFone uses the **G.711a** codec, it is the standard codec used in Australia and Europe. The **G.711u** codec is used within the US, and may be present in PBXs or UC platforms from US vendors. The **G.729a** codec is often used for conference calling services.<br>
> https://www.mynetfone.com.au/support/faq/question/477
> The patents for G.711, released in 1972, have expired, so it may be used without the need for a licence
> https://en.wikipedia.org/wiki/G.711#Licensing
> As of January 1, 2017, the patent terms of most licensed patents under the G.729 Consortium have expired, the remaining unexpired patents are usable on a royalty-free basis.<br>
> https://en.wikipedia.org/wiki/G.729.1
https://git.jami.net/savoirfairelinux/ring-daemon/issues/200Backloghttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/51pkgs manual tests2019-12-31T19:23:41ZFredy Pulidopkgs manual testsAfter we finish #27 we could use containers to test our packages doing video calls from docker.
Jerome show me the way to do it:
```
docker run --privileged -ti --network=host -v /dev/video0:/dev/video0 -v /dev/snd:/dev/snd -v /dev/dri...After we finish #27 we could use containers to test our packages doing video calls from docker.
Jerome show me the way to do it:
```
docker run --privileged -ti --network=host -v /dev/video0:/dev/video0 -v /dev/snd:/dev/snd -v /dev/dri:/dev/dri -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=${DISPLAY} -v /run/dbus/system_bus_socket:/run/dbus/system_bus_socket -e PULSE_SERVER=unix:/run/pulse/native -v /run/pulse/native:/run/pulse/native -e XAUTHORITY=$XAUTHORITY -v /dev/fb0:/dev/fb0 container_id bash
```
There the only thing we have to do is to find (using strace) the file that X require to show Jami in our actual display.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/692[Feature Request] Limit Data Transfer on Data2022-12-30T20:31:59Ztrymeout[Feature Request] Limit Data Transfer on DataPlease add options for Android and iOS to limit/reduce certain file transfers when your using Data and not on Wifi.
Videos files
Audio files
Documents over #mb in size
Pictures over #mb in size
Video Calls quality reduced
Audio call qua...Please add options for Android and iOS to limit/reduce certain file transfers when your using Data and not on Wifi.
Videos files
Audio files
Documents over #mb in size
Pictures over #mb in size
Video Calls quality reduced
Audio call quality reducedhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/687Proper and meaningful changelog2023-05-30T20:18:53ZMark SmithProper and meaningful changelogAs the new version came out on F-Droid I clicked on the changelog link but it redirects to [this page](https://git.jami.net/savoirfairelinux/ring-client-android/tree/master/ring-android/fastlane/metadata/android/en-US/changelogs) full of...As the new version came out on F-Droid I clicked on the changelog link but it redirects to [this page](https://git.jami.net/savoirfairelinux/ring-client-android/tree/master/ring-android/fastlane/metadata/android/en-US/changelogs) full of files one or two years old.
Can we have a proper and meaningful changelog?
Keep up the good work!https://git.jami.net/savoirfairelinux/jami-project/-/issues/780[Feature Request] Self Destructing Messages2024-03-06T11:49:28Ztrymeout[Feature Request] Self Destructing MessagesA cool privacy feature will be the ability to set a timer on a single message weather the message is a text, image, video, etc. Once the other users open and view the message, the timer will start and once the timer expires, the message ...A cool privacy feature will be the ability to set a timer on a single message weather the message is a text, image, video, etc. Once the other users open and view the message, the timer will start and once the timer expires, the message is deleted forever.
I think this will be cool feature for single messages that can be set before sending the message. Also this feature will be cool for conversation were you set a timer on a conversations and all messages you send after will have a timer on it until someone removes the timer from the conversation settings.https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/61One click install for RPMs2021-05-04T13:44:40ZFredy PulidoOne click install for RPMshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/697[enhancement] Allow swiping to view the media content of a conversation2020-01-22T21:28:14ZMaxim Cournoyer[enhancement] Allow swiping to view the media content of a conversationWhat I suggest is to enable gestures such as swipe right to see the previous photo/video file in the conversation, swipe left to go back to the previous photo/video, just as a normal photo browser would on Android.
More precisely, what ...What I suggest is to enable gestures such as swipe right to see the previous photo/video file in the conversation, swipe left to go back to the previous photo/video, just as a normal photo browser would on Android.
More precisely, what is expected:
1. User presses on picture in the conversation. Photo is maximized to fill the screen (OK).
2. User swipes right --> Previous photo/video is displayed, still in full screen mode.
What happens instead:
1. User presses on picture in the conversation. Photo is maximized to fill the screen (OK).
2. User swipes right or left --> Nothing happens.
3. User is forced to use the "Back" arrow of its Android device to return to the conversation, then select another picture to view in full screen.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/377Bugfix - SIP authentication username option missing in desktop clients2022-07-04T18:39:37ZRobinBugfix - SIP authentication username option missing in desktop clientsI'd like to refer to my request on [Twitter](https://twitter.com/jami_social/status/1217490812847763456)... BTW thanks for the quick reply :thumbsup:
---
I'm unable to set up my SIP account since there is no option for `authentication...I'd like to refer to my request on [Twitter](https://twitter.com/jami_social/status/1217490812847763456)... BTW thanks for the quick reply :thumbsup:
---
I'm unable to set up my SIP account since there is no option for `authentication username`. I have something like this:
```config
username: 1234
registrar: example.net
authentication username: johndoe
password: ***
```
Could you please fix this?Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/800[Group-chat] Avoid sha1 in git signatures2020-12-22T20:02:52ZSébastien Blin[Group-chat] Avoid sha1 in git signaturesSwarm-chatSébastien BlinSébastien Blin