• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][11][OFFICIAL] lineage-18.1 for Pixel 3/XL (blueline/crosshatch)

Search This thread

rlotze

New member
Aug 22, 2013
2
0
Hi experienced users,

Due to the end of Google's support I'm thinking about switching to LOS 18.1 now. Is there any drawback comparing to stock ROM? Is the excellent camera working as before? The good stereo sound and stable Bluetooth also?
Thanks a lot!
I've noticed no change in camera, speakers, or Bluetooth. Two weeks ago I installed this for the same reason. After install if you then install the lawnchair launcher and then standard Google apps (phone, contacts, camera, etc) I think you'll notice very little change from Android 11 on pixel 3. Its easy to forget you're using a custom ROM.
 

BloodMist

Member
Feb 17, 2020
18
4
LG G8
i recommend going back to the latest stock A11 from google DL pages flash this one and then flash LOS18.1 again as a "clean install". From my experiences (with other phones too) this is the best practice. And finally going to the next (A12 based) LOS you should do the upgrade to stock A12 again before that to have the latest vendor firmware "parts" including modem software. confused?

So if you are at P3's stock A11 you can:

1.) upgrade to stock A12 now or later, use that a while until LOS19x comes out in spring 2022. Before installing LOS19 make sure that you have the latest stock patches applied. Then goto LOS19 using the usual procedures as described in the (new) LOS19 wiki article.
2.) make sure you have the latest A11 version installed. Then goto LOS18.1. If LOS19 is availiable upgrade from LOS18.1 to LOS19 using the standard procedures (--> wiki)

For my personal usage i think its is wasted time to go to LOS18.1 with my current productive Pixel3 now. i am now on stock A12 with my dev/test phone. i will play a little bit with this one and maybe i will use it as my daily driver for the next few months. Then i take my former prod phone and install LOS18.1 as long as this is available as the official LOS release. After LOS19 is avail i will upgrade to LOS19 coming from LOS18.1, and use this one as my daily driver again. This is the most efficient way to run that migration without doing complete flashes "forward" and "backward" including all their associated possible risks. And i will have a new and an actual version to play with.
I am running a similar procedure with my Samsung klte's for several years now.
lmfao wut? los19 comes out in spring 2022?! dayum thats a lot
 

LargeElephant

Member
Nov 12, 2021
5
2
The battery life on the stock rom is average at best. Is there a way to lock the bootloader on LineageOS? I want to use it for the improved battery life, but I am anxious about the device being compromised should someone have physical access to it. Anyone have any thoughts?
 

lpedia

Senior Member
Sep 18, 2020
196
96
Samsung Galaxy Tab S2
HTC 10
The battery life on the stock rom is average at best. Is there a way to lock the bootloader on LineageOS? I want to use it for the improved battery life, but I am anxious about the device being compromised should someone have physical access to it. Anyone have any thoughts?
You might find this discussion informative (and can someone tell me how to stop XDA from converting this to MEDIA and displaying the entire page instead of just the link?):
Code:
https://www.reddit.com/r/LineageOS/comments/n7yo7u/a_discussion_about_bootloader_lockingunlocking/
 

zimral.xda

Senior Member
lmfao wut? los19 comes out in spring 2022?! dayum thats a lot
Not sure what language this is but the phones maintainer need some time to take the new AOSP version, do some programming and adapt this to the phone. This needs time. Please be aware that a typical Samung stock Android user is waiting alot of months too to receive a new Android version. If he ever will receive it! I am personally got screwed with Samsungs behavior to handle updates, so at the end of the day i will NEVER EVER buy a new Samsung phone. I am moving to use only Google/Pixel phones in the near future either with removed google apps or pure LOS roms (without gapps). I am still using A12 on my both Pixel3 and LOS 18.1 on a Pixel2 and on a Samsung klte. I am just selling all of my Samsungs to buy a used Pixel 5 cause i like this phone - my wife has one. Therefore be patient and you will receive a well working LOS19.x next spring :cool:
 
  • Like
Reactions: lpedia

BootloopedMillennials

Senior Member
Dec 25, 2010
1,037
287
Google Pixel 6
lmfao wut? los19 comes out in spring 2022?! dayum thats a lot

Yes.

Android 9 came out in August 6, 2018. Los16 came out in March 1, 2019.
Android 10 came out in September 3, 2019. Los17.1 came out in April 1, 2020.
Android 11 came out in September 8, 2020. Los18.1 came out in April 1, 2021.
Android 12 came out in October 4, 2021. Los19 out in around May 1, 2022?
 

