savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-05-03T03:51:18Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1266Build daemon error libarchive2023-05-03T03:51:18ZFebry Dwi PutraBuild daemon error libarchiveHi, i'm facing error when building daemon using ./gradlew assembleDebug command
![Jepretan_Layar_2023-05-03_pukul_09.56.34](/uploads/d305b55fc64b90eb1dc663ca2d360559/Jepretan_Layar_2023-05-03_pukul_09.56.34.png)
But i've already install ...Hi, i'm facing error when building daemon using ./gradlew assembleDebug command
![Jepretan_Layar_2023-05-03_pukul_09.56.34](/uploads/d305b55fc64b90eb1dc663ca2d360559/Jepretan_Layar_2023-05-03_pukul_09.56.34.png)
But i've already install libarchive in my mac
![Jepretan_Layar_2023-05-03_pukul_09.57.14](/uploads/cdc6bcd17d5a53c860f072341f28cf40/Jepretan_Layar_2023-05-03_pukul_09.57.14.png)
Anyone can help me solve this issue?
Gradle 7.5
Build time: 2022-07-14 12:48:15 UTC
Revision: c7db7b958189ad2b0c1472b6fe663e6d654a5103
Kotlin: 1.6.21
Groovy: 3.0.10
Ant: Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM: 11.0.17 (Oracle Corporation 11.0.17+10-LTS-269)
OS: Mac OS X 13.2.1 x86_64
cmake version 3.26.3
Android Studio Electric Eel | 2022.1.1https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1095Yourself is not clickable when adding member in swarm group2023-08-23T13:36:28ZPierre NicolasYourself is not clickable when adding member in swarm groupI don't know if it's normal but so why to display ?
## Describe your environment
- OS: Ubuntu 22.04 LTS
- Jami version: Világfa 202304121408
- What build you are using: Ubuntu software
## Steps to reproduce
- Can you reproduce the bu...I don't know if it's normal but so why to display ?
## Describe your environment
- OS: Ubuntu 22.04 LTS
- Jami version: Világfa 202304121408
- What build you are using: Ubuntu software
## Steps to reproduce
- Can you reproduce the bug : at will
- Steps:
1. Click on create a new swarm conversation
2. Try to add yourself
- Actual result: You are not clickable, so why to display ?
## Additional information
![why_to_see_yourself_if_not_clickable](/uploads/86ee43aa9a7dd5a13ec06a13be9144ea/why_to_see_yourself_if_not_clickable.webm)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1262android: crash when importing (certain) CA bundle2023-05-01T19:59:08ZCody T.-H. Chiuandroid: crash when importing (certain) CA bundleTo reproduce:
1. Download and import Twilio CA Bundle https://www.twilio.com/docs/voice/api/secure-media#importing-twilios-root-ca-certificate
2. App crashes (log from 1 version earlier but symptom reproduced under 20230424-01)
```
type...To reproduce:
1. Download and import Twilio CA Bundle https://www.twilio.com/docs/voice/api/secure-media#importing-twilios-root-ca-certificate
2. App crashes (log from 1 version earlier but symptom reproduced under 20230424-01)
```
type: crash
osVersion: google/redfin/redfin:13/TQ2A.230405.003/2023042900:user/release-keys
package: cx.ring:365
process: cx.ring
processUptime: 11245 + 42 ms
java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=569911132, result=-1, data=Intent { dat=content://com.android.providers.downloads.documents/... flg=0x1 }} to activity {cx.ring/cx.ring.client.HomeActivity}: java.lang.NumberFormatException: For input string: "msf:1000001393"
at android.app.ActivityThread.deliverResults(ActivityThread.java:5342)
at android.app.ActivityThread.handleSendResult(ActivityThread.java:5381)
at android.app.servertransaction.ActivityResultItem.execute(ActivityResultItem.java:67)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:138)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2304)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7891)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:952)
Caused by: java.lang.NumberFormatException: For input string: "msf:1000001393"
at java.lang.Long.parseLong(Long.java:736)
at java.lang.Long.parseLong(Long.java:861)
at f6.d.k(SourceFile:124)
at h5.r2.a3(SourceFile:25)
at androidx.fragment.app.FragmentManager$h.a(SourceFile:69)
at androidx.activity.result.e.a(SourceFile:45)
at androidx.activity.ComponentActivity.onActivityResult(SourceFile:3)
at androidx.fragment.app.t.onActivityResult(SourceFile:6)
at android.app.Activity.dispatchActivityResult(Activity.java:8711)
at android.app.ActivityThread.deliverResults(ActivityThread.java:5335)
... 13 more
```https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1259No invitation notification when receiving account is not current2024-03-28T00:05:08ZPierre NicolasNo invitation notification when receiving account is not current## Describe your environment
- Device model: Nexus 5X
- Android version: API 33
- What build you are using: your own -> 02a367ded625244c4e6cf72d61b5c86ee19422af
## Steps to reproduce
- Can you reproduce the bug: at will
- St...## Describe your environment
- Device model: Nexus 5X
- Android version: API 33
- What build you are using: your own -> 02a367ded625244c4e6cf72d61b5c86ee19422af
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. You need three accounts, two on same device A1 and A2 and one on another device C.
2. Select A1 as current account on first device.
3. Send friend invitation to A1 from C. There is a friend invitation notification.
4. Then, send friend invitation to A2 from C.
- Actual result: No notification
## Additional information
![Kazam_screencast_00002](/uploads/0bdca4fbd03b3f56ac0d28cc31f41fec/Kazam_screencast_00002.webm)Vitalii NikitchynVitalii Nikitchynhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1255Content of "member" bottomsheetdialog is poorly displayed2023-04-26T19:47:44ZPierre NicolasContent of "member" bottomsheetdialog is poorly displayed## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own -> 1d959f837a3ec3d1741083f711dac5f1f4fd3f86
## Steps to reproduce
- Can you reproduce the b...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own -> 1d959f837a3ec3d1741083f711dac5f1f4fd3f86
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Go in a swarm conversation (three people at least)
2. From conversation settings, go in members tab
3. Click on a contact
- Actual result: A bottomsheetdialog opens but content is poorly displayed
## Additional information
![members_bottomsheetdialog_is_not_fully_implemented](/uploads/bfc38c91e402293f6a06830abacf77b2/members_bottomsheetdialog_is_not_fully_implemented.mp4)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1088MainView: fix missing active focus overlay for some items2024-02-22T19:52:15ZFranck LaurentMainView: fix missing active focus overlay for some itemsThere are some items that do not have an active focus overlay, which include:
- The advancedAccountSettings page in wizard view: active focus is lost when the Customize button is opened.
- The welcomeview in settings: the JamiIdentifier ...There are some items that do not have an active focus overlay, which include:
- The advancedAccountSettings page in wizard view: active focus is lost when the Customize button is opened.
- The welcomeview in settings: the JamiIdentifier present in the welcomeView takes the active focus even if the settings page is loaded.
- The callview: the active focus is only taken by the comboBox.
This information is related to the following issue: https://review.jami.net/c/jami-client-qt/+/24446.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1253Impossible to establish ip2ip SIP call (at least android->desktop and desktop...2023-04-24T15:22:18ZPierre NicolasImpossible to establish ip2ip SIP call (at least android->desktop and desktop->android)## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Create and connect SIP account on Android (ip2ip UDP)
1...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Create and connect SIP account on Android (ip2ip UDP)
1. Create and connect SIP account on Desktop (ip2ip UDP)
1. Connect your devices on same network
2. Try to make a ip2ip voice call from android, accept from desktop
- Actual result: Call connecting activity disappear without establishing call. Missed outgoing call appears on conversation. It continues ringing. Have to restart the app.
## Additional information
Looking through logs above make think it come from failing media negotiation.
Call logs from desktop to android :
```
[1682347249.158|40881|channeled_transport.cpp :186 ] [SIPS] process disconnect event
[1682347249.158|40880|ice_transport.cpp :1694] [ice:0x7fb0b8cd5570] ice send failed: Not found (PJ_ENOTFOUND)
[1682347249.158|40881|siptransport.cpp :209 ] pjsip transport@0x7fb184219c90 TLS to 142.170.109.216 -> DISCONNECTED
[1682347249.158|56389|siptransport.cpp :100 ] ~SipTransport@0x7faf08032e90 tr=0x7faf0809bfb0 rc=1
[1682347249.158|40880|tls_session.cpp :893 ] [TLS] transport failure on tx: errno = 5
[1682347249.159|56389|gitserver.cpp :477 ] GitServer destroyed
[1682347249.159|56389|siptransport.cpp :100 ] ~SipTransport@0x7fb184216bc0 tr=0x7fb184219c90 rc=1
[1682347249.159|56815|ice_transport.cpp :336 ] [ice:0x7fb0b8cd5570] destroying 0x7fb0b8dee168
[1682347249.659|56815|ice_transport.cpp :350 ] [ice:0x7fb0b8cd5570] Destroying ice_strans 0x7fb0b8dee168
[1682347250.159|56815|ice_transport.cpp :669 ] [ice:0x7fb0b8cd5570] Timer heap flushed after 500ms
[1682347250.159|56815|ice_transport.cpp :382 ] [ice:0x7fb0b8cd5570] done destroying
[1682347250.985|56392|sipvoiplink.cpp :892 ] [call:6027552833534573] INVITE@0x7fb0b9fe44c8 state changed to 4 (CONNECTING): cause=0, tsx@0x7fb14482de48 status 200 (OK)
[1682347250.985|56392|sipvoiplink.cpp :1121] [call:6027552833534573] INVITE@0x7fb0b9fe44c8 media update: status 220048
[1682347250.985|56392|sipvoiplink.cpp :1129] [call:6027552833534573] SDP offer failed, reason 415
[1682347250.985|56392|sipcall.cpp :756 ] [call:6027552833534573] Terminate SIP session
```
Call logs from desktop to android :
```
[1682347307.380|56356|manager.cpp :1047] Answer call 2214803505268786
[1682347307.380|56356|audiostream.cpp :162 ] Destroying stream with device alsa_output.pci-0000_0a_00.3.iec958-stereo
[1682347307.380|56356|sipcall.cpp :889 ] [call:2214803505268786] Answering incoming call with following media:
[1682347307.380|56356|sipcall.cpp :892 ] [call:2214803505268786] Media @0 - type [AUDIO] enabled [YES] muted [NO] label [audio_0] source [camera://046d_0821_0C411BC0] secure [NO]
[1682347307.380|56356|sipcall.cpp :2333] [call:2214803505268786] [audio_0] already un-muted
[1682347307.380|56356|sdp.cpp :604 ] Processing received offer for [Call ID 2214803505268786] with 1 media
[1682347307.380|56356|sdp.cpp :503 ] [SDP OFFER] Remote session:
v=0
o=localhost 3891336105 0 IN IP4 192.168.0.217
s=Call ID 7629516086156536
c=IN IP4 192.168.0.217
t=0 0
a=ice-ufrag:4825cdac
a=ice-pwd:3c5a176c6406842d7f98f7c5
m=audio 18770 RTP/SAVP 104 9 2 112 111 110 8 0 101
a=rtpmap:104 opus/48000/2
a=rtpmap:9 G722/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:112 speex/32000
a=rtpmap:111 speex/16000
a=rtpmap:110 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtcp:18771 IN IP4 192.168.0.217
a=sendrecv
a=candidate:Hc0a800d9 1 UDP 2130706431 192.168.0.217 48819 typ host
a=candidate:Ha556a7c0 1 UDP 2130706431 fe80::2c47:5fff:fe35:d569 51892 typ host
a=candidate:Hc0a800d9 2 UDP 2130706430 192.168.0.217 41158 typ host
a=candidate:Ha556a7c0 2 UDP 2130706430 fe80::2c47:5fff:fe35:d569 36779 typ host
[1682347307.380|56356|sdp.cpp :263 ] Add media description [type [AUDIO] enabled [YES] muted [NO] label [audio_0] source [camera://046d_0821_0C411BC0] secure [NO]]
[1682347307.381|56356|sdp.cpp :503 ] [SDP ANSWER] Local session:
v=0
o=atlas 3891336107 0 IN IP4 192.168.49.92
s=Call ID 2214803505268786
c=IN IP4 192.168.49.92
t=0 0
m=audio 26904 RTP/AVP 104 9 2 112 111 110 8 0 101
a=rtpmap:104 opus/48000/2
a=rtpmap:9 G722/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:112 speex/32000
a=rtpmap:111 speex/16000
a=rtpmap:110 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtcp:26905 IN IP4 192.168.49.92
a=sendrecv
[1682347307.381|56356|sipcall.cpp :3498] [call:2214803505268786] Setup ICE response
[1682347307.382|56356|ice_transport.cpp :331 ] [ice:0x25216e0] Creating IceTransport session for "2214803505268786"
[1682347307.382|56356|sipcall.cpp :3312] [call:2214803505268786] Successfully created media ICE transport [ice:0x5fe8c10]
[1682347307.382|56356|sipcall.cpp :3474] [call:2214803505268786] Setting ICE session [0x5fe8c10]
[1682347307.382|56356|sipcall.cpp :3334] [call:2214803505268786] Init media ICE transport
[1682347307.382|56356|ice_transport.cpp :406 ] [ice:0x25216e0] Initializing the session - comp count 2 - as a slave
[1682347307.382|56356|ice_transport.cpp :447 ] [ice:0x25216e0] Add host candidates
[1682347307.382|56356|ice_transport.cpp :906 ] [ice:0x25216e0] added host stun config for UDP transport
[1682347307.382|56356|ice_transport.cpp :906 ] [ice:0x25216e0] added host stun config for UDP transport
[1682347307.382|56356|ice_transport.cpp :906 ] [ice:0x25216e0] added host stun config for UDP transport
[1682347307.382|56356|ice_transport.cpp :989 ] [ice:0x25216e0] Add srflx reflexive candidates [192.168.49.92:21799 : 192.168.49.92:21799] for comp 1
[1682347307.382|56356|ice_transport.cpp :989 ] [ice:0x25216e0] Add srflx reflexive candidates [192.168.49.92:22898 : 192.168.49.92:22898] for comp 2
[1682347307.382|56356|ice_transport.cpp :469 ] [ice:0x25216e0] Added generic srflx candidates:
[1682347307.387|56356|ice_transport.cpp :707 ] [ice:0x25216e0] UDP initialization success
[1682347307.387|56356|ice_transport.cpp :787 ] [ice:0x25216e0] as slave
[1682347307.388|56356|ice_transport.cpp :881 ] [ice:0x25216e0] (local) ufrag=5d1495c7, pwd=29e8d5446da38dae04605688
[1682347307.388|56356|sipcall.cpp :1872] [call:2214803505268786] Add local attributes for ICE instance [0x5fe8c10]
[1682347307.388|56356|sipcall.cpp :1912] [call:2214803505268786] add ICE local candidates for media [type [AUDIO] enabled [YES] muted [NO] label [audio_0]] @ 0
[1682347307.388|56356|sipvoiplink.cpp :1121] [call:2214803505268786] INVITE@0x7fb0b8b329e8 media update: status 0
[1682347307.388|56356|sdp.cpp :139 ] Set active local session to [0x52c4148]. Was [(nil)]
[1682347307.388|56356|sdp.cpp :503 ] [SDP ANSWER] Local active session:
v=0
o=atlas 3891336107 1 IN IP4 192.168.49.92
s=Call ID 2214803505268786
c=IN IP4 192.168.49.92
t=0 0
a=ice-ufrag:5d1495c7
a=ice-pwd:29e8d5446da38dae04605688
m=audio 0 RTP/SAVP 104 9 2 112 111 110 8 0 101
[1682347307.388|56356|sdp.cpp :147 ] Set active remote session to [0x245f5a8]. Was [(nil)]
[1682347307.388|56356|sdp.cpp :503 ] [SDP ANSWER] Remote active session:
v=0
o=localhost 3891336105 0 IN IP4 192.168.0.217
s=Call ID 7629516086156536
c=IN IP4 192.168.0.217
t=0 0
a=ice-ufrag:4825cdac
a=ice-pwd:3c5a176c6406842d7f98f7c5
m=audio 18770 RTP/SAVP 104 9 2 112 111 110 8 0 101
a=rtpmap:104 opus/48000/2
a=rtpmap:9 G722/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:112 speex/32000
a=rtpmap:111 speex/16000
a=rtpmap:110 speex/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtcp:18771 IN IP4 192.168.0.217
a=sendrecv
a=candidate:Hc0a800d9 1 UDP 2130706431 192.168.0.217 48819 typ host
a=candidate:Ha556a7c0 1 UDP 2130706431 fe80::2c47:5fff:fe35:d569 51892 typ host
a=candidate:Hc0a800d9 2 UDP 2130706430 192.168.0.217 41158 typ host
a=candidate:Ha556a7c0 2 UDP 2130706430 fe80::2c47:5fff:fe35:d569 36779 typ host
[1682347307.388|56356|sipcall.cpp :968 ] [call:2214803505268786] Answering with contact header: <sip:192.168.49.92:5062>
[1682347307.388|56356|sipvoiplink.cpp :892 ] [call:2214803505268786] INVITE@0x7fb0b8b329e8 state changed to 4 (CONNECTING): cause=0, tsx@0x7fb0b404aa98 status 200 (OK)
[1682347307.388|56356|call.cpp :241 ] [call:2214803505268786] state change 0/1, cnx 3/4, code 0
[1682347307.388|56356|call.cpp :275 ] [call:2214803505268786] emit client call state change CURRENT, code 0
[1682347307.389|56356|manager.cpp :603 ] ----- Switch current call id to '2214803505268786' -----
[1682347307.389|56389|sipcall.cpp :2605] [call:2214803505268786] Media negotiation complete
[1682347307.389|56356|manager.cpp :1614] Add audio to call 2214803505268786
[1682347307.389|56389|sipcall.cpp :2671] [call:2214803505268786] Starting ICE
[1682347307.389|56356|manager.cpp :1625] [call:2214803505268786] Attach audio
[1682347307.389|56356|ringbufferpool.cpp :174 ] Bind call 2214803505268786 to call audiolayer_id
[1682347307.389|56389|sdp.cpp :941 ] Media#0 is disabled. Media ports: local 0, remote 18770
[1682347307.389|56356|ringbufferpool.cpp :155 ] Bind rbuf '2214803505268786' to callid 'audiolayer_id'
[1682347307.389|56389|ice_transport.cpp :1231] [ice:0x25216e0] start failed: no remote candidates[1682347307.389|56356|ringbufferpool.cpp :155 ] Bind rbuf 'audiolayer_id' to callid '2214803505268786'
[1682347307.389|56389|sipcall.cpp :2702] [call:2214803505268786] ICE media failed to start
[1682347307.389|56356|audiostream.cpp :50 ] Playback: Creating stream with device (48000Hz, 2 chan
```https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1252TV: can't dictate voice message2023-05-31T20:26:00ZAdrien BéraudTV: can't dictate voice messageIn the conversation view, we should be able to dictate a message by voiceIn the conversation view, we should be able to dictate a message by voicehttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1249Impossible to dismiss edit dialog by pressing outside2023-04-20T14:55:54ZPierre NicolasImpossible to dismiss edit dialog by pressing outside## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: c0e7111b88570646765d3874306f894c39309a66
## Steps to reproduce
- Can you reproduce the bug: at will
...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: c0e7111b88570646765d3874306f894c39309a66
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Go in conversation
2. Long press a message and click edit
2. Press outside
- Actual result: Impossible to cancel the edition dialog.
## Additional information
![unabletoexiteditbyclickingoutside](/uploads/ea4d0e089bc4d02efaad6b851c7a5bde/unabletoexiteditbyclickingoutside.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1248Glitch when long press a message while using the keyboard2023-04-20T15:03:17ZPierre NicolasGlitch when long press a message while using the keyboard## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: c0e7111b88570646765d3874306f894c39309a66
## Steps to reproduce
- Can you reproduce the bug: at will
...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: c0e7111b88570646765d3874306f894c39309a66
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Go in conversation
2. Open the keyboard
2. Long press on message
3. Release focus
- Actual result: There is a glitch (few milliseconds without keyboard and then it shows up)
## Additional information
![glitch_when_selecting_message](/uploads/08de15a8098e9071caac83dc7aac1839/glitch_when_selecting_message.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1244Glitch when opening a media while using the keyboard2023-04-20T15:07:33ZPierre NicolasGlitch when opening a media while using the keyboard## Describe your environment
- Device model: Samsung Galaxy S20 5G SM-G981B/DS
- Android version: 13
- What build you are using: PlayStore Világfa 20230406-01
## Steps to reproduce
- Can you reproduce the bug: occasionally
- ...## Describe your environment
- Device model: Samsung Galaxy S20 5G SM-G981B/DS
- Android version: 13
- What build you are using: PlayStore Világfa 20230406-01
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. Go in conversation
2. Open the keyboard
3. Open a media (tested with a picture)
4. Come back in the app
- Actual result: There is a glitch (few milliseconds without keyboard and then it shows up)
## Additional information
![openmediawhileusingkeyboardmakeglitch](/uploads/9a7c85de88220f52131534c45567a536/openmediawhileusingkeyboardmakeglitch.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1243Open media from conversation also show up the keyboard2023-04-17T13:51:47ZPierre NicolasOpen media from conversation also show up the keyboard## Describe your environment
- Device model: Samsung Galaxy S20 5G SM-G981B/DS
- Android version: 13
- What build you are using: PlayStore Világfa 20230406-01
## Steps to reproduce
- Can you reproduce the bug: occasionally
- ...## Describe your environment
- Device model: Samsung Galaxy S20 5G SM-G981B/DS
- Android version: 13
- What build you are using: PlayStore Világfa 20230406-01
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. Go in conversation
2. Open a media (tested with a picture)
3. Come back in the app
- Actual result: The keyboard show up
## Additional information
![openmediaalsoopenkeyboard](/uploads/8217f35596912ca8734977486ea86930/openmediaalsoopenkeyboard.mp4)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1563Please remove strings that are no longer used in Transifex translation platform2023-05-15T05:30:07ZovariPlease remove strings that are no longer used in Transifex translation platformPlease remove strings that are no longer used on [Transifex](https://explore.transifex.com/savoirfairelinux/) in [Jami](https://explore.transifex.com/savoirfairelinux/jami/), [Jami Website](https://explore.transifex.com/savoirfairelinux/...Please remove strings that are no longer used on [Transifex](https://explore.transifex.com/savoirfairelinux/) in [Jami](https://explore.transifex.com/savoirfairelinux/jami/), [Jami Website](https://explore.transifex.com/savoirfairelinux/jami-website/) and [JAMS - Jami Account Management Server](https://explore.transifex.com/savoirfairelinux/jams-jami-account-management-server/) projects.
This would remove strings which contain incorrect grammar, typos, etc.
If Weblate was used, it is understood that strings that are no longer in use are automatically removed. Surely Transifex has this feature too?
It can also help maintain, and increase, the morale of the translator community.
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1562Please create a separate project in Transifex for Jami documentation (https:/...2023-04-28T19:13:23ZovariPlease create a separate project in Transifex for Jami documentation (https://docs.jami.net/)Please create a separate project in [Transifex](https://explore.transifex.com/savoirfairelinux/) for [Jami documentation](https://docs.jami.net/).
Reasons:
1. Translations for Jami documentation does not show on docs.jami.net anyway.
2....Please create a separate project in [Transifex](https://explore.transifex.com/savoirfairelinux/) for [Jami documentation](https://docs.jami.net/).
Reasons:
1. Translations for Jami documentation does not show on docs.jami.net anyway.
2. Translators will see when the application is 100% translated. At the moment, the highest translation is 71%; however, the application is 100% translated. 29% is just the docs which don't show anyway.
3. [Jami Website](https://explore.transifex.com/savoirfairelinux/jami-website/) is a separate project; so it seems appropriate that Jami Documentation is also a separate project.
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1242Perceptual bug: timestamp should be absolute instead of relative in contacts ...2023-04-15T07:22:31ZPierre MétrasPerceptual bug: timestamp should be absolute instead of relative in contacts listI don't understand when the contacts list display is refreshed. For a week, my contacts showed the bug I'm reporting, while it's no more the case presently because the contacts lists has been refreshed...
In the contacts list, besides e...I don't understand when the contacts list display is refreshed. For a week, my contacts showed the bug I'm reporting, while it's no more the case presently because the contacts lists has been refreshed...
In the contacts list, besides each contact icon, there are 2 lines:
1. The display name of the contact
2. A **relative timestamp** with he last message in the discussion with that contact.
The timestamp is relative (example: "2 hours ago" or "last week"), instead of absolute (example: 2023-04-14 12:36).
I've been using my phone with Jami Android client and the contacts list displayed "**36s ago**, last message..." or "**4 hours ago**, last message..." still for a week. Because this list is not regularly updated, one can feel that the Jami application has frozen, asking himself why the display does not refresh?
If it's normal not to regularly update the contacts list, it would be more natural and less worrying for the user to use absolute timestamps because they are always correct.
## Describe your environment
Please specify the following:
- Jami version: Vilagfa 20230406-01
- Device model: Samsung Galaxy A53
- Android version: 13
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. Send a message to a contact
2. Go back to the contacts list
3. Besides the contact it should display "**A few seconds ago**, the message..."
4. Wait a few minutes, it should still display "**A few seconds ago**, ..." instead of "A few minutes ago, ..."
- Actual result: Incorrect timestamp
- Expected result: Correct relative timestamp regularly updated, or absolute timestamp.
## Additional information
The reason my Android phone updated the contact list and does not exhibit the bug presently is perhaps because I started my PC with Jamy to report the bug and the two devices synchronized...https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1240Daemon folder on jami-android/libjamiclient/src/main/kotlin/net/jami/ missing2023-04-27T01:26:40ZFebry Dwi PutraDaemon folder on jami-android/libjamiclient/src/main/kotlin/net/jami/ missingHi, i want to run jami client android project on my android studio. I'm finished the setup but when i try to build the project i get these error.
![Jepretan_Layar_2023-04-14_pukul_23.04.09](/uploads/6f235dc42da465a993e5fc3c4ea5cf27/Jepr...Hi, i want to run jami client android project on my android studio. I'm finished the setup but when i try to build the project i get these error.
![Jepretan_Layar_2023-04-14_pukul_23.04.09](/uploads/6f235dc42da465a993e5fc3c4ea5cf27/Jepretan_Layar_2023-04-14_pukul_23.04.09.png)
These missing files coming from Daemon folder on jami-android/libjamiclient/src/main/kotlin/net/jami/
Am i missing some configuration perhaps?Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1239SIP call on android: plain RTP session impossible (intentionally unencrypted ...2023-04-14T12:29:07ZTobias HuberSIP call on android: plain RTP session impossible (intentionally unencrypted LAN-PBX)Hi, since Android 13 doesn't offer native SIP support anymore, I thought this great Jami thing could step in...
Unfortunately, it was quiet inconvenient to get at least some idea why this doesn't work with my LAN/VPN PBX
_(Inconvenience...Hi, since Android 13 doesn't offer native SIP support anymore, I thought this great Jami thing could step in...
Unfortunately, it was quiet inconvenient to get at least some idea why this doesn't work with my LAN/VPN PBX
_(Inconvenience: LAN/VPN PBX is asterisk 1.6, which doesn't use identical string for account identification and user authentication; the user corresponding to the password for authentication is different to the name of the SIP account.
It's possible to set Jami up that way, but it's quiet hidden - besides some more not so minor UI nits on android, but that will be a different issue report.)_
I checked that all Security->Security switches are off (SRTP and TLS transport).
1.) Initiating (outgoing) call fails because:
`"Rejecting secure audio stream without encryption details: audio 19686 RTP/SAVP 104 9 2 112 111 110 8 0 101"`
> <--- SIP read from UDP:172.21.97.226:5060 ---> [115/1865]
> INVITE sip:11@pbx.example.net SIP/2.0
> Via: SIP/2.0/UDP 172.21.97.226:5060;rport;branch=z9hG4bKPjaf1c522c-6e92-4539-b899-15c2bad55ad1
> Max-Forwards: 70
> From: <sip:tobimob_line1@pbx.example.net>;tag=b2110c22-6e14-4381-8a99-cc1e40d3872f
> To: <sip:11@pbx.example.net>
> Contact: <sip:tobimob_line1@172.21.97.226:5060>
> Call-ID: 4b970369-1b13-44da-b798-3a74f51d8c39
> CSeq: 629 INVITE
> Subject: Phone call
> Allow: SUBSCRIBE, NOTIFY, REFER, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, OPTIONS, MESSAGE, PUBLISH
> Supported: replaces
> User-Agent: Jami Daemon 13.7.0 (android)
> Authorization: Digest username="tobi.huber", realm="pbx.example.net", nonce="3b54e054", uri="sip:11@pbx.example.net", response="4070f25aadda2536ee24058551dfb64
> 1", algorithm=MD5
> Content-Type: application/sdp
> Content-Length: 1047
>
> v=0
> o=localhost 3890394360 0 IN IP4 172.21.97.226
> s=Call ID 8706183892147327
> c=IN IP4 172.21.97.226
> t=0 0
> a=ice-ufrag:42a09c4e
> a=ice-pwd:04afb39763f13c7f32a67b91
> m=aud--- (15 headers 27 lines) ---
> Sending to 172.21.97.226:5060 (no NAT)
> Using INVITE request as basis request - 4b970369-1b13-44da-b798-3a74f51d8c39
> Found peer 'tobimob_line1' for 'tobimob_line1' from 172.21.97.226:5060
> Found RTP audio format 104
> Found RTP audio format 9
> Found RTP audio format 2
> Found RTP audio format 112
> Found RTP audio format 111
> Found RTP audio format 110
> Found RTP audio format 8
> Found RTP audio format 0
> Found RTP audio format 101
> Found unknown media description format opus for ID 104
> Found audio description format G722 for ID 9
> Found audio description format G726-32 for ID 2
> Found audio description format speex for ID 112
> Found audio description format speex for ID 111
> Found audio description format speex for ID 110
> Found audio description format PCMA for ID 8
> Found audio description format PCMU for ID 0
> Found audio description format telephone-event for ID 101
[Apr 13 19:05:59] ERROR[101987][C-000005d5]: chan_sip.c:33575 int setup_srtp(struct sip_srtp **): No SRTP module loaded, can't setup SRTP session.
[Apr 13 19:05:59] WARNING[101987][C-000005d5]: chan_sip.c:10417 int process_sdp(struct sip_pvt *, struct sip_request *, int): Rejecting secure audio stream witho
ut encryption details: audio 19686 RTP/SAVP 104 9 2 112 111 110 8 0 101
Why does it send RTP/SAVP although I disabled SRTP?
2.) Incoming call signalling works, but not possible to establish RTP session:
```
"Ignoring audio media offer because port number is zero" and
"Failing due to no acceptable offer found"
```
Ringing:
> <--- SIP read from UDP:172.21.97.226:5060 --->
> SIP/2.0 180 Ringing
> Via: SIP/2.0/UDP 172.21.98.12:5060;received=172.21.98.12;branch=z9hG4bK0d2bf1b6
> Call-ID: 1e4bf56a62264ba6792450e4506bed52@pbx.example.net
> From: "T. Huber (22)" <sip:thbuero@pbx.example.net>;tag=as48fb14ca
> To: <sip:tobimob_line1@172.21.97.226>;tag=6c456d21-e6ae-4c85-bf04-da0aaf56e758
> CSeq: 102 INVITE
> User-Agent: Jami Daemon 13.7.0 (android)
> Allow: SUBSCRIBE, NOTIFY, REFER, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, OPTIONS, MESSAGE, PUBLISH
> Contact: <sip:tobimob_line1@172.21.97.226:5060>
... (snipped)
Accepting call on Jami:
> <--- SIP read from UDP:172.21.97.226:5060 --->
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 172.21.98.12:5060;received=172.21.98.12;branch=z9hG4bK0d2bf1b6
> Call-ID: 1e4bf56a62264ba6792450e4506bed52@pbx.example.net
> From: "T. Huber (22)" <sip:thbuero@pbx.example.net>;tag=as48fb14ca
> To: <sip:tobimob_line1@172.21.97.226>;tag=6c456d21-e6ae-4c85-bf04-da0aaf56e758
> CSeq: 102 INVITE
> User-Agent: Jami Daemon 13.7.0 (android)
> Allow: SUBSCRIBE, NOTIFY, REFER, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, OPTIONS, MESSAGE, PUBLISH
> Supported: replaces
> Contact: <sip:tobimob_line1@172.21.97.226:5060>
> Content-Type: application/sdp
> Content-Length: 142
>
> v=0
> o=localhost 3890395686 1 IN IP4 172.21.97.226
> s=Call ID 5890041505306313
> c=IN IP4 172.21.97.226
> t=0 0
> m=audio 0 RTP/AVP 9 8 0 3 101
> <------------->
chan_sip.c:10008 int process_sdp(struct sip_pvt *, struct sip_request *, int): Ignoring audio media offer [5/1992]
port number is zero
chan_sip.c:10438 int process_sdp(struct sip_pvt *, struct sip_request *, int): Failing due to no acceptabl[3/1992]
found
**Here's a working internal call, where sipdroid is the user agent on the same phone:**
> <--- SIP read from UDP:172.21.97.226:40739 --->
> SIP/2.0 180 Ringing
> Via: SIP/2.0/UDP 172.21.98.12:5060;branch=z9hG4bK04f5274c
> To: <sip:tobimob_line1@10.26.229.169:40739;transport=udp>;tag=fb8b4ff3c7a73ee8
> From: "T. Huber (22)" <sip:thbuero@pbx.example.net>;tag=as686012bd
> Call-ID: 3547fb4e68213eb90d8295ae221e36ea@pbx.example.net
> CSeq: 102 INVITE
> Server: Sipdroid/6.3 beta/Pixel 7
> Content-Length: 198
> Content-Type: application/sdp
... (snipped)
Accepting call on SIPdroid:
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 172.21.98.12:5060;branch=z9hG4bK04f5274c
> To: <sip:tobimob_line1@10.26.229.169:40739;transport=udp>;tag=fb8b4ff3c7a73ee8
> From: "T. Huber (22)" <sip:thbuero@pbx.example.net>;tag=as686012bd
> Call-ID: 3547fb4e68213eb90d8295ae221e36ea@pbx.example.net
> CSeq: 102 INVITE
> Contact: <sip:tobimob_line1@10.26.229.169:40739;transport=udp>
> Server: Sipdroid/6.3 beta/Pixel 7
> Content-Length: 198
> Content-Type: application/sdp
>
> v=0
> o=tobimob_line1@pbx.example.net 0 0 IN IP4 10.26.229.169
> s=Session SIP/SDP
> c=IN IP4 10.26.229.169
> t=0 0
> m=audio 21000 RTP/AVP 9 101
> a=rtpmap:9 G722/8000
> a=rtpmap:101 telephone-event/8000
> <------------->
**Significant difference here is "m=audio ...." lines.**
With SIPdroid (the working incomming call), it reads
> m=audio 21000 RTP/AVP 9 101
while with jami (not working)
> m=audio 0 RTP/AVP 9 8 0 3 101
I'd very much appreciate if somebody could take care and bring back originating strenghts of Jami in that it's usable as a working SIP UA - for plain RTP too!
Especially due to dropped native SIP support in recent android versions!
The android settings UI is broken too, like already mentioned, but ther's the workaround to use it in landscape mode, which makes it possible to sroll the account-enabler switch out of overlapping tab selection area... Will tell in a different issue report.
Thanks in advance,
-Tobihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1226[Android] message bubble partially covered in conversation view with a combin...2024-03-19T05:48:48ZPreston Leppanen[Android] message bubble partially covered in conversation view with a combination of higher display scale and font scaleBy setting Android's display scale and font scale to larger, the bottom message bubble is partially covered by message box in conversation view.
It's better explained with a screenshot:
<img src="https://git.jami.net/savoirfairelinux/j...By setting Android's display scale and font scale to larger, the bottom message bubble is partially covered by message box in conversation view.
It's better explained with a screenshot:
<img src="https://git.jami.net/savoirfairelinux/jami-project/uploads/5a6f2d3827f8f3ceec61f9d8c69ce985/image_7.png" width="200"/>
(Nope, you can't scroll up anymore)
Similar issues occur in Account Settings view where some texts are covered by the buttons.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1224Test the app2024-03-28T00:05:08ZPierre NicolasTest the apphttps://developer.android.com/studio/test
# Définition of Done
Provide a way to be able to test the components such as the account combo box, conversation view, call page, settings page
Provide a documentation for new developers
Add ...https://developer.android.com/studio/test
# Définition of Done
Provide a way to be able to test the components such as the account combo box, conversation view, call page, settings page
Provide a documentation for new developers
Add a CI job running the tests
Ideally a dev should be able to test without real data for simpler scenarios (mock model results)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1223TV: Make SIP account creation possible2023-03-30T15:34:34ZPierre NicolasTV: Make SIP account creation possibleNot possible to create a SIP account
## Describe your environment
- Device model: Nvidia Shield android TV P2571
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Add...Not possible to create a SIP account
## Describe your environment
- Device model: Nvidia Shield android TV P2571
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Additional information
No buttons for this action :
![jamsousip1](/uploads/0d3b766fc4742e21642d148fbf839f0a/jamsousip1.png)
![jamsousip2](/uploads/70350b6e0b37dae4a9c10fe361fd8521/jamsousip2.png)