yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dantexaiver:
I take it the LOS updater is supposed to take a while to install?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DarthDestroyeis:
Just installed the 4/9 update. It is showing the vendor patch level to be March. Do we still need to update the vendor manually?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
No, you don't update the vendor manually. I updated them a couple days ago.

https://github.com/TheMuppets/propr...mmit/a71a91e06f2dc8430ee624f4e07629be31925777

https://github.com/TheMuppets/propr...mmit/a19802b3245d66db1a52132c320871d16a7885f3

I also noticed that the patch level date was wrong a couple hours ago and fixed it. I just forgot to update the date, when i updated the vendor img the other day. It's done now.

https://github.com/LineageOS/androi...mmit/6005c983651488c227738cb01553691a75ba3cb2
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DarthDestroyeis:
Thanks! I thought that was the case, but wanted to doubel check just in case ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dantexaiver:
Latest works great , was previously using the first official build and navigating to the cast function in settings crashed my display but now everything is working other than cant seem to charge higher than 99percent
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] tamjan:
I'm on the last v15.1 build with an encrypted phone. I use Magisk, and TWRP for doing backups. I know TWRP 3.2.3-1 should be able to decrypt Pie data...

According to peoples' experience here, will dirty flashing the latest v16.0 build cause headaches or should it just work? :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
Clean install. It's worth it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Irelialolxxx:
Hey [MENTION=614507]razorloves[/MENTION] how to change mac address on sailfish,marlin devices?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mushi_ami:
charging animation.

charging while switched off does not show any charging animation just still image of charging is that a issue or is that normal ? please let me know !
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dcshallot:
The phone boot loop suddently while I was watching app news. Then I can't boot into twrp img any more. Always boot loop. And I tried factory image 'flash-all.bat' with -w or without -w option. It still can't start.

Power off, and bootloader, flash google image not work.

Finally I found someone said use 'fastboot oem lock' then unlock, so I tried, but now, I can't execute ' fastboot flashing unlock' , it said not allow.

What can I do ???????
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbarnes1:
I've noticed that my phone no longer autofills 2 step authentication texts. I've had this happen in both Google pay and device policy.

It could be bc I'm using Google messages and gboard, both installed as user apps. Is this a permission issue?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] thetallguy:
I went dirty, following the instructions in the original post. I did format system before install, but data untouched. My XL works fine. Note though that I do not have Magisk nor LOS root, as my daily driver must "just work" while I am on call so I keep it simple.

Try it dirty and see if it works, if it doesn't you can format data later anyway.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] n3kf:
Hi all, I just got my sons sailfish. He got a new phone. Coming from a 5x. Lots of difference from the nexus line. The Pixel had a bad battery, so I replaced that. Due to the slot stuff, I really messed the stock install up. So decided to move to Lineage. Anyway, I flashed the latest with the installed twrp, installed mindthegapps and rebooted. Of course, no gapps. If I read correctly, I should have rebooted recovery after installing lineage, to swap the slot, then install gapps. Anyway, was shocked with the lineage recovery, but read enough to understand that is due to recovery being in the image. Again due to the slots.

So before I screw myself, I now have a phone without gapps. So looks like I have two options. Replace the lineage recovery with twrp and install gapps, but the next update I'll lose that again. Also, I can connect to my PC, boot to the lineage recovery, fastboot the twrp IMG, and then install gapps. I assume I can also install magisk from there if I want.

Am I understanding that correctly? Also I had done a factory reset in lineage, so assume once I get gapps installed, it will go through initial setup? Thanks. Really appreciate the work being done here.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] venkatsrin:
It's stated quite clearly many times:

Flash ROM then TWRP each time (if you want to keep it from being replaced by stock recovery)

Then reboot to recovery

Install gapps, magisk (some advice not to do it on first boot but I've had no issues)

Reboot and enjoy!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jxr94:
From what I've read, that fastest way to update via the updater is to let the screen stay on while the process is running. I turn on caffeine to infinity and let it run the update process. Also, make sure you have the "prioritize update process" option enabled in the preferences menu of the updater.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] n3kf:
Alright, I am quite confused. I am ok with the lineage recovery, so decided to just fastboot the twrp image. Did that and copied mindthegapps and magisk to the pixel. Then installed mindthegapps and magisk. Rebooted and it got to the lineage boot image. Waited for a bit and the pixel reboots. It does it again, so a long boot loop. Booted back into lineage recovery and see a red message that /data is not accessible and data needs to be reformatted. So I let it do it, but I am back to square 1, lineage without gapps. What the heck happened to data? Guess I'll try again and just try to get gapps in first. Or do I need to start from the beginning and reinstall lineage also??
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] venkatsrin:
At this stage as you have already wiped data, I would just wipe system and cache as well and start again :angel:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] n3kf:
Well, except there is another problem. There must of somehow been some major corruption. If I try to wipe cache/ART Dalvik, I get a message Invalid partition selection. Its basically saying cache is not a valid partition. If I go to the terminal and do a cat /etc/fstab the only partitions that exist are system, vendor, and data. I suspect the lineage recovery complaining about the /data partition was a red herring. So how do I get a cache partition back?! I included a pic of the cat /etc/fstab. Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] n3kf:
Or is it gone and was somewhat replaced with the slots. Is what I am seeing expected behaviour??

