Silence-Android issueshttps://git.silence.dev/Silence/Silence-Android/-/issues2020-08-08T20:31:02Zhttps://git.silence.dev/Silence/Silence-Android/-/issues/811feature request: disable mms2020-08-08T20:31:02Znutfeature request: disable mmsMms usually uses system access (uid 1000) to the internet which cannot be well controlled on Android even with root.. it would be nice to disable mms messaging for those who block system access to the internet.
Otherwise there is a mms f...Mms usually uses system access (uid 1000) to the internet which cannot be well controlled on Android even with root.. it would be nice to disable mms messaging for those who block system access to the internet.
Otherwise there is a mms failed notification repeated for days as the mms is attempted to be resent over and over from the server.https://git.silence.dev/Silence/Silence-Android/-/issues/808Too many notifications when opening silence, opening a conversation, and som...2021-06-29T21:50:34ZKlev42Too many notifications when opening silence, opening a conversation, and sometimes randomly### Bug description
Hello! I'm a on a Fairphone 3. I encountered the bug with stable (0.15.16) and 0.16.11-unstable. I have reinstalled stable and the problem is still here sadly. Basically, some unread messages notifications appears to ...### Bug description
Hello! I'm a on a Fairphone 3. I encountered the bug with stable (0.15.16) and 0.16.11-unstable. I have reinstalled stable and the problem is still here sadly. Basically, some unread messages notifications appears to much. Swapped or not, they come again. If I did not read a message, I have the notification for it in three cases.
1. Sometimes when opening silence
2. Always, and this is the most frustrating, when opening any other conversation
3. Randomly (each five or ten minutes), sometimes wrote as "encrypted message" (in french so maybe not exactly that)
Anyway, thank you for your work on this lovely precious app that is Silence. <3
(Also, it's my first bug report)
### How to reproduce
For the part that seems not random and that occurs when opening any other conversation:
- Open silence.
- Send a SMS to yourself, and quit the conversation with yourself before receiving the SMS (also works if someone else send a message and you dont want to mark it a read now)
- Wait for the first normal notification
- Open any other conversation in Silence
**Actual result:** The previous normal notification pops again (maybe it is updated, IDK?) each time you open any other conversation
**Expected result:** The notification should be shown only if new messages arrives. The notification should remains in the notification area of android. The notification should not reappears just because interacting with other conversations
### Device info
- Device: Fairphone 3
- Android version: 9
- Silence version: stable (0.15.16) and 0.16.11-unstable
### Link to debug log
https://paste.silence.dev/menoyujuzohttps://git.silence.dev/Silence/Silence-Android/-/issues/785Some MMS crash silence app2020-08-08T20:48:58ZChenilleSome MMS crash silence app### Bug description
<!--
A detailed description of the bug. More information is better.
Be sure to include any extra information about your device that could be a factor.
Also include the value of any relevant preferences you have set in...### Bug description
<!--
A detailed description of the bug. More information is better.
Be sure to include any extra information about your device that could be a factor.
Also include the value of any relevant preferences you have set in the app.
-->
When I recieve some MMS (not all but this is the second time I see this bug) the app crash. If chose "restart" it's crash again. Restart my phone doesn't change anything.
My only solution : uninstall the app (and loose all datas) and install it again...
### How to reproduce
- I cannot reproduce this bug on demande. This is the second time it's happend.
- 90% of mms work.
- When I reinstall the app the first time, I can receive the MMS wich crash the app if my contact send me it again so it's not the mms format or content
### Screenshots
Usless because I can only screen the "restart" popup.
### Device info
- Device: Blackview BV9500 Pro
- Android version: 8.1
- Silence version: 1.15.16 via F-droid (of course !)
### Link to debug
https://paste.silence.dev/nuyininimiBastien Le Querrecbastien@silence.imBastien Le Querrecbastien@silence.imhttps://git.silence.dev/Silence/Silence-Android/-/issues/660Crash while receiving a SMS during a backup2018-02-27T12:48:21ZBastien Le Querrecbastien@silence.imCrash while receiving a SMS during a backup*Created by: Massedil*
### Bug description
Receiving a SMS during an encrypted backup.
### Device info
- Device: GT-i9305
- Android version: 7.1.2
- Silence version: 0.15.x
### Link to debug log
```
02-25 20:12:59.463 E/...*Created by: Massedil*
### Bug description
Receiving a SMS during an encrypted backup.
### Device info
- Device: GT-i9305
- Android version: 7.1.2
- Silence version: 0.15.x
### Link to debug log
```
02-25 20:12:59.463 E/WindowManager(7304):
02-25 20:12:59.463 E/WindowManager(7304): android.view.WindowLeaked: Activity org.smssecure.smssecure.ImportExportActivity has leaked window DecorView@36268e0[Exportation en cours] that was originally added here
02-25 20:12:59.463 E/WindowManager(7304): at android.view.ViewRootImpl.<init>(ViewRootImpl.java:418)
02-25 20:12:59.463 E/WindowManager(7304): at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:331)
02-25 20:12:59.463 E/WindowManager(7304): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:94)
02-25 20:12:59.463 E/WindowManager(7304): at android.app.Dialog.show(Dialog.java:329)
02-25 20:12:59.463 E/WindowManager(7304): at android.app.ProgressDialog.show(ProgressDialog.java:116)
02-25 20:12:59.463 E/WindowManager(7304): at android.app.ProgressDialog.show(ProgressDialog.java:104)
02-25 20:12:59.463 E/WindowManager(7304): at org.smssecure.smssecure.ImportExportFragment$ExportEncryptedBackupTask.onPreExecute(ImportExportFragment.java:347)
02-25 20:12:59.463 E/WindowManager(7304): at android.os.AsyncTask.executeOnExecutor(AsyncTask.java:620)
02-25 20:12:59.463 E/WindowManager(7304): at android.os.AsyncTask.execute(AsyncTask.java:567)
02-25 20:12:59.463 E/WindowManager(7304): at org.smssecure.smssecure.ImportExportFragment$9.onClick(ImportExportFragment.java:162)
02-25 20:12:59.463 E/WindowManager(7304): at android.support.v7.app.AlertController$ButtonHandler.handleMessage(AlertController.java:161)
02-25 20:12:59.463 E/WindowManager(7304): at android.os.Handler.dispatchMessage(Handler.java:102)
02-25 20:12:59.463 E/WindowManager(7304): at android.os.Looper.loop(Looper.java:154)
02-25 20:12:59.463 E/WindowManager(7304): at android.app.ActivityThread.main(ActivityThread.java:6186)
02-25 20:12:59.463 E/WindowManager(7304): at java.lang.reflect.Method.invoke(Native Method)
02-25 20:12:59.463 E/WindowManager(7304): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
02-25 20:12:59.463 E/WindowManager(7304): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
02-25 20:12:59.626 E/AndroidRuntime(7304): FATAL EXCEPTION: main
02-25 20:12:59.626 E/AndroidRuntime(7304): Process: org.smssecure.smssecure, PID: 7304
02-25 20:12:59.626 E/AndroidRuntime(7304): java.lang.IllegalArgumentException: View=DecorView@36268e0[Exportation en cours] not attached to window manager
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.view.WindowManagerGlobal.findViewLocked(WindowManagerGlobal.java:473)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.view.WindowManagerGlobal.removeView(WindowManagerGlobal.java:382)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.view.WindowManagerImpl.removeViewImmediate(WindowManagerImpl.java:126)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.app.Dialog.dismissDialog(Dialog.java:370)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.app.Dialog.dismiss(Dialog.java:353)
02-25 20:12:59.626 E/AndroidRuntime(7304): at org.smssecure.smssecure.ImportExportFragment$ExportEncryptedBackupTask.onPostExecute(ImportExportFragment.java:371)
02-25 20:12:59.626 E/AndroidRuntime(7304): at org.smssecure.smssecure.ImportExportFragment$ExportEncryptedBackupTask.onPostExecute(ImportExportFragment.java:342)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.os.AsyncTask.finish(AsyncTask.java:667)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.os.AsyncTask.-wrap1(AsyncTask.java)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:684)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.os.Handler.dispatchMessage(Handler.java:102)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.os.Looper.loop(Looper.java:154)
02-25 20:12:59.626 E/AndroidRuntime(7304): at android.app.ActivityThread.main(ActivityThread.java:6186)
02-25 20:12:59.626 E/AndroidRuntime(7304): at java.lang.reflect.Method.invoke(Native Method)
02-25 20:12:59.626 E/AndroidRuntime(7304): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
02-25 20:12:59.626 E/AndroidRuntime(7304): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
```https://git.silence.dev/Silence/Silence-Android/-/issues/624Every time I check the key with QR code, key never match2017-12-03T15:31:41ZBastien Le Querrecbastien@silence.imEvery time I check the key with QR code, key never match*Created by: slegault50*
Hi guys.
Every time Im checking the key of my friends with the QR code scanner. It always says
"Warning, key does not match"
Whats going on?? A bug ? Or a man in the middle ?
Any help will be appreciate.*Created by: slegault50*
Hi guys.
Every time Im checking the key of my friends with the QR code scanner. It always says
"Warning, key does not match"
Whats going on?? A bug ? Or a man in the middle ?
Any help will be appreciate.v0.15Bastien Le Querrecbastien@silence.imBastien Le Querrecbastien@silence.imhttps://git.silence.dev/Silence/Silence-Android/-/issues/544Cannot select audio attachment2018-01-04T19:28:27ZBastien Le Querrecbastien@silence.imCannot select audio attachment*Created by: josephmangmang*
### Bug description
<!--
Cannot long press or select audio attachment
-->
### How to reproduce
-send audio
-long press the audio message
**Actual result:** No effect, still not mark as selected. ...*Created by: josephmangmang*
### Bug description
<!--
Cannot long press or select audio attachment
-->
### How to reproduce
-send audio
-long press the audio message
**Actual result:** No effect, still not mark as selected. cannot delete
**Expected result:** Should be selected
### Device info
- Device: Samsung J5 2016
- Android version: 6.0.0
- Silence version and build ID: 316b9fe
Bastien Le Querrecbastien@silence.imBastien Le Querrecbastien@silence.imhttps://git.silence.dev/Silence/Silence-Android/-/issues/405SMS reply opens a new conversation when the first SMS is sent from Silence2016-07-16T10:42:54ZBastien Le Querrecbastien@silence.imSMS reply opens a new conversation when the first SMS is sent from Silence*Created by: owiuefiweytgt*
To reproduce:
1. Create a new SMS selecting any contact. This creates a new conversation.
2. Send SMS.
3. Reply from contect creates a new conversation while the original conversation only hast the message se...*Created by: owiuefiweytgt*
To reproduce:
1. Create a new SMS selecting any contact. This creates a new conversation.
2. Send SMS.
3. Reply from contect creates a new conversation while the original conversation only hast the message sent on the previous step.
4. If a contact was already secured but the conversation was deleted, the behavior is the same when sending the first message, and Silence will not recognize the keys have been already exchanged and will alert that the secured session has expired.
This has happened to me on all previous versions, now running 0.14.3.
Bastien Le Querrecbastien@silence.imBastien Le Querrecbastien@silence.imhttps://git.silence.dev/Silence/Silence-Android/-/issues/352Recent Apps list disappears2017-02-08T11:01:42ZBastien Le Querrecbastien@silence.imRecent Apps list disappears*Created by: morph44*
I apologize if this has already been addressed here, but I did a preliminary search to see if others had reported a similar bug and hadn't found anything.
When swiping SMSSecure away from the Recent Apps list, the...*Created by: morph44*
I apologize if this has already been addressed here, but I did a preliminary search to see if others had reported a similar bug and hadn't found anything.
When swiping SMSSecure away from the Recent Apps list, the list disappears/closes out and I'm brought to the home screen.
If I then reopen the Recent Apps list again, I can see that SMSSecure was successfully discarded and other apps in the list are left alone.
This occurs on my previous phone (Samsung Galaxy S4 - Verizon, Android 5.0.1), current phone (Nexus 6P - Google Fi, Android 6.0.1), as well as my friend's phone (Neuxs 5 - T-Mobile, Android 6.0.1) and has done so for about six months, since we first started using SMSSecure.
I've tried enabling/disabling the "Screen Security" feature under Settings > Privacy to no avail.
Is this a known bug and are there any plans to fix it?
Thanks!
https://git.silence.dev/Silence/Silence-Android/-/issues/321SMSSecure does not send confirmation to server upon successfully receiving MMS2018-09-21T17:39:01ZBastien Le Querrecbastien@silence.imSMSSecure does not send confirmation to server upon successfully receiving MMS*Created by: Olangu*
I had a issue where my multimedia messages came in a second time after a few days, so I asked my provider to check the issue.
Turns out that my phone (SMSSecure) does not confirm with the server that it have receiv...*Created by: Olangu*
I had a issue where my multimedia messages came in a second time after a few days, so I asked my provider to check the issue.
Turns out that my phone (SMSSecure) does not confirm with the server that it have received the MMS, and that my providers send out the MMS a second time when it reaches its EOL on server.
Bastien Le Querrecbastien@silence.imBastien Le Querrecbastien@silence.imhttps://git.silence.dev/Silence/Silence-Android/-/issues/264Sending images failed2015-10-15T14:07:23ZBastien Le Querrecbastien@silence.imSending images failed*Created by: 1911hajduk*
fresh smssecure 0.12.3 install on 2 phones, and trying to send images vice versa and it wont work.
I added a dbug:
https://gist.github.com/6b2f76f9f9dcad2e3767
*Created by: 1911hajduk*
fresh smssecure 0.12.3 install on 2 phones, and trying to send images vice versa and it wont work.
I added a dbug:
https://gist.github.com/6b2f76f9f9dcad2e3767
Bastien Le Querrecbastien@silence.imBastien Le Querrecbastien@silence.imhttps://git.silence.dev/Silence/Silence-Android/-/issues/222can't retreive MMS's anymore with the latest version(s)2015-12-07T09:30:58ZBastien Le Querrecbastien@silence.imcan't retreive MMS's anymore with the latest version(s)*Created by: bungabunga*
retrieving MMS messages doesn't work anymore for me and my friends with latest version(s) of SMSsecure. it used to work fine by default. sending is still possible.
https://gist.github.com/7e7b90bd43d4e2026bc1
*Created by: bungabunga*
retrieving MMS messages doesn't work anymore for me and my friends with latest version(s) of SMSsecure. it used to work fine by default. sending is still possible.
https://gist.github.com/7e7b90bd43d4e2026bc1
Bastien Le Querrecbastien@silence.imBastien Le Querrecbastien@silence.imhttps://git.silence.dev/Silence/Silence-Android/-/issues/184group messages aren't backed up during Export (likely because they're all MMS)2019-11-23T11:52:37ZBastien Le Querrecbastien@silence.imgroup messages aren't backed up during Export (likely because they're all MMS)*Created by: bobodod*
To reproduce:
1. Create a group and send them a couple messages.
2. Navigate to Menu → Import / export → Export tab → Export plaintext backup
3. Evaluate the end of the XML file exported to the root of the SD card ...*Created by: bobodod*
To reproduce:
1. Create a group and send them a couple messages.
2. Navigate to Menu → Import / export → Export tab → Export plaintext backup
3. Evaluate the end of the XML file exported to the root of the SD card and gape with minimal horror at the missing messages.
It's probable that this is because MMS, even plain text ones, aren't backed up and group messages are all MMS.
https://git.silence.dev/Silence/Silence-Android/-/issues/105Change Password Style 2015-04-15T11:09:43ZBastien Le Querrecbastien@silence.imChange Password Style *Created by: D0L0S*
Android Version: 5.1
App Version: 0.5.4
Discription:
When setting an application password with the dark theme applied the change password screen maintains the default blue and white theme.
Steps:
Settings -> Appear...*Created by: D0L0S*
Android Version: 5.1
App Version: 0.5.4
Discription:
When setting an application password with the dark theme applied the change password screen maintains the default blue and white theme.
Steps:
Settings -> Appearance -> Theme
Select Dark
App protection -> Enable passphrase
Default theme is displayed
https://git.silence.dev/Silence/Silence-Android/-/issues/98Prevent scrambled SMS: Indicate maximum size of message2016-01-17T04:34:58ZBastien Le Querrecbastien@silence.imPrevent scrambled SMS: Indicate maximum size of message*Created by: SecUpwN*
Hi there! I feel a little strange opening yet another Issue on your wonderful fork, but I just cannot help it since this is something TextSecure lacks as well and has always bugged the hell outa me:
When sending a...*Created by: SecUpwN*
Hi there! I feel a little strange opening yet another Issue on your wonderful fork, but I just cannot help it since this is something TextSecure lacks as well and has always bugged the hell outa me:
When sending a large message, which is longer than 3+ SMS (one SMS contains 160 characters), SMSSecure and TextSecure is sending out the huge message without any complaint and also indicating that it was delivered, but the receiver gets multiple falsely encrypted messages, while not even one sentence is readable. Note: I cannot specify the "minimal" number of SMS that have to be reached until the huge SMS message gets wrongly encrypted (probably needs testing). I also guess that mismatching encryption keys between messages is likely the result of perfect forward secrecy and thus "perfectly normal". But in my eyes TextSecure and SMSSecure should show (and possibly prevent any further typing) when the maximum size of a correctly encrypted message is reached. This would prevent the sender thinking that the monster SMS has been delivered, while the receiver only gets "scrambled eggs".
https://git.silence.dev/Silence/Silence-Android/-/issues/68Lollipop cannot receive MMS when wifi is ON2016-12-16T07:57:15ZBastien Le Querrecbastien@silence.imLollipop cannot receive MMS when wifi is ON*Created by: ghost*
WIFI ON: "MMS Download failed!"
![screenshot_2015 wifi](https://cloud.githubusercontent.com/assets/9587027/6995738/6ecc5854-db10-11e4-9633-d2633a417bcf.png)
WIFI OFF: Receive OK.
![screenshot_2015-data](https://cl...*Created by: ghost*
WIFI ON: "MMS Download failed!"
![screenshot_2015 wifi](https://cloud.githubusercontent.com/assets/9587027/6995738/6ecc5854-db10-11e4-9633-d2633a417bcf.png)
WIFI OFF: Receive OK.
![screenshot_2015-data](https://cloud.githubusercontent.com/assets/9587027/6995739/76f45716-db10-11e4-9a15-768a995044a0.jpg)