yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
So, I've been running the ROM for over 3 days now and I've got to say that it has been great so far. Currently using 20170508 right now, and it's all good.

Have disabled all the AOSP apps and have installed all the Google apps from the Play Store to replace them. Everything is almost the way it is on stock.

Had to install the live data wallpapers, and install the Pixel launcher as a system app to get the Now feed integration, but so far it's been like stock but with all the extra features I've wanted. Even installed the AptX codecs, and my phone still passes SafetyNet.

So far the only downsides I've seen are that Google Camera crashes upon taking a second video, haven't gotten WiFi assistant to work yet, and my phone gets a bit toasty playing music but I'm pretty sure that it is GPM being stupid again and not the ROM. But overall it has been an excellent experience.

The updater has worked just fine for me, taking me from 20170506 to 07 without TWRP installed and from 07 to 08 when I had TWRP installed. Don't if 08 to 09 is broken right now so I need to test.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CZ Eddie:
Yes, I was aware of that "fix". And it's already merged.

But it does not work.

Google Camera 30fps video still crashes.

I was just letting him know the fix he was told about does not work.

The fix being to remove FFMPEG from /system/etc/media_codecs.

I even tried deleting the media_FFMPG file and duplicating at /system_root/etc/.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jasonsamms666:
I read that theme engine is a dead project. Is there oms commits?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] trashmaster76:
No. If you want Substratum without Andromeda ($1,99), you must have root.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jasonsamms666:
I have Andromeda. And if it works with either Andromeda or root there are oms commits.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] banciii:
https://review.lineageos.org/#/c/193486/

Does it mean something good for us?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
Yes Oreo bringup has started
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] markgnarza:
tried to flash this ROM on my 8.0 Pixel XL, got stuck in a bootloop, never gets past the Google splash screen. any ideas?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jackaroop:
Flash a Nougat factory image before you try to leave Oreo.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] markgnarza:
ok! flash-all or just the vendor?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jackaroop:
Flash all. Your problem occured because you essentially tried to flash from Oreo down to a Nougat Rom.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] markgnarza:
makes sense, thank you! this explains similar issues I've had with other Nougat ROMs, appreciate it!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] invisiblek:
Just a heads up everyone, my Pixel (Verizon-branded) had its wifi chip go out and I had to warranty it. Naturally they sent me an updated Verizon-branded Pixel (no bootloader unlock for it), so I'm out of the game for the foreseeable future. :(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Hopefully something good happens along the way, best of luck.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dictionary:
That's a huge blow to the community. :(. Hopefully something turns up for you guys n gals on VZW
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jasonsamms666:
That sucks man. If you do continue to build for this device, I'll test whatever you throw at me.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] deagleonvalium:
I had a similar instance but I did a moronic thing and bought a pixel XL Verizon branded 128gb phone off of swappa. Moron didn't read about the updated bootloader since I have an original pixel Verizon branded phone but it was from like the second month they came out, ended up giving the Verizon pixel XL 128 to my daughter cuz she doesn't care:(:(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Shadoukun:
I'd be willing to test too. I have a Verizon pixel XL with an unlocked bootloader.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Colday96:
Wouldn't you still be able to unlock the bootloader just like you did before ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Man, I'm sorry to hear that; both for your sake and, selfishly, because I am not at all smart enough to make a functioning device tree from scratch. Maybe [MENTION=2376614]jcase[/MENTION] will make a single exception to help out a good developer? We can always hope! :fingers-crossed:

Above v7.1 (.0), the Verizon bootloader unlock does not work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Colday96:
Check out this tutorial

[youtube]3Q_cXradqbo[/youtube]
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
I don't need to watch a tutorial to tell me what I already know. Google bought Pixels unlock. Verizon ones updated to any version above 7.1 do not, their bootloader is locked and can't be unlocked.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jcase:
I'm not buying him an unlockable phone, and while I in the past it seemed like I can pull roots out of my rear, its a different game today. Takes far more work
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
That's....a fair position.

Thanks for the 7.1 unlock though!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dantexaiver:
You know the Pixel custom Rom scene has seriously been lacking development and the Verizon not being unlocked just adds to the issues. Is development on the pixel really that much more cumbersome due to the A/B partitioning
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I would say yes, since you now need to implement a solution that allows your rom to find the system partition in each slot, mount it, and flash itself. Most phones don't have the A/B partitions and still use the single system partition. The only phones that I know have this are the Pixels and possibly select Samsung phones that allow seamless updates.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dmbtech:
Gofundme for invidiblek to get a unlockable google version of pixel xl :)? They are a lot cheaper now.

---------- Post added at 05:25 PM ---------- Previous post was at 05:20 PM ----------

Invisiblek, what issues are outstanding for pixel xl changes to me merged into the main lineogeos and make it official?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HACK3DANDR0ID:
Same here if anything ever happened with that...

---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------

I started my Verizon Pixel XL with a TMO SIM and had no problems unlocking...

---------- Post added at 11:44 PM ---------- Previous post was at 11:42 PM ----------

Looks like not happened since 10/22. That's not good...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dmbtech:
Well, it was merged though... not sure what is needed for it to be an official build with nightlies.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] General_Tso:
To echo others, I'd be happy to test via my unlocked Sailfish...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HACK3DANDR0ID:
Guys, just got some bad info from a Lineage OS Developer : That as of right now, there is no Official Developer for MARLIN for Lineage OS 15.1. This means all work has seized. I created a thread in the Q&A section and i will post here and the other Unofficial Build page as well....

