yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lenin35:
I know that the privacy guard has be depricated in LOS17 but can anyone post some screenshots of the new privacy system ? Is it the same version like the stock or does it have advanced stuff like Start on boot, external read/write , fingerprinter permission etc ?

Edit - nvm its almost the same one as stock one
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lenin35:
Wait, how’d you get to that screen? I dont see the same things in the app info section
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] oranget:
Please make official builds for Pixel 3a XL (Bonito)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ktnxd:
https://play.google.com/store/apps/details?id=com.pavelrekun.skit
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fleagalbaum:
When I plug in my USB c buds that came with the phone. The audio isn't routed to them. They do work sometimes if the usb c is turned around. They are supposed to be reversible. Any ideas?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ktdt00:
12/29 build make any difference to AA working? Tia!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _Ra1n_:
Sounds more like a issue with your USB-C port more than anything, especially if it is intermittent. Does the USB-C to 3.5mm headphone adapter that came with the phone have the same issue?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mcastro90:
Hi, since the first December build I started to have some issues with Netflix app that showed an error suggesting to restart the device, I think it was error 501.-109. I didn't have issues with November build.

The fix for this was to install a Magisk module (liboemcrypto disabler) so the app works fine again.

Was there something significant different between November and December builds that affected this?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
New builds.

Not much changed. Just fixed the chrome & youtubetv issue mentioned on previous page.

blueline rom = https://androidfilehost.com/?fid=4349826312261695799

blueline boot img = https://androidfilehost.com/?fid=4349826312261695800

crosshatch rom = https://androidfilehost.com/?fid=4349826312261695811

crosshatch boot img = https://androidfilehost.com/?fid=4349826312261695813
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
Thanks. I did. Sorry for responding so late.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
new builds with all the security patches and changes from google's january 2020 update. :highfive:

blueline rom = https://androidfilehost.com/?fid=4349826312261697644

blueline boot img = https://androidfilehost.com/?fid=4349826312261697648

crosshatch rom = https://androidfilehost.com/?fid=4349826312261697659

crosshatch boot img = https://androidfilehost.com/?fid=4349826312261697666

Other changes:

Hide or protect apps in the launcher - change link

Hide or show icon labels in the launcher - change link

Fixed missing icon labels in folders - change link

Also, just a heads up... we're on discord now. https://lineageos.org/community/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ptn107:
So the squeeze is the only thing that doesn't work?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ktnxd:
Squeeze doesn't work, nor does expanded desktop in display settings, crashes when I try use it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] peconaut:
[MENTION=614507]razorloves[/MENTION] Audio is coming distorted/muffled. Especially when using YouTube.

Clean install an coming coming from Official January Update
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
squeeze requires proprietary google framework code to be reverse engineered, so that's why it's not in lineage.

and there is no expanded desktop in 17, yet. no one ever finished porting it from 16.

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/260303

the entry in settings is still there, but it does nothing.

audio is fine here. maybe you installed some hack/mod that's causing it.

anyone else experiencing this?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Alpha1BA:
ok my first Pixel! I chose the 3, is this rom suitable for daily driver? is call recording possible? big up to Razor for all your hard work!! it is appreciated!!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
Good news, I fixed wifi calling. :highfive:

So here's some new builds

blueline rom = https://androidfilehost.com/?fid=4349826312261701401

blueline boot img = https://androidfilehost.com/?fid=4349826312261701402

crosshatch rom = https://androidfilehost.com/?fid=4349826312261701443

crosshatch boot img = https://androidfilehost.com/?fid=4349826312261701433

Note: Wifi calling is enabled by default, just like on stock rom. You can disable it if you want, in the phone app settings or in settings->network & internet->mobile network.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Alpha1BA:
ok back to basics for moi, can anybody please supply a link to google drivers exe ive been away from android for years n now... still a noob all im gettin is to manually install n thats not happenin bought what appears to be a dodgy pixel 3 even tho i paid almost first price keep gettin the red triangle at restart this device cannot be trusted but cant even get it recognised on laptop wivout correct drivers somebody pls help!!! ty
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
Do you have the latest SDK Platform-tools r29.0.5 installed on your laptop? https://developer.android.com/studio/releases/platform-tools.html

Also, make sure the USB is not plugged into a USB charging port.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Alpha1BA:
yes, was a dodgy usb cable. Im dissapointed im getting the your device is corrupted and cannot be trusted when i boot :(
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
That will happen as long as your bootloader is unlocked. A word of caution, do not lock the bootloader unless you are 100 percent stock.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] supachris:
This is normal and OK for custom ROM. Your data is still encrypted.

If you want a Google free most secure ROM with locked bootloader, you should use Graphene OS.

https://grapheneos.org/

