Jump to content

Recommended Posts

[mention=21091]ingenium[/mention]
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?
ZFUf6kd.png
I just checked and mine is also off. I never noticed that before. Doesn't seem to have an effect, since NSG confirms that CA works.

Sent from my Pixel 4 XL using Tapatalk

Link to post
Share on other sites
  • Replies 180
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Got my Pixel 4 XL yesterday (Google Store). Activated instantly on Sprint via the eSim. WiFi Calling and VOLTE are functional. Sent from my Pixel 4 XL using Tapatalk

Early testing I'm seeing better dbms from SCP on the p4xl compared to my s10+ but better speeds on S10+. I'll do more testing and screen shots to come. Sent from my SM-G975U using Tapatalk

I pre-ordered from Google within the first few minutes it was on their site. Used my $50 credit from my P3 purchase, earned another $100 credit with this purchase. Should arrive by the end of the mont

Posted Images

10 hours ago, ingenium said:

I just checked and mine is also off. I never noticed that before. Doesn't seem to have an effect, since NSG confirms that CA works.

Sent from my Pixel 4 XL using Tapatalk
 

So probably wouldn't effect the ability to do FDD-TDD??

Link to post
Share on other sites
So probably wouldn't effect the ability to do FDD-TDD??
It does not affect it.

Sent from my Pixel 4 XL using Tapatalk

  • Like 1
Link to post
Share on other sites
  • 4 months later...
  • 3 weeks later...
  • 5 months later...

After reaching "peak VoLTE", I've noticed my phone not getting VoLTE in places it used to.  This began sometime about a month ago in San Francisco, so many calls go over 1x.

Has anyone noticed this too?

Link to post
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

    • By Handyman
      Just installed the 8.1 update on my Pixel.  Still no Sprint Wi-Fi / LTE calling
       
      But ... I did get the mandatory Google Search button added to my launcher.
       
    • By Nrbelex
      The rumor mill has fully geared up, so it seems time for a thread in which the potential HTC-made 2016 Nexus phones can be discussed.
       
      Rumors suggest two phones: a 5" device codenamed Sailfish, and a larger device codenamed Marlin. Both are thought to be produced by HTC. [There's also a report that Google is making its own phone, without an OEM partner--along the lines of a Pixel phone--but that report has been largely discounted.]
       
      Android Police has claimed it knows with 8/10 certainty some specs of the smaller device--Sailfish:
      Manufactured by HTC 5" 1080p display (~440PPI) Quad-core 2.0GHz 64-bit processor (model unknown) 4GB RAM 2770mAh battery 32GB storage (unknown if multiple models will be available, or even if this is the base storage level) 12MP rear camera, 8MP front Rear-mounted fingerprint scanner USB-C port (bottom) Bottom-firing speaker or speakers (unknown if dual) Top-mounted headphone jack Bluetooth 4.2 Any thoughts on these devices? The last several Nexus devices have been Sprint compatible; is there any reason to think these won't be? Any hints in regulatory filings? How is HTC's radio performance, generally? Will Sprint sell them directly, and even if they do, will it still be preferable to buy directly from Google?
    • By jefbal99
      Only specs I've really seen leaked are 5.7" screen and based on the unannounced "Mate 8" model.
       
      From http://www.breathecast.com/articles/nexus-2015-rumors-news-leaked-video-reveals-specs-of-purported-2015-huawei-nexus-video-30407/
       
       
       
       
       
       
       

      The Mate 7 had a 4100+mah battery, speculation is that this could have the same or bigger.
       
      Anything passed through the FCC for a US and/or Sprint version that covers the Spark bands?  I'm in the market for a new phone this fall and will be going off contract, buying a Nexus.
    • By nexgencpu
      Hopefully we can finally start seeing some user feedback. So far so good! it is without a doubt the best device ive owned!!!
    • By topdownat4
      Had not seen a thread for this yet, 
      I see some definite consumer advantages with Sprint's Network combined with TMob and Wi-fi.
      I have had many Nexus devices and I love my Nexus 6, although it is a bit big.
      The price is good for the service. ($20 / unl talk/txt, $10/gb)
       
      I hope the technical aspects work as they propose. I am a Google Voice Number user and love the "Any device" call capability and use it on my Tablet, Chromebook and phone. I rarely actually answer my Phone at the house. Answer the tablet or Chromebook.....
       
      I love Sprint's network, the upgrades they are putting forth and this Site, but if Project Fi works as advertised, it might lure me to sign on.....
       
      What are everyone's thoughts?
       
       
       
       
  • Posts

    • Definitely agree. I'd honestly be satisfied if T-Mobile announced that they were deploying mmWave in targeted locations like airports and stadiums nationwide. Right now it still seems like they've stopped working altogether on expanding mmWave coverage with the exception of installing it at Raymond James Stadium and Tampa International Airport for the Super Bowl. Maybe they're holding out until new antennas and phones come out that support 24GHz and 47GHz spectrum since that's where the majority of their mmWave spectrum is here in NYC. Though there is nothing stopping them from deploying the 400MHz of n260 that they own here. I ran about 5 tests at this site but this was the only test with any packet loss. All with around 70ms pings. Even my mmWave speed tests in Brooklyn show 70ms pings. I've kinda been using it as a gauge for what 5G band I'm connected to. n41 is always in the teens, n71 is typically in the low to mid 20's, and n261 is around 70ms. It's honestly a mystery. Especially when we've seen Verizon mmWave with single-digit pings.
    • Dang, not too shabby! I'm sure this has been said before, but in some ways I kinda feel like T-Mobile has abandoned their mmWave network in NYC. I haven't seen any recent buildout, they're still stuck on 2x 50MHz n261 carriers, and performance (when you can connect) generally isn't much to speak of. On one hand, I don't really blame them when they have so much n41 deployment left to do. But it's also disappointing to hear them preach about the "layer cake" when their mmWave performance (at least in NYC) is a bit underwhelming. Here's hoping they'll get back on it when we start seeing these new 5G oDAS nodes roll out. I wonder what the reason is for the abnormally high pings you're seeing on n261. Didn't even notice that from my last post - it's a bit brutal to see a 77ms ping on n261 NSA and 13ms ping on n41 NSA, from the same site. Is this a recent development? Also, you probably shouldn't be experiencing ~5% packet loss when you're LOS... On another note, that's an interesting setup. Haven't seen one with a single APXVAR18_43-C-NA20, and I don't believe I've seen that 8-port Ericsson (?) midband antenna before.
    • Got my fastest mmWave speeds ever from a "layer cake" site in Chelsea. It recently got n41 but my phone didn't connect to it at all given I was super close to the site and within line of sight. Speeds on LTE alone were about 190Mbps.  I've been noticing consistent ~70ms pings on mmWave citywide.
    • is VoNR a thing yet?  when connected to n71, if a call happens, the device drops over to band 71 LTE to make the call and then switches back to 5G n71.  If I use samsung band selector and lock the device to n71 and do a call, the phone does not switch away from 5G and continues to reflect n71 but i dont have a way to know if that is just the phone not knowing what to show since it is band locked.
    • I have not seen CA on either with TNX.  CA on Sprint B41 is reduced to 2X around here as well.  Where the "magic" happens is n41 NSA. So far, I have not seen very fast speeds out of n41 SA.
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...