No Official Lineage OS 15.1 for MARLIN :( Because of no Developer...

I just chatted with someone at Lineage OS and they are looking for a Developer for Marlin for Lineage 15.1. He is stating there will be no Official Builds because they have any Devs with the device and i told him i would help find someone who would like to take over Lineage OS for Marlin. If your interested, this person is asking for your gerit username i'm guessing to see your work. Please let me know if your interested in taking over Official Lineage OS builds for Marlin at your earliest conveinence or you can contact Lineage OS yourself from the information below on how to become a Developer...

Thanks in advance,

TJ

From Lineage OS Website :

For developers

Contribute!

To contribute, you’ll need to be able to produce builds for your device. Pick your device from our list of supported devices to get started.

Once you’re successfully running your own build, you can begin to make your changes. All the apps included in LineageOS can be found in packages/apps, and core parts of the system can be found in frameworks/base.

Once you’ve finished making your change, simply follow our guide on submitting to Gerrit.

Submit your port!

If you unofficially maintain a device, and think it’s good enough to go live, follow our instructions on submitting a port. One of our developer relations staff will reach out to you, and we’ll work to get the ball rolling on official builds for your device.

Thanks again!

*edit*

If this developement stops, so will the few custom ROMs we have being they are LOS based so if there are any free and no tied up at the moment, or wants to take on another project, PLEASE do this for the Pixel XL Custom ROM Community! Not only I would gladly appreciate your hard work but so will many others in the community. I will even donate $$$ if thats what it takes for the build and for at least weekly updates.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] thewalkingdude:
Um this is almost two years old. We have a current version of Lineage available.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Phalanx7621:
Lol I know. I'm like.,. Yeah, there's no maintainer ... Because we have Lineage 16 now....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] admiralspeedy:
Yah, in the post of yours that I quoted it wasn't obvious that you had already tested it and as far as I know it's not actually merged yet anyways (unless he cherry picked it). But I did test it myself and, you are correct, it doesn't work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reechings:
Can someone check on this ROM if you are actually getting unlimited Google Photos storage? Someone in RR thread has noticed that even though it says in the app that it recognizes the Pixel, your actual storage is getting used up if you check under Google account settings.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jikenda:
I'm on the 05/06 ROM and my Pixel is recognized and showing unlimited storage.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reechings:
Can you check your actual usage in Google account itself and not through Photos?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jikenda:
I just checked the account settings and you're right. Photos are counting towards the storage space allotted. Not cool and thanks for the heads-up on that. Also, sorry for the misinformation.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] names:
This may have been addressed elsewhere on XDA, but what is the reasoning for LTE not showing up when on Verizon? Is this an issue with custom roms specific to the Pixel?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reechings:
Thanks for confirming. This is worrisome because I'm not sure how easy it will be to fix. As much as stock Android can be nice, there's no way I could go back to it now.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Could potentially just be a missed app that handles the feature or a configuration that is missing. What concerns me though is that it has been several months with a lot of people testing the feature outside of the stock ROM and it's only been now that we've discovered this. I have a feeling that there was a Photos update and/or a server side change to block out this. I'm going to try installing an old version of Photos to see if this changes. Also a quick note, the storage displays are delayed by a little bit. I noticed on the Google account page that it would take about 3 minutes for it to completely increment after I uploaded a bunch of photos and the listing for storage in the menu in the Drive app is delayed by like 30 minutes.

