[ROM][UNOFFICIAL] LineageOS 17.1 for Nexus 5 (hammerhead)

Search This thread

philipped346

Senior Member
  • Jun 25, 2010
    1,305
    1,018
    In the mountain
    Google Nexus 5
    Xiaomi Poco F1
    At first: Happy New Year! and thanks for linageOS for the Nexus 5 :)

    I did the update from december 31st, and since then my phone has troubles all over the place. Mostly WiFi, I just can't activate it.
    The update from dec 16th worked fine.
    So ist there a way to get back to that state?

    EDIT: I have reset all the network preferences. For now I have wifi…
    This is weird, I never had to do that before.
    Clean install
     

    TomiLynch

    Senior Member
    Jan 31, 2017
    443
    431
    Google Nexus 5
    Moto E
    At first: Happy New Year! and thanks for linageOS for the Nexus 5 :)

    I did the update from december 31st, and since then my phone has troubles all over the place. Mostly WiFi, I just can't activate it.
    The update from dec 16th worked fine.
    So ist there a way to get back to that state?

    EDIT: I have reset all the network preferences. For now I have wifi…
    This is weird, I never had to do that before.
    really no other option? I mean, this is not Windows, it's linux… (almost ;))
    Try wiping only Sistem, Dalvik and Cache. Then flash Rom, Gapps, and Magisk.

    DO NOT wipe Data or Internal Storage, that way you're basically doing a clean flash, but without losing all your data.

    This is the way I update every time, just to make things a little "cleaner".
     
    • Like
    Reactions: jenkinsad0

    lasser1

    Member
    Jan 1, 2021
    8
    0
    Try wiping only Sistem, Dalvik and Cache. Then flash Rom, Gapps, and Magisk.

    DO NOT wipe Data or Internal Storage, that way you're basically doing a clean flash, but without losing all your data.

    This is the way I update every time, just to make things a little "cleaner".
    Ok, I 've seen your message too late…
    I downloaded the image from dec. 16th and istalled it with TWRP. Looks like it worked, but still no wifi.
    But maybe there's a hint: The phone does not show a wifi mac adress. 'not available'
    Everything else seems to work now, startup is fast again and it's really responsive.

    Is there a way to log the init process of the network interface?
     

    lasser1

    Member
    Jan 1, 2021
    8
    0
    Last edited:

    oli004

    New member
    Jan 7, 2021
    3
    0
    Hi,

    thank you for the great work!

    Everything works fine on my Nexus 5... except the accelerator does not seem to be recognised (so rotating the phone does not work).

    Is there some way to troubleshoot? any tips?

    I already tried to flash back the original android: then rotating the screen works. Once I flash back LineageOS 17.1 it does not work anymore.

    Is there a special version, I have to flash?

    Thxs in advance.

    Greetings from Germany

    Oli4
     

    lasser1

    Member
    Jan 1, 2021
    8
    0
    Ok, my phone had a hardware defect. The wifi module came loose.
    Now I bought another N5 (D821, 32GB). It had CyanogenMod on it and ran fine.
    After installing twrp-3.3.1-HH-hammerhead.img via fastboot it started into recovery.
    Sideloading lineage-17.1-20201231-UNOFFICIAL-hammerhead.zip went well, but I want the gapps too, so I downloaded and sideloaded open_gapps-arm-10.0-pico-20210121.zip
    The installer exits with Error Cod 70, insufficient storage space in System partition.
    After that I tried all pico versions for 10, that I have. Same result.

    Now my /system on that device is 1009 MBm 990MB free.
    What is happening here and what can I do to resolve that problem?

    Thanks in advance!
     

    Lughnasadh

    Senior Member
    Mar 23, 2015
    2,025
    1,321
    Google Nexus 5
    Huawei Nexus 6P
    Ok, my phone had a hardware defect. The wifi module came loose.
    Now I bought another N5 (D821, 32GB). It had CyanogenMod on it and ran fine.
    After installing twrp-3.3.1-HH-hammerhead.img via fastboot it started into recovery.
    Sideloading lineage-17.1-20201231-UNOFFICIAL-hammerhead.zip went well, but I want the gapps too, so I downloaded and sideloaded open_gapps-arm-10.0-pico-20210121.zip
    The installer exits with Error Cod 70, insufficient storage space in System partition.
    After that I tried all pico versions for 10, that I have. Same result.

    Now my /system on that device is 1009 MBm 990MB free.
    What is happening here and what can I do to resolve that problem?

    Thanks in advance!
    You need to repartition your /system size. See the link in Post #2 on how to do that.
     

    lasser1

    Member
    Jan 1, 2021
    8
    0
    Last edited:

    oli004

    New member
    Jan 7, 2021
    3
    0
    Hi,

    thank you for the great work!

    Everything works fine on my Nexus 5... except the accelerator does not seem to be recognised (so rotating the phone does not work).

    Is there some way to troubleshoot? any tips?

    I already tried to flash back the original android: then rotating the screen works. Once I flash back LineageOS 17.1 it does not work anymore.

    Is there a special version, I have to flash?

    Thxs in advance.

    Greetings from Germany

    Oli4

    Hi could somebody please please tell me if the accelerator works form them? So are the motion sensors working when turning the phone? compass etc.? which version do you use if it works?

    Thanks
     

    z3DD3r

    Senior Member
    Feb 9, 2016
    195
    1,147
    Minsk
    Google Nexus 5
    Hi could somebody please please tell me if the accelerator works form them? So are the motion sensors working when turning the phone? compass etc.? which version do you use if it works?

    Thanks

    Known problem. Follow next steps to solve:
    • Boot into TWRP
    • Mount "Persist" partition
    • Open File Manager
    • Remove /persist/sensors folder
    • Reboot your phone
    If this will not help then your accelerator is dead :(
     

    oli004

    New member
    Jan 7, 2021
    3
    0
    Known problem. Follow next steps to solve:
    • Boot into TWRP
    • Mount "Persist" partition
    • Open File Manager
    • Remove /persist/sensors folder
    • Reboot your phone
    If this will not help then your accelerator is dead :(
    thank you so much :). it worked!. now everything is working as it should. so phantastic :)
     

    Juno-First

    Senior Member
    Apr 21, 2010
    555
    40
    Stoke on Trent
    Does anyone know how get Android Auto phone screen version work on this?
    Apparantly it supposed to be baked into the OS10 ROM but is available in the Market if running OS10.
    I have Nano GApps & installed all the necessary GApps.
    thx
     

    machineabuse

    New member
    Sep 28, 2012
    2
    0
    Hello all.

    I've encountered a problem trying to get the ROM to sign into Google Play. First encountered during the startup dialogue. After connecting to Wifi, it prints; "Checking for updates." before asking me for an alternative wifi portal, all give the same result.

    Skipping through the dialogues I am able to get into the home screen and verify through the browser that it is indeed connected to Wifi. The setup dialogue prints; "Couldn't Connect. Try again using another network. If you continue without a connection, you can finish some setup steps later."

    Attempting to log into the Play store gives "Checking Info" with a loading circle for a few minutes before finally; "Couldn't sign in. There was a problem communicating with Google Servers. Try again later."

    ---

    Other details

    - I am running twrp-3.5.0_9-HH.R.8.img with the increased partition, lineage-17.1-20201231-UNOFFICIAL-hammerhead.zip as the ROM.

    - I have tried both open_gapps-arm-10.0-pico-20210128.zip and open_gapps-arm-10.0-nano-20210128.zip, both yield the same result.

    - Android system webview is functional and on a fairly recent version.

    ---

    Any assistance is most welcome. Apologies; it has been a while since I've used XDA, I was not able to find the thread search function.

    ---

    UPDATE: Gave up on this build and tried the latest 18.1 build, that works without issue.
     
    Last edited:

    Top Liked Posts

    • There are no posts matching your filters.
    • 80
      LineageOS 17.1 is a free, community built, aftermarket firmware distribution of Android 10.0 (Q), which is designed to increase performance and reliability over stock Android for your device.

      Code:
      #include <std_disclaimer.h>
      
      /*
      * Your warranty is now void.
      *
      * We are not responsible for bricked devices, dead SD cards,
      * thermonuclear war, or you getting fired because the alarm app failed. Please
      * do some research if you have any concerns about features included in this ROM
      * before flashing it! YOU are choosing to make these modifications, and if
      * you point the finger at us for messing up your device, we will laugh at you.
      *
      */
      LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

      The source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.

      Known bugs:
      Fantom icons in launcher after installing/updating apps. Fixed since 2020-03-18 build.
      Expanded desktop doesn't work. LineageOS team planning to remove this feature entirely. This feature was removed in latest builds.
      For some users phone won't boot after installing Magisk. Right now there is no solution. Use rom without Magisk. Fixed since 2020-02-22 build. Credits to @Sashko98 for help!
      Screen timeout does not work if the Screen lock is set to none. Fixed since 2020-05-31 build.
      Random drops of the bluetooth connection. Fixed since 2020-06-13 build.
      Screen mirroring via slimport HDMI adapter doesn't work.
      PMF aka 802.11w doesn't work.

      Downloads:
      ROM: https://sourceforge.net/projects/hammerhead-lineageos/files/17.1/
      GAPPS: https://opengapps.org/?arch=arm&api=10.0&variant=pico

      Credits:
      Many thanks to the LineageOS team and all the contributors out there in the community

      Contributors:
      @z3DD3r, @EnesSastim, @Sashko98, @razorloves, esa-n, jprimero15 and others

      Source Code:
      Device tree: https://github.com/z3DD3r/android_device_lge_hammerhead/tree/lineage-17.1
      Kernel tree: https://github.com/z3DD3r/android_kernel_lge_hammerhead/tree/lineage-17.1
      Vendor tree: https://github.com/z3DD3r/android_vendor_lge/tree/lineage-17.1

      Android version: 10.0.0 (Q)
      Kernel version: Linux 3.4.113
      Status: Stable

      Created 2020-01-23
      Last Updated 2020-06-23
      28
      Don't worry. This build was released by me. Even if my device is dead i still can release new builds from time to time with updates from LOS team...
      19
      Hello everyone!

      Someone maybe already seen that i've release another one update for LOS 17.1 (2020-12-31). Unfortunately this will be last update from my side, cos i need to shutdown my build server and use it for another purpose.

      I've also released one more version of LOS 17.1 (2020-12-31). You can download it from 'signed' folder from sourceforge. This build doesn't have OTA support but it was signed with release keys. I remember that someone asked for such builds) In other terms these builds are the same. Be aware that YOU MUST DO A CLEAN INSTALLATION OF THIS 'SIGNED' BUILD WITH ALL WIPES. YOU CANNOT INSTALL 'SIGNED' BUILD ON TOP OF PREVIOUS BUILDS.

      There is one more update from my side. I can't promise anything, but everything is possible ;)
      LOS_18_1.png


      HAPPY NEW YEAR!
      17
      Hi there

      Unfortunately i should announce that i stopped N5 support. I have no time to support this device anymore. Furthermore and my N5 is almost dead (motherboard corrupted by water)
      Daily builds already stopped. Maybe i'll release a single last build with May security patch in a few days...

      I want to thank everyone who helped to support N5 all this year. It was a really fun and interesting time! Thanks a lot!!!
      Time to move forward...




      What does this mean from your perspective? What's the difference between unofficial and official support?
      Official builds can't include some changes that are included in unofficial builds. Also official maintainer should continue to support and improve builds for supported device...

      @z3DD3r I am trying to compile LineageOS 17.1 with your sources and the build runs through successfully.

      But I am always facing the same issue after flashing (clean, factory reset and no additional zips) the image: The boot animation is displayed very slowly (~1 frame per second). Only the animation seems to be affected, as you can hear the screen locking sound after a couple of minutes while the animation is still running. Once the animation is finished after 5+ minutes, the screen is black, since the device locked itself in the meantime. If you turn the screen on, unlock it and interact with the device, it runs just fine. Snappy and quick, as you would expect. It seems to be just the boot animation, that is flawed in my personal builds, but not in your builds.
      Is there anything I am missing or doing wrong? Are you building from exactly the same sources that you published? Have you also seen this issue?[/code]
      Not all changes can be included in device trees. Some patches are picked from gerrit. I've already answered similar question here.

      Did some further investigation. Had a Whatsapp call yesterday and had the logging running while the call was going on. Found the following lines before the camera was not showing new frames anymore:

      [05-10 10:13:43.765 383:22238 E/mm-camera]
      module_faceproc_port_event_func:886] MCT_EVENT_MODULE_BUF_DIVERT 131074, Cannot start FD, active 20003, frameid 22715 0, native 1, mapped 1 1

      [05-10 10:13:43.784 306:22245 E/Parcel]
      fcntl(F_DUPFD_CLOEXEC) failed in Parcel::read, i is 0, fds is -1, fd_count is 1, error: Too many open files

      [05-10 10:13:43.790 306:22245 E/Camera3-OutputStream]
      getBufferLockedCommon: Stream 0: Can't dequeue next output buffer: Invalid argument (-22)

      [05-10 10:13:43.790 306:22245 W/Camera2Client]
      notifyError: Received recoverable error 3 from HAL - ignoring, requestId 10000001

      So it seems filedescriptors remain open? Most likely something in the ROM somewhere?

      Whatsapp again... Unfortunately this will not be fixed. At least by me...
      16
      Hi there.
      I highly suggest everyone update to 2020-03-18. This build includes some fixes for SELinux, Bluetooth and kernel.
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone