Jump to content

Google Pixel and Pixel XL by HTC Users Thread


WiWavelength

Recommended Posts

The posts in the preview thread added since the release of the Pixel and Pixel XL late last month have been moved to this users thread.

 

http://s4gru.com/index.php?/topic/7532-pixel-and-pixel-xl-preview-was-fall-2016-nexus-htc-sailfish-marlin-rumors/

 

AJ

Link to comment
Share on other sites

  • 3 weeks later...

My handset was delivered this afternoon.  After unboxing and topping off the battery, Sprint online activation sailed through without a hitch, opting to reuse the universal 3-1 in one CSIM UICC from my Nexus 5X.  The online activation tool automatically recognized the IMEI/MEID as that of a Google Pixel XL.  In my online account manager, the active device and its avatar even immediately updated to the Google Pixel XL, correct color and storage options.

 

Other observations...

 

The AMOLED screen has a green cast in off angle viewing.  It probably is PenTile.

 

The engineering screens and other hidden system apps are accessible via the usual dialer codes as well as SignalCheck Pro shortcuts.  The CDMA1X engineering screen is borked, no readout even while in call.  The LTE engineering screen is standard issue for HTC.

 

fan3n4.png

 

AJ

  • Like 7
Link to comment
Share on other sites

My handset was delivered this afternoon.  After unboxing and topping off the battery, Sprint online activation sailed through without a hitch, opting to reuse the universal 3-1 in one CSIM UICC from my Nexus 5X.  The online activation tool automatically recognized the IMEI/MEID as that of a Google Pixel XL.  In my online account manager, the active device and its avatar even immediately updated to the Google Pixel XL, correct color and storage options.

 

Other observations...

 

The AMOLED screen has a green cast in off angle viewing.  It probably is PenTile.

 

The engineering screens and other hidden system apps are accessible via the usual dialer codes as well as SignalCheck Pro shortcuts.  The CDMA1X engineering screen is borked, no readout even while in call.  The LTE engineering screen is standard issue for HTC.

 

AJ

How does it seem to appear in comparison to your 5X for signal strength?  I know you just received it, but I figured I'd ask.  Not a ton of reviews about this phone in reference to actual phone calls / reception that I found online so far.

Link to comment
Share on other sites

How does it seem to appear in comparison to your 5X for signal strength?

 

My very limited, highly anecdotal impression thus far is that band 41 signal strength and retention are not quite as good as on the Nexus 5X.  I can do direct comparisons with the Nexus 5, Nexus 5X, and 2014 Moto X tonight or tomorrow.

 

AJ

  • Like 4
Link to comment
Share on other sites

My very limited, highly anecdotal impression thus far is that band 41 signal strength and retention are not quite as good as on the Nexus 5X.  I can do direct comparisons with the Nexus 5, Nexus 5X, and 2014 Moto X tonight or tomorrow.

 

AJ

Appreciate the quick feedback.  I'd love to see the comparisons of all devices, whenever you get a chance.

Link to comment
Share on other sites

Appreciate the quick feedback.  I'd love to see the comparisons of all devices, whenever you get a chance.

 

I am in a well deployed band 41 market, so that has limited my experience. But I am going to the library tonight.  Because of its construction, the library typically is a CDMA1X 800 zone.  That should be a good test in a challenging RF environment.

 

AJ

  • Like 1
Link to comment
Share on other sites

SRLTE and low band, for the win.  By holding on to band class 10 and band 26 both, the Pixel XL survives the library challenge better to my recollection than has any other recent handset.  In fact, I am posting this on band 26 from the library.

 

AJ

  • Like 17
Link to comment
Share on other sites

My handset was delivered this afternoon.  After unboxing and topping off the battery, Sprint online activation sailed through without a hitch, opting to reuse the universal 3-1 in one CSIM UICC from my Nexus 5X.  The online activation tool automatically recognized the IMEI/MEID as that of a Google Pixel XL.  In my online account manager, the active device and its avatar even immediately updated to the Google Pixel XL, correct color and storage options.

 

This was my experience as well. I also used a universal SIM (I had to call four stores before I found one with it in stock). The Sprint website recognized the device as a Pixel (regular) immediately upon entering the IMEI/MEID. Very smooth transition, including Sprint Google Voice integration.

  • Like 6
Link to comment
Share on other sites

time for a user thread?  and where to put it, under htc or google, eh.  :ninja:

 

Staff created a user thread weeks in advance.  Presently, it is hidden but will get reopened and posts relocated to it tonight.

 

AJ

  • Like 1
Link to comment
Share on other sites

Does the Sprint activated Pixel have wifi calling?

 

Nvm, found on reddit - mtcii - confirmed it wasn't activated...shame :unsure:

It's a tragedy. :( The phone is the most gimped on Sprint for sure

 

