yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Most likely was the build, the Updater app is pretty useful but still experimental. I'd use it more but I get tired having to constantly use fastboot to boot TWRP so I can reinstall it.

As for AVRCP, it's working fine for me on 20170512: http://i.imgur.com/zjdDBeO.png

I'm going to try testing it with my head unit in the car when I get the time.

I've been continuing my work, crafting yet another flashable ZIP. This one will enable use of the WiFi Assistant VPN, and it installs Google Connectivity Services to /system/priv-app to do so. I haven't tested whether or not the function works, but the settings do show up under the WiFi settings and under Google -> Networking in the Settings app. This one has the same limitation as the Pixel Launcher flashable in that your device's active slot has to be the same as the one the ROM is installed on. This means that you can't flash it at the same time you do the ROM, you'll have to do it after a reboot when the active slots are switched. I've been trying to fix this but I've hit a roadblock right now. You'll also have to flash the ZIP again after doing an A/B update or flashing the ROM. You'll still pass SafetyNet checks after flashing it.

File is attached below and I recommend uninstalling Google Connectivity Services if you installed it from the Play Store.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Why can't you just download the wifi enabler from the play store or apkmirror and drop it in the system/app folder yourself?

Is this just for convenience or am I missing something.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Convenience. Just one flick and you don't have to deal with the process. Can do it before you boot the ROM. If you don't have root enabled then this is certainly better than trying to use the file manager in TWRP.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Curious. I always drop files into system/app, what's the difference between that and system/priv-app?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Apps in priv-app are privileged applications that are granted almost all their permissions and if they are signed they are allowed system permissions that can give them the ability to do more things with the OS. Being a privileged application allows the Pixel Launcher to integrate Google Now into it, and allows GCS to access hooks that can expose settings to enable WiFi Assistant in the Settings app.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
So I've been dropping my apps in system/app and the pixel launcher for example still has the swipe functionality and weather. Is there something else I am missing?

Is dropping the apps in either folder and a reboot enough or should I chmod them?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] trashmaster76:
[MENTION=2385005]invisiblek[/MENTION] How did you made the updater and the downloads page
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Hmm so I guess my source was wrong on the Pixel Launcher needing to be a privileged app unless something has changed since release of it. GCS still needs to be a privileged app though to allow enabling the WiFi Assistant. Generally it's best to follow Google on where they put apps on stock for best compatibility and features. List of priv-apps here:

[LIST]
[*]AppDirectedSMSService
[*] BackupRestoreConfirmation
[*] BlockedNumberProvider
[*] CalendarProvider
[*] CallLogBackup
[*] CarrierEntitlement
[*] CarrierServices
[*] CellBroadcastReceiver
[*] CNEService
[*] ConfigUpdater
[*] ConnMetrics
[*] ConnMO
[*] ContactsProvider
[*] CtsShimPrivPrebuilt
[*] DCMO
[*] DefaultContainerService
[*] DiagMon
[*] DMService
[*] DocumentsUI
[*] DownloadProvider
[*] EmergencyInfo
[*] ExternalStorageProvider
[*] FusedLocation
[*] GCS
[*] GmsCoreSetupPrebuilt
[*] GoogleBackupTransport
[*] GoogleCarrierConfig
[*] GoogleContacts
[*] GoogleDialer
[*] GoogleExtServices
[*] GoogleFeedback
[*] GoogleLoginService
[*] GoogleOneTimeInitializer
[*] GooglePackageInstaller
[*] GooglePartnerSetup
[*] GoogleServicesFramework
[*] HelpRtcPrebuilt
[*] HotwordEnrollment
[*] InputDevices
[*] LLKAgent
[*] ManagedProvisioning
[*] MediaProvider
[*] MmsService
[*] MtpDocumentsProvider
[*] MusicFX
[*] NexusLauncherPrebuilt
[*] OBDM_Permissions
[*] obdm_stub
[*] OemDmTrigger
[*] OobConfig
[*] Phonesky
[*] PrebuiltGmsCore
[*] ProxyHandler
[*] qcrilmsgtunnel
[*] RetailDemo
[*] SettingsGoogle
[*] SettingsProvider
[*] SetupWizard
[*] SharedStorageBackup
[*] Shell
[*] Showcase
[*] SprintDM
[*] SprintHM
[*] StatementService
[*] StorageManagerGoogle
[*] SystemUIGoogle
[*] TagGoogle
[*] Telecom
[*] TelephonyProvider
[*] TeleService
[*] Turbo
[*] Velvet
[*] VpnDialogs
[*] VZWAPNService
[*] VZWAVS
[*] VzwLcSilent
[*] VzwOmaTrigger
[*] WfcActivation
[/LIST]

