yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] team_gold:
[MENTION=3707711]jorgen2009[/MENTION]

Thanks for putting this together! I flashed the 3/17 build from stock and nearly everything seems to be working great.

One problem is that I can't send / receive MMS. I use Sprint and I have a feeling its more of a Sprint issue than a Lineage things. Out of the box Phone/SMS worked. I dialed the sprint network reset *#*#72786#*#* and that got data working.

Seems like previous versions of Lineage have had similar issues that could be resolved by messing with the APN settings. That doesn't seems to be a setting you can easily change anymore. I flashed the /system/etc/apns-conf.XML from stock (were it was working) and that doesn't seem to have helped.

Any ideas?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
You can still change the APN settings. To do this go to Settings - Network & Internet - Mobile network - Advanced - Access point names. Then click on the name of the APN you want to change (nor the selector). The APN settings are displayed there. When you touch any setting you can edit it. Then finally when you changed everything you wanted to change touch the 3 dots in the upper right and touch Save
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] team_gold:
There isnt Access Point Names in the Mobile Network menu. If I use the setting search I get nothing for Access Point Names and APN as well.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] team_gold:
I flashed AOSiP and dotOS and I had the same problem Phone/SMS work fine, Data works with some finessing, but I cant get MMS working. There must be some package from the stock rom that I am missing that Sprint needs for some dumb reason. I tried flashing the 20190307 build without gapps and then flashing the Super Open Gapps package, but it failed saying the system partition didn't have enough space.

If you have any ideas I would appreciate it. I am gonna keep poking at this since it seems specific to Sprint. I don't think that changing the APN would do much at this point but any idea why I can't see that menu?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
A few days ago I was testing another vendor tree than the default one from TheMuppets. As it was a lot bigger than my normal ROM and I couldn't find any benefits myself I reverted back to TheMuppets. I placed it in the TEST folder on my download page. Could you try that build and report back if it works for you?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
Another week, another update. This time, among many other things, for anyone that uses multiple users on their phone they patched the navigation-bar-not-appearing-after-switching-users bug (that's a mouth full lol). You can find the build on the link in the OP
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] micha04081986:
Hey!

On first instalation, after flashing the Rom in twrp i was Landing on the stock recovery and it doesnt boot lineage os. Whats wrong? I instaled only the Rom. thanks
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] KittyRgnarok:
Rom works great been running for a week but was wondering if there was any way to bring back the "notification peeking" settings from oreo
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
Hey!

On my first trip with my new car it doesn't drive. Whats wrong?

Just saying things don't work isn't enough. Like driving a new car, read the fine manual, or OP in this case. Just follow the directions and it should work. You're welcome :)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jeekajoo:
Just wanted to say : thank you [MENTION=3707711]jorgen2009[/MENTION] !

I've been using this rom for a week now and I'm happy with it. It's stable. Just 1 thing that crashes : the tool "markup" to edit screenshots. But I guess you can't do nothing about it, and that it has nothing to do with your work.

Cheers
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] micha04081986:
Hey! Sorry for my short post. After a second instalation from beginning it work. I'm on Lineage OS and I'm very happy ?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
No, you're right, it's not up to me to change that. Added it to the bug list, thanks
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] roblav96:
[MENTION=3707711]jorgen2009[/MENTION] I just want you to know how much I greatly appreciate you providing these lineage builds. =]
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
I've always been a fan of LineageOS and since I've built it for many of my own devices in the past I was very eager to build it for the pixel 3. Unfortunately our phone is a bit neglected compared to the XL (although there are also builds for the regular 3 in the XL forums), so that's why I'm sharing my work for others to try as well. I'm glad you like the builds, that's reward enough for me to keep sharing them:)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] roblav96:
How-to play store device certified

Flash lineage zip as instructed in OP

Reboot to bootloader which will put device on opposite slot

fastboot boot twrp.img

Flash magisk canary release zip https://github.com/topjohnwu/magisk_files/blob/63e96b05256c119f4d6a419bc445085c6cface97/canary_builds/magisk-release.zip

Reboot & profit
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
Another week, another update of the rom. As always you can find it in the OP. Happy flashing
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] hi_im_jason:
Hi [MENTION=3707711]jorgen2009[/MENTION],

Thanks so much for the work you’ve put into building this image, compiling clear OP about the original install, and keeping the build updated!

Since you asked, I just wanted to report my experience with the Pixel 3 XL (crosshatch) as opposed to your Pixel 3 (blueline). After fighting with different approaches and combinations all day, I can't get it to boot past the white Google screen. It seems [MENTION=3299991]rabarkar[/MENTION] and [MENTION=9741843]Kyujay[/MENTION] have had similar experiences:

Here’s what I did:

