Jump to content

Google Pixel 3 / Pixel 3 XL User Thread


Recommended 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 eSIM. Everything works.

Super convenient. No more having to order the correct SIM from Sprint, and I can now swap between Sprint and another carrier easily (traveling internationally, or even using another domestic carrier).

Sent from my Pixel 3 XL using Tapatalk

  • Like 6
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

On 4/20/2019 at 11:28 AM, ingenium said:

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 eSIM. Everything works.

Super convenient. No more having to order the correct SIM from Sprint, and I can now swap between Sprint and another carrier easily (traveling internationally, or even using another domestic carrier).

Sent from my Pixel 3 XL using Tapatalk
 

Well, presumably I'll activate my Pixel 4 on eSIM, so won't need to worry about ordering a new SIM each year like I have been for the last 4 years.

When traveling internationally, the convenience and price of Sprint's roaming plan is really hard to beat, so I don't see myself changing plans when traveling.  

Link to post
Share on other sites
  • 2 weeks later...
On 4/16/2019 at 7:28 PM, ingenium said:

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
 

@lilotimz  mentioned that in Reddit. I don't know exactly.

Link to post
Share on other sites
@lilotimz  mentioned that in Reddit. I don't know exactly.
Yeah, I ended up figuring it out. I'm the one who showed lilotimz [emoji6]

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites
4 minutes ago, ingenium said:

Yeah, I ended up figuring it out. I'm the one who showed lilotimz emoji6.png

Sent from my Pixel 3 XL using Tapatalk
 

Since you have Pixel 3, how is the eSIM activation process? Is it complicated?

Link to post
Share on other sites
5 minutes ago, dnwk said:

Since you have Pixel 3, how is the eSIM activation process? Is it complicated?

Nope. It's really easy, especially if you don't already have the Pixel 3 on your line. You just go to Settings and search for Carriers (or go to Settings, Network & internet, Mobile network, Advanced, Carrier). Tap Add Carrier, and then select Sprint and login to your account. They'll text you a one time authentication code to login, so don't turn off your old phone first. And that's pretty much it.

If the Pixel 3 is already on your line, you'll have to swap it off first to an unused phone. There's no way to switch directly from a physical SIM to an eSIM without having an intermediate device.

  • Like 1
Link to post
Share on other sites
Just now, ingenium said:

Nope. It's really easy, especially if you don't already have the Pixel 3 on your line. You just go to Settings and search for Carriers (or go to Settings, Network & internet, Mobile network, Advanced, Carrier). Tap Add Carrier, and then select Sprint and login to your account. They'll text you a one time authentication code to login, so don't turn off your old phone first. And that's pretty much it.

If the Pixel 3 is already on your line, you'll have to swap it off first to an unused phone. There's no way to switch directly from a physical SIM to an eSIM without having an intermediate device.

Good information. Thanks. I am hoping Android Q will bring eSIM / Physical SIM dual standby.

Link to post
Share on other sites

So I know this isn't necessarily the place for this question but I'll ask anyway since Sprint support has been no help at all. I can't get Sprint Visual Voicemail (VMM) to work on my unrooted, stock Pixel 3 (not 3a) that I bought in November. It worked until about mid-December then stopped. I can download the app however when someone leaves me a voicemail it just doesn't show up...even after yesterday's update. No notifications, not in the app, no nothing. I know I have a voicemail because I can still dial into voicemail from the phone and hear it.

I've uninstalled and reinstalled the app 100 times and even factory reset the phone once. No change. I do get these notification when I open VMM. Anyone have any advice? I'm hoping there will be more answers out there since Sprint is carrying the Pixel 3 now. I just want visual voicemail like it is 2015.

 

PS I know Google Voice is an option...I just don't really want to do it.

Screenshot_20190507-073757.png

Screenshot_20190507-073930.png