Sent from my Pixel XL using Tapatalk

  • Like 1
Link to comment
Share on other sites

I just got my Pixel XL and upgraded from Nexus 6P reusing the old SIM.  Sprint online activation was fast and smooth.  It's a shame it's taken this long, but glad not have to chat with international support.

 

I chose not to copy settings from the 6P, since I suspect some settings might be responsible for miserable battery life that I have.  Plus, i wanted to re-evaluate the decision on all the apps.

 

However, does anyone know if I can selectively copy the Wi-Fi networks from the old phone?

Link to comment
Share on other sites

I believe it's all or nothing.

 

For what it's worth, I also switched from the 6P to the Pixel XL today. It's the first time the online activation has ever worked for me. So far battery life seems drastically better, and I migrated everything over via USB. A lot of app data unsurprisingly didn't copy over (only ones that backup to Drive and are compiled targeting M or higher), but all my settings did. All media (images, audio, etc) copied, but not other files on internal storage. Some apps restored with data (such as Tapatalk) but had broken notifications until I signed out then signed in again.

 

Only my primary Google account copied over. I had to manually add my other accounts, but it at least then "remembered" the sync settings after adding it.

 

Sent from my Pixel XL using Tapatalk

Link to comment
Share on other sites

I have noticed, at least in Pittsburgh, while walking through by the park it will randomly drop from strong B41 to B26 (with an rsrp in the -60s). It really doesn't seem to like B25, unlike my 6P.

 

I did a test and disabled B41, and the phone locked on B26 and refused to budge. I didn't run a speed test, but it felt overloaded. I then eventually disabled B26 as well and then finally got on B25 10x10 carrier, got around 20mbps down and up.

 

My 6P would often load balance off of B41 onto 10x10 B25 because it's faster at times. So it seems Sprint still has some optimizing to do with the Pixel.

 

Sent from my Pixel XL

  • Like 2
Link to comment
Share on other sites

Looks like the those using the stock Google Messenger app for SMS on Pixel now get RCS support on Sprint:

http://www.androidauthority.com/google-messenger-rcs-726627/

 

Has anyone played with this on their Pixel?

Was hoping to see it active for me, but alas it's not there yet. Typical Google rollout, probably 5-10% of users per day will get it enabled with a server side switch.

 

I didn't realize Samsung devices have had it for a while. Does this also mean picture and video quality will be better sent via RCS than with MMS?

 

Sent from my Pixel XL

  • Like 1
Link to comment
Share on other sites

Was hoping to see it active for me, but alas it's not there yet. Typical Google rollout, probably 5-10% of users per day will get it enabled with a server side switch.

 

I didn't realize Samsung devices have had it for a while. Does this also mean picture and video quality will be better sent via RCS than with MMS?

 

Sent from my Pixel XL

Good question, does it mean that above?

Link to comment
Share on other sites

Was hoping to see it active for me, but alas it's not there yet. Typical Google rollout, probably 5-10% of users per day will get it enabled with a server side switch.

 

I didn't realize Samsung devices have had it for a while. Does this also mean picture and video quality will be better sent via RCS than with MMS?

 

Sent from my Pixel XL

 

 

Samsung has had RCS support built into their stock app for some time now. However the fact that Samsung devices as well as Nexus/Pixel device on Sprint are getting this notification about RCS at the same time indicates to me that this is a rollout on Sprint's side as opposed to Google managing it.

 

Also yeah, RCS should provide better picture and video quality though there may still be a size limit. I know on T-Mobile RCS messaging, you can't send files larger than 10MB.

  • Like 4
Link to comment
Share on other sites

Samsung has had RCS support built into their stock app for some time now. However the fact that Samsung devices as well as Nexus/Pixel device on Sprint are getting this notification about RCS at the same time indicates to me that this is a rollout on Sprint's side as opposed to Google managing it.

 

Also yeah, RCS should provide better picture and video quality though there may still be a size limit. I know on T-Mobile RCS messaging, you can't send files larger than 10MB.

 

I still remember those damn size limits on my EVO.  Limit was 2MB for MMS, but god forbid my photo ends up 2100KB, it'll get shrunk by the app down to 20KB.  I ended up retaking photos at slightly lower res to get things through.

 

On my Pixel, i actually switched to using Facebook for SMS.  This at least cuts down the number of messaging apps I need to use, plus it's easy to send bigger videos via FB rather than MMS.  Next question is whether FB Messenger supports RCS too?

  • Like 1
Link to comment
Share on other sites

Next question is whether FB Messenger supports RCS too?

Maybe after Release 2 of the Universal Profile, after the APIs are available? My hope is for that to be the case and see RCS support in Textra. Just not enough features in Messenger comparatively speaking, although RCS is YUGE.

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

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well. 
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
  • Recently Browsing

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