In other news, I made a couple custom recovery flashables to get the ROM close to stock and more. AptX Enabler will simply drop the Apt-X encoder files from here into /vendor and you should immediately be able to use Apt-X Bluetooth devices. The Pixel Launcher Now Feed Enabler will install the Pixel Launcher into /system/priv-app to enable the Now feed integration and also installs the Pixel icons, however I haven't been able to get them to apply yet but I've included it in case it's a simple change or setting to get it working. Make sure you uninstall the Pixel Launcher first if you have installed it from the Play Store.

I've tested these and they work, but the only thing I haven't tested is whether or not you'll be able to flash them after flashing the ROM without booting the ROM at least once.

The Pixel Launcher will get removed after any subsequent ROM updates as I haven't gotten any addon.d scripts worked out yet, so make sure you still have Trebuchet enabled as a backup. Apt-X encoder should survive though. Also I'm still SafetyNet certified after this.

EDIT: Updated Apt-X Enabler to V2 which now installs the encoder to both vendor_a and vendor_b, allowing you to continue using it when you do an A/B update and the active slot switches. This one is Pixel specific, so if you don't have one then don't flash it.

EDIT 2: Any updates done will be continued in the thread here.

File are attached below.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] invisiblek:
Where is this? I was sure this was working at some point.

This is fine here...do you have the N2G47O baseband?

You can probably switch the slot from the reboot menu in twrp to flash these directly after your rom. Addon.d isn't going to work, at all currently. A/B update zips do not include the necessary scripts/hooks to make it happen. Its in the works though.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Ah, haven't dealt with A/B updates before. Going to go do some testing then.

https://www.google.com/settings/storage

Clicking on view details will show a breakdown of how much each service is using, including Photos. You can try uploading a 100MB video through Photos and if you refresh the page about 5 minutes after it's done you'll see the usage has gone up. There has to be some change Google has done server side or via Google Play Services. I installed Google Photos 2.3.0 from after the Pixel was released and uploading items ends up still counting against your storage.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] names:
I can confirm that I am using the N2G47O baseband. All my signal strength will show as is 3G
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] smallsmx301:
I didn't think the O build was for Verizon
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] names:
That may be the reason why then. Could I have this confirmed?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CZ Eddie:
Holy moly it works!

I had spent at least 20 hours over a period of several weeks trying to get a flashable zip to work but never could figure it out.

I could get things to flash outside of system but nothing inside of system.

Could you please post your zips in my AptX thread?

I can then edit the OP to link to your post, with your permission.

Good job, Sir.

So many people haven't bothered with the aptX because there was no flashable zip. :good:

EDIT: Or better yet, start your own aptX thread so you can get some :thanks: :up: :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] smallsmx301:
I just did. You need the baseband from the L build which is Verizon
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] names:
My mistake. Thanks for your help
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] smallsmx301:
Hopefully that fixes it! Let us know
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] names:
Thanks for you help thus far. I tried flashing the L build but upon boot it's giving an error requesting the O build. After ignoring the error message I see that 3G is still all I can seem to pickup.

All help appreciated, keeping this in the thread in case someone else encounters the same issue.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Flash N2G47O to your device, flash the ROM, and flash radio 20170329 from NHG47L and flash the modem (fastboot flash modem modem.img) from the image zip for NHG47L. If you still get a prompt to install the N2G47O vendor then just flash the vendor.img for N2G47O. I think the fastboot update command doesn't apply the vendor image to both A/B partitions, only one, so you can end up with a different vendor when the ROM switches the active slot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] l0rd_VAd3r:
This is great that the Pixel is in the process of getting Lineage support. I am currently thinking about getting a Pixel XL but I am currently looking to see if Lineage can be built and flashed on it.

For the people who have install Lineage on the Pixel how usable it. I dont use Gapps so if all the main issues are with Gapps then is Lineage on Pixel pretty stable without them?

Looking forward to following the progress.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joey.gunnarson:
I can't get this to boot. I'm on the Verizon Pixel XL. I full stock factory imaged to N2G47O, flashed April Verizon bootloader, flashed twrp rc2, reboot to recovery, wipe system, cache, dalvik, flash rom and boot. All it does is play the boot animation endlessly. I also tried this process on the verizon may update no dice. Any help appreciated
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bobbarker2:
Fastboot auto detects the partition in use and flashes to that one accordingly. Also has anyone done the flash of the modem and baseband from the L build for Verizon and had success and seen some improvements? I've done this in the past with pure Nexus in a variety of ways such as a clean Flash and just flashing the radio baseband and modem but I still have a ton of connectivity problems.

