Jump to content

Handoff Native to Roaming?


owensri2

Recommended Posts

An interesting thing happened while I was leaving work today and heading home. I just recently moved to Charlotte, NC (Matthews, suburb). I started a call on the Sprint network in Hartsville, SC, and figured that it would drop once I drove out of Sprint native coverage and the call continued. I decided to look at the display, and it showed that I was roaming! I didn't know that it was possible.

 

The roaming area I drove into is US Cellular. Any ideas? This is the first time that I didn't drop a call while going from Native coverage to Roaming. :lol:

Link to comment
Share on other sites

Are u positive you started the call in sprint coverage and were not roaming when rhe call started? Ive seen my galaxies roam and hang on to the roaming network even once they are back in native.

Link to comment
Share on other sites

Are u positive you started the call in sprint coverage and were not roaming when rhe call started? Ive seen my galaxies roam and hang on to the roaming network even once they are back in native.

 

I am 100% positive. I looked at the signal, and I was near the Sprint tower in Hartsville when I initiated the call.

Link to comment
Share on other sites

I can't say I've ever had that happen, however, my roaming in MI is Verizon 850, so the switch from Sprint 1900 is most likely a hard handoff. Perhaps it is a soft handoff due to US Cellular using 1900 spectrum in your area?

 

We need AJ to chime in here :)

Link to comment
Share on other sites

In my area, the only PCS roaming is Cricket and Commnet. I cannot ever handoff to Sprint or vice versa on these. If I start a conversation on any of these two, I will stay connected to that network, even if I drive into Sprint coverage.

 

It's extremely problematic on Commnet, as they have poor coverage inside Sprint coverage areas. They tend to place sites outside of Verizon/Sprint coverage to sell roaming to them. So I will get dropped when the roaming signal finally runs out, and then I have to wait for my device to scan and connect to Sprint native or another roaming carrier to call back and continue.

 

Also, in my area, we have old Alltel and Verizon roaming on 850 Cellular. These never hand off to anything.

 

When making an outgoing call when roaming, I have to check which carrier I'm on first. Then I have to decide if that carrier has continuous coverage along my route, knowing it will not handoff to another roaming carrier or to Sprint. In many instances while roaming, I will cycle airplane mode to get a better carrier. Because Commnet is really bad for me as none of their sites overlap. So I cannot keep a phone call from one site to the next. I try to get Verizon as much as possible so I can keep the conversation as long as I need to.

 

When I get an incoming call while roaming, there is nothing I can do. I just warn the caller that I may lose service and that I'll call them back. I pretty much know every roaming seam in all of Northern New Mexico.

 

Robert via Nexus 7 with Tapatalk HD

Link to comment
Share on other sites

I can't say I've ever had that happen, however, my roaming in MI is Verizon 850, so the switch from Sprint 1900 is most likely a hard handoff. Perhaps it is a soft handoff due to US Cellular using 1900 spectrum in your area?

 

We need AJ to chime in here :)

 

No, soft handoff is possible only on the very same carrier channel. Plus, USCC has substantial Cellular 850 MHz footprint in the Carolinas.

 

So, if this handoff really did happen as described, it was almost certainly an inter band, inter MSC hard handoff. I would like to see it demonstrated again to show that it is repeatable. Then, we could examine how it is possible.

 

AJ

  • Like 1
Link to comment
Share on other sites

When making an outgoing call when roaming, I have to check which carrier I'm on first. Then I have to decide if that carrier has continuous coverage along my route, knowing it will not handoff to another roaming carrier or to Sprint. In many instances while roaming, I will cycle airplane mode to get a better carrier. Because Commnet is really bad for me as none of their sites overlap. So I cannot keep a phone call from one site to the next. I try to get Verizon as much as possible so I can keep the conversation as long as I need to.

 

Robert via Nexus 7 with Tapatalk HD

 

How can you tell what carrier you are on before cycling airplane mode to another?

Link to comment
Share on other sites

 

How can you tell what carrier you are on before cycling airplane mode to another?

 

I use NetMonitor. It's the fastest way to find out.

 

Robert via Nexus 7 with Tapatalk HD

  • Like 1
Link to comment
Share on other sites

How can you tell what carrier you are on before cycling airplane mode to another?

 

Gotta know your local SIDs, baby. And that, appropriately enough, is going to be the focus of my next engineering screen article. I am thinking of calling it "SID and NIDsy." Anybody get this music reference?

 

