MMS messaging not working

[killerxx2]

i am running wm6 most beautiful addition on my g4 cid locked device and i cant get the mms to work if by any chance anyone has figure this out on t mobile USA it would be greatly appreciated..or if they could re right the guide that t mobile has that would be fantastic.


http://tmobileus.wdsglobal.com/mms?step=services.vm&contractId=235&countryId=37&networkId=90&bearerId=5&phoneId=1184&mobileNumber=&captchaEnabled=true&service=mms
thats the t-mobile guide

thanks in advance

[sgtcasey]

The T-Mobile guide is written for a device still using a T-Mobile ROM which is why it doesn't seem to make sense when you're using WM6.

I have an MDA and I've also had issues getting MMS to work under any WM6 ROM I've tried so far.

If anyone has any suggestions... :)

Dave

[bigrob119]

The TMobile Settings Guide in that link WILL still work. I am running Faria's WM6 ROM (quite happily I might add), just did the TMo settings myself on my CID unlocked TMo MDA about half an hour ago and MMS is now working again.

Just do EXACTLY what the directions say and your MMS will work again.

[Ranger666]

I did EXACTLY word for word and my MMS still not working...it starts to send then just dies out....and msg is moved to the drafts folder.

[bigrob119]

I did EXACTLY word for word and my MMS still not working...it starts to send then just dies out....and msg is moved to the drafts folder.

I have to ask since I had the same problem at first...

Did you try a manual power cycle (not pressing the soft reset button on the side or a software soft reset but actually pressing the power button for 3 seconds, letting it sit off for a few seconds and turning it back on)?

I found that with the Faria ROM, to get some changes to "stick" you have to power cycle your MDA after each and every change. Takes a while and it's a PITA, but it has solved 99% of the problems that I was having with the ROM.

If you HAVE done that already, then I dunno what to tell you guys...my condolences? :( JK but there has to be a permanent fix or a CAB out there somewhere...

[Ranger666]

Well, I hadn't tried the full reset was just doing a soft reset. Tried it and still same. I don't know what the issue is....lot of people are not able to send MMS. Text messaging works fine. I'll just keep trying to mess with it and hope someone finds a solution before I do.

[demontefixo]

Well, I hadn't tried the full reset was just doing a soft reset. Tried it and still same. I don't know what the issue is....lot of people are not able to send MMS. Text messaging works fine. I'll just keep trying to mess with it and hope someone finds a solution before I do.I finally remembered what the "deal" is... the MMS instructions for TMobile has a minor error:216.155.165.050 should be:216.155.165.50

Note the lack of the zero before the .50

Give it a whirl, let me know.

--M

PS I added it to the Wiki for the next time I forget how to fix it.

[sgtcasey]

Hmmm... I'll have to give that a shot. I've been using the 050 per the steps and all it would do when I tried to send a test MMS was move the message to the drafts folder and never send it.

I've got the normal T-Mobile ROM on my MDA right now and I plan on flashing it over to the Faria ROM later on today.

I'll post the results when I'm able to test it. :)

Dave

[marscandybars]

I agree. I ran into the same problem with my very first Crossbow rom. Changing the server gateway is 216.155.165.50

NOTE it ends in .50 not .050 . This worked for me


BIG problem with crossbow roms right now: Receiving pictures messages are VERY small. They will be downsized to 160x120 and less than 15kb. 'til this day i still haven't figured out how to fix that. At first i thought it was the Arcsoft registry settings, but i have meddled through the arcsoft registry settings so many times. I think there is something else in the crossbow roms that is capping the receiving size. I have set all receiving registry settings to receive pictures in their original form or 640x480, but they still keep coming at 160x120. You can test this by sending a picture to yourself (note its size before sending it) or having someone else send you a picture. Good luck!

[Ranger666]

It worked like a charm. Sweeeet! Thanks for the help. I didn't even think about the server being wrong, I figured T-Mobile knew what they were doing. Guess not. XDA Dev got 'em beat.

[sgtcasey]

