yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I am only guessing here (becuae I am not in the UAE or any way to replicate your setup) so take it with a grain of salt. That being said, if its allowed on the mobile side (which I have no clue if it is or not), but if it is, and its only locked by the OS, then you might be able to get around the lock with a custom OS and ROOT. I would say its definitely worth the effort to try it, because I have VoLTE and it works great, BUT I am in the US using verizon.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ibrahim52:
Alright then I guess I'll give it a try then. Thanks for your valuable input.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Peter the Gray:
Edit: Nevermind! Turns out I managed to get a phone with broken face unlock, a nonfunctioning battery meter, and the back was peeling off! New one will be here Friday.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] PR-0927:
Got a notification that a new LineageOS update was available. Is it safe to just do an OTA update through the built-in updater, or will this cause issues with Magisk and GApps?

Used to routinely flash ROMs on my Nexus 5 back in the day, haven't been dabbling in this world again after much time till the last week or so.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] gewecht:
I ran the OTA this morning and it worked without issue. Granted I was not rooted, although I did not have problems with GApps.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Go into settings, apps and notifications, assistant, all settings, languages, and add a language that Google doesn't support with the new UI. It'll use the old UI instead.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] PR-0927:
Hmm, O.K. Guess I'll back stuff up just in case things go South.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Joseph Melancon:
Exactly what I came to this thread to find, you are a life saver! Got sick of using keyboard controls because voice control wasn't working. Thank you!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Giunta._:
Does the motion sense work now?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Joseph Melancon:
Not for me. From what I hear the code is proprietary, it would take some work to get it on a custom ROM.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
No, and as I stated in the A11 PixiDust/LOS/Scorpion forum(s) where you asked the same thing, its proprietary code by Google. Its also listed as not working in all forum threads so why are you asking this same thing over and over in the forums for multiple ROMs? What are you looking to do?

I am not trying to be mean or hurtful, but the same question being asked by the same user in multiple forums (where it states that it DOESNT work), gets redundant and takes away from the goal of XDA. Helping others is why we are here so these useless questions done without any research on your part (and posted multiple times, in multiple forums) wont help the end goal. If you want it quicker than we devs can provide, then reverse engineer it and code it yourself and share for all of us.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Bailx:
where is the best place to submit bug reports?

mine is a SanDisk SDDDC2 - The one that can switch between USB-A & USB-C to easily plug into your phone. on 18.1 it wants to format the drive, all older versions of lineage/stock read the drive fine (various phones tested including another pixel 4 xl). maybe an issue with android 11, i haven't tried stock.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Here is the URL to report bugs in LOS, but make sure you do it right or it wont help. I would read through this first:

How to submit a bug report | LineageOS Wiki

wiki.lineageos.org

Then use the GitLab Issues to report the bug (assuming its not already in the list and is truly a LOS bug, not a USB bug):

issues · GitLab

GitLab.com

gitlab.com
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mangokm40:
Apologies for the error in posting...
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mangokm40:
Sorry....
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
What was the point to this? I am not putting this down, but to really help others, you should clarify what this is regarding. For example, what does this post fix? OR at least explain the post for the newbs reading it so they do not follow it and think this is the install process for LOS (its more than needed for LOS).

You also noted USB formatting issues (which deviates from the install process) as well as adding in MAGISK (ROOT). I would separate the post into sections and explain each section to newbs reading each piece (but break it up first). That way users know this isn't a setup log, or steps needed to follow for LOS.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] nashi0nal:
I was wondering if anyone knows how I can get mobile data working. When I tried lineage 18 I couldn't get it to work .I then tried pixel dust which in still currently on and had no problem with mobile data at all. Thanks in advance.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Well that doesnt really give us any info to help. For example, what service provider, location, did you check APNs, ETC? So far, no one but you has reported data issues (and I didnt have them on LOS 18.1), so without info, its damn near impossible to help.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] gunalarix8:
I successfully install the latest lineage os 18.1 and mindthegapps, however the audioFX app seems blank and i dont know if it is working out of the box.

The next hour later, i rooted using magisk and installed viper4android module. The V4A module cannot proceed to install driver.

Please help me :)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] flash713:
I have not yet used viper on my coral but this may help you find what you are looking for

https://xdaforums.com/t/guide-to-viper-on-4-xl-easy.3992137/

Look at the last post (most recent) on the thread from the link I pasted here..👆

I'm not trying to be rude or anything at all but this is Lineage thread not Viper. Always search high and low before asking. Most answers are already out there some place. Hope this helps.

If you would like to discuss Viper I suggest going over to the link I put in this post. That way things stay organized.. ✌️

