jami-client-android issueshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues2018-05-30T14:29:50Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/478Failing messages are shown like SUCCEED2018-05-30T14:29:50ZJami BotFailing messages are shown like SUCCEEDIssue generated from Tuleap's migration script.
**Originally submitted by: Sébastien Blin (sblin)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Android 90b95bf2dad3e1358bd5f0fc3a...Issue generated from Tuleap's migration script.
**Originally submitted by: Sébastien Blin (sblin)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Android 90b95bf2dad3e1358bd5f0fc3a00b24d082f300d
\* Reproduce steps:
Send a message to a non connected contact and wait a bit.
adb will show something like
[message 5e9449a405e5f139] status changed to FAILURE
\* Expected result:
The message should be mentioned as failed
\* Actual result:
No error, no "sending..." message, it's like the message is successfully transmittedPierre DucheminPierre Ducheminhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/444[Android] Audio call to same username (intercom mode) from Smartphone (Androi...2018-06-08T10:54:55ZJami Bot[Android] Audio call to same username (intercom mode) from Smartphone (Android) to Computer (Linux)Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
Smartphone:
Android 4.4.2
Ring 1.0 - 20170803
Connected by WiFi
Computer:
Linux Mint 18.2 Cinnamon 64-bit
The GNOME client for Rin...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
Smartphone:
Android 4.4.2
Ring 1.0 - 20170803
Connected by WiFi
Computer:
Linux Mint 18.2 Cinnamon 64-bit
The GNOME client for Ring.
Liberté, Égalité, Fraternité - Version 1.0
built on 2017-08-03 21:36:55 UTC
1. Both Smartphone and Computer are signed into Ring
2. On Smartphone:
(a) Click on contact
(b) Click on ⋮ “Unicode Character 'VERTICAL ELLIPSIS' (U+22EE)” located at the upper right
(c) Click on ‘Audio call’
3. On Computer:
(a) Answer call
4. On Smartphone
(a) Video call has been initiated. Should \*only\* be an audio call, with \*no\* video.
Please advise if you need more information or when this has been fixed to test.
Thank youPierre DucheminPierre Ducheminhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/490Some emojis are not displayed stand-alone (emoji-only messages)2018-06-11T21:18:00ZHugo LefeuvreSome emojis are not displayed stand-alone (emoji-only messages)Emojis are supposed to be displayed stand-alone (without background), but this feature is broken with some specific emojis, e.g. 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
I suspect bad handling of Emoji 3.0 (Unico...Emojis are supposed to be displayed stand-alone (without background), but this feature is broken with some specific emojis, e.g. 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
I suspect bad handling of Emoji 3.0 (Unicode 9.0).Full Emoji support 🚩Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/453Delete unmigrated Account2018-06-29T13:53:44ZJami BotDelete unmigrated AccountIssue generated from Tuleap's migration script.
**Originally submitted by: David (davidak)**
What i have done:
- Installed 20160803 from F-Droid
- create new Ring account
- update to 20161103
Now i can migrate the Account,...Issue generated from Tuleap's migration script.
**Originally submitted by: David (davidak)**
What i have done:
- Installed 20160803 from F-Droid
- create new Ring account
- update to 20161103
Now i can migrate the Account, what takes forever \#1255 (waited about 24h!), but i can't just delete the Account.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/460screen rotation causes the lost of text input2018-08-15T19:37:34ZJami Botscreen rotation causes the lost of text inputIssue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
\* Environment:
Android (tested build:
\* Reproduce steps:
When in the middle of doing something (entering a phone numbe...Issue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
\* Environment:
Android (tested build:
\* Reproduce steps:
When in the middle of doing something (entering a phone number, searching a contact, typing a text message, etc.), if the screen is rotated (from portrait to landscape or vice-versa), the state is lost.
\* Expected result:
The current state of what the user is in the middle of doing should \*not\* be affected by rotating the screen. In particular, text entered in any dialog should be preserved.
\* Actual result:
The state is reset. For example, messages being edited are lost when the screen orientation is changed.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/491Ring stays on launch screen2018-10-29T13:41:49ZPierre DucheminRing stays on launch screen## Describe your environment
- Ring version: 20180511
- Device model: Moto G (2nd generation)
- Android version: Android 6.0
- What build you are using: Play Store
## Summary
Ring stays on launch screen.
## Steps to reproduce
...## Describe your environment
- Ring version: 20180511
- Device model: Moto G (2nd generation)
- Android version: Android 6.0
- What build you are using: Play Store
## Summary
Ring stays on launch screen.
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open app
2. If asked answer "allow" to both permissions
3. The launch screen shows
- Actual result: The app is stuck on launch screen
- Expected result: The app loads correctly and moves to link/create account screen
## Additional information
Original e-mail from Joel:
I have a Moto G (2nd generation) with Android 6.0.
I installed the Ring client from the google play store.
When I start it, the blue screen with white ring logo
appears. The spinner beneath it keeps spinning.
I uninstalled and re-installed. On first open, I got
an 'app not responding, do you want to close it?'
dialog. On closing and opening again I am stuck at the
spinner.
btw, on install I gave the app both permissions it asked
for.Pierre DucheminPierre Ducheminhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/366After incorrect app closing , account creation wizard could appear2018-10-29T13:43:13ZJami BotAfter incorrect app closing , account creation wizard could appearIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Sometimes when application freeze, after restarting you could see account creation wizard , even if you have account already con...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Sometimes when application freeze, after restarting you could see account creation wizard , even if you have account already configured .Pierre DucheminPierre Ducheminhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/299video from station1 does not display in station22018-10-29T13:43:24ZJami Botvideo from station1 does not display in station2Issue generated from Tuleap's migration script.
**Originally submitted by: martin (martin)**
I installed ring on ubuntu and on a android 5 set top box.
The android set top box has a logitech webcam connected via USB (UVC).
I make a ...Issue generated from Tuleap's migration script.
**Originally submitted by: martin (martin)**
I installed ring on ubuntu and on a android 5 set top box.
The android set top box has a logitech webcam connected via USB (UVC).
I make a test call from android to ubuntu. (Or vice versa with same result)
Call is established.
In android I see the small picture from the android webcam, and I see the big picture from the ubuntu webcam.
In ubuntu, I see the small picture from the ubuntu webcam and the big picture is black.
So the camera in android works (I see the \_self\_ picture), but the video is not shown in ubuntu.Pierre DucheminPierre Ducheminhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/547Regression on QR code generation2019-02-01T15:10:08ZMohamed FenjiroRegression on QR code generationHi there,
There seems to be a problem regarding the QR generator. Everytime I try to generate a new one to add a new contact, the other device on ios is telling me "bad QR code". Please fix this as this an important feature on the custo...Hi there,
There seems to be a problem regarding the QR generator. Everytime I try to generate a new one to add a new contact, the other device on ios is telling me "bad QR code". Please fix this as this an important feature on the customer perspective. This was created using a Huawei and a Blu smartphone.
UPDATE: it seems to come from the QR code reader from IOS, moving the issueAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/537First message successful even when failed2019-03-05T15:55:15ZSébastien BlinFirst message successful even when failed## Describe your environment
Please specify the following:
- Ring version: Master
- Device model: *
- Android version: *
- What build you are using: play store
## Steps to reproduce
- Can you reproduce the bug: at will
- ...## Describe your environment
Please specify the following:
- Ring version: Master
- Device model: *
- Android version: *
- What build you are using: play store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Shut down internet
2. Open a conversation
3. Send a text message
4. Send another message
- Actual result:
1. First message = "Just now" like a success
2. Second message = Ongoing then failure.
- Expected result:
1. Both should failhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/524Crash when switching to the conversation view during a call2019-03-05T15:58:53ZSébastien BlinCrash when switching to the conversation view during a call## Describe your environment
Please specify the following:
- Ring version: Latest built from sources (14.08.18)
- Device model: *
- Android version: *
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1....## Describe your environment
Please specify the following:
- Ring version: Latest built from sources (14.08.18)
- Device model: *
- Android version: *
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Call somebody
2. During the call, switch to the conversation view
3. Try to send a message
- Actual result: Crash
- Expected result: Not a crash :)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/558Crash After Finishing Manually Adding Contact ID2019-03-25T20:49:42ZvindicatorrCrash After Finishing Manually Adding Contact IDBug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20190317
- Device model: LGLS740
- Android version: 6.0.1
- What build you are using: Play Store
## Steps to reproduce...Bug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20190317
- Device model: LGLS740
- Android version: 6.0.1
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Manually type long/unique contact ID.
- Actual result:
Once the last character is typed, the app crashes.
- Expected result:
The contact is found and prompted to add.
## Additional information
The only reason I manually typed it was because the QR code no longer shows in Gnome client (bug post to come).
LOGCAT:
```
3-21 06:37:04.546 6842 7523 D VCardUtils: vcardPath not exist /data/user/0/cx.ring/files/peer_profiles/2fda03b86c4696a06af19add4961a934ed0cb18a.vcf
03-21 06:37:04.551 6842 6842 W System.err: io.reactivex.b.d: The exception was not handled due to missing onError handler in the subscribe() method call. Further reading: https://github.com/ReactiveX/RxJava/wiki/Error-Handling | The callable returned a null value
03-21 06:37:04.552 6842 6842 W System.err: at io.reactivex.d.d.g.accept(Unknown Source)
03-21 06:37:04.552 6842 6842 W System.err: at io.reactivex.d.d.g.onError(Unknown Source)
03-21 06:37:04.552 6842 6842 W System.err: at io.reactivex.d.e.a.f$a.run(Unknown Source)
03-21 06:37:04.552 6842 6842 W System.err: at io.reactivex.a.b.b$b.run(Unknown Source)
03-21 06:37:04.553 6842 6842 W System.err: at android.os.Handler.handleCallback(Handler.java:739)
03-21 06:37:04.553 6842 6842 W System.err: at android.os.Handler.dispatchMessage(Handler.java:95)
03-21 06:37:04.553 6842 6842 W System.err: at android.os.Looper.loop(Looper.java:148)
03-21 06:37:04.553 6842 6842 W System.err: at android.app.ActivityThread.main(ActivityThread.java:5461)
03-21 06:37:04.553 6842 6842 W System.err: at java.lang.reflect.Method.invoke(Native Method)
03-21 06:37:04.553 6842 6842 W System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
03-21 06:37:04.553 6842 6842 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
03-21 06:37:04.553 6842 6842 W System.err: Caused by: java.lang.NullPointerException: The callable returned a null value
03-21 06:37:04.553 6842 6842 W System.err: at io.reactivex.d.b.b.a(Unknown Source)
03-21 06:37:04.553 6842 6842 W System.err: at io.reactivex.d.e.f.i.b(Unknown Source)
03-21 06:37:04.553 6842 6842 W System.err: at io.reactivex.Single.a(Unknown Source)
03-21 06:37:04.553 6842 6842 W System.err: at io.reactivex.d.e.f.l.b(Unknown Source)
03-21 06:37:04.553 6842 6842 W System.err: at io.reactivex.Single.a(Unknown Source)
03-21 06:37:04.553 6842 6842 W System.err: at io.reactivex.d.e.f.o$a.run(Unknown Source)
03-21 06:37:04.553 6842 6842 W System.err: at io.reactivex.d.g.l.a(Unknown Source)
03-21 06:37:04.553 6842 6842 W System.err: at io.reactivex.d.g.l.call(Unknown Source)
03-21 06:37:04.553 6842 6842 W System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
03-21 06:37:04.553 6842 6842 W System.err: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)
03-21 06:37:04.553 6842 6842 W System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
03-21 06:37:04.553 6842 6842 W System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
03-21 06:37:04.553 6842 6842 W System.err: at java.lang.Thread.run(Thread.java:818)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: FATAL EXCEPTION: main
03-21 06:37:04.555 6842 6842 E AndroidRuntime: Process: cx.ring, PID: 6842
03-21 06:37:04.555 6842 6842 E AndroidRuntime: Theme: themes:{}
03-21 06:37:04.555 6842 6842 E AndroidRuntime: io.reactivex.b.d: The exception was not handled due to missing onError handler in the subscribe() method call. Further reading: https://github.com/ReactiveX/RxJava/wiki/Error-Handling | The callable returned a null value
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.d.d.g.accept(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.d.d.g.onError(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.d.e.a.f$a.run(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.a.b.b$b.run(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5461)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: Caused by: java.lang.NullPointerException: The callable returned a null value
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.d.b.b.a(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.d.e.f.i.b(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.Single.a(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.d.e.f.l.b(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.Single.a(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.d.e.f.o$a.run(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.d.g.l.a(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at io.reactivex.d.g.l.call(Unknown Source)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
03-21 06:37:04.555 6842 6842 E AndroidRuntime: at java.lang.Thread.run(Thread.java:818)
03-21 06:37:04.563 753 3264 W ActivityManager: Force finishing activity cx.ring/.client.HomeActivity
```Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/502Incoming SIP calls are dropped2019-05-03T20:02:38ZJami BotIncoming SIP calls are droppedIssue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
* Environment:
Happens with both gnome-client and the Android client.
* Reproduce steps:
1. Setup SIP account (I'm using ...Issue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
* Environment:
Happens with both gnome-client and the Android client.
* Reproduce steps:
1. Setup SIP account (I'm using a VoIP.ms account)
2. Call the SIP account
3. The call is dropped as show in the logs below (captured with the Gnome client).
* Expected result:
The client should ring and the call be answerable.
* Actual result:
Missing all incoming SIP calls.
* Log
````
13:55:08.632 sip\_endpoint.c Processing incoming message: Request msg INVITE/cseq=102 (rdata0x262a9f8)
[1516128908.632|14665|sipvoiplink.cpp :646 ] username = 179835\_sfl, server = 192.175.96.70, from = 192.175.96.70
[1516128908.632|14665|sipaccount.cpp :1726 ] Matching account id in request is a fullmatch 179835\_sfl@192.175.96.70
[1516128908.633|14665|audiorecord.cpp :89 ] Generate filename for this call 20180116-135508
[1516128908.633|14665|recordable.cpp :33 ] Set recording options:
[1516128908.633|14665|ringbufferpool.cpp:115 ] Ringbuffer created with id '4105047759992942438'
[1516128908.633|14665|call.cpp :197 ] [call:4105047759992942438] state change 0/0, cnx 0/2, code 0
[1516128908.633|14665|call.cpp :220 ] [call:4105047759992942438] emit client call state change CONNECTING, code 0
[1516128908.634|14665|audiorecord.cpp :133 ] Initialize audio record for peer : 5146299726@192.175.96.70
[1516128908.634|14665|sdp.cpp :354 ] Remote SDP Session:
v=0
o=root 849326603 849326603 IN IP4 192.175.96.70
s=voip.ms
c=IN IP4 192.175.96.70
t=0 0
m=audio 18712 RTP/AVP 0 18
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=ptime:20
a=sendrecv
[1516128908.634|14665|sdp.cpp :354 ] SDP: Local SDP Session:
v=0
o=pc-mcournoyer 3725117708 0 IN IP4 192.168.49.36
s=Ring Daemon
c=IN IP4 192.168.49.36
t=0 0
m=audio 25574 RTP/AVP 104 9 112 111 110 8 0 101
a=rtpmap:104 opus/48000/2
a=rtpmap:9 G722/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:25575 IN IP4 192.168.49.36
a=sendrecv
[1516128908.634|14665|sipcall.cpp :1238 ] [call:4105047759992942438] no ICE data in remote SDP
13:55:08.634 tsx0x248a5d8 ..Transaction created for Request msg INVITE/cseq=102 (rdata0x262a9f8)
13:55:08.634 tsx0x248a5d8 .Incoming Request msg INVITE/cseq=102 (rdata0x262a9f8) in state Null
13:55:08.634 tsx0x248a5d8 ..State changed from Null to Trying, event=RX\_MSG
13:55:08.634 dlg0x245aa68 ...Transaction tsx0x248a5d8 state changed to Trying
13:55:08.634 dlg0x245aa68 .UAS dialog created
13:55:08.634 dlg0x245aa68 .Module mod-invite added as dialog usage, data=0x2452768
13:55:08.634 dlg0x245aa68 ..Session count inc to 3 by mod-invite
13:55:08.634 inv0x245aa68 .UAS invite session created for dialog dlg0x245aa68
13:55:08.634 endpoint ..Response msg 100/INVITE/cseq=102 (tdta0x247ae70) created
13:55:08.634 dlg0x245aa68 ..Initial answer Response msg 100/INVITE/cseq=102 (tdta0x247ae70)
13:55:08.634 inv0x245aa68 ..Sending Response msg 100/INVITE/cseq=102 (tdta0x247ae70)
13:55:08.634 dlg0x245aa68 ...Sending Response msg 100/INVITE/cseq=102 (tdta0x247ae70)
13:55:08.634 tsx0x248a5d8 ...Sending Response msg 100/INVITE/cseq=102 (tdta0x247ae70) in state Trying
13:55:08.634 tsx0x248a5d8 ....State changed from Trying to Proceeding, event=TX\_MSG
13:55:08.634 dlg0x245aa68 .....Transaction tsx0x248a5d8 state changed to Proceeding
[1516128908.634|14665|sipvoiplink.cpp :821 ] [call:4105047759992942438] INVITE@0x2452768 state changed to 2 (INCOMING): cause=0, tsx@0x248a5d8 status 100 (Trying)
[1516128908.634|14665|call.cpp :197 ] [call:4105047759992942438] state change 0/0, cnx 2/1, code 0
[1516128908.634|14665|call.cpp :220 ] [call:4105047759992942438] emit client call state change INACTIVE, code 0
13:55:08.634 inv0x245aa68 ..Sending Response msg 180/INVITE/cseq=102 (tdta0x247ae70)
13:55:08.634 dlg0x245aa68 ...Sending Response msg 180/INVITE/cseq=102 (tdta0x247ae70)
13:55:08.634 tsx0x248a5d8 ...Sending Response msg 180/INVITE/cseq=102 (tdta0x247ae70) in state Proceeding
13:55:08.635 tsx0x248a5d8 ....State changed from Proceeding to Proceeding, event=TX\_MSG
13:55:08.635 dlg0x245aa68 .....Transaction tsx0x248a5d8 state changed to Proceeding
[1516128908.635|14665|sipvoiplink.cpp :821 ] [call:4105047759992942438] INVITE@0x2452768 state changed to 3 (EARLY): cause=0, tsx@0x248a5d8 status 180 (Ringing)
[1516128908.635|14665|call.cpp :197 ] [call:4105047759992942438] state change 0/0, cnx 1/3, code 0
[1516128908.635|14665|call.cpp :220 ] [call:4105047759992942438] emit client call state change INCOMING, code 0
[1516128908.635|14665|call.cpp :197 ] [call:4105047759992942438] state change 0/0, cnx 3/3, code 0
[1516128908.635|14665|call.cpp :197 ] [call:4105047759992942438] state change 0/0, cnx 3/3, code 0
13:55:08.912 sip\_endpoint.c .Request msg INVITE/cseq=102 (rdata0x262a9f8) from 192.175.96.70:5060 was dropped/unhandled by any modules
13:55:08.912 tsx0x248a5d8 State changed from Proceeding to Terminated, event=TRANSPORT\_ERROR
13:55:08.912 dlg0x245aa68 Transaction tsx0x248a5d8 state changed to Terminated
[1516128908.912|14665|sipvoiplink.cpp :821 ] [call:4105047759992942438] INVITE@0x2452768 state changed to 6 (DISCONNCTD): cause=503, tsx@0x248a5d8 status 503 (Service Unavailable)
[1516128908.912|14665|call.cpp :197 ] [call:4105047759992942438] state change 0/4, cnx 3/0, code 503
[1516128908.912|14665|call.cpp :220 ] [call:4105047759992942438] emit client call state change FAILURE, code 503
[1516128908.912|14665|manager.cpp :2071 ] [call:4105047759992942438] Failed
[1516128908.912|14665|manager.cpp :1663 ] [call:4105047759992942438] Remove local audio
[1516128908.912|14665|sipcall.cpp :715 ] [call:4105047759992942438] removeCall()
[1516128908.912|14665|call\_factory.cpp :39 ] Removing call 4105047759992942438
[1516128908.912|14665|call\_factory.cpp :43 ] Remaining 0 SIP call(s)
[1516128908.912|14665|call.cpp :197 ] [call:4105047759992942438] state change 4/5, cnx 0/0, code 0
[1516128908.912|14665|call.cpp :220 ] [call:4105047759992942438] emit client call state change OVER, code 0
[1516128908.912|14665|audiorecord.cpp :220 ] Stop recording /home/mcournoyer/20180116-135508-5146299726\_192.175.96.70-ring.wav
[1516128908.912|14665|audiorecord.cpp :220 ] Stop recording /home/mcournoyer/20180116-135508-5146299726\_192.175.96.70-ring.wav
13:55:08.912 dlg0x245aa68 ..Session count dec to 1 by mod-invite
13:55:08.912 dlg0x245aa68 .Dialog destroyed
13:55:08.912 tsx0x248a5d8 Timeout timer event
13:55:08.912 tsx0x248a5d8 .State changed from Terminated to Destroyed, event=TIMER
13:55:08.912 tdta0x247ae70 ..Destroying txdata Response msg 180/INVITE/cseq=102 (tdta0x247ae70)
13:55:08.912 tsx0x248a5d8 Transaction destroyed!
[1516128908.912|14665|manager.cpp :2830 ] Call is NULL
[1516128908.913|14665|manager.cpp :2830 ] Call is NULL
[1516128908.913|14665|manager.cpp :2830 ] Call is NULL
[1516128908.939|14665|manager.cpp :2830 ] Call is NULL
[1516128908.939|14665|manager.cpp :2830 ] Call is NULL
[1516128908.940|14665|manager.cpp :2830 ] Call is NULL
[1516128908.940|14665|manager.cpp :2830 ] Call is NULL
[1516128908.940|14665|manager.cpp :2830 ] Call is NULL
[1516128908.940|14665|manager.cpp :2830 ] Call is NULL
[1516128908.941|14665|manager.cpp :2830 ] Call is NULL
````https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/474Does not work with 4g/3g data enabled2019-05-06T00:04:45ZJami BotDoes not work with 4g/3g data enabledIssue generated from Tuleap's migration script.
**Originally submitted by: Pierre (pierre__)**
* Environment:
Test between Android 6.0.1 with Ring version 20180201 (Nexus5X)
and Android 7.0 with Ring version 20171215 (Huawei Tab) ...Issue generated from Tuleap's migration script.
**Originally submitted by: Pierre (pierre__)**
* Environment:
Test between Android 6.0.1 with Ring version 20180201 (Nexus5X)
and Android 7.0 with Ring version 20171215 (Huawei Tab)
Using 2 different ring id
* Reproduce steps:
- On Nexus5 Set to use mobile data
- on Huawei wifi (this is the only choice because no gsm on this device )
- Send message from Hu to Nexus user
- It's received after a long delay (seeral minutes)
- Send message from Nexus to hu
- It's not received at all
But all messages are received correctly when both use wifi (on the same network at least)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/516Google analytics is enabled2019-05-10T14:09:12ZPierre DucheminGoogle analytics is enabled- Ring version: 20180712
- Device model: Moto G5
- Android version: 8
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Actual result: Google analytics is enabled (FCM defau...- Ring version: 20180712
- Device model: Moto G5
- Android version: 8
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Actual result: Google analytics is enabled (FCM default)
- Expected result: GA is disabled, since we don´t need it
## Additional information
https://firebase.google.com/support/guides/disable-analytics#permanently_deactivate_collectionhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/262call not received when device locked after a long time2019-05-24T19:01:08ZJami Botcall not received when device locked after a long timeIssue generated from Tuleap's migration script.
**Originally submitted by: Romain B. (rbertozzi)**
<p>If the device is locked since a long time, when someone calls, the device does not ring.</p>
<p>If the device has just been locke...Issue generated from Tuleap's migration script.
**Originally submitted by: Romain B. (rbertozzi)**
<p>If the device is locked since a long time, when someone calls, the device does not ring.</p>
<p>If the device has just been locked, then it is ringing.<br />
</p>Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/324Modifying some account settings freezes the Android app2019-05-24T19:08:31ZJami BotModifying some account settings freezes the Android appIssue generated from Tuleap's migration script.
**Originally submitted by: Subiol Git (subiolgit)**
I've installed Ring in my Android phone with Cyanogenmod 13. When I try to deactivate Upnp option the app freezes and it has to be kille...Issue generated from Tuleap's migration script.
**Originally submitted by: Subiol Git (subiolgit)**
I've installed Ring in my Android phone with Cyanogenmod 13. When I try to deactivate Upnp option the app freezes and it has to be killed and restarted (Upnp still on). Stun configuration works but when I try to activate TURN the app freezes and again has to be killed and restarted (TURN still off).https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/386Android or iOS: no contact established2019-05-24T19:08:58ZJami BotAndroid or iOS: no contact establishedIssue generated from Tuleap's migration script.
**Originally submitted by: Yngve Levinsen (yngve)**
I have one account on my Android (or actually both accounts, but only one active), and one on my Mac. I try to send messages and call th...Issue generated from Tuleap's migration script.
**Originally submitted by: Yngve Levinsen (yngve)**
I have one account on my Android (or actually both accounts, but only one active), and one on my Mac. I try to send messages and call the two accounts, but nothing happens.
Unfortunately I do not have a third device available which could rule out which of the two are at fault.
I also do not know which severity to select here, as this could be specific to my setup. I set it to minimal for now.
My Mac is running OSX 10.11.6, and my Android is an OnePlus 3 (so technically OxygenOS I suppose), running Android 6.0.1 (OxygenOS 3.2.8). I suppose there is a slightly higher chance that this is an issue related to OxygenOS (more vanilla), so I select Android as the platform.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/408Vcard photo is not displayed2019-05-24T19:10:27ZJami BotVcard photo is not displayedIssue generated from Tuleap's migration script.
**Originally submitted by: Hadrien De Sousa (hdesousa)**
Vcard photo is not displayed when a call is place.
Profile name is saved in the vcard file but the photo is corrupt.Issue generated from Tuleap's migration script.
**Originally submitted by: Hadrien De Sousa (hdesousa)**
Vcard photo is not displayed when a call is place.
Profile name is saved in the vcard file but the photo is corrupt.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/577When "Enable accelerated encoding" is disabled major video quality loss2019-05-28T13:52:06ZMohamed FenjiroWhen "Enable accelerated encoding" is disabled major video quality lossWhen disabling Accelerated Encoding, the user is left with a major video quality loss and green vertical bars. (ON ANDROID)
The new video encoding is great but it shouldn't be at the cost of loosing basic video encoding when disabling i...When disabling Accelerated Encoding, the user is left with a major video quality loss and green vertical bars. (ON ANDROID)
The new video encoding is great but it shouldn't be at the cost of loosing basic video encoding when disabling it.
![Screenshot_from_2019-05-23_09-50-44](/uploads/24b924d828d6c8411c6eec2cc86c4e2e/Screenshot_from_2019-05-23_09-50-44.png)