yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikaole:
But this could lead to problems if you don't have pure on both slots.

Dirty flashing

Boot into twrp

Boot to the not active slot and hold vol-

Boot to twrp from bootloader

Flash rom and twrp

Now you flash the rom to the last active slot

Reboot and hold vol-

Flash vendor

Flash gapps

Reboot
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Not really, the zip over writes system and data is shared between both slots. Also Gapps are included. The dirty part is the data partition not system. As long as you are booting to the slot you just flashed it really shouldn't be an issue.

As far as the dirty flashing, its a roll of the dice. Doesnt seem any less consistent than other none slotted devices.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pjgraber03:
Ok so I'm having an issue and I'm not sure why. I have a pixel xl no issues at all. My cousin has a pixel xl and I have used the same methods on his but anytime I flash a rom and boot into it run the update on the google apps and reboot back to recovery its encrypted. I'm stumped I have tried numerous things trying to figure out why it keeps encrypting. Anyone have any thoughts that might explain this.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I think we need more detail. The device is encrypted by default. Do you mean that TWRP isn't de-crypting?

Also what version of TWRP are you using.

This might be a question better posed in the TWRP thread if a quick answer isn't achieved.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pjgraber03:
Well I'm using RC1 on both of them..and what I mean by Twrp isn't decrpyting is this. So I'll list my steps (that I have done on both phones)

Completely Flash stock

let it boot - reboot back to Bootloader

fastboot boot twrp

flash twrp zip.

reboot recovery

wipe data and system

Flash PN then twrp zip again

boot PN

reboot back to recovery

Flash SU

boot back to os

Setup phone (as in just signing into google and setting up as fresh device)

Reboot back to TWRP --- Its encrypted (but on my other pixel TWRP is fine)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jrbxx7:
Do you have a lockscreen pin or pattern? Twrp should prompt for it allowing decryption. Sometimes it might take a few tries for it to prompt.

?Tapped from my pure pixelXl?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pjgraber03:
It does prompt and I say allow modifications..... but doesn't actually allow modifications.....It just shows random numbers and letters

and yes he sets up smart lock
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dmb219:
this happened to my phone once or twice, I remember the random characters instead of file names. a reboot fixed it & never saw it again. i've seen others report the same, attributed it to a bug in twrp but not sure. if it won't fix itself, not sure what is up...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pjgraber03:
ok i'll keep trying lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
So it'd confirmed root doesn't work with newest version with custom kernels?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Framedtrash:
Huh ??

Running elemental and root is working just fine
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] shizumie:
Hmm, working fine for me. However I always seem to root, setup, then install my kernel. Seams like I read that there was a problem installing SU before kernel, but I can't attest to this. Also not sure if older kernels will play nice, I'm on latest elementalX.

Also remember it likely walnt show SU in apps, but instead manage through settings. Settins<rom control<superSU

If this is redundant information for you, please ignore?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mac796:
I installed elemental after root. Running good
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] shizumie:
Yup, I figured it would work either way. I just normally flash kernel after root, so my kernel tuner works as soon as kernel install.

Glad to see it works either way. Thank you
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joeyac02:
Finally figured out the visual voicemail issue I was having. It was on Verizon's end thanks for everyone's help!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MeetFace:
If you're seeing the random characters it means TWRP isn't decrypting your biz. SoL until you can get it to decrypt .
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] coldconfession13:
Is anybodys bluetooth randomly shutting off? This is the second day I've noticed this since the update.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] shizumie:
Not for me yet. Only used BT about 4 hours yesterday, (continued use), and about 30 min today.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] coldconfession13:
Yea I only notice it because my moto 360 disconnects and I noticed that my bluetooth is off.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bajasur:
Any T-Mobile users not able to get visual voicemail working on google dialer?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Mennooo:
We will see on monday, i talk in my bt handsfree 8h/Day so i hope it will work. Bought my pixel yesterday.

Skickat från min Pixel XL via Tapatalk
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] WyldOne91:
I use a Pebble smartwatch 24/7 and my Bluetooth headphones all day at work as well. I haven't run into any issues at all myself.

---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------

I know a lot of people have been having visual voicemail issues. Mine will work (or at least says it will) for Verizon but I use Google Voice myself and that doesn't show up as an option with this last ROM update for some reason. Anyone else use Google Voice and have the same thing?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
I'm experiencing some heavy idle drain. My device was at 100% last night, and when I woke up this morning, it was at 87%. Losing 13% overnight seems abnormal.

