Jump to content

Google Pixel 2 XL by LG Preview/User Thread


skid71

Recommended Posts

On 8/6/2018 at 6:21 PM, crazy_vag said:

Went to Carrier Settings for "Update PRL" and "Updated device config", and LTE is back on.

Gotta wonder why that's needed.

Normally that is done automatically as part of the OS upgrade process, very weird

Link to comment
Share on other sites

  • 2 weeks later...
On 8/6/2018 at 4:21 PM, crazy_vag said:

Went to Carrier Settings for "Update PRL" and "Updated device config", and LTE is back on.

Gotta wonder why that's needed.

Both my wife and I's Pixel 2 XL's will not connect to LTE roaming since updating to 9.0 Pie. Can I do a "Update device config" to see if that fixes it on Wifi? I am in non-Sprint for the next few days....

Link to comment
Share on other sites

18 hours ago, though said:

Both my wife and I's Pixel 2 XL's will not connect to LTE roaming since updating to 9.0 Pie. Can I do a "Update device config" to see if that fixes it on Wifi? I am in non-Sprint for the next few days....

Turn off LTE and WiFi and try it... won't hurt.  

Link to comment
Share on other sites

Just an update.... I was in full USCC territory for 4 days with 2 of these phones. Have been to the same area many times in the past without issue. This time, however, neither phone connected to any LTE roaming, none zip zero. Prior to this trip I would connect primarily on USCC with some AT&T here and there the entire time.

I tried rebooting, toggling airplane mode, changing the radio to "LTE Only", making sure Data roaming was enabled, power off/on, a zillion times.

Is this a 9.0 Pie issue? Sprint issue? How do I report this to the "correct" people?

Link to comment
Share on other sites

1 hour ago, though said:

Just an update.... I was in full USCC territory for 4 days with 2 of these phones. Have been to the same area many times in the past without issue. This time, however, neither phone connected to any LTE roaming, none zip zero. Prior to this trip I would connect primarily on USCC with some AT&T here and there the entire time.

I tried rebooting, toggling airplane mode, changing the radio to "LTE Only", making sure Data roaming was enabled, power off/on, a zillion times.

Is this a 9.0 Pie issue? Sprint issue? How do I report this to the "correct" people?

Did you try making a phone call? I hear somethings that works

Link to comment
Share on other sites

Started having very weird band changes in the past few weeks.  My phone will stick and hold on to ehprd for a long time.  Even when I get home to my magic box, it can take up to 30 mins to get a stable LTE signal.

  • Like 1
Link to comment
Share on other sites

2 hours ago, jefbal99 said:

Started having very weird band changes in the past few weeks.  My phone will stick and hold on to ehprd for a long time.  Even when I get home to my magic box, it can take up to 30 mins to get a stable LTE signal.

Yes been noticing this as well.

Link to comment
Share on other sites

1 hour ago, though said:

Yes been noticing this as well.

I'm thinking this is in relation to VoLTE coming with more strict signal strength hand offs...

 

Link to comment
Share on other sites

6 hours ago, jefbal99 said:

I'm thinking this is in relation to VoLTE coming with more strict signal strength hand offs...

 

and/or a possible transition to T-Mobile roaming in the market????

Link to comment
Share on other sites

I am seeing similar behavior where I am onLTE then on eHRPD and down to 1x and back to eHRPD etc. Only happening since the 9.0 update but as mentioned it also somewhat coincides with the soft launch of VoLTE in Chicagoland.  I have done all the carrier updates with no luck but have not full reset yet.  Has anyone found a permanent solution to this?

Link to comment
Share on other sites

34 minutes ago, wobbypetty said:

I am seeing similar behavior where I am onLTE then on eHRPD and down to 1x and back to eHRPD etc. Only happening since the 9.0 update but as mentioned it also somewhat coincides with the soft launch of VoLTE in Chicagoland.  I have done all the carrier updates with no luck but have not full reset yet.  Has anyone found a permanent solution to this?

I did a factory data reset one one of my Pixel 2 XL's. Made no difference...

Link to comment
Share on other sites

16 hours ago, wobbypetty said:

