Native HTC messaging MMS fix (collaboration)

[ziggy471]

Originally Posted by gregbolt

Which ROM is this, Android with Sense2.5?

I saw a regkey in it and was curious.

No, it's just Manila 2.5.19222911.0 from the Leo, which is WinMO 6.5.


Z

[gregbolt]

Originally Posted by ziggy471

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

Not a Noob, but where is the errorrep dir?
Just want to find it quickly rather than searching for it.

[ziggy471]

Originally Posted by gregbolt

Not a Noob, but where is the errorrep dir?
Just want to find it quickly rather than searching for it.

When logging is enabled, it's created on the Device.

Root directory.


Z

[chris1683]

Originally Posted by ziggy471

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

Going to give this a shot today.

[pdawg17]

Originally Posted by ziggy471

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

When I try to edit "LogLevel" it says "Invalid value. Must be between 0 and 4294967295"...

[chris1683]

Originally Posted by pdawg17

When I try to edit "LogLevel" it says "Invalid value. Must be between 0 and 4294967295"...

Make sure you edit the value in hexadecimal.

[ziggy471]

Originally Posted by chris1683

Going to give this a shot today.

Found out what might be the cause, I just decoded the bitmask for HKCU\ControlPanel\Phone\Features, which is 102B908, but should be 122B900. The two bits that are incorrect are:

0x00400000 -
Indicates that the phone is a global phone, and is capable of switching between GSM and CDMA radio modes. If this option is set on a device, it should always be set, regardless of the current operating mode of the phone.


and


0x00000008 -

The radio supports PIN locking. SIM Security UI should be shown.
This bit is supported only for the [HKEY_LOCAL_MACHINE\Security\Phone] registry key, and not [HKEY_CURRENT_USER\ControlPanel\Phone].


The second one should not be a problem, since it should be ignored. I just can't change the value. This might have to be done during cooking, I'll ask Mike.




Z

[chris1683]

Originally Posted by ziggy471

Found out what might be the cause, I just decoded the bitmask for HKCU\ControlPanel\Phone\Features, which is 102B908, but should be 122B900. The two bits that are incorrect are:

I checked this against my working mms registry from Mr.X 1.6.5 and the Features shows the 102B908 so I am not sure if that may be the culprit.

I did however make some good ground so far. One of our main problems was the lack of being able to send using WAP 2.0.

I found that adding the IP address of 63.215.195.152 into the MMS Server settings will now allow us to use the native WAP 2.0 in HTC Messaging Client. Could be leading us a little further down the right path. Lets all keep up the good work.

[pdawg17]

Originally Posted by chris1683

I checked this against my working mms registry from Mr.X 1.6.5 and the Features shows the 102B908 so I am not sure if that may be the culprit.

I did however make some good ground so far. One of our main problems was the lack of being able to send using WAP 2.0.

I found that adding the IP address of 63.215.195.152 into the MMS Server settings will now allow us to use the native WAP 2.0 in HTC Messaging Client. Could be leading us a little further down the right path. Lets all keep up the good work.

I can confirm that at least this does get the "message sent successfully" message...I hit the thanks button...

UPDATE: In case this info is helpful, I'll mention that the success message occurred either way if I had my actual phone number entered OR my MDN number which is different for me...

[chris1683]

The only other thing that I can figure is the fact that every message that send successfully has the "Accept */*" in the error report. When checking this against a working mms report, the Accept is "X-MDN" I am yet to find out where to place the right registry edit for this but will be working hard to find out!