Jump to content

Google Pixel 3 / Pixel 3 XL User Thread


Recommended Posts

17 hours ago, ingenium said:

There is an adb command that you can run, without root I think, that sets what radios are affected by airplane mode. I set mine to not disable Bluetooth. Get an adb shell and run:

settings put global airplane_mode_radios cell,wifi,wimax

You can leave out wifi if you don't want it affected by airplane mode. The default list is cell,bluetooth,wifi,nfc,wimax

Sent from my Pixel 3 XL using Tapatalk
 

Good tip.  I'll try it out.

BTW, yesterday after getting off Caltrain, my phone was back in 3G.  Since streaming seemed to work, I left it as is.  About 10 mins later, I noticed my phone roaming on TMobile LTE (B2 or B4, don't recall).  Then a little bit later, my phone went back to 3G.

I don't know if there's some upgrade happening in SF or if it's on the phone side.

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

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

I just successfully switched my Pixel 3 XL to use the eSIM on Sprint. Works out of the box now. Since I already had this phone on the line, I had to swap to another phone and then swap back with the e

In order to accomplish this, you need to be rooted and have Magisk Manager installed. In Magisk Manager, go to Downloads and search for VoEnabler. Install VoEnabler and reboot the phone. VoLTE should

Cough    >> https://s4gru.com/forums/topic/7833-the-s4gru-byod-sim-compatibility-chart/

Posted Images

12 minutes ago, mikejeep said:

 


Do I spy something interesting in the status bar.....

-Mike

 

 

Maybe... CHECK UR HANGOUTS MESSAGES! :D

 

  • Like 1
Link to post
Share on other sites


Do I spy something interesting in the status bar.....

-Mike
Indeed you do [emoji6]1928c1cd24fc48abc8a7a91a7c0397e8.jpg

Sent from my Pixel 3 XL using Tapatalk

  • Like 2
  • Haha 1
Link to post
Share on other sites
this should work on the essential phone to then, i would imagine (or maybe really any rooted phone?).

Very likely. I'm guessing that any phone that uses the new wifi calling infrastructure will be able to use it. The config is already there, it just needs forced on. 

 

 

Edit: what's interesting is that it allows VoLTE to be used on Airaves and Magic Boxes, which disables it on "supported" devices. I'm guessing that it also works outside of VoLTE enabled markets too. Albeit it probably doesn't have QOS in those cases, so quality may be an issue.

 

Sent from my Pixel 3 XL using Tapatalk

 

 

 

 

 

  • Like 1
Link to post
Share on other sites

In order to accomplish this, you need to be rooted and have Magisk Manager installed. In Magisk Manager, go to Downloads and search for VoEnabler. Install VoEnabler and reboot the phone. VoLTE should start working.

7118710021855960496.png

  • Like 5
Link to post
Share on other sites
this should work on the essential phone to then, i would imagine (or maybe really any rooted phone?).
Do you have an Essential that's rooted? If so, I'd be really curious to see the results and what NSG shows. On the Pixel we've confirmed that it's true VoLTE. Note the EUTRA session with QCI 1. That's the VoLTE call. The session with QCI 5 is the IMS session, and QCI 9 is the normal data session.a6d9f8350327581d4604d133a7d96612.jpg

Sent from my Pixel 3 XL using Tapatalk

  • Like 1
Link to post
Share on other sites

Longtime listener, first time caller (poster) situation here.

Been paying attention to this thread for VOLTE information regarding the Pixel 3. I'm in Indianapolis, IN and I believe we are one of the roll out markets for Sprint VOLTE. I haven't gotten yet but I see some above have in other areas. Just wondering if anyone has any additional insight? Rooting isn't my thing so doing some of the above steps aren't for me.

Side note and somewhat unrelated but since I have a captive audience here. Sprint's visual voicemail app sucks with the Pixel 3. Literally can't get it to work. What do ya'll use? I'm sure Google Voice is the preferred method but I thought I'd check.

Link to post
Share on other sites



Longtime listener, first time caller (poster) situation here.
Been paying attention to this thread for VOLTE information regarding the Pixel 3. I'm in Indianapolis, IN and I believe we are one of the roll out markets for Sprint VOLTE. I haven't gotten yet but I see some above have in other areas. Just wondering if anyone has any additional insight? Rooting isn't my thing so doing some of the above steps aren't for me.
Side note and somewhat unrelated but since I have a captive audience here. Sprint's visual voicemail app sucks with the Pixel 3. Literally can't get it to work. What do ya'll use? I'm sure Google Voice is the preferred method but I thought I'd check.


If you don't want to root, you can't get VoLTE for now. The phone supports it, but we're just waiting on Sprint/Google to flip the switch. No idea when that might be. Could be next month, could be 6+ months from now.

I used to use Google Voice, but wifi calling on the Pixel 3 breaks conditional call forwarding. This forced me back to Sprint voicemail. So far I haven't had any issues with the Sprint Visual Voicemail app, but then again I rarely get voicemails.

Sent from my Pixel 3 XL using Tapatalk

  • Like 2
Link to post
Share on other sites
21 minutes ago, ingenium said:


If you don't want to root, you can't get VoLTE for now. The phone supports it, but we're just waiting on Sprint/Google to flip the switch. No idea when that might be. Could be next month, could be 6+ months from now.

I used to use Google Voice, but wifi calling on the Pixel 3 breaks conditional call forwarding. This forced me back to Sprint voicemail. So far I haven't had any issues with the Sprint Visual Voicemail app, but then again I rarely get voicemails.

Sent from my Pixel 3 XL using Tapatalk
 

 

Thank you for the reply! This is very helpful information. I really appreciate it. Lets hope for the closer to next month as opposed to 6+ months on the switch flip. 

Edited by acebel
Messed up formatting.
Link to post
Share on other sites
Speaking of which.  I used to be able to use data for SMS, but that ability has been removed recently.  Anyone else observe that?
Data has not been used for SMS since the Pixel 1, which uses IMS. The 2 and 3 both have constant SRLTE and use 1x for SMS instead.

If wifi calling is enabled and set to preferred on the 3, it will use that for SMS over 1x (though MMS still needs LTE or CDMA). Likewise, if you force VoLTE on the 3, I THINK it uses IMS for SMS instead of 1x (it should), but I haven't been able to confirm that yet.

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites
VOLTE is working on Pixel 3 XL in So-Cal right now. phone is not rootedab4db89004d6ca40c500872c735b581f.jpg

Sent from my Pixel 3 XL using Tapatalk


Does the enhanced 4G option show up for you in settings?3ad620361a9052de76b0deea09c23f48.jpg

Sent from my Pixel 3 XL using Tapatalk

  • Like 1
Link to post
Share on other sites
Does the enhanced 4G option show up for you in settings?3ad620361a9052de76b0deea09c23f48.jpg

Sent from my Pixel 3 XL using Tapatalk

It doesn't show up. I tried it multiple times though and it worked. Ran a few speed tests, watched a YouTube video.

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites
10 hours ago, maxx880 said:

VOLTE is working on Pixel 3 XL in So-Cal right now. phone is not rooted

Sent from my Pixel 3 XL using Tapatalk
 

Where in Socal were you located at the time of the call? I see you were on 800 1X

Link to post
Share on other sites
It doesn't show up. I tried it multiple times though and it worked. Ran a few speed tests, watched a YouTube video.

Sent from my Pixel 3 XL using Tapatalk

Open SCP and in the overflow menu go to Radio Info. Does it show VoLTE provisioned? Can you post a screenshot?fa10b13d4954f8e4a07e839e97a7202b.jpg

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites
Open SCP and in the overflow menu go to Radio Info. Does it show VoLTE provisioned? Can you post a screenshot?fa10b13d4954f8e4a07e839e97a7202b.jpg

Sent from my Pixel 3 XL using Tapatalk

Those are not able to be toggled but it is working. Just tested again.40e52d522e655b6252732cdc84d20c35.jpg

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites
Those are not able to be toggled but it is working. Just tested again.40e52d522e655b6252732cdc84d20c35.jpg

Sent from my Pixel 3 XL using Tapatalk

Interesting. I'm not sure how else to verify what it's using other than with root. It is odd that they're actually disabled there. I wonder if there was just some kind of fluke and it accidentally got toggled, and if it would persist after a reboot.

You didn't do anything special trying to enable it? It just happened out of the blue?

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites
1 minute ago, ingenium said:

Interesting. I'm not sure how else to verify what it's using other than with root. It is odd that they're actually disabled there. I wonder if there was just some kind of fluke and it accidentally got toggled, and if it would persist after a reboot.

You didn't do anything special trying to enable it? It just happened out of the blue?

 

Fwiw, the essential has the volte toggle enabled but i cant remember if it always has.  maybe it always was since it had the ability to roam off wifi calling onto LTE (and back again)?

Link to post
Share on other sites
  • 3 weeks later...

So I read on Reddit that Pixel 3 directly from Google could be activated on Sprint with eSim? Has anyone done this? Is the feature available right now?

Link to post
Share on other sites
So I read on Reddit that Pixel 3 directly from Google could be activated on Sprint with eSim? Has anyone done this? Is the feature available right now?
Can you link to the thread? To my knowledge the only way to do it is indirectly via Fi. I don't believe Sprint will directly allow the use of the eSIM.

Sent from my Pixel 3 XL using Tapatalk

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

  • Posts

    • It kinda just blows my mind that it's been almost a year and a half since start of auction and there still isn't a band designation. Why spend almost a billion dollars (T-Mobile's $873 million plus Sprint's $114 million) if you can't even get around to working something like that out with the 3GPP? I pray there's something going on behind the scenes, but I'm not too hopeful seeing as the only other owner of the band is DISH, haha.    I'd be shocked if T-Mobile doesn't keep a strong mmWave presence in lower/mid-Manhattan and downtown Brooklyn with their 5G small-cell rollout. That's key use case. But I agree, it'll definitely be interesting to see what they do outside of that area. You gotta imagine that Verizon played a pretty big part in how the nodes were designed, and Verizon typically loads their small cells up with every mid/high-band tech they've got. So it shouldn't be a matter of if the nodes support the tech, just if T-Mobile deploys the radios. IMO, T-Mobile's mmWave strategy (for both macros and small cells) kinda comes down to if T-Mobile is open to exploring the possibility of mmWave-based Home Internet in NYC.   I really hope they do keep them. Even if they aren't immediately upgraded to 5G, they'd be a big benefit for the network in general. Plus, fiber is already run, permits are already signed, sites are already built. Hopefully the neutral-nature of the nodes makes conversion easy.  I haven't spotted any nodes broadcasting the keep PLMN, but I'm not all that surprised about that.   Agreed. There are one or two redditors (who shall not be named) who love to spread questionable info, especially when it comes to NYC. Every carrier has Manhattan blanketed with mmWave! You can get FIOS at any address! T-Mobile has mmWave on every site and it's fast! T-Mobile has the densest small-cell network! Every site has 5gb/s backhaul (or if it doesn't, it's "just about to be upgraded")! It's really weird. Subreddit used to be so much better before it blew up and a handful of great contributors left.
    • My best guess is that it's a combination of the correct equipment not being available to support all of T-Mobile's mmWave bands and n41 taking precedence over mmWave deployment nationwide. It'll be interesting to see whether T-Mobile decides to make mmWave a citywide thing like Verizon (that they'll aggregate with n41 for gigabit speeds in more places) or if they'll just deploy it in stadiums, airports, and convention centers.  When T-Mobile acquired Metro, they retained pretty much all of their DAS sites. If they retain all of Sprint's small cells, they'd have a small cell network easily rivaling Verizon and could have an extremely dense mmWave/LAA/CBRS footprint to compliment their already dense (in most places) macro network. Someone recently made a post about how T-Mobile's tests in C-band were interfering with a local satellite TV operator so it seems like T-Mobile definitely has some interest in getting C-band deployed sooner than later, even if they won't be able to use the spectrum just yet. But like you said, it'll probably be another year or so before we start seeing deployments of that. I completely missed that thread but reading over it, so many people are very confused about the mmWave situation in NYC and T-Mobile's network here as a whole. It's pretty sad how people completely disregarded OP immediately.
    • Interestingly enough, today I came across a site in Seattle where they did the same thing. Previously, Commscope FFHH-65B-R3 panels were live with quadband; now there's only 1900/2100/2500. My knee jerk reaction is that I don't like this deployment. It makes optimizing handoffs sloppy and complicated. I  shot an email to the Seattle network team asking what the logic is - let's see what they say. 
    • I remember that Textra could ask for a delivered notice. Not sure exactly how that works. Haven't used it in a long time though, Android Messages works fine for me plus get the benefit of RCS.
    • It'll definitely be interesting to see what they do, especially considering there's now a lot more money in the pipeline! Personally, I'm most excited to see what they'll be doing with the new 5G small cells - this should be an opportunity for them to get a super dense n41, LTE-LAA, mmWave, and maybe even CBRS (there is 80MHz of GAA available...) infill. Can't wait to see what they'll be doing with these. This also brings up the question of how they'll be addressing mmWave in the future - have they been holding off on upgrades due to their n41 rollout, or because they're waiting for these small cells to be available? Reminds me of how they paused their LTE-LAA macro rollout, but then began to equip their existing LTE oDAS nodes with LTE-LAA. I am curious about their plans for C-Band, but I'm kinda of the impression that it's a very low priority for them. I doubt we'll be seeing any C-Band rollout for at least another year or so, T-Mobile's spectrum isn't available for deployment until Dec 2023. All that said, their n41 rollout does leave them with a ton of capacity to work with. Makes me wonder if upgrades (besides spectrum reallocation) in NYC will be put on the backburner for a little while. Lots of non-NYC Sprint sites to convert, and I've even spotted some recent Greenfield rural buildout upstate (if you can believe that). On another note, very amusing to see the T-Mobile subreddit respond to that NYC mmWave speedtest the other day.
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...