I am seeing similar behavior where I am onLTE then on eHRPD and down to 1x and back to eHRPD etc. Only happening since the 9.0 update but as mentioned it also somewhat coincides with the soft launch of VoLTE in Chicagoland.  I have done all the carrier updates with no luck but have not full reset yet.  Has anyone found a permanent solution to this?

I did every beta of 9 and had it on release day, this behavior was not occurring.  I'm certain it has to do with VoLTE and sharper handoff metrics.

Link to comment
Share on other sites

12 minutes ago, jefbal99 said:

I did every beta of 9 and had it on release day, this behavior was not occurring.  I'm certain it has to do with VoLTE and sharper handoff metrics.

Yeah that makes very good sense.  So if you dont mind explaining to me what the ultimate fix will be and what they are currently tweaking?  Sounds like they are prepping for the quickest handoff so that the phone is losing little to zero voice packets I just dont know how they accomplish that technically and why it is affecting our service so severely right now. 

Link to comment
Share on other sites

28 minutes ago, wobbypetty said:

Yeah that makes very good sense.  So if you dont mind explaining to me what the ultimate fix will be and what they are currently tweaking?  Sounds like they are prepping for the quickest handoff so that the phone is losing little to zero voice packets I just dont know how they accomplish that technically and why it is affecting our service so severely right now. 

I honestly don't know.  My assumption is that Sprint is forcing an LTE->eHRPD cut off at a lesser signal strength than previous to ensure QOS when on VoLTE.  This ensures that a VoLTE session is stable in a call.

The fix is network densification...

  • Love 1
Link to comment
Share on other sites

I wonder if they can broadcast different disconnect thresholds for different devices. I guess it comes down to whether LTE signaling is broadcast/multicast or unicast.

The Pixel 2 for example always maintains a 1x connection (SRLTE) with Sprint, so if LTE is too weak for a VoLTE call, then Sprint can just send it via 1x and pretend the phone isn't on LTE.

With a Verizon SIM, my phone often will maintain SRLTE as well, at least for a little while before going LTE only. So I expect Sprint would keep SRLTE active all the time until they're confident in their network density.

If they can't have different disconnect thresholds for different devices, then yeah we might start seeing drops to CDMA more frequently unfortunately.

Sent from my Pixel 2 XL using Tapatalk

Link to comment
Share on other sites

  • 1 month later...
The October patch for (Pie) has been pushed out today. Please post if you are able to successfully roam after you run the patch on your Pixel 2 and 2 XL.
There is also a "Carrier Services" app update available in the Play Store.

Not sure if it's possible that a fix could be in there.

Sent from my Pixel 2 using Tapatalk

  • Like 1
Link to comment
Share on other sites

2 hours ago, jefbal99 said:

I got the carrier services update a few days ago, but still living on the Sept Security patch.  Haven't gotten the Oct patch yet

Go to settings, system, advanced, system update, check for update

Link to comment
Share on other sites

3 minutes ago, though said:

Go to settings, system, advanced, system update, check for update

oh i have multiple times, just haven't gotten to me in the availability yet.

Link to comment
Share on other sites

oh i have multiple times, just haven't gotten to me in the availability yet.
Did you ever opt in for the beta of pie? If you don't leave the beta then you won't receive the update.