As for permissions it's best to do 0755 for the folder and 0644 for the APK. Usually you can get away with not setting the permissions but sometimes if the permissions are really messed up then the app won't show up.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bobbarker2:
1. So your first step was to flash the factory zip?

2. Did you remove the -w from the bat or leave it in?

3. Flashing the opposite of active, I assume you mean in fastboot? flash boot boot.img/vendor vendor.img?

4. Boot into TWRP mean fastboot boot twrp.img?

5. We don't wipe system for this or flash the TWRP.zip?

Very peculiar process.. Not sure why you'd need to flash the opposite boot/vendor since using a factory zip will flash to both slots.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Factory doesnt fully flash to both slots. For instance I flashed a factory image when we went to 7.1.2 and only one slot has the updated splash screen that says Powered by Android.

The way I see it, it would be redundant to flash everything mirrored since a user using the phone how its intended won't under normal circumstances swap slots. Once they get an update it will install on the inactive slot and upon the next reboot the phone swaps to that slot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Yep, flash the N2G47O factory image to get your device clean and set up for the ROM.

I leave the wipe argument in because I don't carry any large amount of data and I've gotten to the point where I can install all my regularly used apps and punch in my settings on a fresh device in under 30 minutes. Really you don't need to do this, but I do it because I like having a completely clean slate.

Flashing the opposite of the active slot (I'll refer to 'inactive slot' now, which is more precise) is needed for only boot and vendor because fastboot update will only flash to the active slot (except for the system slots). So if you are currently on slot A, fastboot update will flash all the images to slot A (except system which will also flash to system_b). Flashing the inactive slots of boot and vendor are required because when you boot into TWRP to install the ROM it will flash to the inactive slot because it's basically doing an A/B update. This means that the ROM will be flashing to the B slots in this case. The B slots could have old boot or vendor partitions which are sometimes why people will get the outdated vendor partition warning even though they flashed the appropriate build. The reason why this happens is say you are on build N123 with an active slot of B. You then take an A/B update to N234 which applies to the A slot. The A slot is then set as the active slot and build N123 is left alone on the B slot and set as inactive. You then want to flash this ROM and do so in TWRP. The ROM uses the A/B update system so it'll install to the B slot now. This can be a problem because the vendor partition is for build N123, and the ROM uses N234's vendor partition, so you can end up with a ROM that doesn't boot or gives you the warning. This is mainly a precaution, it's to COMPLETELY set up the device for the ROM so if you even take any A/B updates for the ROM you won't have incompatibilities. There aren't commands for specifically flashing to the inactive slot, so just peek at the active slot in the bootloader (say A) and then run

fastboot flash boot_b boot.img

and

fastboot flash vendor_b vendor.img

.

Substitute "b" for "a" if the active slot is B.

When I refer to "boot to TWRP" I do mean

fastboot boot TWRP.img

Wiping system for this ROM is not necessary. You can flash the TWRP installer (do so after the ROM), you just need to go to the Reboot menu in TWRP and set the set the inactive slot as the active slot (basically swap them). You'll then need to use VerifiedBootSigner_v3 from Chainfire after flashing the TWRP installer. Before flashing VerifiedBootSigner I suggest flashing it just on it's own to make sure that it works, it won't do anything bad, it'll just detect that the current image is signed and quit, letting you know it works. After testing you can then flash TWRP and the signer.

Yeah the process is a bit convoluted, but it's that way because the A/B slot system throws everything in for a loop and the conventional way of doing things don't apply to the Pixel devices.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] admiralspeedy:
I've been fooling around trying to run my own unofficial builds of Lineage for the Pixel XL and I noticed that running a totally unmodified and clean build, the default Gallery app causes the phone to totally freeze and reboot when you switch between tabs (it happens almost every time I try but you kind of have to flip between the tabs quickly to get it to crash). I cannot figure out which change is causing this to happen, since it doesn't happen on Invisiblek's May 12th build, and the only marlin specific change that happened after the May 12th build was regarding sdcardfs, which after doing some research, is related to Gallery crashing on the Nexus 5X forever ago.