BootloopedMillennials

Senior Member
Dec 25, 2010
1,037
287
Google Pixel 6
Meantime, enjoy the comfortably familiar LOS 18.1 user interface and regular security updates.

I'm hoping LOS 19 will continue the practice of being much more personalisable than stock Android ... please, don't force that abominable 'square' clock onto our lock screens. :(

Android 12 is meh imo. I'm not a fan of Material You. Lot of wasted space and cartoonish. Sort of related wish my Pixel 6 was the size of the Pixel 3 or 5.
 

supachris

Senior Member
I've noticed no change in camera, speakers, or Bluetooth. Two weeks ago I installed this for the same reason. After install if you then install the lawnchair launcher and then standard Google apps (phone, contacts, camera, etc) I think you'll notice very little change from Android 11 on pixel 3. Its easy to forget you're using a custom ROM.

Done, I switched yesterday and everything seems to be working fine so far. But the battery drain is a little higher than in stock. But it´s okay, I think. I used Lawnchair also on stock, so the appearence is nearly the same now. Great.
 

zimral.xda

Senior Member
Meantime, enjoy the comfortably familiar LOS 18.1 user interface and regular security updates.

I'm hoping LOS 19 will continue the practice of being much more personalisable than stock Android ... please, don't force that abominable 'square' clock onto our lock screens. :(
Yep, 100% agree with this. The Trebuchet should stay as it is. Point. BTW, for me LOS is THE stock Android. I dont like the "material design" either. There were not many changes in the Apps colours for me. My main complaint is the presentation of the GUI, i dont like the round buttons, i prefer the square ones with round corners. Ok, I cleaned most of google stuff ("pm uninstall" etc) and i use the APKPure repository, and i can live with that until LOS 19 hit the street next year :cool:
 
  • Like
Reactions: lpedia
Pixel 3 - Possible to Downgrade Stock Android 12 to Android 11?

I already updated to stock Android 12 but i don' t like it very much.
Can i downgrade with just installing this rom or do i have to downgrade officially with the Android flash Tool and flash stock Android 11 and then Install this rom?

So, did you get an answer to that question or did you do it yourself using https://flash.android.com/welcome?continue=/release/11.0.0 or https://developers.google.com/android/images ?

Do you have a Pixel 3 or Pixel 3 XL?
***
 
Last edited:

ahoyboyhoy

Senior Member
Jul 21, 2013
135
16
Brooklyn, NY
Seeking advice and/or links for two issues:
1. Google Pay (contactless)
I'm passing SafetyNet with the below, but Google Pay still reports "not set up" and "phone doesn't meet security requirements". I'm on the old app, but I don't think the new app was any better. Is the SQL fix still required? I've seen the same results while running that as well.

2. AdAway with systemless hosts
LOS 18.1 appears to be affected by this bug. Is anyone running systemless hosts and AdAway with success?

- latest LOS 18.1 nightly
- Magisk canary installed (23015)
- Zygisk enabled
- DenyList on with apps selected
- Universal SafetyNetFix 2.2.0 installed
- MagiskHideProps 6.1.2 installed w/ Pixel 3 Android 11 fingerprint selected
- Magisk app hidden

p.s. anyone have success flashing/sideloading Magisk canary 23015 so that it survives OTA updates? I've only been able to patch a boot image.
 

dcarvil

Senior Member
Apr 20, 2016
559
317
Seeking advice and/or links for two issues:
1. Google Pay (contactless)
I'm passing SafetyNet with the below, but Google Pay still reports "not set up" and "phone doesn't meet security requirements". I'm on the old app, but I don't think the new app was any better. Is the SQL fix still required? I've seen the same results while running that as well.

2. AdAway with systemless hosts
LOS 18.1 appears to be affected by this bug. Is anyone running systemless hosts and AdAway with success?

- latest LOS 18.1 nightly
- Magisk canary installed (23015)
- Zygisk enabled
- DenyList on with apps selected
- Universal SafetyNetFix 2.2.0 installed
- MagiskHideProps 6.1.2 installed w/ Pixel 3 Android 11 fingerprint selected
- Magisk app hidden

p.s. anyone have success flashing/sideloading Magisk canary 23015 so that it survives OTA updates? I've only been able to patch a boot image.
1. Did you clear Google Pay cache? I have no problems with Google Pay, but I just use it for loyalty cards, not for payment. My configuration is:

Magisk stable v23.0
Universal SafetyNet Fix v1.2.0
MagiskHideProps 6.1.2
Magisk app not hidden
No SQL fix

2. AFAIK, LOS does not have the F2FS bug. I am running LOS blueline Nov. 16 build with systemless hosts with no problems. I don't have AdAway, but I had the F2FS bug before I switched to LOS, and did not have AdAway then either. Before moving to LOS, I used the Kirisakura kernel to resolve the F2FS problem. I've been on LOS for 6 months with no F2FS issues.
 
Last edited:
  • Like
Reactions: ahoyboyhoy

Mogul345

Senior Member
Apr 14, 2006
250
37
Hey everyone, running into a strange issue with Google Play Services on my Pixel 3.

I followed the installation instructions, and I chose MindTheGApps as my GApps during install. I also installed the Fi addon b/c I'm on Google Fi. Finally, I've also installed Magisk, but the current stable version and I've done nothing to fix the failing SafetyNet. Unsure if this matters though. And I've double checked, Play Services is on the latest version in the store.

Every production app I've downloaded from the store or sideloaded seems to work without problems. But I'm having a problem with debug builds of the app I work on for a living, all of a sudden. I keep getting this strange system dialog, and I can't tell where it's coming from (see attached screenshot). And I can see in logcat, that I'm getting SERVICE_INVALID for a couple subsystems of Play Services - location and Firebase Auth. Here's a dump from logcat (package name replaced for privacy, and truncated some logs I believe are unrelated):


2021-12-06 16:36:34.011 22395-22395/com.mypackagename I/FirebaseApp: Device unlocked: initializing all Firebase APIs for app [DEFAULT]
2021-12-06 16:36:34.017 22395-22395/com.mypackagename I/FirebaseCrashlytics: Initializing Firebase Crashlytics 18.2.4 for com.mypackagename
2021-12-06 16:36:34.033 22395-22423/com.mypackagename I/DynamiteModule: Considering local module com.google.android.gms.measurement.dynamite:51 and remote module com.google.android.gms.measurement.dynamite:55
2021-12-06 16:36:34.033 22395-22423/com.mypackagename I/DynamiteModule: Selected remote version of com.google.android.gms.measurement.dynamite, version >= 55
2021-12-06 16:36:34.047 22395-22432/com.mypackagename W/DynamiteModule: Local module descriptor class for com.google.firebase.auth not found.
2021-12-06 16:36:34.048 22395-22395/com.mypackagename I/FirebaseInitProvider: FirebaseApp initialization successful
2021-12-06 16:36:34.055 22395-22437/com.mypackagename W/DynamiteModule: Local module descriptor class for com.google.firebase.auth not found.
2021-12-06 16:36:34.056 22395-22437/com.mypackagename W/GooglePlayServicesUtil: com.mypackagename requires the Google Play Store, but it is missing.
2021-12-06 16:36:34.056 22395-22437/com.mypackagename W/GoogleApiManager: The service for com.google.firebase.auth.api.internal.zzei is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
2021-12-06 16:36:34.065 22395-22395/com.mypackagename D/LeakCanary: Installing AppWatcher
2021-12-06 16:36:34.076 22395-22395/com.mypackagename W/com.facebook.UserSettingsManager: The value for AdvertiserIDCollectionEnabled is currently set to FALSE so you're sending app events without collecting Advertiser ID. This can affect the quality of your advertising and analytics results.
2021-12-06 16:36:34.085 22395-22444/com.mypackagename E/GraphResponse: GraphRequest can't be used when Facebook SDK isn't fully initialized
2021-12-06 16:36:34.085 22395-22441/com.mypackagename E/GraphResponse: GraphRequest can't be used when Facebook SDK isn't fully initialized
2021-12-06 16:36:34.087 22395-22441/com.mypackagename E/GraphResponse: GraphRequest can't be used when Facebook SDK isn't fully initialized
2021-12-06 16:36:34.090 22395-22437/com.mypackagename W/GooglePlayServicesUtil: com.mypackagename requires the Google Play Store, but it is missing.
2021-12-06 16:36:34.090 22395-22437/com.mypackagename W/GoogleApiManager: The service for com.google.android.gms.internal.location.zzay is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
2021-12-06 16:36:34.091 22395-22437/com.mypackagename W/GooglePlayServicesUtil: com.mypackagename requires the Google Play Store, but it is missing.
2021-12-06 16:36:34.091 22395-22437/com.mypackagename W/GoogleApiManager: The service for com.google.android.gms.internal.location.zzay is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
...
2021-12-06 16:36:34.115 22395-22450/com.mypackagename I/FA: App measurement initialized, version: 46016
2021-12-06 16:36:34.115 22395-22450/com.mypackagename I/FA: To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
2021-12-06 16:36:34.115 22395-22450/com.mypackagename I/FA: To enable faster debug mode event logging run:
adb shell setprop debug.firebase.analytics.app com.mypackagename
...
2021-12-06 16:36:34.156 22395-22395/com.mypackagename D/FirebaseAnalytics: enable Firebase Analytics
...
2021-12-06 16:36:34.670 22395-22437/com.mypackagename W/GooglePlayServicesUtil: com.mypackagename requires the Google Play Store, but it is missing.
2021-12-06 16:36:34.670 22395-22437/com.mypackagename W/GoogleApiManager: The service for com.google.android.gms.internal.auth-api.zzq is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
...
(Click the Google sign in button on our login screen)
2021-12-06 16:55:16.013 22395-22437/com.mypackagename W/GooglePlayServicesUtil: com.mypackagename requires the Google Play Store, but it is missing.
2021-12-06 16:55:16.013 22395-22437/com.mypackagename W/GoogleApiManager: The service for com.google.android.gms.auth.api.signin.internal.zzh is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}

Our app does use fusedlocationprovider and firebase auth for 3rd party auth. We also do include SafetyNet in the build, but we don't actually do anything with it (we just log to our internal analytics pass/fail). And even before I installed LOS I was failing SafetyNet with my rooted stock ROM and the debug builds worked fine, so pretty sure that's not the issue.

Any ideas? Should I have used OpenGApps?
 

Attachments

  • Play_Services_Error.png
    Play_Services_Error.png
    27.1 KB · Views: 31

ahoyboyhoy

Senior Member
Jul 21, 2013
135
16
Brooklyn, NY
1. Did you clear Google Pay cache? I have no problems with Google Pay, but I just use it for loyalty cards, not for payment. My configuration is:

Magisk stable v23.0
Universal SafetyNet Fix v1.2.0
MagiskHideProps 6.1.2
Magisk app not hidden
No SQL fix

2. AFAIK, LOS does not have the F2FS bug. I am running LOS blueline Nov. 16 build with systemless hosts with no problems. I don't have AdAway, but I had the F2FS bug before I switched to LOS, and did not have AdAway then either. Before moving to LOS, I used the Kirisakura kernel to resolve the F2FS problem. I've been on LOS for 6 months with no F2FS issues.
Yeah, I've cleared the cache and uninstalled, etc. Strange thing is that despite the messages in app, I've been able to use Google Pay for OMNY (NYC public transit) just today, so maybe it's a non-issue?

As for the freeze on boot, you have a Pixel 3 or XL? It could be something other than the bug I linked to, but on multiple system installs of 18.1 with wipes, I've reproduced a freezing system moments after boot unlock 100% of the time when systemless hosts is enabled and AdAway installed (haven't tested those two in isolation).
 

dcarvil

Senior Member
Apr 20, 2016
559
317
Yeah, I've cleared the cache and uninstalled, etc. Strange thing is that despite the messages in app, I've been able to use Google Pay for OMNY (NYC public transit) just today, so maybe it's a non-issue?

As for the freeze on boot, you have a Pixel 3 or XL? It could be something other than the bug I linked to, but on multiple system installs of 18.1 with wipes, I've reproduced a freezing system moments after boot unlock 100% of the time when systemless hosts is enabled and AdAway installed (haven't tested those two in isolation).
I have a Pixel 3. You didn't mention it was freezing on boot. That was not the symptom I had - it was just random freezes, not on boot.

You can get ad blocking without systemless hosts or AdAway by using the AdGuard DNS servers. https://adguard.com/en/blog/adguard-dns-new-addresses.html Also, change your Private DNS to dns.adguard.com.

Another alternative is to use the Steven Black hosts file with systemless hosts. https://github.com/StevenBlack/hosts
 
  • Like
Reactions: ahoyboyhoy

Top Liked Posts