I have an AT&T Tilt. I hit soft reset after a hard reset so that the bloatware didn't install. I can send text messages no problem. I cannot send a picture message. I can sometimes receive them, but I cannot send them from my phone. I have been trying to send them to a Verizon phone and have not tried an AT&T phone. Has anyone had a similar issue where they weren't able to send a picture message and resolved it?
tytn/tytn II mms
Never worked with wm6 correctly (finland, tytn/tytnII)
-Using port 9201 & WAP version 1.2 -> MMS under 70k possible to send and receive, higher not (when sending , it just hangs in 99%).
-Using port 8080 & WAP version 2.0 -> MMS up to 600k send ok, never able to receive "errMsg: error" (your messages cannot be downloaded).
This is only my experience (Elisa Finland). other providers and countries propably work ok.
anyone?
You won't have your AT&T operator settings installed with the method you used to eliminate the 'bloatware' Search for the Network settings cab on this forum as it may help you.
I found out the problem. AT&T can send and receive up to 600k. Verizon can only receive and send up to 350K. I had to change the outbound pictures to QVGA size and had to adjust the video to a smaller file. I guess different have different size limitations. In case anyone else experiences this problem, you need to adjust your settings.
Removing the bloatware does not remove any of the phone settings. It just remove the unnecessary software.
Please go back and edit your start post Title to this thread with {fixed} then others can use it for reference. Cheers and well done.
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.
SENDING WORKS (for Verizon)
<post deleted>
Telus
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.
Will try this soon pchaso
craig0r said:
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.
Click to expand...
Click to collapse
It takes seconds.
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...
craig0r said:
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...
Click to expand...
Click to collapse
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...
pchasco said:
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...
Click to expand...
Click to collapse
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.
craig0r said:
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...
Click to expand...
Click to collapse
Try it with X-MDN instead of X-VZW-MDN.
pchasco said:
Try it with X-MDN instead of X-VZW-MDN.
Click to expand...
Click to collapse
No dice.
Cool just sent a pic to my email and it worked
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?...
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...
Now that the droid is out, is there any update on receive settings?
Anything new on android verizon mms? Tried the instructions in the first post but it didn't work for me.
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 : )
bumpity bump bump
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.
Nothing new? Sending still works...let's receive! LOL
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 [email protected]_ 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...
I can recieve MMS and sometimes I can send them, but most times I get the message that the MMS cannot send. The ones I cannot send are the same size as the one I could, around 40k. I have no clue why this is happening.
Anyone have a solution for this? I actually use MMS rather often.
also for some reason my notifications say that I'm sending 2 mms when I only send one. Anyone have a solution? I'm on at&t but I don't think that matters.
Delete everything in your outbox, create a new empty MMS and write a letter or two, no images or anything and send it to yourself. If that works, then something might wrong with the stuff you're trying to include in the MMS that fails.
Hello,
I searched the forum, but I don't find solution.
As stated in topic name I can receive MMS message, but I cannot send one. I can send mms with text only, when I attached the picture or some multimedia file I stucked on sending... but there is no data transmition. I tried already few ROMs to exclude ROM factor. On every ROM the problem was present.
All apns are set correctly, receiving works, sending text as mms also.
Has anyone idea how to solve that?
Is that problem is still there.
-----Sent using RemICS-i9000-----
Anyone else having trouble sending MMS since updating? I know for a fact I sent picture messages to two different people on June 30th (before update) and they worked fine. Tonight was the first I tried since updating to 5.1 and it came back saying there was an APN setting error in NextSMS, and it also didn't send while using the stock messaging app... I tried sending it to my own Google Voice number, however, and it worked.
Is this a problem with 5.1, or maybe just the person I'm sending it to? I'll try sending to the person who I know it worked for tomorrow (too late tonight).
I get the APN error when sending. My text message app fails, and provides the error message. However, the MMS does go through to the other end. On the other hand, I have not been receiving MMS at all. Multiple people have notified me that they sent a picture I never received.
My APN settings do not match what appears to be correct (MMS port is blank when it should be 80, and MCC is 311 when it should be 310). Also, I can neither add to nor edit the existing APN settings. Anyone else?