Sent from my Pixel 2 XL using Tapatalk

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

    • Today I was driving over in Bothell/Kenmore area. I noticed the site which used to host Sprint eNB 745953 (where Waynita Way NE turns into 100th Ave NE) before it was fully decommissioned last year is now hosting all new T-Mobile gear. The gear isn't live yet but is fully installed. My guess is they plan to decommission the T-Mobile B2/B66 (enB 84647) only site a few blocks up the hill. This is a great move because decommissioning that old site would reduce interference with eNB 84740/175124. At the same time, the new location should notably improve coverage in the geographically shielded area along Waynita/100th.  The weird thing is I can't find a permit for this anywhere!
    • Mint and Ultra: Welcome to the T-Mobile Family! https://www.t-mobile.com/news/business/t-mobile-closes-acquisition-mint-and-ultra-mobile
    • https://www.t-mobile.com/2023-annual-report Most items s4gru members will be aware of, but an interesting read.
    • I've now seen 100 MHz n77 from SoftBank and 100 MHz n78 from NTT. NTT seems to be a bit better south of Osaka, though in some cases it drops down to B19 LTE as some areas around here are pretty rural. SoftBank has n77 around, but it's flakey enough that I switched eSIMs earlier this morning.
    • I'm currently typing this from a bullet train headed from Tokyo to Osaka. Using a roaming eSIM rather than T-Mobile as it's a lot cheaper, but I'll start with T-Mobile's roaming experience. Since I have a business line, I can't add data packs online, so I'm just using the 256 kbps baseline service you get by default. That service runs on Softank 4G. SoftBank has a well-built-out LTE network though, with plenty of B41, falling back to B1/3/8 as needed. 5G roaming from T-Mobile doesn't appear to exist though. I've seen 20+10 MHz B41 when I've looked, generally speaking. WiFi calling works well, and voice calls over LTE work fine too (I forgot to turn WiFi back on after doing some testing, so I expect my bill to be a dollar more next month). I want to say I even got HD voice over the cell network for the VoLTE call I did. I have a bunch of eSIMs and a couple of physical SIMs to try out. I've gotten the eSIMs up and running, but last I checked the physical SIM wasn't working even after activation so I'll run through eSIMs for the moment and update this thread with pSIM info and details on not-Tokyo in the coming days. First off, there's US Mobile's complimentary East Asia eSIM (5GB) that I grabbed before my unlimited plan Stateside expired. That SIM uses SIM Club, routing through Singapore, running on SoftBank LTE and 5G. I've seen 40 MHz n77, as well as 10x10 n28, and have seen download speeds in excess of 200 Mbps with uploads of more than 50 Mbps, though typical speeds are slower. Routing is via Equinix/Packet.net. 5G coverage is rather spotty, but LTE is plenty fast enough; either my phone doesn't want to use the 5G band combos that have more coverage or 5G coverage is just spottier here than in the US (at least on T-Mibile). Latency is as low as 95ms to sites in Singapore (usually closer to 120ms), which is pretty great considering the 3300 mi between Tokyo and Singapore. Next there's Ubigi. It also routes through Singapore via Transatel (despite being owned by NTT), and sites on top of NTT docomo's network. I didn't see NTT 5G in Tokyo when I tested it, but since then I've seen 10x10 n28, and have seen B1/B3/B19 on the LTE side. So far it's not the fastest thing out there, but I'm guessing coverage will be a little better...or maybe not. This was $17 for 10GB. Latency is a bit higher to Singapore, but still under 150ms it seems. Then there's Airalo, which was the cheapest when I bought it at $9 for 10GB. It also routes through Singapore (on Singtel), but on my S24 I have my pick of KDDI (au) or SoftBank. KDDI has extensive B41 coverage and I've seen 20+20 with UL CA. While waiting for the train at HND Terminal 3 (Keikyu line) I hit 250+ Mbps down and 10+ Mbps up...over LTE...with pretty respectable latency numbers (not much above 100ms). This is in adition to supporting SoftBank, also on LTE (my S24 defaulted to KDDI, while my wife's Pixel 8 defaulted to SoftBank and didn't seem to want to connect to KDDI). Of the various carriers mentioned, I'd say this was the best pick, though prices have bumped back up to $18 for the 10GB plan...but it's probably still what I'd pick if I had to pick just one carrier. Then there's Saily, which uses Truphone out of Hong Kong. I haven't used this as much, as I only grabbed 3GB for $7. It runs on NTT but doesn't seem to have 5G access and doesn't seem to have as good speeds. Yes, Hong Kong is way closer to Japan, but latency didn't seem to be any better, at ~150ms. In all cases, I've had reception even in train tunnels and even at high speed on the bullet train, on all three carriers I've tried (I don't think I'll be able to play with a Rakuten SIM, which is rather disappointing). There have been cases where service has degraded, but it looks like you'd have reasonable cell service no matter which of the big three carriers you picked...and since T-Mobile roams on one of them, that's good enough if you're content to buy day passes.
  • Recently Browsing

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