yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] drozek:
Anyone have issues with Google Pay? I have Magisk installed it passes safeynet but when I open the add it says "Google Pay is unavailable" "Check Connection and try again later"

Google Pay, Chase Pay is hidden under Magisk any ideas?

---------- Post added at 03:35 PM ---------- Previous post was at 02:40 PM ----------

Alright I installed this: https://www.apkmirror.com/apk/googl...3-2-72-020400-206980955-android-apk-download/ and it gave me errors, so I deactivated it and reinstalled the google play services and google pay works again, not sure if it functions but i added my 2 cards.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] waingro808:
Is the image quality exactly the same as stock ROM? That is his question.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] armando_rod:
Yes, using the Google Camera Nexus/Pixel devices don't suffer from degraded camera quality, never have. This is true since the Nexus S something like that
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
wat? lol. no

yep

The lineage pixel roms come with Snap. It's the qualcomm snapdragon camera app, not the aosp one. But yeah, i agree, google camera is better.

There are more options and features and control in Snap though.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] venom_tan:
waiting so long for lineage os . Any major bug detected ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] v8088:
Can you help me?

I want to correctly upgrade

from lineage-15.1-20180707-UNOFFICIAL-marlin.zip

to last official nightly.

On 16 of july I moved from stock android 8.1 and flashed lineage-15.1-20180707-UNOFFICIAL-marlin by all steps from the first post.

I unlocked bootloader, install latest twrp 3.2.2, all wipes needed, then install LOS 15.1 + recomend gapps. After the first boot I made all tunes then I installed Magisk 16.0

Now it works mostly fine but I have some bugs.

I'm moving to lineage-15.1-20180731-nightly-marlin-signed

Am I right about steps order?

1.

NOTE#1

fastboot flash --slot all vendor vendor-marlin-opm4.171019.021.p1.img

fastboot flash --slot all radio radio-marlin-8996-130091-1802061512.img

fastboot flash --slot all bootloader bootloader-marlin-8996-012001-1711291800.img

2.