This has happened before, so I uninstalled the Light Manager app and turned off my LED entirely, since BetterBatteryStats was showing me that was the biggest culprit, however the drainage remains.

Now, BetterBatteryStats shows these as the following culprits:

Netmgr_wl

PowerManagerService.Display

com.google.android.gms

android system

I did a search on this thread, and someone mentioned clearing data for the Google app helped, but that was also a no go for me. Has anyone else experienced this, and have a potential fix? Thanks in advance!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] grinchyyy:
I had the same problem on the previous build, have yet to see it on this build. My wife's Pixel XL suffered from the same thing on stock December image, she's now on February stock and hasn't seen bluetooth shut off yet either. We both have EX kernel.

Bluetooth quality is my only gripe about these phones...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
The TMobile visual voice mail?

---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------

I was having that issue. Kept noticing my gear s3 was disconnecting. I had to do a clean install
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] thehotboy:
Did you disable the phone app and enable the Google phone app? You also have to set Google Phone as your default phone app.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mike489:
Is anyone else unable to restore their pixel launcher layout from the cloud with PN? I was able to do it on DU and RR. Does it work for anyone else?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] eoh7678:
Network switching with Project Fi doesn't seem to be happening

OK, quick question here- I've tried searching but can't seem to hit on any terms that help find an answer.

I've got a Pixel XL, obviously and I'm on Project Fi. When using the stock ROM with Elemental 1.06 kernel, I have no problem when traveling with the phone auto switching between Sprint, T-Mobile, UsCellular, etc as Fi does. It does so automatically and flawlessly.

Yesterday, I clean flashed the latest Pure Nexus, with the proper vendor image and the same Elemental 1.06 kernel, but it seems it stays locked on T-Mobile. When traveling to the same locations today, I had no signal at all and the Pixel seemed to be locked on the T-Mobile network and unable to switch.

I tried FiSwitch, and it didn't work to manually force a change either.

Hate to have to go back to stock when PureNexus is so much better. Any advice?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cowsquad:
So this slot terms got me confused again today. I was on January build right. So I boot into TWRP. Checked that I was on slot A. So it mean PN is installed here (slot A) So I booted into slot B in recovery, since, presumably the ROM get flash to opposite slot. So I am on slot B now. I flash the rom (dirty flash). So I assumed that I will be flashing the ROM to slot A. Bare with me :). Rebooted to slot A. So, I am on A now. Reboot the phone. Bang!!! Phone reboots to a recovery again. Okay, So I reboot back to slot B. Reboot the system. Phone boots just fine. So what the f.... Is this slot craps now? Now PN is booting on slot B with the latest rom. Confused ??
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Paz9:
umm

if your on slot a

and flash

it flashes to slot b and automatically boots to slot b

good guide to follow:

**How to flash new version on existing Pure Nexus slot**

Make sure you download the new version and have twrp and SU zips if you want those again.

-Reboot to recovery

-Tap reboot button (Take note of current slot. This is the slot Pure Nexus is on currently)

-Tap on the opposite slot now

-After it switches DO NOT click "reboot system". Instead press the back arrow and then tap "reboot bootloader "

-Verify in bootloader you are now in the slot you just switched to and then boot to recovery

-At this point my storage was encrypted so I just did a "reboot recovery" and I was promoted for PIN again

-Flash ROM

-Flash twrp zip

-Boot system once then go back to twrp

-Flash SU zip

Reboot
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cowsquad:
You did not read my entire post. I just explained that I was on slot A . So in order to have PN on slot A I had to reboot to slot B. So once in slot B. Then ROM would be flash to slot A. It did not.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Unless you have a reason to preserve the other slot for something. Why manually switch slots?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jjayzx:
There is no reason except confuse people and make things more difficult.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] johnandbodhi:
if you reboot to recovery after flashing pn you're in the same slot you started with..you gotta boot it either into bootloader or the rom itself before you flip to the opposite slot..jmho
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jayf99:
Thanks very much BeansTown for this awesome ROM. It was the reason I finally unlocked my bootloader last month. I've been following this thread for a couple of months and I agree there is a lot of confusion out there still about these new dual slot phones. I wanted to try and help with that.

If you followed Beans' instructions the first time you flashed this ROM you would have wiped you data and done a factory reset. If you did that I'm pretty sure you wiped both slots and not just the one you were currently on. That means when you flashed PN the first time you had PN in one slot and nothing in the other. So now when you want to flash a new version it will flash to the other empty slot. As someone has already stated all of you user data is separate from the slots so if you don't wipe data you effectively get the new version cleanly flashed while still retaining all your data. When you go to flash a third new version of PN now you will be flashing over the old slot with the original version and it should still work just fine. So the short story, as someone already stated, is don't sweat the slots unless you have flashed something other than PN in-between.

