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.
-
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)
- Thread starter razorloves
- Start date
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/
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
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?
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.
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.
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.
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.
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 yearMeantime, 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.
curiousrom
Recognized Contributor
Pixel 3 - Possible to Downgrade Stock Android 12 to Android 11?
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?
***
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:
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. 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.
Found an answer for this one, sideload installer is unified with the apk, you just rename the extension. Very cool!
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:
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):
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?
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):
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
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
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
6Enjoy!
[ROM] [UNOFFICIAL] [blueline/crosshatch] [Android12] LineageOS 19.0
LineageOS is a free, community built...
forum.xda-developers.com
1
No issues on my blueline, unless you are referring to the "Speech Services by Google" issue "waiting for network connection". That is not a lineage problem, it is a problem with the update google pushed a couple of days ago.11
Dude! That worked.
Tried 1.2.0 and it works fine now. Thank you so much for that tip. I was about to go back to stock android. -
24
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki for more details.
Downloads:
pixel 3 - blueline: https://download.lineageos.org/blueline
pixel 3 xl - crosshatch: https://download.lineageos.org/crosshatch
gapps zip (arm64): (optional): https://wiki.lineageos.org/gapps.html
Google Fi addon: https://sourceforge.net/projects/ra...-gapps-addon-arm64-11.0-20210212.zip/download (if you're on Google Fi, install this zip right after installing gapps zip.)
Android Auto addon: https://sourceforge.net/projects/ra...-gapps-addon-arm64-11.0-20201121.zip/download (if you want android auto, install this after installing gapps zip. note: this is only needed with opengapps)
Initial Install Instructions:
https://wiki.lineageos.org/devices/blueline/install
https://wiki.lineageos.org/devices/crosshatch/install
Update Instructions:
https://wiki.lineageos.org/devices/blueline/update
https://wiki.lineageos.org/devices/crosshatch/update
Upgrade Instructions: (from 17.1 to 18.1)
https://wiki.lineageos.org/devices/blueline/upgrade
https://wiki.lineageos.org/devices/crosshatch/upgrade
Notes:
1. lineage-18.1 comes with adb root that you can enable in developer options, but if you want root for apps, you can grab the magisk apk and rename it to .zip and install it in lineage recovery.
An alternative install method is to follow these boot.img patching instructions. You can get the boot img directly from the lineage download site. It's labeled as the recovery img but it's actually the boot img.
2. The newest vendor, radio, & bootloader are included in the lineage rom zip, so no need to worry about updating those manually.
Known issues:
1. when you format data in lineage recovery, you might see "cant send spi message". you can ignore it.
2. there's an issue with sprint mobile data not working. we're looking into it. there's an easy workaround though. send me a pm and i'll walk you through it.
Changelog:
blueline
crosshatch
Bug reporting:
https://wiki.lineageos.org/bugreport-howto.html
Source Code:
crosshatch device tree: https://github.com/LineageOS/android_device_google_crosshatch/tree/lineage-18.1
blueline device tree: https://github.com/LineageOS/android_device_google_blueline/tree/lineage-18.1
kernel tree: https://github.com/LineageOS/android_kernel_google_msm-4.9/tree/lineage-18.1
vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-18.1
Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community.
Android version: 11
Kernel version: 4.9.248
Status: nightly17
Yeah, sorry for delay. Official should be coming in about a week. That's the plan, anyways.12Good news!
I started official 18.1 builds today.
to update from my unofficial 18.1 to official 18.1 without losing any data, follow these steps:
1. go into recovery
2. install official 18.1 zip
3. if you had gapps, select 'Advanced', then select 'Reboot to recovery', then install android 11 (arm64) gapps zip
4. you're done. select 'Reboot system now'
enjoy
See first post post for more info!9new builds with google's monthly december security updates and their quarterly feature drop.
blueline - https://sourceforge.net/projects/razorloves-lineage/files/blueline/
crosshatch - https://sourceforge.net/projects/razorloves-lineage/files/crosshatch/
also added active edge (squeeze) - big thanks to kdrag0n (more info)9new builds with February security patches and fixes from google.
blueline - https://sourceforge.net/projects/razorloves-lineage/files/blueline/
crosshatch - https://sourceforge.net/projects/razorloves-lineage/files/crosshatch/
New posts
-
-
Themes / Apps / Mods SamSprung - Secondary Home (Cover) Launcher- Latest: twistedumbrella
-