Whats the word on sending mms on sprint through android on a vogue? im able to receive but i can't send.
It's possible to get it to "send"....
Go to Menu > Settings > Wireless controls > Mobile networks > Access Point Names
Hit Menu > New APN
Name: MMS
APN: MMS
MMSC: http://63.215.195.152/servlets/mms
MMS Port: 80
APN type: MMS
Hit Menu > Save. REBOOT.
(I think I may have also entered the MMSC and MMS Port under the Android Internet APN, but not the other stuff -- I did get it to send, just not go anywhere. I messed up my Internet APN afterward and had to re-load so I lost my settings)
HOWEVER, the message never makes it to the recipient. Android won't complain it's un-sendable, and will upload it, but Sprint doesn't do anything with it. Currently it seems like that setting acts as a black hole. Now this doesn't mean this is a dead end.
ArcSoftMMS for Windows Mobile uses these settings. However, I'm not sure if any additional settings are used.
63.215.195.152 = mms.sprintpcs.com (ping it if you don't believe me)
Nevermind.
All you do is in the Android APN:
MMSC: http://63.215.195.152/servlets/mms?X-SPRINT-MDN=<your10digitphone#>
MMS Port: 80
However, the Mms.apk messaging application needs to be modified to spoof a particular UserAgent. It should be the same one as in Windows Mobile. This will require a recompile of Mms.apk, along with distributing an androidupdate.tar.
Until then, it'll go through, but won't be relayed.
jnadke said:
Nevermind.
All you do is in the Android APN:
MMSC: http://63.215.195.152/servlets/mms?X-SPRINT-MDN=<your10digitphone#>
MMS Port: 80
However, the Mms.apk messaging application needs to be modified to spoof a particular UserAgent. It should be the same one as in Windows Mobile. This will require a recompile of Mms.apk, along with distributing an androidupdate.tar.
Until then, it'll go through, but won't be relayed.
Click to expand...
Click to collapse
nice detail thanks, maybe in the future.
This should be pretty easy once we have said user-agent. I don't want to have to go all the way back to Windows Mobile to get it though - if anyone's seen it before, let me know and I'll see if I can get the package working.
bri3d said:
This should be pretty easy once we have said user-agent. I don't want to have to go all the way back to Windows Mobile to get it though - if anyone's seen it before, let me know and I'll see if I can get the package working.
Click to expand...
Click to collapse
I don't think anyone's gone down this road. Verizon people can do MMS, just do X-VZW-MDN=<phonenumber> instead. Sprint appears to have some extra filtering...
I installed Windows ArcSoftMMS and can sucessfully send MMS messages. We'll have to reverse-engineer what's being replicated there.
The one I installed is here:
http://forum.ppcgeeks.com/showthread.php?t=61802
Just the Sprint Arcsoft MMS 5.0.82.79.cab
There's also a device capability link that's usually sent to the server.
For example, for Rhodium, this is sent:
http://www.htcmms.com.tw/gen/Rhodium-1.0.xml
By chance, there's a file for our Vogues:
http://www.htcmms.com.tw/gen/Vogue-1.0.xml
I'm not sure what else is sent to the server. There's an entire Rhodium PPCGeeks thread devoted to getting HTC Messaging in Manila 2.5 to work on Sprint. They've been thus far unsuccessful. They, too, are currently chasing down the useragent stuff.
I was talking to someone in the Sprint Hero forum, and they said the hero people had to rebuild Mms.apk and add:
Code:
req.addHeader(HDR_KEY_ACCEPT_LANGUAGE, HDR_VALUE_ACCEPT_LANGUAGE);
//add X-MDN http header
TelephonyManager teleMgr =
(TelephonyManager)context.getSystemService(Context.TELEPHONY_SERVICE);
req.addHeader("X-MDN", "1" + teleMgr.getLine1Number());
to com.android.mms.transaction.HttpUtils
I tried and no go. We'll have to look into replicated what WinMobile is doing.
jnadke said:
I don't think anyone's gone down this road. Verizon people can do MMS, just do X-VZW-MDN=<phonenumber> instead. Sprint appears to have some extra filtering...
I installed Windows ArcSoftMMS and can sucessfully send MMS messages. We'll have to reverse-engineer what's being replicated there.
The one I installed is here:
http://forum.ppcgeeks.com/showthread.php?t=61802
Just the Sprint Arcsoft MMS 5.0.82.79.cab
There's also a device capability link that's usually sent to the server.
For example, for Rhodium, this is sent:
http://www.htcmms.com.tw/gen/Rhodium-1.0.xml
By chance, there's a file for our Vogues:
http://www.htcmms.com.tw/gen/Vogue-1.0.xml
I'm not sure what else is sent to the server. There's an entire Rhodium PPCGeeks thread devoted to getting HTC Messaging in Manila 2.5 to work on Sprint. They've been thus far unsuccessful. They, too, are currently chasing down the useragent stuff.
Click to expand...
Click to collapse
For verizon do we add the entries to the andriod APN or create a new one? Is the port the same?
Reddog80p said:
For verizon do we add the entries to the andriod APN or create a new one?
Click to expand...
Click to collapse
Add to the existing APN. Hit menu/power, then save.
For the MMSC, on verizon you can just do ?X-VZW-MDN=<10digitphonenumber> after the URL.
i.e http://mms.vtext.com/servlets/mms?X-VZW-MDN=1234567890
Okay guys, I looked further into what WinMo is doing.
Apparently the cab I posted that works on my phone is for the Palm Treo Pro.
If you install it and look in:
HKLM,"Software\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader"
You'll see there's a whole bunch of settings. The UAProf points to sprint's website itself, identifying it as a Treo.
Code:
[HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader]
"X-MDN"="1<phonenumber>"
"Accept-Charset"="us-ascii,utf-8,iso-10646-ucs-2,iso-8859-1"
"Accept"="X-MDN"
"hmac-md5-key"="ph1uzoe52iuw"
"Accept-Language"="en"
"User-Agent"="Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile 6.0) Sprint Treo850e"
"x-wap-profile"="http://device.sprintpcs.com/Palm/PTR850HK/Treo850e103.rdf"
jnadke said:
Add to the existing APN. Hit menu/power, then save.
For the MMSC, on verizon you can just do ?X-VzW-MDN=<phonenumber> after the URL.
Click to expand...
Click to collapse
So I just have to enter
http://63.215.195.152/servlets/mms?X-VzW-MDN=<phonenumber>
in the MMSC field.
Reddog80p said:
So I just have to enter
http://63.215.195.152/servlets/mms?X-VzW-MDN=<phonenumber>
in the MMSC field.
Click to expand...
Click to collapse
That's the sprint messaging server (http://mms.sprintpcs.com). You need to use the VZW one.
http://mms.vtext.com/servlets/mms
jnadke said:
That's the sprint messaging server (http://mms.sprintpcs.com). You need to use the VZW one.
http://mms.vtext.com/servlets/mms
Click to expand...
Click to collapse
I added http://mms.vtext.com/servlets/mms?X-VZW-MDN=<my10digitphonenumber> to the MMSC field, saved and rebooted and tried attchinging a picture to a text but it would not send. The envelope with the red circle icon on it remains there.
Reddog80p said:
I added http://mms.vtext.com/servlets/mms?X-VZW-MDN=<my10digitphonenumber> to the MMSC field, saved and rebooted and tried attchinging a picture to a text but it would not send. The envelope with the red circle icon on it remains there.
Click to expand...
Click to collapse
I think for VzW it needs to be 9 digit phone number.
Also VzW not VZW. Case-sensitive. That's at least what I read on the WinMobile forums.
According to here, it's otherwise:
http://forum.xda-developers.com/showthread.php?t=535293&highlight=Verizon+MMS
I can't really answer further, as I don't use Verizon. Try searching the WinMobile forums for the proper settings. Make sure MMS works in WinMobile.
jnadke said:
I think for VzW it needs to be 9 digit phone number.
Also VzW not VZW. Case-sensitive. That's at least what I read on the WinMobile forums.
According to here, it's otherwise:
http://forum.xda-developers.com/showthread.php?t=535293&highlight=Verizon+MMS
I can't really answer further, as I don't use Verizon. Try searching the WinMobile forums for the proper settings. Make sure MMS works in WinMobile.
Click to expand...
Click to collapse
It's always worked in winmo. I'm running from nand. I'll check around thanks J!
Try these threads:
http://forum.ppcgeeks.com/showthread.php?t=93778
http://forum.ppcgeeks.com/showthread.php?p=207114
You could possibly try doing the user/pass thing from the 2nd thread in the Android APN.
If you open the cab in the zip file, you see a setup.xml. This contains the registry entries. If you open it in WordPad, search for "WspHeader". You should then see the proper setting for X-VzW-MDN (and what the proper spelling/case is).
You might need to install it and use PHM Regedit to go to the area in the registry WspHeader is at before that value will appear (it's populated by your phone number, that wouldn't be in the cab.....)
jnadke said:
Try these threads:
http://forum.ppcgeeks.com/showthread.php?t=93778
http://forum.ppcgeeks.com/showthread.php?p=207114
You could possibly try doing the user/pass thing from the 2nd thread in the Android APN.
If you open the cab in the zip file, you see a setup.xml. This contains the registry entries. If you open it in WordPad, search for "WspHeader". You should then see the proper setting for X-VzW-MDN (and what the proper spelling/case is).
You might need to install it and use PHM Regedit to go to the area in the registry WspHeader is at before that value will appear (it's populated by your phone number, that wouldn't be in the cab.....)
Click to expand...
Click to collapse
This is the section that contains "WspHeader" from NFSfans Verizon MMS cab that worked using his 6.5 WInMo rom...
/><parm name="GatewayPort" value="80" datatype="integer" /><parm name="MmscURI" value="http://mms.vtext.com/servlets/mms" datatype="string" /><parm name="Gateway" value="" datatype="string" /><parm name="Name" value="Verizon Wireless" datatype="string" /><parm name="ISP" value="Verizon Wireless" datatype="string" /></characteristic><characteristic type="HKLM\SOFTWARE\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader"><parm name="Accept-Charset" value="us-ascii;utf-8;iso-10646-ucs-2;ISO-8859-1" datatype="string" /><parm name="Accept" value="application/vnd.wap.multipart.related" datatype="string" /><parm name="User-Agent" value="utstar69kv1" datatype="string" /><parm name="x-wap-profile" value="http://www.arcsoft.com/mobile/UAProf/ArcSoft-MMSUA-PPC-v40.xml" datatype="string" /><parm name="Accept-Language" value="en" datatype="string" /><parm name="Profile" value="http://uaprof.vtext.com/utstar/xv69k/xv69kv1.xml" datatype="string" /></characteristic><characteristic type="HKLM\System\Inbox\Templates\IPM\MMS"><parm name="Thread" value="\Windows\thread_sms.htm" datatype="string" /></characteristic><characteristic type="HKLM\SOFTWARE\Microsoft\Inbox\Svc\SMS"><parm name="FriendlyName" value="SMS / MMS" datatype="string" /></characteristic><characteristic type="HKCR\MortScript"><parm name="" value="MortScript" datatype="string" /></characteristic><characteristic type="HKCR\MortScript\DefaultIcon"><parm name="" value="\Windows\MortScript.exe,-130" datatype="string" /></characteristic><characteristic type="HKCR\MortScript\Shell\Open\Command"><parm name="" value=""\Windows\MortScript.exe" "%1"" datatype="string" /></characteristic><characteristic type="HKCR\.mortrun"><parm name="" value="MortScript" datatype="string" /></characteristic><characteristic type="HKCR\.mscr"><parm name="" value="MortScript" datatype="string" /></characteristic><characteristic type="HKCU\Software\Microsoft\InternetSharing"><parm name="LastCellConnection" value="Data Network Connect" datatype="string" /></characteristic><characteristic type="HKLM\Comm\InternetSharing\Settings"><parm name="ForceCellConnection" value="Data Network Connect" datatype="string" /></characteristic><characteristic type="HKLM\Comm\InternetSharing"><parm name="Extension" value="" datatype="string" /></characteristic><characteristic type="HKLM\Comm\ConnMgr\Providers\{7C4B7A38-5FF7-4bc1-80F6-5DA7870BB1AA}\Connections\Phone as Modem"><parm name="Enabled" value="0" datatype="integer" /><parm name="ConnectionGUID" value="{E8F7941B-F379-E1C7-A25E-9C1425630A20}" datatype="string" /><parm name="ReadOnly" value="0" datatype="integer" /><parm name="SecureLevel" value="0" datatype="integer" /><parm name="Secure" value="0" datatype="integer" /><parm name="AlwaysOn" value="0" datatype="integer" /><parm name="RequirePw" value="0" datatype="integer" /><parm name="EntryType" value="0" datatype="integer" /><parm name="DestId" value="{ADB0B001-10B5-3F39-27C6-9742E785FCD4}" datatype="string" /></characteristic><characteristic type="HKLM\Software\OEM\WModem"><parm name="CheckProfile" value="0" datatype="integer" /><parm name="Multi-NAI" value="0" datatype="integer" /><parm name="WModemDUN" value="0" datatype="integer" /></characteristic></characteristic></wap-provisioningdoc>
I'm able to send with the settings ...
MMSC: http://mms.vtext.com/servlets/mms?X-VZW-MDN=1234567890
MMS proxy: leave empty
MMS port: 80
But receiving does not work. I can't believe this whole time I kept trying to put "<>" around my phone number. Noob with a capital "N". So since this is the correct setting why wouldn't we be able to receive? Is there another setting that handles incoming MMS or should it be handled the same?
Reddog80p said:
I'm able to send with the settings ...
MMSC: http://mms.vtext.com/servlets/mms?X-VZW-MDN=1234567890
MMS proxy: leave empty
MMS port: 80
But receiving does not work. I can't believe this whole time I kept trying to put "<>" around my phone number. Noob with a capital "N". So since this is the correct setting why wouldn't we be able to receive? Is there another setting that handles incoming MMS or should it be handled the same?
Click to expand...
Click to collapse
I'm not sure why Android can't receive. It's probably something in the SMS RIL that isn't being passed correctly. I think with MMS, a flag gets sent with SMS, and the client goes and fetches the picture. I'm not sure, so I'd have to look that up.
Good to know it works for VZW users though.
Though, make sure sending really works. On Sprint, it'll "send" but the other end will never receive it. Did you check if the other party received it?
ok not sure if this is really anything to add but here is what i have regarding my touch pro:
it looks like i can send mms. not sure if it's sending media with it but i can def. send. i sent to gmail and yahoo and both came as mms. can't add pics or videos (my thinking is because the camera is not working, it doesn't think it has the capabilities). i was able to attach an audio file (ring tone) though.
but it shows that it's coming from pm.sprint.com.
settings: APN
Name: internet
APN: Android
Proxy:<Not set>
Port:<Not set>
Username:<Not set>
Password:<Not set>
Server:<Not set>
MMSC:http://63.215.195.152/servlets/mms?X-SPRINT-MDN=(10 didgit phone number)
MMS proxy:<Not set>
MMS Port: 80
MMC:310
MNC:995
Authentication Type:<Not set>
APN type:<Not set>
Related
Title says it all
+1 to that.
I know how to send mms but not recieve.
For Verizon do this to be able to send mms
Go to Settings -> Wireless Controls -> Mobile Networks -> Access Point Names -> Android
Modify the following settings:
MMSC: http://mms.vtext.com/servlets/mms?X-VZW-MDN=<your ten-digit phone number>
MMS proxy: leave empty
MMS port: 80
I was thinking i should modify the username to [email protected] and password to vzw like windows mobile but i am afraid to try it because i dont know what the current password is to change it back if it dont work for recieving
How about on sprint?
cp0020 said:
How about on sprint?
Click to expand...
Click to collapse
i dont have sprint but you could try this instead of what i use. i read sprint is more difficult
http://63.215.195.152/servlets/mms?X-SPRINT-MDN=(10 digit phone number)
if that dont work, here is a thread for mms sprint android discussion
http://forum.xda-developers.com/showthread.php?t=627388
This is being discussed in the "Vogue CDMA General Developement" section: http://forum.xda-developers.com/showthread.php?t=627388
Sending works, Receiving does not yet. The link in the prior post has instructions on settings to get sending pic messages working.
Well I have a sprint touch and I can receive. Not sure why everyone says they can't, but I followed the thread and the only sprint version I saw was for the thouch pro 3 so I tried that and it sends but it doesn't make it to the person I'm sending to, tried sending to my email and phone.
Touch pro 2#&$%% my bad lol
cp0020 said:
Well I have a sprint touch and I can receive. Not sure why everyone says they can't, but I followed the thread and the only sprint version I saw was for the thouch pro 3 so I tried that and it sends but it doesn't make it to the person I'm sending to, tried sending to my email and phone.
Click to expand...
Click to collapse
You can receive? But can't send? Sounds strange. Make sure your entering your phone number in the MMSC field as 1234567890 not <1234567890> thats what I was doing wrong initially. Can you post a link to the tp2 thread you are reffering to...I've seen a few but none mentoined any setting besides the ones already listed in this thread.
It was just on the 3rd Or 4th page I think. : http:// Developement" section: http:// forum.xda-developers.com/ showthread.php?t=627388. Yeah I was always able to receive mms, ever since I started using android back in January. But I put in those settings for touch pro 2 found on that site cause it was sprint qnd I was finally able to send it but it wouldn't make it to the person I was sending to.
cp0020 said:
It was just on the 3rd Or 4th page I think. : http:// Developement" section: http:// forum.xda-developers.com/ showthread.php?t=627388. Yeah I was always able to receive mms, ever since I started using android back in January. But I put in those settings for touch pro 2 found on that site cause it was sprint qnd I was finally able to send it but it wouldn't make it to the person I was sending to.
Click to expand...
Click to collapse
When you "receive", is it the actual image or a web link to it? Everyone gets the web link - that just means Sprint thinks your phone isn't MMS-capable on the server side so they text you a link instead. You're not "receiving MMS" unless you get the image straight to your phone.
bri3d said:
When you "receive", is it the actual image or a web link to it? Everyone gets the web link - that just means Sprint thinks your phone isn't MMS-capable on the server side so they text you a link instead. You're not "receiving MMS" unless you get the image straight to your phone.
Click to expand...
Click to collapse
Yeah its just a link to a website. So I don't have mms peroid lol
Well at least you get a link. US verizon user don't get the MMS message at all.
any word on the camcorder?????
incubus26jc said:
I know how to send mms but not recieve.
For Verizon do this to be able to send mms
Go to Settings -> Wireless Controls -> Mobile Networks -> Access Point Names -> Android
Modify the following settings:
MMSC: http://mms.vtext.com/servlets/mms?X-VZW-MDN=<your ten-digit phone number>
MMS proxy: leave empty
MMS port: 80
I was thinking i should modify the username to [email protected] and password to vzw like windows mobile but i am afraid to try it because i dont know what the current password is to change it back if it dont work for recieving
Click to expand...
Click to collapse
I only see T-mobile and Telkila APNs ... I don't see one named Android
tharris297 said:
I only see T-mobile and Telkila APNs ... I don't see one named Android
Click to expand...
Click to collapse
Me too. I've tried this method before and never had any luck sending or receiving. Its the only thing I miss from WinMo.
tharris297 said:
I only see T-mobile and Telkila APNs ... I don't see one named Android
Click to expand...
Click to collapse
You can just edit the T-mobile apn. Keep in mind once you edit it and save it the apn deletes itself. Then all your left with is the telkila apn. Everything will continue to work as it did before. I have sending os pic messages working on VZW using the settings listed below . Receiving does not work.
For Verizon do this to be able to send mms
Go to Settings -> Wireless Controls -> Mobile Networks -> Access Point Names ->
Modify the following settings:
MMSC: h ttp://mms.vtext.com/servlets/mms?X-VZW-MDN=your10digitnumber
MMS proxy: leave empty
MMS port: 80
I believe the MNC needs to be 995 also.
incubus26jc said:
I was thinking i should modify the username to [email protected] and password to vzw like windows mobile but i am afraid to try it because i dont know what the current password is to change it back if it dont work for recieving
Click to expand...
Click to collapse
The password in winmo was vzw. I've tried it but it didn't work for me but you can try.
I have no APN's currently listed but all my data and pic message sending works.
Reddog80p said:
You can receive? But can't send? Sounds strange. Make sure your entering your phone number in the MMSC field as 1234567890 not <1234567890> thats what I was doing wrong initially. Can you post a link to the tp2 thread you are reffering to...I've seen a few but none mentoined any setting besides the ones already listed in this thread.
Click to expand...
Click to collapse
It's not strange, sprint doesn't send MMS to the phone through the old fashion way, they send a link to your phone and you follow that to a webpage containing your image
Hey guys I'm curious, before I make the change how many of us can access mms on our vogues?
I know my carrier (Bell Mobility, Canada) blocks them. what about the rest of you?
In android, winmo, or in general?
i can send with verizon but not recieve
I have verizon so I can send but not receive.
In truth I've never really used mms all that much on any phone.
On sprint, so I receive a link but not send.
interesting..
all right no worries then I was going to disable mms, but if it partially works for some of you we'll leave it.
mssmison said:
interesting..
all right no worries then I was going to disable mms, but if it partially works for some of you we'll leave it.
Click to expand...
Click to collapse
It doesnt work right off the bat for me.It only sends on verizon for me if i change these settings. Recieving still doesnt work regardless. Mabye you can help get it going for us.
Go to Settings -> Wireless Controls -> Mobile Networks -> Access Point Names -> Android
Modify the following settings:
MMSC: http://mms.vtext.com/servlets/mms?X-VZW-MDN=<your ten-digit phone number>
MMS proxy: leave empty
MMS port: 80
MMS works if you use the right settings.
Unfortunately right settings is carrier-specific. And it's not server-provided.
Something is botching the receive messages though. That needs to be fixed.
mssmison said:
Hey guys I'm curious, before I make the change how many of us can access mms on our vogues?
I know my carrier (Bell Mobility, Canada) blocks them. what about the rest of you?
Click to expand...
Click to collapse
A quick search of the 'nets says Bell Mobility does support MMS, they just charge you 50 cents per message.
I've seen:
MMSC Server: http://BellMMSC.bell.ca
User Agent: LGE-LG8700 UP.Browser/6.2.3.2 (GUI) MMP/2.0
User Agent Profile: http://uaprof.bellmobilite.ca/BMC_LGE_LG8700_CX87BL05.rdf
MMG IP: 206.047.201.009
MMG Port: 554
Buffer Length: 7
User Agent String: LGE-LGE8700 QtvPlayer/5.4
As an example of MMS settings.
Verizon allows the sending and receiving of MMS (pic messages) works on Winmo but only sending works on andoid. I believe jnadke mentioned that android does see the incoming message as a MMS but somehow the messaging app does not know how to retrieve it.
jnadke said:
A quick search of the 'nets says Bell Mobility does support MMS, they just charge you 50 cents per message.
I've seen:
MMSC Server: http://BellMMSC.bell.ca
User Agent: LGE-LG8700 UP.Browser/6.2.3.2 (GUI) MMP/2.0
User Agent Profile: http://uaprof.bellmobilite.ca/BMC_LGE_LG8700_CX87BL05.rdf
MMG IP: 206.047.201.009
MMG Port: 554
Buffer Length: 7
User Agent String: LGE-LGE8700 QtvPlayer/5.4
As an example of MMS settings.
Click to expand...
Click to collapse
k I didn't open this thread for support . Bell blocks mms to vogue esns, which is why I said it doesn't work for me. As I already said I was going to disable the mms portion or the messaging app, but if you guys are able to use it I'll leave it alone.
mssmison said:
k I didn't open this thread for support . Bell blocks mms to vogue esns, which is why I said it doesn't work for me. As I already said I was going to disable the mms portion or the messaging app, but if you guys are able to use it I'll leave it alone.
Click to expand...
Click to collapse
What would benefit by disabling it?
Hi
I am having trouble sending an recieving photo messages, i am on orange payg and have just spent 30min talking to them and they dont know thr reason why.
My APN settings are
Name Orange MMS
APN orangemms
Proxy not set
Port not set
User Name Orange
Password Multimedia
Server not set
MMSC ://mms.orange.co.uk (has http before it)
MMS Proxy 192.168.224.10
MMS Port 8080
MCC 234
MNC 33
Authentication type PAP
APN type mms
Is there anything wrong with this???
Have you tried selecting the 'Auto-retrieve' and 'Roaming auto-retrieve' in: Messaging > Settings > (scroll down) Multimedia message settings? As for sending, try enabling 'Data roaming' in Mobile network settings. I am thinking that because Orange/T-mobile have merged, maybe you are trying to send/receive the message over the old T-Mobile network. Just a thought. Hope it works for you.
I've got the same settings as you, except one minor difference, I have a / at the end of the mmsc (ie http://mms.orange.co.uk/)
I have exactly the same problem and have also tried phoning Orange. They just talked me through the settings but I was already set up correctly. Very annoying! I would love to hear of a solution to this problem.
padlad said:
Have you tried selecting the 'Auto-retrieve' and 'Roaming auto-retrieve' in: Messaging > Settings > (scroll down) Multimedia message settings? As for sending, try enabling 'Data roaming' in Mobile network settings. I am thinking that because Orange/T-mobile have merged, maybe you are trying to send/receive the message over the old T-Mobile network. Just a thought. Hope it works for you.
Click to expand...
Click to collapse
I can confirm that this problem has been around for me long before the merger, basically since I got my phone back in July.
@FloridaK - I also have the slash at the end, but it's not working.
Greetings Forum
So, when I had stock ROM I could receive MMS no problem, but when I upgraded to CM7 it no longer wanted to receive them, when I press it, it just says "downloading" and then nothing, then the download button pops up again which I can click on and it repeats over and over.
I'm now on MIUI, and the exact same thing is happening, I've looked at my APNs and they are setup as they should (afaik)
Any help would be GREATLY appreciated, I have some MMS' I'd like to receive
Kind regards
~Neefy
EDIT: I'm on TELENOR DK (Denmark)
Bump, really can't find anything
Neefy said:
Bump, really can't find anything
Click to expand...
Click to collapse
Is your telephony contract set up to support MMS? Some aren't
kiljacken said:
Is your telephony contract set up to support MMS? Some aren't
Click to expand...
Click to collapse
this and also is your APN config correct?
I managed to fix it, I had 4 APNs
Telenor internet
Bibob internet
Telenor mms
Bibob mms
Just deleted the bibob entries and it works now
Well, sorry to revive an old thread, but now it's not working again..
I heard something about a signed-GCI.zip ?
hey
have u managed to fixed it?coz ive got the same problem...
romxygen
provider: telenor
n8w1ng said:
hey
have u managed to fixed it?coz ive got the same problem...
romxygen
provider: telenor
Click to expand...
Click to collapse
I have the same problem all the time, cant read a recieved MMS or can I send one, so annoying, isn't just on this phone either, I had the same problem wih my HTC Desire
it seems like this is gonna b a real issue since nobody can come up with anythin that could fix it...
my post at the oxygen forum is dead as well....:/
What APN settings are you using?
Manny_S said:
What APN settings are you using?
Click to expand...
Click to collapse
ive tried many of them...ive tried those from the APNlist
1. internet(works ok)
<apn name="Telenor Internet" mcc="238" mnc="02" apn="Internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="null" mmsc="" type="default,supl"/>
and 2. MMS(doesnt work)
<apn name="Telenor MMS" mcc="238" mnc="02" apn="telenor" user="" server="" password="" proxy="" port="" mmsproxy="212.88.64.8" mmsport="8080" mmsprotocol="null" mmsc="http://mms.telenor.dk" type="mms"/>
n also those ive found on the net(this set did work on 2.2 stock rom):
Name Telenor MMS
APN: internet
MMSC: http://mms.telenor.dk
MMS: proxy 212.88.64.8
MMS: port 8080
MCC: 238
MNC: 02
APN type: mms
Try with handcent.
Its an easy workaround... atleast for me
Sent from my LG Optimus 2x using XDA Premium App
HerrKuk said:
Try with handcent.
Its an easy workaround... atleast for me
Click to expand...
Click to collapse
ive already tried that...no difference...perhaps i should look at it again.
thx
n8w1ng said:
ive tried many of them...ive tried those from the APNlist
1. internet(works ok)
<apn name="Telenor Internet" mcc="238" mnc="02" apn="Internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="null" mmsc="" type="default,supl"/>
and 2. MMS(doesnt work)
<apn name="Telenor MMS" mcc="238" mnc="02" apn="telenor" user="" server="" password="" proxy="" port="" mmsproxy="212.88.64.8" mmsport="8080" mmsprotocol="null" mmsc="http://mms.telenor.dk" type="mms"/>
Click to expand...
Click to collapse
On my network (not Telenor), my MMS refused to work until I modified the "APN Type" settings...
For internet, the APN Type is "default"
For mms, the APN Type is "mms"
(When I tried internet APN Type "default,supl" on my network, mms would not work - so it may be worth giving this a try)
Unfortunately, this is my only idea for you.
Good luck.
Manny_S said:
On my network (not Telenor), my MMS refused to work until I modified the "APN Type" settings...
For internet, the APN Type is "default"
For mms, the APN Type is "mms"
(When I tried internet APN Type "default,supl" on my network, mms would not work - so it may be worth giving this a try)
Unfortunately, this is my only idea for you.
Good luck.
Click to expand...
Click to collapse
ive tried this one too(didnt work for me)...well i guess this mms issue has smth to do with all AOSP roms...
Ive been trying to use my Captivate with Bell. (Eclair, 2.1-update 1 from Odin)
I found the APN settings on Bell's site and they were forwarded to me by a tech support rep as well. In the "MMSC" box I am instructed to input this:
MMSC: 5778154
<a URL I'm guessing to be a server on the next line>
Click to expand...
Click to collapse
I'm sorry if it doesnt make a lot of sense but I can't post any links or images. The phone only gives me a one line text box for each value and no enter/return to put an extra line. Ive tried to input one or the other, tried adding spaces, ETC and I can't figure out a way to input this MMSC information. When I asked what the number meant and if it was entirely relevant (I could possibly just use the server?) The girl on the phone just kept saying "we don't support that" over and over again, and kept asking me to call Samsung.
Has anyone else successfully used a Captivate with Bell? If so, what does your APN settings look like? Thank you!
Bell Mobility
APN1: pda2.bell.ca
Leave the Username and Password blank.
APN2: pda2.bell.ca
- Leave the Username and Password blank.
MMSC: http://mms.bell.ca/mms/wapenc
MMS Proxy: web.wireless.bell.ca
PORT: 80
taken from this post:
http://forum.xda-developers.com/showthread.php?t=656845
Additionally I used my captivate with my buddies Bell SIM card with no issues using the above settings