Jump to content

Google Pixel 3 / Pixel 3 XL User Thread


Recommended Posts

You can just walk into a Sprint corporate store to grab a free SIM. They will do the activation on the spot for free if you're just swapping devices and want to wait.

-Mike

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

  • S4GRU changed the title to Google Pixel 3 / Pixel 3 XL User Thread
  • S4GRU pinned this topic
Apparently, the 10w wireless charging is a Google standard. If you wish to use Qi, you're limited to 5w. The Qi standard goes up to 15w.

Why, Google, why?


Seems like something Apple would do.
  • Like 1
Link to post
Share on other sites

I am looking for more observations on this.

I believe the restriction on the Google-approved wireless chargers for charging rapidly was instituted in a software update.

Out of the box, my 3 XL was "charging rapidly" from my old generic wireless charger. I installed the update and now it's "charging slowly". Can anyone else confirm?

Can I roll back my update?

Link to post
Share on other sites
9 hours ago, mhammett said:

I am looking for more observations on this.

I believe the restriction on the Google-approved wireless chargers for charging rapidly was instituted in a software update.

Out of the box, my 3 XL was "charging rapidly" from my old generic wireless charger. I installed the update and now it's "charging slowly". Can anyone else confirm?

Can I roll back my update?

Pretty sure the issue was that it was characterizing incompatible fast wireless charging as charging fast before the update. This is because Google uses a proprietary fast charging method instead of what Samsung and others use. With the update it's showing the correct charging.

  • Like 1
Link to post
Share on other sites
13 hours ago, Sanyo M1 said:

Pretty sure the issue was that it was characterizing incompatible fast wireless charging as charging fast before the update. This is because Google uses a proprietary fast charging method instead of what Samsung and others use. With the update it's showing the correct charging.

 

Was the problem in the messaging (calling it charging rapidly when it was really charging slowly) or was the problem in that Google forgot to enable the DRM in the release version?

The only real way to know is a screenshot of a battery management app before the update showing what the charge rate actually is when "charging rapidly".

Link to post
Share on other sites

Anyone else seeing issues with their Pixel 3 XL intermittently connecting to WiFi calling? Any insight on if the VOLTE feature will come to the phone?

Sent from my Pixel 3 XL using Tapatalk

Link to post
Share on other sites
Anyone else seeing issues with their Pixel 3 XL intermittently connecting to WiFi calling? Any insight on if the VOLTE feature will come to the phone?

Sent from my Pixel 3 XL using Tapatalk


Mine is set to mobile preferred, but connects to wifi calling fairly consistently where I do not have a solid mobile signal. It's one of my favorite features, works great. If you set to wifi preferred, it will almost always use wifi when available.

-Mike
  • Like 2
Link to post
Share on other sites
Mine is set to mobile preferred, but connects to wifi calling fairly consistently where I do not have a solid mobile signal. It's one of my favorite features, works great. If you set to wifi preferred, it will almost always use wifi when available.

-Mike
Does it drop the call when you move outside of wifi coverage? Or does it continue the call over LTE?

Sent from my Pixel 2 XL using Tapatalk

  • Like 1
Link to post
Share on other sites

So, this thread isn't very active... How is the radio on this bad boy?  The 3 XL will be delivered on Wednesday, :D.  Wish it had VoLTE out of the box, here's to hoping it will at least get it 🤞🤞🤞🤞🤞.

Link to post
Share on other sites
On 11/3/2018 at 6:04 AM, jreuschl said:

Does SMS and MMS work over Wi-Fi?

Sent from my SM-G892U using Tapatalk
 

YES!!! It used to be that only SMS would work, so you'd miss Group SMS and MMS until went back on cellular.  

 

I can confirm that both work AND both show up on the web https://messages.android.com/.

Link to post
Share on other sites
On 11/17/2018 at 4:33 PM, ingenium said:

Does it drop the call when you move outside of wifi coverage? Or does it continue the call over LTE?

Sent from my Pixel 2 XL using Tapatalk
 

I don't know since I don't have either when going into the elevator, and don't trust public Wi-Fi to test elsewhere.

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

YES!!! It used to be that only SMS would work, so you'd miss Group SMS and MMS until went back on cellular.  

 

I can confirm that both work AND both show up on the web https://messages.android.com/.

It DOES NOT work on wifi only, on the Pixel 2 XL, so this is interesting...

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

It DOES NOT work on wifi only, on the Pixel 2 XL, so this is interesting...

I'm not able to send or receive text messages on wifi on my Pixel 2 XL even if i toggle airplane mode.

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

YES!!! It used to be that only SMS would work, so you'd miss Group SMS and MMS until went back on cellular.  

 

I can confirm that both work AND both show up on the web https://messages.android.com/.

So does texting over wifi work on the Pixel 3?

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

Did you confirm that RCS is enabled?

Yes RCS works on Wifi only. And is only available at the moment for Sprint to Sprint users via the stock Google "Messages" app. RCS is 'rich communication system' and uses data/internet/wifi.

Totally different than SMS/MMS.

  • Like 1
Link to post
Share on other sites
14 hours ago, though said:

Yes RCS works on Wifi only. And is only available at the moment for Sprint to Sprint users via the stock Google "Messages" app. RCS is 'rich communication system' and uses data/internet/wifi.

Totally different than SMS/MMS.

Maybe I'm wrong, but I think RCS sends all messages via RCS pipe to Sprint where they continue either as SMS or RCS depending on the recipient. 

If you read the description of the setting carefully, it says it'll "use data when available"  - and not "use data when recipient has compatible service".

Anyway, I'm happy with this config since now I get all my texts (SMS+MMS) over WiFi and also on my computer.

