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

[ROM][OFFICIAL] LineageOS 17.1 for Nexus 6 (shamu)

Search This thread


Senior Member
Jan 15, 2011
Hello everyone, does anyone have a build of this ROM after @Elektroschmock 's fix for the echo in VOIP calls? I would try to do a build but I lack the HDD space (300+ GB, I hear) for the build.
Also, does the echo fix take care of the echo during speakerphone Whatsapp calls? Thank you
Here is a migration build lineage-17.1-20220116-MIGRATION-shamu.zip (md5sum)
and the unoffical build lineage-17.1-20220116-UNOFFICIAL-shamu.zip (md5sum)

1. Make a backup
2. Flash the MIGRATION build
3. Boot the MIGRATION build
3. Flash the UNOFFICIAL build


P.S. Why not just update to 18.1 ?

Top Liked Posts

  • There are no posts matching your filters.
  • 42
    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. And if you would like to contribute to LineageOS, please visit our Wiki.

    The LineageOS 17.1 reovery is recommended
    If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot

    Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
    So you should be using the radio and bootloader img from that update.
    Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.

    They can be extracted from the factory image on google's site here.
    Or you can use the ones linked below that I already extracted:


    IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.


    You can use fastboot to flash the bootloader and radio.

    More information and installation instructions can be found on the LineageOS wiki here.

    Download Links
    LineageOS: https://download.lineageos.org/shamu
    Google apps: Opengapps Use an ARM (not ARM64) package for Android 10

    HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.


    Builddate: 2020.06.17
    [new] June security updates
    [new] LineageOS clock

    Builddate: 2020.05.29
    [new] May security updates
    [fix] ULL audio fixes
    [new] Add back serif fonts
    [fix] Screen turning itself on when no lockscreen is set
    [new] Etar calendar

    Builddate: 2020.04.12
    [new] April security updates ROM & kernel

    Builddate: 2020.04.08
    [new] Initial LineagOS 17.1 release

    Known Issues:
    [bug] Trusted voice is not working and probably never will
    [bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
    [bug] IMS is not working - if you need it you have to stay on lineage-15.1

    XDA:DevDB Information
    LineageOS, ROM for the Nexus 6

    Elektroschmock, elektroschmock, npjohnson
    Source Code: http://github.com/lineagos

    ROM OS Version: Android 10
    ROM Kernel: Linux 3.10.x

    Version Information
    Status: Nightly

    Created 2020-04-08
    Last Updated 2020-04-08
    Is there any chance to have lineage-18.1 on shamu?

    Well code is ready since 'forever' as you can see on the other Android 11 ROMs for shamu which are using Lineage's code. I just don't see a reason to use you users as guinea pigs for testing as long as there are bugs I am able to reproduce. If nothing goes south shamu will be in the first batch of devices receiving Lineage 18.1
    Hi-no the times are sort of real world screen on and off over a typical, normal day.
    I will play with the Ex Kernel Manager but normally using the conservative setting if anything lengthens battery life. (I think it just throttles back clock speed vs tinkering with all the multiple different frequencies. I believe it was designed originally to manage the Elemental kernel, but it is just overhead software really, and can be used with any. See here: https://play.google.com/store/apps/details?id=flar2.exkernelmanager&hl=en

    But it does raise a useful question - what kernel is used with 17.1 and do you have a better solution to manage that vs. just stock tweaks? Thanks

    Okay sorry I think I was unclear in my writing. I know what Ex Kernelmanager and Ex-Kernel is. I'm just don't know exactly what those profiles intend to do and on which sysfs interfaces the manager relies.
    When Exkernel was a thing shamu was still supported by google hence all kernel were mostly the same. Only some stock tweaks like you call them where the difference. With android 8 the different kernels began to drift apart, and most where given up for various reasons. Since android 9 there is only one kernel left for shamu It's the lineage kernel. You might find other kernels, but on the inside they are the lineage kernel with a different name tag applied.

    Answer your questions what this kernel is, is kind of hard, but I try.
    Base Google's 3.10.40 kernel for shamu
    Updated to 3.10.108
    Security patches up to April 2020
    Full RGB LED support. (hint hint I'm proud of this)
    Binder backport from 3.18
    interactive governor updated to 3.18
    various fixes for a lot of subsystems

    What this kernel does not and will never support
    Over clocking
    CPU Governors with long and funny names and ****ty function
    faking of bootloader status

    Okay now back to your other questions.
    LineageOS does have has power profiles for you too choose from. You can choose between longer battery life and higher performance. I don't know the exact setting for each profile, but I can look them up for you if you are interested.

    I recommend using these and advise against the use of any kernel manager. Those where never meant to be used on this kernel and can wreck all powersavings. Only use them if you know shamu better then me. ;)
    So it was a coincident? :)

    Curious: did you find the reason for the camera crashes and is it explainable to noobs?

    The app crashed because camera HAL was reporting no camera devices.
    For the HAL to work properly there are two services needed. 1. cameraserver and 2. qcamerasvr.
    Cameraserver needs qcamerasvr running to work.

    So we started qcamerasvr and then cameraserver in the init. At least this was the plan.
    But init is not synchronus which means it can reschedule the starting of those services which could lead to switched starting order.

    just reflashed today build.did aclean install from cr droid to lineage 17.1. So far so good. Will we get the june 2020 security patches in the next set of nightlies. .

    I need some more days, as I didn't have the time yet to update the kernel.