Jump to content

Straight talk offering LTE on the Sprint network w/ GS3

coorsleftfield

By coorsleftfield
in General Topics

 Share

Recommended Posts

Conan Kudo Member Level: eHRPD

Conan Kudo

Posted
Posted

Are Sprint's licenses critical to AT&T?

If so, could Sprint extract some more PCS or $$$ out of AT&T?

While the licenses are critical to AT&T, there is no way that Sprint will get any PCS from AT&T. It'll likely be a cash transaction, just like the acquisition of the US Cellular markets was.

Link to comment
Share on other sites
maximus1987/lou99 Member Level: 4G WiMax

maximus1987/lou99

Posted
Posted

 

 

 

Are Sprint's licenses critical to AT&T?

 

If so, could Sprint extract some more PCS or $$$ out of AT&T?

 

 

While the licenses are critical to AT&T, there is no way that Sprint will get any PCS from AT&T. It'll likely be a cash transaction, just like the acquisition of the US Cellular markets was.

Well Sprint could always use some cash.

Link to comment
Share on other sites
jamesinclair Member Level: 4G WiMax

jamesinclair

Posted
Posted

In the cases where Sprint provides customer service to the MVNO, the MVNO pays for that service.  It's an optional feature that costs more.

 

Robert

 

No, Verizon never handled straight talk customers, the problem was when they dialed the shortcut that was suposed to take them to straight talk customer service, sometimes theyd end up at verzion customer service and be irate that we wouldnt help them. That was 2-3 minutes of wasted time.

Link to comment
Share on other sites
S4GRU Member Level: LTE Advanced

S4GRU

Posted
Posted

No, Verizon never handled straight talk customers, the problem was when they dialed the shortcut that was suposed to take them to straight talk customer service, sometimes theyd end up at verzion customer service and be irate that we wouldnt help them. That was 2-3 minutes of wasted time.

 

I get your point.  And I'm sure it happens that way, especially with StraightTalk.  With ST, people have to choose which network they want their service on.  With most of the other Sprint MVNO's, the network they run on is much more opaque and people are often less clued in.

 

Robert

Link to comment
Share on other sites
centermedic Member Level: 4G WiMax

centermedic

Posted
Posted

Yes, really.

I really have to dispute that at least east of the Mississippi. I drove a truck OTR for a couple of years and the only places that I knew for a fact that i would have issues was Kansas(especially west of Salina) and Wyoming. Now, there were a few places that were somewhat remote that I did not get a signal but I can say that I was very happy with the coverage I experienced.

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
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • CalebM
      SignalCheck Beta Crew Forum

      By CalebM · Posted

      Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 

  • Recently Browsing

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