And also from me: NEVER EVER lock the bootloader if you not went back to completely stock ROM!!!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Alpha1BA:
thx for advice it is appreciated!! n yayyyyy I managed to fix my faulty P3 after hrs n hrs n hrs I finakky managed to fix the almosr dead P3 I did this by downloading the penultimate rom from https://developers.google.com/android/images using the akk in one tool it finally flashed and all errors gone. I must say apart from google assistant tryin to get in my pant this seems a relatively decent bloat free rom!! on a diff note when I tried to install razor rom the boot took literally milliseconds and whilst trying to sideload it came back with error file not found!? yes it was in same location etc etc but tbh I think im gonna stick with what I managed to do, it's lightening fast with no issues whatsover!! happy flashin ; )
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
It is OT and rude to post information about another ROM on this thread.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Alpha1BA:
hey hey hey its all good : )
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ahoyboyhoy:
thank you to razorloves and anyone bringing LOS to the Pixel 3! Coming from official LOS 16.0 on a Pixel 1, I just got a good deal on a used Pixel 3 and excited to see that the 3 might get official LOS support.

Based on a few posts and the beta status assigned to this thread, I'm thinking to run this as my daily driver.. Is anyone rooted and able to use Google Pay for in-store payments? I've got my Pixel 1 on LOS 16.0 working. Is there a guide for the Pixel 3 and LOS 17.1?

I've read through this thread and saw mention that Privacy Guard is deprecated in LOS 17.1. Is there a source for what non-AOSP features were added/removed coming from LOS 16.x? I know I could install these builds and poke around to find out for myself, but perhaps there are features that are in development (for addition or removal)?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Brainium:
Thanks for all your hard work! We would not have Lineage for the pixel 3 if not for you.

I am building a personal version Lineage 17.1 for my pixel 3 using your sources for fun (and also to learn how to build Android), and I am curious as to what you did to get wifi calling working?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
added the CarrierServices app

https://review.lineageos.org/c/LineageOS/android_device_google_crosshatch/+/266851
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ahoyboyhoy:
Had some time today and installed this and can mostly answer my own questions:

I've only just installed it, so my experience isn't exhaustive, but everything is stable thus far and I've spent the time configuring it as my daily driver and installed my SIM. Google Pay allowed me to setup a card for in store payments after I followed this guide. I believe you also need to set the device fingerprint same as you did in LOS 16.0 (I did that before the SQL thing). Doesn't seem like anything else is special for LOS 17.1.

I still don't have a good source for this, but here's what I've noticed to be different:

Privacy Guard gone

System Profiles QS tile missing (likely to get added later, took awhile for 16.0 to have it)

System Profiles doesn't allow you to modify Lock Screen setting to disable lock screen or PIN entry
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wishx:
The only thing better than Lineage 17.1 on Pixel 3 XL would be Lineage+microg with no gapps on Pixel 3 XL! :D
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Cyutim:
An unknown icon appears on the launcher, and Bluetooth has to be re-paired every time
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Just wondering if it uses Quickstep launcher instead of Pixel launcher (I am not on this ROM). I had the mystery icon show up after installing Dirty Unicorns 14 RC and bringing my apps back from Google Play. Never had the mystery app on stock (still don't on my wife's P3 with similar apps +root) or on Havoc which uses Pixel Launcher. Also, don't have the issue on unknown app on Lawnchair. My guess is that it is something that Pixel Luncher hides automatically and that Lawnchair does as well. I'll be damned if I can figure it out. Google Play Services for AR is the only thing I can think of that has had an icon sometimes and not sometimes.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mcastro90:
I'm having randomly dead droid icons on my app drawer that looks when installing an app and it never finished after apps updates. They cannot be removed from the drawer and cleaning caches from apps store don't seem to remove them. (I'm on Lineage Stock Launcher with latest January build).

I don't know if it something with GPS, F-Droid and if anybody else has this behavior too.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Replying to myself as well. I figured out the dead apps thing for me at least. It is the stupid "trichrome library" thing that shows up in orphan data in TiBu every time Chrome updates. I look at it for how long I have been able to dirty flash my P3 without a full wipe. I am up to ten instances on the P3. Fortunately, they don't show as freeking apps in Pixel Launcher or Lawnchair.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nr7777:
I second this would be amazing!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] miki4:
That would be awesome indeed. I cannot find even one current custom ROM without Gapps preinstalled.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] supachris:
AFAIK the Google Camera will not work without GApps. Maybe this is the reason
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] :
Google Camera works smoothly with MicroG instead of Google apps on LineageOS 16, but I'm not sure if MicroG is compatible with LineageOS 17.1 or Android 10 at this time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wishx:
CalyxOS is Android 10 with microg already installed and no gapps from the start. I'm running it now and I love it. I rooted it with Magisk as didn't look the bootloader afterwards (as they recommend) because I don't need that, just no gapps.

