Android MMS: How to send on Verizon (receiving still doesn't work) [Archive]

pchasco

10th July 2009, 05:02 PM

I've figured out how to send MMS messages with Android on the Verizon network. Here's how:

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

Please let me know if this works for you. Keep in mind that you must have a data connection open in order to send MMS.

As far as receiving messages, when a picture message comes in it properly receives the SMS, but it isn't recognized as an MMS message. It does however recognize that it's not a standard SMS so it doesn't go to your message inbox.

pchasco

10th July 2009, 05:24 PM

craig0r

10th July 2009, 07:09 PM

I've found some similar settings for Telus, but can't seem to make it work. If anyone wants to give it a shot, I've used the information here:

http://forum.xda-developers.com/showthread.php?t=392284

So far, the message just sits there trying to send. The settings I'm currently using are:

MMSC: http://mmsfeplb01.int.eng.telusmobility.com/mms
MMS proxy: http://216.198.139.113
MMS port: 8088

pchaso, how long does it take you to send an MMS? I'm just curious how long I should wait before I deem a message failed, because it never seems to error out, just sits there.

refthemc

10th July 2009, 07:28 PM

Will try this soon pchaso

pchasco

10th July 2009, 07:46 PM

craig0r

10th July 2009, 08:18 PM

K, so I'm guessing I need something similar to the "?X-VZW-MDN=<your ten-digit phone number>" portion of the verizon settings. Where'd you find this info? It sucks to be so close and yet so far...

pchasco

10th July 2009, 08:36 PM

K, so I'm guessing I need something similar to the "?X-VZW-MDN=<your ten-digit phone number>" portion of the verizon settings. Where'd you find this info? It sucks to be so close and yet so far...

When you configure Arcsoft MMS for Verizon, you have to add a registry entry so that Arcsoft knows to send this field. This entry will cause arcsoft to post this value as part of the HTTP request to the mms servlet. I just took a stab in the dark by putting the value in the querystring. I actually didn't expect it to work...

craig0r

10th July 2009, 08:44 PM

When you configure Arcsoft MMS for Verizon, you have to add a registry entry so that Arcsoft knows to send this field. This entry will cause arcsoft to post this value as part of the HTTP request to the mms servlet. I just took a stab in the dark by putting the value in the querystring. I actually didn't expect it to work...

Nice work! I'll have to try and get Telus MMS working in WinMo this weekend some time... I really don't feel like booting up WM right now though. I will be sure to post any success I have here.

pchasco

10th July 2009, 08:50 PM

craig0r

10th July 2009, 10:01 PM

Try it with X-MDN instead of X-VZW-MDN.

:( No dice.

refthemc

10th July 2009, 11:31 PM

Cool just sent a pic to my email and it worked

refthemc

11th July 2009, 12:02 AM

Kinda just thinking outloud but do you think that we would need a Verizon APN with Verizon specific settings to begin to recieve mms? or does it have to do with dzo's hacked sms settings?...

pchasco

11th July 2009, 02:08 AM

I think it has something to do with the CDMA SMS format being different to that of GSM. I wish I had time to do some hacking on this myself...

trippinnik

30th December 2009, 05:51 AM

Now that the droid is out, is there any update on receive settings?

Reddog80p

1st January 2010, 04:33 AM

Anything new on android verizon mms? Tried the instructions in the first post but it didn't work for me.

cbaty08

19th January 2010, 09:19 PM

Bump... add me to the list of people who want to receive!

Thanks all who help dev this stuff, Android has consumed countless hrs of my time : )

inertone

26th January 2010, 09:40 AM

bumpity bump bump

drewden123

26th January 2010, 07:27 PM

I would really like some development in this area. It seems some settings/apn's could be pulled from the vzw droid. Bluetooth is now working, along with accurate gps. This is the only thing left to be fixed for donut to be completely functional for our vogues.

Reddog80p

19th February 2010, 03:14 AM

Nothing new? Sending still works...let's receive! LOL

jnadke

19th February 2010, 05:23 PM

Need help from you guys then (I don't have Verizon).

1. Make sure MMS sending really does work (send it to someone and ask them if they got it).
2. Get ADB (the command prompt tool) working on Windows (search the forum, there's clear instructions -- its easy)
3. Plug your phone into your computer so you can connect with ADB.
4. Open a command prompt and navigate to where ADB is.
5. Type 'adb shell logcat -b radio > radiolog.txt' (no ')
6. Send a SMS to yourself. Then send an MMS to yourself.
7. Wait a little bit to make sure the MMS notification message is "received". 2-3 minutes should be good.
8. Terminate the adb logging and send me the log at jnadke _@at_ gmail dot com (spam proofed)

A MMS is just an SMS (text message) with instructions to go download data. When you send MMS, the Mms.apk application uses POST command. Receive just uses the GET command. However, this isn't being triggered because I don't think we're correctly interpreting the SMS message that tells us there's an MMS waiting.

I'm making an assumption that we're receiving the MMS notification, and that its reception generates an AT command. It may not, I haven't looked at the SMS RIL code. It's possible I might need to give you a RIL that logs the raw SMS data, so I can compare a SMS message and a SMS-MMS notification message (to see if there's a flag somewhere).

The code is already there in Mms.apk to receive, we're just not telling it to...

mrkite38

19th February 2010, 05:54 PM

Need help from you guys then (I don't have Verizon).

1. Make sure MMS sending really does work (send it to someone and ask them if they got it).
2. Get ADB (the command prompt tool) working on Windows (search the forum, there's clear instructions -- its easy)
3. Plug your phone into your computer so you can connect with ADB.
4. Open a command prompt and navigate to where ADB is.
5. Type 'adb shell logcat -b radio > radiolog.txt' (no ')
6. Send a SMS to yourself. Then send an MMS to yourself.
7. Terminate the adb logging and send me the log at jnadke _@at_ gmail dot com (spam proofed)

A MMS is just an SMS (text message) with instructions to go download data. When you send MMS, the Mms.apk application uses POST command. Receive just uses the GET command. However, this isn't being triggered because I don't think we're correctly interpreting the SMS message that tells us there's an MMS waiting.

I'm making an assumption that we're receiving the MMS notification, and that its reception generates an AT command. It may not, I haven't looked at the SMS RIL code. It's possible I might need to give you a RIL that logs the raw SMS data, so I can compare a SMS message and a SMS-MMS notification message (to see if there's a flag somewhere).

The code is already there in Mms.apk to receive, we're just not telling it to...

Will do. Thanks for the guidance.

Edit: should be in your inbox, sir. Thanks again.

jnadke

19th February 2010, 06:35 PM

Will do. Thanks for the guidance.

Edit: should be in your inbox, sir. Thanks again.

I modified my instructions. Recapture as necessary.

Did you wait a little bit after sending the SMS/MMS messages? I forgot the mention that, because it may take a while before the message is looped back. The purpose is to capture whatever events that aren't being responded to properly in the RIL log.

Basically, about the same time it took for the SMS message to be looped back to you should apply for the MMS (maybe a bit longer).

mrkite38

19th February 2010, 06:38 PM

I modified my instructions. Recapture as necessary.

Did you wait a little bit after sending the SMS/MMS messages? I forgot the mention that, because it may take a while before the message is looped back. The purpose is to capture whatever events that aren't being responded to properly in the RIL log.

Basically, about the same time it took for the SMS message to be looped back to you should apply for the MMS (maybe a bit longer).

I sent sms, received it, then realized i needed to turn data on before sending mms, sent mms, then waited a minute or so after the 'red envelope' disappeared.

But I'll retry based on new instructions.

Edit: new one's on its way

jnadke

19th February 2010, 06:51 PM

I sent sms, received it, then realized i needed to turn data on before sending mms, sent mms, then waited a minute or so after the 'red envelope' disappeared.

But I'll retry based on new instructions.

Edit: new one's on its way

Looks like it worked (in the first batch of data you sent):

SMS Text:
D/AT ( 1593): AT< 000002100202070295665E1445400601FC082A000310085001 0F107D7CA830F2CA837EB41A32F2CA8003061002182323310A 01400E07052ACCBC288A80

D/RIL ( 1593): GSM_PDU=000002100202070295665E1445400601FC082A0003 100850010F107D7CA830F2CA837EB41A32F2CA800306100218 2323310A01400E07052ACCBC288A80

MMS SMS Notification:
D/AT ( 1593): AT< 000002100202070295666A2AA6000601FC08130003100B1001 0410148D200306100219091334

D/RIL ( 1593): GSM_PDU=000002100202070295666A2AA6000601FC08130003 100B10010410148D200306100219091334

I'll look at this more on Monday. Looks like there's a major difference, but I'll have to check the SMS format to see what isn't working properly (perhaps it is and we're just not telling Android properly that an MMS is waiting). You can't just diff the two lines directly, because it's encoded data (avalanche effect applies -- one bit change will make the line entirely different).

I don't think any personal info is in this message, but if you want me to remove the data I can. Just want to post it so if vilord or someone else wants to look at it.

Doesn't hurt to have another batch of data from someone else.

For the record: What specific ROM are you using? Donut and eclair use different RILs, but AFAIK SMS handling is the same in both.

mrkite38

19th February 2010, 07:03 PM

I don't think any personal info is in this message, but if you want me to remove the data I can. Just want to post it so if vilord or someone else wants to look at it.

No worries... although I guess you could call me now if you wanted. :p

For the record: What specific ROM are you using? Donut and eclair use different RILs, but AFAIK SMS handling is the same in both.

Myn's warmdonut, 2nd ed., nand.

tech515

23rd February 2010, 10:19 PM

Reddog80p

24th February 2010, 12:26 AM

I don't have an access point named Android....... are there other values in there that aren't modified so I can make an access point named android?

Which build are you running?

tech515

24th February 2010, 10:15 PM

Which build are you running?

Myn’s Warm Donut – DarkStar Themed - [RLS 3] - 02-20-2010 - *8 New Themes* on nand

seanmcd72

24th February 2010, 11:36 PM

I have the same build also without an "Android" entry.

I have:
"T-Mobile US" (epc.tmobile.com)
and
"TelKila" (Internet)

Neither one is selected...

Reddog80p

25th February 2010, 02:05 AM

Myn’s Warm Donut – DarkStar Themed - [RLS 3] - 02-20-2010 - *8 New Themes* on nand

If your running Myn's build you have a T mobile APN. Go to Settings -> Wireless Controls -> Mobile Networks -> Access Point Names -> There should be an "T-mobile" APN. You can put the settings in there.

inertone

11th March 2010, 03:58 AM

is it possible to use someone else apn settings?
like get someone with a Droid or Eris and hope their APN settings will work on our vogues?

Reddog80p

11th March 2010, 04:35 AM

is it possible to use someone else apn settings?
like get someone with a Droid or Eris and hope their APN settings will work on our vogues?

I don't think the receiving issue is apn related. It's an issue with the process related to message retrieval in android on our phones.

inertone

11th March 2010, 05:25 AM

I don't think the receiving issue is apn related. It's an issue with the process related to message retrieval in android on our phones.

oh that's right
i completely forgot
thanks for reminding me haha :D

Reddog80p

18th March 2010, 02:52 AM

Any new news? MMS on Verizon is the only thing that donut is lacking for me!

drewden123

18th March 2010, 04:08 AM

Any new news? MMS on Verizon is the only thing that donut is lacking for me!

Same here! Everything else is flawless.

Reddog80p

14th April 2010, 12:32 AM

Anything new to try? This thread is almost a year old. We need some closure lol...

inertone

15th April 2010, 03:43 AM

Anything new to try? This thread is almost a year old. We need some closure lol...

HTC Incredible

Reddog80p

15th April 2010, 05:30 AM

HTC Incredible

2 weeks my good man! I'm just gonna add a line since my 2 yr contract is not up until October. Then I'll activate it on my current line's phone number. It would cost me 100 bucks to early terminate and then I'd lose my current number..I've had plenty of time to weigh the options lol. what do you think the icredible will cost w/ 2 yr contract? I'm thinking like $299.00-349.00. I bet the nexus for vzw drops after the incredible not sure how long after tho.

http://store.verizonwireless.com/detail/PhoneSpec.aspx?PhonePK=2098

inertone

15th April 2010, 06:00 AM

2 weeks my good man! I'm just gonna add a line since my 2 yr contract is not up until October. Then I'll activate it on my current line's phone number. It would cost me 100 bucks to early terminate and then I'd lose my current number..I've had plenty of time to weigh the options lol. what do you think the icredible will cost w/ 2 yr contract? I'm thinking like $299.00-349.00. I bet the nexus for vzw drops after the incredible not sure how long after tho.

http://store.verizonwireless.com/detail/PhoneSpec.aspx?PhonePK=2098

that price range sounds about right
i have 7 months till mine is over!
ima have to just drop the whole...599 full retail price? maybe? :(:mad::(

but....HTC INCREDIBLE!:D:D

Reddog80p

16th April 2010, 07:04 AM

that price range sounds about right
i have 7 months till mine is over!
ima have to just drop the whole...599 full retail price? maybe? :(:mad::(

but....HTC INCREDIBLE!:D:D

I see reports of $199.00 w/ 2 year :D Just add a line and drop data on your vogue...then you can still flash the vogue for fun :D

br125

16th April 2010, 05:44 PM

I can't help but notice that wi-fi is not mentioned on here..

http://store.verizonwireless.com/detail/PhoneSpec.aspx?PhonePK=2098

Reddog80p

17th April 2010, 12:03 AM

I can't help but notice that wi-fi is not mentioned on here..

http://store.verizonwireless.com/detail/PhoneSpec.aspx?PhonePK=2098

It's got wi-fi for sure... http://phandroid.com/wp-content/uploads/2010/04/incredible-preorder.jpg look under services..

Massassi

25th April 2010, 12:06 AM

2 weeks my good man! I'm just gonna add a line since my 2 yr contract is not up until October. Then I'll activate it on my current line's phone number. It would cost me 100 bucks to early terminate and then I'd lose my current number..I've had plenty of time to weigh the options lol. what do you think the icredible will cost w/ 2 yr contract? I'm thinking like $299.00-349.00. I bet the nexus for vzw drops after the incredible not sure how long after tho.

[/url]

Online order usually drops the price another $100 fyi

Reddog80p

25th April 2010, 01:20 AM

Online order usually drops the price another $100 fyi

Yup it's $199 after $100 instant rebate if you order online. I heard wirefly is going $150.00 for new customers that sign a 2 year.

f_hugh

16th November 2010, 03:39 PM

I am going to assume that since April there've been no developments on this front?

thoughtlesskyle

18th November 2010, 06:34 AM

I am going to assume that since April there've been no developments on this front?

this is most likely true, their is something in the android port that isnt allowing it to be received, touch pro users are having the same issue with mms on their device too, they ever decompiled the RIL and tried using the Evo one to no avail

the only reason sprint vogue's lucked out in this department was that when our device launched we didnt have mms so sprint did a little trick where they would send a link to the phone. when they finally gave us mms all the client did was process that link into what looked like normal mms. So when we got android the link was simply sent to us again as a text like old times (since the infrastructure was still there). we only needed to get sending working via and apn and we got that too with eclair and froyo thats why sprint's is working. and verizons probably wont

highlandsun

1st May 2011, 10:35 AM

It's a miracle you guys got as far as you did, the way CDMA support was originally hacked into the RIL (by pretending to be GSM). You'll have better luck with my new RIL, which actually implements the real Android CDMA support on Froyo/Gingerbread. (Pretty sure there was no such thing in Cupcake, but it should've been there already in Donut.) If any of you Vogue users are still around, anyway.

With this RIL we have MMS send working fine. MMS receive - the actual message is received correctly, but for some reason the MMS client isn't automatically downloading the attachments. There seems to be some other config element we're still missing.

Correction: MMS works 100% on Verizon. Only Sprint is refusing to play ball on receives...

New RIL (forum.xda-developers.com/showthread.php?t=1009112)