Yep, using .50 instead of .050 worked fine for me here, too. Thanks!

Dave

[johnnylavah]

are you able to send and receive? i am only able to receive. i have followed the instructions and am still not ablt to send. i am using the t-zones plan with proxy...

[sgtcasey]

are you able to send and receive? i am only able to receive. i have followed the instructions and am still not ablt to send. i am using the t-zones plan with proxy...

I sent to my old Verizon phone (which is still working until the 23rd so I've been using it as a test phone lately) and it worked fine. I sent a picture I took with the Verizon phone to the MDA and it received. However, I did get the 160x220 or whatever size it is on the MDA. It works, though. I'll worry about other issues later.

Something I am noticing now is that whenever I connect using IE, it uses the MMS profile I set up instead of the GRPS one I set up first. It works, so no big deal. I guess. :P

Dave

[marscandybars]

I sent to my old Verizon phone (which is still working until the 23rd so I've been using it as a test phone lately) and it worked fine. I sent a picture I took with the Verizon phone to the MDA and it received. However, I did get the 160x220 or whatever size it is on the MDA. It works, though. I'll worry about other issues later.

Something I am noticing now is that whenever I connect using IE, it uses the MMS profile I set up instead of the GRPS one I set up first. It works, so no big deal. I guess. :P

Dave



Outgoing files from the MDA will be in full size. But for some reason, with the new crossbow roms, all INCOMING pictures will the thumbnail size (160x120). This is NOT normal. If you use the standard roms, or Xelecins Custom 2.26 rom, you will notice that you get the full size image. I have been trying to find a fix for this ever since the first cooked crossbow WM6 rom... its annoying :(

[falconeyez]

My friend just sent me a picture through MMS and it cam through at 320x240. How is this possible you ask? Under your MMS configuration, >preferences
There is a drop down menu that allows you to choose the photo resolution. Just pick "orignal" instead of the default setting

[allynm]

It worked like a charm. Sweeeet! Thanks for the help. I didn't even think about the server being wrong, I figured T-Mobile knew what they were doing. Guess not. XDA Dev got 'em beat.

ok, so i set this up on my TYTN (with WM6, thx to this sweet forum).
a buddy with a moto q on sprint tried to send me a pic, but it came as a text with a http link (to sprintpcs.com). i suspect that issue was on his end.

heres the kicker - i hit the link, and IE opened, and went to the page, even though I had wlan off (i.e. it used the picturemessage connection to get there)! i tried going to google, and that worked as well! is this some form of t-zones or tmobileweb? i only have the 1000 min family plan, and i don't have any internet services added to my account. could this actually be some form of simple free proxy-based web browsing?
...or am I going to get bent over on my next bill for some previously unknown pay-by-the-kb-or-minute fees...

please advise.
Al

[marscandybars]

My friend just sent me a picture through MMS and it cam through at 320x240. How is this possible you ask? Under your MMS configuration, >preferences
There is a drop down menu that allows you to choose the photo resolution. Just pick "orignal" instead of the default setting


Mine has been set to original and on occasion 640x480. It makes no difference. They all come in at 160x120 or smaller. Are you sure u're using crossbow WM6? Cuz so far, i've been hearing other ppl with the same problem. We all have our settings at "Original"

[mfrazzz]

All pics coming in to me with MBE, mUn, and Faria WM6 roms come to me 160x120 (and I've had a couple come in smaller than that even). I'm set to Original, and I've even changed it to other settings and back again. Can't seem to figure out why this is happening.

[Ranger666]

a buddy with a moto q on sprint tried to send me a pic, but it came as a text with a http link (to sprintpcs.com). i suspect that issue was on his end.

please advise.
Al

That is a sprint issue...my brother has sprint also.


...or am I going to get bent over on my next bill for some previously unknown pay-by-the-kb-or-minute fees...

please advise.
Al

Unfortunately, you will get charged for the per minute data usage.

[allynm]

Unfortunately, you will get charged for the per minute data usage.

Thanks for the reply. Does the per minute data usage work the same as the voice usage (i.e. if I have unlimited nights and weekends for voice, would the same apply to data)? Or is this a seperate rate? Is there a page detailing this at the T-Mobile site somewhere? I searched for the better part of an hour and could find no specifics.

Thanks in advance.
Al

[dmfbm]

they will not charge you per minute. also its not the wm6 rom its the 3.0.1.xx arcsoft. if you upgrade to the MB crossbow then the arcsoft will be 3.5 and you will no longer have the issue.

[falconeyez]

Mine has been set to original and on occasion 640x480. It makes no difference. They all come in at 160x120 or smaller. Are you sure u're using crossbow WM6? Cuz so far, i've been hearing other ppl with the same problem. We all have our settings at "Original"

Yup, I'm using MB WM6 on T-Mobile

[marscandybars]

Yup, I'm using MB WM6 on T-Mobile

The Very first corssbow rom i tried was the MB version. I still got my pix at 160x120 or smaller, so i dunno why. My settigns are set at "original" but im still getting the same 'ol small pix... *sigh*

[falconeyez]

The Very first corssbow rom i tried was the MB version. I still got my pix at 160x120 or smaller, so i dunno why. My settigns are set at "original" but im still getting the same 'ol small pix... *sigh*

And your MMS Composer Version was 3.5.1.17? Weird.

[big000000]

I agree. I ran into the same problem with my very first Crossbow rom. Changing the server gateway is 216.155.165.50

NOTE it ends in .50 not .050 . This worked for me


BIG problem with crossbow roms right now: Receiving pictures messages are VERY small. They will be downsized to 160x120 and less than 15kb. 'til this day i still haven't figured out how to fix that. At first i thought it was the Arcsoft registry settings, but i have meddled through the arcsoft registry settings so many times. I think there is something else in the crossbow roms that is capping the receiving size. I have set all receiving registry settings to receive pictures in their original form or 640x480, but they still keep coming at 160x120. You can test this by sending a picture to yourself (note its size before sending it) or having someone else send you a picture. Good luck!
Ya the .050 to .50 in the gateway fixes it. makes me mad how much time i wasted thinking I did something wrong and it was tmobile's settings the whole time. grrrrrrr

Thanks

[mfrazzz]

The Very first corssbow rom i tried was the MB version. I still got my pix at 160x120 or smaller, so i dunno why. My settigns are set at "original" but im still getting the same 'ol small pix... *sigh*
This turns out to be settings for your connection. See your seperate post on this topic and you'll see a link over to the Hermes forum where they have Cingular CABs. This fixed my issue with the 160x120 scaled images.Here's a link to the thread in the Hermes forum that fixed my Wizard's settings and this problem:
http://forum.xda-developers.com/showthread.php?t=299393

I used the second cab in the first post.

[eminkel]

I'm having an issue with my MDA. I have done the setup to what tmobile has on their website. I did change the .050 to .50 and it says it connects to the Tmobile GPRS EDGE network. But, nobody seems to get the picture messages. I am running WM6 MBE. Any suggestions?

[demontefixo]

I'm having an issue with my MDA. I have done the setup to what tmobile has on their website. I did change the .050 to .50 and it says it connects to the Tmobile GPRS EDGE network. But, nobody seems to get the picture messages. I am running WM6 MBE. Any suggestions?add a wap.voicestream.com connection.

--M

[eminkel]

Could somebody post how to do this step by step on a WM6 phone? Or send me a link. I'm a newb to this ;)

[marscandybars]

Many of you have noticed, that if you manually created an access point and manually configured MMS server settings, your incoming text messages are TINY thumbnail pictures. This of course is unacceptable for a device such as ours :-p. I have put together a little step by step solution SPECIFICALLY for t-mobile. There are some Cingular cabs out there, but for some reason it didn't work for me. This however did:

After this procedure you should be receiving the picture messages in the exact size the sender had sent it (given that their phone/network is capable of sending you large files without pre-downsizing them)

For T-mobile USA customers do this

1. Install t-mobile_network_customizations.cab
2. Menu > Tools > Options > MMS> Servers

You will then see a profile called "Default" (if you dont see it in the MMS server profiles settings, simply close out and repeat step 2 again. It will have very weird settings in the boxes; simply write over them)

Open it and edit as follows

Server Name: Default (or any will do, but i usually leave this as is)
Gateway: 216.155.165.50
Port number: 8080
Server address: http://216.155.174.84/servlets/mms
Connect via: T-mobile GPRS (this should already be pre-set for you if you installed the cab)
Sending size limitation: 292K
WAP version WAP 2.0

Press ok and make sure this profile is set to default. Delete any other profiles (unless they are needed if you use other servers)


I have tested this with BOTH my MDA and my New 8525. Without it, i get TINY picture messages. To clear things up, receiving tiny picture messages is NOT a T-mobile server downsizing issue. There was something that was skipped over when the WM6 roms were cooked (or maybe an arksoft issue??? however, with all versions i had this problem if i didnt not install the cab). Which is why simply editing an access point and creating a MMS profile will NOT work. This cab file does miracles! ENJOY!

[eminkel]

marscandybars, Thank you for the post. I did everything on that and still it doesn't send or recieve. I am looking for a program to take screen shots of my phone settings for anybody who can help. I am running Most Beautiful edition. Anybody have issues with their MMS service sending on MBE?

[eminkel]

Here is my issue, I took screen shots of the process I took to set it up. (Someone could use these images if they need to).

http://img476.imageshack.us/img476/8176/92894934fg2.png
http://img124.imageshack.us/img124/3940/10942235lf7.png
http://img476.imageshack.us/img476/5908/62721885ze5.png
http://img476.imageshack.us/img476/1772/21586529lu1.png

[eminkel]

http://imageshack.us][img=http://img469.imageshack.us/img469/4081/80400140ej2.png
http://img469.imageshack.us/img469/5984/39344965ak9.png

And then Error Synchronizing when pressing Send/Recieve (Even with messages in the Outbox)
http://img469.imageshack.us/img469/5269/errorsynchronizingzt1.png

Any help is greatly appreciated :D

[eminkel]

Hmmm... after a hard reset (I think thats what its called when you hold the power button to turn the device off) it seems to want to send. Gets to 90% but then doesn't say anything... No responses out of the person i'm sending it to. LOL.

[eluth]

Please find attached the two CABs I'm using on my MDA.
They are heavily inspired from the T-Mobile USA Cabs delivered in their 2.26 official ROM, but I had to tweak them to support ArcSoft 3.5.1.17.

In essence, what did change (among other thing) is how ArcSoft deals uses the registry keys to name profiles and refer to the default profile.

The T-Mobile GPRS.CAB file setup the GPRS/EDGE parameters.
Please note they are two connections (GPRS for regular data connection and MMS for ArcSoft MMS based connections).

Please see attached T-Mobile_GPRS_setup.xml.txt.
I could add a CODE section - post was getting too long.


The T-Mobile MMS.CAB sets up ArcSoft, once GPRS is already setup.
Tested with ArcSoft 3.5.1.17 and working, when the GPRS.cab is used first.


<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\ArcSoft\ArcSoft MMS UA\Config\UI" translation="filesystem" >
<parm name="DownloadHomeNetworkOnly" datatype="integer" value="0" />
<parm name="VideoFilter" datatype="string" value=".3gp;" translation="filesystem" />
<parm name="AutoDisconnect" datatype="integer" value="1" />
<parm name="SupportAutoSignature" datatype="integer" value="0" />
<parm name="AllowSendReadReport" datatype="integer" value="1" />
<parm name="AlphaTagDispTxt" datatype="string" value="" translation="filesystem" />
<parm name="AlphaTag" datatype="string" value="" translation="filesystem" />
<parm name="EnableSaveAudioObject" datatype="integer" value="1" />
<parm name="DefaultResolution" datatype="integer" value="0" />
<parm name="NeedDisplayMsgInfo" datatype="integer" value="0" />
<parm name="EnableSentNotify" datatype="integer" value="0" />
<parm name="EnableSentPrompt" datatype="integer" value="0" />
<parm name="EnableDownloadedNotify" datatype="integer" value="1" />
<parm name="EnableDownloadedPrompt" datatype="integer" value="1" />
<parm name="EnableReceiveNotify" datatype="integer" value="0" />
<parm name="EnableReceivePrompt" datatype="integer" value="0" />
<parm name="EnableServerEdit" datatype="integer" value="1" />
<parm name="HideDlgControl" datatype="integer" value="16234" />
<parm name="PromptForActiveConnection" datatype="integer" value="0" />
</characteristic>
<characteristic type="HKLM\SOFTWARE\ArcSoft\ArcSoft MMS UA\Config\mm1" translation="filesystem" >
<parm name="DefaultSetting" datatype="string" value="T-Mobile MMS" translation="filesystem" />
<parm name="Enabledrmfl" datatype="integer" value="0" />
<parm name="SuppressDelayedNotifyResp" datatype="integer" value="1" />
<parm name="ReportAllowed" datatype="integer" value="1" />
<parm name="SendDelayedNotifyResp" datatype="integer" value="0" />
</characteristic>
<nocharacteristic type="HKLM\SOFTWARE\ArcSoft\ArcSoft MMS UA\Config\mm1\MMSCSetting\Default" />
<characteristic type="HKLM\SOFTWARE\ArcSoft\ArcSoft MMS UA\Config\mm1\MMSCSetting\T-Mobile MMS" translation="filesystem" >
<parm name="ConnectionVia" datatype="string" value="{FF445A54-ADF8-4fab-86B7-E31482BEE8BE}" translation="filesystem" />
<parm name="waptype" datatype="integer" value="1" />
<parm name="GatewayPort" datatype="integer" value="8080" />
<parm name="ISP" datatype="string" value="T-Mobile MMS" translation="filesystem" />
<parm name="MmscURI" datatype="string" value="http://216.155.174.84/servlets/mms" />
<parm name="Gateway" datatype="string" value="216.155.165.50" translation="filesystem" />
<parm name="Name" datatype="string" value="T-Mobile MMS" translation="filesystem" />
<parm name="RecvDefault" datatype="integer" value="512000" />
<parm name="SendDefault" datatype="integer" value="307200" />
<parm name="WAP2DefaultSize" datatype="integer" value="307200" />
<parm name="WAP1DefaultSize" datatype="integer" value="307200" />
</characteristic>
<characteristic type="HKLM\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader" translation="filesystem" >
<parm name="Accept" datatype="string" value="application/vnd.wap.mms-message;*/*;" />
<parm name="User-Agent" datatype="string" value="prodigy/arcsoft-mmsua-ppc-3.0.0.xx" />
<parm name="Profile" datatype="string" value="http://www.htcmms.com.tw/gen/wizard-2.0.xml" />
</characteristic>
<characteristic type="HKLM\SOFTWARE\ArcSoft\ArcSoft MMS UA\Config\UI\SizeLimit" translation="filesystem" >
<parm name="SendLimit1" datatype="integer" value="307200" />
<parm name="SendCount" datatype="integer" value="1" />
</characteristic>
<characteristic type="HKLM\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\UI\SendOption" translation="filesystem" >
<parm name="NeedReadReportFac" datatype="integer" value="0" />
<parm name="NeedDeliveryReportFac" datatype="integer" value="0" />
<parm name="NeedReadReport" datatype="integer" value="1" />
<parm name="NeedDeliveryReport" datatype="integer" value="1" />
</characteristic>
<characteristic type="HKLM\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\Capture" translation="filesystem" >
<parm name="VideoFileRatio" datatype="integer" value="90" />
<parm name="PhotoRes" datatype="integer" value="128" />
</characteristic>
<characteristic type="HKCU\Software\HTC\MMSTool" translation="filesystem" >
<parm name="Notification Interval" datatype="integer" value="3" />
</characteristic>
<characteristic type="HKLM\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\UI\TryLimit" translation="filesystem" >
<parm name="TryDefault" datatype="integer" value="5" />
<parm name="Interval5" datatype="integer" value="20" />
<parm name="Interval4" datatype="integer" value="15" />
<parm name="Interval3" datatype="integer" value="10" />
<parm name="Interval2" datatype="integer" value="5" />
<parm name="Interval1" datatype="integer" value="1" />
</characteristic>
<characteristic type="HKCU\ControlPanel\Notifications\{C3465585-39EF-4c9b-B2A3-5558BF27BFB0}" translation="filesystem" >
<parm name="Options" datatype="integer" value="0" />
</characteristic>
<characteristic type="HKCU\ControlPanel\Notifications\{70C48D00-C1A6-43cf-B4C5-5B4E771E2462}" translation="filesystem" >
<parm name="Options" datatype="integer" value="0" />
</characteristic>
<characteristic type="HKCU\ControlPanel\Notifications\{3C781384-05F3-4035-A8F9-C23F19A93AF0}" translation="filesystem" >
<parm name="Options" datatype="integer" value="9" />
</characteristic>
<characteristic type="HKCU\ControlPanel\Notifications\{3C850505-06F3-5035-C8F9-C25F19A93AF1}" translation="filesystem" >
<parm name="Options" datatype="integer" value="0" />
</characteristic>
<characteristic type="HKCU\ControlPanel\Notifications\{3C850506-07F3-6035-E8F9-C29F19A93AF2}" translation="filesystem" >
<parm name="Options" datatype="integer" value="0" />
</characteristic>
<characteristic type="HKCR\3gpfile\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Videos" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\mp4file\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Videos" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\avifile\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Videos" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\m4vfile\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Videos" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\m4afile\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Music" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\wavfile\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Music" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\midifile\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Music" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\amrfile\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Music" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\awbfile\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Music" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\bmpimage\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Pictures" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\wbmpimage\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Pictures" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\gifimage\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Pictures" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\jpegimage\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Pictures" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\pngimage\Shell\Save\Save Location" translation="filesystem" >
<parm name="Default" datatype="string" value="My Pictures" translation="filesystem" />
</characteristic>

</characteristic>
</wap-provisioningdoc>



Cab file are packed in the attached .ZIP files.

Regards,
--eluth.

[eminkel]

eluth, I tried yours still Error Syncronizing. I reverted back to the default settings on my entire device. Installed the GPRS.cab and then the MMS.cab and it doesn't even connect to the GPRS network anymore. This is frusturating me. I pay for 1000 picture messages each month and I haven't been able to use that feature after upgrading to the phone. (I may revert back to the tmoble factory rom).

[eminkel]

I think I got it to work!!! :D :D Sorry for so many posts.

[eluth]

I think I got it to work!!! :D :D Sorry for so many posts.

What was the original problem?

Did you use the two Cabs I posed? Btw, these are for T-Mobile USA only.

Regards,
--eluth.

[marscandybars]

Mine has ALWAYS had the error synchronizing issue ever since i've installed ALL custom WM6 roms. But it has not affected functionality. I am still able to send and receive files. My step by step instructions were to resolve the small picture message issue. If i had no outgoing or incoming mms messages waiting, it would say error synchronizing. But if there was something in my outbox that was waiting to go out, or an mms message that i havent received yet, then the synchronization would pull or send the mms pictures thru the server.

[eminkel]

Here is how I got it to work. I reset my OS back to default and installed the .CAB's provided by eluth. And then those didn't seem to work, I was still not able to send or recieve MMS. So, I installed the .CAB provided by marscandybars, checked all my settings to make sure everything was pointing to the correct connections, changed the server from: internet3.voicestream.com (because of eluths cab) back to: wap.voicestream.com. Did a soft reset, and tried to send a message and it connected to GPRS, and sent 100%, got a response from the person I sent it to, they sent me an MMS back and it downloaded and showed up, full size. This thread helped me alot, I got my phone just under 2 weeks ago. This forum is amazing, tons of info, as I learn more I will definatley try to contribute :)

Sorry for the delayed conclusion.

[rsfaze]

I have faria real thing rom. I am able to send MMS messages. I am able to recieve the message but when i click on the message to select download its not an option as its grayed out. Any ideas? I was happy that I was finally able to send these messages now that the server address was found to be an issue.

[youngyoshi]

Mine has ALWAYS had the error synchronizing issue ever since i've installed ALL custom WM6 roms. But it has not affected functionality. I am still able to send and receive files. My step by step instructions were to resolve the small picture message issue. If i had no outgoing or incoming mms messages waiting, it would say error synchronizing. But if there was something in my outbox that was waiting to go out, or an mms message that i havent received yet, then the synchronization would pull or send the mms pictures thru the server.

I get this error even when sending txt messages, and they wont send when it happens

[marscandybars]

I get this error even when sending txt messages, and they wont send when it happens

The cabs provided in this forum do not affect SMS whatsoever. SMS complications result from either the rom, or your network, as they are not configured thru the GPRS settings nor the MMS settings. Have you tried other roms, or reinstalling the rom?

If decide to reflash or trying another rom, try sending a test sms message first before installing any MMS settings. SMS messages work without configuration with all the roms.

You might also want to trying using a different Radio rom.

[rsfaze]

bump for my unsolved problem

[rsfaze]

wow I am in shock. I dont think there has ever been a thread about something here that got no responses. This has been an ongoing issue. I guess its time to flash a different rom than the real thing as the community cant figure out the little issues with it. Thanks to all who have replied this is not directed at any of you.

[eminkel]

rsfaze, have you attempted to re-flash the faria rom? Has there been any other reported issues similar to your in the faria rom threads?

[gibhenry]

I've followed links all over the place but never managed to get my i-mate Jasjar to send or receive MMS for 6 months. Somehow, finally, I got all the pieces into place, and here are two key elements:

1. Despite instructions to the contrary in the T-Mobile MMS configurator (http://tmobileus.wdsglobal.com/mms?step=services.vm&contractId=235&countryId=37&networkId=90&bearerId=5&phoneId=1184&mobileNumber=&captchaEnabled=true&service=mms), at least for the HTC Universal, do NOT put a leading zero in any 2-digit dotted quad in Messaging/Menu/MMS Configuration/Servers tab (e.g., ignore "216.155.165.050" and instead type exactly "216.155.165.50"; same for "http://216.155.174.84/servlets/mms" instead of "...174.084..."); and

2. After setting up MMS, click the power button until the device turns off (not just the screen; don't press and hold, just click and release; if you're sync'ed, you'll hear it disconnect). Repower to load the settings!!

These steps may or may not be necessary/helpful with other devices. Here are the promised screenshots. Each screenshot is named for the T-Mobile Configurator step number (mouse over an image to see its name in a "tool tip"). Hope this helps some folks! Cheers,

[pickpocket]

I got my MMS to work. My problem is not being able to send emails. I thought that MMS and emails were sent/received using the same network? I don't know for sure. I can receive all day just can't send with out getting a sychronizing error unless I send via MMS or I'm connected to my laptop via USB. Am I alone on this one?

[gibhenry]

I got my MMS to work. My problem is not being able to send emails. I thought that MMS and emails were sent/received using the same network? I don't know for sure.
E-mail generally uses the same network as, for example, your web browser--but it's not MMS.

I can receive all day just can't send with out getting a sychronizing error unless I send via MMS or I'm connected to my laptop via USB. Am I alone on this one?

Assuming your can use your browser, then this sounds like a POP or IMAP configuration problem. Check whether your incoming and outgoing mail use the same or different servers and authentications. Also be sure your authentication is what your e-mail server expects. Cheers,

[Master Loon]

Fellas, Thanks. I have had messages hanging in my inbox for weeks.

This helped!

[eboy44]

when i install the GPRS cab it says installation was unsuccessful, what am i doing wrong?

Please find attached the two CABs I'm using on my MDA.
They are heavily inspired from the T-Mobile USA Cabs delivered in their 2.26 official ROM, but I had to tweak them to support ArcSoft 3.5.1.17.

In essence, what did change (among other thing) is how ArcSoft deals uses the registry keys to name profiles and refer to the default profile.

The T-Mobile GPRS.CAB file setup the GPRS/EDGE parameters.
Please note they are two connections (GPRS for regular data connection and MMS for ArcSoft MMS based connections).

Please see attached T-Mobile_GPRS_setup.xml.txt.
I could add a CODE section - post was getting too long.




Cab file are packed in the attached .ZIP files.

Regards,
--eluth.

[mp3maker]

I finally remembered what the "deal" is... the MMS instructions for TMobile has a minor error:216.155.165.050 should be:216.155.165.50

Note the lack of the zero before the .50

Give it a whirl, let me know.

--M

PS I added it to the Wiki for the next time I forget how to fix it.

Thanks this worked awesome I thought my phone was just being messed up until I changed that...

[cellphoneman]

hi,
i hav a cingular 8125 n flashed NBD v8.0 a week ago.. everything wrks fyn xcpt i cant send emails through text messeging. it says. emails cant be sent. can ne one please help me.

[hkbladelawhk]

Hmm, This is odd. Mine will give me the error, though I have still been able to send. I have recieved pics from friends as well. Thought when I try to email myself something, it doesn't go through...

[theguynamedkem]

this actually works! amazing what a difference one little zer0 can make. thank you very much gibhenry!

[Ray_jai]

Hi,
i can't recieve MMS,

I looked on t-mo site and this is what it says:
Setting up the MMS profile

Tap Start again.
Tap Messaging.
Tap Menu.
Tap MMS Configuration.
Tap the Servers tab.
Tap New.
Enter T-Mo MMS in the Server Name field.
Enter 216.155.165.050 in the Gateway field.
Enter 8080 in the Port number field.
Enter http://216.155.174.84/servlets/mms in the Server address field.
Tap to select T-Mobile GPRS from the Connect via drop down list.
Tap to select WAP 2.0 from the WAP Version dropdown.
Tap OK.
Scroll to T-Mo MMS and tap Set As Default.
Tap OK.

But don't seen MMS configuration under menu. how can i set it up?

Thanks in advance.

[jlowe8700]

I Finally Got Mine To Work On My Unlocked 8525 Thankz Xda

____________________
At&t 8525(upgraded To Wm6.1) :)
Sim Unlocked To T-mobile
Tmobile Mda(crossbow Wm6)

[scousemartin]

Hi,
i can't recieve MMS,

I looked on t-mo site and this is what it says:
Setting up the MMS profile

Tap Start again.
Tap Messaging.
Tap Menu.
Tap MMS Configuration.
Tap the Servers tab.
Tap New.
Enter T-Mo MMS in the Server Name field.
Enter 216.155.165.050 in the Gateway field.
Enter 8080 in the Port number field.
Enter http://216.155.174.84/servlets/mms in the Server address field.
Tap to select T-Mobile GPRS from the Connect via drop down list.
Tap to select WAP 2.0 from the WAP Version dropdown.
Tap OK.
Scroll to T-Mo MMS and tap Set As Default.
Tap OK.

But don't seen MMS configuration under menu. how can i set it up?

Thanks in advance.

change the gateway ip for starters (enter 216.155.165.50 instead) and if you dont see the mms configuration under menu click messages > menu > tools >options > MMS > servers and that is where you need to enter the details above. If you havent got that option in your rom then maybe you have not got arcsoft mms installed (is it a cooked rom) search for arcsoft mms and install it

[tbnext]

Thank you so much, I have gone through tons of different setups for this and i was doing the t-mo setup for the htc touch rom that i have running on my mda, and nothing worked, in the end it was the .50 rather than .050... THANK YOU!!!