OK, I answered my own question so it no longer exists. That makes me feel a bit better! Looks like I needed to read some books worth of info.....

---------- Post added at 08:55 PM ---------- Previous post was at 08:23 PM ----------

So here is the deal. I did a factory reset. I formatted data to be safe. I followed the instructions. Downloaded the latest ROM, mindthegapps, and twrp to a directory on the sdcard. I then installed the ROM, then installed twrp again per the instructions. I did a reboot to recovery via twrp. When I get back into twrp, I install the mindthegapps zip. When that is done, I reboot. It gets to the lineage boot animation. It sits there for maybe about ten minutes. It then reboots and goes back into recovery (twrp). If I go to the sdcard, all the stuff I had put there is gone. If I try to "fix" the data partition in wipe to look at it, it says the data partition is invalid. Seems like it is getting corrupted via the boot. So lineage recovery complaining about data is correct (sorry I doubted it!?). I should note I have used the format data in twrp to get the sdcard back to where i can put data on it. So something is not right with data. Any ideas on diagnostics I could run, or even better, any idea what's going on?? Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] n3kf:
So everything I am reading out there is basically saying that I should go back to stock and re lock the device to let the system sort it out. I know I had to do that a time or two on my Nexus devices. Sounds reasonable? Does not appear that anyone on here has seen anything like this or understands what may be going on. I might fsck it and see if that finds anything first.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] n3kf:
So one more shot at some help. I did a df on the twrp terminal to get the block info for data. Then unmounted data and did an efsck on that and the file system was clean. Hmmm. I then mounted data. I did an ls of /data/media. That shows the twrp and test directories. The test directory is where I put my lineage and mindthegapps images. Hmm. So do an ls of /data/media/test and lo and behold the images are there. Yet if I go into twrp and go to file manager and look at sdcard it is empty. Also if I go to install, it also shows the sdcard is empty.

I'm beginning to think that there was encryption on /data/media (cause son was using the finger sensor for security) and doing a format data in twrp has not completely removed it. It's apparent that during the boot of a new image, lineage thinks there is something wrong with data and aborts. Then going into twrp, it shows the sdcard as empty. Something isn't right. And this same thing happens no matter how many times I do a format data in twrp.

Odd part is that the first install of lineage worked, but I did not have gapps installed! ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DarthDestroyeis:
Sound like it may be time to flash the factory image and start over
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NepoRood:
Your best bet is to download the factory zip from Google, here, get the latest image (PQ2A.190405.003, Apr 2019), flash it with fastboot.

This will totally reset the device, set it up asap (no need for lots of info, you can skip pretty much everything) then install Lineage with your new knowledge :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] n3kf:
. That's what I figured I would do. Have done it and its back running the latest stock plus its locked. Going to let it be for a couple days to make sure it's running OK. Then I'll try one more time.

I'm not enabling any, but I assume if you have a lockscreen set, like finger lock, it encrypts the internal SD card. If you want to move to lineage, I am assuming you should turn that off before you make the move. I'm thinking there was vestiges of encryption that was causing my problem.

Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NepoRood:
Anything other than "none" or "swipe" (on the lockscreen) will cause you problems, just to keep it basic. Best to have no encryption when trying to flash a custom ROM, IMO, anyways
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] n3kf:
Hi all,

Sorry for all the recent posts, think we are good now. Do appreciate the help. What kind of battery drain or life are petiole seeing on this ROM? Looks like stock increased battery drain from what I read on P. What kind of battery life are people seeing on this ROM on sailfish? Thanks again!! And great job to the developers!!!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NodCom:
Seems I (of course..) ran into problems when attempting to install LineageOS on my marlin.

Followed the guide in the first post, no error messages appears. Upon booting the device up, the LineageOS logo animates for a couple of minutes before the device automatically reboots into Recovery again.

