MMS on Xperia 10-3 / Is Porting the N9 Messaging Application Possible?

Hi All,

So has Jolla developers just given up on getting MMS working with Xperia 10-3?
I have the latest paid version of Sailfish OS on the phone and MMS is just a no go!

I guess what I never understood about sailfish is why they don’t have fields for all of the settings. It would seem like they would give us users a better chance at success. It’s like we are starting behind the 8 ball when it comes to SMS and MMS with sailfish.

The Nokia N9 did messaging very well for the most part. Sailfish seems to think messages are not important. Or am I just missing something?

Also is there some other messaging app that you guys are using that will Allow better sms and mms messages?

I find it borderline insane that we can’t attach a picture to a SMS message as well has how sailfish handles group messages.

Has any one tied porting the N9 messaging application to sailfish???

Thanks!

I use Red Pocket / Settings Below

Name: RedPocket Mobile

APN: WHOLESALE
Proxy: Not set
Port: 8080
Username: Not set
Password: Not set
Server: Not set
MMSC: http://wholesale.mmsmvno.com/mms/wapenc
MMS proxy: Not set
MMS port: Not set
MCC: 310
MNC: 280
Authentication Type: None

APN type: Default,mms,supl
APN protocol: IPv4
Bearer: Unspecified

1 Like

Whether your operator has a bearing upon this I know not, but in the UK with 10III I can send from O2 to MVNO of O2 and to EE. I can’t remember whether I had to send an MMS to myself to initiate process in the first place.

Thank you for the reply. I don’t know if red pocket support MMS or not. They say they do but It is not working with the setting they have listed. I looks like we may have reached the point that Sailfish is not going to work well in the US market.

Back a year ago MMS worked (Group messages did not but MMS did… it was slow but worked)

It also worked when I had that X2A or XA2 phone… but struggles with this version of sailfish.

MMS works for me with T-Mobile in USA. No group texts, but otherwise fine.

I think Teleshoes broke the code for me that when an MMS shows it’s perpetually downloading, go into airplane mode and back, then it downloads. Don’t have to do that often.

So not sure your situation is completely a SFOS-fixable problem. Potentially a settings thing, or perhaps carrier doesn’t support SFOS?

2 Likes

what i do now for tmobile usa is:

  1. apn=epc.tmobile.com, protocal=dual
  2. uncheck download-mms-automatically in the messages app settings
  3. when i get an mms pending, i disconnect from wifi (i still cannot get MMS to work while connected to wifi)
  4. i then hit download mms in the messages app. if it gets stuck at ‘downloading’, i run pkill mms-engine (i have triple-click-camera-button set to this shortcut) and then hit retry. i never have to restart mms-engine more than once after disconnecting wifi.

since i started doing it this way a while back, i have not missed a single mms, or been unable to send an mms when i need to. its still such a pain, but its so much better than it was.

2 Likes

Ok doing what you suggested allowed a messgevtoncome throug!

I was not able to send but , yes this worked thank you.

So I will accept this as a small victory for sure. Lol

may I ask what is teleshoes?

Thank you for the help

I don’t even know where to begin. This is ridiculously naive on so many levels.

Like the frontend application has any bearing on this - seriously?!
And even taking a less literal interpretation - a 14 year old telephony stack with 3G as highest supported technology won’t do you much good. Heck; most of what we are running now are probably even improved versions of it.

And where do you suppose you’d get the source code anyway?

As pointed out time and time again, basic mms support is generally a configuration problem now.

1 Like

Thank you. I dont know how to do that command thing but I slso based on your suggestion turned off autobdownloads… I will look into that command thing.

I so wish the devs cared a little bit but I know they dont when it comes to this feature.

I have been here since the first Jolla phone.

my desire NOT to be on apple or google is the only reason I put up with this nonsense.

my mind gets blown that these are the same folks behind The N9 an almost perfect phone…and they release software like sailfish that stuggles with basic phone functions.

it is what it is… One day hoprfully the basics will work and work well.

Thank you again for the suggestions

