View Full Version : are MMS resized on USA t-mobile?
chainsawbeer
30th August 2006, 11:28 AM
Good morning! Hopefully this hasnt already been discussed, and if it has, maybe somebody could point me to the thread, because I've done some searching to no avail.
When I recieve an MMS on my universale using t-mobile usa, the photos are always resized to 160x120 which is barely viewable with the vga display. Is there a setting I'm missing somewhere, or is this just t-mobile's standard behavior? Video files seem to go through just fine.
sk0t
30th August 2006, 08:46 PM
I don't have a Universal, but I had a similar issue on my Wizard when I would hard reset, but not apply the Cingular CAB's.
There are several registry keys that I used to correct this. I don't have them handy, but will dig them up when I get a chance for you.
sk0t
31st August 2006, 05:30 PM
These settings may help:
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\Capture]
"VideoRes"=dword:00000008
"PhotoRes"=dword:00000080
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\UI]
"SupportAutoSignature"=dword:00000000
"AllowSendReadReport"=dword:00000001
"AutoDisconnect"=dword:00000001
"AlphaTag"=""
"AlphaTagDispTxt"=""
"EnableReceivePrompt"=dword:00000001
"EnableReceiveNotify"=dword:00000002
"EnableDownloadedPrompt"=dword:00000001
"EnableDownloadedNotify"=dword:00000002
"EnableSentPrompt"=dword:00000001
"EnableSentNotify"=dword:00000002
"DownloadHomeNetworkOnly"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\UI\SizeLimit]
"SendLimit1"=dword:0004b000
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\8832]
"WAP2SendDefaultSize"=dword:0004b000
"WAP1SendDefaultSize"=dword:0004b000
"WAP1RecvDefaultSize"=dword:0004b000
"WAP1DefaultSize"=dword:0004b000
"WAP2DefaultSize"=dword:0004b000
"SendDefault"=dword:0004b000
"RecvDefault"=dword:0007d000
"GatewayPort"=dword:00000050
"WAP2RecvDefaultSize"=dword:05f5e0ff
"PacketSize"=dword:000003e8
"WAPType"=dword:00000001
Bear in mind I use these on my Wizard and on Cingular, so I don't know if they'll all apply or not. Also, on that last key, 8832 is my connection to the Cingular network. So your key may be named differently.
Hope that helps some.. Good luck!
chainsawbeer
2nd September 2006, 10:25 AM
Thanks for the reply guys! I"m a lil hesitant to start poking at the registry unless it's a confirmed fix on t-mo... er maybe I'll just do a backup and have a jumping point to unhose everything from. I dont suppose there's any other nice folks who've had similar experience?
sk0t
3rd September 2006, 10:55 PM
Unfortunately, I have no clue if anyone else has tried it, as I'm Cingular. But, if you do try, good luck! Perhaps, maybe you may wish to export your registry first, try it, and if it doesn't work, re-import the one you exported.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.