Jump to content

Recommended Posts

How exactly are you finding this out?
Was it from the February Pixel update?
How do you/we know when any of the combos go "live" on Sprint?
Thanks for the info!
As I've said in multiple previous posts, you need root with the pay version of NSG. That's the only way to get it on a Pixel.

It was either pushed in the Feb OTA, or Sprint pushed the config change. For what it's worth, the modem is identical in Jan and Feb OTAs (same sumcheck).

These are all "live", in that the phone will seemingly attempt to use them. The only additions here are domestic roaming combos. No international combos are present.

Interestingly, it has AT&T bands 14 and 30, but no 66.

No B71 for T-Mobile.

And it has B13 (Verizon) combos. Maybe a sign that Verizon LTE roaming is coming?

Sent from my Pixel 4 XL using Tapatalk

Link to comment
Share on other sites

14 hours ago, ingenium said:

As I've said in multiple previous posts, you need root with the pay version of NSG. That's the only way to get it on a Pixel.

It was either pushed in the Feb OTA, or Sprint pushed the config change. For what it's worth, the modem is identical in Jan and Feb OTAs (same sumcheck).

These are all "live", in that the phone will seemingly attempt to use them. The only additions here are domestic roaming combos. No international combos are present.

Interestingly, it has AT&T bands 14 and 30, but no 66.

No B71 for T-Mobile.

And it has B13 (Verizon) combos. Maybe a sign that Verizon LTE roaming is coming?

Sent from my Pixel 4 XL using Tapatalk
 

Can you share some of your speedtest results on Sprint? Are you in a Samsung market? Ericsson?

More importantly, is TDD-FDD enabled nationwide yet? Specifically Nebraska/West Iowa.

Thanks

Link to comment
Share on other sites

Can you share some of your speedtest results on Sprint? Are you in a Samsung market? Ericsson?

More importantly, is TDD-FDD enabled nationwide yet? Specifically Nebraska/West Iowa.

Thanks

I haven't really seen a speedtest get above 10 Mbps upload on B41. But on NSG it does show 2xCS UL if the signal is strong (otherwise it does 1 carrier with HPUE). NSG shows upload though in the 15-20 Mbps range, which is about the most I'd expect.

 

Samsung market.

 

I've seen FDD-TDD in Ohio, Pennsylvania, and NYC market. It's only used when B41 is too weak to use as a PCC, and it would switch to B25 anyway. The result is that B41 throughput isn't very good usually since it's so weak. I managed to get a speedtest with NSG running, and you can see B25 has 2 MIMO streams (rank 2, at 13 Mbps on one stream and 4 Mbps on the other). B41 is too weak to do 2 streams, so it's 1 stream (rank 1, at 3 Mbps on one carrier, 5 Mbps on another, and the third having no throughput)

3fd8ca454d3094aae7e9d9ec6c2b26d5.jpg

 

Sent from my Pixel 4 XL using Tapatalk

 

 

 

Link to comment
Share on other sites

16 minutes ago, ingenium said:

I haven't really seen a speedtest get above 10 Mbps upload on B41. But on NSG it does show 2xCS UL if the signal is strong (otherwise it does 1 carrier with HPUE). NSG shows upload though in the 15-20 Mbps range, which is about the most I'd expect.

 

Samsung market.

 

I've seen FDD-TDD in Ohio, Pennsylvania, and NYC market. It's only used when B41 is too weak to use as a PCC, and it would switch to B25 anyway. The result is that B41 throughput isn't very good usually since it's so weak. I managed to get a speedtest with NSG running, and you can see B25 has 2 MIMO streams (rank 2, at 13 Mbps on one stream and 4 Mbps on the other). B41 is too weak to do 2 streams, so it's 1 stream (rank 1, at 3 Mbps on one carrier, 5 Mbps on another, and the third having no throughput)

Thanks for the info. Man that app really rocks. Too bad it requires root grrrrrrr!

FDD-TDD is supposedly live in Denver.

Im gonna grab a Pix 4 when funds allow.

I appreciate all your input.

Link to comment
Share on other sites

Thanks for the info. Man that app really rocks. Too bad it requires root grrrrrrr!
FDD-TDD is supposedly live in Denver.
Im gonna grab a Pix 4 when funds allow.
I appreciate all your input.
It's easy to root Pixels. Especially if you do it as soon as you get the phone, before setting things up (I skip everything, even adding a Google account) since unlocking the bootloader does a factory reset.