Edited
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Can someone test and see if they can set/change the Emergency Location Information for Wi-Fi calling? I used to be able to set it to my apartment under other ROMs, but its timing out now under LOS18.1. NOTE, I haven't tried the older LOS 17.1, only 18.1.

Wi-Fi calling works fine, and I tested it thoroughly so its not broken, but I wanted to make sure my address was right and it time(s) out. I assumed originally that it was a Google temporary issue but no, it doesn't work 2 days later still. It doesn't look to be a temporary Google issue but a LOS issue (at least for my Pixel 4 XL running the latest 18.1).

Its under system/network & internet/mobile network/advanced/wi-fi calling/emergency address:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dynamiclynk:
I have LOS 4/25 on my 4xl.

I chose to install the latest 5/2 from the System menu then reboot after download and after the update but sticks at the boot logo.

Then if I hard restart the device it boots but still shows the 4/25 firmware.

I have tried adb sideloading the install.zip and same results am I missing something ?

Also I am using LOS recovery from same build date. Maybe I will wait for another nightly.

Used fastboot 31.0.2
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mangokm40:
TTS engines crashing Settings app...

I've been using flite TTS engine on various phones with LOS since (I think) LOS 14.

The first 2 phones I upgraded to LOS18 had a weird issue when I installed flite.

After installing the apk, I ran the app & setup the voice. I tested the voice in the app.

Everything was fine. When I went to settings to select default TTS engine & voice,

the Settings app hangs for a while. It shows the dialog that says the app is not responding.

I choose "wait" in the dialog. Then, everything is fine. TTS works just as always.

This happens every time I restart those phones.

In the Pixel phones (4 & 4a) with LOS18.1, the Settings app allows me to select the default TTS engine & voice. However, TTS never works. If I try to go back to

Settings->Accessibility->"Text-to-speech output", the Settings app restarts.

I have captured a "logcat -d" after these Settings app crashes. I got one with

flite TTS installed. I got another with IVONA TTS installed.

1) does anyone have TTS (not Google) installed?

2) are those logcat files of any value?

3) is it OK to cross-post this to the 4a forum?

Thanks for taking the time to read this.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] PR-0927:
Possibly a dumb question - where do I get the latest boot.img for the latest LineageOS build for the Pixel 4 XL? I See it even mentioned in the first post but no links anywhere.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mangokm40:
You extract it from the ROM.

This might help:

https://xdaforums.com/t/guide-how-to-extract-payload-bin-from-ota.3830962/
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] PR-0927:
Much thanks! I actually did this last time and didn't think it was likely the most logical way to handle this. A helpful forum member sent me a DM telling me the "recovery" .img file on the LineageOS download page is actually the boot.img, as Pixels don't have recoveries. Saves me a lot of confusion/time!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mangokm40:
That happens to be how I installed it. I patched the LOSrecovery.img file. However, I haven't seen that in any posting. I was just testing. I was kind of surprised I got root. ;) Thanks for letting me know you've heard that from others as well.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
You can disregard this, my own doing with disabling the verizon tracking apps. I noticed it also happened on stock when resetting my device which led to my own config and what I change when building out an OS. I reversed the steps until it worked and was due to this app I disabled (so that piece of crap company can't track me):
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] AlkaliV2:
Okay so I'm getting very weird UI behavior across three different launchers. When I swipe up and hold to show recents there is a massive delay before the first app slides in. The other issue I'm facing now is some kind of border around my home screen seen in the two screen shots below. I attempted to change the wallpaper and the launchers but it is like a permanent resolution decrease that is not there on startup. I am running the May 16 build, I did a factory reset after I did the OTA and the issue is present since first setup with the recents. Anyone else having these issues?

Edit: In case anyone has the border issue the fix is under developer settings > Display cutout. I have absolutely no idea why it was changed to Waterfall but that was the issue. I have put it back to "Device Default" and the resolution is normal now. Also switching back to trebuchet corrected my recents issue so I'm at a loss for what is going on. I might clean install it later today again to be sure I'm not messing anything up.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dvdram:
I am trying to install TWRP to a Pixel 4. So far, I have successfully installed LOS 18.1 and the appropriate LOS recovery. Now I want to install TWRP and I followed these instructions. After flashing and rebooting into recovery, I am presented the TWRP starting screen. That looks good, but nothing more is happening, there's no way of getting beyond this screen: neither touching the screen nor using any hardware button makes TWRP advance to its menu page.

What am I missing?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mangokm40:
I think you need to follow this:

https://xdaforums.com/t/twrp-flame-official.4110641/

The first 2 posts provide the information needed, I think.

The instructions at your link don't seem to follow the instructions from the dev of the TWRP images. You can also see info under "Installation" at the TWRP official page: https://twrp.me/google/googlepixel4.html
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bleh815:
i'd like to note that i am using a slightly different way for updating compared to what's given in OP

