Funny story. In the 6 years I was with VZW, I used MMS a total of less than 20 times. I got an iPhone/switched to AT&T about two weeks ago just for a change of pace. I signed up for the developer program, got all the fancy trimmings, and started reading about the MMS functionality. I NEEDED it for some visceral reason, so I started my quest to make it work with 3.0.
With a basic understanding of what needed to be done from forum browsing before this, I placed my first call to at&t, asked a very nice support rep to 'provision me' for mms, gave the "I'm a developer" spiel- she was happy to oblige- suppose I got lucky. Done, rebooted, tried several send/recieve MMS's with her, no dice. So I do more research. Get the updated .ipcc, edit it manually to make the proxy settings user configurable, try with a bunch of different proxies and proxy combos. No dice. Downgrade to 2.2.1 and get SwirlyMMS2. No dice.
Read about WAP push. Called today to have that enabled, the VLR cleared and activation sent. The same support rep (what are the odds?) puts me on hold for like 5 minutes, comes back and say "Well, here-" and then the call is lost. No service in a 5 bar 3G area. To me, this was absolutely horrifying. I freaked out for about 10 minutes frantically pacing around a crowded restaurant parking lot with my phone above my head figuring I caught the wrong chick on the wrong day and she destroyed my beautiful hopes.. before I went "Gee, guess they did it..," rebooted my phone and SwirlyMMS worked! Figured, "Hey, if this works now, I can go back to 3.0 with no issues!'
Come home, upgrade back to 3.0, no dice. Back to square one. Ok maybe the story isn't funny.
So, I had WAP PUSH enabled when I was running 2.2.1, upgraded to 3.0, and I am using the exact same settings that worked with Swirly and MMS is not functioning. I don't know enough about WAP PUSH to determine if getting it enabled when I was in 2.2.1 and then upgrading somehow disabled it, if the jig is up and one of the 'sweeps' kicked in, or some other anomaly happened. To the best of my knowledge, it's just a set of protocols, correct? So like, it's all AT&T's end and if they enabled it, it would be enabled no matter what OS I'm running?
All I know is that a function I went the better part of a decade rarely using has somehow taken control of my life in the past few days and I must make this work. It's almost to the point of virgin sacrifices.
Thoughts?