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/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/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/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/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/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.