jami-client-android issueshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues2024-03-28T00:05:08Zhttps://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/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/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/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/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/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.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/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/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/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/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/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/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/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/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/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/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/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/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-running