MMS Receiving not working with non signal users #8571
Comments
|
Looks like we're having trouble establishing an MMS connection: 2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: null
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: java.io.FileNotFoundException: open failed: ENOENT (No such file or directory)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at android.os.ParcelFileDescriptor.openInternal(ParcelFileDescriptor.java:313)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at android.os.ParcelFileDescriptor.open(ParcelFileDescriptor.java:211)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at org.thoughtcrime.securesms.providers.MmsBodyProvider.openFile(MmsBodyProvider.java:77)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at android.content.ContentProvider.openAssetFile(ContentProvider.java:1626)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at android.content.ContentProvider.openTypedAssetFile(ContentProvider.java:1806)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at android.content.ContentProvider.openTypedAssetFile(ContentProvider.java:1872)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at android.content.ContentProvider$Transport.openTypedAssetFile(ContentProvider.java:487)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1503)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1340)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at android.content.ContentResolver.openInputStream(ContentResolver.java:1060)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at org.thoughtcrime.securesms.providers.MmsBodyProvider$Pointer.getInputStream(MmsBodyProvider.java:133)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at org.thoughtcrime.securesms.mms.IncomingLollipopMmsConnection.retrieve(IncomingLollipopMmsConnection.java:92)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at org.thoughtcrime.securesms.mms.CompatMmsConnection.retrieve(CompatMmsConnection.java:76)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at org.thoughtcrime.securesms.jobs.MmsDownloadJob.onRun(MmsDownloadJob.java:140)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at org.thoughtcrime.securesms.jobmanager.Job.doWorkInternal(Job.java:111)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at org.thoughtcrime.securesms.jobmanager.Job.doWork(Job.java:64)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at androidx.work.Worker$1.run(Worker.java:84)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
2019-01-28 17:14:07.325 EST W IncomingLollipopMmsConnection: at java.lang.Thread.run(Thread.java:764)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: null
2019-01-28 17:14:07.337 EST W CompatMmsConnection: org.thoughtcrime.securesms.mms.MmsException: java.io.FileNotFoundException: open failed: ENOENT (No such file or directory)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at org.thoughtcrime.securesms.mms.IncomingLollipopMmsConnection.retrieve(IncomingLollipopMmsConnection.java:105)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at org.thoughtcrime.securesms.mms.CompatMmsConnection.retrieve(CompatMmsConnection.java:76)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at org.thoughtcrime.securesms.jobs.MmsDownloadJob.onRun(MmsDownloadJob.java:140)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at org.thoughtcrime.securesms.jobmanager.Job.doWorkInternal(Job.java:111)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at org.thoughtcrime.securesms.jobmanager.Job.doWork(Job.java:64)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at androidx.work.Worker$1.run(Worker.java:84)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at java.lang.Thread.run(Thread.java:764)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: Caused by: java.io.FileNotFoundException: open failed: ENOENT (No such file or directory)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at android.os.ParcelFileDescriptor.openInternal(ParcelFileDescriptor.java:313)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at android.os.ParcelFileDescriptor.open(ParcelFileDescriptor.java:211)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at org.thoughtcrime.securesms.providers.MmsBodyProvider.openFile(MmsBodyProvider.java:77)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at android.content.ContentProvider.openAssetFile(ContentProvider.java:1626)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at android.content.ContentProvider.openTypedAssetFile(ContentProvider.java:1806)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at android.content.ContentProvider.openTypedAssetFile(ContentProvider.java:1872)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at android.content.ContentProvider$Transport.openTypedAssetFile(ContentProvider.java:487)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1503)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1340)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at android.content.ContentResolver.openInputStream(ContentResolver.java:1060)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at org.thoughtcrime.securesms.providers.MmsBodyProvider$Pointer.getInputStream(MmsBodyProvider.java:133)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: at org.thoughtcrime.securesms.mms.IncomingLollipopMmsConnection.retrieve(IncomingLollipopMmsConnection.java:92)
2019-01-28 17:14:07.337 EST W CompatMmsConnection: ... 8 more
2019-01-28 17:14:07.344 EST I CompatMmsConnection: Falling back to receiving via legacy connection
2019-01-28 17:14:07.345 EST W MmsDownloadJob: null
2019-01-28 17:14:07.345 EST W MmsDownloadJob: java.io.IOException: Both lollipop and fallback APIs failed...
2019-01-28 17:14:07.345 EST W MmsDownloadJob: at org.thoughtcrime.securesms.mms.CompatMmsConnection.retrieve(CompatMmsConnection.java:98)
2019-01-28 17:14:07.345 EST W MmsDownloadJob: at org.thoughtcrime.securesms.jobs.MmsDownloadJob.onRun(MmsDownloadJob.java:140)
2019-01-28 17:14:07.345 EST W MmsDownloadJob: at org.thoughtcrime.securesms.jobmanager.Job.doWorkInternal(Job.java:111)
2019-01-28 17:14:07.345 EST W MmsDownloadJob: at org.thoughtcrime.securesms.jobmanager.Job.doWork(Job.java:64)
2019-01-28 17:14:07.345 EST W MmsDownloadJob: at androidx.work.Worker$1.run(Worker.java:84)
2019-01-28 17:14:07.345 EST W MmsDownloadJob: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
2019-01-28 17:14:07.345 EST W MmsDownloadJob: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
2019-01-28 17:14:07.345 EST W MmsDownloadJob: at java.lang.Thread.run(Thread.java:764) |
|
Any ideas on what could cause this/what I could do to fix it? |
|
I don't have any immediate ideas, sorry. Just wanted to note what the issue was for future reference. |
|
I am thinking this may have something to do with using a oneplus phone on Verizon. Its a new CDMAless service they offer. The default APN can't be changed and it disallows any custom apns from being used. This is the apn in use https://photos.app.goo.gl/opc3dtBE3AJ2mgQR8 |
|
I too have this problem and am using a oneplus 6t on the Verizon network. MMS works fine in other apps like the Android "Messages" app. |
|
I'm using a h2o sim on a unlocked sprint device and i've been experiencing the same thing. p.s my APN settings are correct |
|
FWIW, I got someone on Google Hangouts to send an MMS with a PNG image file to my AT&T Samsung S7, Signal 4.33.5, Android 8.0.0, and I seemed to get it OK. |
|
Same problem with Signal 4.33.5 on a Samsung Galaxy S9 and T-Mobile. |
|
Same issue on OnePlus 6T with Verizon |
|
Chiming in here as another OP6T user on Verizon. Then again, back when I had an HTC One M8 user also on Verizon, I remember Signal had the same issue... https://debuglogs.org/433a6f92aad3742488b8f7bf903797e050e975574583daae623d4b523b347393 |
|
Same issue with new phone I got yesterday. Carrier: Verizon Old nexus 6p did not have this issue. Same carrier, same signal version, android 8.1.0. |
|
also seeing this on a OP6T connected to verizon. |
|
Started happening to me sometime after the 19th Feb 2019. Carrier: Optus |
|
Usually if I have wifi connected I get the problem, turning it off fixes it. If I don't have wifi on when I experience the issue, turning Airplane mode on then off gets things working. |
|
Same problem on Android S7. Carrier: vErizon. Signal version 4.38.3. Debug log: https://debuglogs.org/48507d6ad975b3e21fe3674c587f7139f5538e33eb9087e3327664aaf0bb148f |
|
It never worked for me, on many Android versions, including 9. |
|
Same issue on blackberry key2le on verizon. Also a CDMA-less device. |
|
Same issue with OnePlus 7 Pro on Verizon. Able to receive MMS fine using the default app. I love Signal and would love to keep using it as my default app. Interestingly, I am able to send MMS messages, I just cannot receive them. Steps to reproduce:
Expected results: Observed results: Additional info: Debug log: Version: 4.39.4 |
|
Same issue with a Google Pixel 3 (blueline) on AT&T (unlocked). I do find I am able to see the MMS if I reboot the phone. Killing and restarting the Signal App is not enough to do it. Signal 4.39.4 Debug log: This is a fairly big blocker as I receive a number of messages like this every day. |
|
I'm getting this issue too with a Samsung Galaxy S8, latest OS version, and latest signal version. Every time I tap to retry, it fails to download the image. For now, I am using a different messaging app as this is a necessary functionality for me. I would love nothing more than to go back to using Signal! Android Version 9 Debug Log: https://debuglogs.org/41520d64f26830573acdbbb612271fa562a7472ca264bec238ca82048468d1c1 |
|
+1 Signal 4.41.6 |
|
Same issue. OnePlus 7 Pro - Verizon - CDMA Less feature activated. |
|
Exact same issue. One Plus 7 Pro - VZW with CDMA Less enabled. |
|
Same problem here. Oneplus 7 pro, Verizon CDMA-less. Signal to signal works fine... All non signal users "fail to download mms" |
|
I have the same issue. |
|
I also have the same problem on Verizon with the OnePlus 7 Pro. As already stated by others, this phone is registered as a "CDMA-less" device on Verizon's network (specifically, "Feature #83856" has to be added to the line the device is used on).
The behavior is the same regardless of whether I have 'WiFi Calling' compatibility mode turned on/off in the Signal settings and the outcome is also the same regardless of whether I am connected only to WiFi or only to mobile data (LTE). As others have also stated, sending/receiving MMS messages works fine in other SMS applications. I feel absolutely naked when Signal is not set as my default SMS/messaging, so I hope this can be resolved soon. I would be happy to provide packet captures or anything else that would be helpful in fixing the issue so please just let me know (my bootloader is currently locked, so I will need a bit of time to unlock it and gain root, but I would be happy to do so in order to provide any info that would be useful). |
|
Same issues here...
Debug log suggests it's failing to download the MMS |
|
@EngineerFaunce, @agmlego, @porkpuga555, @amcnicho, and all other non-Verizon users: This issue was originally started by a Verizon user whose issue appears to be fixed, and as @mdaniel said earlier, it may be best not to turn this into a catch-all issue. Bugs with different root causes should be filed separately. @thinkbrown: Could you reopen #9153 and include “AT&T” in the title? Thanks! |
|
I've reopened and renamed #9153 |
Are you saying if I ship you a pixel that is hooked up on AT&T you could put some serious effort into fixing this bug? This bug has been killing me for months. I am very willing to send one of the signal maintainers a phone to use and test with until this bug is fixed if that will help. |
|
My parents have complained about this issue. They're each using AT&T with a Galaxy Note 9. This issue should really be reopened. |
|
@tycho @Paulieb81: As noted yesterday, there's an AT&T-specific ticket open: #9153 My question for @Cerberus0 @mdaniel and others: Should we repost our AT&T-specific info from this thread in that one? Would that be useful or would that just add noise? |
@myersjustinc Thank you, I just posted my log on #9173 That one appears to be similar if not the same as #9153 . It's an issue specific to AT&T where this thread got mixed up between Verizon and AT&T. I just wanted to comment back to that dev above on this thread that said he didn't have a phone on AT&T. I'm willing to send him or another dev a phone that is live on my account to get this issue fixed asap. It's been going on for months and is super annoying. |
I am on Verizon and experiencing the issue still. It worked on Android 9 but my phone upgraded to 10 and now MMS is no longer working. Oneplus 6t Verizon Android 9 debug log linked below. 12:07 is when it tried to receive an MMS. https://debuglogs.org/ec22ce6282d942fa0542d00df9e6930bc64b66a5b361511edeb165f8dd0aed3d |
|
@myersjustinc: Sorry, I don't have an answer to that. Linking back to the AT&T-specific comments in this thread may be enough for now. |
|
Can this be re-opened? I am on Verizon and MMS is not working for me. The fix was working when my OnePlus 6t was on Android 9 but it upgraded to 10 and MMS is broken again. Below is my debug log, scrolling down to the bottom at 12:07 is when I tried to receive an MMS. https://debuglogs.org/ec22ce6282d942fa0542d00df9e6930bc64b66a5b361511edeb165f8dd0aed3d |
|
Never did work for me and I am on Verizon.
https://debuglogs.org/ab498087352dd41a07f9e02cfb01ec8e93cb22b2b77195a241f3810cae0135ad
…On November 13, 2019 12:04:34 PM CST, Threefifty ***@***.***> wrote:
@mdaniel
Can this be re-opened? I am on Verizon and MMS is not working for me.
The fix was working when my OnePlus 6t was on Android 9 but it upgraded
to 10 and MMS is broken again. Below is my debug log, scrolling down to
the bottom at 12:07 is when I tried to receive an MMS.
https://debuglogs.org/ec22ce6282d942fa0542d00df9e6930bc64b66a5b361511edeb165f8dd0aed3d
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#8571 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
|
This issue is really intermittent with me and my signal contacts. Sometimes it works, most times we get the MMS error when someone in the group is not a signal user. Has this been picked up in another thread? |
|
I have a Pixel 2 on Verizon and I am unable to receive videos or gifs (a gif comes through as a picture) from non-signal users. Videos simply show a play button and if I take it, it says Error losing video. I used to have no issue with Signal receiving everything! It suddenly stopped working, I think after an Android update. If I use the Android Messages app, I can receive them just fine still, so it's clearly an issue with Signal. If I go to look at the Verizon APN, most fields, including the mms ones, say Not Set, but that are also all dithered; I cannot manually set the fields. https://debuglogs.org/2b1182b3205cc2d67e0e9f876a507398335650baadddc760109839f3a3533ba0 NOTE: received a GIF that came through as a static image at 08:50 |
Bug DescriptionCan confirm that restarting the phone as mentioned in #8571 (comment) temporarily allows me to download MMS messages. Device InfoDevice : Google Pixel XL (marlin) Link to debug loghttps://debuglogs.org/6b9f8c11a8a75412e942d6c9667e6b9bb9425821ea4f06c7aeeb0ae7f60f0e01 |
|
Not sure if this helps to add, but download error also occurs when receiving MMS from Google Voice numbers. |
|
Why has this been closed? Has the Signal project been abandoned? I have a Verizon Android 10 device and an AT&T Android 9 device. Neither one works any longer. |
|
It appears not to be a problem with Signal but 3rd party SMS/MMS apps in general. I was on One plus 6t experiencing the issue and followed this guide after updating to A10. I followed Option A, rebooted to recovery, using TWRP cleared Dalvik/ART cache. Booted up with MMS working in Signal. https://forum.xda-developers.com/oneplus-6t/how-to/issues-sms-mms-oos-10-try-steps-t4004641 To send test MMS messages: Verizon |
|
Why is this closed when it is still an issue!!!!! It has NOTHING to do with what phone or what service you use folks, (software systems engineer and UNIX Network Administrator) it is a bug within the signal app. I use Consumer Cellular with a Nokia and have same issues with MMS and lately it keeps crashing, over and over when I try to use it. Has same issues when I was with Boost with an entirely different Android phone too. Love this app but I am about to delete it entirely. Signal developers need to fix their SH*T!!! |
|
@aeppacher If you are talking about me mentioning my college degrees it was only to display the fact that I am not some 16 year old asshole that has no idea what he is talking about you fucktard. What's the matter, did I make you feel inadequate? |
|
|
|
@hwac121 Open source projects like Signal exist because people want to contribute to something for everyone's benefit. I guess it is a little bit "socialist" in that way. No one here owes you anything, so coming in here screaming about how "Signal developers need to fix their shit!" is totally inappropriate. Bringing politics into it, personal attacks, and suggesting violence are even more so. https://medium.com/@fommil/the-open-source-entitlement-complex-bcb718e2326d |
@hwac121 this kid is 14 |
|
Same problem Galaxy S20 on Mint Mobile (T-mobile MVNO). |
I'm pretty sure this whole issue is dead, but when reporting issues, please use the Debug Logs feature to provide specifics about your situation |
|
Dead? The developer doesn't give a shit is the problem. |
This MAN is 53 and still spry enough to handle the likes of you punk. I bet you voted for Biden... |
|
@aeppacher this asshole hides behind a computer. |
and others
Bug description
Cannot receive MMS from non signal users at all
Steps to reproduce
Attempts to fix
Actual result:
Message just says mms fails to download, click to retry
Expected result:
See the mms
Device info
Device: OnePlus 6T
Android version: 9.0.0
Signal version: 4.32.8
Carrier: Verizon
Link to debug log
https://debuglogs.org/c4b1cd7ad755c63f96d26c173b5324b5d7125dedf51032e09e0e1715e0f52280
The text was updated successfully, but these errors were encountered: