View Full Version : Receiving TINY Picture Messages!
marscandybars
13-03-2007, 12:25 AM
I am having a problem with picture messaging. When I receive them, they are only about 5 -10 kb and they are VERY tiny. Is there any way to set the phone to download the actual file size of the picture sent?
How I tested: I send a 95 kb picture to myself, and when it got sent back to me, it was only 5kb. However, when I sent the picture to my e-mail address, it received the entire 95 kb file. So I know there was no cap on the file size when i sent it, but why am i getting it back in a tiny 5kb? Any help would be most appreciated!
mfrazzz
24-03-2007, 07:54 PM
Ok, I'm going to update and bump this back up to see if there are any other reports. I'm also getting tiny pictures on all WM6 MMS messages I receive. I don't do a lot of MMS stuff, but my daughter sent me a 640x480 image and it came in as a thumbnail 160x120 size which is frustrating. I can send out images in full size from WM6, but all images coming into me are scaled.
I've verified that in the MMS settings, Photo Resolution is set to Original size (i've even set it to every other size and it still doesn't matter, all pics received are 160x120).
Is there anyone out there running WM6 that receives full size images? If so, which WM6 rom are you using? What version of Arcsoft is on your phone? I'd like to try to get to the bottom of this.
mfrazzz
24-03-2007, 11:00 PM
Just got off the phone with Cingular and HTC. Decided to call Cingular as I saw on another forum (for another type of phone) that if the celluar provider doesn't have the info on your phone then their system will scale pics to small images like 160x120. Cingular of course has no clue about this and claims its an issue with the device so they put me to HTC. HTC checks a few things then puts me back to Cingular...
What I can see is the message I'm sending has a size of 71K and contains a 640x480 image (by doing Info on the objects in the MMS composer of my sent messages). But the downloaded message is only 11K and the objects info shows the downloaded image is 160x120. So this tells me the scaling is happening elsewhere (I even turned off automatic download and I can see the header message I receive telling me that the message size is smaller than what I sent, so its already been scaled).
So is there something on our phones that send info up to the cell tower that tells it what type of phone this is? If so, could it be that WM6 is sending a code that isn't expected by the cell company, so they then scale it to the 160x120 size?
Here's a link to the forum note I found about this similar issue on a different phone. http://www.esato.com/board/viewtopic.php?topic=131824 In that thread, it just started working (so they are guessing the cell provider fixed something on their end).
Thoughts? Comments?
Just got off the phone with Cingular and HTC. Decided to call Cingular as I saw on another forum (for another type of phone) that if the celluar provider doesn't have the info on your phone then their system will scale pics to small images like 160x120. Cingular of course has no clue about this and claims its an issue with the device so they put me to HTC. HTC checks a few things then puts me back to Cingular...
What I can see is the message I'm sending has a size of 71K and contains a 640x480 image (by doing Info on the objects in the MMS composer of my sent messages). But the downloaded message is only 11K and the objects info shows the downloaded image is 160x120. So this tells me the scaling is happening elsewhere (I even turned off automatic download and I can see the header message I receive telling me that the message size is smaller than what I sent, so its already been scaled).
So is there something on our phones that send info up to the cell tower that tells it what type of phone this is? If so, could it be that WM6 is sending a code that isn't expected by the cell company, so they then scale it to the 160x120 size?
Here's a link to the forum note I found about this similar issue on a different phone. http://www.esato.com/board/viewtopic.php?topic=131824 In that thread, it just started working (so they are guessing the cell provider fixed something on their end).
Thoughts? Comments?
Most likely Cingular has a database of their "Official" phones and what resolutions they support. Their system is probably configured to send the small image to any phone that has no entry in the database. The only way you are probably going to get full size images is for cingular to add your model phone running win mobile 6 to their database of phones. My guess is this will be next to impossible to do so youll have to live with it or switch to a provider that wont limit your MMS picture sizes based on phone. If you can get enough wizard users to complain to Cingular they might do something about it.
mfrazzz
25-03-2007, 06:58 AM
Most likely Cingular has a database of their "Official" phones and what resolutions they support. Their system is probably configured to send the small image to any phone that has no entry in the database. The only way you are probably going to get full size images is for cingular to add your model phone running win mobile 6 to their database of phones. My guess is this will be next to impossible to do so youll have to live with it or switch to a provider that wont limit your MMS picture sizes based on phone. If you can get enough wizard users to complain to Cingular they might do something about it.
Yeah, the more I research this, the more I think this is likely the case. Cingular wants to send me a replacement phone (some guy called me back tonight :eek:) said, the guy I spoke to had talked to him aobut my issue, and he was authorizing a replacement for it. I kindly told him I'd have to think about it as I'm not ready to rebuild this phone (little do they know I've done that multiple times in the past few days ;).
Tempted to fall back to AKU3.3 and test it there (I didn't test MMS any). I've started questioning what WM6 is really buying me right now. Its been fun to play with. May have to switch back to see how it feels and then decide whether I stay on WM6 or not.
djaladin
25-03-2007, 03:54 PM
I'm actually using an 8525 Hermes and not an 8125 Wizard, but I had the exact same problem as you. I think the problem lies somewhere in the setup of the Cingular MMS, GPRS, and Media Net settings. I'm not positive about that, but I do know that (at least for me) my picture downsizing problem went away as soon as I used the Cingular cab file developed by shogunmark, which can be found in this thread.
http://forum.xda-developers.com/showthread.php?t=299393&page=2
So if any of you are on Cingular/AT&T and having the MMS picture sizing problem, try the cab. It may be just what your Wizard ordered!
mfrazzz
25-03-2007, 10:46 PM
http://forum.xda-developers.com/showthread.php?t=299393&page=2
So if any of you are on Cingular/AT&T and having the MMS picture sizing problem, try the cab. It may be just what your Wizard ordered!
Dude! This fixed my problem completely. Just sent and received a couple of 640x480 images with no issues! Thanks a ton for this info, I honestly thought running WM6 was the problem, but it was in how I was setting up my connections... Very very cool ;)
FWIW: I actually went to the first post of the thread (they are keeping that one updated) and used the second cab in that post:
Cingular WAP MediaNet MMS Settingsv2.cab . I also removed the stuff I added so there weren't extra settings.
I'm actually using an 8525 Hermes and not an 8125 Wizard, but I had the exact same problem as you. I think the problem lies somewhere in the setup of the Cingular MMS, GPRS, and Media Net settings. I'm not positive about that, but I do know that (at least for me) my picture downsizing problem went away as soon as I used the Cingular cab file developed by shogunmark, which can be found in this thread.
http://forum.xda-developers.com/showthread.php?t=299393&page=2
So if any of you are on Cingular/AT&T and having the MMS picture sizing problem, try the cab. It may be just what your Wizard ordered!
Tested and working!!! Thank you so much!
mfrazzz
27-03-2007, 06:51 PM
For those of you on services other than Cingular, you may want to check out this thread and see if the cab(s) here help on your particular service:
http://forum.xda-developers.com/showthread.php?t=299023
If you try it, report back here with your findings.
I7oobie
27-03-2007, 08:09 PM
For those of you on services other than Cingular, you may want to check out this thread and see if the cab(s) here help on your particular service:
http://forum.xda-developers.com/showthread.php?t=299023
If you try it, report back here with your findings.
I am getting the same problems, only with TMO. I'm running Faria's Real Thing WWE Rom. I also can't send out any MMS, just receive thumbnailed MMS....
demontefixo
27-03-2007, 09:04 PM
I am getting the same problems, only with TMO. I'm running Faria's Real Thing WWE Rom. I also can't send out any MMS, just receive thumbnailed MMS....Are your MMS settings correct? TMo's instructions have a mistake in them for the IP address. Check and make sure your IP address ends with .50
--M
I7oobie
27-03-2007, 09:28 PM
Are your MMS settings correct? TMo's instructions have a mistake in them for the IP address. Check and make sure your IP address ends with .50
--M
Yup, got that all set up. At first, I had no MMS, I then did the steps you are talking about, and now I receive MMS, but thumbnails...
T-Mobile MDA
IPL/SPL 2.26
Faria's Real Thing WWE WM6
Projectile
28-03-2007, 01:59 AM
I am on TMO US, I can send and recieve MMS.... But I have the small video & pic issue. Will try fooling around with the settings, but it seems simular to what the Cingular folks were having.
mUns Build..
Tmobile MDA
demontefixo
28-03-2007, 06:52 AM
Yup, got that all set up. At first, I had no MMS, I then did the steps you are talking about, and now I receive MMS, but thumbnails...
T-Mobile MDA
IPL/SPL 2.26
Faria's Real Thing WWE WM6hmm, are the options within MMs set to send "original" size?
--M
I7oobie
28-03-2007, 02:44 PM
hmm, are the options within MMs set to send "original" size?
--M
I can check that, but that still wouldn't explain not receiving any MMS... I know there is a CAB file to fix it, but it's for Cingular... I suppose it wouldn't be wise to try that, would it?:eek:
marscandybars
28-03-2007, 05:27 PM
It is set to send "original size" but that wont affect "receiving". My MMS sends the entire file size, but all pictures received are 160x120 or smaller. Its annoying.
I have T-mobile.
FYI, my mms works fine with WM5. I first thought that maybe T-mobile had a server issue and downsized pix. But then when i went back to Xelecin's custom 2.6 rom, it worked fine. I even tried the standard t-mobile 2.26 rom. I am only getting small pix with WM6
falconeyez
28-03-2007, 07:12 PM
Hey guys I was looking at this problem with the tiny pictures coming through on the MMS. I didn't have the problem on MBE but I flashed Not Too Smart's ROM and found this problem. One of the possible solutions I came up with was to unlock the Extended Rom using the UNLOCK EXTENDED ROM WIZARD and the running the setup file to restore this to a T-Mobile (branded?) Style phone. It will keep WM6 on there but add on the other features from the T-Mobile WM5 ROM such as OZ instant Messaging, T-Zones, Hot Spot Locator, as well as all the default settings for SMS, MMS, and EDGE.
As soon as I can get someone to send me an MMS, I'll let you know if it worked.
I7oobie
28-03-2007, 07:17 PM
Hey guys I was looking at this problem with the tiny pictures coming through on the MMS. I didn't have the problem on MBE but I flashed Not Too Smart's ROM and found this problem. One of the possible solutions I came up with was to unlock the Extended Rom using the UNLOCK EXTENDED ROM WIZARD and the running the setup file to restore this to a T-Mobile (branded?) Style phone. It will keep WM6 on there but add on the other features from the T-Mobile WM5 ROM such as OZ instant Messaging, T-Zones, Hot Spot Locator, as well as all the default settings for SMS, MMS, and EDGE.
As soon as I can get someone to send me an MMS, I'll let you know if it worked.
But, I'm running the Faria V5.0 Extended Rom already... Does that matter? Also, will I be able to do this fix with Vista, I used a buddies computer to flash the rom...
mfrazzz
28-03-2007, 07:37 PM
As soon as I can get someone to send me an MMS, I'll let you know if it worked.
Just send one to yourself, or PM me and I'll send you an MMS.
falconeyez
28-03-2007, 07:38 PM
But, I'm running the Faria V5.0 Extended Rom already... Does that matter? Also, will I be able to do this fix with Vista, I used a buddies computer to flash the rom...
I don't know. I would assume that Faria's Etended ROM would have over write the T-Mobile extended ROM.
I have the files in a zipped folder, but for some reason I keep getting upload errors. Any help?
Just unzip the file and throw the unzipped folder onto an SD card. When the card is in your device, launch the autorun program. Hopefully it should work. I would probably delete all the previous MMS settings, and GPRS settings that you placed previously.
falconeyez
28-03-2007, 08:06 PM
Yeah, don't do what I said, because now I'm not getting any messages, and I can no longer edit the settings for MMS. Sorry.
I7oobie
28-03-2007, 08:51 PM
Yeah, don't do what I said, because now I'm not getting any messages, and I can no longer edit the settings for MMS. Sorry.
It was a good try, and thanks. No anyone else for a shot?
I7oobie
29-03-2007, 04:01 PM
BUMP. Someone please help.:o
fryman
29-03-2007, 04:31 PM
I'm actually using an 8525 Hermes and not an 8125 Wizard, but I had the exact same problem as you. I think the problem lies somewhere in the setup of the Cingular MMS, GPRS, and Media Net settings. I'm not positive about that, but I do know that (at least for me) my picture downsizing problem went away as soon as I used the Cingular cab file developed by shogunmark, which can be found in this thread.
http://forum.xda-developers.com/showthread.php?t=299393
So if any of you are on Cingular/AT&T and having the MMS picture sizing problem, try the cab. It may be just what your Wizard ordered!
This worked for me on cingular. djaladin thanks for the link!
Maybe if you T-Mo guys run the second cab (http://forum.xda-developers.com/attachment.php?attachmentid=35979&d=1174855986)and then go back in a manualy change the settings to T-mobile:
If you are in the US try:
Gateway: 216.155.165.50
Port: 9201
Server: http://216.155.174.84/servlets/mms
Connects via: My ISP or whatever
Let me know if this helps :)
I7oobie
29-03-2007, 04:58 PM
This worked for me on cingular. djaladin thanks for the link!
Maybe if you T-Mo guys run the second cab (http://forum.xda-developers.com/attachment.php?attachmentid=35979&d=1174855986)and then go back in a manualy change the settings to T-mobile:
If you are in the US try:
Gateway: 216.155.165.050
Port: 9201
Server: http://216.155.174.84/servlets/mms
Connects via: My ISP or whatever
Let me know if this helps :)
Trying now, will report back...
I7oobie
29-03-2007, 05:07 PM
Nope, didn't work
marscandybars
29-03-2007, 05:17 PM
Also, i believe that US gateway is 216.155.165.50
NOT ".050"
The zero on front of the 50 made a huge difference for me. With .050 it didn't connect
I7oobie
29-03-2007, 08:34 PM
Also, i believe that US gateway is 216.155.165.50
NOT ".050"
The zero on front of the 50 made a huge difference for me. With .050 it didn't connect
Yup, I did that, now I can receive the little guys, but not send anything...:eek:
fryman
30-03-2007, 03:31 PM
Also, i believe that US gateway is 216.155.165.50
NOT ".050"
The zero on front of the 50 made a huge difference for me. With .050 it didn't connect
Sorry for the confusion I got the settings off the Tmo website?? I edited my post but I guess it doesn’t matter since the fix didn’t work. I looked into the different settings and the reason the new cab worked on Cingular is because it uses different gateway and server addresses. So I guess it is just a problem on the Tmo end…sorry.
Projectile
30-03-2007, 07:24 PM
I think the problem is with WM6 and how it identifies itself to the Cells, I can flash the previous Rom without the T-Mobile customizations, enter the setings manually and it works. If you look at the Cingular thread, they change a few things other then the Server and Gateway....
demontefixo
30-03-2007, 07:33 PM
Sorry for the confusion I got the settings off the Tmo website?? I edited my post but I guess it doesn’t matter since the fix didn’t work. I looked into the different settings and the reason the new cab worked on Cingular is because it uses different gateway and server addresses. So I guess it is just a problem on the Tmo end…sorry.Try internet2.voicestream.com instead of internet3.... or vice versa. Also what port are you using?
--M
demontefixo
30-03-2007, 07:36 PM
And more info just for reference:
The different access points that T-mobile commonly uses are:
wap.voicestream.com: used for T-Zones - allows SMTP (sending email); WAP/HTTP (browsing); POP3/IMAP4 (receiving email)
internet2.voicestream.com: unlimited Internet -- SMTP, WAP/HTTP, POP3/IMAP4; all other protocols; secure protocols
internet3.voicestream.com: unlimited Internet plus VPN -- provisioned & used primarily for VPN access plus all other protocols
--M
marscandybars
31-03-2007, 03:19 AM
I think the problem is with WM6 and how it identifies itself to the Cells, I can flash the previous Rom without the T-Mobile customizations, enter the setings manually and it works. If you look at the Cingular thread, they change a few things other then the Server and Gateway....
Well i know this much, it is NOT a server issue with t-mobile. When i flash to xelecin's 2.26 custom rom or use the factory rom, MMS works PERFECTLY and i get all my MMS messages in full size. But the settings for both were locked, and possibly there is some small detail that i missed?
But ever since i started with all the cooked wm6 roms, i've been getting the super tiny picture messages :(.. boo...
marscandybars
01-04-2007, 06:28 PM
Xelecin's custom WM5 2.26 rom has a cab that auto installs when you first install the rom. It is the t-mobile customization cab. His rom is the only customized rom that i was able to receive full size messages with.
For T-mobile USA customers try this and tell me if it works out for you:
1. Install t-mobile_network_customizations.cab then soft reset
2. Menu > Tools > Options > MMS> Servers
You will then see a profile called "Default" (it will have very weird settings in the boxes; simply write over them)
Open it and edit as follows
Server Name: Default (or any will do, but i usually leave this as is)
Gateway: 216.155.165.50
Port number: 8080
Server address: http://216.155.174.84/servlets/mms
Connect via: T-mobile GPRS (this should already be pre-set for you if you installed the cab)
Sending size limitation: 292K
WAP version WAP 2.0
I have tested this with BOTH my MDA and my New 8525. Without it, i get TINY picture messages. To clear things up, receiving tiny picture messages is NOT a T-mobile server downsizing issue. There was something that was skipped over when the WM6 roms were cooked. Which is why simply editing an access point and creating a MMS profile will NOT work. This cab file does miracles! ENJOY!
demontefixo
01-04-2007, 09:29 PM
Xelecin's custom WM5 2.26 rom has a cab that auto installs when you first install the rom. It is the t-mobile customization cab. His rom is the only customized rom that i was able to receive full size messages with.
For T-mobile USA customers try this and tell me if it works out for you:
1. Install t-mobile_network_customizations.cab
2. Make sure your mms server settings are as follows:
Create or replace any profile and make sure to set it as a default
Server Name: T-Mobile MMSC (Any name will do)
Gateway: 216.155.165.50
Port number: 8080
Server address: http://216.155.174.84/servlets/mms
Cnnect via: T-mobile GPRS (this will be set for you if you installed the cab)
Sending size limitation: 292K
WAP version WAP 2.0
If this doesn't work, then i'm for sure that its not a settings problem. I really do believe that it is some compatibility issue with WM6 and MDAs. I just upgraded to a 8525, and these settings now work with WM6 Black. So if these settings don't work, then i think there is something in the cooked roms that is not quite right.Tried it. Only thing to add is: remember to reset after installing. BUT, no fix to picture scaling.
I am beginning to think that TMobile scales them on the server (they just pick on those of us with WM6). Sending seems to work no problem, it is just the incoming that get all "goofy". The odd thing also is that the .jpg files "play" when you view them...almost as if they are a small video as opposed to a static image. Definately on of those things that makes you go "hmmm".
I think I'll call ArcSoft on Monday and see if I can get a description on the registry settings. (unless someone already has them and wants to post them :) ).
--M
marscandybars
01-04-2007, 10:50 PM
Tried it. Only thing to add is: remember to reset after installing. BUT, no fix to picture scaling.
I am beginning to think that TMobile scales them on the server (they just pick on those of us with WM6). Sending seems to work no problem, it is just the incoming that get all "goofy". The odd thing also is that the .jpg files "play" when you view them...almost as if they are a small video as opposed to a static image. Definately on of those things that makes you go "hmmm".
I think I'll call ArcSoft on Monday and see if I can get a description on the registry settings. (unless someone already has them and wants to post them :) ).
--M
T-mobile doesn't scale them. If you flash to Xelecins 2.26 custom WM5 rom, you will see that you get the FULL sized pictures. I tried this on my MDA and my 8525, and it works like a charm :) I redid the directions. Follow them step by step and u just might run into a miracle ;)
demontefixo
02-04-2007, 12:55 AM
T-mobile doesn't scale them. If you flash to Xelecins 2.26 custom WM5 rom, you will see that you get the FULL sized pictures. I tried this on my MDA and my 8525, and it works like a charm :) I redid the directions. Follow them step by step and u just might run into a miracle ;)But they must scale them, lol. I tried it again, I am not seeing the "default" profile, just the PictureMessaging one that I had previously. Weird. I get a positive install message with the exception of the "this app was meant for a previous version of WM..." Maybe I'll just reflash the whole thing and try from scratch.
--M
marscandybars
02-04-2007, 01:39 AM
But they must scale them, lol. I tried it again, I am not seeing the "default" profile, just the PictureMessaging one that I had previously. Weird. I get a positive install message with the exception of the "this app was meant for a previous version of WM..." Maybe I'll just reflash the whole thing and try from scratch.
--M
Reflashing should help. I tried this cab only newly flashed devices :p. I am running WM6 on my MDA (Xplore 1.0) AND my 8525 (WM6 Black Ed). And its working :)
In my phone it creates another profile called "default". It may be named differently in your phone (just a hunch). But just look for another profile that wasn't there prior to the cab install :)
demontefixo
02-04-2007, 04:29 AM
Reflashing should help. I tried this cab only newly flashed devices :p. I am running WM6 on my MDA (Xplore 1.0) AND my 8525 (WM6 Black Ed). And its working :)
In my phone it creates another profile called "default". It may be named differently in your phone (just a hunch). But just look for another profile that wasn't there prior to the cab install :) :( no such luck. I flashed back to TMo's and the to WM6. Nada.
Where is the .cab writing to files to?
--M
marscandybars
02-04-2007, 06:04 AM
:( no such luck. I flashed back to TMo's and the to WM6. Nada.
Where is the .cab writing to files to?
--M
I have no idea... Xelecin made it last year. Which rom are you using?
demontefixo
02-04-2007, 08:43 AM
I have no idea... Xelecin made it last year. Which rom are you using?Faria's Crossbow
I7oobie
02-04-2007, 02:22 PM
Faria's Crossbow
I'm using Faria's also. As of yet, I have not tried this cab. Will let you know.
marscandybars
03-04-2007, 03:04 AM
I tried this yet again with another cousin's MDA. It worked like a charm.
We just reflashed his phone today to Xplore 1.1 :)
I've tried it with farias, and it works as well, so im sure its not rom specific :-p
demontefixo
03-04-2007, 04:32 AM
I tried this yet again with another cousin's MDA. It worked like a charm.
We just reflashed his phone today to Xplore 1.1 :)
I've tried it with farias, and it works as well, so im sure its not rom specific :-pI hate you... LOL
I flashed, reflashed, flashed some more... bingo success. It is strange that I am not getting the "default" MMS server setting. I just went to the xPL 3.08 and the 2.61 radio and those work well so far, just small pics still. I'll give it a few days and try again. Maybe 17oobie will have some success.
--M
marscandybars
03-04-2007, 04:43 AM
I hate you... LOL
I flashed, reflashed, flashed some more... bingo success. It is strange that I am not getting the "default" MMS server setting. I just went to the xPL 3.08 and the 2.61 radio and those work well so far, just small pics still. I'll give it a few days and try again. Maybe 17oobie will have some success.
--M
Heh... i really don't know if this will work... but try reflashing.. then delete any profiles in the MMS settings that way it is COMPLETELY blank. The install the cab. DO NOT RESET. Check the MMS server settings and see if a default setting comes up.
When i wrote the first posting, note i didn't have the instructions to soft reset. Thats cuz i didn't (and actually forgot to) soft reset :p ... but the other devices i did after that tutorial i soft reseted. But try it without soft resetting and see if anything pops up. report back
:)
If you initially don't see anything, close out of the MMS settings, then open up the server settings AGAIN. Usually the first time i look through the server profiles, i dont see the default menu. When i close out of it and open it up again, it mysteriously appears... maybe u might run into the same luck ;)
myk_83
19-04-2007, 12:57 PM
I'm using Faria's REAL THING rom and have also just noticed that I'm receiving tiny pictures! The only settings/cabs that I've seen so far appear to be for Cingular or T-Mobile users. I'm on O2 in the UK, so I was wondering if any of those cabs would work, or if anyone knew of a way to make it work on my network?
Intergalactic
21-04-2007, 08:46 PM
The MMS T-Mobile Messaging settings works like a charm with machine like precision. I'm using the Wizard_NTS_1010811_21911 ROM. What I like best about this ROM, it does not do the heck up, the freeze or the stop and go, nor do you have to do a lot of soft resets, it runs very smooth all the time. Another thing the 2.19 radio is very powerful, it does wonders for my mobile Slingbox SlingPlayer mobile client. My cellular signal strength has sky rocked up very high, which has increase video resolution on my Wizard when I'm using WAN connecting back home to my Slingboxes.
marscandybars
22-04-2007, 08:14 PM
Here you go guys... I have tried this with over 10 phones now, so it should and WILL work. Post back if it doesn't. But like i said, this has worked consistently for me.
To prevent any mixups, install these cabs after a NEW rom flash. This has worked for all the custom roms i have used.
1. Install t-mobile_network_customizations.cab (119.5 KB)
2. Install T-Mobile_MMS.cab (1.3 KB)
Then do a soft reset, and BAM! You will be receiving FULL size text messages. Feel free to pm me if you have any issues.
If you are sending a picture back to yourself to test it, make sure that your outgoing file settings in the MMS settings are set to 640x480 or Original, unless u prefer to send small picture messages. Note the file size before sending it, and you should see the same file size when you receive the picture back. If you have someone else sending the picture to you, make sure their phone is capable of sending large pictures, as some phones downscale before sending.
A FIX FINALLY!
SiLeNtKiLLa
23-04-2007, 03:26 AM
Just to let you guys know, the previous post on how to get this thing to work has worked for me as well. I reflashed, xplorer 1.1, then installed tmobile network customiztions cab file before install anything else, and it works for me, no more little pics, the mms porgram looks waaayy different now, but its working....
Going to try the new posted files and see if they work.
The_Wizard
24-04-2007, 01:25 AM
Success for me as well... I didn't install the cabs to a clean flash so i had to delete the T-Mobile GPRS connection that was created by the 1st cab and then recreate it... but once i configured the MMS server profile I was good to go...
duprade
02-08-2007, 07:05 AM
I'm having the same problem everyone else has ... I have a T-Mobile Wing (P4350 Herald) running WM6, and I can send people MMS pics without any problems and they receive them just fine, but I am receiving scaled down versions of the pictures.
Even when I send a picture to myself, I'll send a 20kb picture, and receive an 11Kb smaller version.
I've spent a few hours on the phone with T-mobile working on this, and first they screwed up the ability for me to even receive MMS ... when I would send myself one, it would come back as "rejected" ... then after we finally got that to work, we're still at step one.
The technician sent me to the Tmobile store to exchange my phone, since it of course "must be a defective unit" since the geniuses at tech support weren't able to fix it... so I came home today with the new unit and guess what? SAME DAMN THING.
Just called Tmobile again ... their system is down, so they can't follow their little on screen teleprompter BS, so a few guys talked and the supervisor told the guy to tell me this was normal! I told him that was BS, because i've been looking the issue up online, and they pretty much said to call back when their systems were back up and running. :mad:
marscandybars
02-08-2007, 06:31 PM
Please see my post #48!
Just install the two cabs and ur set!
duprade
06-09-2007, 05:32 AM
that didn't work for me.
chainsawbeer
12-09-2007, 06:07 PM
w00000 you guys are AMAZING. Didnt even require a reflash. I deleted all of my gprs profiles and cleared out the mms settings. soft reset. installed the cabs in order. changed the mms settings from the verizon entries in the "Default" mms profile over the the tmo settings. VOILA!!! Full size MMS messages! w00t! BTW This fix worked on my HTC Advantage running the OEM ROM 1.25.405.2 radio 1.38.00.00. I've been giving some thought to the upgrade to WM6, but with this working so smoothly Im not convinced it's a good idea.
joemanb
13-09-2007, 01:01 AM
those 2 cabs didn't work for me either, but this one does (for me) I'm also running WM6.
DISREGARD check post #57
Pumpiron579
13-09-2007, 06:29 AM
Try this. It is the best. Make sure your MMS settings are connected to MEdia Net
joemanb
13-09-2007, 04:21 PM
I think I've got it figured out for T-MobileUSA on WM6..disregard my previous post.
First download Lurches CAB file for your plan ($5.99, $29.99, or $39.95) here:
http://forum.xda-developers.com/showthread.php?t=311446&highlight=lurch
install Lurches Cab then soft reset
Install "MMS auto config t-mobile.cab" then soft reset
Install "T-Mobile UStPPC.CAB" then soft reset
Set MMS picture size to Original
In 'servers' 'T-Mobile MMSC' 'Connect Via' field select 'T-mobile MMS'
good to go.
Let us know if this works
Update:
I've messed with this all day and this is what i've come up with:
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader]
"Accept-Charset"="us-ascii;utf-8;iso-10646-ucs-2;ISO-8859-1"
"Accept"="application/vnd.wap.mms-message;*/*;"
"User-Agent"="prodigy/arcsoft-mmsua-ppc-3.0.0.xx"
"Profile"="http://www.htcmms.com.tw/gen/wizard-2.0.xml"
"Accept-Language"="ge"
This is all I've needed (it might be just one or the other etc...), Instead of installing a bunch of cabs that are doing who knows what.
Try it and let us know...
So now I'm getting full sized pics!...I've NEVER got full sized pics, I've always though that it was just the cheesy way the networks worked...Until I encountered this thread.
I'm not sure, but these MAY NOT be carrier specific. they might work on all services because these reg keys are included with arcsoftmms rgu files in cook packages, but the values are different.
I'm using arcsoftmms 3.0.7.19
I've made a cab file if anyone's interested..WSPHeader.cab. Just use this ONE cab if your settings are aready the way you want them and your only issue is picture size
dkb218
14-09-2007, 05:09 PM
Not sure which CAB fixed my problem but I am now getting pics at the size sent to me!!!
duprade
23-09-2007, 12:32 AM
Same here!! I'm not sure which CAB fixed it, but I installed all 3 and at first it didn't work, but after a reset or 2, it fixed itself.
thewingzman
03-10-2007, 08:45 AM
I think I've got it figured out for T-MobileUSA on WM6..disregard my previous post.
First download Lurches CAB file for your plan ($5.99, $29.99, or $39.95) here:
http://forum.xda-developers.com/showthread.php?t=311446&highlight=lurch
install Lurches Cab then soft reset
Install "MMS auto config t-mobile.cab" then soft reset
Install "T-Mobile UStPPC.CAB" then soft reset
Set MMS picture size to Original
In 'servers' 'T-Mobile MMSC' 'Connect Via' field select 'T-mobile MMS'
good to go.
Let us know if this works
Update:
I've messed with this all day and this is what i've come up with:
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader]
"Accept-Charset"="us-ascii;utf-8;iso-10646-ucs-2;ISO-8859-1"
"Accept"="application/vnd.wap.mms-message;*/*;"
"User-Agent"="prodigy/arcsoft-mmsua-ppc-3.0.0.xx"
"Profile"="http://www.htcmms.com.tw/gen/wizard-2.0.xml"
"Accept-Language"="ge"
This is all I've needed (it might be just one or the other etc...), Instead of installing a bunch of cabs that are doing who knows what.
Try it and let us know...
So now I'm getting full sized pics!...I've NEVER got full sized pics, I've always though that it was just the cheesy way the networks worked...Until I encountered this thread.
I'm not sure, but these MAY NOT be carrier specific. they might work on all services because these reg keys are included with arcsoftmms rgu files in cook packages, but the values are different.
I'm using arcsoftmms 3.0.7.19
I've made a cab file if anyone's interested..WSPHeader.cab. Just use this ONE cab if your settings are aready the way you want them and your only issue is picture size
worked like a charm.. im using the PDAviet Wing rom, and used total commander and just followed the above :
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader]
"Accept-Charset"="us-ascii;utf-8;iso-10646-ucs-2;ISO-8859-1"
"Accept"="application/vnd.wap.mms-message;*/*;"
"User-Agent"="prodigy/arcsoft-mmsua-ppc-3.0.0.xx"
"Profile"="http://www.htcmms.com.tw/gen/wizard-2.0.xml"
"Accept-Language"="ge"
had to add some text where there was none be4, tested by sending my self an mms and bang.. done.. thank u so much, ur the man.
tomix
04-10-2007, 03:16 PM
About TINY picture massages! I read your posts and try to fix this issue in my phone too. Finally my device can send and receive everything (max. 300K). But still have a problem (2 problems)!
1.: if the message size is 300K, my device try to send and then say that there was a problem. (I SHIT ON IT) :D
2.: if i start to compose a multimedia message and insert a picture which is bigger than 300K, the software offer to reduce the picture size and/or picture quality, then you have to tap the compress job, after this procedure the big picture will shown as 0K and the whole message size is 1K/300K! (SHIT ON IT TOO) :eek:
My hack for MMS receiving in my country - TMO Hungary
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader]
"Accept-Charset"="us-ascii;utf-8;iso-10646-ucs-2;ISO-8859-1"
"Accept"="image/bmp;image/x-bmp;image/x-ms-bmp;image/vnd.wap.wbmp;image/gif;image/jpeg;image/jpg;image/png;audio/amr;audio/x-amr;audio/mid;audio/midi;audio/sp-midi;audio/x-mid;audio/x-midi;audio/wav;audio/x-wav;audio/3gpp;audio/mp4;video/3gpp;video/mp4;text/x-vCalendar;text/x-vCard;text/plain;application/smil;application/vnd.wap.multipart.related;application/vnd.wap.multipart.mixed;application/vnd.oma.drm.message;application/vnd.wap.mms-message;"
"User-Agent"="MDA Vario/2.0/arcsoft-mmsua-3.2.0.xx"
"Profile"="http://www.htcmms.com.tw/tmo/mdavario-2.0.xml"
"Accept-Language"="en"
"x-wap-profile"="http://www.htcmms.com.tw/tmo/mdavario-2.0.xml" (i have this by default!)
joemanb
06-10-2007, 05:37 PM
QUOTE:1.: if the message size is 300K, my device try to send and then say that there was a problem. (I SHIT ON IT)
I was having the problem of failed sends over 100k until I set the WAP version to 2.0 (Don't shit on it anymore!)
jizital
16-10-2007, 01:29 AM
worked like a charm.. im using the PDAviet Wing rom, and used total commander and just followed the above :
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader]
"Accept-Charset"="us-ascii;utf-8;iso-10646-ucs-2;ISO-8859-1"
"Accept"="application/vnd.wap.mms-message;*/*;"
"User-Agent"="prodigy/arcsoft-mmsua-ppc-3.0.0.xx"
"Profile"="http://www.htcmms.com.tw/gen/wizard-2.0.xml"
"Accept-Language"="ge"
had to add some text where there was none be4, tested by sending my self an mms and bang.. done.. thank u so much, ur the man.
i edited the registry with that info on my wing and i am now able to receive full size mms messages. thank youuuuuuu
djphredee
21-10-2007, 05:57 AM
this worked AWESOME!! THANK YOU SOOO MUCH! now i can die happy =)
tadevinney
26-10-2007, 07:31 AM
worked on my wing with original WM6 rom. Thanks all
boldfacelies
28-10-2007, 03:16 AM
tmobile, usa, wm6, pictures are fine.
sent 42.5k
recieved 43k
bbrain
31-10-2007, 08:27 AM
would this fix work on a htc s710?
jay-dub377
17-12-2007, 02:20 AM
installed all 4 cabs listed in this thread and soft reset then change settings to carrier specific. but still no luck. it has to be something with ppc's and smartphones because no other phones have this problem. I've had several differnt phones and never encountered this problem till i got my 8125. any help would be appreciated
jay-dub377
17-12-2007, 02:21 AM
:confused: installed all 4 cabs listed in this thread and soft reset then change settings to carrier specific. but still no luck. it has to be something with ppc's and smartphones because no other phones have this problem. I've had several differnt phones and never encountered this problem till i got my 8125. any help would be appreciated
bshakil
07-02-2008, 02:04 AM
Hello
First of all i would like to mention that i live in Saudi Arabia so dere is no cingular , Tmobile here .. We have Two Networks called STC and MOBILY
I have read all the posts in this thread. and it still doesnt solve the problem for me.
But it guided me towards the solution so i figured a way out myself.
First of all these all solutions are Carrier Dependent. but in a way or other its doing the same thing.
There are two small points of get a hold on the thing.
First What are all these cabs doing and how its solving problems for some guys and not all..
Second How it can solve your problem
Answer to the first question is ...
These Cabs are changing your registry (Specifically Two Keys)
1.User-Agent
2.Profile (or "X-WAP-Profile" Which was in my case so i renamed it to "Profile")
Lets try to get into a little detail so we can better understand whats happening here.Skip it if you want the solution only
What is happening is that your operator's MMSC is performing content adaptation before delivering the message to your device. What that means is that the MMSC is making changes to the content to "better" adapt it to the receiving device.
At least that is the theory behind it ... different devices have different capabilities ... different screen sizes ... different limits on the maximum image or message size that they can handle.
So in theory, the MMSC is performing a service, and scaling down the image so that it is usable when you receive it.
The reality, however, is that the content adaptation performed by most operator MMSCs is poor ... and ends up diminishing the user experience.
We all know that camera phone picture quality is relatively poor (but improving), but arbitrarily scaling pictures down to 160x120 makes the situation worse.
So ... in a situation like this, the only solution is to try to figure out how to bypass or alter the mobile operator MMSC content adaptation.
Usually, if an image is being scaled down to 160x120, this is what you'd call a "lowest common denominator" size ... that is to say, the smallest image size that is required to be supported by a device that supports MMS.
If the MMSC is scaling down images to the "lowest common denominator", then this usually means that the MMSC does not know what type of device is on the receiving end, so it is assuming that it is the most limited type of device.
In my case, with the receiving device is HTC TYTN 2,and this is really new device and HTC is not popular here. 90% of Saudi PPL Buy Nokia Phones so it does kind of make sense that the operator MMSC does not know what type of device is on the receiving end.
Solution
As in my case Nokia is the Most Common Choice of Saudi Ppl so i checked the SMS on my Friends Nokia N95 and it was working Perfect
So the solutions for my Problem was to change my Mobile`s User Agent and Profile to Nokia N95`s User Agent and Profile
Nokia N95:
User-Agent: NokiaN95/11.0.026; Series60/3.1 Profile/MIDP-2.0 Configuration/CLDC-1.1
Profile: "http://nds1.nds.nokia.com/uaprof/NN95-1r100.xml"
When i did that TADA... MMS Tiny Size Problem Solved in an instance
you can find UserAgent of nearly all the Mobile Phones on the internet e.g.
Motorola KRZR:
User-Agent:MOT-K1/08.22.07R MIB/BER2.2 Profile/MIDP-2.0 Configuration/CLDC-1.1 EGE/1.0
Profile: "http://motorola.handango.com/phoneconfig/k1/Profile/k1.rdf"
Blackberry 8800:
User-Agent: BlackBerry8800/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100
Profile: http://www.blackberry.net/go/mobile/profiles/uaprof/8800/4.2.1.rdf
So go ahead ... change these values till you find the one that is supported by your Carrier...
This way .. no matter where you live or what Carrier you use.. You can solve this MMS Issue...
Hope This Helps
hottnikkz
11-03-2008, 03:22 PM
worked like a charm.. im using the PDAviet Wing rom, and used total commander and just followed the above :
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader]
"Accept-Charset"="us-ascii;utf-8;iso-10646-ucs-2;ISO-8859-1"
"Accept"="application/vnd.wap.mms-message;*/*;"
"User-Agent"="prodigy/arcsoft-mmsua-ppc-3.0.0.xx"
"Profile"="http://www.htcmms.com.tw/gen/wizard-2.0.xml"
"Accept-Language"="ge"
had to add some text where there was none be4, tested by sending my self an mms and bang.. done.. thank u so much, ur the man.
Thanks, yours and joemanb's settings worked for me! Also, bshakil's post was very informative and explains it very well!
One thing to note, I think the max may be 1024x768 with these settings? I received one sent from a phone that took a pic with a resolution of 1280x968 and I received it at 1024x768, 242k which is less than the 300k max?? I can live with it I'm just throwing it out there for topic. Thanks again everyone!
cybrnetico
17-03-2008, 07:08 AM
thank you joemanb for the wspheader.cab work liked a charm on my wing.
hottnikkz
17-03-2008, 01:07 PM
Thanks, yours and joemanb's settings worked for me! Also, bshakil's post was very informative and explains it very well!
One thing to note, I think the max may be 1024x768 with these settings? I received one sent from a phone that took a pic with a resolution of 1280x968 and I received it at 1024x768, 242k which is less than the 300k max?? I can live with it I'm just throwing it out there for topic. Thanks again everyone!
Ok I tried from several different phones, the 1024x768 appears to be a limit of the 1st phone I tried sending with. All the other phones send to my wizard in whatever form they were originally sent in. Thanks again everyone!
majeede
17-05-2008, 08:10 PM
Ok guys please help me out here, i have a unlocked BlackJack 2 from ATT and im using Tmobile on it, ok I recieve small pics on my mms, is there some kind of cab or settings to change that please. help me
Tylerspilker
05-10-2008, 06:40 AM
So I have tried following many of your advice, and I was really excited to read that the tiny images weren't the fault of having a "younger" mobile provider: Tmobile
A lot of the CABs wont work for my blackjack though.
Here is what I use:
Windows Mobile 6.0 (fresh ROM from samsung)
Blackjack I i607
Tmobile
I can't get the internet settings cab to take and the others dont seem effective either.
I can manually set up my connections so i can send/recieve mms, and use data, however when i edit the registry settings listed above 2 of the strings arent there, so i added them, and it doesnt change the way anything operates, even when i reboot.
Any advice for me? I dont have a PPC device.
Tylerspilker
06-10-2008, 12:55 AM
So I have tried following many of your advice, and I was really excited to read that the tiny images weren't the fault of having a "younger" mobile provider: Tmobile
A lot of the CABs wont work for my blackjack though.
Here is what I use:
Windows Mobile 6.0 (fresh ROM from samsung)
Blackjack I i607
Tmobile
I can't get the internet settings cab to take and the others dont seem effective either.
I can manually set up my connections so i can send/recieve mms, and use data, however when i edit the registry settings listed above 2 of the strings arent there, so i added them, and it doesnt change the way anything operates, even when i reboot.
Any advice for me? I dont have a PPC device.
Here are the pictures:
This is the original image, you can see it is 99kb
http://lh5.ggpht.com/TylerSpilker/SOlRAocpOTI/AAAAAAAAAM0/613wjxjBFIs/1.JPEG
This is the image as a recieve it (I sent it to myself, but it applies the same when i recieve them thru MMS from anyone. It doesn't appear to be carrier specific, but WM specific, as some people have fixed it on PPC devices.
http://lh5.ggpht.com/TylerSpilker/SOlRAt8tLNI/AAAAAAAAAM8/9g-wiM-YaS0/2.JPEG http://lh5.ggpht.com/TylerSpilker/SOlRA1sUpAI/AAAAAAAAANE/eSokrJtPr_I/3.JPEG
This is the file size as recieved:
http://lh6.ggpht.com/TylerSpilker/SOlRA7U5BEI/AAAAAAAAANM/LRD75PZ8vQE/4.JPEG
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.