yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Yup go to settings, notifications then the gear icon on top.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Protibus:
Update: found Google Exchange Services on apk mirror. Fixed setting up Exchange active sync accounts.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sn0warmy:
Problem solved. Thanks!!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
Anyone else's flashlight not working?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Custom kernel? Probably incompatible with Jan update.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
Nope I was 100% before flashing this. I haven't even rooted or installed twrp until 20 min ago when I flashed this ROM. Back to stock I guess. I wiped data before I don't know if flashing again would make a difference
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Fool proof guide for those still confused on process. Everything up and running perfectly well.

TWRP = RC1

SuperSU = 2.79 SR1 or SR2

'*' = Optional

1)* flash-all 26U or 26V (w/o '-w')

2)* fastboot boot TWRP

3)* TWRP Install TWRP

4)* TWRP backup (boot, system img, vendor img, data)

5) TWRP wipe data factory reset

6) TWRP flash PN

7) TWRP flash TWRP

8) reboot recovery

9) TWRP flash NMF26V vendor img

10) Boot to OS -> complete initial setup

11)* TWRP flash SuperSU

12)* TiBu restore (all user apps)

Don't bother reporting back issues if you aren't using TWRP and SuperSU mentioned above, or if you skipped any non-optional steps, or if you performed any steps out of order.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Thats pretty good, but your still on an old bootloader and radio. (Radio didn't change this time, bootloader did change). I flash the new bootloader, radio and vendor to both slots so both slots are the same. Factory images only flash those to the active slot. The inactive slot keeps the previous BL, radio and vendor.

Edit:Boot image also applies to the above but the rom overwrites it anyway.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Chronzy:
He's on the current BL and radio if he flashed-all, correct?

Why do you need it flashed to the inactive slot? I always make sure I'm on a in twrp and that's it.

These steps are spot on, more detailed than what I post.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
I followed his same steps. When you flash a custom rom it switches to the inactive slot. (Now active) I had the previous bootloader and vendor. Flashing factory images only flashes the active slot and system_other image to the inactive slot. The rom switched slots and I had all the old partitions. So after flash all I would add manually flashing boot, bootloader, vendor and radio to the inactive slot. (Assuming they change from month to month) Which they don't always do.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
[MENTION=4395895]BeansTown106[/MENTION] First issue: can't get notification led to work. Anyone else? Using PN led settings, not in-app settings.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Your steps are perfectly fine if you don't ever plan on dual-booting.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
He's still on the old bootloader. Just for clarification. Lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
But his point was that he's satisfied with running a ROM in slot b all the time. He wrote that he makes sure he's always in a in TWRP. I'm saying he doesn't care what boot, radio he has in a.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Chronzy:
Sorry, your right. Forgot it switched slots for custom roms. Stupid pixel so confusing lol.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] unhappybirthday:
In the meantime, you should be able to add them yourself with Custom Navigation Bar.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] koreyb:
So to get root on this latest version do I need to flash an older factory image/older version of ROM, root, then install this latest version?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
If you're talking about the June build, I just flashed ElementalX/Patched version of Magisk just like previous builds, using TWRP RC2. You don't even have to flash boot signer anymore.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] koreyb:
Yeah I'm talking about the latest build. After I read your post I flashed a "Magisk-v12.0-Pixel.zip" I had downloaded (don't remember where I downloaded from or for what haha) but it gave me an error: 1. Is there a link you could point me to for the one you're using? Appreciate man.

Edit: Do you mean flash it with ElementalX?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
No, i mean install ElementalX first, I'm using 1.13 on the June security based PN...and don't forget you have to flash TWRP again after doing all of this, and make sure you have slot straight for ROM vs Kernel/Magisk installation.

My Magisk filename is the same as yours, for whatever that's worth. Your error may be due to flashing with TWRP 3.0.2 RC1 rather than 3.1.0 RC2.

I'll see if I can find the Magisk link, it's from goodwin_c like all the Pixel builds...think it was this one: https://xdaforums.com/showpost.php?p=71727728&postcount=1189

Also to fix SafetyNet you need to run this via terminal after each reboot now:

su

resetprop --delete init.svc.magisk_pfs

resetprop --delete init.svc.magisk_pfsd

resetprop --delete init.svc.magisk_service

resetprop --delete persist.magisk.hide

resetprop --delete persist.magisk.busybox

resetprop --delete magisk.version