https://www.calyxos.org/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zehlek:
What does it have? Any screenshot anywhere
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wishx:
It's just AOSP with micro and a couple custom bits and bobs. Don't expect it to be a tricked out mod with every whistle and bell thrown in from every other mod out there. It's Android 10 with microg. Period. Enjoy. :laugh:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rockingondrums:
Or LOS 17 with full Stock Pixel Gapps preinstalled!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Alpha1BA:
How long for registration??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Alpha1BA:
[MENTION=614507]razorloves[/MENTION] would it be poss to do a microg version in your next update??

is it possible to have this pre rooted??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Alpha1BA:
pretty pretty pretty please
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _Ra1n_:
I'm attempting to get the Google Phone app fully functional. Both Visual Voicemail and Call Screening are not working even with the Google Phone app set as the default. Visual Voicemail does work in the LOS Phone app, though. I'm running my own build; up to date sources with b1c1: Update proprietary files list cherry picked.

The following two logcat entries are likely the culprits:

DialerVvmLog: com.android.voicemail.impl.VvmLog.i:65 VoicemailModule.provideVoicemailClient missing permissions [com.android.voicemail.permission.WRITE_VOICEMAIL, com.android.voicemail.permission.READ_VOICEMAIL]
DialerUbiquitousRequirements: com.android.incallui.callscreen.coordinator.impl.UbiquitousRequirements.hasRequiredPermissions:57 missing permission: android.permission.CAPTURE_AUDIO_OUTPUT

I suspect the CAPTURE_AUDIO_OUTPUT permission is related to LineageOS restricting call recording in the US? I'll rebuild with call recording enabled and see if fixes it. Edit: I just realized call recording is configured by location inside the LineageOS Dialer (android_packages_apps_Dialer); it isn't some system-wide option. Enabling it likely won't fix this. Edit2: Yep, CAPTURE_AUDIO_OUTPUT is only given to system apps (or those signed by the platform key). Darn!

I'm not sure on the READ_VOICEMAIL/WRITE_VOICEMAIL permission.

Thanks for all of your work on this!

Edit: Disregard all of this, I guess. It randomly started working on its own. I have no clue what was preventing it from working prior to today; I haven't changed anything. MindTheGapps (or any Gapps package) should provide the required permissions & system libraries for the Google dialer to be feature-complete. I've included MindTheGapps in all of my personal builds so I have no clue why it wasn't working.

Edit2: Call Screening actually still doesn't work. It is still complaining about the CAPTURE_AUDIO_OUTPUT permission.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] infamous_black:
Using this as my daily driver. Noticed a few minor bugs but nothing to serious. Keep up the great work!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Furby4284:
Unable to boot to boot.img

I have been unable to get this ROM installed. I purchased a new Pixel 3 XL almost a year ago which I never used. Decided to install LineageOS. When I do "fastboot flash boot boot.img" (it appears to install to slot b successfully) and then I hit volume up to get to "Recovery Mode", it reboots immediately to fastboot again with "Enter reason: error booting boot.img". I've tried with several boot.img files including 20200115, 20200110, 20200108.

Device state is listed as "unlocked". Does anyone have any suggestions? Anything I can try?

I currently have factory image crosshatch-pq2a.190405.003-factory-379f92bd.zip installed. Should I be using a different factory image to start from? What might cause this?

BTW I've also tried installing from the latest TWRP, but I got an error on the install of the ROM zip file. Since this thread doesn't suggest using TWRP, I figured that wasn't expected to work.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fratletimac:
How to install Android updates with Google Pixel Repair Tool - 9to5Google

https://ww.9to5google.com/9:jQA0lQV...B11lPAqmPDcI29eI2guUGKynPEbUGSulPOylr10k29bUf
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] supachris:
You have to bring the Pixel to Android 10 first. The base version must meet the version of the LOS 17 version. Currently you have to flash to the January 2020 Q stock version. You can do this with the Google Factory images.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Furby4284:
Thanks a bunch for your reply. This appears to have solved the problem. I can now flash the lineageos ROM using ADB sideload from the boot.img recovery.

But now when I reboot to recovery after installing the ROM and try to 'adb sideload open_gapps-arm64-10.0-pico-20190928-BETA.zip', I get "Insufficient storage space available in System partition". Am I supposed to boot Lineage first? I always thought I wasn't supposed to boot first.

Any further assistance will be greatly appreciated. Is there another gapps I should be using?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] supachris:
You cannot install Gapps in this way. For this reason the Gapps are already included in the ROM.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
new builds with February 2020 security patches from google [emoji106]

blueline rom zip - https://androidfilehost.com/?fid=4349826312261719447

