12-27-2009, 12:33 AM
|
|
PPCGeeks Regular
Offline
|
|
Join Date: Aug 2009
Posts: 75
Reputation: 110
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 am on Sprint.
Added the three keys you said, changed MMS and SMS preferred networks to 2, and put the extra stuff in my MMSCurl, and I now am getting a "message could not be sent" error
KD8FRE
EDIT: the preferred networks, i set to 1, not 2
__________________
KD8FRE
Pocket PC Phones I've Had:
HTC Mogul; HTC Touch Pro; HTC Touch Pro 2
(All have been Sprint)
If I have been of any help, please hit the fancy "Thanks" button in the corner!
Last edited by kd8fre; 12-27-2009 at 12:35 AM.
Reason: wrong info
|