yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] z3DD3r:
Push latest ROM and GAPPS to /sdcard/ and then try next:

1. Boot into TWRP

2. Uninstall Magisk if installed

3. Wipe system, cache, dalvik cache

4. Install ROM from /sdcard/

5. Install GAPPS from /sdcard/ if u use them

5. Reboot into system

6. If phone will boot, then install Magisk if u use it.
[Nexus 5 Original Android Development] JohnDCP:
Thank you very much for your hyper-fast response....I was about to ask how to uninstall magisk but I already figure out and followed your instructions and I got my phone alive back. Again, thank you very much @z3DD3r ! Some issues with google apps after reboot that were solved reinstalling those apps.
[Nexus 5 Original Android Development] beebbeeb:
Hello, I have just installed the LOS 18.1 2022-04-16 version, updated from the 2022-02-28 version. No problem in booting into the 2022-04-16 version.

However, during installation in TWRP, Magisk 24.3 cannot mount the system partition. There is no such issue in the 2022-02-28 version.

Is there any solution to that?

(My Nexus 5 has been re-partitioned to accommodate LOS 18.1.)
[Nexus 5 Original Android Development] z3DD3r:
Not related to rom. Nothing was changed in partitions. Try to install rom (dirty flash) with gapps and magisk following instruction i’ve posted on previous page.
[Nexus 5 Original Android Development] sera:
Thanks @z3DD3r Works great. Gapps pico (May 2 release) didn't work for me even though installed it after the boot of rom. Playstore will not respond to sign in. This one worked MindTheGapps-11.0.0-arm-20220217_095902.zip found it from https://wiki.lineageos.org/gapps.
[Nexus 5 Original Android Development] lulli1:
Why don't you try to install magisk from magisk manager in stead of TWRP?
[Nexus 5 Original Android Development] z3DD3r:
Hi all,

I have updated 3rd post with patches for this rom because LineageOS Team has merged some changes to their repos. If anybody builds the ROM using my trees then please take new patches from 3rd post.
[Nexus 5 Original Android Development] snow:
@z3DD3r Out of curiosity, what changes have you done to 18.1's kernel compared to 17.1's one?

I ask this because LOS 18.1 is ~4 slower at booting time compared to LOS 17.1.

At LOS boot animation stage I can see the circle passing through the line about 16-17 times for LOS 18.1 compared to 3-4 times for LOS 17.1. Perhaps you can fix this.
[Nexus 5 Original Android Development] z3DD3r:
@snow,

Kernel for both 17.1 and 18.1 is the same… Are you comparing my builds of 17.1 and 18.1? I’m asking because i’ve added some changes to kernel tree which wasn’t included in the last build and wasn’t tested. And if you comparing your personal build with my 17.1 then this maybe the answer.

Anyway you may wait until i’ll release new builds with July security patch and then try compare again.
[Nexus 5 Original Android Development] snow:
Hi,

Yes, I'm comparing your builds, I didn't create any personal build of either 18.1 or 17.1.

The longer boot times for 18.1 seems to be present in all 18.1 builds, or at least the last 18.1 builds. This year I've switched from 17.1 to 18.1, I believe I made the switch this spring or something like that.
[Nexus 5 Original Android Development] z3DD3r:
Well this can be Android 11 stuff. As i told earlier it is not right to compare different android versions. Android 11 has more things to setup at boot time. This can explain longer boot time. Moreover LOS 17.1 has strange glitch with boot animation. If i remember correctly you will see a completely black screen before boot animation on LOS 17.1. LOS 18.1 doesn't have such glitch and boot animation starts right after google logo. This also explains why you see the difference. Last time i used these roms i saw 2-3 'circles' on LOS 17.1 and '11-12' on LOS 18.1 with my setup. Also your setup (gapps, magisk, additional apps and services) may affect booting time...
[Nexus 5 Original Android Development] snow:
Yeah, I know there are different Android versions. I also noticed LOS 18.1 doesn't have that boot glitch anymore, unlike LOS 17.1.

It's just, from my own experience, LOS 18.1 feels a lot slower while booting. Even at the "Google" logo stage, I wait for about 30 secs before seeing the LOS booting animation. Maybe more than 30 secs, not 100% sure, but feels slow too. Not sure if this happens due to a different Android version or to some specific kernel changes. Or maybe a combination of both?!

As for my setup, I use the same apps, GApps, and Magisk. Everything is 99% the same.

