I do have the correct MMS settings. I have checked them several times. The problems I’m having are identical to @808 's and @WedgeStratos described in this thread. Fails to download, have to toggle off wifi and in and out of airplane mode several times, sometimes reset the phone, and still sometimes I just can’t get an MMS. In a world where I’m often cc’d on group texts and iPhones default simple messages to MMS formats, this is a lot of missed messages…
Not complaining, just wondering where we’re at with a fix.
I’m on TMobile, but happy to switch if that solves the problem.
Also doing a deep dive on VoLTE stuff.
1 Like
Have you tried canceling it and restarting the download. That used to work for me when mine was working wonky (since resolved). And I had to have wifi off for it to work.
I also found multiple settings for T-mobile (now on AT&T reseller), and tinkering with those also helped.
US user here. Putting it out there incase it’s not known by others. Slapping a data only SIM from TMobile, Mint, RedPocket or USMobile combined with S1P or Grandstream Wave (android) works pretty well. SMS/MMS work with Granstream Wave. I’ve made several improvements to make S1P more reliable and feature complete (daemon from boot, ring/answer over lockscreen, SMS, proper contacts), but without the sources it’s impossible for me to implement SSL. If anyone wants to get after unmaintained to release it, I’d be happy to share my changes. The VoIP provider I’ve been using with good results is voip.ms (https://voip.ms/en/invite/MzMwNzMz if you want to use my referral code). Using this approach on 2 x XA2 Ultra (non-technical family) and 10 II (personal/development).
3 Likes
@svalmont I’m happy to hear more about the multiple TMobile settings you tried, in case I’m missing anything. I typically cancel and restart download, or go airplane mode and reconnect, or reset entirely.
Hi @hackman238 and welcome! Yes, many of the users above are also working with data-only SIMs and SIP apps too. I’d prefer to do that only as a last resort … maybe come July 22…
I put my solution in the forum when I found it. More or less, I looked up multiple sites what the settings were and tried different ones until it ended up working out. I don’t have T-mobile anymore, so I can’t just look up my settings for you.
Yeah its a pain… so here is a screen shot of my setting…im.on RedPockets…I was on TMobile.the I went to mint and now on RedPocket… i typed and retyped these same settings in over and over… I tried so many thing short of getting into an airplane (I’m a low time. pilot) and dropping this sumbish out the window from.altitude into a volcano… but then.I remembered… its not the phone… its the poorly written and tested software. I would add some snaps of messages that still have notnot downloaded but the message app crashes if you close it so I have to reboot this flipping thing before I can open the message app again.
I rebooted…Jolla Devs…the thing has been spinning since January… what is wrong with this os??? Honestly.
Just remember to stay the minimum requested 2,000 ft above the surface if the volcano is located on National Park Service ground 
3 Likes
I set my protocol to IP, not IPv6. That helped me.
3 Likes
I think IPv6 is somewhat broken on sailfishos anyways…
bro its all broken… they should call it brokefish…
But Im going to stick with it!
1 Like
hmmm interesting development.
I did contact Sony support shortly after they released this: Status of Xperia Phones after 3G Shutdown (3G Sunset) by US Wireless Carriers | Sony USA to ask if they would still support the Xperia 10 i3113 and their answer was yes. But still, it looks like the VoLTE rollout from Jolla will affect the 64bit machines, which get terrible signal, and not the 32bit one that will still have some semblance of service post 3Gpocalypse. At last check TMobile, Mint, ATT and other subsidiaries flat out labeled my 10ii as incompatible with their network, and the best I got with an IMEI for a potential 10iii was “partially compatible”.
Apart that one could always change its imei to a more compatible one, I really wonder up to which point a compatible imei would really be enforced/ incompatible phones would be excluded from the network? Exclusion would not only limit the number of available devices but also hinder e.g. travellers to roam on the network, while these are always very welcome since roaming costs are a very welcome extra charge…
I had to give in and stop using the XA2 and Sailfish - The MMS issues, memory management, the low storage (which isn’t helped by only having 18 of the 29GB on the device) and the degrading battery life started to grate on me. I’m a Mint user currently using the 10iii (XQ-BT52) and it’s been perfectly fine despite the middling compatibility and missing bands. At least where I live, LTE has been consistent (often I’m getting “LTE+” whatever that is) and Fast.com reports typically solid 35MB/s down speeds. I haven’t had a chance to see how 5G should perform, I believe I have to be closer to my city’s downtown for it, but with how this phone’s performing right now, I have no doubt that it’ll be fantastic from a hardware level.
I guess much like Blackberry 10, my time with an alternative OS is over. It was a fun ride at least.
1 Like
I am glad to hear that about the 10iii! Maybe once sailfish incorporates a VoLTE toggle that will be a real option….
1 Like
The XA2 hardware is a bit outdated already but I think the free space issue could easily be overcome by changing partitioning and does not appear any longer in fresh installs( newer had problems with my 10ii). I guess the MMS thing is something bothering only a vast minority of users (if at all) and according to some other thread still some patches are delivered. The hardware experience sounds like the x10iii might become the future Sailfish-device of choice! Congrats for buying!
I was about to post something along those lines!
I assume that with the next release, with 10iii being supported, hopefully with VoLTE working, and hopefully we can start buying SFX in the US~! Up until now I was considering porting Hardware Adoption of my current device, but sadly that has had some hiccups
1 Like
I want to set the expectation here- devices in the USA must be certified to register to IMS and use VoLTE. This is why VoLTE won’t work on the 10 iii under Android on a USA carrier right now. It could change down the line or perhaps a workaround found. I do know of “ways” to make it work. They are not technically violations of any specific law in the USA, but they are highly likely to garner users’ negative attention from the digital authorities here- namely the NSA.
One addendum- if anyone finds a carrier in the USA that does consider the 10 ii or 10 iii VoLTE certified, please let me know. I haven’t found any, but that’s not to say there are none or that the details I have are exclusively correct.
4 Likes
I’ve been told by several carriers in the USA they won’t kick devices considered incompatible from the network if they’re using a data-only SIM and don’t rely on 3G/UMTS/EvDO for data. No guarantees, but the message has been consistent.
Please don’t alter your IMEI. While it’s not a violation of any specific USA law I can identify it will attract the attention of authorities if not carefully executed. I do think at some point the 10 ii and 10 iii will be able to register to USA carrier IMS services for VoLTE after some of the cut over craziness calms down. There’s no technical reason they cannot work [in Android].
4 Likes
what Mms patches. Can you point out where to get these patches? Thanks