|
|
|
||||
|
Re: Native HTC messaging MMS fix (collaboration)
But which Mighty rom are you running? If it is a Manilla 2.1 rom it should work...the problem is with sense 2.5 roms...
|
|
||||
|
Re: Native HTC messaging MMS fix (collaboration)
The problem arrises when you want to run a manila 2.5 ROM & send/receive MMS through the HTC app. That only works with Verizon.
Sprint users have to send MMS with ArcSoft. ~John |
|
||||
|
Re: Native HTC messaging MMS fix (collaboration)
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 |
| This post has been thanked 4 times. |
|
||||
|
Re: Native HTC messaging MMS fix (collaboration)
Quote:
|
|
||||
|
Re: Native HTC messaging MMS fix (collaboration)
Quote:
[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\SP] "LogBuffer"=dword:00000001 "Logging"=dword:00000001 (This will create log files in ErrorRep dir) "UserAgent"="T7380" "UAProfile"="http://device.sprintpcs.com/HTC/PPCT7380SP/%CDMA_ROM_VERSION%.rdf" Also try this for the server: http://mms.sprintpcs.com/?X-SPRINT-MDN=1234567890 These are just the settings out of Mike prov file. If it doesn't work, please pm me the contents of the send.dat, I only need up until the phone numbers or email, change them if you like, but replace phone numbers with 1234567890. Also include the contents of recv.dat file from ErrorRep directory. Z EDIT: OR use http://mms.sprintpcs.com/?X-MDN=1234567890 Last edited by ziggy471; 12-27-2009 at 12:45 AM. |
|
||||
|
Re: Native HTC messaging MMS fix (collaboration)
Quote:
KD8FRE
__________________
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! |
|
||||
|
Re: Native HTC messaging MMS fix (collaboration)
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\SP] "LogBuffer"=dword:00000001 "Logging"=dword:00000001 (This will create log files in ErrorRep dir) "UserAgent"="T7380" "UAProfile"="http://device.sprintpcs.com/HTC/PPCT7380SP/%CDMA_ROM_VERSION%.rdf" & [HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\MMS\OEM\HTTPHeaders] "AcceptHeader"="X-MDN" "AcceptCharSet"="us-ascii,utf-8,iso-10646-ucs-2,ISO-8859-1" "AcceptLanguage"="en" (I didn't see Jataayu\MMS\HTTPHeaders so I had to manually add it) When using 1 infront of the 10 digit number it was stuck on sending, but when I removed the 1, it said sent, however nothing has shown up yet on the receiver. Last edited by ajent; 12-27-2009 at 03:11 AM. |
|
||||
|
Re: Native HTC messaging MMS fix (collaboration)
Quote:
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 Last edited by kd8fre; 12-27-2009 at 12:35 AM. Reason: wrong info |
![]() |
|
|
|