Didn't mean to be rude or anything like that, sorry if I made you believe so. I just suspect some changes done to the kernel might slow down to a greater extent the boot duration time.
[Nexus 5 Original Android Development] z3DD3r:
No need to apologize for anything. As i told earlier kernel is the same for LOS 17.1 and LOS 18.1. So i believe it is android itself. Maybe the slow down related to new memory allocator or any other services. Or maybe it is related to kernel because something is missed. I’m not a kernel dev and can’t say is it kernel or not. Anyway for my opinion Android 11 is too much for Nexus 5. Android 10 works much better on this device. Maybe CAF version will wok better but it requires some work…

Anyway i feel that this device is EOL. We can run Android 12 on Nexus 5 but it will be even worse than Android 11. Old drivers, old kernel and etc…

If you liked the LOS 17.1 than use it. There is no real need to upgrade to 18.1. 18.1 consumes more memory and this may be a problem for you. All current apps will run on A10 (LOS 17.1) without any issues for a long time…
[Nexus 5 Original Android Development] MilkisFTW:
Very interesting analysis. Do you think that a current, optimized kernel and drivers (which of course will never be there) would possibly significantly speed up this device?

Anyway, thank you very much for still releasing builds for this device!
[Nexus 5 Original Android Development] Baonks81:
We need Android 13, we had tweaks and optimize kernel, so we need more and more new to testing :D. This LOS 11 was so interesting but it needs to upgrade android 13
[Nexus 5 Original Android Development] dum2go:
I have no issues with encrypting the device. My crypto partition is filled with zeros (not sure if it is an accident or manufacturer feature). Actually I have no issues at all, it runs smoothly. No lags. Camera, sound works. Seems like everything working fine... I build img my self.

Also I have to install gapps AFTER first boot. If I install gapps at the same time with system image - gapps crashing and auto reboot the device.
[Nexus 5 Original Android Development] SirRGB:
Well Android 11 did work quite nicely, but z3dd3r doesnt work on it anymore, so even Android 12 is unlikely and if it ever happens it will defenitely lag a lot due to the high hardware requirements on S.

So S and T probably wont happen for hammerhead.
[Nexus 5 Original Android Development] MilkisFTW:
I recently realized that someone is indeed working on bringing the upstream kernel to the Nexus 5. Should that be successful, I think we might see some interesting ROMs again.
[Nexus 5 Original Android Development] Baonks81:
Yes of course, upstream will run pmOS and mobian. Those used Phosh UI, gnome-mobile and mutter will come soon :D. Even waydroid can run Android 12 on those distros
[Nexus 5 Original Android Development] z3DD3r:
Someone made S for hammerhead https://stats.lineageos.org/model/hammerhead ;)

But i guess it was dropped because of performance problems...
[Nexus 5 Original Android Development] dum2go:
Bugs I found, using this build for a month:

1) Notifications ambinet light sometimes do not turn off screen

2) some apps showing garbage on screen (app: cronometer)

3) sometimes power button does not turn screen on

4) slow (low memory, stucks/hungs)

I downgrade back to lineage15.1
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Hello,

First make sure you made a backup of all your important files.

Then you have to make sure that you have the latest version of TWRP installed:

https://xdaforums.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead.4047653/

Give that thread a good read and go through the re-partition process. It's a requirement for some new ROM's and makes it possible to install larger Gapps packages as well if you want to.

Now let's talk about the bootloader and radio, the latest version of the bootloader is "hhz20h" and the latest version of the radio is "2.0.50.2.30". Check if the versions shown by the bootloader match with the ones I mentioned.

If they don't you may need to update them, I'm not sure if that's required but I assume it is.

This guide explains how you can update the bootloader and radio:

https://www.nextpit.com/how-to-update-nexus-5-bootloader-and-radio

With all of that out of the way you can proceed to installing this ROM.

1. Copy the ROM zip, Gapps zip and the Magisk zip to your device. (both Gapps and Magisk are optional)

2. Boot into Recovery.

3. Wipe Dalvik / Art Cache, /System, /Data & /Cache.

4. Flash the ROM zip.

5. Optional: Flash the Gapps zip.

6. Optional: Flash the Magisk zip.

7. Reboot to System.

That's it, good luck!
[Nexus 5 Original Android Development] snow:
I made a migration script for anyone who wants to flash easily from unsigned 17.1 builds to signed 18.1 builds. This way you don't have to make a clean flash of LOS 18.1.

If you're still on an unsigned LOS 17.1 build, all you have to do is to flash the script via TWRP, then you can flash any signed LOS 18.1 build.

It worked well in my case, the first boot since dirty LOS 18.1 installation took a while.

