Jump to content

No data connection on 1xrtt


Recommended Posts

Since upgrading to my Galaxy S5 I have noticed that when I fall back to 1xrtt I have no data connection available. The same thing happens when I'm roaming on U.S. Cellular. 1xrtt worked for data on my single band S4. Is anyone else experiencing this on tri-band handsets?

Link to comment
Share on other sites

Since upgrading to my Galaxy S5 I have noticed that when I fall back to 1xrtt I have no data connection available. The same thing happens when I'm roaming on U.S. Cellular. 1xrtt worked for data on my single band S4. Is anyone else experiencing this on tri-band handsets?

 

I actually just noticed this on my M8. On native Sprint 1x, my phone refuses to turn on mobile data.

Link to comment
Share on other sites

I have experienced very very slow data on 1xRTT, but its definitely expected.  or at least I expected that.  

Link to comment
Share on other sites

I actually just noticed this on my M8. On native Sprint 1x, my phone refuses to turn on mobile data.

Hmm weird I get 1x a lot when I'm on fringe areas or in CDMA only mode with data. Guess the m8 H/K edition is quite different then the m8 regular variant. More bugs but seems OK this go around.
Link to comment
Share on other sites

Data roaming is enabled, but even with native sprint coverage I get no data. The phone kicks out an error code. I think it was 67, I'll have to pay closer attention next time it happens.

Sent from my SM-G900P using Tapatalk

Link to comment
Share on other sites

Forced CDMA only and got this.attachicon.gifuploadfromtaptalk1407466241724.jpg

 

Maybe Sprint still has more CDMA1X voice traffic than we realize, and that precludes enough bandwidth to make a CDMA1X connection to the data server.

 

Regardless, whatever you do, steer clear of the "Korea Mode" in your pic.  Almost a decade later, I still do not know its purpose.  But the end result is bad, really bad.

 

AJ

Link to comment
Share on other sites

Forced CDMA only and got this.attachicon.gifuploadfromtaptalk1407466241724.jpg

Sent from my SM-G900P using Tapatalk

curious do you have an airave?
Link to comment
Share on other sites

I do not have one.

I usually got that error when I did a profile update on the airave, and then went outside of the airave zone, but a new profile update outside of the airave zone fixed it usually.
Link to comment
Share on other sites

Maybe Sprint still has more CDMA1X voice traffic than we realize, and that precludes enough bandwidth to make a CDMA1X connection to the data server.

 

Regardless, whatever you do, steer clear of the "Korea Mode" in your pic.  Almost a decade later, I still do not know its purpose.  But the end result is bad, really bad.

 

AJ

 

Wait what happens? Have you done it before?

  • Like 1
Link to comment
Share on other sites

Maybe Sprint still has more CDMA1X voice traffic than we realize, and that precludes enough bandwidth to make a CDMA1X connection to the data server.

 

Regardless, whatever you do, steer clear of the "Korea Mode" in your pic.  Almost a decade later, I still do not know its purpose.  But the end result is bad, really bad.

 

AJ

I'm curious about this Korea mode as well, please allow us to learn from your actions so as that we may not be doomed to repeat them.

Link to comment
Share on other sites

Ditto.

 

I'm in L.A., and 1x on iPhone 5S and Nexus 5 won't establish a data connection. It so consistently won't connect to data, that I'm starting to think that Sprint is blocking data over 1x (not necessarily unwise, to ensure enough bandwidth for voice).

Link to comment
Share on other sites

I'm curious about this Korea mode as well, please allow us to learn from your actions so as that we may not be doomed to repeat them.

This is an old thread but it may be applicable.

http://www.howardforums.com/showthread.php/796999-Toggle-KoreaMode-!

  • Like 1
Link to comment
Share on other sites

Error code 67 is a provisioning problem. I've had it before after changing devices. I think its from your phone number or data credentials being incorrect in your device. If you call Sprint technical support explain the issue and give them that error code, they should be able to walk you through it.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

Hmm, the author of that nearly decade old HowardForums thread seems vaguely familiar.  If only we could have someone that experienced here at S4GRU...

 

;)

 

AJ

Look it that....AJ lived vicariously through me...wait....I lived vicariously through AJ....wait.......... :frantic:

  • Like 1
Link to comment
Share on other sites

Error code 67 is a provisioning problem. I've had it before after changing devices. I think its from your phone number or data credentials being incorrect in your device. If you call Sprint technical support explain the issue and give them that error code, they should be able to walk you through it.

Robert via Samsung Note 8.0 using Tapatalk Pro

wait calling in an issues and them resolving it? When did this start happening :P
  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • https://www.theverge.com/2022/7/1/23191183/sprint-network-shutdown-t-mobile-sunset-lte-3g-cdma
    • I was thinking that Dish could be in a pickle with limited low-band.  But forgot they will have n26. Dish needs to also push carriers to support that band as well. I know that is like 14x14.  With 5G, is that something that Dish will be fully able to utilize?
    • Update: Throughout my time in Ireland, I've been on 4G (LTE) via Global Roaming with no issues. Nothing from Sprint/TMo re upgrading service. Hopefully, no bad surprises on my next bill . . .   Installed new TMo SIM in my daughter's phone while here, and she's had no data whatsoever. I had received mixed responses from TMo folks prior to the trip as to whether that was possible.
    • Went up to Woodbury again and it looks like the Archdiocese and NW Spectrum LLC are hampering T-Mobile's ability to expand beyond 40MHz still. Unlike in NYC, Band 41 is still alive and well on Sprint in Orange County. I was seeing 20MHz of Band 41 on both Sprint and T-Mobile. n41 is still at 40MHz unfortunately with no sign of a second n41 carrier anywhere. 
    • Author kinda doesn't know what they're talking about, as they assumed their speeds were n71-only (it's like they half-read the PCMag article they cite). The speeds they're mentioning are 100% from n71 + n66 SDL, which also explains speeds dropping off a cliff when they walk indoors. In fact, Dish has some paired AWS-3 in Spokane, albeit just 5x5, so I wouldn't be surprised if they haven't bothered deploying that and are just doing 71 + n66 SDL (the former at 5x5). May head down to San Marcos and New Braunfels tonight to do some testing. I expect either n71-only or n71 + SDL, not sure which. n71 is 5x5 here as Dish has leased half of their 10x10 to T-Mobile. When that lease expires they'll be at 10x10, and they could get another 10 MHz FD (albeit not contiguous) from speculators if T-Mobile didn't outbid them. Will be interesting to see who buys what when.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...