12-27-2009, 12:28 AM
|
|
Regular 'Geeker
Offline
|
|
Join Date: May 2007
Posts: 313
Reputation: 135
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
|
Re: Native HTC messaging MMS fix (collaboration)
Quote:
Originally Posted by ziggy471
I've found a few keys that actually work, at least in MM War2.
They are:
Verizon version:
[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\OEM\HTTPHe aders]
"AcceptHeader"="application/vnd.wap.multipart.related"
"AcceptCharSet"="us-ascii,utf-8,iso-10646-ucs-2,ISO-8859-1"
"AcceptLanguage"="en"
Sprint should be:
"AcceptHeader"="X-MDN"
"AcceptCharSet"="us-ascii,utf-8,iso-10646-ucs-2,ISO-8859-1"
"AcceptLanguage"="en"
If you like to be able to choose between 2 servers, and have MMSPreferedNetwork=0, you can set the following so you don't see Operator Not Found:
[HKEY_LOCAL_MACHINE\Software\OEM\RIL]
"CDMAOperatorName"="CDMA MMS Server"
"GSMOperatorName"="GSM MMS Server"
Even with the extra settings for the HTTP Headers, I still have to have the X-VZW-MDN in the post line of the server. I'm still going through a disassembly of the mms.dll. There are a lot of limits we can set under MMS\SP\Limits. I have also verified that GSMorCDMA(dw), MDNorMIN(dw), MDNPrefix(sz), and CDMAHeader(sz) values are under MMS\SP, but still can't get them recognized when set.
If someone on Sprint can try the extra HTTP Headers and the X-SPRINT-MDN in the MMSC url set, who knows, it just might work. I'm still not going to quit working on this until I can get it working without the extra variable in the server url.
Z
|
I'll try it but I'm unclear what I need to do...just change the 3 keys above or something more?
|