Sideload the latest build of Lineage OS (adb sideload lineage.zip)

(Optional) Reboot to recovery again and flash gapps of choice (MindTheGapps are recommended)

(Optional) Flash custom kernel / Magisk

Reboot to system

This way around it saves 1 reboot cycle. But the main reason to follow this order for me as a user of safetynetfix is that cts profile check keeps passing and certified state in play services will remain.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
I had that thought about the safetynet and if you just confirmed my though, I'll now have to test that out. 🤔
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dvdram:
If automatic screen rotation is active, the "alway-on-screen" (what's the correct name?) does not rotate back when the phone was locked while it was in landscape mode. Can this be fixed somehow?

Furthermore, I'd like to make two suggestions for improvements:

1.

I am beginning to like this "alway-on-screen" and the information it can provide. I also like the option "tap to activate device". However, I think (optional) "double-tap to activate" would be a better option, as it would prevent unwanted screen activation, thus saving battery. And besides: a double tap action looks way cooler than a single tap! :cool:

2.

This is an issue that has been annoying me (and many more users!) since Android 10: the missing possibility to *not* play certain sounds via bluetooth. Since Big G decided every single sound has to be send to a connected BT device, regardless of the user's wish and the BT device's capabilities, it's very likely to miss alarms when you're not wearing your headphone and it is not possible any more to listen to a car's FM radio and hearing the navigation instructions from the phone at the same time. Last week I missed several turnings because of this, each costing me lots of wasted time, as I was very busy concentrating on driving and I could look at the phone's screen.

Is there any way that this can be corrected, so that system sounds will be played on the phone's speakers, while only media sounds and phone calls are routed to the connected Bt devices?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dvdram:
Thanks for the information. I decicded to stick to LOS recovery. The reason I wanted to use TWRP is its ability to backup up the whole system. But because the Pixel 4 is an A/B device, I guess I don't need to worry about faulty updates as much as I had to worry before. If I am wrong about that, please let me know.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
You do not need to nandroid (backup) both slots (A/B). Just the active slot, as it's pointless to nandroid both slots. Only the active slot matters to the running OS, thus only the active slot needs to be backed up. You will have a terrible time with issues if you tried to restore both slots from a nandroid backup.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] AlkaliV2:
For anyone who's been using MindtheGapps from OP and having trouble with the assistant crashing or not registering your voice using English then there is a fairly simple fix I didn't know about until now. Go to:

1. Settings > Apps and Notifications > Default Apps --> Select Google as your digital assistant app

2. (Optional: Assistant on Squeeze) Settings > System > Gestures > Active Edge --> Select, "On Squeeze Assistant"

3. Settings > Google > Settings for Google Apps > Search Assistant and Voice > Google Assistant > Languages

4. Click the + language button to add something like Deutsch. This will warn you the new assistant isn't available on this language and you can then acknowledge it and the Google Assistant will be the old working version. This fixes screen off, "Hey Google" for me and the Squeeze for Assistant gesture. Hope this helps someone else using LOS 18.1!

Credit this post #3: https://xdaforums.com/t/rom-officia...google-pixel-4-xl-coral.4228943/post-84430261
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
That's why I try to only use opengapps, I find they work pretty much solid every time. Didn't crash using OG when I tested LOS.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] AlkaliV2:
I did try to use Opengapps however Android Auto immediately locks up my device when connected to my car. So I have to use Mindthegapps since it works better with Android Auto.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
This is good to know, my 2006 Jeep is a bit to old for AA, but my wife's buggy isn't. I will test a few things in her buggy with AA and see if I can get it working with OG. I prefer OG because its more recent with the latest Google framework (I found over years of testing) but it doesn't take AA into account.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mangokm40:
Is the OTA Updater working (flame) for LOS 18?

I've done it a few times with sunfish, but this would be my first try with the flame phone.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bleh815:
Yes, it's working fine
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] insestito:
Hey dude! How works LOS 18.1?

Any big bug or something?

How is battery drain?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
If you are asking how does LOS perform battery-wise, its fine, but battery-life is very unique to the users. I would suggest trying it yourself, otherwise you will get someone else's battery results based on different things they have running, configured, or kernel based, so it wont ever be 100% accurate. I am not on LOS now, but I do test them all, and I found it was fine for me.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Also to add to my older post, the latest LOS11 runs AMAZING! The battery life I get now with LOS is far beyond any other ROM in my opinion, this is including stock, and all AOSP flavors. This was not always the case with LOS though and my PX4, but whatever they changed or fixed over the life of 11 between my original LOS test of 11 and now has DRAMATICALLY improved battery life. This is is on stock LOS kernel too with no modifications, out of the box!!

