Jump to content

Who roams on whom? (Updated Title)


burnout8488

Recommended Posts

I guess I'm most curious on who the other networks will roam on rather than who sprint roams on. But its cool to see how it differs in different areas.

 

In my hometown, we only have the big 4 networks. Would Verizon customers roam on Sprint? Are the devices capable of this?

Link to comment
Share on other sites

Who roams on who?

 

Uh oh, did Citizens United make wireless operators "people," too?

 

AJ

  • Like 2
Link to comment
Share on other sites

I know this is still Sprint, but here it's Carolina West (full native bilateral roaming), then Alltel, then US Cellular, then Verizon.

 

Edit: forgot to mention Cricket, I think they're after Alltel and before Verizon, probably same priority as USCC.

Link to comment
Share on other sites

I've roamed on Cricket and US Cellular in Tulsa. I've roamed onto Nextech in Kansas and Colorado. While in Idaho I've roamed on Inland Cellular.

 

On T-Mobile I've roamed onto Union Wireless, Viaero, CellularOne (Comnet and Chinook), Chinook (it actually said Chinook), and for what little they allow AT&T. Most of this roaming was HSPA but I imagine it was seriously throttled.

Link to comment
Share on other sites

In East Texas I've had Sprint roam on metropcs, and Alltel. Had a T-Mobile Sim in my nexus 5 and said it was roaming on Chinook wireless,which is labeled as cellular one. That is sad because I'm getting coverage from a roaming partner the next county over, with a farther tower, than I am with T-Mobile with a closer tower.

Link to comment
Share on other sites

In NYC, Sprint roams on Verizon exclusively. MetroPCS has a presence here but my guess is that Sprint simply has greater signal propagation than Metro so I never encounter their signal.

Since MetroPCS never had a PCS CDMA network in NYC, Sprint would never roam on MetroPCS in NYC. Sprint could only roam on MetroPCS in Texas, Florida, Michigan, and California, where MetroPCS had PCS CDMA.

  • Like 2
Link to comment
Share on other sites

Sprint is pretty well covered in this thread now, what about the other carriers? 

 

T-Mobile roams on AT&T, but only in certain, specific, hand-picked areas (on a nearly tower by tower basis). It's usually only allowed in places *far* removed from T-Mobile's own native coverage.

 

AT&T does not usually allow any roaming on T-Mobile, even when they have no native service and T-Mobile does. (This might be different for Business or M2M customers, or in some hand-picked markets -- I don't know about that specifically. But generally, normal lines do not allow roaming of any kind onto T-Mobile.)

 

This isn't always true however.  For instance, during Hurricane Sandy,  AT&T and T-Mobile agreed to complete network sharing temporarily, so that you could switch between them at any time on any device - http://www.engadget.com/2012/10/31/att-and-t-mobile-temporarily-share-their-networks-in-nyc-nj/

 

But acts like that (while always 100% technologically available) are very rare to see in practice.

  • Like 1
Link to comment
Share on other sites

ManBearPig roams the Earth alone.  ManBearPig simply wants to get you.

 

Ghjkl.JPG

 

AJ

  • Like 3
Link to comment
Share on other sites

Since MetroPCS never had a PCS CDMA network in NYC, Sprint would never roam on MetroPCS in NYC. Sprint could only roam on MetroPCS in Texas, Florida, Michigan, and California, where MetroPCS had PCS CDMA.

This explains why I get connected to MetroPCS around Los Angeles at times. I thought their CDMA network was dismantled already after the T-Mobile merger.

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.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • https://www.fiercewireless.com/wireless/t-mobile-gets-little-closer-accessing-its-25-ghz-spectrum-auction-108 Senator Kennedy's bill to grant the FCC temporary auction authority to finish processing the Auction 108 licenses it has sold to their proper licensees. This would greatly benefit T-Mobile.  This delayed process took what would have been a strategic advantage for T-Mobile (1 one year plus head start)  and turned into catch-up, since AT&T and Verizon haven been busy installing their c-band n77 in rural areas.
    • I configured -44/-3 scenarios on an Edge 2022 to be an invalid connection, so yes, it would show no service.. I didn't realize it was a frequent issue though. How certain are you about the other values? Perhaps they are just unchanged from the previous array of signal information that was reported? If that is the case, I can try to have the app discard -44/-3 datapoints and leave the screen unchanged. I worry about the slippery slope of having it display as -140, because that leads users to believe there is a -140 signal present, when in reality we don't know what the actual reading is.   Haha me and you both wish this!!!
    • Following up, I've gone into the office in person today and took my Edge with me. It looks like it now shows "No service" instead of the -44/-3 value.  I saw a lot of "no service" because it apparently does it a lot.  I'll check again on the train ride home later. Assuming I'm correct, is it possible to have some kind of middle ground on this?  I think it was showing other legitimate values, like the TA, even when it was showing -44/-3.  I'd prefer it show the data it has but at -140 dBm in those cases.  I recognize this could be a pain to implement, and if it is, then no worries, mostly curious. EDIT:  But now I'm sitting here thinking "what if the PCI is bad and I don't know it?"  But that can just as easily be the case on other phones that aren't caught.  I do regularly see bad PCI entries on my other devices, so maybe this isn't the best option.  Bleh, I wish this stuff just worked properly! - Trip
    • Forgot to follow up on this. The service was once again abysmal .
  • Recently Browsing

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