AJ

  • Like 3
Link to comment
Share on other sites

Gotta know your local SIDs, baby. And that, appropriately enough, is going to be the focus of my next engineering screen article. I am thinking of calling it "SID and NIDsy." Anybody get this music reference?

 

AJ

 

I'm guessing its a Sid Vicious/Sex Pistols reference?

  • Like 1
Link to comment
Share on other sites

Just reproduced the handoff again on my way home. I started the call on Sprint, and it handed off to US Cellular!

 

I'd love to see engineering screenshots before, during, after handoff, and hangup

Link to comment
Share on other sites

Just reproduced the handoff again on my way home. I started the call on Sprint, and it handed off to US Cellular!

 

The only way that is possible is if their MSCs are harmonized. And I am not aware of that elsewhere, so it seems out of place here.

 

I suppose one possibility is that -- because this area outside of Charlotte is a former affiliate market -- AirGate PCS could have contracted to use USCC's MSC as its own. But even if that were the case, I would have expected Sprint to take that in house with its affiliate acquisitions several years back.

 

AJ

  • Like 1
Link to comment
Share on other sites

When Sprint 800 Mhz CDMA is launched for us to use' date=' will the voice calls change from 800 to 1900 to 800 on the fly?[/quote']

 

Robert observed this when doing his field testing in Austin

 

Sent from my cm_tenderloin using Forum Runner

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

Happened again today.  Started on Sprint, 6 bars near the tower.  I initiated a call and it ended up on US Cellular.  I looked at the screen after I had figured the call would have dropped, and the little roaming triangle appeared as soon as the display turned on.  The SID before the call was 4376.  I checked SignalCheck during the call after it had switched to roaming and it was 1648.  Any ideas on who the SID's belong to?  I would assume 4376 is Sprint, but not sure about the 1648 (US Cellular). 

Link to comment
Share on other sites

Any ideas on who the SID's belong to?  I would assume 4376 is Sprint, but not sure about the 1648 (US Cellular). 

 

Are you sure that you did not read it incorrectly?  SID 1643 is USCC.

 

AJ

Link to comment
Share on other sites

The only way that is possible is if their MSCs are harmonized. And I am not aware of that elsewhere, so it seems out of place here.

 

I suppose one possibility is that -- because this area outside of Charlotte is a former affiliate market -- AirGate PCS could have contracted to use USCC's MSC as its own. But even if that were the case, I would have expected Sprint to take that in house with its affiliate acquisitions several years back.

 

AJ

 

Perhaps related to the Sprint/USCC customer and spectrum transaction? Just throwing it out there as a possible reason, no idea myself.

Link to comment
Share on other sites

In my area, the only PCS roaming is Cricket and Commnet. I cannot ever handoff to Sprint or vice versa on these. If I start a conversation on any of these two, I will stay connected to that network, even if I drive into Sprint coverage.

 

It's extremely problematic on Commnet, as they have poor coverage inside Sprint coverage areas. They tend to place sites outside of Verizon/Sprint coverage to sell roaming to them. So I will get dropped when the roaming signal finally runs out, and then I have to wait for my device to scan and connect to Sprint native or another roaming carrier to call back and continue.

 

Also, in my area, we have old Alltel and Verizon roaming on 850 Cellular. These never hand off to anything.

 

When making an outgoing call when roaming, I have to check which carrier I'm on first. Then I have to decide if that carrier has continuous coverage along my route, knowing it will not handoff to another roaming carrier or to Sprint. In many instances while roaming, I will cycle airplane mode to get a better carrier. Because Commnet is really bad for me as none of their sites overlap. So I cannot keep a phone call from one site to the next. I try to get Verizon as much as possible so I can keep the conversation as long as I need to.

 

When I get an incoming call while roaming, there is nothing I can do. I just warn the caller that I may lose service and that I'll call them back. I pretty much know every roaming seam in all of Northern New Mexico.

 

Robert via Nexus 7 with Tapatalk HD

Make a custom PRL that lowers priority or gets rid of the Commet towers altogether.

 

 

I might be making a quick tut on that soon.

 

 

Link to comment
Share on other sites

  • 3 months later...

Well, since about the beginning of August, I am no longer able to handoff from native to roaming.  The call drops like it did before.  Strange...

 

The mysterious handoff over the summer must have been due to sunspots, a coronal mass ejection.

 

AJ

  • Like 2
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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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