[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 4 / 4 XL

[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.

 

[GROOVYJOSHCLARK]

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.

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.

 

[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

 

[flash713]

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

I have not yet used viper on my coral but this may help you find what you are looking for

Guide to Viper on 4 XL (Easy)

Here are the steps to install viper with a Pixel 4 XL: 1. In magisk go to downloads, install the audio compatibility patch 1.7 3. Choose volume up for requested settings, although USB can be set as preferred. 2. Reboot 3. Install XDA Labs...

forum.xda-developers.com

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

 

[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:

 

[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

 

[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.

 

[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.

 

[mangokm40]

You extract it from the ROM.

This might help:

[Guide] How to extract payload.bin from OTA

This is guide for extract payload.bin from OTA zip file ----------------- Pre-requirement: - Python3 ----------------- For extract OTA update Please flow step by step instruction Step 1: Get a OTA for Nokia 7 plus -> here Step 2: Download...

forum.xda-developers.com

 

[PR-0927]

You extract it from the ROM.

This might help:

[Guide] How to extract payload.bin from OTA

This is guide for extract payload.bin from OTA zip file ----------------- Pre-requirement: - Python3 ----------------- For extract OTA update Please flow step by step instruction Step 1: Get a OTA for Nokia 7 plus -> here Step 2: Download...

forum.xda-developers.com

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!

 

[mangokm40]

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!

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.

 

[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:

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):

 

[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.

 

[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?

 

[mangokm40]

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?

I think you need to follow this:
https://forum.xda-developers.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

 

[bleh815]

i'd like to note that i am using a slightly different way for updating compared to what's given in OP

1. Sideload the latest build of Lineage OS (adb sideload lineage.zip)
2. (Optional) Reboot to recovery again and flash gapps of choice (MindTheGapps are recommended)
3. (Optional) Flash custom kernel / Magisk
4. 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.

 

[Curiousn00b]

i'd like to note that i am using a slightly different way for updating compared to what's given in OP

1. Sideload the latest build of Lineage OS (adb sideload lineage.zip)
2. (Optional) Reboot to recovery again and flash gapps of choice (MindTheGapps are recommended)
3. (Optional) Flash custom kernel / Magisk
4. 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.

I had that thought about the safetynet and if you just confirmed my though, I'll now have to test that out.

 

[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!

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?

 

[dvdram]

I think you need to follow this:
https://forum.xda-developers.com/t/twrp-flame-official.4110641/
...

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.

 

[GROOVYJOSHCLARK]

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.

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.