yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] cp0020:
it didn't disappear but I still wasn't able to send mms :(
[Touch CDMA Android Development] mrono:
If you use http://www.androidfreeware.org/download/handcent-sms-2.9.29 Handcent SMS you can spoof the outgoing mms stuff, like device model and such
[Touch CDMA Android Development] cp0020:
did you set it up? are you able to send? or are you syaing that it would be easier to get mms to work on that.

edit... i downloaded the file but its not an apk file
[Touch CDMA Android Development] Reddog80p:
This saves as an .apk for me... http://www.androidfreeware.org/hotlinkmenottmp/0189d3/1264303029_Handcent_SMS_(NEW)_2.9.29.apk
[Touch CDMA Android Development] mrono:
No i didn't, I didn't know what I should fill in
[Touch CDMA Android Development] mirth18:
I am not sure why everyone is having such a difficult time with this? I just used the settings posted by jnadke in the third post and can send MMS fine using the stock Messaging app. I am running mssmison's eclair 7 build.
[Touch CDMA Android Development] cp0020:
yes but what phone are you using?
[Touch CDMA Android Development] mirth18:
Vogue.. this IS the vogue forum.. ;)
[Touch CDMA Android Development] mrkite38:
Seriously? if he asks, there's a reason he's asking. There are at least 4 phones supported under the 'vogue' kernel and it's a pain to start trying to help someone then realize that they have a different phone. Do yourself and the rest of us a favor - put your phone (and maybe your carrier) in your signature so we don't have to ask.

