yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Got it! The first time I misunderstood the step (my bad, I'm used to the old android 6 ways of ROM/Root) about rebooting before GAPPS, but I restarted with sideloading LOS, then the reboot directly to recovery (used to TWRP, but like LOS Recovery now that I'm used to it), then GAPPS. All is wonderful... Except... One thing I want to make clear before I do it - I'm about to do Magisk (also new to that). Magisk says best way is to patch my boot.img and then load it. From notes I'm seeing on LOS installation wiki, the boot.img IS the recovery img for LOS 18.1? Just want to make sure before I mess up what is currently working great.. Thanks!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] zhouyh:
Thanks so much for you replay! When I use official Android 12, the face unlock always broke down (Clean the top of your screen, including the black bar). It is very boring. So I want try the Lineage os.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Zenjir0:
Thank you I was able to get everything installed. It does seem to be TWRPs fault for not being able to install OpenGapps correctly and I needed to install via sideload. I did try to do sideload through TWRP but it also failed but not on LineageOS boot.img so pretty sure the issue was TWRP all along. I can't install TWRP because if I do it can't boot into system and I also think if I did Magisk would not work. So I just have to wait for TWRP to mature more. I mostly only used it for doing a full device backup.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kaykhoso96:
My P4XL went into EDL mode for no reason. Everything was okay at night time.. then I woke up to dead phone.

I was running Android 11 public beta at that time.

Several other people had exact same issue reported on Reddit. But you are right that its very very few unfortunate ones who had that problem on P4XL.

Majority of EDL dead phones were P3.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
True, PX3s and a few 4s but as you pointed out, you were running a beta. Normally I wouldn't expect a beta to damage anything, but anything can happen with beta.

I can assure you, I swap firmware's, ROMs, kernels, Android 11 --> upgrade 12, downgrade to 10/11, all the time (pretty much every 2 to 3 days to help other users so I can reproduce it) No EDL issues here. I use officials or custom ROMs but not so much beta firmware.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
You actually can do both TWRP with ROOT/custom kernel and have it boot, but I don't recommend it. It broke my updater when I tested it (OTA). You can install TWRP after ROOT/KERNEL by installing the TWRP.img in TWRP itself (not the .ZIP). The TWRP .IMG is an install image as well as a BOOT package, which will do it for you, but don't. Stick with ADB SIDELOAD temp boot and/or sideload the installs in the OP steps and you will be fine.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Who is this directed towards, and do you need help?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
If anyone is wondering, magisk beta 24 works well with LOS. I'd recommend changing the feed within magisk app config to use the beta channel and update the app and magisk itself through magisk directly. That's how I did it and it works well!!

--EDIT UPDATE-- YES it works well, BUT I do have issues with SafetyNet so I am working through them so for now, hold off on upgrading tot he BETA MAGISK (stick with ver23).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
OK final update on MAGISK 24 (BETA but it's about to be mainstream) so better to be ready now, then be late and not know how to do something, causing issues!! I got SafetyNet working with MAGISK 24 Beta, you need the following (ZYGOTE MUST be ENABLED in MAGISK 24), + SafetyNetFix (ZYGOTE). Reboot after enabling ZYGOTE in MAGISK settings, then reboot and test.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
***WRONG POST***
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] hi_s10e:
could soli be activated after flashing the rom? possible? or maybe unofficial lineage with soli...
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ryu945:
Does this ROM support Volte for the Pixel 4 XL?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] rafsteam:
To all the users:

Would your recommend to switch to this ROM from the stock one? Is everything working as it should? I have problems on stock with Bluetooth connection to my smartwatch (notifications not going trough sometimes) and battery life of Pixel 4XL seems to be quite low. Would this rom improve?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I'm my opinion yes to both because you can tweak everything within LOS so my battery life is phenomenal. But I don't have any BT issues on stock or LOS so I can't comment there but everything else, definitely will improve!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] rafsteam:
Great! Maybe will try LOS + Magisk(with all the GooglePay/SafetyNet mumbo-jumbo) + Kirisakura kernel combo.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
you most def should! you wont be sorry!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xikotenkalt01:
which version of kirisakura is compatible with LOS?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
LOS 18.1 is A11 so any of the A11 ones will work fine
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] skothiya:
I am not able to root via magisk boot.img method.