Magisk Manager acts a little funny but I still have functioning root apps and Android Pay works.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] creeve4:
Yep, that's what I've done, but it's nice to only have them when I'm using the keyboard.

---------- Post added at 09:56 PM ---------- Previous post was at 09:16 PM ----------

Is ambient display supposed to pulse on and off every few minutes when there is a notification?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Chocobubba:
Does this rom always install to the inactive slot?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
Yes, this is so if a system update fails it can boot back up into the old system, even works on custom ROMs. :p
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
You can also set up one slot with Magisk, and one without.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] koreyb:
Thanks for your time. I'm by no means to flashing but the pixel is like a completely different animal compared to phones I've used in the past. I'm still ignorant to the whole slot thing. When you said to make sure I have the slot straight, I assume you mean ROM/ Kernel on one slot and Magisk on the other? I just did everything from [my] memory and not paying attention to the slots everything seemed to work but magisk kept causing Settings to FC when I tried to open it. I forgot to flash the kernel though so I hoping that was issue. Bout to give it another shot. Thanks again.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
When you flash a ROM, and i think also things like GApps and vendor image, using TWRP, it flashes the inactive slot. When you flash kernels, Magisk, etc, it flashes the active slot. TWRP flashes both, always, I think.

Hope that helps. Also hope someone can confirm or correct re GApps and vendor image.

Also, happy to help. Believe it or not, Pixel was my first Android device. Easier and also harder, it seems.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
I've never flashed gapps (or needed to) on this device, but vendor img is flashed to current slot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nil253259:
Not really, only ROM gets flashed in inactive slot. Everything else does in the active slot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
If I had to do this after every reboot, I would just stick to my landline....damn
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Obaterista93:
Now, I'm by no means an expert and I haven't used it in forever, but couldn't you put that into a batch script and have tasker run it on every boot? That'd definitely save some time in the long run.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
Yep. You can also put it in an init script that runs automatically at boot. I'm doing mine manually because I'm hoping an official Pixel version of Magisk v13 is coming soon so I won't have to worry about it for long.

Also, I have only had to reboot maybe every couple of weeks. If Magisk ever gets to the point that it's too much of a pain to get SafetyNet working, I am planning to go back to a dual boot setup with one slot not having root access, so that I can still use Android Pay, etc. I set that up on the May build but Magisk was working so we'll I never switched between slots, so when I flashed June I just set both slots identically.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] rohitece06:
Magisk has been fixed btw https://www.xda-developers.com/unof...-the-pixel-and-pixel-xl-get-dedicated-thread/
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nuwan32:
Thanks for this awesome ROM! Just got my pixel and flashed this. Gonna give it a try and will report back :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jidccruz:
Is this still the updated installation instruction? Because I cannot install the the ROM and no root as well.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nuwan32:
I did this yesterday and worked fine.

Boot twrp via fastboot, flash twrp, flash ROM, flash vendor image, boot into rom, reboot recovery, flash supersu.

Btw, I'm trying to get the notification light to work, but it just wont show. The setting is not available in Settings>Notification>Settings and even installing lightflow didn't help. Any ideas?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
Settings - purenexus settings - display - notification light
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jidccruz:
Thanks bro. Now its working! Boot twrp via fastboot, flash twrp, wipe data, flash ROM, flash superSU v82, flash verifiedbootsigner v8. Now everything works!

One question tho, no need to flash beans gapps?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Gapps are packaged within the ROM zip for now (and possibly indefinitely)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nuwan32:
Thank you so much! I thought i was going crazy because I couldn't find it. It should be enabled by default :/
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
No, problem ?

A lot of people like choice, I actually like the fact you have to enable it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
Why is this? What's preventing the ROM from working without gapps being built in, other Pixel ROMs do just fine without gapps.. :confused:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
¯\_(ツ)_/¯
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
Seems legit.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] rohitece06:
[MENTION=4395895]BeansTown106[/MENTION] any plan to integrate automated high-brightness and wakelock blocker in this rom? For a reference you can look at pixeldust.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BeansTown106:
will definetly look into these for O, supposedly O will be dropping within a few weeks so i dont plan on doing much in terms of features til then just security and fixs
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BeansTown106:
Okay guys the time is here, PureNexus update Based on July Security patch!!

A few things to note,

1. kernels have been upstreamed to the latest Stable linux branch

2. with O right around the corner adding new features has been paused while we prepare for the newest android version, only fixs and security updates til O

