yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
It's not the same thing. Gapps has more to it. This is the core functionality for project file. You can always build it yourself and remove those apps. As for the official not having it, I would check one of the fi supported devices to see if they have it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
If all gapps had those 2 apps, yes. but they don't. Only the huge super gapps has them, which doesn't fit on pixel's small system partition. So they'd have to use aroma gapps and manually select them and try not to go over the available space on system partition. Whichever way I go it's going to inconvenience either the project fi users or the tinfoilers. lol. I feel it's pretty easy to go to settings and disable those apps, so that's what i went with.

I may still remove those 2 apps and just add an install note that project fi users have to use aroma gapps.

All official builds on nexus (like 5x and 6p) have had carrier services and gcs apps (for project fi users) for years, until recently. I removed them due to the crashes that started with oreo. But those devices have a system partition 3 times bigger than pixels, so project fi users can easily install the stock gapps or aroma.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lukazaz:
Sorry for the noob question (our phones are on their way and will flash it on thursday when I pick them up)

Besides the flash this then that then this then LOS.... Why nano gapps? I usually flash stock or mini (my girls use mini gapps) on all our phones

Also could you explain the issue with carrier services? I would hate to do all the steps to my phone to see carriers apps and the rest do not work (text and voice on telcel - Mexico) seem to crash when does apps crash

extra dumb question

Also, seeing how I damaged (2 times) the micro usb on a nexus 6, is there anything I should worry about on the pixel XL?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MrMarques01:
May I ask how you got Google Camera working? Mine keeps on crashing
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Poebat:
I restored from a cloud backup that had the Google Camera installed. The play store installed it automatically. try visiting the desktop version of the play store and installing it from there.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
you flashed the wrong gapps. see first post.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lukazaz:
[MENTION=614507]razorloves[/MENTION] do you have a video on of the steps?

---------- Post added at 10:46 AM ---------- Previous post was at 10:45 AM ----------

any videos showing of the steps that someone could share?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
Delete please
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] acroptics:
Feedback + APN

The instructions and 20180614 build works great on my Pixel. Thank you so very much for putting it together!

FYI, the Ting Data APN is incorrect per help.ting.com/hc/en-us/articles/115008890528-Completing-Activation-for-Your-Google-Pixel (new user can't post urls, sorry -- the info is below)

Name: Ting Data
APN: wholesale
APN type: default,admin,fota,mms,supl,hipri,internet,dun
enter the above exactly as written, without spaces
MMSC: wholesale.mmsmvno.com/mms/wapenc
MCC: 310
MNC: 260
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6

NOTE: I had to change the MMSC above because it is a url

Furthermore, trying to add a new APN leads to "Carrier does not allow adding APNs of type dun"
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
Stock doesn't allow apn type "dun" either. Just FYI.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] acroptics:
Good to know. I made a new APN without the dun type in the list and it still didn't work for MMS though it did work for mobile internet. I'll follow up with Ting on this too.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lukazaz:
Little help please, keep getting this

target reported max download size of 536870912 bytes

archive does not contain 'boot.sig'

archive does not contain 'recovery.img'

failed to allocate 1847750912 bytes

error: update package missing system.img

Press any key to exit
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] acroptics:
I had that at first before I realized that my system that I was trying to flash my device from needed more free space. The included "flash-all" script further uncompresses a zip that it pulls the images (*.img) from.

TL;DR; Free up some space on your laptop/desktop doing the flashing -- I moved 12GB of images to an external hard drive.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ethanhunt123:
just curious why this rom is unofficial? I guess what I'm asking is why its not officially maintained/built/distributed with other LOS devices? Dev support?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] acroptics:
Before the official build can exist, unofficial test builds exist. Official support is coming, see www.xda-developers.com/lineageos-15-1-supports-a-b-devices-moto-z2-force/
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lukazaz:
No go, even changed folder location and still I get the same issue
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lukazaz:
Finally!!!! Got it working.... after inital boot and etc, can we flash stock gapps? or is only nano gapps "approved"?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Poebat:
I had a similar issue with "carrier doesn't allow APNs type of dun". I just exited settings and it saved.

---------- Post added at 09:48 PM ---------- Previous post was at 09:47 PM ----------

Has anyone else had trouble detecting printers using this rom? I had no issues printing with my phone with PureNexus but I can't get my phone to detect my printer on LOS

