frals | # 471 | 2010-01-24, 00:26 | Report

Yes, according to Nokias UAProf document associated with the N95 User-Agent string. See http://nds1.nds.nokia.com/uaprof/NN95-1r100.xml

Yes, obviously your carrier ignores x-wap-profile and does not care what the standard says about content-adaption (the way I've understood the purpose of x-wap-profile anyway, but I've been wrong before :P). I'm afraid the best workaround so far is sending N95 UA, which gives you 1024x768 and 150kb pictures - if you have any idea how to solve this please do share.

Regarding your problem with senders looking like they come from the same person, it's probably because there is no code at all dealing with e-mail addresses yet, and the phone matching algorithm is just a quick placeholder for now. It's on the todo


Thanks for testing.

---

Last edited by frals; 2010-01-24 at 00:37.

HeinzHarald | # 472 | 2010-01-24, 01:45 | Report

Don't know if this has been mentioned and if it's network specific (OS specific perhaps?), but I wanted to say ending the proxy in .030 as it was reported in my old phone didn't work with fMMS until I changed it to .30 (fMMS just sat there and after a long while delivered an error message). Now it works like a charm.

Oh and thanks for a great app!

---

Last edited by HeinzHarald; 2010-01-24 at 01:52.

benaranguren | # 473 | 2010-01-24, 01:57 | Report

Just a quick thought. What if fmms uses a new and unique User-Agent? Wouldn't that force some carriers to respect x-wap-profile value since they won't have a clue what the target device's capabilities are?

Maybe add a way in fmms to set different user-agent and profile?

---

Last edited by benaranguren; 2010-01-24 at 01:59.

frals | # 474 | 2010-01-24, 02:02 | Report

Been there, done that ;-)

Setting a unique User-Agent made TMO go stoneage on us and resize to min. allowed size, even if profile header was set like it should be The thing is, it seems only TMO USA has this problem (don't think anyone outside TMO USA has encountered this?), I see a few hits on my webserver from MMSCs that actually do respect the x-wap-profile header and fetches the UAProf document

dinz | # 475 | 2010-01-24, 03:36 | Report

i din't set any proxy....

bullion87 | # 476 | 2010-01-24, 05:30 | Report

Hello Frals, here is my new observation, If the picture is sent as a horizontal picture then it will arrive as a thumbnail, however, if the picture is sent as vertical, then it will be alrite. Not sure why though

bullion87 | # 477 | 2010-01-24, 06:15 | Report

Dear Frals, another observation, it seems that I was only able received 1 picture full size that I mention before. Later on, everything is thumbnail. I am using 0.2.8

synplex | # 478 | 2010-01-24, 12:06 | Report

So can anyone that has FMMS fully working with TMobile USA please post their info/setup (APN).
I can receive MMS, but not send them. And when I receive them their small thumbnails. I just really need to be able to send them.

Sorry if this has been answered already.
Thanks

sygys | # 479 | 2010-01-24, 12:08 | Report

Cant there be made a plugin? so that you receive them in the conversation menu?

ohwut | # 480 | 2010-01-24, 12:21 | Report

I've noticed that coming from T-Mobile USA I'm unable to send any MMS to a user on Verizon Wireless. Every other carrier they go through fine, tested it out on 4 different users in different regions of the US(Arizona, Florida, New Mexico, North Carolina) over the past 2 weeks and none of them received it, or even a notification. They receive them just fine if they're sent from my BlackBerries, HTC Win-Mo phones, or the Nexus One so I know it's a fMMS issue somewhere. No idea what it would be though.