Native HTC messaging MMS fix (collaboration)

**mswlogo** · #1 (**permalink**) 12-20-2009, 12:42 PM

Quote:

Originally Posted by ziggy471

That's about right, and I haven't forgotten about the Sprint Users, that's why I spent so much time on this yesterday, that and all the snow. Once I finish my first cup of coffee, I'll start on it again today.

Z

Thanks Ziggy, be very interested in what you find.

How can you debug Sprint if you are on Verizon though?

I played around a lot last night and I suspect I'm still catching up. But I noticed that there are two sets of settings. One for GSM and one for CDMA. I'm not sure all pieces agree which to use.

Any way I came up with this REG script to set everything consistent (see bottom).

But I notice that when I send something larger than 300k it still warns me it's over 300K even though I set everything 1024K.

Before installing Valyrie (Sprint) Cab it would fail to send. And I'd get a Message Box "Send ... Get ... Failed" or some such. After installing Valyrie (Sprint) Cab. And rerunning the reg script below a Send to myself completes but nothing comes back. I have no other working MMS device to check if it actually sent.

I also googled and noticed some devices use X-sprint-MDN instead of X-SPRINT-MDN not sure if it's case sensitive but usually paramters are case sensitive.

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\Messaging\MMS\ Profile\CDMA]
"Lock"=dword:00000000
"Port"=dword:00000050
"ConnectionType"=dword:00000000
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=508XXXXXXX"
"SendLimit"=dword:00000400
"IPAddress"=""
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"Name"="Sprint"

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\Messaging\MMS\ Profile\GSM]
"Name"="Sprint"
"IPAddress"=""
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=508XXXXXXX"
"SendLimit"=dword:00000400
"ConnectionType"=dword:00000000
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"Port"=dword:00000050
"Lock"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\Profiles]
"ActiveProfileGSM"="Sprint"
"ActiveProfileCDMA"="Sprint"
"DefaultSendSize"=dword:00000400
"DefaultNetwork"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\Profiles\S print]
"Lock"=dword:00000000
"Port"=dword:00000050
"ConnectionType"=dword:00000000
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=508XXXXXX"
"IPAddress"=""
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"SendLimit"=dword:00000400
"Name"="Sprint"

**chris1683** · #2 (**permalink**) 12-20-2009, 01:31 PM

Quote:

Originally Posted by mswlogo

Thanks Ziggy, be very interested in what you find.

How can you debug Sprint if you are on Verizon though?

I played around a lot last night and I suspect I'm still catching up. But I noticed that there are two sets of settings. One for GSM and one for CDMA. I'm not sure all pieces agree which to use.

Any way I came up with this REG script to set everything consistent (see bottom).

But I notice that when I send something larger than 300k it still warns me it's over 300K even though I set everything 1024K.

Before installing Valyrie (Sprint) Cab it would fail to send. And I'd get a Message Box "Send ... Get ... Failed" or some such. After installing Valyrie (Sprint) Cab. And rerunning the reg script below a Send to myself completes but nothing comes back. I have no other working MMS device to check if it actually sent.

I also googled and noticed some devices use X-sprint-MDN instead of X-SPRINT-MDN not sure if it's case sensitive but usually paramters are case sensitive.

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\Messaging\MMS\ Profile\CDMA]
"Lock"=dword:00000000
"Port"=dword:00000050
"ConnectionType"=dword:00000000
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=508XXXXXXX"
"SendLimit"=dword:00000400
"IPAddress"=""
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"Name"="Sprint"

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\Messaging\MMS\ Profile\GSM]
"Name"="Sprint"
"IPAddress"=""
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=508XXXXXXX"
"SendLimit"=dword:00000400
"ConnectionType"=dword:00000000
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"Port"=dword:00000050
"Lock"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\Profiles]
"ActiveProfileGSM"="Sprint"
"ActiveProfileCDMA"="Sprint"
"DefaultSendSize"=dword:00000400
"DefaultNetwork"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\Profiles\S print]
"Lock"=dword:00000000
"Port"=dword:00000050
"ConnectionType"=dword:00000000
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=508XXXXXX"
"IPAddress"=""
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"SendLimit"=dword:00000400
"Name"="Sprint"

Just to clarify, did these setting work for sending/receiveing on Sprint or are they just to keep things the same within the registry?

**mswlogo** · #3 (**permalink**) 12-20-2009, 02:30 PM

Quote:

Originally Posted by chris1683

Just to clarify, did these setting work for sending/receiveing on Sprint or are they just to keep things the same within the registry?

NO !! I was just sharing my progress and discoveries. Which I believe ziggy is well aware of.

It does "send" with no error. But I have no idea if it really went since I have no known working receiver.

Folks saying "it works for me" on verizon at this point is not helpful because that appears to be a no brainer for verizon folks now.

I'm waiting for ziggy to finish his morning coffee.

**ziggy471** · #4 (**permalink**) 12-20-2009, 05:25 PM

Quote:

Originally Posted by mswlogo

NO !! I was just sharing my progress and discoveries. Which I believe ziggy is well aware of.

