Oakley707

Well, the latest development in the saga is I went to a Sprint store and we tried all sorts of things, including settings resets and swapping out SIMs, to no avail. I got in touch with someone on the Sprint community site who was helping people activate Pixels, so maybe that avenue will get it straightened out.

 

If that doesn't work I guess I'll complain to Google and see if they'll swap out the device for a fresh one that presumably will activate correctly on Sprint (unless they've messed up some deep magic in my account at their end).

Have you asked to see if Google has released your MEID from their system?  Or have you asked Sprint to whitelist / add the device?  That was the hardest part to convince of either company and was a completely necessary step.

Good luck.

Somehow - very long story short - my Pixel XL seems to be provisioned for Sprint in such a way that it will only connect to 3G (the phone definitely connects to LTE with a Project Fi SIM installed on both Sprint and T-Mobile, so it's not a hardware problem). This has baffled everyone I've talked to at Sprint; we've tried everything (72787, PRL updates, device config updates...). In the hidden radio info screen I've tried wedging it into LTE-only mode and LTE cell information shows up under the "Cell Measurement Info," but for whatever reason it won't register on the network.

 

About to resort to the final straw of going to the local Sprint store and seeing if they'll try swapping out the BYOD SIM I picked up last week for another BYOD SIM and reactivating.

This sounds like the same problem I had with the Nexus 6 when i went to Project Fi.  Project Fi and Sprint do not play well together because they share services as you know.  When I activated Project Fi on my Nexus 6 AFTER I had my Nexus on Sprint it worked while on Project Fi, but when I tried to switch back to Sprint (was just test driving Fi) it would not re-activate.  Two weeks later after multiple store visits they found out that my phone's MEID was associated to Fi and that it wouldn't be removed from Fi's system thru Sprint.  So, I called Google and they were no help because it was VERY early on in the process.  I then went back to Sprint and they had to manually add my MEID (a two day process) which did eventually work.  I hope this is not your problem, as it was a real pain to troubleshoot / get a resolution.  Thankfully, persistence paid off.

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?

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.

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.

Nice speeds for B25? or B41?

 

I believe this was a Clearwire site and now is converted.Perhaps someone can provide input. 

Looks like the same pattern as Columbus, OH w/ our converted Clear sites.  GCI endings look similar.  Are you a Samsung market for NV?

If we were to win and wanted the XL, are we able to pay the difference to upgrade if the fundraiser only raises $750?

Thanks in advance.

https://madeby.google.com

 

In case you haven't done so already...

Thanks!

I hope the rumors that the phone will only be available thru Google and Verizon stores.  Especially if the price point is $650+...

I snagged this and so far, very happy

Only difference I see, is that the type c cable for us is plugged in.  We therefore can purchase a longer / shorter cable if necessary.  Not a big deal at all, but FYI.  It certainly gets great reviews on Amazon.

I keep the rapid charger at home, it moves rooms as needed   I have the A-C cable in my laptop bag and I throw it on the charger for my hotspot when needed at the office.  Once I have an appropriate car charger, I should be all set.

For what it's worth, I have been using this for about a month with great success.  Charges quickly and efficiently.

Just based on observed charge times and watching the charging meter in Android OS.  I could get about a 90% charge on the MXPE in 45 mins, takes probably an hour and a half on the N6P with the included charger.  Also, looking at the expected charging line in Android, the MXPE line is a much steeper graph indicating a much faster increase in battery percentage.

I would stand to reason it is due to the smaller battery in the MXPE? 3000 mAh compared to 3450mAh.

Having this device for just over a week and all my reviews are very positive except the lack of Miracast and QuickCharge 2.0.  Band switching is very fast, on par or faster than my Moto X Pure Edition.  This thing loves Band 26 and stays on it in many places that I would drop to to 3g or 1x.  Data sessions are much more stable, on the MXPE, many times I would have an icon for an LTE connection, but data would never actually flow.  The bump for the camera is much smaller than I expected and not an eye sore at all.  I love Android N and the Finger Print scanner for unlocking.  I can't wait for more apps to integrate finger print authentication.

Why are you missing QC2? IIRC, USB-C charges faster than QC2 though it's been awhile since I measured charge voltage on my 6P, I was pretty concerned about it too when I first got it back when it first came out. 

I agree, what is the loss of QC2?  USB-C rapid charging is just over an hour from nearly dead and way faster than my Nexus 6 charged.  Or at least it feels this way.

I'm with you on the fingerprint scanner.  Sooooo nice.  Wish Android apps would start leveraging it though.

My 6p reception beats my old n6 signal wise. Best phone I've had as far as signal goes.

 

Sent from my Nexus 6P using Tapatalk

Unfortunately, I have to agree with david279.  I came from a Nexus 6 to a 6P and the reception is great.  I do have rare issues where my radio will sometimes hunt and not perform but a reset resolves this issue.  What software are you on, by chance?  I'm on Developers Preview N...

Man, I left sprint for about two years (since I last posted) and am now back with a GS7 and I'm amazed at the progress made on speed and better coverage. I love WiFi calling too big savior when  i'm at moms house with no service visiting. Anyways, are there plans to switch to VoLTE and use the wifi calling handoffs to VoLTE like Tmobile and Verizon do? That would be great. Wifi calling right now is kinda like an (dare I speak its name) air rave.

 

VoLTE from what we believe is still quite a ways out.  I believe the last I heard was 1-2 years at least.  They simply need to have the LTE density expanded dramatically in order to not have dropped calls.

I must admit, this phone is awesome!  I cannot believe how much of an upgrade it is over the Nexus 6.  Love it and the battery life so far has been phenomenal.

Damn you Prime day and your $400 Nexus 6P...  I guess, I will be joining this thread tomorrow, .

I know. While it is old, it is lighter and has no annoying Verizon Wireless ads (or ads at all).

Just brought back memories.  For a minute, I thought I was looking at a post from 2010.  For what it is worth, I just used my Google Opinion Rewards to pay for an ad-free version.

This phone acts extremely weird with Band 41. Sometimes, it is too quick to drop it, but other times it sticks to it like its life depended on it. Sorry for the SpeedTest, but it's just to show that the phone was still making a successful (yet terrible) connection to the cell tower.

 

On a positive note, SMS was fine both inbound and outbound at this RSRP level.

 

Holy old speedtest.net app batman.

I believe that is your problem.  I think it happens with any Sprint MVNO.

Ordered it from Google.

 

Went online and found that it needed a special sim, couldn't just cut my N5 sim to fit. Called the store, told me to call Sprint cause it needed to be ordered, so I did Chat which gave me some special number to call.

 

Then went to the online portal of which my phone does not appear in the system. Chat confirmed of which they put in a ticket for me.

 

 

I did take advantage of the ProjectFi deal, so the phone did have to activate on ProjectFi. But that is cancelled. Does Google send Sprint a list of phones that get activated on ProjectFi so Sprint to remove them from the Whitelist?

Back when I first received my ProjectFi sim card and activated and then tried to re-activate my Sprint sim on the same phone I had a similar issue.  Unfortunately, it took almost 5 days to fix...  Thankfully I had an old N5 laying around I could use in the interim.  I believe the process is supposed to be smooth and hopefully by now is better, but when I activated on Fi the IMEID went into their database / flagging Sprint's.  The cancellation process from ProjectFi took forever for them to let go of the IMEID.  It eventually had to be manually entered, or at least that is how they described it to me.

So, when I'm showing B41^2 on SCP, shouldn't I be indicating DL Channel (scc2):

on the engineering screen?

 

(I wasn't last night while on 0B14F303 - Plattsmouth, NE.)

 

Everything was still (SCC1)

 

I took screen caps.

 

As mentioned previously, when you are on B41^2 it doesn't mean you are on CA.  It simply means you are on the second carrier of B41.  In other words, the second 20 Mhz channel not the first 20 Mhz channel.  SCP does NOT show you whether you are connected to both the first and second / or CA from a nearby site.  Only way to find that out is thru engineering screens..  Hope that helps.

I guess you're missing something..because I've had an airave since the very first one hit the market back in 08..and had Samsung branding on it. And the same sh*tty connection that I've always had. I know what works, and the airave is better than wifi calling. The current airave supports 6 simultaneous connections....3 voice calls and 3 data sessions.

 

While the airave is designed to handle just traffic from a phone (read:femtocell), wifi calling has to battle with everything else on the network and is subject to any other traffic that might be happening at that time.  While the real-world application differs from the "it's supposed to" application, I have no problem using 2-3 lines at once on the airave, while I have issues using just 1 line on wifi calling and nothing else can happen while that wifi call is in progress. Once the airave gets here, I'll be glad to post some screens from my Nighthawk X8 (R8500) router with wifi calling while in a call, then post a screen of the airave traffic while in a call...

I already know which one eats up the most...but if it'll help anyone understand what I'm saying, so be it.

It would be great to see your the real world data comparing Airave to WiFi calling.  Some of the difference may also be how your equipment is connected/configured.  Sprint normally wants the Airave first, which gives it high priority.  Most people also setup any VOIP also with high priority.  It is also great to see the amount of bandwidth consumed.  It used to be that very high quality voice took 64Kbps.  I am uncertain what HD voice takes.  The odds are everyone will learn something from you comparison.  Looking forward to your info.

I would also like to see the data.  I believe dkyeager may have hit the nail on the head with the configuration of the airrave as well as the QoS vs. wifi calling.  I guess I just find it interesting that wifi calling is so much more inefficient than an airrave with the connection coming from the same "backbone".

Yeah, at my house.

 

And mainly the reason I don't want to use wifi calling and use the airave is because I can't. When you have 4 devices ...or even 2 devices on wifi calling at the same time and you have a 511kbps upload speed, it tends to make it not worth even hitting the "call" button.

For a single device, Wifi calling is fine, but once you get past that amount, you can't make phone calls if someone is 1)uploading photos/vids to cloud, 2)watching anything streaming, 3)listening to music streaming, 4)considering a google search, 5)having a thought process that involves anything internet-related...

 

It'd be great if i had another option, but I don't.

I might be missing something, but the airrave is connected to that same connection that your wifi calling would be as well, no?  Back when I had an airrave I remember it using bandwidth for the 3G connection from my cable modem.  I would think you would have the problem regardless of airrave / wifi calling.

Flashing the newest software and being unrooted and such did nto fix my camera.

 

Also, I found something sweet...the Voicemail tab within the native dialer now works for those who use google voice to handle voicemail!  FINALLY decent visual voicemail works again.  You just have to enable it within the google voice app to show voicemails in the dialer tab.  This is huge to me.

To clarify, do you mean you are now able to use the native dialer to check visual voicemail?  I have a Nexus 6 and the only reason why I use the GV app is because the Sprint VVM app wouldn't work with it.

I may have to try using the native dialer on the N6 and see if it works there as well.  That would be nice.  I cannot stand the archaic look of the GV app.

Didn't realize it was this easy!  Just checked for the N6 and it works flawlessly.  I wonder if there is a way to setup a shortcut to open that tab directly.  I'm glad you posted about this, I cannot STAND the look of the Google Voice app.

Others here http://forum.xda-developers.com/nexus-6p/help/lte-issues-6-0-1-radio-canadian-carriers-t3267270 are having the same issue.  A couple people have reported that flashing the old radio (.2.6.1.c4-00005-M8994FAAAANAZM-1) does NOT fix the problem, some have reported that it does.

Hmmm... that is weird.  I wonder why flashing the radio wouldn't fix the issue.  I stand corrected.

That's unfortunate, didn't have an issue with the previous one. Now I randomly drop to 3G. Also happens after a call as well which never happened before.

Flash the old radio?  Nexus FTW!