I can get 4G but the signal will randomly drop to no bars and then go back up to where it was previously. The time where I'm at no bars or -120db is completely random comma sometimes it's five seconds sometimes it's 30 seconds excetera.

Does anyone else experience this issue regardless of the build or ROM they are on?

And I've tested this in multiple States so it isn't a local issue. I watched the radio logcat and can see the exact line in a log where the signal drops and then brought back but no amount of searching has lead me to any type of solution. I even contacted Google and Verizon, got a replacement phone and the problem still existed.

Since I eliminated local network and Hardware as potential causes, the only conclusion is that there's something screwy with the radio code or the radio itself.

At one point Google said they were aware of the issue and we're working to patch it but I was speaking to entry-level support and they don't really know anything.

I've yet to flash this ROM, which I'll be doing shortly, so maybe it's a AOSP thing?

---------- Post added at 04:34 AM ---------- Previous post was at 04:31 AM ----------

Is the kernel signed in this ROM? Because the April bootloader added a new check which requires the kernel to be signed. If it's not see chainfire's thread where he provides a flashable zip to sign a kernel.

If the kernel is in signed it won't boot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joey.gunnarson:
i thought the may bootloader added the signing process? pure nexus flashes without doing the signing process
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bobbarker2:
The previous PN build clearly stated that the ROM is now signed so the April bootloader update have no effect.

And the Bootloader doesn't do the signing it checks to see if the kernel is signed and won't boot if it isn't.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Pure Nexus?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bobbarker2:
Yes
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
What does that have to do with Lineage OS.

Oh nevermind. Saw the post above you. Not having a quote had me confused.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] devsx:
Is this rom also available with userdebug or eng tag?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Well went to test to see if my flashable ZIPs work, so I did a factory wipe and now the ROM just hangs on boot again. I got it to work before, I don't know why it refuses to work now. My process hasn't changed since last time.

Flash N2G47O, making sure both A and B slots have been flashed.

Let it boot

Reboot back to bootloader to boot TWRP

Copy over ROM

Flash it

Boot to system

Always ends up with it hanging on boot, continually showing the boot animation. I've also tried wiping the cache, but still hangs. I'm trying to flash 20170511, but I guess I'll try 20170506 which I know works.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Yeah turns out it was most definitely an issue with 20170511. Download the 20170512 build and you should be able to install it just fine. Here's the steps I took:

Flash N2G47O

Flash the opposite of the active slot for boot and vendor (boot_b and vendor_b if the A slot is active)

Boot TWRP

Copy over ROM

Wipe only cache and data

Flash ROM

Reboot

For Verizon users flash the radio and modem from NHG47L.

Has been a long day of troubleshooting for me.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] invisiblek:
I'm on Verizon and all my firmware is from N2G47O, including radio and baseband. I have no issues booting (signing thing) or radio issues with LTE.

Everything works. These builds have gapps baked in so you'll have to roll your own for the time being if you want it without gapps.

These builds are userdebug. You could roll your own if you want something different.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EggZenBeanz:
does sRGB mode work? The toggle in RR didn't change anything
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kitila:
All Nano gaps is is less of the Android apps pre-installed you can go through there and redownload all the stock apps that you want Nano I believe comes with just the Play Store and maybe Gmail all you have to do is reinstall the rest of the apps
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
The only app from the Play Store that the Nano package has is the Google app. The rest of the apps installed are listed here.

Works fine here on 20170512.

Also I updated my Apt-X Enabler ZIP to install to the vendor_a and vendor_b partitions so that the encoder can still be used when doing A/B updates. This will go nicely with, as any updates done with the Updater app will not affect the encoder. It'll continue to work until you need to flash an updated vendor image. More info and download at my post here.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jeffyh:
Just confirming, I'm on verizon, I'm showing "LTE" and "LTE+" I'm on the 05-08 build with Bootsigner and N2G47O. Maybe APN issue?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hobbified:
Must have been something about the 05 build, or some other random thing. I posted that after failing to go from 05 to 07, or 08 using the updater, then I flashed 08 using TWRP. Used the updater from 08 and it worked just fine. So false alarm I guess.

Today's new nitpick: Bluetooth A2DP/AVRCP. When playing music to my car I get artist and track, but not time / time remaining. Worked fine on stock and PN. Not important at all, just making note of it.