[ROM][unOFFICIAL] LineageOS 15.1 for Nexus 6P (angler)

Search This thread

Nexus4Owner1

Member
Mar 21, 2016
19
5
Hey @razorloves !
As I noticed, you are a member of the LineageOS core team. So you are a pro. :)

Is it possible to build LOS 18.1 for the angler? I learned how to set up a build machine, but it seems you need developer skills to migrate the 15.1 code base (kernel and device specific code) to a newer version of LineageOS. Is this possible and are you maybe working on it?
 
  • Like
Reactions: nilse

razorloves

Senior Member
Sep 19, 2007
3,102
14,796
Miami
Google Nexus 5
Nexus 9
Is it possible to build LOS 18.1 for the angler? I learned how to set up a build machine, but it seems you need developer skills to migrate the 15.1 code base (kernel and device specific code) to a newer version of LineageOS. Is this possible and are you maybe working on it?
sure, it's possible to build it, with some dev work.
but i'm not working on it.
ims (volte, wifi calling, hd voice, rcs texting, video calling) is broken on all angler custom roms newer than oreo. No one has figured out how to fix it. That's why i continue updating 15.1.
 

titanreign

Member
Nov 1, 2012
46
10
I just wanted to drop in and thank @razorloves for maintaining such an awesome ROM for this device. I have bounced around with the others; Bliss, Havoc, as well as 16, 17, and 18 LOS roms. None of them have the stability or battery life that this build delivers. Again, thank you @razorloves, you rock!

Screenshot_20210519-160408_Settings.png
 

Letitride

Senior Member
@razorloves - updated my N6P from the April 2021 build to the newest, May 2021 with a simple dirty flash, with the last step flashing the 4 core patch from within TWRP. Boot up nicely & butterly smooth. Everything just works and I see no reasons to find another daily with any of the newer custom roms, including LOS - been there & came back here. Thank you for keeping the device "live" - had a brand new OEM battery installed last year so going to have lots of fun for a while.
 
Last edited:

Sam Nakamura

Retired Forum Moderator
@razorloves - updated my N6P from the April 2021 build to the newest, May 2021 with a simple dirty flash, with the last step flashing the 4 core patch from within TWRP. Boot up nicely & butterly smooth. Everything just works and I see no reasons to find another daily with any of the newer custom roms, including LOS - been there & came back here. Thank you for keeping the device "live" - had a brand new OEM battery installed last year so going to have lots of fun for a while.
That's exactly my experience too, tried pretty much everything out there and ended where I once started for the sake of reliability, stability and performance combined with incredible battery life, I got a great replacement battery 6 month ago with fast charging working and according to AccuBattery 99% of it's design capacity remaining! Actually managed to replace the battery without breaking anything (talking to you damn rear camera glass!) and now I feel like I'm having a perfect spare device to tinker a little with Magisk and stuff...

I had many android devices but the last nexus has a special place in my heart, I like it's design and the feel of it! It's part of the important android history!

tl; dr
It's absolutely incredible this ROM, it's the perfect daily driver material!

Many thanks to everyone involved with developing it...
 

NUMAflex

New member
Dec 31, 2017
4
4
Hi1 Perhaps you talking about that trick you have to flash and then proceed to set it with no lockscreen option, do a reboot and then it get detected, also in my own tests, flashing magisk (together with opengapps) has booted for the first time already with mobile signal.
 
  • Like
Reactions: sinkoo1979

blitzkriegger

Senior Member
Apr 30, 2014
330
169
Las Piñas City
@razorloves Sir first off thank you so much for your work keeping the most stable android version for 6p alive and kicking with LineageOS. You guys and the devs here inspired me to start my android building journey with lineage-17.1

I do have a question, for successful lineage builds that end up getting looped at the lineageOS boot screen, how do you guys troubleshoot what's causing the bootloop? Are there any particular errors in the logs? I did try to look at recovery and kernel logs and try to spot the errors. but usually I end up with trial and error stuff so it gets time consuming. I figure the process would be faster if I get to learn how to read the logs so as to know which commits I have to revert here and there.

Also just to share with you I've continued to encounter this sporadic issue for Lineage builds on Q where in the build works but after subsequent reboots it eventually lands back to twrp recovery , re-wiping data to regain access. Disabling FBE side steps this issue but then the other sporadic issue (which I recall has been happening since Android O) where in after subsequent reboots the phone I get this lock screen loop, and I have to go back to twrp to delete the locksettings.db etc. stuff. Just my amateur speculation that some necessary commits had to be included somewhere along the path from O to Q to properly transition angler from FDE to FBE. My search thus far pointed to system/vold and or system/core commits and so I've tried looking at AOSP gerrit at those platforms, tracing back from commits made for O onwards. I can't fully lay my finger on which exact commits though. ;/
 

ok2ok

Member
Aug 22, 2012
10
1
Google Nexus 4
Nexus 7
sure, it's possible to build it, with some dev work.
but i'm not working on it.
ims (volte, wifi calling, hd voice, rcs texting, video calling) is broken on all angler custom roms newer than oreo. No one has figured out how to fix it. That's why i continue updating 15.1.
First of all, thank you for the work of building ROMs for 6p.

I'm quite confusing about building ROMs for 6p based on newer Android versions. I see that PE has Android 10 for 6p (https://download.pixelexperience.org/angler) and CarbonRom for 6p is based on Android 9 (https://get.carbonrom.org/device-angler.html).
And the same situation for OG Pixel. I recall maybe you or intervigil has said there's no driver support for OG Pixel for A11 so so many things will be broken on OG Pixel with A11. But PE has A11 builds for OG Pixel (https://download.pixelexperience.org/sailfish) and it says there's no issues (https://forum.xda-developers.com/t/rom-11-0-sailfish-pixelexperience-aosp-official.4247201/).
How could it be possible?

The question itself may be stupid but I don't know what to search or where to follow for the answers.
 

Top Liked Posts