However, I reverted this commit in my local branch and rebuilt, but it still crashes.

EDIT: So, you don't even have to switch tabs for it to reboot the phone. In addition to that, it doesn't seem to throw any errors in logcat.

EDIT 2: I'm not sure why it worked this time, but I did another totally clean build with the sdcardfs commit reverted again (which has now been reverted officially and awaiting approval) and everything is working fine.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Just discovered a bug in the Expanded Desktop feature. It was discovered in my search for why my phone wasn't entering deep sleep when it should, and why the little cores would max out the clocks when the device is locked. If you enable the system-wide hiding of the navigation bar, your logcat will be spammed with

[COLOR="DarkOrange"]W/WindowManager( 1392): Layout repeat skipped after too many iterations
W/WindowManager( 1392): Layout repeat skipped after too many iterations
W/WindowManager( 1392): Layout repeat skipped after too many iterations
W/WindowManager( 1392): Layout repeat skipped after too many iterations
W/WindowManager( 1392): Layout repeat skipped after too many iterations
W/WindowManager( 1392): Layout repeat skipped after too many iterations[/COLOR]
[COLOR="Red"]E/WindowManager( 1392): Performed 6 layouts in a row. Skipping[/COLOR]

at a rate of about every other millisecond when you lock your device. It seems that the lock screen apparently does not like the navigation bar being hidden and as a result you get this. So far system-wide hiding of only the status bar seems to be OK, and choosing to hide the navigation bar on a per-app basis seems to be OK as well. This bug will also happen if you use the ADB command to hide the navigation bar or use an app like Tiles.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Did you say you did have a zip that could enable wifi assistant VPN in settings?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Attached to this post https://xdaforums.com/showpost.php?p=72275533&postcount=57

Make sure to clear the data and cache for the app and uninstall it before hand if you have installed it as a user app.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jayvijay Gohil:
Does this ROM pass safetynet with unlocked bootloader and Magisk root? Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TheGreatB:
Does Daydream (split screen in Unity-based apps) work on this ROM? I want to fix it on other device's LOS builds but it has proven quite hard.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jayvijay Gohil:
Anyone?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
I'm going to assume yes. It passes without Magisk or root.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] blaze9090:
Anyone got v4a working on this rom?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CZ Eddie:
Google Camera is working beautifully. Thanks! :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Try this https://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mlin:
Curious, did this mean the 30fps camcorder issue is resolved?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CZ Eddie:
yep
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mlin:
Awesome! Time to jump in.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] robotnikz:
Are wie going to get some builds without gapps baked in? I am not using Google things.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] KeithGS:
Having issues with my boot, sitting at the logo, flashed from twrp, not coming back..any idea what could be going on? Pixel XL, I have also notice recovery goes back to stock... network: verizon
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] blaze9090:
Flash verified Boot after twrp!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] KeithGS:
Figured it out, if you're running Verizon, be sure to use 7.1.2 (N2G47O, May 2017) vendor.img can be found in many threads here, or directly from google in their factory zips: developers.google. com/android/images#marlin Google XL seems to be the only affected, not sure about sailfish.. 1. Flash the ROM -> 2. Flash the vendor image, 3. flash twrp again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
What issue are you talking about?