Here's what I did to upgrade to the 20170215 version. I am in the US and my carrier is Verizon.

Reboot to Recovery and perform a backup

While still in Recovery connect phone to computer. Copy the entire contents of your Internal Storage to your computer as a full backup of your internal sdcard data. Doing this while in Recovery allows you unrestricted access to your entire Internal Storage.

Disconnect phone from computer. Flash PN 20170215

Flash TWRP 3.0.2.0-RC1

Reboot to system

While starting I got the error message about having the wrong vendor image. Hit OK.

Reboot to Recovery again.

Flash the vendor image NOF26W to the Vendor partition

Reboot to System. No vendor image error message.

Reboot to Recovery again. Flash SuperSU 2.79 SR3

Reboot to System

A lot of problems I see people having are because they try to flash the wrong versions of things like SU and TWRP. It is confusing because there are multiple versions out there and multiple threads on these forums about all of them. You have to triple check that you are using the correct versions of SU and TWRP for the Pixel XL.

Also for those that have not yet unlocked their bootloader but are considering it to install this ROM. I would recommend doing so but with a word of caution. Unlocking your bootloader wipes all of your data. So backup everything any way you can before doing so. I found that out the hard way :(

This is a little off topic but, I saw someone asking about not having to enter a password or PIN or pattern in order to use the fingerprint scanner. It's not particular to PN but Android has the ability to unlock itself under certain conditions such as your location etc. That way you can wake up your phone with your fingerprint and not have to unlock it. Read about that here.

Thanks again BeansTown. I bought you a couple of six packs. You deserve it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I think people are asking about a way to use the fingerprint scanner to wake up while only using swipe for lock screen security. Which can't be done natively in android.

It doesn't register the scanner unless finger prints are present and it won't register fingerprints unless a back up is present.

Also flashing to an empty slot is technically not a clean flash since your data is still present from the previous.

It's essentially the same as not wiping data but instead wiping system and installing which could still cause issues.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rwrutl:
When I try to install the PN zip file from TWRP, it says it can't find the update binary in the META-INF directory, if anyone can advise where to look for help I would be very thankful
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Sounds like a bad download.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rwrutl:
Thanks and in the meantime I found a reference to the issue I was using twrp alpha 2 instead of RC1. I switched versions and it's good now
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Great, glad you found it!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] noidea24:
just chiming in because i saw mentions of it earlier on in the thread.

it has to deal with supersu breaking the flashlight tile.

i went through a little testing to verify my findings so everything i say can be repeated in my device.

just flashing pure nexus, the flashlight tile works fine.

flash super su (2.79 sr3), and i notice i lose flashlight tile functionality.

performed a reboot, flashlight tile becomes functional again until another app uses the led (such as camera).

after using camera with flash or any flashlight app, i have to perform a reboot, and then the tile will work again

im just mentioning my finding in case someone searches the thread with similar problems.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mac796:
I'm on pure Nexus with 2.79sr3. I tried what you're describing mine seems to go back and forth and work fine.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] thehotboy:
Hey Beans can you please add the commit to allow 2 column settings? I know DU now does this. Please and thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] icebear8:
just flashed the new vendor and the new pure rom but i kept getting a boot loop so was gonna do a clean install and now when i flash pure nexus i get a could not find "meta-inf/com/google/android/update-binary' in the zip file Error installing zip file
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
What version of TWRP are you using?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] icebear8:
i am on 3.0.2-0 alpha2 ( just flashed RC1 for twrp and still same bootloop, tried going fresh and still same thing and now i can't boot to anything.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] coldconfession13:
Christ you figured by now people would be on RC1
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] icebear8:
flashed RC1 and still same thing.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikaole:
Just fastboot boot

Fastboot flash boot_a boot.img

Fastboot flash boot_b boot.img

Than fastboot boot twrp.img

And flash rc1 in twrp
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chadwick359:
[MENTION=4395895]BeansTown106[/MENTION]: is there any chance you would consider merging the lockscreen audio visualizer from CM12+/other ROMs? Personally that feature is one of my favorite dumb phone tricks; though I haven't seen it mentioned much lately so I may be way in the minority on that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] coldconfession13:
Seems Bluetooth has issues. I'm working out and Everytime I move phone it causes skipping
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cowsquad:
You probably have a bad download or the wrong rom
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] coldconfession13:
Happens when the phone isn't moving. Seems noises makes it skip like a CD is scratched
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] M9guy:
My bluetooth works perfectly moving or still, and I"am running the latest PN and Elemental x.