Flash March factory base image (bootloader.img, radio.img, and image.zip extracted from crosshatch-pq2a.190305.002-factory-dc7e9ca4.zip). I used your monthly-flash-all.sh script, so I believe it flashed to both slots.

Boot to TWRP, wiped Dalvik and Cache [tried also: factory reset]

Flash LineageOS ROM (your posted lineage-16.0-20190327-UNOFFICIAL-crosshatch.zip)

[tried with and without] Also flash TWRP (twrp-pixel3-installer-crosshatch-3.2.3-5.zip)

[tried with and without] Also flash Magisk (Magisk-v18.1.zip)

Reboot leads to stuck white Google screen. I waited 10-20 minutes before giving up.

I tried starting with the February base (bootloader, radio, image) instead to no avail (though per your 9th March 2019 post, it seems using the February base is no longer recommended). I’ve probably tried 15 major or minor variations, and all seem to lead to the stuck Google screen.

Any ideas? Anything else I should try? Or any other information I can give about the process? It seems others may be getting stuck at this stage too.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] codygs83:
Try a full wipe.

Then flash the rom and twrp only.

If it boots setup for the first time then reboot to flash magisk.

This is the process I use running dirty unicorns as magisk borks something on the first boot and it hasn't been fixed yet.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
Thanks for trying on the XL! Much appreciated

Yes, a full wipe is absolutely needed for the first installation. Otherwise than that I have no idea. In the meantime I made a new version, this time without GAPPS. Try flashing that after a full wipe and you installed a stock image on both slots. Also, don't install another kernel, recovery or Magisk for the first time test, so just the ROM. We need to rule out some things first. Too bad I don't own the device...
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] NOTilyass:
Is this rom as smooth as stock ?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] ShadowJP88:
Will the April update be in the next week update?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] neitin:
Wrong post please delete
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
For me it is, but YMMV

Depends if it's already merged by the LineageOS team before the weekend. If not I'll compile a build as soon as it it's merged in. So the next build will contain the April patches.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] hi_im_jason:
Thanks for the suggestion. I've tried this, to no avail (see details below).

Thanks for posting the new version. Sadly I haven't had any better luck with it than with lineage-16.0-20190327-UNOFFICIAL-crosshatch.zip.

First, two notes on your monthly-flash-all.sh script:

Running the line fastboot --slot other produced an error for me, so I changed it to fastboot --set-active=other. I've also tried explicitly setting the slot to a, flashing baseband/radio/image, setting to b, flashing baseband/radio/image, and setting back to a using fastboot --set-active=a and fastboot --set-active=b. Nothing I tried produced a different outcome. Note I'm on fastboot version 28.0.2-5303910.

The script runs fastboot update image.zip --skip-reboot twice, one for each slot, but the fastboot documentation indicates that update already flashes both partitions (fastboot --help -> "update ZIP Flash all partitions from an update.zip package").

Here's a list of what I've tried, none of which ever resulted in getting past the white Google screen:

Attempt: baseline

fastboot boot twrp.img

Wipe -> format data, reboot -> bootloader

./monthly-flash-all.sh # edited per above

adb push lineage-16.0-20190401-UNOFFICIAL-crosshatch.zip /sdcard/

Install that, reboot system -> stuck on white screen (waited 4min)

Attempt: "format data" in addition to "factory reset"

fastboot boot twrp.img

Wipe -> format data, wipe -> factory reset, reboot -> bootloader

./monthly-flash-all.sh # edited per above

adb push lineage-16.0-20190401-UNOFFICIAL-crosshatch.zip /sdcard/

Install that, reboot system -> stuck on white screen (waited 8min)

Attempt: NOGAPPS version

fastboot boot twrp.img

Wipe -> format data, wipe -> factory reset, reboot -> bootloader

./monthly-flash-all.sh # edited per above

adb push NOGAPPS_lineage-16.0-20190401-UNOFFICIAL-crosshatch.zip /sdcard/

Install that, reboot system -> stuck on white screen (waited 7min)

Probably silly attempt: ROM only, no base image-crosshatch-pq2a.190305.002.zip

fastboot boot twrp.img

Wipe -> format data, wipe -> factory reset, reboot -> bootloader

./monthly-flash-all.sh # removed line: fastboot update image.zip --skip-reboot

adb push lineage-16.0-20190401-UNOFFICIAL-crosshatch.zip /sdcard/

Install that, reboot system -> stuck on white screen … (waited 7min)

Probably silly attempt: NOGAPPS ROM only, i.e. no base image-crosshatch-pq2a.190305.002.zip

fastboot boot twrp.img

Wipe -> format data, wipe -> factory reset, reboot -> bootloader

./monthly-flash-all.sh # removed line: fastboot update image.zip --skip-reboot

adb push NOGAPPS_lineage-16.0-20190401-UNOFFICIAL-crosshatch.zip /sdcard/