Link to post
Share on other sites
So I know this isn't necessarily the place for this question but I'll ask anyway since Sprint support has been no help at all. I can't get Sprint Visual Voicemail (VMM) to work on my unrooted, stock Pixel 3 (not 3a) that I bought in November. It worked until about mid-December then stopped. I can download the app however when someone leaves me a voicemail it just doesn't show up...even after yesterday's update. No notifications, not in the app, no nothing. I know I have a voicemail because I can still dial into voicemail from the phone and hear it.
I've uninstalled and reinstalled the app 100 times and even factory reset the phone once. No change. I do get these notification when I open VMM. Anyone have any advice? I'm hoping there will be more answers out there since Sprint is carrying the Pixel 3 now. I just want visual voicemail like it is 2015.
 
PS I know Google Voice is an option...I just don't really want to do it.
Screenshot_20190507-073757.thumb.png.ed6101daafa0404414cda80e96cd6c07.png
Screenshot_20190507-073930.thumb.png.d42a898b8a5c0fe0fb9c158db36a0a2b.png
That's really weird. I haven't had any issues like that with the Sprint VMM app, other than it taking about 6+ hours to notify me of a voicemail. And when I mark them as read about half the time it won't clear the persistent notification and I have to force stop the app.

Have you called Sprint about it? Now that they sell the Pixel you should be able to get support?

Sent from my Pixel 3 XL using Tapatalk

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

That's really weird. I haven't had any issues like that with the Sprint VMM app, other than it taking about 6+ hours to notify me of a voicemail. And when I mark them as read about half the time it won't clear the persistent notification and I have to force stop the app.

Have you called Sprint about it? Now that they sell the Pixel you should be able to get support?

Sent from my Pixel 3 XL using Tapatalk
 

Thanks for the response, ingenium. I've contacted them via visualvoicemail@sprint.com and at least got a response there...they said to wait for the update that happened yesterday. It didn't help. General Sprint support has been less than helpful. Maybe I'm just not being patient enough for the voicemail to show up...I'll try waiting 6 hours! I just wish they'd let us use the default voicemail in the phone app. I'm tired of calling my voicemail after missed calls like a caveman. I have a feeling the root of the issue is the app is unable to verify my account. 

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

Sometime in the last month or so, I noticed that while I do get the Wi-Fi Calling icon showing in SignalCheck Pro, all my calls still go over the mobile 1x network instead of over Wi-Fi.  This is on my Pixel 3 XL with latest updates.  Anyone else notice that?

Link to post
Share on other sites
Sometime in the last month or so, I noticed that while I do get the Wi-Fi Calling icon showing in SignalCheck Pro, all my calls still go over the mobile 1x network instead of over Wi-Fi.  This is on my Pixel 3 XL with latest updates.  Anyone else notice that?
It depends on your signal leve,l if you have it set to mobile preferred. Change it to wifi preferred and it will always use wifi calling when available.

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites

Even with WiFi preferred, even when signal check pro showing WiFi calling, even when LTE/1x signal at -115db and WiFi of 70db, my Pixel 3 XL won't pick WI-FI for calls.

 

It used to work about 4 months ago, but no more.

It stopped working around the time when the phone started holding onto 3G instead of going to LTE.

Link to post
Share on other sites

Are there any other ways to troubleshoot Wi-Fi calling other than contact Sprint Support where they'll likely just blame Google?  Seems like I'm not able to remove Wi-Fi calling from my account either with contact support.

Link to post
Share on other sites
17 minutes ago, crazy_vag said:

Are there any other ways to troubleshoot Wi-Fi calling other than contact Sprint Support where they'll likely just blame Google?  Seems like I'm not able to remove Wi-Fi calling from my account either with contact support.

Have you tried using it on Airplane mode? Service is pretty bad in my work building due to cement walls and sometimes when calling it will use regular 1X and sometimes Wifi Calling. I have it set to Mobile Preferred but notice improvement in audio call when on Wifi calling. Also, when other devices are both  on wifi calling the HD logo appears on the call and audio quality is great.