3. I have been sick the past few weeks so i didnt get a chance to get the update out in a timely manney :( so sorry for the delay

ok, Lets get to the goodies!!

07/25 PureNexus sailfish Update is Live!!!

Download Link: https://www.androidfilehost.com/?fid=817550096634788628

Vendor image: https://www.androidfilehost.com/?fid=745425885120746499

Dont forget to check the Changelog!!

As always if you like my work dont forget to hit that thanks button.

Donations are always appreciated but never required, I am only posting the link for convenience, Donate link
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jidccruz:
Thanks so much! Question tho, if I flash the updated ROM do I still need to flash TWRP again?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mnrivera210:
Yes.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shinesthru:
Hope you are feeling better, and thanks for sharing your work. [emoji111] [emoji106]
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nathanchance:
I want to take a moment and explain a bit about the kernel upstreaming in the latest release, in case you guys didn't see my post on Google+, since it's a pretty big deal.

The primary reason for doing this is bug fixes and security patches ahead of Google. Most if not all bug or CVE fixes are pushed to Linux mainline where they are then added or backported to a stable tree. This fixes are important as they are only allowed under these circumstances. They are stable.

Now I have gotten flack or scoffed at by several developers for this for a few reasons which I will (try to) debunk now:

1. Linux upstream causes instability

This CAN be true, if your upstream merge is done improperly. But this is also the case with something like a Google security update; any time there are conflicts, there is a risk that you may do a mismerge and cause instability. If you are smart and confident in your ability to look at code and understand the context (which I am), you will have no issues with this. Furthermore, I always recommend people go version by version, testing to make sure nothing breaks. There is only one commit in 3.10 that I know for sure breaks something and it is not even needed due to the way Qualcomm chips are setup. Same thing with 3.18.

2. We don't use 99.9% of upstream commits

Just yesterday a developer said this, which is completely and utterly inaccurate. Almost every single version has at least a few commits that are relevant to us. Just in the last few versions of 3.10 and 3.18 there have been SEVERAL CVE fixes, mostly to the networking stack, bugs that have been present since 2007. While I will concede a lot of the patches aren't relevant to us, they aren't going to do anything if they are in the source. It's very easy to do upstream on top of stock source then add your custom modifications on top of it so you don't get overwhelmed (that's what I do). I can go through and probably pick out at least 5-10 CVEs that are patched in upstream but not Google's source.

3. You'll never feel a difference

This is pretty much true; you won't. However, that's not the point. Most if not all of these fixes are to certain subsystems that don't impact performance, like ext4, filesystems, sound, networking, arm64, etc. These are to prevent vulnerabilities and prevent crashes or oops. Not all problems are a user visible issue. The kernel is massive and may be experiencing internal issues without you realizing it.

Ultimately, I don't want people to buy into the notion that upstreaming isn't important; it is. It's taking relevant bug fixes from paying companies for free (even though they may not have a visible user impact but it's rare that any kernel patch does). If a kernel developer doesn't want to do this, it's usually because they don't have the time or are lazy, which I disagree with. This is about security and the user experience, it's worth the time to do as I did.

Do realize if your custom kernel isn't upstreamed, you are losing out on this.

More reading: https://xdaforums.com/android/software-hacking/reference-how-to-upstream-android-kernel-t3626913
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Awesome, you answered my question and more without asking. Thanks.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JAYNO20:
This can be dirty flashed over a previous release?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] rohitece06:
[MENTION=4395895]BeansTown106[/MENTION] apparently the "Block/Report Spam" option is gone from the dialer (did google dialer removed it?)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] usman14:
Just did that no problems
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JAYNO20:
I'm noticing the same thing. Had it on the June release and now it's gone.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
The changelog notes going back to stock dialer, contacts, calculator. June patch says they were changed to AOSP. Guessing this is why?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JAYNO20:
That shouldn't be why. I've had this option since I first got the phone and was completely stock. The AOSP dialer is a completely different app.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JAYNO20:
Fix posted here:

https://xdaforums.com/pixel-xl/development/rom-pure-nexus-substratum-fi-wifi-t3533539/page454
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Anthony2oo5:
Hi, thanks for the update.

"Transfer Files" dosnt seem to work anymore for me?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] hochoch:
I had this issue the other day. You have to go into the app info screen for the phone then towards the bottom there's an option to set it as default phone. It should then work. Have not tried on July release tho.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] rohitece06:
That worked. Thank you very much. BTW I like AOSP dialer's large photo call screen. I wish [MENTION=4395895]BeansTown106[/MENTION] can give AOSP dialer as an option in this ROM.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JAYNO20:
Already posted above. :good:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Slomies:
What are the steps to dirty flash? I usually do a clean install but I'm feeling lazy tonight ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JAYNO20:
Same here...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
For each PN update:

I just boot recovery (TWRP), clear dalvik and flash the new ROM, then switch slots, flash vendor.img, reflash ElementalX Kernel, Magisk, TWRP. Works great.

This last time I had to flash kernel and Magisk twice for some reason to get them to take.

I should test to see if PN kernel works with Magisk and lets safety net work with unlocked bootloader, as that's the main reason for me using it. Upstreamed kernel would be great.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
Your really wasting your time clearing dalvik, as it don't even exist

On devices that support seamless updates [Google Pixels], Android basically slipstreams OTAs as it writes the updated partitions, meaning that it can merge in changes without first creating copies. An advantage of this system is that it does away with the need for a dedicated /cache partition. It does not exist on the new Pixel phones and isn't likely to appear on future devices supporting seamless updates.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jidccruz:
Yes. Did it. No issues at all.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piccit:
That's true of "cache."

"Dalvik" still exists, it's '/data/dalvik-cache'
[Google Pixel ROMs, Kernels, Recoveries, & Other De] rm501:
Hi

Could you please point me to link for the latest Magisk binaries for Pixel?

Thank you
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
Sure, you can do that manually with root with a file manager, in TWRP it will give you a warning in red and the contents are still there, that was during my testing when TWRP came out for the pixel, maybe things have changed since then.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] danaff37:
Perhaps related to the people unable to connect to PC - my Android auto (also through USB) is no longer working on the latest update. Going to try a different kennel this afternoon.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
The official unofficial build thread is over in the Magisk forum.

I'm running 13.3b4 with Manager version 5.1.1. I was having problems getting the June PN build to show as certified for the Play Store. I don't know if it was just because I installed the July update, or something else I did while upgrading (like clear dalvik), but everything is perfect now. Safety Net passes, Play Store certifies, root works. It's great.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JAYNO20:
Let us know if it works... Are you using supersu or magisk?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] just_visiting:
Deleted.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JAYNO20:
I just installed EX kernel and that DOES indeed fix the "transfer files" issue so it must be an issue with the kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Well flashed the latest PN, flashed twrp rc2, rebooted to recovery

Installed supersu and EX kernal

Proper reboot

Forgot to flash vendor so did a reboot, selected recovery but it just hangs and sends me to the ram dump screen each time I try to access recovery.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
You should let PN boot once after flashing the PN zip and twrp zip. Then you can flash supersu, reboot again, and then flash ElementalX
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Thanks will fix it up later by using ADB to boot into Twrp and flash it again
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TheBurgh:
Are you rebooting to system or back to recover before flashing ElementalX?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
To system, so that supersu can do it's bootloop installation so that when you go back to recovery to flash ElementalX you will have all of the aroma installation options [emoji106]
[Google Pixel ROMs, Kernels, Recoveries, & Other De] danaff37:
Fixed Android auto as well.

I am ok magisk, and everything is running great now.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nathanchance:
I will be looking into the transfer files issue in a couple of hours, please message me if you are willing to test this with me.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Nate are you going to release the kernel by itself or only up to devs to include in Roms?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nathanchance:
I guess I can release it on its own if there is a demand for it. Just need to fix this issue :(
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kingkong0821:
Haven't been flashing stuffs for a month

Just find out that i cannot boot into bootloader or recovery

It boot straight forward to system

Don't know what is causing this, any idea?

Edit: Tried power off the phone then power+ volume down and it worked
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aditya_g8:
I am also looking for the same.

[MENTION=4395895]BeansTown106[/MENTION] can you please explain for this ROM how did you manage to get Project Fi working.

I want to use /port a different rom. Can you please provide a little information, for adding project fi support to an AOSP based rom. (Mainly copper head).

Edit: I guess I have to use the radio, and some config files from my existing device. I can extract them, but can you give a little bit of a guide/list of files & configurations I need to save. Thanks in advance.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I am able to enable it on Verizon so I'm pretty sure it works on Fi.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aditya_g8:
Hi, the question is more geared towards fixing WiFi calling and network switching on Fi, between T-Mobile and Sprint. I don't think if Verizon works Fi would work. Is there something I am missing, which makes this obvious?