/rant
[Touch CDMA Android Development] cp0020:
what he said lol. but ive tried those settings and it'll send but it wont actually make it to the other person.but yes there are several different types of phones floating around on this forum and it gets pretty confusing
[Touch CDMA Android Development] mirth18:
Wow.. I guess I have to tread lightly on this forum. I was assuming that the ;) smiley would indicate that I was joking around. :( :( :( :(

My original intent was to help by saying what worked for me. I have verified that the MMS is sent and received.

I will update my sig with the information, thanks for pointing that out as a helpful way to move forward.
[Touch CDMA Android Development] cp0020:
to your running a sprint touch/vogue and you put those settings in and your able to fully send mms? i thought those setting were for the tp1? ive tried alot of differnt stuff and i cant get it to send
[Touch CDMA Android Development] mirth18:
Yes.. I just updated the Android APN MMSC and MMS port as indicated in the third post, saved, rebooted and then sent MMS to my wife. Verified she got the pic. I am using the latest eclair nbh that dzo put out to fix the bluetooth freezes, maybe that helps?

If you want you can PM me your number and we can try exchanging MMS.
[Touch CDMA Android Development] cp0020:
i would but my touch screen broke. its gonna be a few weeks before i can get it fixed. just to be exact, your on mssmisions eclair and what apn did you click on? cause i know that there is no android apn on myn's
[Touch CDMA Android Development] mirth18:
Settings->Wireless & networks->Mobile networks->Access Point Names->Android

'Android' is the only APN I have.
[Touch CDMA Android Development] Reddog80p:
Mine works as well but I'm using the verizon mmsc settings. My MNC is set to 995. I'm running Myn's build. I edited the t-mobile apn and when I saved it disappears but still works. Make sure your not including the <> around your ten digit number or it will not work.

Mirth what's your MNC set to?
[Touch CDMA Android Development] mirth18:
Mine is 995 as well.. was already populated in eclair build.
[Touch CDMA Android Development] cp0020:
what do you mean by already populated in eclair build? sorry if thats a stupid question im a little slow :) lol
[Touch CDMA Android Development] mirth18:
I mean that MNC property was already set to 995 in the 'Android' APN in mssmison's build.

IE, when you navigate to the 'Android' APN to edit it.. those values were already filled in.
[Touch CDMA Android Development] Reddog80p:
He mean's the default MNC in the eclair build is set to 995.
[Touch CDMA Android Development] cp0020:
oooohhh ok. yeah once i get my touch screen fixed im gonna have to mess with mms on mssmisions eclair.
[Touch CDMA Android Development] myn:
What does MNC 995 dictate?
[Touch CDMA Android Development] Reddog80p:
Not sure. DZO is the man to ask in the kernel thread.
[Touch CDMA Android Development] thoughtlesskyle:
hey i know it will be time consuming but can you give me whats entered in all of your fields since Donut doesnt have just an android APN
[Touch CDMA Android Development] mrkite38:
I don't think we're quite sure. :p

mnc (mobile network code) and mcc (mobile country code)... iirc dzo has stated that it shouldn't matter for the

data

connection, but the carriers could be checking that info for services like mms, who knows?

Myn, that info's in build.prop, right?

NOPE - info's in apns-conf.xml, I'm sure everybody already knew that. SOOoO you could try changing the 'android' apn defined in that file to reflect the sprint info and see what happens. Probably 310/120. I gotta believe someone's tried it, though.
[Touch CDMA Android Development] myn:
The apn list is indeed in the apns-config.xml. However the dictation is in the ril.

Interestingly enough in Warm Donut the default values are continuously overwritten by the full pay market script which is a service. This explains why when people make a change manually it doesn't persist as the service is overwriting it.

dzo just gave me a brand new ril a couple of days ago with some MNC/MCC settings configured for the same values used in the Full Market script (T-Mobile US). This eliminates the need for the full market service now.

This should hopefully give users the ability to edit their APN without worrying about the values being overwritten by the service.
[Touch CDMA Android Development] mrkite38:
Ha - I was just looking at that ril and wondering why it was there since I didn't see an update in the kernel thread.

So you'd have to change the xml and comment out the market fix bit from sysinit, or change the marketenable script to reflect the mnc info from Sprint. OR you could just wait for myn's next release. :)
[Touch CDMA Android Development] egzthunder1:
Hey mrkite!,

I guess that myn forgot to update his first post with the submission I made on his thread. In either case, I played with the apn-config.xml and changed the value of Android to 995 (which I believe was set for 210) and that brought my connection back to life (still no luck with gapps, Beautiful Widgets, or most apps that require an internet connection for MetroPCS, but at the very least, I get e-mails and can browse the web). I also added an entry for MetroPCS, which I believe it isn't doing jacksquat :), but at least I had fun trying...

From what dzo has said, the 995 is a generic number that enables internet connection (or something like that).

If you are interested in the apn-config that I uploaded, let me know and I will point you to it. I also have a nice little apk in there that allows you to back up and restore the xml.
[Touch CDMA Android Development] mrkite38:
Yeah, I think I didn't get enough sleep last night - I'm reading the thread backwards. 995 IS working to send on sprint, others are NOT working, is that right? So someone could change the stuff I mentioned in myn's build, but use 995 INSTEAD of 210 or whatever it is now.
[Touch CDMA Android Development] hamagc:
995 is the default for cdma.

however i have seen a samsung moment using the following mcc="310" mnc="120"

i never tried to change them manually in the apns-conf.xml so whenever i did change those values, the apn was deleted.

but we are still betting on the ril being the issue in not letting the mms in, or getting confused when i sees an incoming mms. (tp1 side of things)

if the touch is still not sending mms, i would def. try to play with the apn a bit to see if you can get 995 to stick and see if it will allow you to send.
[Touch CDMA Android Development] hamagc:
ok so i have edited the apns-config.xml file to allow 120 for the mnc.

i replaced the file in the /system/etc directory and in the /etc directory.

the file in the /system/etc directory sticks but the one in the /etc directory does not stick. everytime i reboot it reverts back to the original one that was there from 3/17.

and i still can not change the mnc value from 995 to 120. still deletes it, which makes me think that the values are pulled from the apns-config file in the /etc directory, not the /system/etc directory.

any input would be great guys!
[Touch CDMA Android Development] hamagc:
oh, almost forgot. to do this i used root explorer. root explorer can not get the write abilities when using system.sqsh, i used staysafe.apk to create a system.ext2 file which i am now booting off of. deleted the system.sqsh file alltogether.

using the ext2 file system, i am able to get root access to do these changes. can't be done in squash.
[Touch CDMA Android Development] mirth18:
I recently switched from the eclair build back to this build and now understand the issue. MMS just works on eclair with the proper MMSC url and MMS port.

I am sure everyone involved already knows this but just to be clear this is a donut / myn's build problem only right?
[Touch CDMA Android Development] cp0020:
so you can send mms from your phone on eclair? and hopefully myn wont mind but.... the next release should fix that
[Touch CDMA Android Development] mirth18:
Yes.

[10 chars]
[Touch CDMA Android Development] jdemar:
you can send mms on eclair, but you can't take pictures with the camera :(
[Touch CDMA Android Development] inertone:
people on verizon CAN send with myns build

just not receive
[Touch CDMA Android Development] thoughtlesskyle:
works in warm eclair APN will still vanish but i just tested it on 2 email addresses and a friends phone

edit the T-mobile APN to this

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>

save then reboot
[Touch CDMA Android Development] jaiden05:
If I had my original changed should I add this as my MDN?
[Touch CDMA Android Development] hamagc:
still nothing new huh?
[Touch CDMA Android Development] thoughtlesskyle:
except that it works? why would there be more?
[Touch CDMA Android Development] hamagc:
you guys got sprint mms incoming to work? i didn't see it confirmed anywhere in here.
[Touch CDMA Android Development] thoughtlesskyle:
we never had a problem with incoming because of the way mms was built for the vogue, while all of the other phones have an mms application the vogue never had that at launch we would get sent links, there was no mms app until the very end of it's life, so we still get them as links ontop of now being able to send them
[Touch CDMA Android Development] hamagc:
lol well that doesn't help me at all. damnit!

thanks for the update!
[Touch CDMA Android Development] thoughtlesskyle:
no problem just another reason why i love my vogue
[Touch CDMA Android Development] chumpalunski:
Anybody got this to work with 2.2 ? I was able to on 2.1 by changing the APN settings. But now it just disappears after saving.
[Touch CDMA Android Development] thoughtlesskyle:
would you seriously forum search before asking this question its been answered at least 30000000 times
[Touch CDMA Android Development] smojica:
MMS WORKS!

Hello everyone. I was able to get REAL MMS to work using these APN Settings. I got it to work on

Incubus26Jc's Super Eclair 2.1 Odexed [RLS6.1] - [6/24/10] Working Camera!!

and

Incubus26Jc's Super FroYo 2.2 RLS3 after that build the APN was changed and MMS no longer works. I am running Super Eclair just for MMS.

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>
[Touch CDMA Android Development] Naemion:
Got it to work as in getting pics straight to your phone? or just a link to the browser?
[Touch CDMA Android Development] smojica:
straight to my phone. Like it should be
[Touch CDMA Android Development] Naemion:
I wonder if those setting will work for boost cdma since it runs through Sprint's network. If not I wonder if the mm.myboostmobile.com will work.

Another question though, how did you get your apn settings to save? Everytime I try it goes away as I save.
[Touch CDMA Android Development] hamagc:
i am so jelious right now :mad:
[Touch CDMA Android Development] Naemion:
It sucks cause when finally everything is running good on FroYo, I find a MMS fix for boost mobile on WinMo. I would really love to get this working, but the only fix I have found is in the form of a .cab, which you can't use on Android.
[Touch CDMA Android Development] hamagc:
the only way to tell is to test it out on froyo.

you can't change the mnc and mcc numbers. that deletes the apn. but everything can be changed. for cdma, the mnc and mcc numbers shouldn't matter anyways.

on our end it looks like it's an ril issue. the msg notification comes in but the message doesn't.

for boost try to find the server and port numbers and throw them in your apn and see if it does anything.
[Touch CDMA Android Development] Naemion:
A .cab file will not work on Android. It is a WinMo file, like a .exe.

The server for Boost is Http://mm.myboostmobile.com and the port is 80, but I have set those and I still can't send or recieve.
[Touch CDMA Android Development] nickel911:
This is getting a bit muddled now ..... So we have the right custom settings in ECLAIR, but this does not work in FROYO 2.2? Or it does as well? Because I would like to test this out on the latest incubus 10.5 RLS
[Touch CDMA Android Development] thoughtlesskyle:
here is the easiest way to do it, so in froyo after RLS 3 they went to using an RIL just like what donut used, attached is an update that changes the RIL to the old settings, update your current build to it and then change the APN since you dont need to change the MNC because it is set for CDMA your apn will not disappear and your settings will be saved

this was all answered in another thread like 2 weeks ago
[Touch CDMA Android Development] Naemion:
Is that for sprint or Boost as well?
[Touch CDMA Android Development] hussmanne:
So update with this tar file on RLS 10.5, or roll back to RLS 3 and update with this file?

Thank you in advance.
[Touch CDMA Android Development] thoughtlesskyle:
You can use it with any release
[Touch CDMA Android Development] hamagc:
do you know what changes were in that ril? once i put it on my tp it broke the radio. would love to apply the changes to our ril however.
[Touch CDMA Android Development] thoughtlesskyle:
I'm not sure what the changes were, that's a question for dzo, the disappearing apn is caused by the paid market script I know there are ways to turn it off but you lose your paid apps in the market
[Touch CDMA Android Development] hamagc:
ok i'll shoot a pm to dzo, thanks!
[Touch CDMA Android Development] tablo:
Can someone please explain how to update the RIL with the file that thoughtlesskyle attached or direct me to the thread he referenced? My APN setting keep disappearing after saving.

Thanks.
[Touch CDMA Android Development] thoughtlesskyle:
Put the androidupdate.tar from that zip in the anboot folder on your SD card restart your phone and hold volume up then when your in the nomorootfs menu choose update
[Touch CDMA Android Development] know.patience:
worked for me and it didn't break my radio. thanks!

now if i could just figure out why my sd card is not working i'd be in business.
[Touch CDMA Android Development] thoughtlesskyle:
If your on a vogue it shouldn't break your radio
[Touch CDMA Android Development] tablo:
Thank you very much. I got my APN to update to from your instructions, but my MMS is still not functional.

I go to Gallery >> choose pic >> Share >> Messaging >> then I put in a number to send the pic to but it just stays on "Sending..." and never completes the send. Is there something I missed or a different method to send MMS?
[Touch CDMA Android Development] thoughtlesskyle:
did you reboot your phone after you saved the apn i don't know if that will help
[Touch CDMA Android Development] tablo:
Yes, I rebooted a few times. I'll play around with some more. Thanks for the suggestion.
[Touch CDMA Android Development] thoughtlesskyle:
only other thing i can think of is having to turn the paid market script off
[Touch CDMA Android Development] tablo:
I updated these 2 settings in my APN and I can now send MMS!

MMSC:http://63.215.195.152/servlets/mms?X-SPRINT-MDN=(10 didgit phone number)

MMS Port: 80

Still have to go to a Sprint URL to receive MMS, but this is def. better than no MMS functionality at all. Thanks!
[Touch CDMA Android Development] thoughtlesskyle:
oh i forgot to mention that step :P

do the messages still come in under 9000 or do they still come up in the thread
[Touch CDMA Android Development] tablo:
No sweat. They come up under 9000. Is there a way to fix that?

Thanks!!
[Touch CDMA Android Development] thoughtlesskyle:
i wasnt able to find one, i think its something on sprints side actually like a month ago i noticed the changed, but even with a stock apn it still did that either that or something with froyo
[Touch CDMA Android Development] nickel911:
Hmmmmm, I am sure there is a reason for this, but after I applied the UPDATE, I had to re-enter my GMAIL password (said that it was incorrect).

Otherwise I can now send MMS on sprint directly from my VOGUE (pause for applause). Thanks to everyone who made this possible. I read thru the whole thread, but can someone explain why we cannot use settings from a SAMSUNG MOMENT to fix the other part of this? (namely the receiving part). I am sure its entirely more complicated than I think. Also, does it have something to do with the TEXT notifications coming from this "9000" number on sprint. And what's this "9000" thing about?
[Touch CDMA Android Development] thoughtlesskyle:
the gmail password thing is normal, i think its some sort of security setting, i dont know why it comes in under 9000 it did for me on froyo even without the apn being changed so i dont know but i did switch to eclair for a little while and it still did it i almost wonder if its something on sprints side, and the moment settings more than likely wont work because of the way our phones receive sms, we were never meant to get pictures sent directly to the phone so i dont know how some other people are getting around it
[Touch CDMA Android Development] ricerx614:
can't get it to work for me.
[Touch CDMA Android Development] superflysocal:
i am running incubus froyo rls11

should i update the existing APN (labelled T-Mobile) or create a new APN as suggested by the first post?

i have a Sprint Touch
[Touch CDMA Android Development] thoughtlesskyle:
no update to the radio like 2 pages back

then when the APN says android, change it to those settings
[Touch CDMA Android Development] weezyfeezy:
I was able to just edit the existing APN and change the values. Now, I can send mms, but still receive via the picture mail website link.
[Touch CDMA Android Development] thoughtlesskyle:
you always will receive them as links, that one guy some how was able to get around it but, our phone was only ever meant to get sent links
[Touch CDMA Android Development] superflysocal:
crap, i installed that update and got the android apn but now i lost internet, including that 3g symbol.

i have sprint touch running incubus froyo 2.2

how do i get internet back or my original radio back?

edit:

nevermind, it's working. shouldn't have changed apn type to mms
[Touch CDMA Android Development] shiftasic:
So I went ahead and applied the old radio APN fix and edited the MMSC and MMS port settings to the Telus settings suggested online and I proceeded to send an MMS.

Send sucessful. But immediately following the successful send I had a text sent to me from 16505551000 stating;

"subjectAuto Upgrade Your legacy account has been upgraded to an MMS account."

USERID:1173567790162*****

PASSWORD:a0d3dd04bc1*****

Anybody had this or something like it happen yet.
[Touch CDMA Android Development] thoughtlesskyle:
since this is a sprint thread probably not ;)

on a side note, to get pictures to send to your phone instead of the link (i dont have my touch active to test this out), there is an option in the messaging menu to spoof your user agent, try changing that and see if it fixes it
[Touch CDMA Android Development] nickel911:
Not seeing this option on the latest froyo builds.... is this donut or eclair?
[Touch CDMA Android Development] know.patience:
that option is in the messaging app settings. i've been looking around trying to find what custom settings would be good to use but haven't found any answers yet.
[Touch CDMA Android Development] thoughtlesskyle:
what happens when you pick a BB 8800
[Touch CDMA Android Development] hamagc:
hey guys, thought i would pop in again and see if any new development has come up.

last i saw, there was no mms on 2.2, but with the use of the ril posted a few pages back you had true mms on 2.1

i've pmed dzo to see if he can look at our ril to see if anything needs to be changed. i'm sure he is busy though.

our status is still the same, can send but not receive. can see the mms come in (3g icon drops to E for a second then goes back which means the mms notification is coming in) but android isn't grabbing the mms.

figured i would see if there are any suggestions.

thanks guys!
[Touch CDMA Android Development] thoughtlesskyle:
2.2 was actually the one that needed the RIL update to get MMS, both work fine for sending and receiving (still and always as links). but yea everything is working on that front.
[Touch CDMA Android Development] thoughtlesskyle:
what happens if you change the user agent any change?
[Touch CDMA Android Development] hamagc:
no option to change useragent but we aren't getting links, we have true mms on our devices.

i spoke with sprint who said it would not be possible to get weblinks on our devices (atleast not on their end. i would rather have weblinks than nothing at all).

someone said they were getting true mms on their vogue. speaking with Dzo he said he didn't think that was possible. maybe via spooing useragent though.

let me see if i can spoof my useragent (option isn't readily available) and play.

thanks for the help guys!

edit: still no change. stole the mms.apk from the cm6 build for the g1 which enables me to spoof my UA and still no change. 3g drops to e and back to 3g without a msg coming in.
[Touch CDMA Android Development] nickel911:
Let us know how it turns out.
[Touch CDMA Android Development] wellVersed:
Sprint MMS step by step

I've done a fair amount of reading for Sprint Android MMS, but some of these threads started awhile back and have seemingly differing instructions... could an expert perhaps provide a step-by-step process to get Sprint MMS working (as much as possible, weblinks whatever) after a clean install of Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS13] [8/18/10]?

Thanks in advance.