I was floored yesterday after finishing my LOS11 test build-out (this ROM) and thought it was broken (battery percentage). When I went to bed, about 4 hours later (after completing my 200+ apps, and configuring my device with LOS), I saw my battery percentage was STILL at 100%, no joke, no lie, so I thought it was buggy or not working. Well was I pleasantly wrong, I fired up my fav game, played for a few minutes, and the percent dropped 3% (with my phone warming up) so I know it was cranking out some 0 and 1s as I played the game (bits/bytes)! This shows it was clearly at 100% still, and was working/accurate then only dropped when I ran her pretty hard with gaming. This was 4 to 5 hours later and from sitting idle while not used for anything but RIL (phone/MMS) after I completed all of the apps, configs, setup, ETC., IDLE IS DRAIN IS AMAZING!

Well done LOS team and Eamo5!!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] insestito:
Wow... Nice review... Maybe i try it one more time...
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I definitely would, and don't be like me and test, but wait months before re-testing because you miss out on a lot. I try to test as often ad possible, but its getting harder and harder as time goes on to keep up with ROM updates and test all different ROMs for users. Life keeps getting in the way so honestly, I haven't used LOS in weeks, but I am VERY glad I came back and tested the recent builds last week!

Its so far, FLAWLESS, with ZERO issues, zero bugs, its stable, its blazing FAST (in my opinion), and battery is insanely good. This is with NO KERNELS (but stock/LOS), I do use MAGISK ROOT with LSPOSED. I only install/run two fun LSPOSED icon modules, plus safetynet (universal safetynet module), so nothing crazy there there either. Point being, I didn't have to tweak or modify kernels or modules to get this get battery life, I use Out of the Box kernel and most ROM settings are LOS default (performance-wise).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Essasetic:
I have a Pixel 4 and I'm debating whether to flash this or upgrade to Android 12.

What would be the benefits of LineageOS over stock Android 11/12? Or should I just stick to stock Android?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I can tell you, from actual, personal experience, with going both routes (official firmware 12 and LOS 11), that I find LOS (especially the most recent version of LOS) far, I mean FAR exceeds stock 12.

My vote is to use LOS, and A12 official later on, down the road after all issues are sorted out and more stable. I had a few annoying issues on 12, so I actually rolled back to LOS. Aside from testing and helping users on other ROMs, LOS is my new daily driver and the ROM that's remaining on my PX4 unless testing other ROMs for users/devs!

LOS is faster, absolutely no bloat (stock Android has Verizon crap and COVID notifications), LOS is just faster and less buggy with better, much better battery life in my opinion!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] insestito:
Installed and working perfect.

No LOS bugs founded at the moment

But, i have the same bug like on Android 12... Just when i updated to A12 this appears...

My pixel says that the battery percentage can't read....

And i don't know how many % has the battery...

sometimes it fix it rebooting but it appear again in a few minutes...
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
This is a hardware issue with Pixel 4 batteries, not a bug. I had this on my old coral. You should contact Google and sort out an RMA.

1-year extended repair program for Pixel 4 XL - Pixel Phone Help

Google is offering a one-year repair program for Pixel 4 XLs purchased in the US, Singapore, Canada, Japan, and Taiwan, for certain power-related issues. In Canada, if you’re eligible for

support.google.com
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] flash713:
1-year extended repair program for Pixel 4 XL - Pixel Phone Help

Google is offering a one-year repair program for Pixel 4 XLs purchased in the US, Singapore, Canada, Japan, and Taiwan, for certain power-related issues. In Canada, if you’re eligible for

support.google.com

I definitely agree with you too Josh on Los 18.1 being much better than stock 12. I always stay on previous version for some months until the roms are all mostly fully featured and more mature before I jump over.

I dropped my 4xl last week and now it has the battery issue as well. What sucks is I bought it used so Im not eligible for the free fix. :/ Great job on Los 18.1 op!! 🔥
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] KJ7LNW:
Hello, thank you for maintaining the ROM!

I just installed on a 4 XL with microG and it seems to be working great except two issues:

1. VoLTE isn't working: in ghe *#4636#* menu it shows LTE but when I call the phone it falls back to UMTS so the call isn't staying on LTE for VoLTE. Do you know what this might indicate?

2. Just a minor issue: it shows "5Ge" in the corner, but, unless I'm mistaken, this phone only supports 4G
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I have no such issues as you report and I use LOS as my daily driver, I have WiFi calling, VoLTE, and no 5G in the corner. What mobile provider are you using? Do you have anything extra (kernels, LSPosed, XPosed, ETC)?