Jump to content

Google Pixel 3 / Pixel 3 XL User Thread


Recommended Posts

I honestly forget already. If it doesn't give you the option to factory reset as soon as you disable, then it should when you re-enable. But yeah, the end result is that you need it enabled.

Link to post
Share on other sites
  • 1 month later...
  • 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

In random news, this morning, my Pixel 3 XL froze.  When it rebooted, it said "No SIM".  Rebooted and reinserted SIM, but no go.  Tried a co-worker's SIM and it was recognized immediately, so chatted with Sprint about activating eSIM since was getting errors in the Pixel UI.  Chat referred me to call, and operator tried a few times, but got errors on their end, so told me to go to a store.

No line, but learned Sprint only does eSIM on Pixel phones purchased from Sprint.  They won't activate eSIM Pixel phones purchased from Google, so 5 mins later I was out the door with a replacement physical SIM.

 

Hasn't anyone successfully activated their Pixel 3 on eSIM with a phone purchased from Google?

Link to post
Share on other sites
Hasn't anyone successfully activated their Pixel 3 on eSIM with a phone purchased from Google?


I have Sprint eSIM on my Pixel 3 purchased from Google.. did it months ago. Works great.

-Mike
Link to post
Share on other sites

I had heard that to activate esim on a device that is currently activated with a physical sim that it was necessary to first activate some other device and then it was possible to reactivate on esim.

For whatever that's worth

Sent from my Pixel 2 using Tapatalk

Link to post
Share on other sites
In random news, this morning, my Pixel 3 XL froze.  When it rebooted, it said "No SIM".  Rebooted and reinserted SIM, but no go.  Tried a co-worker's SIM and it was recognized immediately, so chatted with Sprint about activating eSIM since was getting errors in the Pixel UI.  Chat referred me to call, and operator tried a few times, but got errors on their end, so told me to go to a store.
No line, but learned Sprint only does eSIM on Pixel phones purchased from Sprint.  They won't activate eSIM Pixel phones purchased from Google, so 5 mins later I was out the door with a replacement physical SIM.
 
Hasn't anyone successfully activated their Pixel 3 on eSIM with a phone purchased from Google?
The eSIM works on phones purchased from Google. I'm using it on mine. The issue is that you can't migrate directly from physical SIM to eSIM on the same phone. You have to first swap to a different/old device, remove the physical SIM from your 3, and then setup the eSIM on it (select add, then select Sprint). The phone will have you sign into your Sprint account and select which line you want to use, and that's basically it.

The issue I believe is because the IMEI is already in use and tied to the physical SIM, so it won't let you swap the IMEI to eSIM while in use. By swapping to a different device first, it frees up the IMEI to be linked to your eSIM.

Sent from my Pixel 3 XL using Tapatalk

  • Like 1
Link to post
Share on other sites
2 hours ago, ingenium said:

The eSIM works on phones purchased from Google. I'm using it on mine. The issue is that you can't migrate directly from physical SIM to eSIM on the same phone. You have to first swap to a different/old device, remove the physical SIM from your 3, and then setup the eSIM on it (select add, then select Sprint). The phone will have you sign into your Sprint account and select which line you want to use, and that's basically it.

The issue I believe is because the IMEI is already in use and tied to the physical SIM, so it won't let you swap the IMEI to eSIM while in use. By swapping to a different device first, it frees up the IMEI to be linked to your eSIM.

Sent from my Pixel 3 XL using Tapatalk
 

Makes sense.

All that code to check IMEI to prevent you from upgrading to same phone is now coming to bite us.

Sounds like best to make the eSIM jump when getting the Pixel 4.

Hopefully eSIM supported from day 1.

Link to post
Share on other sites
Makes sense.
All that code to check IMEI to prevent you from upgrading to same phone is now coming to bite us.
Sounds like best to make the eSIM jump when getting the Pixel 4.
Hopefully eSIM supported from day 1.
It should be supported day 1. If you have an old phone you can swap to, it's a 5 minute process to switch to eSIM. Definitely worth it if you ever use a SIM from another carrier.

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites

Went down the VoEnabler rabbit hole and found that the module is no longer available in the Magisk Official Repo and therefore not available in the Magisk app.

So, found the original git, downloaded and repacked it and manually installed it and it seems to be working on Android 9 with eSIM.

Here's a link to the repacked module. Copy do device. and manually install from the Magisk App, reboot. Not responsible for any damaged, errors, etc. by using this on your device.
https://drive.google.com/file/d/1Aai3avK96zqmwBoNTYGs5OhLnyMxKGn1/view?usp=sharing

Link to post
Share on other sites
On 9/16/2019 at 5:57 AM, mhammett said:

Does anyone have a Pixel 3 XL case recommendation that's more rugged than the Spigen Rugged Armor? Let's just say it's not rugged enough.

This is the one I have but is not rugged as the Spingen Rugged but it has sustained small drops with no damage at all. I have tempered glass as well.

 

https://www.caseologycases.com/collections/google-pixel-3-xl

Link to post
Share on other sites
Just noticed that VoLTE was enabled on my Pixel 3 XL.  Haven't used it yet, but my phone no longer needs to connect to  1x + LTE... It's now just LTE or Wi-Fi.  Life's Good! [emoji4]
Yup! It came with the Android 10 update. Glad to have it officially supported instead of requiring a hack.