Run this script called lineage-migration-signed.zip in TWRP (from the NOTE#4)

3.

3.1. boot into twrp and wipe data and system

3.2. flash rom zip (lineage-15.1-20180731-nightly-marlin-signed)

3.3. flash twrp zip (twrp-3.2.2-0-marlin.img)

3.4. reboot -> recovery (this will reboot you into the other slot)

3.5. flash mindthegapps zip (MTG-unofficial-8.1.0-arm64-20180721.zip (from the NOTE#2))

4.

Then reboot to system

5.

Flash latest Magisk v16.7 beta

Thanks in advance for reply.

I need my Pixel XL for everyday using and I don't want to make a mistake(s) and flash it again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
In the version of mindthegapps i am using it definitely asks you if you would like to use aod during initial setup. Lol. I promise it is something that is part of mindthegapps. I think this is where the confusion is coming in.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
Could you please explain this then? Which is part of the setup wizard, which is part of mindthegapps!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Lka1988:
I also used MindTheGapps (linked in OP), but I never got that screen.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
Must be the version I used... Lol. I know Dan probably used the same version as me so that's that. I am using the official build. Los's must be different
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dangambino:
I'm using arm64 6/1018 MTG .....I just started using that gapps package with official LOS and that's when I started noticing it. I just flashed flashed that same package with firehound ROM and got the same option at the end of the initial setup.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
i've done like 10 clean installs over the past few weeks, with my mindthegapps and official one, and never seen that screen.

It's in the setupwizard but only shows up if it detects the always on config, "doze_always_on".

Which is only there if an always on hack is installed, or you restored a backup that has that config saved in it.

So I'm pretty sure what's happening is, if someone at one time or another was on a rom that had the aod hack built in or they added it, and google did it's normal thing of saving/syncing your settings, then later down the road you do a clean install on a different rom and restore a google backup while in the setup wizard. Then it shows up.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stebomurkn420:
That's sounds pheasable. But I just clean installed LOS from stock P and I didn't restore. And it still asked me that. It's definitely something in MTG that is triggering it because open gapps doesn't do it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dangambino:
I'm a noob when it comes to development so I can only speculate and go off the knowledge of others ( which is a very few devs, and dev teams that thankfully maintain ROMs and development for marlin stilI)

I wiped and did a clean install on firehound earlier today (which is Im really digging btw), and it prompted an AOD screen and option. I first used MTG with Official Lineage and thought it was a ROM feature, tbh.

Now my curiosity is peaked due to the previous comment about needing an extensive hack to enable this feature on marlin and getting it to work, and since I don't use the damn feature anyway lol, I'd like to remove any such mod on any ROM I may be running if I can.

I also don't recall any such prompt or option during initial setup, while I used opengapps every time I flashed a ROM prior to lineage OS official build being released.

P.S. Thanks again
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Stealth111:
[MENTION=614507]razorloves[/MENTION], are these eventually going to become "nightlies" or are they going to be compiled more of on a weekly basis?

Thanks Again for all you do!

Stealth111
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dangambino:
I didn't independently install any such hack ever since I unlocked my bootloader at the end of June.

I guess I should of just asked if this hack was part of a custom ROM I have flashed in the past, and if I've done a clean install as soon as today, where would this hack be stored, and if I can remove or delete it and why it persists even after a wipe and clean install of another custom ROM.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
you don't wipe data when using the migration zip. thats the whole point of using it.

for the past year and half, since beginning, lineage has only done weeklies. there's no plans to change that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] v8088:
Thanks for your reply.

So I don't need any wipes or make wipe system only?

Or I must to skip step

3.1. boot into twrp and wipe data and system

and continue with next step

3.2. flash rom zip (lineage-15.1-20180731-nightly-marlin-signed)

Update:

Flashed official nightly.

All bugs from my previuos posts are still here (splash messages about missed libs when I start some apps, force closes from time to time of some apps & games etc.)

Maybe I need make factory reset or flash stock firmware (factory image) and then flash LOS 15.1
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lukazaz:
just wondering once the next update is out, do we use the lineage updater or do we need to the manual dance and flash (flash rom then TWRP reboot then GAPPS?)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] luckylui:
If I'm not mistaken the LOS updater will handle it. TWRP should survive the update, but Magisk would need to be re-flashed since it won't survive the update.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sg114:
So I just installed Lineage OS on my Pixel XL which previously was running Copperhead OS. So far everything works but I cannot for the life of me get the Play Store to work. I have tried both MTG, the unoffical MTG, and GAPPS. They usually install without issue but when I try and load the play store it gets hung upon "Checking info" and then it alerts me the app has stopped responding.

Any ideas would be great.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
Installing Play store from scratch or via Titanium backup?

Have you tried wiping the cache and data for Play Store?

When you tried the different Gapps - have you started from scratch each time?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] davidshen84:
I have been using [MENTION=614507]razorloves[/MENTION]'s unofficial LOS 15.1 build for my Sailfish for a long time, and everything works well. But last time when I try to flash his unofficial LOS 15.1 on my Marlin, I got infinite boot loop as well.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
Yes, you can use the updater. You'll get a notification when an update is available and you can tell it to download and install it, if that's what you want. When it's done, it will let you know and give you the option to reboot to complete the update. Just like what happens on stock rom.

You can go to settings>system>about phone>lineageos updates and manually check for updates. You can also check your updater settings there.

it does not. https://xdaforums.com/showpost.php?p=77128976&postcount=789

did you install and boot into lineage first, without gapps? sounds like you did that. you have to flash gapps when you install rom.

gapps has to be installed with initial install because that's when all the default permissions are set up.

to fix it, you have to factory reset.

just means you're flashing it wrong. try again or give details on what you're doing exactly so that we can see where you're going wrong.

Many thanks to verizon user [MENTION=8636583]bnmEEFaej[/MENTION] for spending a lot of time doing a ton of testing for me to help me fix verizon wifi calling. :good: :highfive:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UberActivist:
What does the "install updates faster" toggle do in the updater?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
basically, google intentionally made the install on a/b devices go slow, so we added an option to make it faster.

more info here https://source.android.com/devices/...ile-the-system-is-running-isnt-that------slow
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
Can we get an ETA on 16.1?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
um... google hasn't even released 9.1 yet.

but to answer your question, 42.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Stealth111:
Sorry if this has already been answered somewhere, but, will your customized opengapps nano package survive the update process? I think not, and if so, what is the process to do an update with the built in updater and keep the opengapps nano working? Also, on the same note, If I am running the first official build and I came from a dirty flash of your old unofficial build running your opengapps nano package, is there any way to convert or shift over to using the mindthegapps package you provided without blowing out my install and starting over? If so, that would be great, then I could move to your build of the mindthegapps package before I did my first update with the LineageOS updater.

Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] luckylui:
New update is out for Marlin [emoji16]
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jacobas92:
Just gonna put it out there that I absolutely could not get this rom to boot on two different sailfish at all under uny circumstance until I updated to TWRP 3.2.2.0 and reflashed it. 3.2.1.2 refuses to flash 15.1 correctly on the sailfish. Just thought I'd mention it in case anyone else had problems
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Ermahgerd we are getting these in our threads too. I swear these people were dropped on their heads as children.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joeski27:
So I've downloaded today's rom update, and I want to just manually flash (so I don't lose Magisk via the OTA update method)...do I still need to flash rom & twrp, reboot recovery to switch slots, and then flash gapps & magisk?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] luckylui:
This is how I manually flashed..

Reboot to Recovery & switch from Slot B to A

Reboot recovery

Wipe Cache & Dalvik + System (Not Data)

Install Rom

Install TWRP

Reboot to Recovery (Should be on Slot B now)

Install Gapps

Reboot to system (wait till it loads)

Reboot back to Recovery

Flash Magisk

Reboot to system

Working fine here :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
I removed the link to my custom opengapps a week ago when official lineage came out because they don't survive. Neither do official opengapps.

My custom mindthegapps (mtg) linked in the op, and official mtg do survive.

You can switch to my custom mtg with no problems. Just flash it using old manual flash steps. Flash rom + twrp, reboot recovery, flash mtg. Then you can start using lineage updater.

yep. until the magisk dev fixes it, you'd do the same old manual flash method

there's unneeded steps in there.

you don't wipe anything when you're just doing an update (dirty flash). completely unnecessary.

you don't reboot to system before flashing magisk when updating. it's only required on initial magisk install.

just follow the same old manual flashing steps.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] luckylui:
Old habits, brother. I always like to wipe when updating just to be safe and I haven't had any issues the way I go with it. :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UberActivist:
I don't know if any other Verizon users had this issue, but I wasn't getting the toggles for VOLTE or WiFi calling.... and the carrier was showing up as "Verizon" instead of "Verizon Wireless."