Hi thank you for your reply, not helpful but thank you all the same.

UI coding is expensive.

Did it ever? SFOS is a European affair. IIRC you can’t even purchase it in the US.

I’m not a fan of customer mentality even with licensed users.

1 Like

For example MCC and MNC are inherent properties of the network and not something you should ever need to input.

There was a time when things worked. And yes being that this phone is designef for the Euro market…being a user outside of that market…you kinda have to roll with the punches.

It becomes a problem when the rolling stops working and you keep getting punched in the face.

The devs talk about how excited the future looks and even built a new magic box thing…but cant take a little time to chat with the users and just acknowledge that messges are not their thing.

Maybe they have and I missed it because I have been heads down trying to get things to work and just missed the memo.

So Im thinking its cheaper to add some fields to a UI va build an AI box thing thst does AI stuff I guess??

Still would not hurt to have them under an advance form…the more info the better chance at trouble shooting.

Today was the first time in months I have been able to get and send an mns.

Thanks to the tip of turning on and off airolane mode…

I would take those fields over jumping through all them hoops…

but a win is a win…

No; they are literally told to your phone by the network - being able to input them would be stupid.

Which tells you that you don’t need those settings.

:person_facepalming:

So what’s your specific problem with MMS? You can’t send or receive?
Mine are 50% automatic, 50% I turn off mobile data, retry send/download and it works. X10 III here

  • attah is perhaps being a bit rude, but what they say is correct. entering those fields would not and could not help you. apn, proxy, and IPv4/6 settings are essential, tho, and finding the right config there for your provider could make all the difference.
  • the problems we have with MMS have nothing to do with the Messages app. (there was an MMS bug in Messages in SFOS 4, caused by sailjail, with not being able to start mms-engine from the messages app when you hit retry, but that was fixed around ~4.4)
  • the main problem with MMS is with the mobile internet connectivity in general, which is bad on Sailfish-X and always has been, and is not at all easy to fix. the telephony stack involves proprietary sony android blobs and i dont particularly understand it. jolla/jollyboys have not particularly been able to do much about it, and probably never will now that they have a non-sony flagship they can control a bit better.
  • for those of us with weird providers (like tmobile USA) that require IPv6 and do network whitelisting and other odd things, sailfish has just never been tested on our providers. these are things that could likely be fixed in mms-engine (not in the messages app)
  • ‘group messaging’ in USA is sooooo dumb+annoying, but i don’t know if folks realize how ubiquitous it is here. even if you’re just visiting, if you know two people, they will probably send you a group MMS. it’s painful to have to read the MMS headers to figure out who the message is actually for; this is something that could be addressed in Messages app even without functional group-MMS support.
  • my app, sf-button-monitor, lets you assign volume/camera/power button presses to commands. double-press volume up turns on my flashlight, and triple-press camera button restarts mms-engine, etc. i rely on it. its not terribly easy to install+configure and it has no GUI, but other folks have gotten it working.
1 Like

Another thing to keep in mind is that Sailfish MMS is unable to do DNS resolution over MMS data connection. It’s doable, it just wasn’t done and it’s fair to assume that it’s never going to be done, since MMS is a dying technology. Which means that in order for MMS to work reliably (without another data connection being active at the same time and providing DNS resolution) the MMS proxy should be there and it should be an IP address.

1 Like

Thanks for the reply

Yes… I started doing that and I was able to send one and receive one, The first time since I had this version of the OS. Thanks to the suggestion of turning stuff off and back on again seems to help.

I wonder if the devs will fix this.

1 Like

A billion thanks. Yes I normally ignore that user name… many negative interactions so I normally just think him for his service and move on.

I will download your app. Thank you for that. And YES group messages are the worse! The phone Pings for 2 days with strangers replying… the Venerable N9 had BCC which was an amazing option.

Thank you for explaining the root issues to the problem… its good to know it’s not the devs fault regarding the matter…

By the way… I have the hardest time with github… I download the program via the green button correct? (code)

Do I need visual studio or something to compile this to make it work for the phone?