blueline boot img - https://androidfilehost.com/?fid=4349826312261719448

crosshatch rom zip - https://androidfilehost.com/?fid=4349826312261719459

crosshatch boot img - https://androidfilehost.com/?fid=4349826312261719458
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
Anyone run in to issue like this with apps that are partially "installed"?

The app info doesn't lead anywhere and the icons persist across reboots.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _Ra1n_:
Yes. It is a bug in Trebuchet (the default launcher). While an app is downloading/installing a temporary icon (with a progress ring) is added. The issue is the placeholder is never removed after the app installation completes. They shouldn't show up on other launchers.

It was mentioned a few pages back: https://xdaforums.com/pixel-3-xl/de...l-blueline-t4010943/post81568425#post81568425
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
Thank you! Tried searching but didn't see anything.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gunner1253:
Noob Question

Can someone please explain the difference between the blueline rom/boot img and the crosshatch rom/boot img? The instructions only mention flashing the boot.img and then applying the rom, but doesn't specify which pair to use? Apologies if this is a stupid question, but I've installed lineage on other devices and don't recall having two sets?

Thanks in advance.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _Ra1n_:
"crosshatch" is the codename for the Pixel 3 XL and "blueline" is the codename for the Pixel 3 (non-XL). If you have a Pixel 3 XL, you have to flash the "crosshatch" ROM; otherwise, if you have a Pixel 3 (non-XL), you have to flash the "blueline" ROM.

For reference, these codenames come directly from Google: https://developers.google.com/android/images
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gunner1253:
DOH! I didn't even think about the fact each Pixel gen has two models (so far).... Thank you!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wangdaning:
Actually, there are 4 now. Pixel 3a(xl) ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] :
Since TWRP's support for the Pixel 3 XL on Android 10 will be delayed, is this device still eligible to be officially supported by LineageOS 17.1 without TWRP?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Just check the first post! :svetius: the modified boot.img allows us to apply unsigned updates via stock recovery.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _Ra1n_:
TWRP support will not be an issue. The LineageOS device requirements will be adjusted for 17(.1) and require device maintainers to support using the LineageOS recovery for initial installations and updates. TWRP will not be required, but once Android 10 is supported with TWRP, it should still function with LineageOS.

See the following commit: https://review.lineageos.org/c/LineageOS/charter/+/265936
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] queuecumbr:
For some reason I can't enable WiFi calling using lineage. Is this a known issue? I should be able to have WiFi calling since I'm on Xfinity mobile. It just gives me an error saying "Unable to activate WiFi calling. Please try again later."
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] uglatto:
Is anyone else having trouble generating ??????? ??????? ????? on this rom? Fantastic job otherwise!

Edit: Hmmm, its just the on site tell.wtf and a few others. I was able to get viewable characters via the fsymbols site. Odd/specific problem, just bringing it up because it worked fine on stock, even tried multiple browsers, must be something weird about the way those sites are coded.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
new builds

blueline rom - https://androidfilehost.com/?fid=4349826312261728583

blueline boot img - https://androidfilehost.com/?fid=4349826312261728575

crosshatch rom - https://androidfilehost.com/?fid=4349826312261728592

crosshatch boot img - https://androidfilehost.com/?fid=4349826312261728585

some notable changes:

* added lockscreen music visualizer - https://review.lineageos.org/q/topic:ten-visualizer

* added lineage wallpappers - https://review.lineageos.org/q/topic:ten-wallpapers+status:merged

* added context-aware Bluetooth in airplane mode - https://review.lineageos.org/267480

* updated canadian apn's - https://review.lineageos.org/268667
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] PantherXtreme:
Thanks for the phenomenal work Dev.

Just a question, perhaps it's been answered, has anyone experience the error " reboot to recovery to gain system write permission" message when attempting to use rooted app on this tomorrow. I already patched the boot image with magisk and flashed it via fastboot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
i think i see the problem. from the looks of your log wifi calling is probably broke for everyone on verizon's network, including all verizon mvno's, like xfinity mobile.

can anyone else on verizon's network confirm that they can't enable wifi calling? if they can enable it, does wifi calling work? thx

steps to turn it on - https://www.verizonwireless.com/support/knowledge-base-219991/

here's a test build to try out. let me know if it fixes that problem. thx

crosshatch rom - https://androidfilehost.com/?fid=4349826312261729080

crosshatch boot img - https://androidfilehost.com/?fid=4349826312261729081
[LG K20 Plus Questions & Answers] chugs:
Hello. Im trying to use my old k20 on a new network. The doner sim card fuctions fine on 3 other teat devices. However it is not unlocking from Metropcs. Its been in my drawer for a while and can not find the original sim card. Whwn i insert working sim there is no Sim card detected. The Device Unlock app states both Pass and Fail.. What am i missing?