savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2020-06-29T20:27:11Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/812Jami Android Friends list loading2020-06-29T20:27:11Zkl0001Jami Android Friends list loadingMultiple mobile phones, loading friends list under wifi environment, the speed is very slow. Jami Android. I can email the phone model if needed.Multiple mobile phones, loading friends list under wifi environment, the speed is very slow. Jami Android. I can email the phone model if needed.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/702[enhancement] Quote messages2020-02-25T15:13:46ZSimon Brand[enhancement] Quote messagesIn huge conversations it is beneficial to be able to quote messages, so the recipient can retrace which answer belongs to which questions. In other messengers there is usually a little preview of the quoted message and when clicking on i...In huge conversations it is beneficial to be able to quote messages, so the recipient can retrace which answer belongs to which questions. In other messengers there is usually a little preview of the quoted message and when clicking on it, the messenger jumps to the point in the history where the message is (So it is possible to also click here on the quoted message and have something like a thread in a conversation)
To have easy access to the quoting mechanism, you can usually swipe messages to the right edge of the screen and then this message is selected for quoting.
So features:
- Quote message through context menu and swiping message to the right.
- Show quoted message above the input field while answering the message
- Show preview of quoted message above the answer
- When clicking on the quoted message, jump to the original messagehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/810Ios Local dht node2020-02-20T02:24:37Zkl0001Ios Local dht nodeIOS cannot establish a local DHT network. In a LAN environment, the ability to resist network congestion is not strong.(Enable local peer discovery Connect to other DHT nodes advertising on our local network)“~feedback “~enhancement “~"f...IOS cannot establish a local DHT network. In a LAN environment, the ability to resist network congestion is not strong.(Enable local peer discovery Connect to other DHT nodes advertising on our local network)“~feedback “~enhancement “~"feature request" https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/61Switching to low-latency protocol for no reason2020-10-28T14:09:50ZRaphaelSwitching to low-latency protocol for no reasonJami build: `20200130`
OS: iOS `13.3` on iPhone XR
Bluetooth ear phones: Jabra Elite 65t
Since installing Jami and linking my account, I noticed that when I am listening to e.g. Podcasts on my iPhone via Bluetooth, the earbuds randomly ...Jami build: `20200130`
OS: iOS `13.3` on iPhone XR
Bluetooth ear phones: Jabra Elite 65t
Since installing Jami and linking my account, I noticed that when I am listening to e.g. Podcasts on my iPhone via Bluetooth, the earbuds randomly switch to the low-latency telephone protocol now and then.
This results in stopping the current playback. I guess because the OS thinks, a call is being made. This is of course really annoying. It happens even if I have "killed" the app and the only way to get around this is uninstalling it.
Which makes the app unusable at this point for me.
Also any time I start the app, the protocol is switched to the low-latency calling protocol and my playback is paused reproducibly. Other apps like Facetime, Skype, etc. only switch to this protocl right when accepting a call and disable it after ending the call.
//Edit:
I wanna add that the behaviour of what happens when the profile switches is apprently depedent on the app you are listening to. In Pocket Casts for example, the playback stops. In Spotify, the playback continues in that shitty protocol that is optimized for calling and low latency.https://git.jami.net/savoirfairelinux/jami-project/-/issues/807Beeps/Tones during connection - question2020-06-29T20:30:44Zw5pnyBeeps/Tones during connection - questionWhat is the meaning of the beep/tone that is generated by jami every few seconds during
a connection?What is the meaning of the beep/tone that is generated by jami every few seconds during
a connection?https://git.jami.net/savoirfairelinux/jami-project/-/issues/806Switching to low-latency protocol for no reason2020-02-13T18:58:19ZRaphaelSwitching to low-latency protocol for no reasonJami build: `20200130`
OS: iOS `13.3` on iPhone XR
Bluetooth ear phones: Jabra Elite 65t
Since installing Jami and linking my account, I noticed that when I am listening to e.g. Podcasts on my iPhone via Bluetooth, the earbuds randomly ...Jami build: `20200130`
OS: iOS `13.3` on iPhone XR
Bluetooth ear phones: Jabra Elite 65t
Since installing Jami and linking my account, I noticed that when I am listening to e.g. Podcasts on my iPhone via Bluetooth, the earbuds randomly switch to the low-latency telephone protocol now and then.
This results in stopping the current playback. I guess because the OS thinks, a call is being made. This is of course really annoying. It happens even if I have "killed" the app and the only way to get around this is uninstalling it.
Which makes the app unusable at this point for me.
Also any time I start the app, the protocol is switched to the low-latency calling protocol and my playback is paused reproducibly. Other apps like Facetime, Skype, etc. only switch to this protocl right when accepting a call and disable it after ending the call.
//Edit:
I wanna add that the behaviour of what happens when the profile switches is apprently depedent on the app you are listening to. In Pocket Casts for example, the playback stops. In Spotify, the playback continues in that shitty protocol that is optimized for calling and low latency.https://git.jami.net/savoirfairelinux/jami-project/-/issues/804Feature request Virtual webcams recoqnition or possibilty of broadcating wirt...2021-07-09T20:57:45ZsviatorusFeature request Virtual webcams recoqnition or possibilty of broadcating wirt OBS, Xsplit and suchHi!You made very good messenger. It has all features of standard messengers and better security. Unfortnaly it do not recognize virtual caneras, like OBS, Xsplit and others. It also can permit to transmit in input only sound of microphon...Hi!You made very good messenger. It has all features of standard messengers and better security. Unfortnaly it do not recognize virtual caneras, like OBS, Xsplit and others. It also can permit to transmit in input only sound of microphone, but not of soundcard. If you will add options to choose any available audio and video input and output, it will allow users make video broadcasting and video conferencing where will be possible to demonstrate videos and make voice comments at the same time. Also will be nice to transmit directly to the group rtmp broadcasting. It will set Jami far ahead of any competition. Hope someday it will be possibe. My best regards.https://git.jami.net/savoirfairelinux/jami-project/-/issues/802Choose appropriate replacement hash function for SHA12021-11-28T20:52:48ZAdrien BéraudChoose appropriate replacement hash function for SHA1**Design change draft proposal**
* Use the full public key or certificate instead of the public key hash whenever possible
* Use SHA-256 when using the full public key is not necessary for security and if the performance impact of the f...**Design change draft proposal**
* Use the full public key or certificate instead of the public key hash whenever possible
* Use SHA-256 when using the full public key is not necessary for security and if the performance impact of the full public key is too large.
* Make sure future changes are easier
**Discussion**
* Using SHA-3 would be possible but is not currently implemented by GnuTLS (see https://gnutls.org/reference/gnutls-x509.html#gnutls-keyid-flags-t)https://git.jami.net/savoirfairelinux/jami-project/-/issues/801Identify uses of SHA1 in Jami and evaluate needs of replacement2021-12-20T18:40:05ZAdrien BéraudIdentify uses of SHA1 in Jami and evaluate needs of replacementSha1 is currently used:
* For device identification:
* Internally for device list
* In device sync data
* In JAMS & JAMS device sync
* User identification
* Internally for contact list
* In device sync data
* In JAMS & JAM...Sha1 is currently used:
* For device identification:
* Internally for device list
* In device sync data
* In JAMS & JAMS device sync
* User identification
* Internally for contact list
* In device sync data
* In JAMS & JAMS contact syncAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/67LMDE 42020-04-11T11:54:40ZovariLMDE 4Please add `LMDE 4` to https://jami.net/download-jami-linux/
LMDE 4 is based on Debian 10.
https://blog.linuxmint.com/?p=3858
Thank youPlease add `LMDE 4` to https://jami.net/download-jami-linux/
LMDE 4 is based on Debian 10.
https://blog.linuxmint.com/?p=3858
Thank youGuillaume HellerGuillaume Hellerhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/696Multiple instances opened when sharing2021-11-25T16:52:23ZSébastien BlinMultiple instances opened when sharingvia @mcournoyer
# Reproduce steps
1. Open Jami
2. From another app, share a file via Jami
# Expected
One jami instance should be open
# Current result
Two instances are opened, leading to unstable calls/file transfer sometimes bec...via @mcournoyer
# Reproduce steps
1. Open Jami
2. From another app, share a file via Jami
# Expected
One jami instance should be open
# Current result
Two instances are opened, leading to unstable calls/file transfer sometimes because both instances are answeringAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/694File transfer notifications lack overlay (pop-up) and are too easy to miss2021-11-25T17:01:28ZMaxim CournoyerFile transfer notifications lack overlay (pop-up) and are too easy to missTested on: Jami 20200107-01 (F-Droid). Device: HTC U Play (Android 6)
When sending files to a contact using the Android client, the receiving end notification is very easy to miss because:
1. It doesn't draw a notification on top of ot...Tested on: Jami 20200107-01 (F-Droid). Device: HTC U Play (Android 6)
When sending files to a contact using the Android client, the receiving end notification is very easy to miss because:
1. It doesn't draw a notification on top of other applications, like a text message would, and;
2. it vibrates the device very briefly, and;
3. it doesn't trigger any kind of notification sound (to be confirmed).
This is particularly annoying for bigger file transfers, which must be accepted by the remote peer, as they tend to get noticed only after they timed out and failed.https://git.jami.net/savoirfairelinux/jami-project/-/issues/785[Feature Request] Link Previews2021-08-20T19:56:20Ztrymeout[Feature Request] Link PreviewsNot an important feature. But to get the webapge details such as image and a short description for any links sent from certain websites. This is only needed for popular websites such as YouTube, Twitter, Facebook, maybe news articles. Th...Not an important feature. But to get the webapge details such as image and a short description for any links sent from certain websites. This is only needed for popular websites such as YouTube, Twitter, Facebook, maybe news articles. This is a feature in WhatsApp and Signal.https://git.jami.net/savoirfairelinux/jami-project/-/issues/781[Feature Request] Phone Number/Email Registration2023-12-27T20:18:13Ztrymeout[Feature Request] Phone Number/Email RegistrationHere me out before you say no,
I like Jami since it you can register without an email or phone number and be anonymous. I am not suggesting to remove this at all, but to make it more user friendly to sign up and manage your Jami account...Here me out before you say no,
I like Jami since it you can register without an email or phone number and be anonymous. I am not suggesting to remove this at all, but to make it more user friendly to sign up and manage your Jami account for those who are not tech savvy and do not care about usernames, anonymity and want an easy signup and login, I would like to suggest this.
**Create Account Or Login To Your Account**
* When you go to create a new Jami Account it will ask weather you want to use a phone number, email, username, or be anonymous (RingID only). If you choose phone number or email it will take you to the next page
* It will ask for your phone number/email, you enter it and then it will send a text message/email to that phone number/email address. You get the 6 digit code and enter it into the app. Then it will take you to the next page.
* Then you choose your avatar and name and after that your all set.
The Jami username for a phone number will be +12223334444. This is possible since "+" characters are not allowed in a username making it impossible for people to register a username that is someones elses phone number. Same goes for email, the Jami username for a email address will be the email address john@gmail.com. "@" characters are not allowed in a username making it impossible for people to register a username that is someones elses email address.
This will allow for an easy account setup and recover for those who do not mind using their phone number or email address as their username. The con of signing up and logging it is that it will require internet access or cellular network but once your signed up/logged in, no need for any cellular network or internet connection since your account will still have a unique Jami ID.
The one thing that maybe be needed is storage for these phone number/email accounts on a server. This will need to be decentralised and will not be constantly used, it will only be accessed when users signup or login to their accounts for the first time. I would like to suggest the name servers/blockchain can handle this. No password is needed since to access your account you need access to the phone number or email address and enter the 6 digit code to verify the login.
If sending text messages for phone number registration will become a cost burden, then email registration is fine and very user friendly since most online accounts require a email address to signup.https://git.jami.net/savoirfairelinux/jami-project/-/issues/778Long delay before message appear as delivered2021-08-16T21:03:43ZRobert AndrewLong delay before message appear as deliveredI am experiencing very long delivery delay (messages stay grayed) from a broadband static IP to an Android device on 4G.
Could it be that Android devices do not automatically share their new dynamic IP? Or am I misinterpreting the graye...I am experiencing very long delivery delay (messages stay grayed) from a broadband static IP to an Android device on 4G.
Could it be that Android devices do not automatically share their new dynamic IP? Or am I misinterpreting the grayed messages (not delivered vs. not read) ?https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/203[Feature Request] Read Reciepts2020-12-22T20:05:19Ztrymeout[Feature Request] Read RecieptsJami has a sending indicator, and received indicator. But not a read indicator. Please add read reciepts for Jami. Here is how I picture it could work for two way conversations and even group conversations.
[Spinning Circle - Sending......Jami has a sending indicator, and received indicator. But not a read indicator. Please add read reciepts for Jami. Here is how I picture it could work for two way conversations and even group conversations.
[Spinning Circle - Sending...]
[Hollow Checkmarks - Sent]
[Filled Checkmark - Received]
[Username Icon - Read]https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/55Jenkins: all cached contrib are rebuilt2021-03-01T14:59:35ZSébastien BlinJenkins: all cached contrib are rebuiltEven if there is 5 different versions for the same contrib
We think 3/4 of the daemon build time is taked by contribEven if there is 5 different versions for the same contrib
We think 3/4 of the daemon build time is taked by contribMaxim CournoyerMaxim Cournoyerhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/686client-android : configuration of the type and sound of jami's notifications2020-01-09T21:43:51Zjpgclient-android : configuration of the type and sound of jami's notificationsWhen I received a message, the notification does not look like an "sms" or "normal call" notification (sound and led) but like calendar notifications.
Please add an option to change the type and sound of notification.
Jami F-droid vers...When I received a message, the notification does not look like an "sms" or "normal call" notification (sound and led) but like calendar notifications.
Please add an option to change the type and sound of notification.
Jami F-droid version 2019-08-24-01)
Android version 5.1.1https://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-ios/-/issues/60Own TURN-server2023-05-17T17:28:59ZRalph HahnOwn TURN-serverI have read that I can use an own TURN-server. In Linux-, Mac- and Wndows-version I see it's possible to change this params. How to do this in a mobile app?I have read that I can use an own TURN-server. In Linux-, Mac- and Wndows-version I see it's possible to change this params. How to do this in a mobile app?BacklogKateryna KostiukKateryna Kostiuk