+ Reply to Thread
Results 1 to 6 of 6
  1. #1

    Join Date
    Jul 2012
    Posts
    6

    Re: right apn for straight talk sim card off a samsung galaxy s2 straight talk

    Hi guys, I had a Galaxy S2 straight talk version (branded) and I took the sim card and put it in on an att phone and call and text works, however, when I try to make the web and mms work, I can't. Does anyone know the right APN for a sim card out of a galaxy s2 branded phone? I tried this:

    APN: att.mvno
    Proxy: proxy.mvno.tracfone.com (also tried att2.tracfone.com)
    Port: 80
    MMS: http://mmsc.cingular.com
    Proxy: 66.209.11.33 (also tried att2.trafcone.com)
    Port: 80

    I know this settings work for an Att sim card off the web cause I had one before, the "att2.trafcone.com" I copied from the Straight Talk branded phone.


  2. #2

    Join Date
    Apr 2012
    Posts
    2

    Re: Re: right apn for straight talk sim card off a samsung galaxy s2 straight talk

    Remove the proxy. Leave it blank.

  3. #3

    Join Date
    Feb 2012
    Posts
    7

    Re: Re: right apn for straight talk sim card off a samsung galaxy s2 straight talk

    Remove the proxy. Leave it blank.
    I tried and didn't work :/

  4. #4

    Join Date
    Feb 2012
    Posts
    4

    Re: Re: right apn for straight talk sim card off a samsung galaxy s2 straight talk

    Did you the same settings as the St branded s2?

  5. #5

    Join Date
    Mar 2012
    Posts
    5

    Re: Re: right apn for straight talk sim card off a samsung galaxy s2 straight talk

    At one point, I did the same thing - took the activated sim from the ST branded S2 and put it in another phone (a TM SG2). Here were the setting I used that worked:

    name - AT&T MVNO
    apn - wap.tracfone
    proxy - blank
    port - 80
    username, pw, server - blank
    mmsc - http://mmsc.cingular.com
    mms proxy - att2.tracfone.com
    mms port - 80
    mnc - 410
    auth type - none
    apn type - internet + mms + supl

    When I had the proxy set to att2.tracfone.com, the data would crawl. Removing the proxy fixed that.