After flashing magisk boot.img device restart but touch is not working.

I also tried magisk.zip method but faced same issue.

Than how do i root?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
You're doing something wrong then, ROOT/MAGISK on LOS works perfectly fine. You simply need to patch the boot.img then flash that to boot but don't use whatever zip method you mentioned. ONLY use the patch boot method. Also what kernel are you using, stock or 3rd party? If 3rd party, flash back to stock, ROOT and try again then let us know the results (but only use the patch boot method).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] skothiya:
I used patch boot method and tried to root on lineageos stock kernel.

I successfully root on stock rom.

I used stock rom boot.img for patch.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
How are you getting the LOS boot.img? Make sure you're patching the LOS boot, but not the bootloader or stock boot. I know it gets confusing but you can only use LOS boot with LOS so you must patch that LOS boot. I've seen it many times before, users patch the stock boot by accident or the LOS bootloader image but not the boot.img.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] skothiya:
Got it your point.

Thanks.

How do i get lineageos boot.img?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
no worries, its what I figured happened when you said the touch stopped working. Thats almost always an indicator of a wrong boot.img used. You need to get it with the DL of the ROM, follow the same link but grab the boot.img and patch then use only that image:

LineageOS Downloads

download.lineageos.org
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] skothiya:
I will try.

Than you.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
all set now?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] skothiya:
Yehh, thanks for the help.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Is there still an issue with the trebuchet launcher and icons disappearing sometimes? I'm loving lineage OS but my wife just called and said a bunch of her icons disappeared. This happened to me a while back and I just put them all back on and wrote it off as some kind of an issue I had caused myself. But after her call, I did some googleing and discovered that this could be an issue with the trebuchet launcher. Has anybody seen this? Is there a fix other than switching to a different launcher?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] insestito:
Install Nova Launcher...
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] insestito:
March 20 Update changelog:

Spoiler content hidden.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
agreed, I only use Nova premium, and never have this issue
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] zhouyh0701:
When will the lineage os19 based on android 12 be released?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] insestito:
New update 2022 03 28

Changelog:

Spoiler content hidden.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
delete (I broke the comment) :)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
My guess is when you build it for us, then share it out :poop: JK. Seriously though, we don't allow ETAs to be asked, ever. It annoys the devs and if we annoy the LOS dev, we may lose the ROM so this is why we do not ask for ETAs. That being said, I was joking with my build comment, but seriously, anyone is free to bake their own flavors of LOS. If you do, please share them as unofficial ROMs, otherwise wait until Eamo5 or someone like us, bakes it.

I often say I am going to bake my own LOS11 or A12, but I never find the time to finish it, I get it going, then get pulled away by some work disaster, and never return. I doubt it will be me baking LOS A12, but I will try to get to it if I have time. This is also assuming the code exists for LOSA12 (I dont know yet). I haven't reviewed anything, so I have no idea right now if there is even a LOS A12 tree yet, but I assume there is and will review when I have time.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Mykemonster:
Good afternoon.

Install the android 11 Mini gapps and configure the Google assistant but it does not react when "Hey Google" is mentioned, I emphasize that it is already configured as the default assistant in the system.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Nope. Installed Nova a couple weeks ago. Today I had lots of app updates, and my phone has been up for over two weeks, so I made a nova Backup, and rebooted. Phone comes back up, all app icons are as normal, most widgets are good, but chrome shortcuts to urls are gone, mix explorer shortcuts are gone, and things like drive shortcuts are gone. I went into nova launcher, did a restore of the backup I did right before rebooting, no change, nothing came back.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I have never had that happen (ever), and I use Nova (pro) as my ONLY launcher (unless testing something to help others). I use the same Nova backups across the board on ALL my ROMs (Android 8/9/10/11/12). They can all reuse the same backup - if the backup is taken correctly am successful). I use the SAME Nova backup on Android 9 (Nexus Tablet), as I do with Android 11/12 (pixel 4 XL), and what you just described with missing apps has ever happened to me before nor have I heard of it before. The only time apps are missing from my restoring Nova, is when I didn't physically install those apps. Then they disappear (with a link to "find" in the PlayStore, but otherwise nothing is lost, moved, or even out of place. Meaning the apps, settings, features, functions, gestures, whatever I have set in Nova and saved successfully in the backup, is restored to the new device without failure. I have even used the SAME backup files from one device, to another device using a different Android level 9wihtout issue). Nova backups are rock solid, so I need more info to try and help you.