NSG is tricky on the Pixel 4 though, since Google removed the Qualcomm diagnostics interface in the production build. You have to also flash the userdebug vendor.img from Google, which breaks some things in the February build (no dual SIM, you'll get no service and a "No SIM" error, and breaks active edge / squeeze for assistant). They all worked in the January build, so I'm hoping it gets fixed in March.

But worth it in my opinion for NSG. It's just such a useful app. You can find out so much information in LTE Signaling too if you know where to look (CA combos, the VoLTE enabled flag on an eNB, etc).

Sent from my Pixel 4 XL using Tapatalk

  • Like 1
Link to comment
Share on other sites

That's a big update.  I wonder if along the way the fix the problem where phone won't do LTE after losing signal due to a tunnel or an elevator getting stuck either roaming on TM, stuck on 3G or not having any data at all.

Link to comment
Share on other sites

15 minutes ago, crazy_vag said:

That's a big update.  I wonder if along the way the fix the problem where phone won't do LTE after losing signal due to a tunnel or an elevator getting stuck either roaming on TM, stuck on 3G or not having any data at all.

Looks like Carrier Services got updated for me today via Google Play.  I wonder if that's how update gets pushed?

Link to comment
Share on other sites

1 hour ago, jordanlong20 said:

Is there a consensus opinion (or even objective proof) about RF performance between the P3XL and P4XL, w/r/t holding or picking up weak signals? 

I am interested in this too. Would like to know compared to the Pixel 2 XL.

Link to comment
Share on other sites

Is there a consensus opinion (or even objective proof) about RF performance between the P3XL and P4XL, w/r/t holding or picking up weak signals? 
My Pixel 4 XL gets noticeable better performance than my 3 XL. I somewhat regularly drive a route that would cause me to drop Sprint service (or go to 1x only) and roam on all my Pixels until the 4. The 4 holds LTE constantly, doesn't even drop to 1x or 3G. Now I haven't tested how VoLTE performs on this route, but I honestly haven't seen my 4 drop LTE yet.

Sent from my Pixel 4 XL using Tapatalk

  • Like 2
Link to comment
Share on other sites

CA combos for the Pixel 4 in a format that's easier to browse. Missing Verizon combos because I don't have a Verizon SIM with active service (inactive SIM connects to CDMA only).

https://cacombos.com/device?model=GA00677-US

Some combos might be missing because so many were listed that it was getting truncated in the message. Sprint took a few attempts to get all of the non roaming combos, and some roaming combos may not be listed. So att and T-Mobile may also be missing some (they maxed out the message size too), but at first glance nothing stands out as missing.

Sent from my Pixel 4 XL using Tapatalk

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...
On 11/25/2019 at 7:42 AM, mikejeep said:

Same exact things are happening to me here in the Boston area. It's becoming very annoying. I resisted from toggling airplane mode the other day and remained roaming for over 6 hours in an area I know Sprint has had good LTE coverage for years. It also seems to struggle to pick LTE back up on its own once it drops back to 3G.. even when in areas of extremely strong LTE signal. Airplane toggle usually grabs LTE immediately, but we shouldn't need to do that.

Hopefully it's a software issue that can be resolved quickly. I have been trying to remember to report it through the My Sprint app, but not sure how helpful that really is.

This finally is fixed for me in the March update.  Amazing how quickly the phone gets LTE after a tunnel or elevator ride.

  • Like 1
Link to comment
Share on other sites

15 hours ago, crazy_vag said:

This finally is fixed for me in the March update.  Amazing how quickly the phone gets LTE after a tunnel or elevator ride.

Mine seemed to be better too, but I wasn't sure if I was paying close enough attention.. it would be awesome if it was resolved.

Link to comment
Share on other sites

9 minutes ago, mikejeep said:

Mine seemed to be better too, but I wasn't sure if I was paying close enough attention.. it would be awesome if it was resolved.

It was a huge pain for me on Caltrain.  I'd be tethering, so I'd lose data.  I'd have to toggle airplane mode, then re-enable tethering.  And then wait for my laptop to "rediscover" my phone and reconnect.  Easily a minute of work would be lost while I wait for things to be back to normal.  And with 4 tunnels, it's a lot of work or a long wait...

Link to comment
Share on other sites

  • 2 weeks later...

Got my Pixel 4 XL yesterday. Pretty sweet phone! It will not connect to my Magic Box no matter what. Tried rebooting, toggling airplane mode, reboot magic box, etc.

I checked the PRL and it says "1". I updated the PRL and it still says "1".

Does everyone else's phone say PRL version is 1? How about connecting to the Magic Box? Any issues?

Edit: A day later and it connected to my MB but PRL still says "1"????

  • Like 1
Link to comment
Share on other sites



Got my Pixel 4 XL yesterday. Pretty sweet phone! It will not connect to my Magic Box no matter what. Tried rebooting, toggling airplane mode, reboot magic box, etc.
I checked the PRL and it says "1". I updated the PRL and it still says "1".
Does everyone else's phone say PRL version is 1? How about connecting to the Magic Box? Any issues?
Edit: A day later and it connected to my MB but PRL still says "1"????


Yeah devices usually take a bit to find a MB initially.

My PRL is fine. f8f486ce016d09e2d6a8f28a7789bdcb.jpg

Sent from my Pixel 4 XL using Tapatalk

Link to comment
Share on other sites

I use the downloaded eSim just an fyi...
 
neFxELm.png
I'm also using eSIM. No idea why yours is like that. Seems like it hasn't actually downloaded the PRL or something.

Sent from my Pixel 4 XL using Tapatalk

  • Like 1
Link to comment
Share on other sites

14 hours ago, ingenium said:

I'm also using eSIM. No idea why yours is like that. Seems like it hasn't actually downloaded the PRL or something.

Sent from my Pixel 4 XL using Tapatalk
 

Lovely!

Link to comment
Share on other sites

It does. Not sure on roaming yet...
PRL isn't just for roaming. It's for native CDMA too. If you didn't have a valid PRL then you wouldn't be able to use CDMA. It basically says "these sites are native, these are roaming, try them in this order and prefer this group over this other group".

You can also try the #*#*72786*#*# dialer code. That will wipe CDMA provisioning and force it to run again. But like I said, as long as CDMA works, I wouldn't worry about it.

Sent from my Pixel 4 XL using Tapatalk

  • Like 1
Link to comment
Share on other sites

Seems like the Pixel 4 XL LOVES to hold on to B41. Makes me wonder if the Pixel 2 XL actually supported HPUE.

It seems like the performance of the Pixel 4 XL > Pixel 2 XL.

Faster speeds, never falls to 3G, better radio performance overall!

Link to comment
Share on other sites

1 hour ago, though said:

@ingenium

I went into Data Settings on my Pixel 4 XL and noticed that it says CA Enabled Off.

I turned it to on and rebooted the phone and it still says Off.

Is this proper behavior for this phone?

My P4 (non-XL) has always shown that. Doesn't seem to have any effect.

  • 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

  • Similar Content

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