I had to go into the carrier testing menu by pressing *#*#4636#*#* in the dialer, and then toggling on "VoLTE Provisioned" in the carrier settings menu. This automatically toggled on WiFi calling too, and changed the carrier title back to "Verizon Wireless."

So far, I think this sticks, as it persists a reboot too. After toggling that switch, the setting for VoLTE and Wifi Calling show in the settings menu.

Edit: volte works when doing this, but wifi calling errors when you try to turn it on. Did the wifi calling fix for Verizon make it into today's build?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dangambino:
Looks like it'll be in the next build if I'm bit mistaking
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
it's definitely in the nightly. i merged it a couple hours before the marlin rom was built. the changelog timing must be off a couple hours.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Stealth111:
WiFi Calling is broken for me in the latest nightly. I have turned all settings off and on, in both the secret menu, as well as in the call settings. They all say "WiFi" for Roaming as well as "Mobile Preferred" for all calls, but it never switches over to saying Verizon Wireless WiFi Calling at the top now. Tried a reboot as well as Airplane mode off and on. It has always worked for me through the Unofficials as well as in the first Official via Dirty Flash...

Edit: OK, found out the issue, for some reason after using the built in updater and flashing to the latest nightly, this setting got reverted, or changed back to default: "wfc_ims_mode 2". It was back to "wfc_ims_mode 1", which makes it not use WiFi as the default for all calls. WHEW! I really rely upon having WiFi calling be the default for all my calls, so I am glad it was just a small fix. ADB Shell and a quick "settings put global wfc_ims_mode 2" and I am all back up and running.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Phantop:
Not necessarily related to the ROM but is anyone else unable to unencrypt using TWRP? I used to have a guest account from Island but after that I wiped system, data, internal storage and I'm still unable to. The TWRP page says it can't decrypt from Android P, but the latest stock I was up to before getting this ROM was on security patch June 2018. Right now, I'm running this rom with all the vender, bootloader, and radio files installed from there. Anyone know what's going on?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UberActivist:
From my experience twrp just can't decrypt android p. You'll have to format to get it to work I think...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Phantop:
Here's thing thing: I was never on Android P... and I DID try formatting Internal Storage from TWRP. Still wouldn't decrypt... Removing encryption still works, though.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
It is probably better to take this up in a separate thread dedicated to TWRP. This can confuse users who are trying to troubleshoot Lineage with those troubleshooting TWRP.

Maybe this thread? https://xdaforums.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joeski27:
Hey, does anyone know where the LOS updater saves the update file after downloading? For the life of me I can't find the file in order to flash it in twrp.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
There's an option to delete it after installing in the lineage updater. I'm not sure where it stores it as I have that option ticked.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
I will definitely be looking into that dt2w when i have some free time. It has annoyed me soooo much since i first started using the pixel. lol

And long press back to kill app will be in next build.

