I purchased an unlocked nexus 4 last month to go with my prepaid unlimited voice + data on straight talk. i had previously joined s/t via BYOP from T-Mo (also didn't have data with my old phone, but S/T said I'd need answers from Samsung and T-Mo, and the latter two said "Only the other can help you." Later I got an e-mail from Samsung admitting that they could have helped, but they'd be violating their agreement with T-mo. grrr)
So, I cut up my mini-Sim, put it in the micro-sim holder, changed the APN in accordance with S/T instructions. Voice and text messages work like a charm. Data works like a charm, but only via wi-fi. Signal strength -- great. T-Mo coverage in this area -- great. The 3-G icon does not appear in the status bar. Any time I try to connect via S/T -- whether it's maps or Itunes or chrome browser -- I get http error 500 (internal server error), along with the text "encountered an error while retrieving http://androidapi.t-mobile.com/apppack/mvno.html." don't know whether that's relevant or not, but i find it curious that despite my straight talk apn config, the browser immediately tries to retrieve a t-mo page...
Talked with Straight Talk for 45 minutes today, and they concluded -- wait for it! -- that only the manufacturer can help.
anybody else out there with similar problems? or better yet, someone who *had* similar problems but was able to resolve them?
So, I cut up my mini-Sim, put it in the micro-sim holder, changed the APN in accordance with S/T instructions. Voice and text messages work like a charm. Data works like a charm, but only via wi-fi. Signal strength -- great. T-Mo coverage in this area -- great. The 3-G icon does not appear in the status bar. Any time I try to connect via S/T -- whether it's maps or Itunes or chrome browser -- I get http error 500 (internal server error), along with the text "encountered an error while retrieving http://androidapi.t-mobile.com/apppack/mvno.html." don't know whether that's relevant or not, but i find it curious that despite my straight talk apn config, the browser immediately tries to retrieve a t-mo page...
Talked with Straight Talk for 45 minutes today, and they concluded -- wait for it! -- that only the manufacturer can help.
anybody else out there with similar problems? or better yet, someone who *had* similar problems but was able to resolve them?