Can you explain how you backed up Nova (did it save successfully to the documents folder) - assuming you are on LOS18.1 (A11), but not A12? A12 doesn't allow the document folder to backup/save so are you 100% SURE everything backed up successfully? I only ask because before I realized A12 was the cause (unable to save in Documents), I kept having backup losses but I couldn't understand why at first. If the answer is yes, and yes it is its backing up properly, then thats good, but how the about the restore step? Did it work, or did you have any hiccups? If you had hiccups, what were they?

I am mainly concerned about the "shortcuts" you made in Nova, where/how you did so? Can you explain this in depth please so I can help fix it?

Also can you list out your build process (ROM and Nova / restore of Nova), I don't need a deep-level but high level in regards to how you are using Nova (and restoring it)?

Android 12 breaks the backup/restore locations so it works, but you have to bury it within a folder you can write to (thats the ONLY hiccup I ever have). Its not even an app bug, but solely due to Google and Google locking down the filesystem structure/permissions/compression. Android 12 is perfectly fine IF you ALREADY have a backup taken (any Android level works) as long as backup is successful.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Ok, when I posted this message, I also sent a message to Nova Launcher support - they replied back yesterday saying this is expected behavior. Any app icons or widgets will be backed up, but Google (for quite some time now, he says) doesn't allow him to back up things like chrome shortcuts, drive shortcuts, any shortcuts that refer to a URI/URL.. That's the behavior I'm seeing. As for your other questions, I installed step-by-step from the LineageOS installer instructions, and have had no issues other than this one (icons sometimes disappear after a reboot - the Google bug).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Oh wait, I might have misunderstood your comment with what you mean by "backup". Please clarify the " backup" you used? Was this done through NOVA (nova settings / backup/restore)? OR do you mean using backup through Google using the Android backup (settings / system / advanced / backup)?

If you're saying that Google backup doesn't work, yup, that's to be expected (Google backup isn't intended for those settings). BUT using NOVA to manually backup NOVA settings, you'll NEVER have an issue. The NOVA backup will restore every icon to the same original location, with the same name, settings, icon, everything. It even restores the app shortcuts WITH custom icons when the icon pack ISN'T installed yet. Meaning NOVA backup/restore is SO efficient that if you apply icon packs to your app/shortcuts, when you backup/restore NOVA, it will ALSO restore the icon packs using your custom settings EVEN BEFORE YOU INSTALL THE ICON PACK. I know because I do this as my FIRST rebuild step as it lays out my droid, with all shortcuts back including any customization I did to them before backed up.

Nova restore will also show you the original location and any missing / not installed apps. Those missing apps will show as a direct Play Store link to reinstall (taking you directly to the app install). It's an amazing app, the devs for NOVA are REALLY good and they think things through so nova is awesome in my book!! Because of the missing app links, NOVA is the first app/restore I perform when building a new device so I can easily reinstall missing apps! It's GREAT!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
I hear what you're saying.. all my APP icons restore, but chrome shortcuts (web links) don't.. here's the reply I got from nova launcher ?dev?..

...................

Third party launchers aren't allowed to backup and restore shortcuts due to security and privacy reasons. That's something Google changed quite some time ago and has no plans to ever change again.

People on the forums are lying to you, and only what you stated in the first statement above is true. Google doesn't allow it so that you don't create a shortcut to your bank app for example, someone else gets hold of your Nova backup, restores it and then has access to your bank stuff.

...................
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Sorry, yes, I'm talking about nova launcher backup, not phone backup
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Then please list what doesn't work for you (you can PM me if its long) because there shouldn't be a thing missed app-wise. Links and custom shortcuts (outside of NOVA or an icon pack) won't backup with nova but the apps and how they look will.