The question is, does it continue to ignore the VoLTE flag on the eNB (ie, will it work on a Magic Box or Airave), unlike other VoLTE enabled devices? I've been out of the country since it came out, so haven't been able to test.

Sent from my Pixel 3 XL using Tapatalk

  • Like 1
Link to post
Share on other sites
On 9/21/2019 at 5:53 AM, ingenium said:

Yup! It came with the Android 10 update. Glad to have it officially supported instead of requiring a hack.

The question is, does it continue to ignore the VoLTE flag on the eNB (ie, will it work on a Magic Box or Airave), unlike other VoLTE enabled devices? I've been out of the country since it came out, so haven't been able to test.

Sent from my Pixel 3 XL using Tapatalk
 

No VoLTE on Magic Box Gold.... 

Link to post
Share on other sites
Still havent been able to update to Android 10 on my P3XL as it fails to install. [emoji20]
Are you rooted? That can prevent the OTA from applying.

If you aren't rooted, download the full factory image and flash it with adb. This will not apply though if you're currently rooted, and will also throw an error.

If you are rooted (or bootloader unlocked at least), get the factory image and remove "-w" from the one line in the .bat (Windows) or .sh (Linux/Mac) file, so that it won't wipe your data. Leaving -w wipes the device, removing it preserves data. This is guaranteed to work.

Sent from my Pixel 3 XL using Tapatalk

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

Are you rooted? That can prevent the OTA from applying.

If you aren't rooted, download the full factory image and flash it with adb. This will not apply though if you're currently rooted, and will also throw an error.

If you are rooted (or bootloader unlocked at least), get the factory image and remove "-w" from the one line in the .bat (Windows) or .sh (Linux/Mac) file, so that it won't wipe your data. Leaving -w wipes the device, removing it preserves data. This is guaranteed to work.

Sent from my Pixel 3 XL using Tapatalk
 

Nope not rooted. Completely stock. I will have to download the factory image but I dont want to delete all my stuff from the phone. I believe everything deletes if I flash the factory image from the settings right?

Link to post
Share on other sites
Nope not rooted. Completely stock. I will have to download the factory image but I dont want to delete all my stuff from the phone. I believe everything deletes if I flash the factory image from the settings right?
No. See my comment above. If you remove -w from the script and save it, it won't wipe data.

Sent from my Pixel 3 XL using Tapatalk

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

Still havent been able to update to Android 10 on my P3XL as it fails to install. :(

I've had trouble updating Chrome, but a few weeks later, Google seemed to have fixed the installer.  There's the lazy option of waiting a few more weeks in hope of installer getting fixed.

Or 2 more weeks until October security update - which might fix it.

Or 4 more weeks until Pixel 4. :D:D:D

Link to post
Share on other sites

My old Pixel 3 XL had a broken USB-C Connector.  It would only charge if cable is inserted in one direction - no longer reversible connector.  I've got it all setup, so with a new IMEI, should I be able to get eSIM activated on it?

Link to post
Share on other sites
8 hours ago, crazy_vag said:

My old Pixel 3 XL had a broken USB-C Connector.  It would only charge if cable is inserted in one direction - no longer reversible connector.  I've got it all setup, so with a new IMEI, should I be able to get eSIM activated on it?

The answer is still a "no" on eSIM if you bought your phone from Google. After many attemps at the store, it just would not work, so back to physical SIM. 😖

Link to post
Share on other sites
4 hours ago, crazy_vag said:

The answer is still a "no" on eSIM if you bought your phone from Google. After many attemps at the store, it just would not work, so back to physical SIM. 😖

 

12 hours ago, crazy_vag said:

My old Pixel 3 XL had a broken USB-C Connector.  It would only charge if cable is inserted in one direction - no longer reversible connector.  I've got it all setup, so with a new IMEI, should I be able to get eSIM activated on it?

 

I just activated my girlfriends Google purchased P3 with e-sim right from the device itself running android 10. Sprint was an option through "download my sim" setting and auto-activated. 

Link to post
Share on other sites
2 hours ago, nexgencpu said:

 

 

I just activated my girlfriends Google purchased P3 with e-sim right from the device itself running android 10. Sprint was an option through "download my sim" setting and auto-activated. 

I see that same option, but continually get an error upon selecting it and confirming a sprint dialog.  Then I'm told to call a number for help.  Starting to suspect it's something about my plan / account that's choking it.

Link to post
Share on other sites
I see that same option, but continually get an error upon selecting it and confirming a sprint dialog.  Then I'm told to call a number for help.  Starting to suspect it's something about my plan / account that's choking it.
Could be. I have a Google purchased Pixel 3 XL and it worked fine. You get to the step where you login to your Sprint account and select the number right?

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites
6 hours ago, ingenium said:

Could be. I have a Google purchased Pixel 3 XL and it worked fine. You get to the step where you login to your Sprint account and select the number right?

Sent from my Pixel 3 XL using Tapatalk
 

I never get to that step. Simply get an error.

I'll take a video of doing that when pixel 4 comes out.

Link to post
Share on other sites
I never get to that step. Simply get an error.
I'll take a video of doing that when pixel 4 comes out.
Wait you never even get to login to your Sprint account? I don't think that's Sprint related then. This might be a silly question, but you're on wifi when you try to add the eSIM right?

Do you have a regular Sprint account? Or is it through an MVNO?

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