yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChiTownPack:
I have been having this same problem lately. As you stated, it is problematic because you don't know you are missing messages/calls. I updated PN in mid June when it dropped and didn't start seeing issues until last week, so i would question other apps (or Verizon) as the culprit.

I suspected a call blocking app I installed just before I started seeing this issue. I haven't had any problems after removing it, but how do I really know, right? :silly:

I have heard it could be a Verizon issue as well.

I know that's not a helpful answer, but it let's you know someone else is sharing in your misery! I'd be interested to see how many others have this issue......
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aostrom:
OT: Should I move from nexus 6P to Pixel XL?

OK, I know this is off topic (a little), but since I've been running Pure Nexus on my Nexus 6P for well over a year and this is the Pixel XL Pure Nexus thread I think you are the right people to ask...

So - the question is - for those of you who have used both phones, the 6P and the Pixel XL - is it a worthwhile upgrade? I own my 6P outright, but I can get the 128GB Pixel XL from Verizon on sale now (I know about this issue with locked bootloader from Verizon - I'll figure a way around that), and pass the 6P along to someone in the family.

I really like my 6P, my biggest complaint would really be that I live in a fringe LTE area (20 miles from Boston!) and sometimes I can't get a decent signal while my wife's Moto works fine. I just got a referb under the extended warranty from Google, my fingerprint reader died, so I am getting good battery life once again. Would those of you who moved from the 6P to the Pixel XL do it again? Is it worth the $25/month ($600 over 2 years)?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
My first ever Android phone was the 6P, and this XL being my second ever - and I'd say just from the amount of development available for the 6P, it's worth sticking with.

The dual slots tend to cause a lot of confusion and chaos as well, so if you want to avoid that whole headache, it's another reason to stay with the 6P.

I live in Canada, so I don't have too much knowledge on mobile plans in the US, but from what I've read, there is no real easy way to get around unlocking the bootloader on a Verizon model.

Lastly, the Pixel 2 is not too far away, so you could also wait until that releases, see how you like it, and make the upgrade then.

I know my main point of staying with the 6P focused just on development for the device, but that's mainly what I look for in an Android smartphone, so I'm just speaking from my own personal wants in an Android smartphone!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ASwedishDragon:
Whenever I try to change the boot animation on my Pixel XL running PureNexus, it stays the same. I tried everything, I changed the permissions to 644, rebooted, nothing. Any help would be greatly appreciated. I really hate the stock boot animation, and im trying to get the black Pixel boot animation. Also by the way this the best room I've ever tried so yeah, just wanted to tell you..... Keep up the good work!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
Deleted - Fixed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 318sugarhill:
Having owned the 6p and the Pixel XL I would absolutely NOT trade up for a LOCKED vzw model. The pixel with dual boot slots makes tinkering more of a hassle, but not terrible. There is definitely more development for the 6p. As far as fringe LTE.....that definitely was an issue for my 6p. The radio was horrible and I often had to step outside my house to the back yard to make a phone call. I did not have wifi calling on it (not sure if it has it now but I didn't when I had mine). The radio and signal in my pixel is leaps and bounds better.

I will say of all the phones I've ever owned, the HTC models ALWAYS had the best radios and signal. LG would be a distant 2nd, and Samsung even further behind in 3rd. The radio/signal on the 6p was one of the worst. Signal strength has a huge effect on your battery life.

So you have to ask yourself what's important. I know the Pixel 2 is coming in a few months. Me personally I would ride it out with the 6p until the next pixel comes out. The Pixel is almost a year old at this point. And I don't see an unlock method in the pipeworks anytime soon.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
I would totally recommend AGAINST moving to Pixel XL. From a benchmarks perspective, yes Pixel XL has better specs, but if you install PureNexus on BOTH the 6p and the Pixel XL, remove bloatware and have a nice Kernel - the real world speed difference is negligible. The faster 821 chipset and an extra gig of RAM - help, but not significantly. To counter that, 6p has a bigger screen and stereo speakers and I also felt that it ran cooler than the Pixel XL (less battery/CPU temperature).

I used to have a Nexus 6, got a 6p as well and used both. So my Nexus 6 USB port failed, and 6p I gave to my cousin. Decided to get a Pixel XL. Paid $840 with Taxes for a 32 gb. For that kind of money, I am decidedly underwhelmed. Yes, it is a good phone, and I like it, but maybe not worth that much.

Since I purchased Pixel XL in May 2017, I feel that I should have waited and purchased Pixel XL 2, especially as there was NO discount on Pixel XL. But I had to get a new phone as I had given away my 6p and Nexus 6 charging port failed. Please do NOT make the same mistake that I did and wait until October this year.

The newest renders show that Pixel XL 2 will be an amazing phone with bigger screen and super thin bezels (http://bgr.com/2017/07/12/google-pixel-xl-2017-release-date-soon-image-leak/ ). I regret not waiting for the phone. Now if I want to get it, I will have to sell Pixel XL at a loss (maybe $250-$300 less than list price) - which doesn't seem worthwhile.

So I would STRONGLY urge you to retain your Nexus 6p and wait for the Pixel XL 2. Nexus 6p will also get Android O, so you're covered with updates.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aostrom:
318sugarhill & iamjimmy, thanks for the great input. I've been doing this Android thing for a long time -- I started with the OG Moto Droid at Christmas 2009, then a Samsung Galaxy Nexus, then (unfortunately) an LG-G3, then the Nexus 6P. (And lots of non-android phones before that, going all the way back to a monster "bag" phone circa 1989). I've been rooted and ROM'd since the beginning (except with the LG). I'm not into hardcore gaming, or over the top theme customization (tried Substratum, much more hassle than it was worth). I find the combination of a ROM that's close to AOSP like Pure Nexus (RASTA ROM in the past), an efficient kernel (Flash Kernel now, Trinity Kernel in the past), plus Nova Launcher really does enough for me.. I do have LOTS of apps loaded (Google market says 304), a few of which are CPU hogs (and lots of mp3 files), so the speed of the 6P with 128GB of storage is really the first phone with enough performance for me.

My thinking was that the Pixel would have a longer future than the 6P (I'm pretty sure I could find a way around the locked bootloader somehow). I really have no major issue with the 6P other than the weak radio and occasional issues connecting to my PC over USB. I just got a refurb device from Google because my fingerprint scanner died and the USB port was flaky, so even battery life is good once again. [I can get one more refurb for $79 with my extended warranty - I have a feeling I might have a hardware problem sometime early next year ;)].

I suppose that as long as Beans & Nathan keep releasing updated ROMs and Kernels for the 6P I have no real need to "upgrade," and since I don't hear anyone saying that their Pixel is a huge step up from the 6P I think I'll just stick with it. Thanks again for the feedback.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
PureNexus will likely be supported at least until Fall 2018 on Nexus 6p with Android O. Even after that, maybe Nathan himself, or someone else, will probably port Android P to Nexus 6p. So you should be good from a support perspective. I also doubt you would see a real world difference in performance - with the lower specs of 6p vs Pixel XL.

To put the dev support into perspective, I still have a Nexus 5 (purchased in 2013). I recently installed Pure Nexus 7.1.2 6/12 release with Flar2's excellent Ex kernel and the phone just flies. This is when Google didn't even officially support Android 7 on Nexus 5.

If you want to spend some cash, I would say wait till later this year and see Pixel XL 2. So far it seems that it might be an amazing phone. One final pt: the dual boot setup of Pixel is NOT a disadvantage I feel. It seems confusing initially, but once you get the hang of it, it's pretty neat and allows a dual boot partition.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] med458:
Hi a couple of questions if I may.

I installed it and its working good, thanks.

Is there a trick to getting maps etc other than the obvious play store route?

Also, how to determine what the most current version of radio, vendor, etc is?? I used the most current version of vendor and my phone told me to downgrade to an earlier version. Thank you.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Search www.apkmirror.com for maps

Get builds here:

https://developers.google.com/android/images

I probably would've baseline off a July build before installing PN.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nil253259:
PN is yet to release July security I think..the latest is based off June..so latest vendor would throw warning after boot up... Flash June vendor and you're good to go
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] med458:
very cool thanks guys and/or gals
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bb12489:
So maybe I'm doing something wrong here with flashing....but why am I getting dual Phone, Contacts, and Calculator? I don't remember this happening in previous PN builds. I mean I understand that one set is AOSP, and the other is Official Google/Playstore. Is this normal?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Are you flashing gapps?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bb12489:
No Gapps. Just the PN zip
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
And they didn't restore from the cloud?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bb12489:
The AOSP versions were already on the phone as system apps. The Official Google versions installed during my cloud restore.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] WhiteEVO:
Can't you delete the AOSP versions and set the Google versions default? I'd rather have the Google apps myself, what are the advantages of the AOSP apps?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bb12489:
Yeah, I already disabled the system app versions. I'm not really sure the AOSP versions have advantages over the Google ones. The Google versions can at least receive updates from the Play store.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Amritttt:
I've tried most of the roms and i keep coming back to PN its flawless.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fletch33:
is PN slowing down on updates? i have noticed we are 1 month past the last release and there doesnt seem to be a changelog started yet?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xxfwmxx:
Have you checked the git?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jammol:
I might be wrong but he maintains more than two devices, and has personal life things so.... Yeah! ??
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fletch33:
Yeah I know. He is also tweets a lot. I was hoping he might catch that post ;)

Been donating and using his ROMs since before PN
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] PaulPizz:
View attachment 4213666