I believe Beans has posted if anyone is having issues with bluetooth that it is not due to this rom.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vidfinnx:
latest radio seems to give me whacked out problems it work great for a long time on this update rom then it just develops this weird ping problem, its on a 5ghz router im using

the throughput speeds are good but the ping starts to get weird...anyone else experience stuff like this on 5ghz wifi bands?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] coldconfession13:
I'm gonna try another headset cause it doesn't happen on my car radio just headset.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nasty64:
Mine stops working every couple of days or so and I have to reboot the phone to get it to work again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] M9guy:
I think it was a few days ago that Beans posted that. Mine bluetooth works great with my kenwood car stereo and with my motorola stereo headset also.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jk8260:
Same here, sometimes just starting maps will fix it.

- PixelXL running PureNexus
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Taebom:
I haven't gotten mine to work reliably either. Went back to stock and had the same problem so maybe the new update to play services messed it up
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chadwick359:
Is anybody having luck with their visual voicemail tab in Google dialer? I've tried disabling ASOP, toggling voicemail config globally, resetting and re-entering my VM PIN on both the phone and VZW sides, to no avail. Seems to be working fine in the ASOP phone app.

Edit: My bad, missed setting Google Dialer as the default phone.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] docluv01:
I was having this problem on the last build, but after installing the latest, problem has gone away....FWIW
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Protibus:
I am not having an issue with either dialer with VVM. Make sure you disable AOSP dialer. Set Google dialer as phone app and give Google dialer all permissions.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chadwick359:
[MENTION=3223325]docluv01[/MENTION] [MENTION=4399947]Protibus[/MENTION] Well, now I feel dumb. Somehow missed getting it set as default in the Apps menu despite getting that step right last time.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] elreydenj:
Check your notification from VVM when it comes in. Even if you have Google dialer set as default the voicemail notification still comes from AOSP dialer. They look almost identical. If you freeze your AOSP dialer app then push notifications wont come from the Google dialer until you open that app. So while it isn't necessarily an issue if you have both apps active it is not working as intended. Multiple users have reported it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Protibus:
Yes that is a quirk of using the Google dialer.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 318sugarhill:
So, I flashed the TWRP image (RC1), and I flashed the TWRP zip, rebooted....all was well. Flashed the purenexus zip and then flashed the twrp zip again. First boot gave me the Android system message that my vendor image doesn't match the system.. So I flashed the NOF26W vendor image from page 75 on here. I got the Failed (remote: partition table doesn't exist) message when flashing it. I can set up the phone, but it wont recognize my sim card now.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] D0CTOR:
You need to flash the .img using the TWRP image installer and select the Vendor partition if you didn't already....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xxfwmxx:
Just to be safe I would flash it in twrp using the image flash utility and I would flash it to both slots to be safe. Won't hurt anything.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] danielson2047:
Loving this ROM! Add black stock theme with substratum and I'm in heaven.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] irule311:
I'm getting some pretty weird bugs when I try to install this rom. I started with wiping both a and b slots and flashing a factory image to slot a and booted up. Then, I booted into TWRP and installed pure nexus on slot b. When I boot into pure nexus's setup, the keyboard is missing, and only the voice keyboard is available. When I boot back to slot a with the factory image, the keyboard is also missing from there too! (It was there before I installed pure nexus and booted up)

I then did a few more experiments. I again wiped both slots and this time only installed pure nexus on slot b. When tap restart, I get an infinite vibration from TWRP until I force restart my device? This time, the keyboard did show up though.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jjayzx:
Are you trying to dual boot? If not don't mess with slots and flash stock to straighten everything up and then just follow normal procedure to install PN.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Golf c:
Sounds like your not clean flashing. Are you wiping data? Dual booting two different roms with the same data equals problems.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] irule311:
Yep. Ive read that some people have stock on one slot passing safetynet and pn on another. I don't know what's going on since I've wiped everything and flashed the factory image multiple times. This is a brand new device.

---------- Post added at 07:15 PM ---------- Previous post was at 07:12 PM ----------

Yes. I've wiped everything in twrp using advanced wipe and selecting everything. I then booted to bootloader and flashed factory image (booted but didn't setup anything). Then back to twrp and flashed pn and I get the keyboard glitch. Recommendations on how to dual boot?