What could the problem be? I am more than confused.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] roman.ramirez.12:
You don't have to lock the bootloader you can keep it unlocked but if you go into TWRP have to wipe options and select every box. Wipe it a couple of times. If something's wrong with the SD card it'll usually give you an option to fix it or format it. So I wouldn't be formatting and if I didn't have to. Once it's wiped clean even though you are in TWRP ,TWRP will no longer work once you reboot it. So yes you need to reinstall it after the ROM if you wish to have TWRP as recovery. After you clean the phone , remember pick every option in wipe , wipe this phone completely clean. Go to the Google Website on your computer and find the latest firmware for your phone. Download and extract to it the desktop. Put your phone into bootloader mode and plug it in to the computer then go in to the folder you extracted and double tap the flash all bat file. Let the computer do it thing once it's done it'll tell you to hit any key to exit then you can reboot your phone let it set itself up. Once it's fully up and running again. You can now add the necessary files you need into the download folder , TWRP, GApps, magisk ,that's when you can put your phone back into bootloader mode and fastboot TWRP and do what you need to do to install the ROM.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jayloofah:
Question about updating:

If I'm just updating within 16.0, do I need to reflash gapps? I know I need to flash TWRP.

Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NodCom:
Okay, update time.

Flashing just LineageOS and TWRP works, phone boots into LineageOS, no errors.

As soon as I attempt to flash SuperSU or Magisk, the phone never gets beyond the LineageOS boot animation before kicking me back to Recovery (TWRP) after 4-5 minutes.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jayloofah:
I've had problems with this as well. Not sure if it has to do with Magisk modules installed or something else. Anyone have any advice?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NodCom:
I attempted the same as before, but flashing the GAPPS package suggested by OP (plus LineageOS and TWRP before that).

Still the same result (fails to boot after sitting on the boot logo for several minutes), which I find quite strange.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UberActivist:
Are you trying to install magisk with a fresh install every time? When you are installing this rom fresh, it's recommended to let the phone boot and setup first before installing root.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NodCom:
I tried both ways with the same result.

Edit once more: Tried it again today.

1. Boot TWRP, wipe Data and System from the Advanced Wipe menu.

2. Flash LineageOS

3. Flash TWRP

4. Boot Android (I went through the first set up guide and looked around some in the OS)

5. Boot to TWRP, install Magisk.zip (Used latest available from the Magisk website)

6. Boot Android, which now booted correctly and I have root access.

I do not personally really want the Google apps; the only caveat would be if push messages or some other vital function is broken without it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] adm1jtg:
You do realize between steps 2 and 3 you need to do a reboot recovery?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NodCom:
No?

The first post in this thread claims otherwise, as does my on hand test result with my phone. Rebooting between 2 and 3 seems like I would be put into the LinageageOS Recovery, as TWRP gets overwritten when flashing the ROM. Please explain.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UberActivist:
You boot into TWRP to install the rom, then you run the installer for TWRP after you install the rom. THEN you boot into installed TWRP to install TWRP. The TWRP doesn't get overwritten until you update, then it gets replaced with lineage recovery
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NodCom:
The wording is a bit strange in the middle there. Are you saying you to install TWRP twice?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UberActivist:
Fastboot boot isnt an install. You're running the boot able image of TWRP to use it first time, because A/B devices don't have a recovery partition
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NodCom:
I am not using fastboot. TWRP already was on my device, coming from another (now wiped) ROM.

What I wrote already assumes the device is unlocked and TWRP is installed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UberActivist:
That's not... that's not how TWRP works on pixel devices. They don't have a recovery partition because all the updating is done by the system (I'm oversimplifying). TWRP has two parts, a bootable file to use "fastboot boot twrp.img" and a twrp.zip to install using the fastboot booted twrp. This TWRP is not permanent, as again, the pixels don't have a recovery partition, so they get installed on the boot image (I think). If you're doing things right you shouldn't have TWRP installed anymore, as you're supposed to wipe the partitions where that'd even be installed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] plittlefield:
I am loving this ROM as my daily driver - it is solid, smooth and fast, with NO problems so far.

Quick question, is it possible to add a CLEAR ALL button to the RIGHT hand side of the running apps list?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NodCom:
This comment literally makes no sense at all. I have the device right here with TWRP on it. Fastboot has NOT been used since I got the phone last summer.

I am perfectly aware that you need to flash the TWRP after doing anything with the OS image.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] thewalkingdude:
I had to fastboot the twrp image when got this phone. It's even in the twrp instructions. How else would you get it on the phone? Can't use stock recovery to do that. I'm not trying to cause problems just wondering how you got it on there without fastbooting it the first time?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] adm1jtg:
Apologies, I answered to quickly.... I meant that after installing rom and BEFORE installing gapps you need to do the reboot recovery as stated in step 4 of the op. If you miss that step you will get a boot loop at least that's what happened to me till I realized my mistake
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cwassman:
Took me quite a while to find the solution--same issue for me. This worked for me:

