View Single Post
Posts: 547 | Thanked: 1,383 times | Joined on Sep 2009 @ Stockholm, Sweden
#474
Originally Posted by benaranguren View Post
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?
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
__________________

Problem with fMMS? Run in x-terminal: cp /tmp/fmms.log /home/user/MyDocs/
After that you'll see fmms.log in filemanager or when you connect the device to your desktop as a mass storage device.
E-mail the log to me, if you don't have the email address, drop me a PM. Thanks!

fMMS - MMS for your N900
fAPN - GUI for adding a new GPRS APN
If you like this post, don't be shy to thank me -->