Re: Native HTC messaging MMS fix (collaboration)
 

Under PredefinedPort try Sprint = 80 (or whatever your data connection for sprint is called, used elsewhere in the MMS regkeys)

Re: Native HTC messaging MMS fix (collaboration)
 

I've already tried this on VZW, but still need the X-VZW-MDN in the server URL. The messaging client is still not filling in the From field (0x89), it just sticks a 0x01 right after it, then the 0x81, BCC, and finally 0x97, To, which it fills out. If you look at what is returned from the MMS server, it replies with Originator not Found. With VZW and USC, you can override this by passing the MDN in the URL Post, with Sprint, this doesn't work. For Telus, I guess that they are ignoring the value and going off of the connection, which I think makes more sense anyway.

EDIT: Just found some clarification as to what's happening.
The encoding mechanism works like this:
From-value = [0x01 or VALUE-length] [0x80 or 0x81] [Optional: Encoded-String-Value]
If we have 0x80 we have an encoded-string-value (0x80 is part of that string).
If we have 0x81 this is a insert-adress-token which means that the MMSC is supposed
to insert it, which means that we can't retrieve the sender.

In other words, VZW, Sprint, and USC, will not insert the sender, but Telus supports it.
Guess if I would have read the entire thing, I would not have mistaken the insert-address-token
for the BCC field.


Z

Re: Native HTC messaging MMS fix (collaboration)
 

Just found a possible key from looking at the mms.dll.

IsInsertAddressTokenEnable

This might fix the problem, now just to figure out where it belongs.


Z

Re: Native HTC messaging MMS fix (collaboration)
 

Can't get this to work on EnergyROM. I am going to try and get the provisioning off MightyROM and try it on Energy and see if that helps, will update with the results.

Re: Native HTC messaging MMS fix (collaboration)
 

The provisioning won't help, I just copied his values into the appropriate keys for Jataayu.


Z

Re: Native HTC messaging MMS fix (collaboration)
 

I would double/triple check everything settings wise.

It is working perfectly for me using Juicy & Verizon. If it works with Juicy's ROM, I would think the same setup would work with NRG also. Generally, I have found these ROM's are similar enough that if something works in one the chances are good it will work in the other the same way.

If I get time later, I may flash to NRG & try it myself just to see what happens.

~John

Re: Native HTC messaging MMS fix (collaboration)
 

I'm running NRG EnergyROM on Verizon, I ran Valkyrie 2.5 MMS fix and adjusted the mms settings. Not working for me. Can someone who has this working list all the changes they made.

Re: Native HTC messaging MMS fix (collaboration)
 

From what I just read in this thread, which was from start to finish, do not install Valkyrie cab or Arcsoft, make the necessary mms changes and you (Verizon users) are good to go.

Re: Native HTC messaging MMS fix (collaboration)
 

Flashing to MM Impact 2.5 and will be able to test, validate, and assist in resolving this issue for Sprint users like myself.

Re: Native HTC messaging MMS fix (collaboration)
 

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