Also if you flash the rom and vendor without rebooting you will likely need to flash the vendor again since the vendor flashes to the active slot and the rom flashes to the inactive slot (which becomes the active slot on next boot)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jkashuba07:
Any intention to support Substratum? When opening up it comes up Legacy.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AerialSlckr:
Does Google Assistant work in this? It said no data when I was first loading it up.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yung40oz84:
Lineage never supported substratum, it would have to be built in unofficially by the maintainer of this thread if he so chose to add and support it, it can be done though as it already has many times.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fracman:
Just read cmte was merged with lineage.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yung40oz84:
Where'd you see that, I just looked at their Gerrit?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fracman:
Saw it listed on g plus with a link showing a merge in gerritt. Trying to find the post.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CZ Eddie:
CMTE?!? I read not long ago that Lineage decided to ditch CMTE in favor of Substratrum for Nougat and beyond. I think it was an XDA news article.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rockingondrums:
Wasn't this (30 fps video recording) the last bug with LOS? Everything in the core os works now?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reechings:
Not sure if anyone has confirmed lately if their unlimited Google photos storage is actually staying unlimited if they check their usage through Google account settings.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] robotnikz:
Hello,

is it possible to make this rom without gapps just like OctOS for sailfish?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] brangalm:
FINALLY got this working on my Pixel XL!

This A/B stuff is very annoying and confusing. (I haven't been keeping up really, I was running stock from October.)

Just one issue though - when I leave my phone plugged in for long periods (eg overnight), when I check it in the morning, it's bootlooping at the lineage boot screen. I have to turn off the phone, restart it, and then it works fine. Any suggestions?

Otherwise running this with the June update and Magisk v12 (couldn't get superSU to work).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] brangalm:
Well that's too bad. I'm still having some issues and unfortunately I'm out of time for experimenting this weekend - need to go back to stock :(

My downloads weren't working (for example, in Dropbox I couldn't open any files or export them), sometimes I would get some random crashes, and sometimes when rebooting it would get stuck booting into recovery (even though I selected system) and would need to boot into the inactive slot then reboot again into the active slot in order to boot properly. Just too many issues for me for now. Maybe I'll come back in a few weeks :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rockingondrums:
Well dang it. I need that.

I also did a quick search plus on XDA app but did not find an answer: is Netflix still blocking unlocked bootloaders? Or has someone made a workaround for it yet?

Oh yeah, does cloud restore during initial setup work?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
The ROM defeats SafetyNet so you'll be fine. Cloud restore does not work yet.

Haven't had any random crashes in the month I've been using the ROM. A few days ago on the 20170609 build I did have it where rebooting ended up trapping me in TWRP, and another where it would fail to boot and I would end up on the other slot. Haven't had that happen again though.

Haven't ever come across the phone rebooting and then bootlooping. I would say that Magisk was the problem.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rockingondrums:
Cool. What about the USB transfer restore?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] admiralspeedy:
It's working on my ROM but it never worked for me on this one.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] thewavelength:
I still only get an endless boot animation with using build from 07-06. I was on N2G47O as [MENTION=5689426]Namelesswonder[/MENTION] said it has to be.

Any ideas?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
The ROM updates as the security updates from Google are released each month. Builds 20170607 to 20170705 are based on NJH47B, while builds 20170706 and onward are going to be based on NJH47D (until the next security update). You're using a outdated firmware version and need to flash NJH47D if you want to use 20170706. When downloading the nightlies check the changelog provided on the build and see what firmware build the latest "marlin: update fingerprint" commit says. Usually the ROM will require the latest firmware builds the day of or at most a couple days after they are released.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] thewavelength:
[MENTION=5689426]Namelesswonder[/MENTION], thanks for explaining. This makes sense, of course. Sadly, I still get an endless boot animation with 07-06 build and NJH47D.

