Re: Native HTC messaging MMS fix (collaboration)
 

although its my info im on metropcs not sprint, but i guess i could have been more clear and added that in the post

Re: Native HTC messaging MMS fix (collaboration)
 

I'm assuming you're on MetroPCS, since that's what you're carrier is listed as. Anyway, quick Google search, and here's your answer:

Gateway IP: 92.242.144.10
Port number: 3128
Server address: http://mms.metropcs.net/mmsc?X-metropcs-MDN=1234567890 (your phone number)
WAP=None

You might need to change the MMSC to: http://mms.metropcs.net/mmsc?X-metropcs-MDN=(your number)&X-DEVICE-MIN=1(your number)



Z

Re: Native HTC messaging MMS fix (collaboration)
 

thanks for trying, but it's a no go :(

Re: Native HTC messaging MMS fix (collaboration)
 

Does anyone know if the ROM available for the Hero can be unpacked in a kicthen like a WinMo ROM into packages. Perhaps if the 2.5 Messaging Client is in there we can see exactly how it is set up.

Re: Native HTC messaging MMS fix (collaboration)
 

I just downloaded the Leo 2.02 ROM Yesterday, let me find the link again for you.


Z

EDIT: Here it is: http://www.sendspace.com/file/6rvqwc

Re: Native HTC messaging MMS fix (collaboration)
 

And didn't someone mention that on the Hero MMS is set up using WAP 2.0? So shouldn't we be trying combinations of things using WAP 2.0 or is it possible to get it working without WAP as well?

Re: Native HTC messaging MMS fix (collaboration)
 

Yes, the Hero is using WAP 2.0. I have a deviceanywhere account and have check the Hero's MMS settings and it is definitely using WAP2.0

Re: Native HTC messaging MMS fix (collaboration)
 

Which ROM is this, Android with Sense2.5?

I saw a regkey in it and was curious.

Re: Native HTC messaging MMS fix (collaboration)
 

I've figured out how to enable better logging functions in the Jataayu client. It appears that it might not be an issue with the jMMS client to wanting to go into CDMA mode, it appears that it queries RIL, which tells it that our phone is a twin sim GSM, not a CDMA global. This could be why it's ignoring some of the keys we've been trying.

Anyone here understand RIL and can give me a hand, I'd appreciate it.

If anyone wants to see the extended logging, change the following:
HKLM\Software\Jataayu\Messaging
LogBuffer=dword:00000100
LogLevel=dword:000000ff
HKLM\Software\Jataayu\MMS\SP
Logging=dword:00000001

You'll notice new files created now under ErrorRep, the one I've been looking at is MessagingService.txt, it's the debug log file for the MessagingService.dll.


Z

Re: Native HTC messaging MMS fix (collaboration)
 

Acrsoft also uses WAP 2.0. Myself and others have tried every option we can think of to make it work. The only thing that we've been able to get working is WAP=None. While going through this whole process, I've discovered the keys we most likely need to set, it's just the client doesn't read them right now. Most likely this is do to the phone reporting that it's a twin-SIM GSM, instead of a CDMA WorldPhone, at least that's my guess.

Mine works on Verizon, I just want it to work correctly on ALL networks, without having to posts to the server in the url line. If anyone has the setting files off the Hero, shoot them my way, maybe that will help with what I'm missing.


Z