savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2018-05-22T00:35:45Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/362Android: Imposible to send message using mane instead ring ID2018-05-22T00:35:45ZJami BotAndroid: Imposible to send message using mane instead ring IDIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Steps:
In search field type registered name , click enter
Text message to this account .
Result : message not send , state...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Steps:
In search field type registered name , click enter
Text message to this account .
Result : message not send , state `Sending message...`https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/328Unable to update Ring account after Beta 2 upgrade2018-05-22T00:34:30ZJami BotUnable to update Ring account after Beta 2 upgradeIssue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Juneau (njuneau)**
Summary
=======
After the Beta 2 November release, I am unable to use my Ring account because the update process never ends.
...Issue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Juneau (njuneau)**
Summary
=======
After the Beta 2 November release, I am unable to use my Ring account because the update process never ends.
Steps to reproduce
==================
1. Have a Ring account created using the Beta 1 Ring release
2. Update the Ring client
3. Open Ring (the account migration notification will pop up)
4. Enter a password and confirm the password
5. Update the account
Current behaviour
-----------------
A pop-up window showing "Updating account" will appear. Ring may be left opened for many hours (I left it open for a whole night), but the process will never end.
Closing Ring and re-opening it will trigger the account migration process (prompting for a new password).
Killing the Ring background process doesn't work.
The account settings can no longer be viewed and modified since the migration wizard always shows up.
Suggested behaviour
-------------------
If the update process takes longer than expected, an error or a warning should be shown to the user. Otherwise, account migration should work.
Also, the UI should let the user manage his/her account if the migration failed to work. Otherwise, he/she cannot post his/her settings in the bug report ;) .
Technical information
---------------------
\* Phone : OnePlus X (ONE E1005)
\* OS: Oxygen OS 3.1.3 (Android 6.0.1, not rooted)
\* The Ring account was configured to use "turn.ring.cx" TURN server before the migration. However, I cannot validate if it's still the case (see "Suggested behaviour")
I do not have the Android logs, but if I ever get a hold of them, I'll post them here.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/313android: no audio with Ring 20160803 and Cyanogenmod 13.0-20160530-NIGHTLY-wt...2018-05-22T00:34:02ZJami Botandroid: no audio with Ring 20160803 and Cyanogenmod 13.0-20160530-NIGHTLY-wt88047Issue generated from Tuleap's migration script.
**Originally submitted by: Andres Gomez (tanty)**
In my company, we have an Asterisk based SIP server.
I have activated the TLS option and the registration succeeds but, when placing ...Issue generated from Tuleap's migration script.
**Originally submitted by: Andres Gomez (tanty)**
In my company, we have an Asterisk based SIP server.
I have activated the TLS option and the registration succeeds but, when placing a call, the connection works but no audio is received.
I've also tried deactivating TLS with the same result: proper registration, call succeeds but audio is not received/heard.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/293Ring used up all the data finding a person on DHT2018-05-22T00:32:46ZJami BotRing used up all the data finding a person on DHTIssue generated from Tuleap's migration script.
**Originally submitted by: NAVDEEP SINGH SIDHU (navdeepsingh)**
I was testing the ring for our use. I created my account on my Android device and also imported it on Ubuntu 16.04 desktop. ...Issue generated from Tuleap's migration script.
**Originally submitted by: NAVDEEP SINGH SIDHU (navdeepsingh)**
I was testing the ring for our use. I created my account on my Android device and also imported it on Ubuntu 16.04 desktop. I also created another account on Android to test if it works or not. I didn't received any message from my second account and it looks like ring used all my data trying to send the message over network.
So from my point of view problem is related to message delivery and confirmation. But you guys know it better.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/282Android version can`t receive text messages during call2018-05-22T00:26:33ZJami BotAndroid version can`t receive text messages during callIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
<p>During call android version can only send messages , but can`t receive.</p>
<p>&nbsp;</p>Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
<p>During call android version can only send messages , but can`t receive.</p>
<p> </p>https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/261crash: receiving unknown mime/type2018-05-21T23:28:43ZJami Botcrash: receiving unknown mime/typeIssue generated from Tuleap's migration script.
**Originally submitted by: Romain B. (rbertozzi)**
<p>When calling an Android device from a client sending a profile, the app crashes when calling the StringMap\_getRaw method.</p>
<p...Issue generated from Tuleap's migration script.
**Originally submitted by: Romain B. (rbertozzi)**
<p>When calling an Android device from a client sending a profile, the app crashes when calling the StringMap\_getRaw method.</p>
<p>This method is throwing an out of range exception if the key passed as parameter is unknown from the stringmap.</p>
<p>Resolution: before calling getRaw, the application java code is calling has\_key to check the state of the stringmap.</p>https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/250Android: application crashes when deleting all Ring accounts and trying to call2018-05-21T23:12:59ZJami BotAndroid: application crashes when deleting all Ring accounts and trying to callIssue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
<p>The Android application crashes&nbsp;when deleting all Ring accounts and then trying to make a Ring call.</p>
<p>Steps to r...Issue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
<p>The Android application crashes when deleting all Ring accounts and then trying to make a Ring call.</p>
<p>Steps to reproduce:</p>
<ol>
<li>Create a Ring account</li>
<li>Make a Ring call to somebody</li>
<li>Go to the settings and delete the Ring account</li>
<li>Go back to the home of the application, go to the conversation created at 2., and try to call the person again</li>
<li>The application freezes</li>
</ol>
<p>Tested on 20160315 from F-droid.</p>https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/228Ring doesn't ring2018-05-21T22:37:07ZJami BotRing doesn't ringIssue generated from Tuleap's migration script.
**Originally submitted by: Dmitry (dikins)**
Hi
I v tried v.2.0.009 and 2.0.003 (from f-droid). They both have the same problem - no voice communication. Only text messaging is allowed. ...Issue generated from Tuleap's migration script.
**Originally submitted by: Dmitry (dikins)**
Hi
I v tried v.2.0.009 and 2.0.003 (from f-droid). They both have the same problem - no voice communication. Only text messaging is allowed.
Frankly the app is very buggy. And please add the delivery status for messages.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1418Wrong UDP ICE candidates (UPnP Enabled/TURN disabled)2023-10-26T15:53:59ZSébastien BlinWrong UDP ICE candidates (UPnP Enabled/TURN disabled)# Scenario
+ Connect to JamiLabs
+ Disable TURN for the account, Enable UPnP
+ Start a call
# Expected result
UDP ICE candidates should show public ip in srflx candidates
# Current result
+ UDP candidates doesn't have the public ip ...# Scenario
+ Connect to JamiLabs
+ Disable TURN for the account, Enable UPnP
+ Start a call
# Expected result
UDP ICE candidates should show public ip in srflx candidates
# Current result
+ UDP candidates doesn't have the public ip in the srflx list
+ However, TCP candidates are correct
Meaning that depending the configuration, you can have a TCP negotiation success and media failure (causing the call to stop)
```
[1698335554.247|23970|sdp.cpp :498 ] [SDP OFFER] Remote active session:
v=0
o=localhost 3907324354 1 IN IP4 192.168.0.147
s=Call ID 1888667388261686
c=IN IP4 192.168.0.147
t=0 0
a=ice-ufrag:124cdb6c
a=ice-pwd:621c04a84d50cacf2ef374ff
m=audio 27538 RTP/SAVP 104 101
a=rtpmap:104 opus/48000/2
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtcp:27539 IN IP4 192.168.0.147
a=sendrecv
a=candidate:Hc0a80093 1 UDP 2130706431 192.168.0.147 42590 typ host
a=candidate:Ha0989db2 1 UDP 2130706431 fe80::7c8d:d8ff:fed4:ac16 42915 typ host
a=candidate:Sc0a80093 1 UDP 1694498303 192.168.0.147 21296 typ srflx
a=candidate:Hc0a80093 1 UDP 2130706431 192.168.0.147 21296 typ host
a=candidate:Hc0a80093 2 UDP 2130706430 192.168.0.147 38712 typ host
a=candidate:Ha0989db2 2 UDP 2130706430 fe80::7c8d:d8ff:fed4:ac16 37073 typ host
a=candidate:Sc0a80093 2 UDP 1694498302 192.168.0.147 23972 typ srflx
a=candidate:Hc0a80093 2 UDP 2130706430 192.168.0.147 23972 typ host
m=video 57832 RTP/SAVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 profile-level-id=428029
a=rtcp:57833 IN IP4 192.168.0.147
a=sendrecv
a=candidate:Hc0a80093 3 UDP 2130706429 192.168.0.147 42826 typ host
a=candidate:Ha0989db2 3 UDP 2130706429 fe80::7c8d:d8ff:fed4:ac16 48183 typ host
a=candidate:Sc0a80093 3 UDP 1694498301 192.168.0.147 22465 typ srflx
a=candidate:Hc0a80093 3 UDP 2130706429 192.168.0.147 22465 typ host
a=candidate:Hc0a80093 4 UDP 2130706428 192.168.0.147 42565 typ host
a=candidate:Ha0989db2 4 UDP 2130706428 fe80::7c8d:d8ff:fed4:ac16 40706 typ host
a=candidate:Sc0a80093 4 UDP 1694498300 192.168.0.147 21643 typ srflx
a=candidate:Hc0a80093 4 UDP 2130706428 192.168.0.147 21643 typ host
```https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1118No connectivity change on background/router disconnect2022-09-16T17:58:36ZSébastien BlinNo connectivity change on background/router disconnect# Scenario
+ Alice (android - wifi & LTE enabled - wifi enabled), Bob (desktop)
+ Bob calls Alice => OK
+ Alice pass jami in background, phone is idle
+ Disconnect the router (LTE will be used)
+ After 1 min, reconnect the router and wa...# Scenario
+ Alice (android - wifi & LTE enabled - wifi enabled), Bob (desktop)
+ Bob calls Alice => OK
+ Alice pass jami in background, phone is idle
+ Disconnect the router (LTE will be used)
+ After 1 min, reconnect the router and wait for connectivity
+ Then, first call fails
# Observation
There is no log in HardwareService connectivityChangedSébastien BlinOlivier DionAdrien BéraudSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1111SIP account can't receive incoming calls with TLS activated2022-10-26T15:13:31ZLem MingSIP account can't receive incoming calls with TLS activatedWhen TLS is enabled in the SIP account, no incoming calls are received.
Environment:
- OS: Android 11
- Jami version: Taranis - 20220615-01 (F-Droid)
- Device: Teracube 2e
- SIP provider: voip.ms
Steps to reproduce:
1) Create a SIP ac...When TLS is enabled in the SIP account, no incoming calls are received.
Environment:
- OS: Android 11
- Jami version: Taranis - 20220615-01 (F-Droid)
- Device: Teracube 2e
- SIP provider: voip.ms
Steps to reproduce:
1) Create a SIP account following this [post](https://forum.jami.net/t/how-can-i-create-a-sip-account-in-the-android-version-of-jami/1294)
2) Follow the [Jami wiki on voip.ms](https://wiki.voip.ms/article/Jami) for the basic configuration
3) Activate: Encrypt media streams (SRTP)
4) Activate: Enable SDES as key exchange protocol
5) Activate: Use TLS Transport
6) Permutate between 5061 (voip.ms TLS port) and the default value for whatever port options available
Expected and actual behaviors:
- On Jami, the account is online
- Echo test work (voip.ms: 4443)
- On the portal, it is registered with secure transport
Expected behavior:
- I can receive incoming calls
Actual behavior:
- I can't receive incoming calls
Following steps:
7) Deactivate "Use TLS transport"
Actual behaviors:
- On Jami, the account is online
- Echo test work (voip.ms: 4443)
- On the portal, it is registered but **no with secure transport**
- I **can** receive incoming calls
Following steps:
8) Install Linphone for Android
9) Follow the Linphone for Android tutorial specific for voip.ms [here](https://wiki.voip.ms/article/Linphone_Android)
Expected and actual behaviors:
- On Linphone, the account is online
- Echo test work (voip.ms: 4443)
- On the portal, it is registered with secure transport
- I can receive incoming calls
For the same environment:
- same network
- same voip.ms portal configuration
- same device
it works for Linphone but not for Jami.Sébastien BlinAntoine NoreauSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1083Notifications: hangup not working2022-02-15T12:06:14ZMaxime CalletNotifications: hangup not working- Ring version: 326
- Device model: p30
- Android version: 10
- What build you are using: F-droid & Play Store & build
## Steps to reproduce
- Can you reproduce the bug: [at will | occasionally | not at all]
- Steps:
1. m...- Ring version: 326
- Device model: p30
- Android version: 10
- What build you are using: F-droid & Play Store & build
## Steps to reproduce
- Can you reproduce the bug: [at will | occasionally | not at all]
- Steps:
1. make a call
2. try to hangup using the dedicated button in the notification tray
- Actual result: button freezing and call is not terminated
- Expected result: should end the callMaxime CalletMaxime Callethttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1070Plugins: add new UI for plugins with pref per account2022-05-04T19:09:20ZMaxime CalletPlugins: add new UI for plugins with pref per account- Add the new UI for the update plugins system inside the bottom control panel (bottom sheet)- Add the new UI for the update plugins system inside the bottom control panel (bottom sheet)Next major releaseAmirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1059Overlaping elements in account settings2023-11-01T18:09:55ZAltonsOverlaping elements in account settings
## Describe your environment
Please specify the following:
- Ring version: Taranis 20211210-01
- Device model: Samsung Galaxy Core Prime
- Android version: 5
- What build you are using: F-droid
## Steps to reproduce
- Can y...
## Describe your environment
Please specify the following:
- Ring version: Taranis 20211210-01
- Device model: Samsung Galaxy Core Prime
- Android version: 5
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
2. Open account settings
- Actual result: Some elements overlap!
- Expected result: The elements should not overlap!
## Additionnal information
![image](/uploads/fcd82de68a33a235c1e6ecf896de3218/image.png)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1049[Own?] Profile picture in contact list is missing2023-03-31T19:07:13ZElys[Own?] Profile picture in contact list is missingJami Android (beta, Version 20211202-01)
Mate 20 Pro (EMUI 11)
Your own (Jami-) account name is normally shown in contacts (so you can send yourself messages Windows -> Android etc.) after you have added yourself.
However now the accou...Jami Android (beta, Version 20211202-01)
Mate 20 Pro (EMUI 11)
Your own (Jami-) account name is normally shown in contacts (so you can send yourself messages Windows -> Android etc.) after you have added yourself.
However now the account name is gone.
AND the profile picture of yourself ("contacts) is not shown anymore.
![Accountmissing](/uploads/14cb3cf5118b5eb9926f81e10c170f11/Accountmissing.png)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1046Overview: LocationSharing2022-01-04T16:05:28ZMaxime CalletOverview: LocationSharing## Android location sharing
This issue wants to regroup in one all the known bugs and features request available. This is done to give a general overview on how the sharing location feature must be improved and give a better global visi...## Android location sharing
This issue wants to regroup in one all the known bugs and features request available. This is done to give a general overview on how the sharing location feature must be improved and give a better global visibility to team members and users.
## Current bugs
- [ ] Fix cross platform location sharing (ios/android)
- [ ] Location sharing does not always show when you open the conversation and you have to click on the notification¨
- [ ] ...
- [ ] ...
## Features request pool
- [ ] the Map should be contained in a card like a message or a link [#960](https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/960)
- [ ] ...
- [ ] ...Maxime CalletMehdi GhayourKateryna KostiukAdrien BéraudAmirhossein NaghshzanMaxime Callethttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1044Build: Transition to Kotlin DSL2021-12-15T19:03:00ZMaxime CalletBuild: Transition to Kotlin DSLMaxime CalletMaxime Callethttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1032Conference: doesn't delete particpant from participants list when call fails2021-12-08T15:21:34ZMaxime CalletConference: doesn't delete particpant from participants list when call fails- Ring version: `Android last beta 05112021`
- Device model: `Samsung tab 2`
- Android version: `7.0`
- What build you are using: `playstore / f-droid`
## Steps to reproduce:
- Can you reproduce the bug: `at will`
- Steps:
1. Add a...- Ring version: `Android last beta 05112021`
- Device model: `Samsung tab 2`
- Android version: `7.0`
- What build you are using: `playstore / f-droid`
## Steps to reproduce:
- Can you reproduce the bug: `at will`
- Steps:
1. Add a new participant to a call
2. Refuse the call
## Actual result:
![20211110_191431](/uploads/21af815f1b4874ca973789ac54dec354/20211110_191431.png)
## Expected result:
The participant should be deleted from the list when the call fails/endMaxime CalletMaxime Callethttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1031Rework contact requests2022-11-26T20:52:10ZSébastien BlinRework contact requestsI see several bugs with contact requests:
1. If you have 5 contact requests, declining the first one will remove the last from the list
2. After accepting the first one, it will clone the conversation, but let the item in the contact r...I see several bugs with contact requests:
1. If you have 5 contact requests, declining the first one will remove the last from the list
2. After accepting the first one, it will clone the conversation, but let the item in the contact request tab until we refresh the view
3. No metadata shown for group swarm with profiles
4. If you decline a conversation ; restarting Jami will show you the previously rejected conversation.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1028Conversation: Missing messages in conversation2022-08-28T03:07:30Zmika-nlConversation: Missing messages in conversation
When you receive a message on android, you do not see the message appear (not even a notification) but I know that the other person has sent something.
force closing and reopening the android app solves the problem for a while.
this hap...
When you receive a message on android, you do not see the message appear (not even a notification) but I know that the other person has sent something.
force closing and reopening the android app solves the problem for a while.
this happens a few times a day.
Sometimes the contact list is also empty, even then it helps to close the app completely and restart it.
It seems that the demon continues to work but the UI crashes
Please specify the following:
- Ring version: latest jami (beta) but also earlyer beta
- Device model: oneplus 6
- Android version: lineageOS
- What build you are using: Play Store
but also same version jami on oppo a72 give this problem.Maxime CalletMaxime Callet