Install that, reboot system -> stuck on white screen … (waited 10min)

No dice on any of that. Open for suggestions of other stuff to try. Do we have any reports of successful installs on crosshatch?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
First of all thanks for the thorough testing, you're the first one actually giving me some feedback.

I changed the script a bit, you were right, slots didn't change, so basically the image was flashed twice to the same slot. As for the update, if you watch the update progress in the terminal you see that the other slot only gets 2 (system) images flashed as opposed to the 9 of the active slot. Have a look in the update.zip file and you'll find a system.img and a system_other.img for the other slot. All other images in the zip file are only flashed to the active slot (including the very important vendor.img), that's why we need to update the second slot as well. The script uses --skip-reboot, because a normal boot follows with a normal update and we want to remain in control of the entire fastboot proces for the second slot and booting to recovery at the end to flash LineageOS.

To be honest I have no idea why the ROM doesn't boot. The same reason probably why the blueline ROM without GAPPS won't boot either, I haven't found out that either. For some reason including GAPPS for blueline makes it boot normally, unfortunately for crosshatch it doesn't boot either :( If anyone has a clue why and also has a solution I'm more than willing to see if I can make it work. Until that time I'm afraid there will be no crosshatch version from my side...
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] KittyRgnarok:
I was also looking through the script when I flashed mine and had to fight with it for hours before deciding I would manually switch slots and flash it. I meant to post here but never got around to it, my bad.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
The script is and always was safe to use if you followed the instructions. The only thing not working was switching the slots so it flashed the Google image twice to one shot. If you flashed LineageOS on the untouched slot it might have given you boot loops. But that's fixed now
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] KittyRgnarok:
I didn't say it was unsafe or causing bootloops. I just wanted it done right and it didn't properly switch slots which I failed to report. Glad someone got around to it though
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] MS.:
Installing Pixel Launcher didn't help. I can see weather on a widget but not on lockscreen.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] hi_im_jason:
Sure, glad to!

NP, and thanks again for trying just in the name of helping the community.

If anyone else out there gets Lineage to work on Pixel 3 XL, I'd / we'd be happy to hear what worked :).
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
I just uploaded a new rom with the April patches in. It's a bit larger, because I used other, more complete vendor files from Dirty Unicorns inserted of the Ives from The Muppets. Don't forget to update your vendor.img

Happy flashing:)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jeekajoo:
Thanks much !!

Does this mean "Active Edge" could be working (with the help of https://github.com/Magisk-Modules-Repo/active_edge_system_mod) ?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
I highly doubt that, it needs a lot more than a few binaries, but why don't you try and let us know? :)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
I just compiled a new rom from today's sources, the last one with the April patches in. As usual, see the OP for the download link. Happy flashing :)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] mworl:
Without OpenGapps?

First of all thank you very much for taking the time to make and release this.

I have been using lineage on my last couple phones but know nothing about compiling and such. I would very much like to try to run this phone with microG, which it seems should be possible after patching for signature spoofing. I have been reading up on this and understand the security risks involved but on my phone I am more concerned about privacy than security.

So my question is, is it possible to flash this rom without any OpenGapps package? Or if it is not a difficult task would you be willing to compile a version without OpenGapps for blueline? I would be willing to pay you for your time if so.

Thanks

Edit: Should have read through the thread first. I see it doesn't boot without gapps for an unknown reason, damn.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wintrxtrem:
Is it likely Pixel 3 will become officially supported by LineageOS? I'd like to get one and run the microG Lineage but they only build for official devices : \
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
I can't say anything about it, but so far only the Pixel 1 is officially supported. Let's hope a proper maintainer for our device stands up to make it happen. It won't be me though, my coding skills are way too low for that
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] collapsinghrung:
There was an official statement from LineageOS linked earlier in the thread ( reddit /r/Android/comments/aw083c/lineageos_160_builds_start_tonight/ehjalju/?context=3&st=jvhcs1dj&sh=d778e8d6 , URL incomplete because this is a "guest quick reply"):

"""Pixel 1, 2, and 3 series are all ready to ship.

We used to allow device maintainer's to rely on installed pre-built vendor images, and demanded they additionally assert necessary firmware to abort installation if the firmware was too old.

As of 16.0, for a viariety of reasons (one of which that the popular method we used to use to "assert" and prevent installs on old firmware no longer is feasible on A/B devices due to the new payload install format) we decided that we would require that a vendor image of some sort must be shipped on devices who rely on them, as it's bad UX/dangerous to not do some on some devices (Moto A/B devices for example hard brick if you install a Pie build over Nougat firmware, and we can't have that happening).

At first, it was the plan to allow prebuilt vendor images. Due to infrastructure limitations (not space, bandwidth, and no, we aren't looking for help on this), we have all but decided this isn't feasible.

We'll be building vendor images for all device's who rely on them (as you've likely seen in the many recent commit chains to do so on gerrit). So far, only the OG Pixel's have the groundwork done to build a vendor image inline, but its less than a days work for the P2/P3 maintainers to do so.

The reason this wasn't done sooner is that the common belief was that we would be able to use prebuilt vendor images until just before our planned ship (this is no one's fault, to clarify)."""