You can build your own unofficial version from source. That's what I did and usually do. ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Donating really isn't a justification for on the sly asking for ETAs. It never has been and in fact this whole statement sets a bad example for other users.

If you know he is active in other places ask him the question directly, not these passive statements like:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 318sugarhill:
I get both versions too when I install. I just delete one version. One is lighter icon the other dark. Not sure which is official and which is AOSP but the lighter blue is the one I keep.

I don't know about anyone else but in the past I've run elemental kernel and I've run it without. Battery life for me is far better anymore with elemental. It used to not matter, but I can't go without elemental on PN and expect to make it through the day
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jammol:
Damn, I was about to bring out my Pats soon. You know.....for his back! :p
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 93fuelslut:
Does anyone have the problem where data is cut off during a phone call? I use my hotspot at the house. Pixel isvl the only phone that does this
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] laxattack:
anyone passing safetynet today?

Edit: Passing now, it was Magisk followed https://xdaforums.com/apps/magisk/safetynet-fix-pass-safetynet-2017-07-17-t3637801/ and also ran "getprop | grep magisk" to make sure all magisk signs were removed
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jammol:
What carrier do you have?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dorqus:
Nope :(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] laxattack:
check the edit of my post
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 93fuelslut:
Verizon with Google pixel. I've had multiple phones with cm or aosp for years and never had that issue.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jammol:
Verizon does VoLTE? I think that's the feature that enables use of data while on a phone call.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bradhoschar:
Don't ask for ETAs
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 93fuelslut:
Not sure if VoLTE is the problem, because I never had the issue years ago.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fletch33:
Thanks for the update I didn't see him post that :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alg0rhyth3m':
So I was earlier trying to flash another ROM and having issues so after reverting to stock I bounced over to this thread. Now I'm wondering if I should have reverted to the June build instead of the July build? It actually matters, right? So I just booted into system for the first time and its saying "Your vendor image does not match the system. Please flash the NJG47B vendor image for your device." But I am supposed to be on NHG47N build if i was actually using the June image, but I'm currently on NHG47O for the July build. What should I do at this point? Do I need to stock again? Please tell me no lol.