Edit: got it working!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] acroptics:
Great! What fixed the "failed to allocate" error that you ran into?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] acroptics:
After finding "adb logcat" and showing him, a Ting support rep confirmed that the url being POSTed to (APN settings -> MMSC) was incorrectly http://mms.wholesale.mmsmvno.com/mms/wapenc instead of http://wholesale.mmsmvno.com/mms/wapenc like it should be. I entered the correct value in the APN settings. I do not yet know why lineage ended up prefixing the host with "mms."

For the record, this is also happening on an official Lineage 14.1 release on an LG Nexus 4

UPDATE: [MENTION=614507]razorloves[/MENTION] helped me get things working by having me delete all of the non-Ting APNs and reboot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
New builds are ready with the July security update from google.

That also means a new vendor img is needed from the July update released by google a few days ago. OPM4.171019.021.P1

The radio & bootloader img's are the same as what was in last month's update from google, so no need to flash them if you already have them. You can reboot into bootloader mode and see the radio and bootloader version numbers you have installed, if you want to double check that you have the newest.

You can extract the img's from the OPM4.171019.021.P1 factory image on google's site, or use the one's here that I already extracted:

Pixel img's: https://androidfilehost.com/?w=files&flid=278596

Pixel rom: lineage-15.1-20180707-UNOFFICIAL-sailfish.zip

Pixel XL img's: https://androidfilehost.com/?w=files&flid=278595

Pixel XL rom: lineage-15.1-20180707-UNOFFICIAL-marlin.zip

If coming from another rom, follow steps in the first post.

If you're updating from my previous build, follow steps below:

Note: You'll need the new rom zip and new vendor img and new gapps zip for the following steps, so put them on your internal storage (/sdcard)

1. Reboot into recovery.

2. Then select 'Reboot' menu and select the opposite slot from which you're currently in.

3. Then select 'Back', then select 'Recovery'. This will do a reboot into twrp.

4. Then select 'Install' menu and flash the new rom zip and flash the twrp zip.

5. Then select home button and select 'Reboot' menu and select 'Recovery'. This will reboot you into the other slot, where the new rom was just installed to.

6. Then select 'Install' menu and select 'Install image' and select the new vendor img you placed on your /sdcard and select the vendor partition, then swipe to flash it.

7. Since you flashed a new vendor img, you will once again have that /vendor/overlay folder that you have to delete. So, select 'Mount' menu and select the vendor partition and open the file manager and delete the /vendor/overlay folder.

8. Then select home button and select 'Install' menu and flash the gapps zip linked in the first post.

9. You're done. Select 'reboot system'

Major changes since last release:

1. July security patches. (details here and here)

2. July functional patches. (details here)

3. Customizable lockscreen shortcuts were added - change

4. Limited share targets to reduce lag - change - info

5. Allow fine tuning of Trust notifications - change

Note: There's a new version of twrp available. I used it to flash some zips and imgs and it worked fine.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
Update and TWRP working fine. I got a trust alert saying it was built with publicly signed keys. Interesting, and I am guessing that came with the trust update.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
You can just disable that alert in Settings>Security>Trust, since all my builds are signed with public aosp key.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Droid_JD:
Perhaps this is just me, but I tried using the new lock screen shortcuts option. Previously, the camera was in the right side and Google Assistant/search was on the left. I would often double press the power button when the screen was off in order to launch the camera app.

After the update, I put the camera on the left side of the lock screen and the phone app on the right. Now, when I double press power when the screen is off, the phone app launches.

Expected behavior?

[Edit] Swapped camera back to the right side, and how double press launches camera again.

Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] skatastic:
I just put lineage on my phone and it's randomly rebooting. I don't know why. I only find out it has rebooted because my fingerprint won't unlock it and I get the message saying that it needs the pin after a boot.

One time I did pull it out of my pocket in the middle of booting but that doesn't help me discover why.

Any ideas or troubleshooting to-dos because I have no idea.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
Log or it didn't happen... ;) Word of mouth honestly helps nothing unless someone can reproduce the issue and generate a log. This Lineage base is used for many flavors of Android and not one OS has any RR issues. This must be a result of third party software, a bad kernel you have flashed or just down right user error when installing.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] skatastic:
How do I get logs that would persist through a reboot? I'm perfectly happy to collect logs of i knew how to log through a reboot. I do have magisk as far as 3rd party stuff is concerned but not a different kernel. I didn't mean to come off as though I was blaming the ROM.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
Google "dmesg". The file will be stored in /sys/fs/pstore/console-ramoops. Thats if it is a kernel panic.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
What was your install process including magisk? When did you install magisk? Did you reboot first?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] skatastic:
1. unlock bootloader.

2. Install TWRP using fastboot