This other person seems to be fairly generous with your time. :D

I'm not saying this means you should be doing anything more than you're already doing -- but could you explain what this comment means? I can't say I understand it well.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
Remember I tell you every month to update your vendor image because of the new security patches Google implemented in the Android sources? What this means is that Lineage is trying to build the vendor files directly in the ROM, so you don't have to update the vendor image anymore. It's already merged for Pixel 1 and that is official. You would still need the bootloader and radio, but usually you don't HAVE to do that (although I do recommend it strongly). There are already some commits in the Lineage sources for that to happen for Pixel 3. I tried to build it with these commits, but there were lots of missing files while extracting the vendor files from the stock image. Probably because the extract script is specific for crosshatch, not blueline.

I made another build with the 'normal' sources as well and placed it in my download folder (see OP). Until the open commits are merged you still have to update the vendor image. Happy flashing
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] ShadowJP88:
Am I the only one having trouble with the Rom?

Android auto have lots of difficulties to read messages and to start listening to me.

I can't figure out how to make Google pay work again with magisk on.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] optionalmgrr.la:
i heard battery life on Pixel 3 (not XL) is not good, I wonder what you guys getting for SOT in this ROM?

Thanks.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] vimjam:
SOT is fine for me , Im using LOS as is. No custom kernel or other battery optimizatioms.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] vimjam:
I don't use either but have you had success with other ROMs ? What error message do you get when you try to use google pay ??
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] ShadowJP88:
The app tell me that I can't use my phone to pay
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] optionalmgrr.la:
7hr SOT? oh mine that's very good
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] drocny87:
How do you get such good battery life? I'm currently on a different rom and get maybe half the battery life you get.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] vimjam:
Well looks like 5-8hrs sot is the norm people are reporting in at Pixel 3 real life sot reviews. Although I did not flash any kernel or battery tweaks I did do some automation to get the best of my battery.

1. Toggle location on/off when opening/closing maps

2. Set mobile data off when WiFi is on.

3. Toggle WiFi off & battery saver to on during sleep hours (midnight) & toggle it back early morning

4. Greenify apps which do not need background service worker running.

5. Turnoff Bluetooth when wireless headset disconnected

6.set NFC to off

7. Utilize dark mode on all possible application I use.

As you probably know it also depends on how battery hungry your use case is (calls, games will cost a lot more battery). I use macrodroid to automate some of the stuff specified above.

---------- Post added at 11:29 PM ---------- Previous post was at 11:12 PM ----------

This might not be much help but Can you do a safteynet check in magisk manager and see if the status is green ?

If this is in failed & mismatched state then you probably need to install magiskhide or whichever module hides root.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] ShadowJP88:
Yeah, Safetynet did pass, I'm on the canary chanel if that can help
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Archmag3:
Can anyone please guide me as to how I can install the original google camera with all its functionality on this ROM ? :)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] farbeyondoverkill:
I use cstark's Gcam mod and its the same thing as the original with some extra functionality. Just install the apk from here: https://xdaforums.com/apps/google-camera-mods/gcam-google-pixel-1-2-3-t3875663/

Also, if you want some extra performance and camera quality you can install this magisk module here: https://xdaforums.com/showpost.php?p=78520564&postcount=243

Just make sure you have installing apps from unknown sources turned on and you should be good to go.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] waingro808:
I thought if you install the right GAPPS, you get the original camera?

EDIT: nevermind, I see you don't flash gapps with this ROM. OP is including nano gapps. Maybe ask OP to use "Stock" gapps package, which has google camera.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] optionalmgrr.la:
sorry just wondering if we usually have official LOS for pixel phones in the long term?

thanks in advance.

---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------

can we use opengapps + stock gcam apk on this rom?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jorgen2009:
Lineage for our device is planned, but as always no ETA.

Regarding the gapps is already in the ROM and the camera can be installed normally through the play store. You will have the exact same camera as on a stock ROM then.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Archmag3:
The gapps included is nano gapps and doesnt have a pixel stock cam, the camera than you can install from playstore is google cam not the one that comes with pixel :(
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Portgas D. Ace:
:eek: The Google Camera from the Play Store is exactly the one that comes preinstalled on Pixel devices. Not sure why you think that this is a different app.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] farbeyondoverkill:
Did you see my post? Cstark's Gcam is the same as the stock pixel camera but with extra functionality. I suggest you try that before complaining about the lack of stock Gcam again.