Hacker News Reader

Comment by latortuga | Hacker News Reader

I used TextSecure as my text client exclusively for about the last 6 months and it worked great except for 3 things: group messages and MMS. Something changed recently that prevented any MMS from showing up and it kept offering for me to configure the proxy settings. I looked briefly for the correct settings but there don't seem to be any for Verizon on their list. Group messages just didn't seem to work the way the do in the normal Android client. Texting worked flawlessly though it's sort of chicken and egg - no one I know used it so none of my communication was encrypted in transit.

Oh and the third thing: my SO thought I was borderline paranoid/crazy/hiding something for even installing it.

View on HN

FYI, from another Verizon user: https://github.com/WhisperSystems/TextSecure/issues/467

Looks like we need to add some new MCC/MNC values to the defaults for that MMSC. Group messages use MMS, so hopefully this gets you down to one problem (paranoid). =)

I really appreciate the response, Moxie. I admire your work and your privacy advocacy and I downloaded TextSecure after seeing it here and associated with your name. I'll take another look and see if that link can solve my (technical) issues.

Just noting that when Google switched to using the Hangout app for SMS/MMS messaging, it broke MMS for me - so that problem is hardly unique to TextSecure

I understand HN is not tech support but...

TextSecure crashed on receiving MMS on my Nexus 5 on T-mobile's value plans(I mention their value plan because it works slightly differently than their regular ones). After I manually configured the MMSC it stopped crashing and displays MMS correctly.

This was my exact usage problem with it as well. It was seamless in receiving standard SMS, but MMS & group messages simply did not come through, though I would be alerted to receiving them.

I gave up on TextSecure because of the flaw. I'll pick it back up if there's a fix.

There was a period of time where Android made a sudden unannounced change to an app's ability to access APN settings on the device, which prevented MMS from working.

We now prompt users to configure their MMSC for their carrier if APN details are not available from the device.

If you have problems like this in the future and would like to help the project get better, please file the bugs you encounter on the GitHub issue tracker so that we can get the information we need to fix them for everyone.

Reply on news.ycombinator.com