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

    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
    • So how does this whole direct to satellite thing fit in with the way it works now? Carriers spend billions for licenses for specific areas. So now T-Mobile can offer service direct to customers without having a Terrestrial license first?
  • Recently Browsing

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