-
for me, on tmobile, MMS works, 100% of the time, just not easily. try using epc.tmobile.com for the MMS APN. (‘group messaging’, which is a purely USA monstrosity, also sort of works. you receive them as individual MMS messages from the sender, which is how it works on android+ios, too. the message app just stitches them together in the ui. making proper group messaging is something we could do ourselves in a messaging app on top of telepathy/commhistory/mms-engine/etc)
-
please update here if at&t works, as that would give options for additional potential devices.
-
as for not giving a shishkabob about the good ol US of A, jolla/jollyboys very explicitly and publicly do not target the US market. you cannot even buy a license to use sailfish unless you lie and say you live in europe. this is very clearly and publicly stated, so it is strange to complain about them spending time developing things to support their business instead of doing the things they explicitly said are not part of their business.
Or iodéOS. It’s made in Europe, but does support users in USA. I believe they have just started employing someone in the US (part-time) to help out in their community forums. I’m in UK, and use iodéOS on my ‘daily driver’, until I can get SailfishOS working well enough to make the switch. MMS seems to work fine, though I don’t use it much.
I like that Shiskabob thing! LOL!! my point was not a complaint, it was more a statement of fact. Which I followed up on with the line…
“To be fair to them, this phone OS is not built for the US market so if you use it. You will just have to roll the dice and get lucky like Teleshoes…”
I will report back for sure and I hope the new guy gives it a try. Just pointing out that results may very.
Following up on your other point about Group Messages… you are so right about it being Awful. My screen shot is showing that very thing… I remember back in the day that Meego (Nokia N9) for sure and maybe Symbian OS (Pureview 808) as well had BCC option with in SMS…you could send text to lots of people without every one getting disturbed when someone wrote back.
Today this group message thing is a real horror show! Credit to the Nokia 909 you could silence group chat… at the cost of having microsoft junk for an OS… Those were my darkest days…
So what do you guys use to send pictures and stuff to each other in the UK?
When I was over there in 2007 and 2008 for a few weeks to visit SW19 and see the sights, the one thing I recall and I found it to be so flipping cool and easy at the time was that you could get access to public wifi almost anywhere and it was free, unlike here in the US at the time, US carriers were scamming people forcing them on data plans and charging extra for it; even claiming you could not buy phone X without the expensive extra data plan Y add on; T-Mobile was the exception at the time I think.
The Other cool thing was that people had duel sim phones. Which was unheard of here in the states. At least by me.
I remember how easy it was to run down by any market and get a GSM sim that allowed me to call home to the US for a very cheap rate. It was so easy there…
But, yeah… what do you guys us for pictures?
Whatsapp, Signal, Telegram etc.
Thanks folks - I think this puts Sailfish in my “monitor for now” category, much to my chagrin. I’m liking iodeOS as my backup plan so far. I’m sad to come to that conclusion, but I appreciate the candid info, and I really do want to keep Sailfish on my watch list over time. If they ever decide to support the US market, I’d be keen to try it out. Best wishes to all!
Depends who I’m sending to. Email, WhatsApp, Messenger, email, Element / Matrix
Can anyone with functioning MMS on T-Mobile share their current MMS settings?
New phone, lots of international travel, I keep losing my TMobile settings and could use a reminder. Am still on Xperia 10III, running 5.0.0.68, T-Mobile USA Magenta.
@hackman238 @teleshoes @808 any ideas?
note: MMS works just fine for sending+receiving, except you have to disconnect from wifi first. my procedure is still:
- turn off wifi
- go to newly sent or received msg and cancel it so it says ‘tap to retry’
- hit retry
- restart mms-engine (this should automatically cancel the msg. if it does not, start over from step two)
- hit retry (succeeds 100% of the time for me when i have good reception)
ip4/6: dual
apn: epc.tmobile.com
mmsc: http://mms.msg.eng.t-mobile.com/mms/wapenc
internet:
Name: T-Mobile
Type: internet
Active: true
Protocol: ip
AccessPointName: fast.t-mobile.com
AuthenticationMethod: none
Username:
Password:
Settings: [dict entry(
string "Interface"
variant string "rmnet_data3"
)
dict entry(
string "Method"
variant string "static"
)
dict entry(
string "Address"
variant string "192.0.0.2"
)
dict entry(
string "Netmask"
variant string "255.255.255.224"
)
dict entry(
string "Gateway"
variant string "192.0.0.1"
)
dict entry(
string "DomainNameServers"
variant array [
string "192.0.0.1"]
IPv6.Settings: []
mms:
Name: T-Mobile MMS
Type: mms
Active: false
Protocol: dual
AccessPointName: epc.tmobile.com
AuthenticationMethod: none
Settings: []
IPv6.Settings: []
MessageCenter: http://mms.msg.eng.t-mobile.com/mms/wapenc
Why not GrapheneOS? Seems like a mainstream alternative to SFOS that is free from corp-y spyware.
Has to be used with Google hardware.
only runs on pixels, based on android, i don’t touch googly things. sailfish has a longer history with its origins in nokia and linux first open os.
how are you restarting the mms engine?
Edit: Figured it out - pkill mms-engine.
It’s still not working though, and I can’t figure out why. The MMS log shows it isn’t even opening a connection and it fails repeatedly. Will try to post the logs.
yep, that is how i kill mms-engine. i have double-press-camera-button tied to do just that with sf-button-monitor.
my internet settings are ipv4 only, and fast.t-mobile.com, and my MMS settings are epc.tmobile.com and ipv4+ipv6. no other combination works
it sounds like you may be having dns trouble. try pinging mms.msg.eng.t-mobile.com and pasting the ip address you get into the mmsc field (e.g.: http://10.188.239.161/mms/wapenc works for me right now) and checking if that fixes it. if so, you will need to put the cname back and fix your dns problem.
oh! one more thing. set the max msg size to Large. XtraLarge fails every time
Thank you! That worked. I had to try it a few times but clearly the mms.msg.eng…address was not resolving to the correct IP. Ping from su at command line and repeated pkill msg-engine worked in some combination.
There’s got to be a way to make this easier on us. Did you post your script somewhere for the double tap pkill? or maybe we need a Nofono app for Msg-Engine .. hm…
cool. my script for the button shortcuts:
its just a single perl script and you have to run it as root since it reads raw input. the config file is fairly straightforward to make. i never got around to wrapping the script in a user friendly app. (also, if you run it with keepalive-tool it will work while the screen is locked. keepalive will also drain about ~4% more battery per day, at least on my 10III)
i use sfbm for a billion things, like restarting ofono, restarting pulse-audio, restarting mms-engine, restarting appsupport, restarting bluetooth, restarting the camera server (it occurs to me that sailfish basically doesnt work), and also toggling the torch and pause/next/prev mediaplayer.
btw, hardcoding an IP is not a permanent solution. at least for me, it will stop working after a few days (presumably tmobile shuts down some servers or reassigns IP addresses occasionally)
you should try to figure out why you’re having resolv issues. maybe try removing dnsmasq or configuring it or installing it? as with any connectivity issue, if its not dns, keep looking until you figure out it actually was dns.
This seems to work with this latest update and even with red pocket. I am using this setting vs the red pocket settings…. for their GSM-T
Thanks