|
||||
Re: Native HTC messaging MMS fix (collaboration)
Quote:
On the flip side. 2.1 has a Jayaatu Registry key even though it's using Arcsoft. |
|
||||
Re: Native HTC messaging MMS fix (collaboration)
I know, but I have confidence that it will soon. When it does, is this thread gonna get organized a bit? No disrespect cuz this thread is amazing, but it's kind of a mess haha.
|
|
||||
Re: Native HTC messaging MMS fix (collaboration)
Quote:
Am I missing a setting??? I went into the MMS settings and Resolution is set to "Original". Not sure what else to check. Any help is appreciated.
__________________
Current: Verizon Droid X
- Former Verizon Touch Pro 2 -- Former Verizon Samsung Omnia I910 ---- Former Verizon XV6700 |
|
||||
Re: Native HTC messaging MMS fix (collaboration)
Quote:
I've now looked through most of the files that would relate to HTCMessaging from the Leo 2.02 dump. I've found new keys that weren't there before, but nothing that looks like it will help us, at least yet. The keys that still remain of interest to me are GSMorCDMA, MDNorMIN, CDMAHeader, DualSIMSupport and IsInsertAddressTokenEnable. The last one being of the most interest to me, since the MMS client is inserting an address token in the message sent to the server, instead of your phone number. I think this is why it is failing, at least without adding X-VZW-MDN to the post line for the server. The key is supposed to be in "Software\\%s\\MMS\\OEM", but since my assembler is very rusty, I can't seem to figure out what the string is replaced with. The function that checks this is at 0x10003484. I have tried replacing this with Jataayu and Jataayu\Messaging, and on an earlier version, I even tried it in HTC. But I'm tired for today, assembler does that to you. If I don't get back to this tonight, I'll start again in the morning, since I don't have to go back to work until next year. Z |
|
||||
Re: Native HTC messaging MMS fix (collaboration)
Quote:
Haven't tried sending any big pics yet, maybe it auto resizes on the phone or the mms server. Have you tried sending it to an email address, does it resize then? If not, maybe it's the VZW mms server. Z |
|
||||
Re: Native HTC messaging MMS fix (collaboration)
Quote:
- Sent 592k image to MMS (with "Original" resolution setting) ---> Outgoing MMS size: 593k, 2048 x 1216 dimensions ---> Incoming MMS size: 39k, 640x380 dimensions - Sent 592k image to Email (with "Original" resolution setting) ---> Outgoing MMS size: 593k, 2048 x 1216 dimensions ---> Incoming Email size: image @ 592k, 2048 x 1216 dimensions - Sent 592k image to Email (with "WVGA (800x480)" resolution setting) ---> Outgoing MMS size: 84K ---> Incoming Email size: image @ 83k, 1024 x 608 dimensions So, it looks like the server is setting size, dimensions, resolutions limits on incoming MMS images. Emails are fine. |
|
||||
Re: Native HTC messaging MMS fix (collaboration)
has anyone been able to get htc messaging mms from Leo\HD2 to work on METROPCS ? mms works fine without it, but for the leo messaging there's an extra mms settings that i just cant get. i think what i am missing is which ip address to use, which port and weather it should be WAP1.2 or WAP 2.0 or no wap.
ive been trying every setting possible n i got nothing
__________________
T-Mobile MDA\HTC Wizard--> At&t Tilt--> Sprint Touch Pro (MetroPCS)--> Sprint Touch Pro 2 (Sold) --> Moto DROID (MetroPCS) --> T-Mobile HD2 --> EVO 4G (MetroPCS) --> Thunderbolt
“Scientists dream about doing great things. Engineers do them.” James A. Michener You can find me on XDA under Lebmb, everywhere else under Mikezpc Last edited by mikezpc; 12-29-2009 at 07:30 PM. Reason: Added carrier name |
|
||||
Re: Native HTC messaging MMS fix (collaboration)
Quote:
|
|
|
|