NOTE: Dirty installation might break the lock screen, even if your pin/pattern is correct, leading to impossibility to unlock the screen.

In this specific case, use TWRP and go to the /data/system folder, then delete all the files containing the word "locksettings" and/or "gatekeeper". Reboot the device and then you should be able to unlock the screen and set back any lock screen you want.

WARNING: Use script at your own risk.
[Nexus 5 Original Android Development] marzapane:
Thank you very much for the expansive answer! You answered all my doubts and more
[Nexus 5 Original Android Development] z3DD3r:
Yep, that bug exist. Idk right now what wrong cos some users reported that encryption works fine for them... I'll update first post with known bugs
[Nexus 5 Original Android Development] ViseLu:
Hi! I've installed the ROM but I don't have enough space to install Gapps and if I try to expand the System size it doesn't works. What con I do?
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Have you tried to repartition your device with this recovery?

https://xdaforums.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead.4047653/
[Nexus 5 Original Android Development] z3DD3r:
Hello everyone.

Some spoilers from me:

I guess you know what does it means :)

No magisk, no hacks, just ROM + GAPPS.
[Nexus 5 Original Android Development] bemanet:
Will the wifi Issue with PMF work in future ?
[Nexus 5 Original Android Development] z3DD3r:
This bug wasn't fixed in LOS 17.1 and most likely will not be fixed in LOS 18.1
[Nexus 5 Original Android Development] z3DD3r:
New build with SELinux enforcing available!

PS: Please note that installed Magisk will break your certification in Play Market and SafetyNet checks will fail. This is not related to ROM!
[Nexus 5 Original Android Development] edu24lal:
So if i flash magisk ,safety net will fail?
[Nexus 5 Original Android Development] z3DD3r:
Yep. At least SafetyNet checks failed with Magisk 21.2. Maybe newest beta or canary versions of Magisk will work. I don't know and can't test. Anyway this problem is on Magisk side...
[Nexus 5 Original Android Development] Lughnasadh:
Google did some server-side changes the other night to make a lot of devices fail safetynet by forcing hardware attestation but making it look like you were using evalType basic. This "may" be the problem you are having with failing safetynet checks. It is unrelated to Magisk or the latest update of Magisk. The commit is here to fix it... https://github.com/ProtonAOSP/andro...mmit/15633a3d29bf727b83083f2c49d906c16527d389

There is also a Magisk Mod zip in the Magisk thread to fix it.
[Nexus 5 Original Android Development] z3DD3r:
Well, this commit not required for LOS. My latest build doesn't have any issues with Play Market and SafetyNet checks without Magisk. So for me this problem related only to Magisk 21.2. Btw one user told me that Magisk 21.1 works fine and safetynet checks passed successfully.
[Nexus 5 Original Android Development] realx3m:
Just tried 21.1 , i did have 21.2 before it which i uninstalled with the uninstall zip from magisk github, and then flashed 21.1. So unless the uninstaller leaves some traces, i think its safe to say that it doesnt work for me.

Btw with 18.1-20210113 seems like bluetooth works more stable than the couple of 17.1 builds that ive been using last couple of months and also 18.1-20210109. In all of those before, i did get frequent receiver disconnects with LDAC when switching sample rate/bitrate in devops(especially when streaming music over wifi), and with 18.1-20210113 i can get sort of a hiccup in place of what would be a disconnect on the other builds. For the whole day ive been playing with it, i only got 1 disconnect, id say it dropped from 30% of the time to 10% of the time that happens. Was something done regarding bluetooth in the latest build(or maybe some wifi improvement) , or is it some lucky side effect?

Edit:

BTW Has anyone had any luck with JamesDSP? Been getting system UI crashes after flashing the magisk module.

Or Ryuki Dolby Atmos, depending on the version i was either getting bootloops or app just not starting/crashing. Tried with setprop dolby.force.permissive 1 which worked for me on LOS17.1 , but no luck.
[Nexus 5 Original Android Development] misterfallen:
try many different Gapps zips,always failed.

I used pico package,show me the device does not have sufficient space available in the system partition to install

who can help me，please！

# End Open GApps Install Log

INSTALLATION FAILURE: Your device does not have sufficient space available in

the system partition to install this GApps package as currently configured.

You will need to switch to a smaller GApps package or use gapps-config to

reduce the installed size.
[Nexus 5 Original Android Development] sant514:
https://xdaforums.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead.4047653/
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Try to search for a solution before asking for help.