3. Install Lineage using https://xdaforums.com/pixel-xl/development/rom-lineageos-15-1-pixel-xl-marlin-t3725985 with all the restarts and changing slots. I didn't record myself doing it so I guess it's possible that I messed up a step but I don't think so.

I ran Lineage for a day before I installed Magisk. I'm not sure if I was getting the rebooting in that day because the evidence of rebooting is usually just that I have to put a PIN in instead of using fingerprint and it took a few iterations of doing that before I started to pay attention to it. There have been 2 times (one just today) where I've pulled the phone out of my pocket in the middle of a reboot so it's definitely rebooting.

4. Install Magisk

Here is my console-ramoops

https://pastebin.com/rdSvQSWn

Here is the current dmesg output

https://pastebin.com/KWcHDiiT

I suspect the dmesg isn't helpful now since it doesn't start at the beginning anymore.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
There's one reboot in the initial setup...

What Magisk version?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] skatastic:
Magisk-v16.6.zip is what I still have in my storage. (I know MM updated itself just recently.)

My Magisk manager is 5.8.1(127)

If it helps/matters...

My modules are Magisk Google DNS v2.1.2, Viper4Android FX for Magiskv15 v6.1.2, YouTube Vanced v13.23.59

I'm using systemless hosts with adaway.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
My suggestion would be disable all modules and start them running again 1 at a time for a day at a time. I believe V4A has had some issues, but it should be okay. I just recently dumped magisk and did a fresh install simply because I wasn't using root so I won't be a huge help.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] skatastic:
I'll give it a shot. I'm about as far from an audiophile as you can be so I won't miss V4A if that is the cause of the problem. My biggest root demand is adaway. Right now the only things I've used root for are adaway and logcat.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] phenoxis:
Could you kindly provide instructions on how to build from source? I'm looking to port some of my earlier kernel changes from LineageOS angler to sailfish and would like to build LineageOS from source.

I tried doing so with

breakfast sailfish && brunch sailfish

but the resulting images end up in a bootloop. I did flash the vendor.img file after running

fastboot flashall -w

edit: NVM, it turned out that although I'd run the commands correctly, I hadn't done a

repo sync

in a while. Everything works great! Thanks for your work on this. Much appreciated!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] juggalofr33k:
This isnt my first rodeo flashing roms, but my first phone with an A/B system... and i searched the thread, but didn't see an answer... what is the process for dirty flashing the latest build? Im on the June build and wanna flash the July. Do i have to follow all the steps again, (minus wiping)or just download, reboot to twrp and flash? The initial install was more difficult than the Nexus' (which i had em all) so i just dont wanna screw it up...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
Dirty flashing instructions are absolutely in this thread... That being said. Yes you need to follow all the flashing steps besides wiping and use the JULY vendor image.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
um, look on previous page :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] juggalofr33k:
Yeah, I got it...lol...I was searching for the term "dirty flash" and didn't come up with that...kinda sucks you have to do all that work to dirty flash though...I came from the 6p most recently and it was a breeze to update. I guess that is no more?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
"All that work" doesn't even come close to the amount of man hours that went into producing Lineage itself though. Lol.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
It will be much easier, even more so than the 6p, as soon as i start official nightlies. It will use a/b seamless updates. Soon™ :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
This is awesome news!!!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Poebat:
Will we be able to dirty flash the official rom?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NepoRood:
I learned this the "hard way", lol

No, when this device specific build of Lineage goes official, you will need to do a clean install. The reason is because of signing keys attached to the "Official" version. After you do the clean install, future updates will be "seamless", as Razor stated earlier ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] v8088:
Hi everyone.

Can I use Pico gapps?

open_gapps-arm64-8.1-pico-20180705.zip

or first post gapps only?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
You can use any gapps you want but you'll likely only get support if you used the ones OP recommends
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] luckylui:
I've been using Pico since I got my phone a couple months back with no issues.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] clambert11:
Ok, I apologize for being slightly off topic. I recently upgraded from PureNexus and have become a little rusty because the ROM hadn't been developed in a long time.

So anyway, the detailed ROM installation instructions by the OP were fantastic. No problems. I then wanted to update the kernel and root, so I installed the stock boot.img, installed ElementalX, and then installed Magisk. I thought I was good and everything booted like it should. For some reason though I lost recovery.

At this point I fastbooted TWRP and reinstalled the TWRP.zip file. After that I was hosed and all the phone would do was boot into recovery.