Here is what I did exactly:

1. Flashing NJH47D

2. Booting it once, skip everything possible in the setup

3. Enabled Developer Options / USB Debugging

4. Bootet into bootloader

5. Fastboot TWRP

6. Install TWRP and Lineage 07-06 build via TWRP

7. Clean cache/dalvik

8. Boot into system

Here I get the endless animation and my phone heats up.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Don't you need to flash twrp after the rom?

Also should you be factory resetting as well? Or is this a dirty flash?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] thewavelength:
I now tried it this way, too, same result.

Factory reset is done automatically when flashing Google Pixel Stock ROM.

I also tried to use the build from 07-04 using NJH47B, but does not work either.

Sad!

[MENTION=5689426]Namelesswonder[/MENTION], I also don't find an option to select between Slot A and B. TWRP just does "magic things" and that's it. No way to modify that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
You can swap slots in twrp in the reboot menu, once you choose the slot you need to reboot.

Alternatively you can do it from the bootloader using the command

fastboot --set-active=a or b
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] thewavelength:
Thanks!

I finally found the problem: wiping cache/data after flashing was the problem. When I do it before, it just works. Great! Thank you both!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yosu8282:
Hi [MENTION=5689426]Namelesswonder[/MENTION],

Have you found a solution or workaround for this bug? Im having the same after going inmersive.

I think that if all recents apps are cleared before the device is locked there is no battery drain.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hanakon:
On flashing Sailfish Lineage-14.1-20170713 latest nightly available at time of posting on my Sailfish Pixel, I'm getting an error "A vendor image mismatch has been detected...ensure you are on NJH47D" and my SIM card can no longer be detected. Here is my exact installation process:

1) Factory data reset everything, including userdata

2) Installed latest sailfish-NJH47D from https://developers.google.com/android/images via flash-all.bat including wipe

3) Booted system, completed basic setup skipping as much as possible, allowed installation to finish

4) Booted bootloader, fastboot latest image TWRP-RC1.img, installed latest zip TWRP 3.0.2 RC2

5) Rebooted system

6) Rebooted recovery, flashed lineage-14.1-20170713-UNOFFICIAL-sailfish

What am I missing? Thanks for any help.

EDIT- Nevermind, I just tried repeating the entire process for a third time, changing literally exactly nothing, and for no apparently reason it worked without any issues at all this time. :/
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
That's because you did a factory reset to only one slot. The ROM installs to the other slot on your phone, so you may have updated the firmware on slot A, but when you install the ROM it will install to slot B which could have an old firmware on it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hanakon:
I see, so for next time should I factory reset and flash the ROM onto both slots?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hanakon:
Sorry for the double post but this is on an (possibly) unrelated issue.

While I can now get Lineage working fine, I can't get root access going. I've tried both the root access addon offered by Lineage for ARM64, and SuperSU (which is what I was using with stock with no issues). I've also tried every possible combination of installing via fastboot boot TWRP RC1 or flashed TWRP RC2. I'm wondering if this is also a slot issue; has anyone gotten root working with Lineage on their Pixel Sailfish? Again, when I was doing stock Security Patch updates, I would just flash SuperSU via TWRP RC2 with no issues, didn't need to do anything with slots.

As it is now, I'll have Lineage working fine, with or without TWRP RC2 flashed into the recovery as well. In either case, and weather I flash SuperSU 2.82 stable via booted RC1 or flashed RC2, and whether or not I use VerifiedBootSigner V8 thereafter, I get one successful boot with SuperSU working just fine, but as soon as I restart my phone (even having done nothing), I get loops and ramdumps until I flash Lineage again.

Thanks again for any help on this.