jami-client-android issueshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues2020-10-02T15:34:20Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/607Video preview is stretched after opening chat and returning to call2020-10-02T15:34:20ZFrançois Naggar-TremblayVideo preview is stretched after opening chat and returning to callOnly in landscape orientation.Only in landscape orientation.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/750Ringtone during call on AndroidTV2023-06-01T17:12:35ZPierre DucheminRingtone during call on AndroidTV- Ring version: 2020069-01
- Device model: Nvidia Shield
- Android version: 9
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
0. Enable auto-answer
...- Ring version: 2020069-01
- Device model: Nvidia Shield
- Android version: 9
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
0. Enable auto-answer
1. Let the device stay idle (looks like it helps reproducing)
2. Using a Gnome or Android client with the same daemon version, call the Android TV
3. Video start, the ringtone start. Now we would expect the ringtone to quickly stop (or even never start), but it's continuing until we hang up.
## Additional information
This log looks suspicious:
```
2020-06-17 15:06:54.546 6869-8621/? D/CallService: incoming call: 9b0e16b62be79cde, 8472596603105053, Pierre <...@ring.dht>
2020-06-17 15:06:54.546 6869-8621/? W/CallService: Call already existed ! 8472596603105053 Pierre <...@ring.dht>
2020-06-17 15:06:54.546 6869-8621/? D/ConversationFacade: onCallStateChange Thread id: 9223
2020-06-17 15:06:54.546 6869-8621/? D/HardwareServiceImpl: updateAudioState: Call state updated to CURRENT Call is incoming: false Call is video: true
```https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/778TV: call hanging up after 2 seconds2023-06-01T17:34:45ZPierre DucheminTV: call hanging up after 2 seconds- Jami version: 20200722-01
- Device model: Mecool KM9Pro Deluxe
- Android version: 10
- What build you are using: client: 175a9b425068d4a1d18c58a29e8233a38b9353f0 + daemon: 4357af81409d209f0208f9b0b59059cd244d7b54
## Steps to r...- Jami version: 20200722-01
- Device model: Mecool KM9Pro Deluxe
- Android version: 10
- What build you are using: client: 175a9b425068d4a1d18c58a29e8233a38b9353f0 + daemon: 4357af81409d209f0208f9b0b59059cd244d7b54
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
0. Enable auto-answer on Android TV device
1. kill/restart jami-gnome or jami android
2. call Android TV device from jami-gnome (2020-07-24) or jami android (20200715-01)
- Actual result: after exactly 2 seconds, the Android TV device hang up.
- Expected result: the call starts normally
## Additional information
- Everything works fine if the Android TV device calls jami-gnome or jami android
- race condition?
- Call log:
[callhangingup.log](/uploads/e72e1c791109a4d7cf339c1d66690925/callhangingup.log)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/782TV: bad preview ratio2023-06-01T17:33:43ZPierre DucheminTV: bad preview ratio- Jami version: 20200810-01
- Device model: Mecool KM9Pro Deluxe
- Android version: 10
- What build you are using: c1158499d97b9f24843617a44402c148e6bff08e + daemon: 27668c3a564c22e8a1971d7f9467f0a58b615990
## Steps to reproduce...- Jami version: 20200810-01
- Device model: Mecool KM9Pro Deluxe
- Android version: 10
- What build you are using: c1158499d97b9f24843617a44402c148e6bff08e + daemon: 27668c3a564c22e8a1971d7f9467f0a58b615990
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. call Android TV device from jami-gnome (2020-08-10)
- Actual result: in some cases, the preview is malformed: bad orientation and inverted width and height. After a while the preview freeze.
![device-2020-08-13-164350](/uploads/264312e69249a07f37c90eb408690f8a/device-2020-08-13-164350.png)
- Expected result: the preview is showing as usual.
![device-2020-08-13-165925](/uploads/b231ca1a8a11418e258343123f1d2069/device-2020-08-13-165925.png)
## Additional information
[badpreviewratiotv.log](/uploads/09ece7be49e9613f4cba00028f755c2b/badpreviewratiotv.log)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/803Some images are not displayed2020-09-18T14:51:34ZCyrille BéraudSome images are not displayedsend a png file to a Jami/android - the image is received but not diplayedsend a png file to a Jami/android - the image is received but not diplayedAdrien BéraudPierre DucheminAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/916samsung galaxy j3 prime: Video and sound become choppy and call drops2022-01-03T02:01:58ZMaxim Cournoyersamsung galaxy j3 prime: Video and sound become choppy and call dropsBug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20210315-01
- Device model: Samsung Galaxy J3 (SM-J327W)
- Android version: 8.1.0
- On the Samsung Galaxy J3: Play Stor...Bug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20210315-01
- Device model: Samsung Galaxy J3 (SM-J327W)
- Android version: 8.1.0
- On the Samsung Galaxy J3: Play Store; on the other device: Tried with Play store (20210315-01) or jami-gnome built from the latest sources on GNU/Linux
## Steps to reproduce
- Can you reproduce the bug: With one of my contacts though which is using a SM-J327W device, it always occur on her side (their Jami app crashes after a while). I couldn't reproduce using a SM-J320W8 (a different, but close model).
- Steps:
1. Call Jami on a Samsung Galaxy J3 SM-J327W
1. The call originally proceeds normally, with good video and audio and a decent framerate (~15 fps on both ends).
1. After 2-5 minutes of call, the video and audio sent from the Galaxy J3 device becomes choppy, with the framerate dropping to near zero (0.09 fps) and eventually the call dropping.
- Actual result: The call drops after a while.
- Expected result: The video and audio should remain fluid, and the call should not drop even after a prolonged period of time.
## Additional information
The phone specs are available from https://www.phonearena.com/phones/Samsung-Galaxy-J3-Prime_id10506. It has the following processor and GPU:
- CPU: Quad-core, 1400 MHz, ARM Cortex-A53, 64-bit, 28 nm
- GPU: Adreno 308
- RAM: 1.5 GiBhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999Incoming call is displayed to user after it has immediately failed (for a few...2023-10-29T19:53:06ZElysIncoming call is displayed to user after it has immediately failed (for a few times) / or you hear the call ringing without viewing any notificationUpdate: You can get the call without any noticiation but you'll hear the ringing forever: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_45879
Update: https://git.jami.net/savoirfairelinux/jami-client-androi...Update: You can get the call without any noticiation but you'll hear the ringing forever: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_45879
Update: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_44908
Always reproduced!
---
using newest version of Jami Android 20221107-01 and Jami 202211101600 Windows 10
I was able to reproduce again (sameuseraccount (Android) -\> sameuseraccount (Windows 10)).
Reproduced if two devices use **different networks AND** if two devices use the **same WLAN**
I think if you make a call useraccount 1 -\> useraccount 2 even if the green dot of your own contact in the contact list on Windows 10 is not visible the Android version will still "remember" the call and as soon as the green dot is visible (on Windows 10) the call will succeed.
EDIT: **Maybe you have to make a call successfully before (Android -\> Windows 10) and then JUST exit Windows 10 to reproduce.**
EDIT: I think I now know why and how it fails?
1. Make a call before you can view the green dot of your contact (?)
2. Make a call shortly before you can view the green dot of your contact (?) / or as soon as you would see the green dot
3. The other peer should receive the call after ten seconds (but you'll never know)?
Sometimes you have to exit Jami (just) on the smartphone a couple of times (over 20 times?) to reproduce?
Just reproduced a couple of times again:
**DISABLE "run in background"**
Steps to reproduce (You actually just have to exit ONE device; NOT BOTH, but I think you have to enable TURN, even if you use the same network) (See: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_38603)
---
EDIT: I was also able to reproduce **Android -\> Windows 10** (**sameuseraccount -\> sameuseraccount**); different network
(The Windows 10 user and the Android user have themselves already in the contact list)
Steps to reproduce:
1. Android: Open Jami and keep Jami running (more than 30 seconds)
2. Now the Windows 10 user opens Jami
3. As soon as the Windows 10 user opens Jami, (BEFORE the green dot of the Android user is visible on Windows 10) the Android user makes one call (Android -\> Windows 10), quickly a second call and maybe you also need a third call - they will all immediately fail
4. Now wait for a few seconds or even longer (nobody does anything; meanwhile the Windows 10 views the green dot of the Android user)
5. The Windows 10 user will receive a call (but the Android user will never notice)
I think you can't reproduce if the green dot is not gone- for example if just the Windows 10 user exits Jami but as soon as he opens Jami again the green dot is already there? In that case I wasn't able to reproduce I think ...
---
**Android \<-\> Android**
1. Open Jami and quickly make a first call (maybe even before I can see the green dot ?? (Can't tell because of issue https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/994) - it will immediately fail
2. Now after a few seconds (or even just one second) make the second call - it will immediately fail
3. Now wait
4. Now the Android tablet will receive a call after 10 seconds or more (but the smartphone user will never be able to view the call)
I had a few possibilities:
- Sometimes you don't reproduce?
- Sometimes the other device just gets one call (2 calls failed)
- Sometimes the other device gets both two calls (2 calls failed)
- Sometimes you need to make a third call (after a few seconds) and the other device will receive the third call AND the second call
---
Option B:
Another option how to reproduce this issue:
EDIT: I think I was even able to reproduce even if you make a call after you can view the green dot of the Android contact but BEFORE the green dot of your own account refreshes again.
1. Just open Jami on Android (never exit; keep Jami running at least 30 seconds; Maybe you've already closed Jami on Windows 10)
2. Now the Windows 10 user opens Jami
3. Make a call Android -\> Windows 10 (before the Windows 10 user can view the green dot of the Android contact): It will immediately fail
4. Make a second call Android -\> Windows 10 (before the Windows 10 user can view the green dot of the Android contact): It will try to connect; However (just) the Android user now stops the call ("connecting" \[although this time it might would work\])
5. Now the Android user makes another call - it will immediately fail (again)
6. Maybe the Android user makes again another call - immediately fail (Sometimes it it will show "connecting" again and the call might successfully work)
7. Maybe all peers need to wait a few seconds
8. Now just the Windows 10 user will receive a call - the Android user will never noticehttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/988Push notification will not show at the beginning when the device is restarted2021-08-24T07:19:05ZMing Rui ZhangPush notification will not show at the beginning when the device is restartedWhen the device is restarted, there will be for sure no Jami running in the background.
At this time, when a push notification is received, Jami will wake up from the debugging log and
messages, calls will be received and handled correc...When the device is restarted, there will be for sure no Jami running in the background.
At this time, when a push notification is received, Jami will wake up from the debugging log and
messages, calls will be received and handled correctly.
But, there will be no system notification being showed unless the contact keeps sending or calling (until ```bootstrapDaemon``` is called again).
Current speculations:
1. When the client is started normally, the ```ConversationFacade``` instance will be created which is in charge of
notifications' build.
```
2021-08-23 12:22:52.434 17572-17572/cx.ring D/DERP: init conv facade
java.lang.RuntimeException
at net.jami.services.ConversationFacade.<init>(ConversationFacade.kt:631)
at cx.ring.dependencyinjection.ServiceInjectionModule.provideConversationFacade(ServiceInjectionModule.kt:140)
at cx.ring.dependencyinjection.ServiceInjectionModule_ProvideConversationFacadeFactory.provideConversationFacade(ServiceInjectionModule_ProvideConversationFacadeFactory.java:78)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC.conversationFacade(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:285)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC.access$3800(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:200)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC$SwitchingProvider.get(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:1569)
at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC$ActivityCImpl.injectHomeActivity2(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:1339)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC$ActivityCImpl.injectHomeActivity(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:1242)
at cx.ring.client.Hilt_HomeActivity.inject(Hilt_HomeActivity.java:67)
at cx.ring.client.Hilt_HomeActivity$1.onContextAvailable(Hilt_HomeActivity.java:38)
at androidx.activity.contextaware.ContextAwareHelper.dispatchOnContextAvailable(ContextAwareHelper.java:99)
at androidx.activity.ComponentActivity.onCreate(ComponentActivity.java:322)
at androidx.fragment.app.FragmentActivity.onCreate(FragmentActivity.java:273)
at cx.ring.client.HomeActivity.onCreate(HomeActivity.kt:132)
at android.app.Activity.performCreate(Activity.java:7183)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1220)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2910)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3032)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6944)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
```
2. When the application wakes up by push notification, no instance of ```ConversationFacade``` will be created. Therefore,
there will be no subscription to create notifications on the representation level.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1023Do not reset account informations when linking it from another device2023-06-01T13:15:12ZMaxime CalletDo not reset account informations when linking it from another deviceThis sequence is not useful, user will retrieve his data, thus do not need to reset informations
![Screenshot_20211026_144223_cx.ring_edit_97742123916855](/uploads/5753a464d1bb903bbd1182af26cd27cd/Screenshot_20211026_144223_cx.ring_edit...This sequence is not useful, user will retrieve his data, thus do not need to reset informations
![Screenshot_20211026_144223_cx.ring_edit_97742123916855](/uploads/5753a464d1bb903bbd1182af26cd27cd/Screenshot_20211026_144223_cx.ring_edit_97742123916855.jpg)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1030Conversation: scrolling block sent file2022-03-02T21:48:25ZMaxime CalletConversation: scrolling block sent file## Details:
- Ring version: `any`
- Device model: `Samsung T2`
- Android version: `7.0`
- What build you are using: `jami.net | F-droid | Play Store`
## Steps to reproduce:
- Can you reproduce the bug: `at will`
- Steps:
1. I...## Details:
- Ring version: `any`
- Device model: `Samsung T2`
- Android version: `7.0`
- What build you are using: `jami.net | F-droid | Play Store`
## Steps to reproduce:
- Can you reproduce the bug: `at will`
- Steps:
1. In a conversation with sent files
2. Scroll down until you reach a video you sent
3. Then scroll up/down above and below the file preview
4. The preview is now white and can't be accessed
## Actual result:
![Screenshot_20211109-173024](/uploads/1bad59c5b8d42b2fe75e27f9abc538a5/Screenshot_20211109-173024.png)
## Expected result:
The preview should be visible and the file accessible
## Additional informationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1050Question about improvements2022-01-04T09:36:52ZSkretch1974Question about improvementsHello. In the process of testing the latest version of Android, we found some problems with the Xiaomi Poco F3 phone.
## Bug
* When the switch is set to automatically download the program when the phone is restarted, the program start...Hello. In the process of testing the latest version of Android, we found some problems with the Xiaomi Poco F3 phone.
## Bug
* When the switch is set to automatically download the program when the phone is restarted, the program starts, but it is impossible to get through or receive a message until you open the window of the program itself.
This is not always convenient, especially when there is a need to restart the phone, and the user may forget to enter the program and minimize it to the background.
## Features request:
1) Add the ability to activate the Ptt function and automatically play voice messages when they are received
> it is necessary for this function to provide a more convenient button on the smartphone screen.
>
> Ptt will allow operation on low-speed Internet networks, as well as through TOR (Orbot) or similar networks
2) you also need to add low-speed voice codecs (Melpe1200 (2400), Codec2, (Silk))
3) make an automatic Jitter buffer for voice communication via TOR ( Orbot), this will significantly increase the privacy of the application as a whole.
Thank you.
> Hello. In the process of testing the latest version of Android, we found some problems with the Xiaomi Poco F3 phone, when the switch is set to automatically download the program when the phone is restarted, the program starts, but it is impossible to get through or receive a message until you open the window of the program itself. This is not always convenient, especially when there is a need to restart the phone, and the user may forget to enter the program and minimize it to the background. Also, if necessary, add the ability to activate the Ptt function and automatically play voice messages when they are received; it is also necessary for this function to provide a more convenient button on the smartphone screen. Ptt will allow operation on low-speed Internet networks, as well as through TOR (Orbot) or similar networks, you also need to add low-speed voice codecs (Melpe1200 (2400), Codec2, (Silk)), and make an automatic Jitter buffer for voice communication via TOR ( Orbot), this will significantly increase the privacy of the application as a whole. Thank you.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1051buttons remain in pressed state although they are no longer used2023-06-01T16:59:31ZElysbuttons remain in pressed state although they are no longer usedusing Jami Android (Version, 20211210-01 beta)
For example: If you use the system Back button to exit the dialpad the button is displayed as still pressed - Although there is no dialpad anymore.
Anyway I would like to suggest that the ...using Jami Android (Version, 20211210-01 beta)
For example: If you use the system Back button to exit the dialpad the button is displayed as still pressed - Although there is no dialpad anymore.
Anyway I would like to suggest that the developers (@mcallet and @aberaud ) try out the following things:
1)
> You receive a call; Now you are using your front camera; Now you select the “Screen Sharing” option; You tap the overview button; You tap the home button; Then you open another app;
Now change the screen mode from landscape to portrait mode or from portrait to landscape mode.
> Now open another app
> Return to Jami: (using the overview button)
2)
Tap any button
Now change the screen mode from landscape to portrait mode or from portrait to landscape mode.
Tap another button
Now change (again) the screen mode from landscape to portrait mode or from portrait to landscape mode.
Tap another button
3)
Tap any button
Tap the overview button; Then tap the home button
AND/or
use the system Back button
Tap another button
(and change the screen mode from landscape to portrait mode or from portrait to landscape mode randomly)
-------------
You'll find many bugs where the buttons remain in pressed state or are in wrong position. (Please also randomize the order of the steps mentioned above)
It would be very complicated if I list every issue I had so please try out yourself.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1217Switch Between Portrait and Landscape Orientation does not work if you share ...2024-01-10T16:18:31ZElysSwitch Between Portrait and Landscape Orientation does not work if you share your screen immediately; 180° does generally not workSteps to reproduce:
2 devices (Android and Android)
or
Android and Windows 10
Android smartphone:
1)make a video call
you can see the your face
2)Rotate the smartphone
The other person (B) can see Person A in landscape (horizontal) m...Steps to reproduce:
2 devices (Android and Android)
or
Android and Windows 10
Android smartphone:
1)make a video call
you can see the your face
2)Rotate the smartphone
The other person (B) can see Person A in landscape (horizontal) mode (other device)
3)Now if you - Person A - start to share your screen Person B can see the screen in landscape (horizontal) mode [**Windows 10**: Here **crash** https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/536]
**BUT**
If you make a video call and share your screen immediately and rotate the screen, Person B only sees the screen horizontal BUT in portrait mode! [same issue using Jami,Windows 10]
Example:
![ScreenshotNOautorotate](/uploads/e949197ad9e27adc1837719f0f5efd55/ScreenshotNOautorotate.jpg)
Device B can have **Windows AND Android OS**
Auto rotate works if I start call horizontally!https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1067Screensharing: issue while coming back from pip, stack lost, preview bug2024-01-10T16:15:49ZMaxime CalletScreensharing: issue while coming back from pip, stack lost, preview bug- Ring version: 326
- Device model: Huawei p30
- Android version: Any
- What build you are using: F-droid | Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Create a call
2. Start scree...- Ring version: 326
- Device model: Huawei p30
- Android version: Any
- What build you are using: F-droid | Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Create a call
2. Start screensharing
3. click on home to go in PiP mode
4. expand the PiP to go back to the call view
5. Stop screensharing
- Actual result: the preview is not showing the camera stream, but the receiver gets the video stream
- Expected result: the preview should be shown correctly
## Additional informationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1076Pixelated video call (especially if hardware accelerated encoding is disabled)2023-10-26T13:12:39ZElysPixelated video call (especially if hardware accelerated encoding is disabled)Mate 20 Pro (EMUI 11)
Jami: Version 20220121-01
Although the internet connection of the smartphone is fast (download speed 93 Mbit/s, upload speed 14 Mbit/s) I often get a pixelated video (of the user of the smartphone)
Especially if ...Mate 20 Pro (EMUI 11)
Jami: Version 20220121-01
Although the internet connection of the smartphone is fast (download speed 93 Mbit/s, upload speed 14 Mbit/s) I often get a pixelated video (of the user of the smartphone)
Especially if I move quickly and especially if I use the phone in landscape mode. But sometimes you get a pixelated video after a few seconds and suddenly you have no more pixelated video for the next few seconds.
However- using Jami Windows 10 - although the upload speed is just 1 Mbit/s - even if I quickly move the webcam (HD, 30 fps) I don't get any pixelated video (of the user of the pc).https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1079Cancel File Transfer not working2022-02-10T22:55:55ZtrymeoutCancel File Transfer not workingWhen I cancel a file transfer midway though the file being downloaded to my device, the cancel button does nothing and the file keeps downloading.When I cancel a file transfer midway though the file being downloaded to my device, the cancel button does nothing and the file keeps downloading.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1087Cannot delete a downloaded file2024-02-14T16:01:30ZAmirhossein NaghshzanCannot delete a downloaded file
## Steps to reproduce
- Can you reproduce the bug: [at will]
- Steps:
1. Receive a media or a file from another client, either video, audio, image, or file.
2. Long press on the message.
3. Select Delete.
- Actual result: Nothing...
## Steps to reproduce
- Can you reproduce the bug: [at will]
- Steps:
1. Receive a media or a file from another client, either video, audio, image, or file.
2. Long press on the message.
3. Select Delete.
- Actual result: Nothing happens.
- Expected result: The message should be removed.
## Additional informationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1091Jami starts ringing but no way to accept call if user's conversation is open2022-04-01T18:48:10ZAnjandev MomiJami starts ringing but no way to accept call if user's conversation is open![1bc96c58_screen-20220324-151737](/uploads/aab1bb4c9c119c706ccd341c10f104af/1bc96c58_screen-20220324-151737.mp4)
User must go back and re-enter the conversation with the user that's calling them to accept the call![1bc96c58_screen-20220324-151737](/uploads/aab1bb4c9c119c706ccd341c10f104af/1bc96c58_screen-20220324-151737.mp4)
User must go back and re-enter the conversation with the user that's calling them to accept the callAdrien BéraudAmirhossein NaghshzanAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1094High mobile data consumption2023-07-08T07:41:39ZBruno KleinertHigh mobile data consumptionHi,
I experienced high and excessive mobile data consumption on a Samsung and a Huawei device.
Jami was used on both devices for about 3 hours. Less than 15 text messages were exchanged between both devices. On both devices the 'share ...Hi,
I experienced high and excessive mobile data consumption on a Samsung and a Huawei device.
Jami was used on both devices for about 3 hours. Less than 15 text messages were exchanged between both devices. On both devices the 'share location for 1 hour' function was enabled twice.
The Samsung device moved often between outside locations with good mobile network reception and underground locations with poor mobile network reception (I used the metro a few times). The Huawei device remained outside with permanent good mobile network reception.
On both devices, Jami was used without WiFi for the first time.
Samsung:
* Galaxy A52 with Android 12
* Jami 'Taranis 20220311-01', installed via F-Droid
* DHT Proxy function enabled
Huawei:
* Jami, version unknown, installed most likely via Google Play Store
* DHT Proxy function setting unknown
After 3 hours, the devices showed the following data consumptions:
* 340MB on the Samsung device
* 9,5GB (It's indeed Gigabytes) on the Huawei device
Can I provide any other information from the Samsung device that helps to track this issue down?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1104Jami doesn't show any notification for incoming calls on TV2023-08-15T18:40:12ZRichard BranchesJami doesn't show any notification for incoming calls on TVWhen a call or videocall is incoming, I only hear the ringtone but no notification appears and when I open the app, the call gets disconnected immediately.
This happens on Android 11 whether on the Android TV UI or the Google TV UI.When a call or videocall is incoming, I only hear the ringtone but no notification appears and when I open the app, the call gets disconnected immediately.
This happens on Android 11 whether on the Android TV UI or the Google TV UI.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1119using VP8 won't show the video of the Android caller if the Android user enab...2024-03-08T13:12:46ZElysusing VP8 won't show the video of the Android caller if the Android user enabled hardware accelerationusing newest beta version of Jami
Make a call Windows 10 -> Android
If you just choose the VP8 video codec during a call:
* The video of the webcamera of the Windows 10 user can be viewed by the Android user
* The Android user will vie...using newest beta version of Jami
Make a call Windows 10 -> Android
If you just choose the VP8 video codec during a call:
* The video of the webcamera of the Windows 10 user can be viewed by the Android user
* The Android user will view his own video preview
* The Windows 10 user will view his own video preview
BUT:
The Windows 10 user won't see the video of the Android user (or sometimes just a black & white video that will freeze (just the Windows 10 user will see the frozen video of the Android user) if the **Android user enables hardware acceleration** and **just uses VP8**
No issues if just the Windows 10 user enables or disables hardware acceleration
If the developers can reproduce, can you also try to reproduce this issue in conferences (and/or Multistream)?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/11251080p, 1440p and 4K video issues on TV2023-10-18T20:26:41ZRichard Branches1080p, 1440p and 4K video issues on TV## Describe your environment:
Jami for Android TV didn't support the 1440p Quad HD quality option until it was added as per the https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1103 request.
However, testing that new ...## Describe your environment:
Jami for Android TV didn't support the 1440p Quad HD quality option until it was added as per the https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1103 request.
However, testing that new resolution doesn't seem to work, the preview window at the bottom right appears white and the video stream in the other party appears black.
I tested the other quality options (480p, 720p, 1080p) and they worked correctly, it's important to clarify that in order to make them work, I had to test them one by one by exiting the app, force stop it and then reopen it.
Please specify the following:
- Jami version: 20220906-01
- Device model: Mecool KM2 Plus.
- Android version: The device has Android 11, I'm not sure if this works correctly on previous Android versions.
- What build you are using: Play Store.
## Steps to reproduce
- Can you reproduce the bug: At will.
- Steps:
1. Select the desired quality option by going to settings -> video resolution -> 1440p Quad HD.
2. Exit the app.
3. Go to android settings, look for the app and force stop it.
4. Go back to Jami.
5. Make a video call.
- Actual result: The bottom right appears white and the video stream in the other party appears black.
- Expected result: The bottom right should appears show a video preview and the video stream in the other party should output the video correctly.
## Additional information:
The preview camera that appears at the bottom of the UI is constant and fluid but I assume it's in the 720p quality.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1129Issue if you add a participant to a video call2024-02-15T09:09:34ZElysIssue if you add a participant to a video callAndroid: 20220906-01
Windows 10: 202209300958
Steps to reproduce:
Android: You have only one own account ("myusername1") with contacts like "myusername2" and "myusername3"<br>
Windows 10: You have multiple own accounts ("myusername2")...Android: 20220906-01
Windows 10: 202209300958
Steps to reproduce:
Android: You have only one own account ("myusername1") with contacts like "myusername2" and "myusername3"<br>
Windows 10: You have multiple own accounts ("myusername2") but always the same contact ("myusername3")
1. Make a video call Android ("myusername1") -> Windows 10 ("myusername2")
2. Android: You can view the video of the Windows 10 user
3. Android: Add participant (Windows 10 contact: "myusername3")
4. Android: All videos are gone; you just view your own video preview
5. Windows 10: You can actually see three videos but all are black
Windows 10: If you want to view most of the videos (again) you have to select another own (second) account and return to your other (first) account to view the video again.
Sometimes you will be able to view the video on Android again.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1151File transfer (Windows 10 -> Android): Jami (Android) does not show any downl...2023-07-30T19:40:31ZElysFile transfer (Windows 10 -> Android): Jami (Android) does not show any download progressusing newest (beta) version of Jami (20221207-01); different networks; (sameuseraccount (Windows 10) -> sameuseraccount (Android))
send a file (any size) Windows 10 -> Android
Jami (Android) does not show any download progress - you al...using newest (beta) version of Jami (20221207-01); different networks; (sameuseraccount (Windows 10) -> sameuseraccount (Android))
send a file (any size) Windows 10 -> Android
Jami (Android) does not show any download progress - you always have a size of 0 / 14,34 MB (running) and suddenly you have a file time and size like for example 11:05 - 14,34 MB.
another issue?
If you return to the contact list you always get a message like "2 seconds ago" (even after 10 minutes) while another file is transferred
no issues Android -> Windows 10 ?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1159Swarm: Create a swarm without members (only current account) is not correctly...2023-01-25T21:29:33ZSébastien BlinSwarm: Create a swarm without members (only current account) is not correctly shown# Scenario
+ On a Desktop device, start a swarm (e.g. "Notes to self") without other members
+ Android got sync
# Current result
+ No title/members (even us) is shown
# Expected
+ Members should be 1 (admin, me)
+ Title should be "N...# Scenario
+ On a Desktop device, start a swarm (e.g. "Notes to self") without other members
+ Android got sync
# Current result
+ No title/members (even us) is shown
# Expected
+ Members should be 1 (admin, me)
+ Title should be "Notes to self"https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1201Douple tap on buttons blocks the app2023-07-12T15:53:02ZPierre NicolasDouple tap on buttons blocks the app## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit e9c89e96c91fc3ce7afdccc3b4ff861b73ffcaca
## Steps to reproduce
- Can you reproduce ...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit e9c89e96c91fc3ce7afdccc3b4ff861b73ffcaca
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Add account
2. Connect from backup
3. Select the account you want to add
4. Double tap on connect from backup
- Actual result: The app load forever (can be restarted).
- Expected result: It should not be possible to double tap.
## Additional information
![device-2023-03-27-115924](/uploads/ccf11737405245ef56b6efda8f070593/device-2023-03-27-115924.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1206Impossible to mark conversation as read2024-02-08T15:10:01ZPierre NicolasImpossible to mark conversation as read## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce ...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce the bug: at will (but only with these accounts)
- Steps:
1. Open an unread conversation
2. The conversation is mark as read
3. Close the app and reopen
- Actual result: The same conversation reappears unread
## Additional information
![output](/uploads/e74b089dd0e4b1359d371ac1978607c3/output.mp4)Alexander Lussier-CullenAlexander Lussier-Cullenhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1208New SIP conversation only appears at restart2023-07-12T15:53:35ZPierre NicolasNew SIP conversation only appears at restart## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce ...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open a SIP account
2. Search for a new contact and start talking to him
- Actual result: The conversation is created but your new contact doesn't appears in contact list. Furthermore, it appears at restart.
## Additional information
![output](/uploads/f7a1c29ebc9648bf453acd95c7ecbbe6/output.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1212Call: Peer's camera preview is disabled for few seconds when changing your ca...2023-07-20T16:04:02ZPierre NicolasCall: Peer's camera preview is disabled for few seconds when changing your camera side## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce ...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start a call (with camera).
2. Change your camera's side.
- Actual result: Your camera side changes, but your peer's camera preview is also disabled for a few seconds.
## Additional information
![why_does_change_camera_also_change_peer](/uploads/aa167dd8492ec6058e65b88253aebda8/why_does_change_camera_also_change_peer.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1228JamiAccount: disable message sending on non-swarm2023-03-31T17:14:38ZSébastien BlinJamiAccount: disable message sending on non-swarmNon-swarm conversations must be disabled as we migrate to swarm only more than a year ago.
Sending a message to a non-swarm conversation will break the conversation for the peer causing a downgradeNon-swarm conversations must be disabled as we migrate to swarm only more than a year ago.
Sending a message to a non-swarm conversation will break the conversation for the peer causing a downgradehttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1233Calls to Android client is not workable (private JAMI network)2023-07-26T13:49:31ZAleksey KvasnikovCalls to Android client is not workable (private JAMI network)We roll-out JAMI in the network without Internet access. Network have 5 IP subnets. In 2 subnets we have Windows 10 with JAMI clients, in 2 subnets we have Android phones with JAMI clients, installed from Google Play. In the last subnet ...We roll-out JAMI in the network without Internet access. Network have 5 IP subnets. In 2 subnets we have Windows 10 with JAMI clients, in 2 subnets we have Android phones with JAMI clients, installed from Google Play. In the last subnet we have Debian 11 server with dhtnode installed from APT package. We use this dhtnode as a bootstrap for all clients. All other settings disabled. For Android we disable push notifications and allow JAMI to run in background.
Between Windows clients everything works OK - we can call, send messages and files. Between Windows and Android we can send messages and files. Call from Android to Windows work fine (video and audio). In case if we call from Windows to Android, Android client cannot pickup call. We press button, but no effect. Telephone coninue ringing. If we disconnect call from Windows side - no effect, Android continue ringing. After some time ringing stops, but app not working and suggest to return to ongoing call. If I close app, it will not help - still suggesting to return to ongoing call. Only after phone restart JAMI app become workable. I collect two log files in Android app in the moment, when call from Windows was received and I cannot pickup call.
Jami version 20230310-01
Phone - Samsung A32
Android 13
Windows 10 19045.2728
Jami version 202303031415
I should mention what we try 3-4 different phones and 2-3 different Androids client for JAMI. Problem exactly same.
Also exactly same problem arise when we call between two Android phones.
[log_20230407_125847_4077836806239187095.log](/uploads/ee71c0f0d2c056db93ceed01b38d0800/log_20230407_125847_4077836806239187095.log)
[log_20230407_133601_2759086551447336315.log](/uploads/f5dba07503e2dac5e3ff091d99958e0f/log_20230407_133601_2759086551447336315.log)Sébastien BlinSébastien Blinhttps://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/1284Voice messages should be visually recognisable as such in the document view2023-05-29T12:12:41ZannaVoice messages should be visually recognisable as such in the document view![Screenshot](/uploads/45192233b09aaf350ea5f4557546080d/Screenshot.png)
At the moment, there is simply a dark arrow on a white background.
If there are several voice messages, there are several dark arrows listed on a white background i...![Screenshot](/uploads/45192233b09aaf350ea5f4557546080d/Screenshot.png)
At the moment, there is simply a dark arrow on a white background.
If there are several voice messages, there are several dark arrows listed on a white background in a row.
Világfa - 20230502-01 (F-Droid)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1295Jami is unable to use the local area network without a network connection2024-01-19T20:13:44Zsession 21Jami is unable to use the local area network without a network connectionWhen only the local LAN is connected, devices cannot communicate with each other.
Because Jami seems to have to be connected to the internet to use it. If there is no internet, Jami will prompt 'No network connection'.
This situation s...When only the local LAN is connected, devices cannot communicate with each other.
Because Jami seems to have to be connected to the internet to use it. If there is no internet, Jami will prompt 'No network connection'.
This situation should be easily reproducible, but I am still willing to provide relevant records if gentlemen need them.
I think that if it can be compatible with a local area network, not just the internet, it may allow Jami to have similar functions as Briar, and Jami can make voice and video calls, which is a great feature of Jami.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1299Crash when using localization2023-06-16T15:46:37ZPierre NicolasCrash when using localization## Describe your environment
Please specify the following:
- Jami version: 20230602-01
- Device model: Samsung SM-T720
- Android version: Android 11 API30
- What build you are using: your own android:0f6cf118a2d1c3cc497a4b4bebe...## Describe your environment
Please specify the following:
- Jami version: 20230602-01
- Device model: Samsung SM-T720
- Android version: Android 11 API30
- What build you are using: your own android:0f6cf118a2d1c3cc497a4b4bebe7183ded515d4d daemon:5bf8188d6990d586da4121389cf4dfa193e48574
## Additional information
[crash_localization](/uploads/27ec12a1caa211ee96e980b22d7017b5/crash_localization)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1305Beep is playing on incoming call, regardless of ringtone2023-10-26T18:33:48ZWear GuxjBeep is playing on incoming call, regardless of ringtoneWhen receiving incoming call on Android client, there is a soft beep playing on intervals, similar to what the caller hears when placing a call on a regular telephone. It plays even if ringtone is set to silent in account/media settings....When receiving incoming call on Android client, there is a soft beep playing on intervals, similar to what the caller hears when placing a call on a regular telephone. It plays even if ringtone is set to silent in account/media settings. Or if a ringtone is indeed set, this beep will combine with the real ringtone. I see no reason for this beep to be present. Not sure if it's the daemon or the client that generates this sound.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1306Delayed clearance of "in-call" banner2023-07-12T16:37:16ZWear GuxjDelayed clearance of "in-call" bannerAfter I hang up from a call, the chat view reappears, but the banner at the top saying "return to ongoing call" will linger for some seconds before disappearing. This may not be a significant problem, but if instead the banner would not ...After I hang up from a call, the chat view reappears, but the banner at the top saying "return to ongoing call" will linger for some seconds before disappearing. This may not be a significant problem, but if instead the banner would not show to begin with, it would be less confusing. Or maybe the solution would be to not return to the chat view before the call is completely hung up.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1314SIP call with SRTP doesn't work, RTP fallback doesn't work either2023-07-25T08:31:05ZPierre NicolasSIP call with SRTP doesn't work, RTP fallback doesn't work either## Describe your environment
- Device model: Samsung SM-T720
- Android version: Android 11 API30
- What build you are using: your own android:94f816d399ba5f24af1670dfea99b87da1497a6e daemon:3c25f607f4f52028409fc0ea119ca943550e55e0...## Describe your environment
- Device model: Samsung SM-T720
- Android version: Android 11 API30
- What build you are using: your own android:94f816d399ba5f24af1670dfea99b87da1497a6e daemon:3c25f607f4f52028409fc0ea119ca943550e55e0
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Active param Encrypt media streams (SRTP)
2. Try to place or receive a cal
- Actual result: it doesn't work
3. Active param Fallback to RTP if SRTP fails
- Actual result: it doesn't fallbackhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1316Superposed UI elements when adding a SIP account2023-07-12T14:04:20ZPierre NicolasSuperposed UI elements when adding a SIP account## Describe your environment
- Device model: Samsung SM-T720
- Android version: Android 11 API30
- What build you are using: your own android:94f816d399ba5f24af1670dfea99b87da1497a6e daemon:3c25f607f4f52028409fc0ea119ca943550e55e0
## A...## Describe your environment
- Device model: Samsung SM-T720
- Android version: Android 11 API30
- What build you are using: your own android:94f816d399ba5f24af1670dfea99b87da1497a6e daemon:3c25f607f4f52028409fc0ea119ca943550e55e0
## Additional information
![image](/uploads/f71b1b7686963d74c18b6a1bba752d92/image.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1319UI glitch when selecting contacts for new swarm2023-07-12T18:05:40ZPierre NicolasUI glitch when selecting contacts for new swarm## Describe your environment
- Jami version:
- Device model: Samsung-T720
- Android version: 20230710-01
- What build you are using: own 575fc884dfb95e46ae9a8bad5e7bf15f7c5b6b2f
## Additional information
![random_bottomsheeti...## Describe your environment
- Jami version:
- Device model: Samsung-T720
- Android version: 20230710-01
- What build you are using: own 575fc884dfb95e46ae9a8bad5e7bf15f7c5b6b2f
## Additional information
![random_bottomsheetidalog](/uploads/4649284b55634abcda16abce10ab9972/random_bottomsheetidalog.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1322[SIP-Account] Android version of Jami still shows "Block contact"; Deleting (...2023-07-14T13:34:52ZElys[SIP-Account] Android version of Jami still shows "Block contact"; Deleting (SIP-)contact takes longusing Jami(20230710-01) on Android
If you receive a call the caller will be added to the contact list.
- If you tap the contact you'll still get the option "Block contact" (which does NOT work https://git.jami.net/savoirfairelinux/jami...using Jami(20230710-01) on Android
If you receive a call the caller will be added to the contact list.
- If you tap the contact you'll still get the option "Block contact" (which does NOT work https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1207)? So you should remove it
- If you try to delete a caller (Name "Anonymous" since the caller used a private number) from the contact list it can take very long (like 30 seconds or longer)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1325Network doesn't support video calls2023-12-27T16:32:21ZElysNetwork doesn't support video callsI am using the newest beta version of Jami and Mate 20 Pro (EMUI 12)
Steps to reproduce:
Make a video call (Android -> Desktop)
You'll get this notification:
![Videocall](/uploads/c3a3d011bbad97909e011f570e49d51a/Videocall.png)
I thi...I am using the newest beta version of Jami and Mate 20 Pro (EMUI 12)
Steps to reproduce:
Make a video call (Android -> Desktop)
You'll get this notification:
![Videocall](/uploads/c3a3d011bbad97909e011f570e49d51a/Videocall.png)
I think it's wrong because I've tried like 5 other messengers with video calls without any issues (same network)
Also I think sometimes video calls still work although this notification is shown
AND you can make an audio call and add video.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1338Jami for Android sends 1080p, 1440p and 4K video streams with a 4:3 aspect ra...2023-07-24T19:57:07ZRichard BranchesJami for Android sends 1080p, 1440p and 4K video streams with a 4:3 aspect ratio when using the front cameraPlease specify the following:
* Jami version: 20230714-01
* Device model: Moto G32
* Android version: Android 12.
* What build you are using: Play Store.
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Ope...Please specify the following:
* Jami version: 20230714-01
* Device model: Moto G32
* Android version: Android 12.
* What build you are using: Play Store.
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami app
2. Select a contact
3. Hit the videocall button
4. The videocall starts with no problem on both ends
- Actual result: 1080p, 1440p and 4K video streams are sent with a 4:3 aspect ratio when using the front camera, however, they are sent with the 16:9 aspect ratio when using the rear camera.
- Expected result: Looks like the Jami app must detect what resolutions the front camera supports and what resolutions the rear camera supports and display them in two separate settings, it appears the front camera only supports up to 1080p but I can't confirm it, but if the front camera also support 1440p and 4K, then the aspect ratio for both should be 16:9, otherwise, they should remain hidden.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1340RTP Port Range Configuration in SIP Account gets to Defaults every time you r...2023-07-26T16:04:27Zdenn0nRTP Port Range Configuration in SIP Account gets to Defaults every time you restar the appEvery time you restart the app the RTP PORT configuration reset to he default Minimun 16384 and Maximum 32766
and I had to disconnect the Account restart the app reconfigure the Port Range and then reconnect the account to the change wo...Every time you restart the app the RTP PORT configuration reset to he default Minimun 16384 and Maximum 32766
and I had to disconnect the Account restart the app reconfigure the Port Range and then reconnect the account to the change works if you don't do in the correct order you get a connection error
## Describe your environment
Please specify the following:
Jami version: 20230502-01
Device model: Xiaomi Merlin mt6768
Android version: 11
Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:Create an SIP Account
1. Configure RTP Port Range and any other configuration The Sip Account needs
2. Reboot the Movil Or Restart the Jami App
...
- Actual result: the Rtp Port Range it's Change to the defaults Minimun 16384 and Maximum 32766
- Expected result: Keeps the Configuration
## Additional information
I Had test this on other devices whit same result !Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1341Video (of the other peer) lost if you double tap "Make video call"2023-07-27T14:43:04ZElysVideo (of the other peer) lost if you double tap "Make video call"might be related to: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999
using the newest beta versions of Jami (Android (useraccount1) -> Windows 10 (useraccount2))
Steps to reproduce (always on Android):
1. Tap "Ma...might be related to: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999
using the newest beta versions of Jami (Android (useraccount1) -> Windows 10 (useraccount2))
Steps to reproduce (always on Android):
1. Tap "Make video call"
1. Very shortly after / while you tap: Tap "Make a video call" again
1. You'll get a notification that you are already making a call
Now I think there are two steps:
- The first time you reproduce these steps everything will work?
- The second time you reproduce these steps the video of Android will be lost and if you use the desktop client to exit the call the video of the Android user will be still running forever (just the video (own preview) will stuck (NOT just 30 seconds https://git.jami.net/savoirfairelinux/jami-project/-/issues/1583#note_44521))?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1342"Swarm group" context menu should differ from "swarm one to one" one2024-01-26T13:38:16ZPierre Nicolas"Swarm group" context menu should differ from "swarm one to one" oneTicket extracted from meta-ticket https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1272#note_42534 @wearguxj
> In the list of conversations, the context menu for a group conversation looks exactly as for a 1+1 conversa...Ticket extracted from meta-ticket https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1272#note_42534 @wearguxj
> In the list of conversations, the context menu for a group conversation looks exactly as for a 1+1 conversation:
>
> #### Copy number
>
> I think it's not clear what kind of number is being referred to. Should it instead be called "Copy address"?
> Anyway, clicking this option on a group conversation causes the app to crash.
>
> #### Remove contact
>
> This option is functional, but it needs different phrasing. I suggest any of:
>
> * Leave group
> * Leave conversation
> * Abandon group
> * Abandon conversation
>
> I'm thinking that the word "abandon" better suggests that the conversation will be removed from my list, an then it cannot easily be reaccessed.
>
> The word "remove" should not be used, since that would imply that all other members would also be kicked out, which is not the case.
>
> But if I am the last remaining member, maybe "delete" would be a more proper word?
>
> #### Block contact
>
> Either this option should not be present, or it should not refer to a "contact".
> Would it make sense to block a group conversation? Maybe. Anyways, clicking on this does not appear to prevent me from receiving new messages. And cannot tell later that it's in blocked state.Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1345Can't cancle file transfer/ Jami will still show a download progress2024-01-12T21:24:23ZElysCan't cancle file transfer/ Jami will still show a download progressusing newest beta version of Jami
useraccount 1 (Windows 10) -\> useraccount 2 (Android)
* Start a file transfer (big file) Windows 10 -\> Android
* Exit Jami just on desktop (Windows 10) during the file transfer
* Jami on Android will...using newest beta version of Jami
useraccount 1 (Windows 10) -\> useraccount 2 (Android)
* Start a file transfer (big file) Windows 10 -\> Android
* Exit Jami just on desktop (Windows 10) during the file transfer
* Jami on Android will still show a download progress (other issue https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1151)
* Now you exit Jami on Android too (Jami will still show a notification?; although you disabled "run in background")
* Now enter Jami on Android again (desktop is still no longer used)
* Jami will show "unjoinable peer"
![filetransferFAIL.png](/uploads/521618c83338ce1d089554193ec9a219/filetransferFAIL.png)
* One you exit Jami and enter Jami again (only on Android; after 20 minutes?) you will view a download option that won't work
* If you open Jami on desktop too the download will start again (the desktop will always show "finished" although that's not true)
* If you exit Jami just on Android Jami will now show a (wrong; non-workingj)"Download" option again
* You have to exit both apps on Android and Windows so that the download will proceed
---
Not sure what will happen with voice and video messages or the other way desktop -\> Android but maybe you can try outhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1352Google TV 12 doesn't pick up sound from mic when making videocalls to other d...2023-09-03T02:48:34ZRichard BranchesGoogle TV 12 doesn't pick up sound from mic when making videocalls to other devicesDevices involved in the test:
Onn 2023 with Google TV 12.
Homatics Box R 4K Plus with Android TV 11.
When I make videocalls from my Google TV device with Android 12 to my Windows 10 computer or to my Android TV device with Android 11,...Devices involved in the test:
Onn 2023 with Google TV 12.
Homatics Box R 4K Plus with Android TV 11.
When I make videocalls from my Google TV device with Android 12 to my Windows 10 computer or to my Android TV device with Android 11, the microphone from the webcam connected to the Google TV device with Android 12 doesn't pick up any sounds, it's completely mute, however, when I make videocalls from the Windows 10 computer or from the Android TV device with Android 11 to the Google TV device with Android 12, the microphone picks all sounds correctly.
Please specify the following:
- Jami version: 20230818-01
- Device model: Onn 2023, Homatics Box R 4K Plus
- Android version: Android 11, Android 12 and Windows 10.
- What build you are using: Play Storehttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1353volume output too low (and speaker mode doesn't change anything)2023-08-24T15:54:14ZMaxim Cournoyervolume output too low (and speaker mode doesn't change anything)
Please specify the following:
- Jami version: 20230818-01
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. P...
Please specify the following:
- Jami version: 20230818-01
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Place video call from GNU/Linux client (but probably doesn't matter)
2. Receive video call on Android client
...
- Actual result: Volume is barely audible.
- Expected result: Volume should be loud, when volume is maxed out and speaker mode is on.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1354Sharing files from Android creates multiple Jami tasks to run in parallel, ca...2023-08-24T15:54:38ZMaxim CournoyerSharing files from Android creates multiple Jami tasks to run in parallel, causing problems## Describe your environment
Please specify the following:
- Jami version: 20230818-01
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the ...## Describe your environment
Please specify the following:
- Jami version: 20230818-01
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Ensure there is no Jami in your active tasks.
1. Open your favorite Android file manager app.
1. Select a file, then press "Share" -> Press the Jami "Share with..." icon -> Select contact
1. Press the Android tasks button, and observe there is now two Jami related tasks: "Share with..." and "Jami".
1. Repeat steps 2 and 3.
1. Observe there is now *four* Jami related tasks.
- Actual result: Jami tasks keep adding up.
- Expected result: A single Jami task should run.
See the video below for a demonstration of the problem.
https://youtu.be/eg-6YsyJ2i4Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1355Horrible video decoding artifacts (sender: GNU/Linux, receiver: Android)2024-01-10T17:22:54ZMaxim CournoyerHorrible video decoding artifacts (sender: GNU/Linux, receiver: Android)## Describe your environment
Please specify the following:
- Jami version: 20230818.01
- Device model: Galaxy Tab S2
- Android version: Android 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bu...## Describe your environment
Please specify the following:
- Jami version: 20230818.01
- Device model: Galaxy Tab S2
- Android version: Android 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Place a video call from GNU/Linux to Android client. Make some movements to more easily trigger the problem.
2. Observe the video quality received on the Android client.
- Actual result: Video quality is abysmal, with the caller at points hardly discernible (see images).
- Expected result: Received video should be free of serious artifacts and have a decent quality.
## Additional information
The sender video is from a Logitech G920 camera and hardware acceleration is in effect (Radeon R9 290 with amdgpu driver), in case this matters.
![Screenshot_20230806-125331.png](/uploads/eaf9e213b21d91811b3d7c14a3ecea28/Screenshot_20230806-125331.png)
![Screenshot_20230806-125639.png](/uploads/7d27e3b9fbaaa5726839789ce0161992/Screenshot_20230806-125639.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1362ForegroundServiceStartNotAllowedException2023-09-12T14:45:14ZPierre NicolasForegroundServiceStartNotAllowedExceptionGoogle play console : crash at runtime
Devices : android 12, 12L and 13
```plaintext
Exception java.lang.RuntimeException:
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:5110)
at android.app.ActivityThread.ac...Google play console : crash at runtime
Devices : android 12, 12L and 13
```plaintext
Exception java.lang.RuntimeException:
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:5110)
at android.app.ActivityThread.access$2100 (ActivityThread.java:310)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2319)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loopOnce (Looper.java:226)
at android.os.Looper.loop (Looper.java:313)
at android.app.ActivityThread.main (ActivityThread.java:8663)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1135)
Caused by android.app.ForegroundServiceStartNotAllowedException:
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel (ForegroundServiceStartNotAllowedException.java:54)
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel (ForegroundServiceStartNotAllowedException.java:50)
at android.os.Parcel.readParcelable (Parcel.java:3345)
at android.os.Parcel.createExceptionOrNull (Parcel.java:2432)
at android.os.Parcel.createException (Parcel.java:2421)
at android.os.Parcel.readException (Parcel.java:2404)
at android.os.Parcel.readException (Parcel.java:2346)
at android.app.IActivityManager$Stub$Proxy.setServiceForeground (IActivityManager.java:8094)
at android.app.Service.startForeground (Service.java:786)
at cx.ring.services.DataTransferService.onStartCommand (DataTransferService.kt:62)
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:5092)
Caused by android.os.RemoteException: Remote stack trace:
at com.android.server.am.ActiveServices.setServiceForegroundInnerLocked (ActiveServices.java:1955)
at com.android.server.am.ActiveServices.setServiceForegroundLocked (ActiveServices.java:1455)
at com.android.server.am.ActivityManagerService.setServiceForeground (ActivityManagerService.java:14154)
at android.app.IActivityManager$Stub.onTransact (IActivityManager.java:3648)
at com.android.server.am.ActivityManagerService.onTransact (ActivityManagerService.java:3038)
```Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1364SIP account "randomly" disconnect with "connection error"2023-09-13T18:20:26ZThomas M.SIP account "randomly" disconnect with "connection error"Hello
I am new to Jami. I use it as a SIP client, with ntfy for push notifications
It appears that sometimes, “randomly”, at least I cannot reproduce it, it disconnects
It is written “Connection Error” and in the logs, I have read: “SIP ...Hello
I am new to Jami. I use it as a SIP client, with ntfy for push notifications
It appears that sometimes, “randomly”, at least I cannot reproduce it, it disconnects
It is written “Connection Error” and in the logs, I have read: “SIP registration failed, status=500 (Registering glare condition)”
I have to toggle on/off to reconnect. Sometimes it reconnects by itself after a while
What could it be? I tried different app, and two are installed at the same time (Jami and another one)
There could be a conflict?
I have already read some thread looking this one, but they date from 2021, they are maybe outdated?
Thank you in advance for your help
specifications:
* Another SIP client than Jami is installed on the smartphone
* I use e/OS and not "regular" Android
* I use a VPN
* It seems it only happens on Wifi, not on mobile data (with mobile data, I do not use the VPN)
Here is the log I exported finding the account disconnected (I hope I deleted all personal data...)
Thank you in advance for your help
<details><summary>Click to expand</summary>
```
[xxxxxxxxx.xxx|19808|manager.cpp :720 ] Not initialized
[xxxxxxxxx.xxx|19808|manager.cpp :794 ] Using PJSIP version 2.12.1 for aarch64-unknown-linux-android
[xxxxxxxxx.xxx|19808|manager.cpp :795 ] Using GnuTLS version 3.8.0
[xxxxxxxxx.xxx|19808|manager.cpp :796 ] Using OpenDHT version 2.6.0
[xxxxxxxxx.xxx|19808|manager.cpp :797 ] Using FFmpeg version 4.0.0-3315-g9899ae3f2
[xxxxxxxxx.xxx|19808|manager.cpp :800 ] Using Libgit2 version 1.6.4
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :742 ] SIPVoIPLink@xxxxxxxxxxxx
[xxxxxxxxx.xxx|19808|manager.cpp :816 ] Configuration file path: /data/user/0/cx.ring/app_config/dring.yml
[xxxxxxxxx.xxx|19808|system_codec_container.cpp:220 ] Can't find a usable accelerated H265/HEVC codec, disabling.
[xxxxxxxxx.xxx|19808|system_codec_container.cpp:250 ] Encoders found: H264 VP8 MP4V-ES H263-1998 opus G722 G726-32 speex speex speex PCMA PCMU
[xxxxxxxxx.xxx|19808|system_codec_container.cpp:251 ] Decoders found: H264 VP8 MP4V-ES H263-1998 opus G722 G726-32 speex speex speex PCMA PCMU
[xxxxxxxxx.xxx|19808|sipaccount.cpp :1476] Presence enabled for xxxxxxxxxxxxxxxx : false.
[xxxxxxxxx.xxx|19808|ringbuffer.cpp :55 ] Create new RingBuffer urgentRingBuffer_id
[xxxxxxxxx.xxx|19808|audiolayer.cpp :65 ] [audiolayer] AGC: 1, noiseReduce: auto, VAD: 1, echoCancel: auto, audioProcessor: webrtc
[xxxxxxxxx.xxx|19808|sipaccount.cpp :1476] Presence enabled for xxxxxxxxxxxxxxxx : false.
[xxxxxxxxx.xxx|19808|sipaccount.cpp :566 ] doRegister xxx.xxxx.fr
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :1521] try to resolve 'xxx.xxxx.fr' (port: 0)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :663 ] Creating transport
[xxxxxxxxx.xxx|19808|siptransport.cpp :332 ] Created UDP transport on address 0.0.0.0:5060
[xxxxxxxxx.xxx|19808|siptransport.cpp :83 ] SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=2
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [xxxxxxxxxxxx]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :755 ] Using contact header <sip:xx.x.x.x2xxxx@xx.x.x.x:5060> in registration
[xxxxxxxxx.xxx|19808|sipaccount.cpp :528 ] [SIP Account xxxxxxxxxxxxxxxx] setPushNotificationToken:
[xxxxxxxxx.xxx|19824|sipaccount.cpp :1565] [Account xxxxxxxxxxxxxxxx] Checking IP route after the registration
[xxxxxxxxx.xxx|19824|sipaccount.cpp :1590] Checking received VIA address: 1xx.x.x.x.125
[xxxxxxxxx.xxx|19824|sipaccount.cpp :1671] [account xxxxxxxxxxxxxxxx] Contact address changed: (xx.x.x.x:5060 --> 1xx.x.x.x.1xx.x.x.x). Updating registration.
[xxxxxxxxx.xxx|19824|sipaccount.cpp :887 ] New contact: <sip:003xxx.xxx.xx.xxx.2.1xx.x.x.x9238>
[xxxxxxxxx.xxx|19808|configurationmanager.cpp:967 ] received connectivity changed - trying to re-connect enabled accounts
[xxxxxxxxx.xxx|19808|sipaccount.cpp :307 ] Removing old transport [xxxxxxxxxxxx] from account
[xxxxxxxxx.xxx|19808|siptransport.cpp :104 ] ~SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=11
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [0x0]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :566 ] doRegister xxx.xxxx.fr
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :1521] try to resolve 'xxx.xxxx.fr' (port: 0)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :663 ] Creating transport
[xxxxxxxxx.xxx|19808|siptransport.cpp :295 ] Recycling transport 0.0.0.0:5060
[xxxxxxxxx.xxx|19808|siptransport.cpp :83 ] SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=11
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [xxxxxxxxxxxx]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :755 ] Using contact header <sip:xx.x.x.x2xxxx@xx.x.x.x:5060> in registration
[xxxxxxxxx.xxx|19825|message_engine.cpp :346 ] [Account xxxxxxxxxxxxxxxx] saved 0 messages to /data/user/0/cx.ring/cache/xxxxxxxxxxxxxxxx/messages
[xxxxxxxxx.xxx|19808|configurationmanager.cpp:967 ] received connectivity changed - trying to re-connect enabled accounts
[xxxxxxxxx.xxx|19808|sipaccount.cpp :957 ] pjsip_regc_send failed with error 171001: Object is busy (PJSIP_EBUSY)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :701 ] doUnregister VoipLinkException occurred: Unable to send request to unregister sip account
[xxxxxxxxx.xxx|19808|sipaccount.cpp :307 ] Removing old transport [xxxxxxxxxxxx] from account
[xxxxxxxxx.xxx|19808|siptransport.cpp :104 ] ~SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=15
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [0x0]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :566 ] doRegister xxx.xxxx.fr
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :1521] try to resolve 'xxx.xxxx.fr' (port: 0)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :663 ] Creating transport
[xxxxxxxxx.xxx|19808|siptransport.cpp :295 ] Recycling transport 0.0.0.0:5060
[xxxxxxxxx.xxx|19808|siptransport.cpp :83 ] SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=15
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [xxxxxxxxxxxx]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :755 ] Using contact header <sip:xx.x.x.x2xxxx@xx.x.x.x:5060> in registration
[xxxxxxxxx.xxx|19808|sipaccount.cpp :528 ] [SIP Account xxxxxxxxxxxxxxxx] setPushNotificationToken:
[xxxxxxxxx.xxx|19808|configurationmanager.cpp:967 ] received connectivity changed - trying to re-connect enabled accounts
[xxxxxxxxx.xxx|19808|sipaccount.cpp :957 ] pjsip_regc_send failed with error 171001: Object is busy (PJSIP_EBUSY)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :701 ] doUnregister VoipLinkException occurred: Unable to send request to unregister sip account
[xxxxxxxxx.xxx|19808|sipaccount.cpp :307 ] Removing old transport [xxxxxxxxxxxx] from account
[xxxxxxxxx.xxx|19808|siptransport.cpp :104 ] ~SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=21
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [0x0]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :566 ] doRegister xxx.xxxx.fr
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :1521] try to resolve 'xxx.xxxx.fr' (port: 0)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :663 ] Creating transport
[xxxxxxxxx.xxx|19808|siptransport.cpp :295 ] Recycling transport 0.0.0.0:5060
[xxxxxxxxx.xxx|19808|siptransport.cpp :83 ] SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=21
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [xxxxxxxxxxxx]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :755 ] Using contact header <sip:xx.x.x.x2xxxx@xx.x.x.x:5060> in registration
[xxxxxxxxx.xxx|19824|sipaccount.cpp :854 ] SIP registration failed, status=500 (Registering glare condition)
[xxxxxxxxx.xxx|19824|sipaccount.cpp :1773] Scheduling re-registration retry in 51 seconds..
[xxxxxxxxx.xxx|19816] Connectivity change check: host address xx.x.x.x
[xxxxxxxxx.xxx|19808|sipaccount.cpp :528 ] [SIP Account xxxxxxxxxxxxxxxx] setPushNotificationToken:
```
</details>https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1370Should not display color and emoji customisation for contact request2023-09-12T17:59:08ZPierre NicolasShould not display color and emoji customisation for contact requestAnd should load value by default.
![Screen_recording_20230912_135740.mp4](/uploads/4b19069a50aba8e4cb35f2d192a9a748/Screen_recording_20230912_135740.mp4)And should load value by default.
![Screen_recording_20230912_135740.mp4](/uploads/4b19069a50aba8e4cb35f2d192a9a748/Screen_recording_20230912_135740.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1374Incorrect preview in conference2023-09-15T14:09:37ZSébastien BlinIncorrect preview in conference# Scenario
+ Alice (Desktop) calls Bob (Desktop)
+ Carla (Android) is added to the conference by Alice
# Expected result
Carla's video tile should show Carla
# Current result
Carla's video tile is empty.# Scenario
+ Alice (Desktop) calls Bob (Desktop)
+ Carla (Android) is added to the conference by Alice
# Expected result
Carla's video tile should show Carla
# Current result
Carla's video tile is empty.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1376Swarm title should be its name, not a list of participants2023-09-18T15:03:25ZWear GuxjSwarm title should be its name, not a list of participantsIn the main screen (list of recent conversations), a swarm title currently consists of all participants' names.
Preferably, the title should instead primarily be the name that was set for the swarm, if any. Then, a less significant sub...In the main screen (list of recent conversations), a swarm title currently consists of all participants' names.
Preferably, the title should instead primarily be the name that was set for the swarm, if any. Then, a less significant subtitle could mention the participants as well.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1385Jami will still run in background for a few seconds/minutes or even longer if...2024-01-08T16:59:32ZElysJami will still run in background for a few seconds/minutes or even longer if you exitusing the newest beta version of Jami
and Android 13
Go to advanced settings:
You've always
* disabled "Start Jami on startup",
* disabled "Run in background"
* optional: disable "Push notifications"
Steps to reproduce:
* After you...using the newest beta version of Jami
and Android 13
Go to advanced settings:
You've always
* disabled "Start Jami on startup",
* disabled "Run in background"
* optional: disable "Push notifications"
Steps to reproduce:
* After you've rebooted your phone you might have to make a call once (Desktop -\> Android)
* After you've used Jami exit Jami on Android (but the desktop user (same account) will never exit)
* Even after a few seconds or even minutes you can still call the Android user (Call: samecontact -\> samecontact) - Jami will open the Android app - but this might not be always the case - sometimes calls will immediately fail - sometimes the Android user will receive the call
Expected: Shouldn't the Android user never receive any call anymore?
If you don't use the same user account (username1 \<-\> username1) but a different (username2 -\> username1) Jami on desktop will receive an invitation of username2 and the account username1 will now have username2 twice in the contact list?
---
Even if you exit the desktop app and open Jami on desktop again still same behaviour - Maybe related: https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1352
Two more things:
* Maybe this happens if you are using the same Jami account on multiple devices
* Maybe this also / or only happens if you exit during a file transfer?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1387Possible to modify avatar of searched contact2023-09-29T16:14:16ZPierre NicolasPossible to modify avatar of searched contact## Describe your environment
- Jami version: 20230925
- Device model: Samsung S20
- Android version: 13
- What build you are using: Play Store
## Additional information
As you can see, option "add to contacts" is displayed. So...## Describe your environment
- Jami version: 20230925
- Device model: Samsung S20
- Android version: 13
- What build you are using: Play Store
## Additional information
As you can see, option "add to contacts" is displayed. So it's not my contact but a contact I searched on the search view.
![Screen_recording_20230929_120313](/uploads/cf9a73f0b5c59575f2a0eb4e75b433c7/Screen_recording_20230929_120313.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1389Crash because of the new JamiId feature2023-10-02T23:19:16ZPierre NicolasCrash because of the new JamiId feature## Describe your environment
- Jami version: apk 383
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
Related the stop/start of the activity
![Screen_recording_20231002_093108](/uploads/c359...## Describe your environment
- Jami version: apk 383
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
Related the stop/start of the activity
![Screen_recording_20231002_093108](/uploads/c359edd04616fa28c6b35c44a0b8403b/Screen_recording_20231002_093108.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1398The synchronisation of the reactions does not work as expected2023-10-10T14:53:00ZannaThe synchronisation of the reactions does not work as expectedWhile on the Dekstop a reaction from my contact is displayed once, the Android version displays the same reaction of the contact four times.
Another entry in the mobile version shows two hearts that I supposedly gave in response to a me...While on the Dekstop a reaction from my contact is displayed once, the Android version displays the same reaction of the contact four times.
Another entry in the mobile version shows two hearts that I supposedly gave in response to a message from my contact. However, in the desktop version from which I sent this message, there is no reaction from me to my contact's message. If I deselect the two hearts by tapping on the reactions in the mobile message, it only works for one of the hearts. If I also want to remove the second one, it will mark itself again. If I now restart Jami, the Android version suddenly shows me three hearts for the same message.
One more note: I'm currently online with both devices at the same time, but not on the same network.
Eleutheria 20231002-02https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1399Crashes when scrolling or fast scrolling in Contact Details > Documents2023-10-11T12:53:46ZannaCrashes when scrolling or fast scrolling in Contact Details > DocumentsWhen scrolling or fast scrolling in Contact details > Documents, either the crash "Jami keeps stopping" occurs or the window crashes so that I find myself back in the chat.
Reminds me a bit of https://git.jami.net/savoirfairelinux/jami-...When scrolling or fast scrolling in Contact details > Documents, either the crash "Jami keeps stopping" occurs or the window crashes so that I find myself back in the chat.
Reminds me a bit of https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1254
Eleutheria - 20231006-01https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1400Nothing happens when I tap "DOWNLOAD"2023-10-14T09:34:23ZannaNothing happens when I tap "DOWNLOAD"![Screenshot](/uploads/6dc4550e2e7701c0b5ef6851c9a92dd7/Screenshot.png)
Incidentally, it's a file that was originally sent to my desktop client even before I exported Jami to my Android device.
Eleutheria - 20231006-01![Screenshot](/uploads/6dc4550e2e7701c0b5ef6851c9a92dd7/Screenshot.png)
Incidentally, it's a file that was originally sent to my desktop client even before I exported Jami to my Android device.
Eleutheria - 20231006-01https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1411connect device broken button in android app2023-10-23T18:57:03Zdsb-yconnect device broken button in android appon my pc i installed jami from debian bookworm package and made an account and set a password. i then downloaded the app from the google play store on my android one plus 9 android 13. i selected to sign in from an existing device. on my...on my pc i installed jami from debian bookworm package and made an account and set a password. i then downloaded the app from the google play store on my android one plus 9 android 13. i selected to sign in from an existing device. on my pc i said link a new device and it gave me a pin. on my android i entered the correct pin and password and yet the button to sign in would not activate. i had to transfer a backup from my pc to my phone and then sign in that way.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1408Tapping on "Share location" in the three-dot menu only causes a pop-up window...2023-12-21T20:01:37ZannaTapping on "Share location" in the three-dot menu only causes a pop-up window to flicker up briefly and then close againIf it is not just a bug, but a technical requirement for this functionality is not met, I would like to see a note.
For example, if the audio recorder app or camera app is missing, the following message appears after tapping: "Can't find...If it is not just a bug, but a technical requirement for this functionality is not met, I would like to see a note.
For example, if the audio recorder app or camera app is missing, the following message appears after tapping: "Can't find audio/camera recorder app".
Eleutheria - 20231006-01https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1414Sometimes messages in certain groups are ignored2023-10-26T12:41:41Zsession 21Sometimes messages in certain groups are ignoredSometimes, because members in a group are not always online, we may miss certain messages.
For example, in group chats, there are many people. When a member sends a message on the 1st, but we only receive it on the 3rd, we may miss the ...Sometimes, because members in a group are not always online, we may miss certain messages.
For example, in group chats, there are many people. When a member sends a message on the 1st, but we only receive it on the 3rd, we may miss the message due to too many chat records.
Can Jami highlight unread messages to help us not miss any of them?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1435Moderator icon and function does not appear in conference2023-11-08T15:20:39ZEmma FalkiewitzModerator icon and function does not appear in conferenceOn QT the crown is shown:
![image](/uploads/40873037bb7f7f49ab95fac8855f2abd/image.png)
But on android no, and the function is not set in the conference parameters:
![Screenshot_20231103_165727](/uploads/dd60ae6fd42c2e0ede9690ff36e9b4b...On QT the crown is shown:
![image](/uploads/40873037bb7f7f49ab95fac8855f2abd/image.png)
But on android no, and the function is not set in the conference parameters:
![Screenshot_20231103_165727](/uploads/dd60ae6fd42c2e0ede9690ff36e9b4b6/Screenshot_20231103_165727.png)Emma FalkiewitzEmma Falkiewitzhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1436Raise hand icon is not shown immediately2023-11-03T21:19:21ZEmma FalkiewitzRaise hand icon is not shown immediately![Screen_recording_20231103_171224](/uploads/ade93725671523667ed0382e7ebe38ae/Screen_recording_20231103_171224.mp4)![Screen_recording_20231103_171224](/uploads/ade93725671523667ed0382e7ebe38ae/Screen_recording_20231103_171224.mp4)Emma FalkiewitzEmma Falkiewitzhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1438Click on notification doesnt redirect user to conversation2023-11-06T19:27:31ZPierre NicolasClick on notification doesnt redirect user to conversationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1442Abnormal group message, unable to transmit normally2023-11-23T13:07:48Zsession 21Abnormal group message, unable to transmit normallyIn a group of multiple people, there are certain factors that can cause messages to not be transmitted properly. But I cannot confirm if they are the same issue.
So I can only describe the situation I encountered.
**Computer, Windows 1...In a group of multiple people, there are certain factors that can cause messages to not be transmitted properly. But I cannot confirm if they are the same issue.
So I can only describe the situation I encountered.
**Computer, Windows 10, version (Beta): 202311011813**
Sending messages in a group of multiple people can occasionally be very slow, and the received messages may be missing.
**Android 12, version 390, Samsung**
I have set up the background running and set the app's background running time to "unlimited" in the system, but after the phone's screen is stopped, the app will no longer display new messages. You need to forcibly close the application and then restart it to receive new messages.
**The same situation will be encountered**
My phone and computer are missing messages received in a group of multiple people, but if I restart and receive the previously missing messages, I don't know if this is a problem with the UI display or the network.
Causing distress.
[3b80ed3cdb31dc07159f50f84adf30f949331e75_6757820254627505.log](/uploads/f8830e344f5d4b8360973f1fe4a63418/3b80ed3cdb31dc07159f50f84adf30f949331e75_6757820254627505.log)
[b7cc9d87f8395b8e93cd150646da5770691c8974_3186995143081089.log](/uploads/64c7818a013ed1be0be7f6a49a1b07bd/b7cc9d87f8395b8e93cd150646da5770691c8974_3186995143081089.log)
[windows.txt](/uploads/23b942e75047105e070f393807eec9dc/windows.txt)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/1464Notification doesn't disapear at the end of the swarm:group call2024-03-28T00:05:08ZPierre NicolasNotification doesn't disapear at the end of the swarm:group call
![image](/uploads/34fed8ee7d8c0dff31ed724cd1d53841/image.png)
![image](/uploads/34fed8ee7d8c0dff31ed724cd1d53841/image.png)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1465Presence not correctly refreshed by client2024-03-19T13:46:40ZSébastien BlinPresence not correctly refreshed by client# Debug patch
https://review.jami.net/c/jami-daemon/+/26448
# Scenario
On some network, just wait. At some point presence is lost but account is online.
# Observation
AccountManager::startSync() (for presence put on the DHT) is not ...# Debug patch
https://review.jami.net/c/jami-daemon/+/26448
# Scenario
On some network, just wait. At some point presence is lost but account is online.
# Observation
AccountManager::startSync() (for presence put on the DHT) is not called for days
This means that `JamiJobService.kt` is not correct or fail at some point.
Ideally it would be good to get a debug patch for android where the logs of the job are written in some place that we can monitor like the patch I did for the daemon to debug this issue (to check where the android client blocks)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1472Crash when returning to conversation after closing menu option2023-11-30T21:53:53ZEmma FalkiewitzCrash when returning to conversation after closing menu option![Screen_recording_20231130_165209](/uploads/97c530f82e42c8ee9d46339184c76fa2/Screen_recording_20231130_165209.mp4)![Screen_recording_20231130_165209](/uploads/97c530f82e42c8ee9d46339184c76fa2/Screen_recording_20231130_165209.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1513Wrong display of the account after clicking on a group call notification2023-12-21T22:01:47ZEmma FalkiewitzWrong display of the account after clicking on a group call notificationI call from an account (P account) a group and I answer by clicking on a notification. This notification leads me to another account (S account) that belong to the group. But the display of the S account does not change on the top left c...I call from an account (P account) a group and I answer by clicking on a notification. This notification leads me to another account (S account) that belong to the group. But the display of the S account does not change on the top left corner (it is still P account and not S account).
![Screen_recording_20231221_164913](/uploads/4a7ff7d7e0f2d00294a9edb8d9c32e3e/Screen_recording_20231221_164913.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1524Bug in reaction chip2024-01-03T22:14:28ZEmma FalkiewitzBug in reaction chip## Describe your environment
- What build you are using: master 05551ae4e81f73ebf7413caa151e897f108efd82
## Steps to reproduce
![image](/uploads/845426a98ee9f6fab7c50494c28b020e/image.png)## Describe your environment
- What build you are using: master 05551ae4e81f73ebf7413caa151e897f108efd82
## Steps to reproduce
![image](/uploads/845426a98ee9f6fab7c50494c28b020e/image.png)Emma FalkiewitzEmma Falkiewitzhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1527Emojis not delete when deleted message2024-01-17T17:09:29ZXavier Jouslin de NorayEmojis not delete when deleted message## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue i...## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue instead of creating new one.
## Bug report form
## Describe your environment
Please specify the following:
- Jami version: Eleutheria - 20231228-01
- Device model: phone
- Android version: 9
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. create a message
2. add emojis
3. delete the message
- Actual result: the emojis still here
- Expected result: should delete the emojis with the deletion of message
## Additional informationPierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1536add a member that is already in the swarm2024-01-17T15:10:37ZXavier Jouslin de Norayadd a member that is already in the swarm## Bug report form
## Describe your environment
Please specify the following:
* Jami version: Eleutheria - 20231228-01
* Device model: phone
* Android version: 9
* What build you are using: Play Store
## Steps to reproduce
- Can you...## Bug report form
## Describe your environment
Please specify the following:
* Jami version: Eleutheria - 20231228-01
* Device model: phone
* Android version: 9
* What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: \[at will | occasionally | not at all\]
- Steps:
1. create a swarm
2. add a member
3. add an other member
- Actual result: could see contact already in the swarm
- Expected result: should not see contact that are already in the swarmhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1539Receiving swarm group invitation from blocked contact2024-01-08T20:58:33ZPierre NicolasReceiving swarm group invitation from blocked contact## Bug report form
## Describe your environment
Please specify the following:
* Jami version: 399.apk
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
* Alice sends a swarm group invitation to Bob
* Bob receiv...## Bug report form
## Describe your environment
Please specify the following:
* Jami version: 399.apk
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
* Alice sends a swarm group invitation to Bob
* Bob receives an invitation and clicks on "block"
* Alice sends a new swarm group invitation to Bob
- Actual result:
- Bob receives an invitation.
- Expected result:
* Bob should not receive an invitation as Alice is blocked.
## Additional information
Looks like it works on QT.
Looks like it doesnt work on iOS.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1542Jami not receiving messages in background2024-01-17T15:20:29Z-Jami not receiving messages in background- Jami version: Eleutheria - 20231228-01
- Device model: Google Pixel 5
- Android version: 14
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Set battery optimizat...- Jami version: Eleutheria - 20231228-01
- Device model: Google Pixel 5
- Android version: 14
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Set battery optimization option for Jami to unrestricted (which disables battery optimization)
2. Turn on "Run in background"
3. Use another client to call and message this client to make sure it can receive calls and messages
4. Move this client to background by swiping left
5. Wait 10 seconds
6. Use another client to call and message this client
- Actual result: No calls or messages are received
- Expected result: Calls and messages are received
## Additional information
Messages are received after opening this client (moving to foreground).
Jami website states that [... using a permanent notification, to prevent the application from being killed (this is what the "Run in background" option in Jami has done)](https://jami.net/unifiedpush/). There is no "permanent notification" or any notification after turning on "Run in background".
When I developed an Android app that needs to run in the background, I had to use `setForegroundAsync` to keep it alive, calling this function also creates a notification. Maybe that's what Jami needs? Code example can be found here https://developer.android.com/develop/background-work/background-tasks/persistent/how-to/long-runninghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1549Conversation color is not respected for search message feature2024-01-18T15:57:19ZPierre NicolasConversation color is not respected for search message feature## Bug report form
## Describe your environment
Please specify the following:
- Jami version: 20231228-01
## Additional information
![Screen_recording_20240110_180055.mp4](/uploads/88dd89fab7885457843e696b83cb2a4d/Screen_recording_2...## Bug report form
## Describe your environment
Please specify the following:
- Jami version: 20231228-01
## Additional information
![Screen_recording_20240110_180055.mp4](/uploads/88dd89fab7885457843e696b83cb2a4d/Screen_recording_20240110_180055.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1556chatview keyboard UI bug2024-01-19T19:52:36ZPierre Nicolaschatview keyboard UI bugBug report form
---------------
## Describe your environment
Please specify the following:
- Jami version: 20240119
- Device model: smt720
- Android version: 11
- What build you are using: playstore
## Steps to reproduce
- ...Bug report form
---------------
## Describe your environment
Please specify the following:
- Jami version: 20240119
- Device model: smt720
- Android version: 11
- What build you are using: playstore
## Steps to reproduce
- Can you reproduce the bug: occasionally
## Additional information
![Screen_recording_20240119_144522](/uploads/7db3b086ea2de576adb251e67a9b6632/Screen_recording_20240119_144522.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1584Message bubble is too wide2024-01-30T21:11:30ZPierre NicolasMessage bubble is too wide## Bug report form
## Describe your environment
Please specify the following:
- Jami version: 401
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps: I don't know exactly but it happens when the message has a certain...## Bug report form
## Describe your environment
Please specify the following:
- Jami version: 401
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps: I don't know exactly but it happens when the message has a certain lenght. Doesn't happens in single line message.
## Additional information
![image](/uploads/d48f2431dd73d5aed9a03ee3a44f0af5/image.png)
Can be seen on the LayoutInspector (it looks like the custom message bubble is well calculated)
![image](/uploads/b5597af7355d959687e63858e0a785de/image.png)
Can be seen on AndroidStudio DesignMode (prove it's not related to recycling)
![image](/uploads/123eee54106f9960b97d4fcf76d248ba/image.png)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1585Weird left margin on outgoing messages2024-01-30T20:44:10ZPierre NicolasWeird left margin on outgoing messagesBug report form
---------------
## Describe your environment
Please specify the following:
- Jami version: 401
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
![image](/uploads/5bd05e133d0e...Bug report form
---------------
## Describe your environment
Please specify the following:
- Jami version: 401
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
![image](/uploads/5bd05e133d0eb5c1dff178b563de58ca/image.png)
![image](/uploads/bfb4064c96657215e79f0b51e0651c4d/image.png)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1615Call messages: Invalid color for outgoing2024-02-22T20:46:56ZSébastien BlinCall messages: Invalid color for outgoingDiscussed with Charlotte:
Because we can got red on red:
![Screenshot_20240220-130057](/uploads/d21b795596efd269fb25ca763916b91e/Screenshot_20240220-130057.png)
The color of outgoing calls MUST be the same as the reply color (design o...Discussed with Charlotte:
Because we can got red on red:
![Screenshot_20240220-130057](/uploads/d21b795596efd269fb25ca763916b91e/Screenshot_20240220-130057.png)
The color of outgoing calls MUST be the same as the reply color (design on adobe are updated)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1621CallView: Missing icons2024-02-27T13:04:46ZSébastien BlinCallView: Missing icons# Scenario
In a conference, click to make the call buttons disappears, re-click to show it.
# Current result
![1000010657.png](/uploads/03efc8fa0fb18fc26b8db7305a2d1d11/1000010657.png)# Scenario
In a conference, click to make the call buttons disappears, re-click to show it.
# Current result
![1000010657.png](/uploads/03efc8fa0fb18fc26b8db7305a2d1d11/1000010657.png)Vitalii NikitchynVitalii Nikitchynhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1629First back press close conversation instead of settings2024-03-28T00:05:08ZPierre NicolasFirst back press close conversation instead of settings## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Actual result: The conversation is closed at my first click
- Expected result: It sho...## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Actual result: The conversation is closed at my first click
- Expected result: It should close the settings page.
## Additional information
![Screen_recording_20240315_105829](/uploads/58aa1e8b141426437ee7ddfedb775b04/Screen_recording_20240315_105829.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1630Links not clickable2024-03-28T00:05:08ZPierre NicolasLinks not clickable## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Send a link
2. Click on the link
- Actual result: Nothing happens
...## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Send a link
2. Click on the link
- Actual result: Nothing happens
- Expected result: Should open web browser.
## Additional information
![image](/uploads/1f7a069536e03e0f421c4d5e84cdf5e0/image.png)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1632Buttons are missing in CallView when Android interface scaling and font scali...2024-03-19T13:20:57ZPreston LeppanenButtons are missing in CallView when Android interface scaling and font scaling are set to too large## Environment
- Jami version: 20240308-01
- Device model: Xiaomi Mi 10T Lite
- Android version: 12
- What build you are using: F-Droid
## Description
Android has scaling options for interface/font in display settings. When yo...## Environment
- Jami version: 20240308-01
- Device model: Xiaomi Mi 10T Lite
- Android version: 12
- What build you are using: F-Droid
## Description
Android has scaling options for interface/font in display settings. When you change the scaling to the largest, buttons in CallView are no longer visible.
<img src="/uploads/f7b16d478c43666770f03231f58ba0b1/c92cb1f3-fcb3-499d-afb5-ea1f8c33ede0.png" width="200"/>
This can be partially considered an accessibility issue, as users with difficulty reading small texts are more likely to change Android interface/font scaling option.
## Steps to reproduce
How often can you reproduce the bug: always
#### Steps:
1. Open Android Settings app -> Display (Some vendors might have different locations, for example in Accessibility -> Vision -> Display)
2. Find Display scale settings, change it to the largest
3. Find Font scale settings, change it to the largest
4. Open Jami, make a voice/video call
#### Expected result:
Buttons in CallView are visible. I can hang-up the call without using Android notification center.
#### Actual result:
Buttons are missing in CallView, including the hang-up button. I have to resort to notification center to hang-up the call.
## Additional information
Jami has multiple similar issues when display scale is too large (logical size is too small), like https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1226 to name one.