IDK what you're trying to do. The links is what I'm mainly asking about now so I can help you with a solution.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
What you just said is what I'm seeing. Apps and how they look works fine, but links and custom shortcuts don't get backed up. Prolly my misunderstanding, I originally thought Nova would back them all up.. thx
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Nope, not by design but if you explain them for me, I can probably help you with a workaround but I need to know whats being missed.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
What's happening is the google bug, that sometimes when I reboot my phone, icons go missing. App icons are all there in the correct places, but any shortcuts I've put on the homescreen that point to web pages disappear, shortcuts I've made using the google drive widget disappear, and shortcuts to local folders I've made using Mix Explorer also disappear. The only thing that remains after a reboot are app icons, and widgets that occupy some screen space, like the calendar, keep task list, etc. My biggest complaint (and this is a complaint against google and I'm just trying to find a way to not recreate them) is my web shortcuts - I have 20-30 of them on my screens and replacing them is very time-consuming. I'm thinking of just creating a webpage on my server with all my links so I can just go through one-by-one clicking, adding to homescreen, etc.. It's not a LineageOS issue, I just brought it up here because the initial searches I found on the web blamed Trebuchet launcher, and then multiple people pointed out that Nova Launcher would fix it via backup/restore..
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
ah got it! Thanks for the detailed explanation, and yes, I am sorry to say but neither NOVA nor Google can (or would) back those up. Those are all custom settings outside of normal app backups, plus you have noted multiple apps so no one app will backup all settings across multiple apps (out of the box). I am not saying you can't build, or script something that does it for you (because thats exactly how I do it), but not with NOVA or Google. You'd probably be better off making a few backups, then restoring each app backup one at a time (nova / mix explorer / + you also have mixed in system settings) so I few issues right off the bat. I can see at least 3 different services (probably more) that would require a specific backup to restore those settings (thats even assuming mix explorer can backup/restore), but you have to many variables in the mix for any single backup to succeed.

If this were me, I would reverse engineer it, one by one, and backup/restore/test what app handles what setting, then list it all out and know what needs to be restored, in what order, that way its not lost. This is of course assuming all 3rd party apps you are using to create said shortcut, can do this (backup settings).

For me, to not lose any custom locations (network/local/laptop/SAMBA/ETC), I use FX Explorer with root and paid add-on (not needed), then I create my shortcuts within FX, and use Tib (Titanium) to backup JUST FX. When I restore the FX app/data, so does the custom shortcuts within FX. This is the thinking I am getting add with my comment above.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Or better yet, Google could fix the bug that erases icons when you reboot, lol
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
lol but keep in mind, I don't have that issue whatsoever. I have NEVER lost an icon, shape, location, name, nada and I reboot when needed. That being said, again, I don't feel its solely due to Google but multiple other parameters that could be bugging out Google (or NOVA since thats your launcher).

Google positioning/icons appearing wont come as much into play (as NOVA would), if you are using NOVA as your launcher. Most likely you have NOVA set as the default app (launcher) so this is what's holding the positions so we should figure this out first. I don't know what else you have in the mix, but I move between ROMs all the time, and reboot without ever losing an an app or anything about the app (location, name, settings, ETC). I truly do feel something else is at play but IDLK what yet because I don't know your process.

All that being said, I need to ask, is NOVA your default launcher? If not, set it and test a reboot.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Yes, nova is my default launcher. That said, the same thing has happened on both nova and trebuchet, people on other roms/phones have reported the same thing, and I think Google has acknowledged it as a bug. Their solution is to do a factory reset, but I've heard some people say they did a factory reset and had the issue repeat itself afterwards so I'm not inclined to reset my phone occasionally in order to hope I can save my icons, lol. I feel like somewhere there has to be a database or XML file or something that describes the home screen layout that I could just back up occasionally and restore if it happens. This phone is my daily driver so I try not to play with it too awfully much. I'm rooted with magisk, still on A11 (A12 people still have the issue as well). I have not removed trebuchet yet, by the way, but Nova is my default launcher.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
show me the references to the google bug you mention please, I am not saying its not one, but I want to review it so I can elaborate on what I meant. There is no Google bug with how I use it, thats my point (and what I mean), and I switch ROMs weekly, A11 / A12 / LOS to anything, and NEVER has there been a hiccup. I am curious if there is an issue I don't know about, but I don't trip it with how I use it.

Don't remove the default launcher, just set NOVA to default in app/settings/defaults. If you remove the default (or freeze it) you may have switch (recent) failures to launch
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Here's the link I found, the thread was pretty close or top of search results..

All my web shortcuts have disappeared from Android phone home screen. How do I get them back???? - Android Community