Scroll up a bit, I literally posted a solution for someone with the same issue as yours a couple of posts above.
[Nexus 5 Original Android Development] aa84:
Great rom! Its really smooth especially if you turn off window/transition/animator scale in developer settings.

I tried dirty flashing from 17.1 using snow's script but the homescreen would crash at "phone starting" screen - wiping system and data then reinstalling fixed it.
[Nexus 5 Original Android Development] mrvelvet:
Has anyone had success with the built-in OTA updater?

I tried with TWRP 3.4.0-HH-R7 (twrp-3.4.0-HH.R.7.img) as recovery but it fails to update with an error about a recovery.img in the TWRP log (though I did uncheck the "Update recovery" from within the updater Preferences.
[Nexus 5 Original Android Development] zagzag99:
Is there a maintained 15.1 ?
[Nexus 5 Original Android Development] dum2go:
No. Build it from original lineageos 15.1 source. Looks fine for a few months.
[Nexus 5 Original Android Development] fckwan:
Will there be any plan to upgrade to Lineage OS 19 for Nexu 5?
[Nexus 5 Original Android Development] zhengz:
hello, thank you for your great work

if i want to build the lineageos 18.1 for myself, how can i apply the SurfaceFlinger patchs?

i have already applied other patches by replacing folders with ones from your github, but the SurfaceFlinger patch is on the lineageos gerrit, does it mean that these patches already included in lineageOS code and there's no need to apply them manually?

thank you.
[Nexus 5 Original Android Development] z3DD3r:
No

1. You should not replace original folders with mine. You should apply listed patches on top of original folders (cherry-pick). I’ve posted a command for each patch from my github.

2. Patches from gerrit are not included in LOS code. You should also apply them to required folders. Click on ‘Download’ button on gerrit, then copy command under ‘Cherry Pick’ and apply to it to required folder
[Nexus 5 Original Android Development] zhengz:
Thanks for your reply! I will try it later. maybe i have to learn more about cherry-picking.
[Nexus 5 Original Android Development] pingwin123:
I have a question. It looks there are monthly updates showing up at https://sourceforge.net/projects/hammerhead-lineageos/files/18.1/ . The newest version is dated 2022-11-11. However I cannot find a changelog. Are these new updates just an automated security-patches builds or do they bring new features and fixes as well?

I have an issue with "Pioneer Remote App v.3.0" - the screen is flickering strangely on 2022-10-20 build (the previous 2.0 version worked well). I wonder if this issue has been fixed in new LOS 18.1 build.
[Nexus 5 Original Android Development] z3DD3r:
Try it and tell us. This new build includes november’s security patch and some changes in kernel
[Nexus 5 Original Android Development] eBug:
I have the flickering with some apps too with 17.1. But I have it on my Nexus 7 too, so I think it might be related to the code in the apps rather than the device itself?
[Nexus 5 Original Android Development] eBug:
I'm back to Nexus5 as a daily driver.

I know this topic has been discussed before, but given the current state of the 17.1 and 18.1 builds, which version would you recommend in terms of battery and stability?
[Nexus 5 Original Android Development] pingwin123:
I prefer 18.1 build as it works quite well. Didn't notice significant change in battery efficiency, however if you want to use N5 for everyday use I would recommend someting like that: https://xdaforums.com/t/mugen-power-3000mah-battery-case-for-the-nexus-5-review.2986295/
[Nexus 5 Original Android Development] jenkinsad0:
Thanks very much for the new build! Downloaded the 20221111 version and the appropriate gapps and it seems to work OK. Replaced an installed /e/ OS which wasn't being updated any more.
[Nexus 5 Original Android Development] paul222008:
Hi what does /e/ OS means?
[Nexus 5 Original Android Development] jenkinsad0:
https://e.foundation/e-os/ - which I had installed after an unofficial build of LineageOS 14 stopped being updated.
[Nexus 5 Original Android Development] assdredxexfg:
Hi,

I am not able to install it.

I always get

E:1001: Failed to update system image.

I have tried with:

- Stock TWRP

- twrp-3.7.0_9-HH.R.17.img

- twrp-3.7.0_9-HH.S.17.img

and lineage-18.1-20221111-UNOFFICIAL-hammerhead-signed.zip

any idea?

thx
[Nexus 5 Original Android Development] LegendOcta:
Did you do the repartitioning?

You should follow the guide in HH TWRP's XDA post.
[Nexus 5 Original Android Development] assdredxexfg:
thx, after hh_repart -m it worked
[Nexus 5 Original Android Development] Stepyon:
Hi,

I have rooted the ROM with Magisk and also installed IPControl module to be able to limit the phone charge when it is constantly connected to a charger. But when trying to use the module under SU I'm getting Permission Denied, how is that possible? Any hints how to fix? Or maybe someone has found another working way to limit phone's charging?
[Nexus 5 Original Android Development] z3DD3r:
@Stepyon,

su doesn't necessary allows you to run any commands. Check the file and group permissions for ipc. Also you may try to switch to permissive mode using the senenforce 0 command in terminal or adb shell
[Nexus 5 Original Android Development] Stepyon:
Tried to give the permission, now says that the device is not supported, but it is in the supported list of IPC module.
[Nexus 5 Original Android Development] z3DD3r:
New build (20230218) with february security patch is out!

Please don't ask me for OTA or any bug fixes.

I don't have Nexus 5 anymore and can't provide proper support.
[Nexus 5 Original Android Development] johnnybgoode1885:
Hey! Thanks for your build for our devices. Unfortunately, after wiping everything and repartition I'm unable to flash the ROM from /sdcard. It says "Failed to update system image". I suppose it might be due to the fact that this might be an OTA package and not a full image? Where do I get the full image? Thanks!
[Nexus 5 Original Android Development] Edevane:
Gapps don't install
[Nexus 5 Original Android Development] edu24lal:
Rom works super fast, no issues, only bug i found was with gesture bar, when a play a game, gesture bar does not move horizontally if i go to recent apps it moves, but then if a go to home screen gesture bar stays on the side of the screen
[Nexus 5 Original Android Development] candrayudhatama:
Wifi display is fix it ???
[Nexus 5 Original Android Development] Edevane:
please put the gapps compatible with the rom
[Nexus 5 Original Android Development] z3DD3r:
I already answered this question. Most likely Wi-Fi Display will not be fixed. I'll remove it from UI in the next build.

Right now there is no release version of gapps for Android 11. Links in the first post will start work once opengapps will be released. For now u can use unofficial builds of opengapps or test versions from here: https://sourceforge.net/projects/opengapps/files/arm/test/ Also read the second post of this thread about gapps installation...
[Nexus 5 Original Android Development] abcdef121448:
I have installed your Version 17.1 on my Nexus 5 and I am incredibly happy with it. It´s crazy that a 7.5 year old phone can run so well. The only problem is that after about 55h of runtime apps start freezing and force closing randomly and the phone gets a lot more sluggish. It seems like it has a problem clearing the RAM? Has anyone with v18.1 experienced the same behaviour? If not I will update and give it a try. Rebooting your phone every 3 days isn´t fun.
[Nexus 5 Original Android Development] edu24lal:
Yeah me tooo
[Nexus 5 Original Android Development] edu24lal:
Guys latest build with latest magisk safety net passed 😁
[Nexus 5 Original Android Development] edu24lal:
Another bug i found, after booting (not sure how much time after normal use) videoplayback from whatsapp,telegram stops working. youtube , instagram videos work fine tho
[Nexus 5 Original Android Development] candrayudhatama:
I try clean install version 2021/16 google map is not working navigate is freez....I try another app it's still same.... navigate not working
[Nexus 5 Original Android Development] jvifdz:
Hi where can i found The changelog of The builds?
[Nexus 5 Original Android Development] Mr.FREE_Bird:
You can see the changes on Gerrit Code Review.
[Nexus 5 Original Android Development] candrayudhatama:
Notification bubble is not included in last build ????
[Nexus 5 Original Android Development] caravagio:
Excellent rom for nexus 5, everything it's working as it should, battery life is a bit low but hey, we cannot expect miracle from a 7 year device. Keep up the good work!
[Nexus 5 Original Android Development] z3DD3r:
Well, Android 11 consumes more memory than Android 10. So i guess you will see the same problems on LOS 18.1

Try new build 2020-01-21

Try new build 2020-01-21. Clean flash is recommended. Google Maps works fine for me

This is only for new devices. FDE worked fine on Android 10 on hammerhead. Moreover maintainer of G2 told me that FDE encryption works on his device. So i need to find what is wrong on hammerhead. I can't give u any timelines because i'm out of free time :(

Maybe it was disabled. Can't say. I didn't change anything. Each version was built from LOS sources without any changes...
[Nexus 5 Original Android Development] candrayudhatama:
Thanks for new update 😁
[Nexus 5 Original Android Development] candrayudhatama:
Finally can install Viper4Android 😁 last update build rom
[Nexus 5 Original Android Development] edu24lal:
Same for me, location does not work, using new build