- Go to settings

- Go to Apps and notifications

- Go to App Permissions (in advanced section at bottom)

- Select CONTACTS

- Hit overflow menu button in top right corner (three dots)

- Show system

- Ensure that contacts, google, AND, google contacts sync are all toggled ON.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] gaebler:
My Verizon Services for non Verizon customers

Hi,

I have attached two screenshots from the my verizon services, I am not a verizon customer and not in the USA, so my pixel was never in contact with a verizon network or simcard. What concerns me is the amount of times this app as tried to make calls, send text messages and woke up the phone. Unfortunately its a german screenshot, erlaubt=permission granted, Im Hintergrund ausführen=Execute in Background, Telefonstatus lesen=Read phone status, SMS schreiben=Send Text Message, verweigert=denied

Can I simply uninstall it using adb and pm commands? What is this service needed for, for non Verizon customers? Why is it enabled in the Pixel lineage os images?

Thanks in advance.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] tamjan:
You can. I have this script to disable unneeded packages:

su -c pm disable com.android.calendar; \

su -c pm disable com.android.contacts; \

su -c pm disable com.android.deskclock; \

su -c pm disable com.android.email; \

su -c pm disable com.android.exchange; \

su -c pm disable com.android.messaging; \

su -c pm disable com.android.sdm.plugins.sprintdm; \

su -c pm disable com.android.terminal; \

su -c pm disable com.android.vzwomatrigger; \

su -c pm disable com.android.webview; \

su -c pm disable com.google.android.carrier.authdialog; \

su -c pm disable com.google.android.hiddenmenu; \

su -c pm disable com.qualcomm.ltebc_vzw; \

su -c pm disable com.svox.pico; \

su -c pm disable com.verizon.mips.services; \

su -c pm disable com.vzw.apnlib; \

su -c pm disable org.lineageos.audiofx; \

su -c pm disable org.lineageos.jelly; \

su -c pm disable qualcomm.com.vzw_msdc_api; \

su -c pm disable org.lineageos.trebuchet;

And my Pixel, running v15.1, works. Only disable all of these if you really want to - I do disable quite a few packages.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Anonturtle:
Did you do any extra steps or anything? I can't get it to work
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] spaghettiAlready:
No, I used the file manager in TWRP. Moved the Google phone folder to the system apps just like his instructions.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Anonturtle:
It started working out of the blue so idk
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jdmst77:
Does this ROM allow you to have the unlimited full image quality photo uploads in Google Photos guaranteed in the stock ROM?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] OSantal:
I believe so:

https://www.xda-developers.com/google-photos-broken-unlimited-backup-google-pixel-custom-rom/
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UberActivist:
It didn't at one point, but it turns out it was just a typo that broke it. https://www.xda-developers.com/google-photos-broken-unlimited-backup-google-pixel-custom-rom/

Edit: aw crap we posted the same link
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jdmst77:
Thanks! I didn't find the details in this thread when I searched. Interesting that they would use a capitol "G" when they are a *nix based os

So glad that the bootloader is easy to unlock on Verizon variant. Looking forward to getting off my LG G3 Pixel ROM and take the real thing out for a spin
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ofirmz:
when i install opengapps 9.0 stock i got error #70 need help!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] adm1jtg:
I would recommend just using the gapps listed in op
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] revamper:
yes.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] revamper:
Updater has soft bricked my phone two times. When updating manually via recovery, my Google play services stopped working. What am I doing wrong? I am using magisk and opengapps mini. I'm having major trouble updating nightlies without things breaking. Please help.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] adm1jtg:
I have done a few updates no issues but I shifted to mind the gapps a while ago after reading about and also personally experiencing issues with all my open gapps installs
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ofirmz:
Can some tell me if im doing everything right

1- install the rom and the twrp installer

2- reboot into recovery mode on slot b and install gapps

3- reboot system ?

Also Gapps from here., Or can i use opengapps., I try so bad with openapps but im getting error 70 following the steps on top!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
Just a quick note for you all. The lockscreen shortcuts feature has been added to lineage-16.0. It will be in tomorrow's build (20190424).

https://review.lineageos.org/q/topic:"pie-lockscreen-shortcuts"+status:merged
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Anonturtle:
Anyone been able to get markup working?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jayloofah:
Doesn't the new TWRP change the install process, there's no more .img needed to boot into, only a zip that installs to ramdisk. Thoughts? Because I'm not sure how it would change the update process as well.