PPCGeeks

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   HTC Touch Pro 2 (http://forum.ppcgeeks.com/forumdisplay.php?f=97)
-   -   Native HTC messaging MMS fix (collaboration) (http://forum.ppcgeeks.com/showthread.php?t=101286)

kd8fre 12-26-2009 05:38 PM

Re: Native HTC messaging MMS fix (collaboration)
 
Quote:

Originally Posted by badwolf (Post 1438616)
what happend from page 7 to here that it now works or is this verizon only?

Sprint is still not working.

KD8FRE

PS, instead of cluttering this thread with these questions, please read or search the thread first.

mrimage 12-26-2009 10:14 PM

Re: Native HTC messaging MMS fix (collaboration)
 
verizon r the lucky guys, i guest no more will ever get this tin work for the sprint ppl

mrm0er 12-26-2009 10:33 PM

Re: Native HTC messaging MMS fix (collaboration)
 
1 Attachment(s)
i am currently running mighty rom and i use the sprint network
i have been using this version of arcsoft mms, i send and recieve mms msgs just fine and fast i might add

pdawg17 12-26-2009 10:35 PM

Re: Native HTC messaging MMS fix (collaboration)
 
Quote:

Originally Posted by mrm0er (Post 1439072)
i am currently running mighty rom and i use the sprint network
i have been using this version of arcsoft mms, i send and recieve mms msgs just fine and fast i might add

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...

jmorton10 12-26-2009 10:51 PM

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

ziggy471 12-27-2009 12:10 AM

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

pdawg17 12-27-2009 12:28 AM

Re: Native HTC messaging MMS fix (collaboration)
 
Quote:

Originally Posted by ziggy471 (Post 1439222)
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?

kd8fre 12-27-2009 12:33 AM

Re: Native HTC messaging MMS fix (collaboration)
 
Quote:

Originally Posted by ziggy471 (Post 1439222)
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

ziggy471 12-27-2009 12:43 AM

Re: Native HTC messaging MMS fix (collaboration)
 
Quote:

Originally Posted by pdawg17 (Post 1439259)
I'll try it but I'm unclear what I need to do...just change the 3 keys above or something more?

Those three and make sure that you have these also set correctly:
[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

chris1683 12-27-2009 12:45 AM

Re: Native HTC messaging MMS fix (collaboration)
 
Testing this now on Juicy R5...


All times are GMT -4. The time now is 01:51 AM.

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0