Link to post
Share on other sites
Maybe I'm wrong, but I think RCS sends all messages via RCS pipe to Sprint where they continue either as SMS or RCS depending on the recipient. 
If you read the description of the setting carefully, it says it'll "use data when available"  - and not "use data when recipient has compatible service".
Anyway, I'm happy with this config since now I get all my texts (SMS+MMS) over WiFi and also on my computer.
It means that if data isn't available on your phone, it will send as SMS/MMS instead. Or if the recipient doesn't have data for some reason (such as on a phone call) and the message doesn't get delivered within a certain period of time, then the phone resends it as SMS/MMS. Sprint doesn't resend it as SMS from their end.

Sent from my Pixel 2 XL using Tapatalk

  • Like 1
Link to post
Share on other sites
On 11/23/2018 at 6:04 PM, ingenium said:

It means that if data isn't available on your phone, it will send as SMS/MMS instead. Or if the recipient doesn't have data for some reason (such as on a phone call) and the message doesn't get delivered within a certain period of time, then the phone resends it as SMS/MMS. Sprint doesn't resend it as SMS from their end.

Sent from my Pixel 2 XL using Tapatalk
 

I guess I haven't run into a case where SMS/MMS doesn't work over WiFi.  Are you saying that if I try to send SMS over WiFi while recipients phone is powered off, my phone will try to switch to 1xRTT and send message over cellular?  

Link to post
Share on other sites
I guess I haven't run into a case where SMS/MMS doesn't work over WiFi.  Are you saying that if I try to send SMS over WiFi while recipients phone is powered off, my phone will try to switch to 1xRTT and send message over cellular?  
No, I'm saying that in that case it won't send it as an RCS message, and instead will fall back to SMS/MMS.

Sent from my Pixel 2 XL using Tapatalk

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

    • I may have missed it, but what are the the benefits of moving over to TNX on a 5G device that would automatically have TNA (prefer the T-Mobile network). It doesn't seem like it would change the network experience all that much. My devices are all TNA, and on the T-Mobile network all the time except while near Sprint Keep sites. I'd prefer to keep the easy access to Sprint sites since Sprint have a bigger network than T-Mobile here.
    • Has anyone on eSIM switched to T-Mobile eSIM?
    • Unfortunately, I'm seeing the gaps in the customer experience for TNX and I'm wondering if I should just leave the "T-Mobile Unlimited Freedom Plan with Included Taxes/Fees" behind and bring everything over to a T-Mobile Plan/Account at a certain point for usability and management sake. iOS: The experience on iOS has been fine. When I upgraded my 3 iPhone 12 Pro's it was easy to update the E911 Address for Wi-Fi Calling right on the device. Quick and done. Google Pixel 5: The experience on a Google Pixel 5 on eSIM for Sprint was mediocre. I received conflicting information about whether the device was eligible for TNX. Chat said yes, so I ordered a SIM and installed it. The device threw an error and said to take it out. Chat then said that device wasn't eligible for TNX. Is this in fact the case? Has anyone here put a Google Pixel 5 on TNX? Samsung: The experience for two Samsung Galaxies on our account was actually terrible. For the S20+ 5G: I put in the TNX SIM and after I enabled Wi-Fi Calling, I wanted to update the E911 address on the device. Nope, the address update button in the device menu took me to the T-Mobile Login Screen. I contacted chat and they said I had to do it on the Sprint website. Ok, so I went to the Sprint Website and to Account Dashboard. I selected "Options" for the device, and selected the Update E911 Address link. I then got taken to an absolutely ancient portion of the Sprint website that hadn't been part of the recent redesign and I was able to update the address.... but the interface looked terrible and like it wouldn't actually work. I still can't update the E911 address on the device itself. Ridiculous. For the S21 5G, which was a device upgrade on that line from an absolutely ancient BlackBerry KEYone (Don't ask. They held on forever hoping keyboards would come back): After activating the device with the T-Mobile SIM Card that came with it, I went to activate Wi-Fi Calling on the device. I then went to update the E911 address on the device and the button took me to the same T-Mobile Login page as it did on the S20+. So I went to my Account Dashboard and it showed the S21 on the line and that it was on the T-Mobile network. It showed that Wi-Fi Calling was enabled under account services. I then went to Manage Device -> Options -> Update E911 Address for WiFi Calling, and the ancient content page loaded.... and it still showed the old device on the account. I contacted Customer Care via Chat and they removed the old device from the account and it then showed the S21 on the page. I then tried entering the address for WiFi Calling and it wouldn't accept it. When I hit "save" it threw an error for the address, which makes no sense since this was the valid shipping address for the device via UPS. So I put in a ticket with the Advanced Tech Support to have the Network Team go and manually try to enter the address on the backend or figure out what's going on here. C'mon T-Mobile..... TNX is good. The customer experience for account services management you're having Sprint run on the Sprint website actually stinks, and we're starting to see the cracks where Sprint's legacy content that was never updated (and probably never will be) or that customers get misinformation about device eligibility for TNX (Google Pixel 5) can negatively affect the TNX customer experience. In my case, I'm having a miserable time trying to update the E911 Addresses for Wi-Fi Calling on my Samsung devices and its because TNX broke Sprint's E911 Address management on Android devices. iOS devices however seem to work fine for these updates to be made on the device. Not sure why that is. Interested in what people think.
    • This one I found particularly interesting. They filed to upgrade the T-Mobile (orange) to n71 and n41 a while back. Then this week, they filed to keep the two surrounding Sprint sites (blue). The T-Mobile one is very tall with a huge footprint, so I understand why they might want to use the Sprint sites, but just very interesting they filed to upgrade it and then decided against it (as best I can tell).
    • Oftentimes they're locked into contracts with their contractors, otherwise they would just cancel the T-Mobile site's upgrade. 
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...