jami-client-android issueshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues2023-11-03T21:19:21Zhttps://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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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 Store