It does "send" with no error. But I have no idea if it really went since I have no known working receiver.

Folks saying "it works for me" on verizon at this point is not helpful because that appears to be a no brainer for verizon folks now.

I'm waiting for ziggy to finish his morning coffee.

Sorry, after three cups, then three hours of shoveling snow, then 2 cups of hot chocolate, then a trip to the mall, and then lunch, I'M TIRED.

I promise that I'll start again tomorrow, maybe this evening, if I don't have a Guilty Verdict drink, then again that might help, if you don't know what that is just Google it. I did leave a very detailed post as to where I left off at 6:30am, someone else can take over for now. I'll check back before starting again.

Z

auburnmk · #5 (**permalink**) 12-20-2009, 05:30 PM

Forget the mms issue, what's a Guilty Verdict? lmao

Quote:

Originally Posted by ziggy471

Sorry, after three cups, then three hours of shoveling snow, then 2 cups of hot chocolate, then a trip to the mall, and then lunch, I'M TIRED.

I promise that I'll start again tomorrow, maybe this evening, if I don't have a Guilty Verdict drink, then again that might help, if you don't know what that is just Google it. I did leave a very detailed post as to where I left off at 6:30am, someone else can take over for now. I'll check back before starting again.

Z

**ziggy471** · #6 (**permalink**) 12-20-2009, 05:33 PM

Quote:

Originally Posted by auburnmk

Forget the mms issue, what's a Guilty Verdict? lmao

151 and OJ, the bartender that invented it said that if OJ had that much proof on him.......

Z

auburnmk · #7 (**permalink**) 12-20-2009, 09:34 PM

Lmao!!

Quote:

Originally Posted by ziggy471

151 and oj, the bartender that invented it said that if oj had that much proof on him.......

Z

auburnmk · #8 (**permalink**) 12-20-2009, 01:47 PM

I have 2 Sprint devices I can test with, just trying to get my bearings on what settings to change and where within TP2. It's been awhile since working within the registry, but no sweat jumping right in.

I'm running MM Impact(6.5.3) with Sense 2.5. I swore I was able to change some mms settings last night, but now can't find where for the life of me. Of course, this was after a few potent vodka libations....lol

Not a n00b, but not a cook by any means, just want to collaborate and succeed with this endeavour.

Quote:

Originally Posted by mswlogo

Thanks Ziggy, be very interested in what you find.

How can you debug Sprint if you are on Verizon though?

I played around a lot last night and I suspect I'm still catching up. But I noticed that there are two sets of settings. One for GSM and one for CDMA. I'm not sure all pieces agree which to use.

Any way I came up with this REG script to set everything consistent (see bottom).

But I notice that when I send something larger than 300k it still warns me it's over 300K even though I set everything 1024K.

Before installing Valyrie (Sprint) Cab it would fail to send. And I'd get a Message Box "Send ... Get ... Failed" or some such. After installing Valyrie (Sprint) Cab. And rerunning the reg script below a Send to myself completes but nothing comes back. I have no other working MMS device to check if it actually sent.

I also googled and noticed some devices use X-sprint-MDN instead of X-SPRINT-MDN not sure if it's case sensitive but usually paramters are case sensitive.

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\Messaging\MMS\ Profile\CDMA]
"Lock"=dword:00000000
"Port"=dword:00000050
"ConnectionType"=dword:00000000
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=508XXXXXXX"
"SendLimit"=dword:00000400
"IPAddress"=""
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"Name"="Sprint"

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\Messaging\MMS\ Profile\GSM]
"Name"="Sprint"
"IPAddress"=""
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=508XXXXXXX"
"SendLimit"=dword:00000400
"ConnectionType"=dword:00000000
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"Port"=dword:00000050
"Lock"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\Profiles]
"ActiveProfileGSM"="Sprint"
"ActiveProfileCDMA"="Sprint"
"DefaultSendSize"=dword:00000400
"DefaultNetwork"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\Profiles\S print]
"Lock"=dword:00000000
"Port"=dword:00000050
"ConnectionType"=dword:00000000
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms?X-SPRINT-MDN=508XXXXXX"
"IPAddress"=""
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"SendLimit"=dword:00000400
"Name"="Sprint"

**chris1683** · #9 (**permalink**) 12-20-2009, 02:17 PM

These are some of the settings taken from Arcsoft on Sprint. They were originally in the WspHeader and WspHeader2 entry folders. I am going to try adding/moving them into some corresponding entries on 2.5. Lets all keep up the good work and give Sprint users a Merry Christmas of Messaging with a working 2.5!!!

auburnmk · #10 (**permalink**) 12-20-2009, 02:41 PM

Anyone else notice the url is much different than what we've been working with so far? Seems to make sense if I'm reading it correctly....

Quote:

Originally Posted by chris1683

These are some of the settings taken from Arcsoft on Sprint. They were originally in the WspHeader and WspHeader2 entry folders. I am going to try adding/moving them into some corresponding entries on 2.5. Lets all keep up the good work and give Sprint users a Merry Christmas of Messaging with a working 2.5!!!