Jump to content

Data issues with Us Cellular roaming


Cardsfan96

Recommended Posts

On 10/19/2018 at 10:25 AM, bretton88 said:

I have an unlocked Note 9 on Oreo and it LTE roams fine. So it might just be a Pixel issue. Or Pie.

Sent from my SM-N960U1 using Tapatalk
 

Be nice to know which it is (if either)!

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...
November update being pushed out now to Pixel/Nexus devices...
For what it's worth, with the November update, T-Mobile roaming works on my Pixel 2 XL. I didn't see AT&T roaming tho. The last I had seen it was in June, and I think it may have stopped working for a bit after that until recently.e7aaa81785588b2bfa8e673dfda40d8e.jpg1405d75d3a32ab0319347cc5e77ad555.jpg

Sent from my Pixel 2 XL using Tapatalk

  • Like 1
Link to comment
Share on other sites

16 hours ago, ingenium said:

For what it's worth, with the November update, T-Mobile roaming works on my Pixel 2 XL. I didn't see AT&T roaming tho. The last I had seen it was in June, and I think it may have stopped working for a bit after that until recently.

Sent from my Pixel 2 XL using Tapatalk
 

Is this in Cali?

The T-Mo roaming is great news, but it would be nice to confirm that USCC roaming is still working on Pixel devices.

Link to comment
Share on other sites

Is this in Cali?
The T-Mo roaming is great news, but it would be nice to confirm that USCC roaming is still working on the Pixel devices.
Yeah it is. East of Sacramento

Sent from my Pixel 2 XL using Tapatalk

  • Like 2
Link to comment
Share on other sites

When devices roam do they use carrier aggregation or will they only connect to a single carrier?
When I looked while T-Mobile roaming, it was only B4 (other bands may not have been present, or also possible that they didn't have B4-B12 CA enabled at all). When roaming internationally, CA works.

Sent from my Pixel 2 XL using Tapatalk

  • 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.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Was able to install the March 1 Android security patch. Seems slightly more accurate with 5g ca band id, but can not swear by it. Updated google play system update through the software information screen to March 1. *#73# still works. Froze updates waiting on SCP update beta to fix n41 showing as n38.
    • Just installed it. Thanks for the info.  71 mb mar 1st date.
    • There's a permit for a new 47 story building at 205 Montague St in Downtown Brooklyn. The problem is that  T-Mobile eNB 48352 is on the building next door and this new building will block two out of 3 sectors of the site. For reference, the new building will be roughly as tall as 16 Court St which is right across the street. This site is the primary site covering Cadman Plaza so I wonder what the plan is. Will they just try to change sector placement, move to a different building, or will this just speed up the conversion of the Sprint site at 25 Monroe Place?
    • At least not recently.  I think I might have seen this a year ago.  Not Sure.
    • Did they previously hop between n38 and n41 in prior version of SCP, or have you always seen n41 displayed properly?
  • Recently Browsing

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