** EDIT.

Fixed. I just reflashed the stated vendor image through TWRP and rebooted into system and am good now!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bradhoschar:
Wut?

So, I thought I would try DP3. That only lasted about 3 hours.

Wanted to go back to PN, and I did the following:

Rebooted to bootloader.

verified my device was showing up by: fastboot devices

ran fastboot boot twrp.img

Now for the weird part.

Phone reboots to twrp, but it only flashed for ONE second then reboots, and that keeps happening.

I thought it was something to do with the slots, so i REflashed DP3, enabled USB debugging, and tried to fastboot boot twrp.img again, and its still bootlooping and flashing TWRP for another second.

Anybody ever see this?

It's freaking me out! and I just want my PN back!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
I think you need to first flash N images and then flash PN and twrp
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
So fastbooting twrp patches both boot.imgs. If the boot.img in your other slot is the O beta it's going to cause twrp to fail.

So what I would do is boot into the bootloader

Fastboot flash boot --slot all boot.img (stock July N)

Fastboot boot twrp
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bradhoschar:
Well ****.....

I ended up dl'ing stock 7.1.2, and extracting and flashing it that way.

Thanks guys~!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aaronpw0621:
Made a lock wall for our device. Please enjoy! If ya want it for the little Pixel follow this link....

https://plus.google.com/+AaronWieneke/posts/UoTdFrs1W3d
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
So I decided to try using flash-all by removing the "w" to avoid wiping data. Seems like many of you do this to save time for clean flashing to new builds while leaving your data intact. Unfortunately, it did not go so well for me. I'm wondering if anyone is able to provide some insight on what I did wrong (although I already may have an idea, I'm still hoping someone else can confirm):

My steps were the following:

1. Downloaded July factory images

2. Edited the flash-all file by removing the "-w"

3. Executed flash-all

4. Rebooted system, and it seemed like it was successful

5. Rebooted back into the bootloader and switched slots, then ran the same edited flash-all (this is where I think I messed up)

6. Rebooted back into the system and everything was crashing (was getting several messages saying "x app has stopped")

To remedy this, I just ran flash-all with the "-w' intact, and started from scratch.

If I had to guess, I believe switching slots is where I went wrong. When doing a flash-all with the "-w" removed, am I supposed to do it on the active slot, and not the inactive?