Link to post
Share on other sites
1 hour ago, nexuss4g said:

Have you tried using it on Airplane mode? Service is pretty bad in my work building due to cement walls and sometimes when calling it will use regular 1X and sometimes Wifi Calling. I have it set to Mobile Preferred but notice improvement in audio call when on Wifi calling. Also, when other devices are both  on wifi calling the HD logo appears on the call and audio quality is great.

  I'm not able to make calls when connected to WiFi only (Airplane mode on).   Whether I have Mobile Preferred or Wi-Fi Preferred doesn't matter.  

Can you actually make a calls while on Airplane Mode On with your Pixel 3?? 

Link to post
Share on other sites
Even with WiFi preferred, even when signal check pro showing WiFi calling, even when LTE/1x signal at -115db and WiFi of 70db, my Pixel 3 XL won't pick WI-FI for calls.
 
It used to work about 4 months ago, but no more.
It stopped working around the time when the phone started holding onto 3G instead of going to LTE.
With wifi preferred it should always use wifi calling. At least mine does. The only time when it didn't seem to use it was when I connected to WiFi that was using an LTE modem connected to a magic box. For some reason it didn't really like that combo.

If it's not working, then my guess is that something is blocking or interfering with the ipsec tunnel on your wifi. Or the wifi signal is too low or there are other problems with it. It's possible it won't use it if it determines that the connection isn't stable/good enough.

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites
27 minutes ago, crazy_vag said:

  I'm not able to make calls when connected to WiFi only (Airplane mode on).   Whether I have Mobile Preferred or Wi-Fi Preferred doesn't matter.  

Can you actually make a calls while on Airplane Mode On with your Pixel 3?? 

Yes, I am able to make calls while on airplane mode on my Pixel 3 XL

Link to post
Share on other sites
Anyone found any fixes for the 'stuck on 3G issue'?
Nothing besides doing an airplane toggle

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites

After playing around some more, I'm convinced that Wi-Fi Calling isn't provisioned correctly on my phone.  It doesn't work in Airplane Mode, it doesn't work on any WiFi network regardless of the strength.  SCP does show WiFi calling enabled, but even then calls go over 1x.  

What's more annoying is that I can't disable Wi-Fi calling service on my account without customer support for whatever reason.

Link to post
Share on other sites
After playing around some more, I'm convinced that Wi-Fi Calling isn't provisioned correctly on my phone.  It doesn't work in Airplane Mode, it doesn't work on any WiFi network regardless of the strength.  SCP does show WiFi calling enabled, but even then calls go over 1x.  
What's more annoying is that I can't disable Wi-Fi calling service on my account without customer support for whatever reason.
Wi-Fi Calling generally works well on my Pixel 3. It didn't work with airplane mode enabled for at least the first 4 months, but I just tested it a moment ago and it did work. An Android and/or carrier update at some point must have fixed that -- I hadn't tried it in awhile so I can't say when that happened.

-Mike
Link to post
Share on other sites
  • 5 weeks later...

I just got a Pixel 3 XL and couldn't activate RCS messaging, it would just stay stuck on setting up and verifying number. I activated it using eSim.

I found that there were people on Rogers having same issue. The fix is to goto Settings > Apps & Notifications >See All > Carrier Services. When you click disable it'll give you an option to restore to factory. RCS worked immediately.

Just in case anyone else runs into it.

  • Like 1
Link to post
Share on other sites
On 7/2/2019 at 12:12 PM, ericwalton said:

I just got a Pixel 3 XL and couldn't activate RCS messaging, it would just stay stuck on setting up and verifying number. I activated it using eSim.

I found that there were people on Rogers having same issue. The fix is to goto Settings > Apps & Notifications >See All > Carrier Services. When you click disable it'll give you an option to restore to factory. RCS worked immediately.

Just in case anyone else runs into it.

After you "disable" it, what's next?  Do you re-enable it or leave it disabled?  

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