I was going to release an update yesterday, but google released the january security update, so i'll wait till those changes are merged into lineage. then i'll merge all the marlin device and kernel and proprietary files changes from the january security update and release an update.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I have 15.1 for sailfish available on Telegram in the Google Pixel group, group is [MENTION=253311]Pixel[/MENTION]_ithehappy
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dcillusions77:
First time off WiFi running this rom, and I get Sprint DM configuring notification. It went on for my entire shift last night. It didn't drain battery or anything. Just thought it was kinda wierd is all. Everything else is working perfectly. Any help would be appreciated as to how to get rid of that. I'm on Project Fi.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] wgrant:
Sprint network is weird with custom roms on the pixel xl it seems. I get that after a reboot when not on stock. I just hit cancel and all is well. It seems to be a failure in connecting back to sprint to update any phone provisioning that's necessary.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
I don't use project fi. Provide logs so i can see what's going wrong and fix it.

https://play.google.com/store/apps/details?id=com.tortel.syslog
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dcillusions77:
Ok installed I'll keep an eye on it and see if it will pop up again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
New build with January security patches. :good:

That also means a new vendor img is needed from the January security update released by google 2 days ago. OPM1.171019.012

The bootloader img is also new, so you should also flash it. The radio is the same as what was in last month's security update from google, so no need to flash it.

You can extract them from the OPM1.171019.012 factory img on google's site, or use the one's here that I already extracted:

https://www.androidfilehost.com/?w=files&flid=239134

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

If you're updating from my previous build:

1. Reboot to recovery.

Note: When you do that you will be in the slot in twrp that has your current lineageOS installed. When you flash a custom rom on the marlin, it goes to the other slot from which you're currently in, so you want to reboot into the other slot because you want to get into the habit of always doing the rom install while in the same slot. That way you don't get mixed up flashing things to wrong slot or booting into wrong slot. So, go to 'Reboot' then look at the "Current Slot" and select the slot button for the other slot. Then select the "Back" button and look at the "Current Slot" to confirm you're in the other slot. Now, we need to go into bootloader mode to flash the new bootloader img, so select "Bootloader".

2. Flash the new bootloader img.

Note: make sure you use the '--slot all' option so that you flash both bootloader slots. Like this:

fastboot flash --slot all bootloader bootloader-marlin-8996-012001-1711091153.img

3. Using the volume buttons select 'restart bootloader'. Or do the 'fastboot reboot-bootloader' command.

4. Flash the new vendor img.

Note: make sure you use the '--slot all' option so that you flash both vendor slots. Like this:

fastboot flash --slot all vendor vendor-opm1.171019.012.img

5. Using the volume buttons select 'recovery mode'.

6. Now you can flash the new rom lineage-15.1-20180105-UNOFFICIAL-marlin.zip

7. When that's finished, flash the twrp 3.2.0-0 zip.

8. Then go to 'Reboot' and select 'Recovery'. This will reboot you into the other slot, where the new rom was installed.

9. Since you flashed a new vendor img earlier, you will once again have that /vendor/overlay folder that you have to delete. So, mount the vendor partition and open the file manager and delete the /vendor/overlay folder.

10. Flash the new updated gapps zip open_gapps-marlin-8.1-nano-20180105.zip

11. When that's finished, flash the latest stable magisk zip (currently v15.2).

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

Major changes since last release:

january security patches

added advanced restart (the power menu setting still crashes, but advanced restart is working. you can enable in dev options.)

added long press back to kill app

fixed battery charging led notification

enabled unlimited storage in google photos on full res pics

fixed some (all?) sprint, verizon, and project fi issues

LiveDisplay is now implemented and working properly
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Dachfenster:
Thanks for the detailed description! :) Working great so far.

Since I was trying to find out how to get the advanced reboot to work: it's under developer options in case anybody's wondering, too.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] buski:
[MENTION=614507]razorloves[/MENTION] i get unknown --slot option when i try to flash bootloader or vendor :confused:

and i cannot find long press back to kill...

anyway i just flashed one slot at a time and its all good thanks!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dorqus:
You may have an older version of fastboot.

See if you can get the most current version from Google. Glad you're all good and you were able to get it flashed!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
As mentioned in the previous post, this is happening because your fastboot binary is old.

Update it with the sdk manager, or if you have a standalone version you can get the latest here https://developer.android.com/studio/releases/platform-tools.html

It's where we've had that setting for years, in developer options all the way at the bottom. :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Zyphur:
Updated from the Dec 27 version to todays, and this is probably the first time in a long time I've seen the LED on. BUT my gapps and a few others keep stopping and the colours/brightness look really wonky (more orange, like nightlight?) :/