A second question I have is, once I do successfully complete a flash-all with the "-w" removed, what would be my steps for getting PN, or any other custom ROM on my device? I ask because majority of the time, ROM flashing instructions mention swiping to factory reset in twrp, but doesn't that delete all data? And therefore result in removing the "-w" to be pointless?

Sorry for the lengthy post, but if I can get this figured out, I feel switching between ROMs or upgrading to new PN builds would be much more painless! Thanks in advance :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I dont think its switching slots and without switching slots and have never been able to recover those apps with the dirty factory image, I always end up doing a factory reset. Not very helpful but I don't think switching slots caused your issue.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
No worries, thanks for your input! I may just stick to doing what has been working for me - flash-all with the "-w" and using TiBackup to restore apps
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I guess at some point I thought -w wiped much like a bootloader unlock did so I found myself removing it out of habit and then doing a factory reset anyways before flashing the rom. Not very smart on my part.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
It's all good, it's all a learning process, especially with these dual slot Pixels lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Were you on stock ROM or Pure Nexus before running the flash -all script?

If you were on PN before running the flash -all script on both slots. Then you need to flash the ROM before rebooting system.

Basically the flash -all script (-w removed) will flash the stock system, boot and recovery. If you boot without installing the ROM first, there will be inconsistencies with the ROM data on your system (since you're NOT doing clean flash) and the stock image.

If on Custom ROM, for dirty flash, I would first Flash ROM again and then reboot. The steps would be:

flash -all (remove -W)

reboot bootloader

switch slot in bootloader (using fastboot set active)

flash -all

reboot bootloader

Fastboot Twrp

Install/FLash TWRP.zip

In TWRP - advanced Wipe - Clear Cache, System ( do NOT wipe data)

Flash PureNexus.zip

Flash TWRP.zip

Reboot system.

Reboot to Recovery

Install SuperSU

Reboot to System

Install Custom Kernel

Reboot to System

__________________

I personally feel that it is enough to just flash the radio, bootloader and vendor from the stock image on both slots. No need to do the entire flash -all script.

That way you do NOT overwrite the recovery and do NOT need to install TWRP again. ( Flash -all script will overwrite TWRP).

For dirty flash you first flash radio and bootloader on both slots. Then you can reboot to TWRP and just clear cache (and system [optional] ), install ROM, install TWRP (as the ROM overwrite TWRP) and reboot. Finally install SU, reboot system and install Kernel. As for the vendor, that can be installed through TWRP itself.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] toakster:
I agree with this. Also, if you want to skip the set active command, you can use fastboot flash radio_a {name of radio} then repeat with radio_b. Same goes for bootloader_a and bootloader_b
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
Ahh, this makes a lot more sense now. I was on PureNexus before doing all of this! I thought by removing the -w, it would be somewhat of a "shortcut" of clean flashing, so I can go to other ROMs, but I guess not. So by removing the -w, I should be reflashing the current ROM I'm on, not stock/other ROMs.

Thanks for all the additional tips and steps! It's much appreciated; I'll give those a shot when I start itching for flashing again haha #flashaholic
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Using the -w switch preserves the UserData for a dirty flash. A dirty flash is only good, when you are NOT changing ROMs. If you're going to change ROMs or go to stock, then put back the -W in the flash.all bat file.

As mentioned before, running flash-all.bat will replace system and boot partition with stock, so in case one is dirty flashing a new release for a custom ROM, you need to flash TWRP and the custom ROM again before rebooting to system.

Overall, if you're dirty flashing, it is probably easier to just fastboot the radio and bootloader on both slots. Then TWRP will be preserved and you don't have to fastboot and install twrp again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I also think you can use the command

Fastboot flash bootloader --slot all bootloader.img

And it will flash both slots. Works for other fastbooted files as well
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] RhapsodyK:
Does anyone experiencing the following issues as i have been undergoing in the past 2 weeks after July security patch? Bought the phone on late 2016 and have been using flawlessly in the past few months. However things started to get mess up. At first my device occasionally freezes itself without any notices, which causes random reboot. 3.5mm jack and microphone stopped working somehow (reboot might help at first but not anymore) and now i even can't watch any videos on my pixel xl (error code occurs no matter i'm watching youtube or videos that i have shot in Google Photo). Everything started about 2 weeks ago. I have checked the product forum on Google and several users also reported the above issue (s).

Running the latest Pure Nexus + Supersu 2.82 with pixel fix

Thank you.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Nice. This would be shorter than having 2 commands for both.

I'm assuming this could be used for flashing radio and vendor as well?

Also do you know whether the July Security patch (from google) has any major bug fixes or features?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I have no comments on either. Nothing saying stay away and nothing saying must have either
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] taz1458:
Did it help? I already had mine there and still get it. Full data, but no call/text. Pain in the butt