As it stands now I've reinstalled the ROM, which is fantastic btw, and have root. Does anyone have an idea why I lost recovery after installing the kernel and Magisk?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] schjor:
Will unlimited storage for photos and videos still be available if I install this rom? Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
Wiping the cache may have fixed your issue and got you out of a bootloop. I would do a clean install and make your final step flashing twrp install .zip!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] roman.ramirez.12:
Just make sure you do exactly as the OP says. Install ROM then install TWRP then reboot recovery that makes sure that you are in the opposite of slot. Whenever your phone does that forces you to keep rebooting into recovery you're usually on the wrong slot. So if you're still having that same problem stuck in recovery at first you can try to reboot into the opposite slot that your having the trouble with, and see of it boots up. If not start fresh wipe everything install ROM install TW RP then reboot into opposite slot.

Sent from my Pixel XL
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] luckylui:
I use Flash Kernel which doesn't remove recovery nor magisk. Other Kernels do because they aren't properly set up to keep those two intact..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] skatastic:
Just an update. I disabled all the modules and I haven't rebooted in at least a couple days. Thanks for the advise.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] codebam:
How do I know what my device password is? I removed screen lock before flashing, and my previous screen lock password does not work
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] methuselah:
[MENTION=614507]razorloves[/MENTION] I have flashed your gapps on another device that is using A/B partition table. The installation went fine. The device is even showing certified status. Well, I would like to ask if you can answer that whether they can survive the OTA or they needed to again reflash with each incremental update. Because as this partition table need to support special kind of gapps package that needs some sort of script so that it can survive the update. I hope I was able to make you understand what I wanted to ask.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
yes

no, neither mine nor official opengapps will survive an ota a/b update.

the only gapps that do are mindthegapps, and only when using the lineage updater in settings.

we will be making a blog post very soon with more info on this.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] methuselah:
Well, thank you. But the issues with Mind the gapps is not certified status. Who knows when will Google pull the plug.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
It being uncertified is not caused by the gapps zip used. And who cares if they pull the plug... Just register it if you're worried about that.

yes, i'll provide instructions
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] methuselah:
Well I have got no idea about that it was caused by gapps. But with your gapps it is registered. And it's far better smooth than mindthegapps. But thank you for your gapps package. The A/B thing is very difficult.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
You don't have to remove the device password if you are using one of the two most recent versions of TWRP. Your password can be input on this page. Sounds like you either created a password or are using an older/wrong version of TWRP that can't decrypt.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] i42o:
sounds like youre talking about the pin it asks when you try to set up the fingerprint... i ran into the same issue... turns out that because i didnt format the deviec this happened. once i formatted it it worked
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Zyphur:
Finally decided I cant go without long press to skip tracks, so now that there's OREO builds I rooted and ended up choosing this ROM. No issues so far, just the system settings which I know is a WIP. Been great, super smooth with nova. Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
Daily Driver

After a 12 hour test everything is looking great.

All mission critical functions appear to be working for me.

Well done & many thanks [MENTION=614507]razorloves[/MENTION].
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jkoch3:
Diag mode

Just installed on to my XL with 8.1

Only issue I had was having to disable my password since TWRP wouldn't decrypt properly. After that, installed like butter, great instructions!

Not sure if this the proper place for my question. I am having trouble getting QPST and my phone talking. I did set using setprop sys.usb.config diag and getprop returns it is in diag mode. I installed lineage os because I need to do this on my XL because I am a China Telecom user and to use my SIM I need to update my carrier_policy.xml file. A little guidance would be useful.

I am planning to write my experience up as post since I have been digging through Chinese and English language threads to make this work for the last week now. And I am sure others would come across this as well.

Thanks guys and gals
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kd0g:
Finally!

Much thanks for your work.

I'd just like to put in a request for expanded desktop.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
Thanks for the reminder. I meant to add a note about that in the instructions the other day, since a few people have brought up that problem. It's there now. :good:

It sucks that the newer 3.2.1-0 twrp doesn't work for flashing custom roms. I talked to dees troy a couple days ago about it and he wasn't even aware of the problem. lol.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
I think that is a wider Lineage issue. Yet to come for 15.1. In the interim, I use adb immersive. xda thread: https://xdaforums.com/pixel-xl/themes/how-to-enable-true-immersive-modes-t3554299

This is what I use: adb shell settings put global policy_control immersive.full=apps,-com.teslacoilsw.launcher,-com.strava,-com.google.android.googlequicksearchbox,-com.snoggdoggler.android.applications.doggcatcher.v1_0,-com.klinker.android.evolve_sms,-com.whatsapp