yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] abcdef121448:
@z3DD3r yes thank you! It works perfectly now. Still trying to troubleshoot the wifi issue with that app though. I tried a reinstall but that sadly didn´t help. I think I will contact the app developer.
[Nexus 5 Original Android Development] z3DD3r:
@abcdef121448,

Thanks for test! I think i will release a new build with this kernel with September’s security patch
[Nexus 5 Original Android Development] hackepeterbroetchen:
Thank you so much for your work! Is there any ETA for this release?
[Nexus 5 Original Android Development] z3DD3r:
No ETA. This depends on how fast google will push september security patch to aosp and how fast LineageOS team will merge it into their repos.
[Nexus 5 Original Android Development] hackepeterbroetchen:
Is there any documented upgrade path without losing data?

I'm fairly new to lineage and I would like to give my old Nexus to my parents.
[Nexus 5 Original Android Development] Crrrr:
1. Dirty flash when you are upgrading the same custom rom;

2. using a back-up app, such as Migrate, when installing a new custom rom or moving to a new device.
[Nexus 5 Original Android Development] z3DD3r:
New build is out. lineage-18.1-20210913-UNOFFICIAL-hammerhead-signed.zip.

Short change log:

September security patch.

Charging currents are reduced to stock values as on android 6.0.1

Updated interactive governor

Updated ZRAM driver (version from 4.1 kernel)

Updated F2FS driver (version from 3.10 kernel)

Small fixes and improvements in kernel
[Nexus 5 Original Android Development] Glonf:
Hi

Is your GPS already working?

Because I have this problem too ://

@z3DD3r Do you know how to fix it?

​
[Nexus 5 Original Android Development] z3DD3r:
@Glonf,

I don't have Nexus 5 anymore and can't test. But i've asked my tester to check this app. He has no problems at all. Look at attached screenshot. He uses clean installation of latest LineageOS 18.1 (2021-09-13) + OpenGapps pico (2021-09-14)
[Nexus 5 Original Android Development] Glonf:
I don't have a gps in general, not necessarily in this app.

I have everything the same, on lineageos 14.1 I had gps, so I don't know what the problem could be.

I will try to reinstall it again.

Edit:

It is possible that I broke the gps antenna and something is not touching.

Because on other versions of android there is also a problem.
[Nexus 5 Original Android Development] mag01:
Looks like the last build (0913) was pulled. Is there anything wrong with it?
[Nexus 5 Original Android Development] z3DD3r:
Looks like this is a reason of broken GPS for you. Check the connection between connectors on back cover and motherboard.

I've uploaded this build twice on SF because first build disappeared from SF for some unknown reason. If you was lucky and installed first build then rn you can see a new update in updater app. You can install it but this second build of 09/13 doesn't have any difference from the first one except a build date :)
[Nexus 5 Original Android Development] abcdef121448:
My GPS is working again perfectly. I think the app just had a small hickup :)
[Nexus 5 Original Android Development] ssauger:
I tested 2 hours ago with latest build and got a gps fix within few seconds. I used gpsstatus from playstore.
[Nexus 5 Original Android Development] z3DD3r:
Nope. All required patches are listed in the 3rd post of this thread.
[Nexus 5 Original Android Development] Glonf:
I fixed the GPS antenna, also had to fix the wifi module so that it connects me to the GPS at all.

I don't know what the GPS wifi module has, but I had to heat the wifi module with a heat gun according to the guides.

I didn't do it that well and therefore I can't always turn the wifi on properly, but it's better than last time that I couldn't turn it on at all..
[Nexus 5 Original Android Development] z3DD3r:
This flag is defined here:

android_vendor_lineage/build/soong/Android.bp at lineage-18.1 · LineageOS/android_vendor_lineage

Contribute to LineageOS/android_vendor_lineage development by creating an account on GitHub.

github.com

android_vendor_lineage/config/BoardConfigSoong.mk at lineage-18.1 · LineageOS/android_vendor_lineage

Contribute to LineageOS/android_vendor_lineage development by creating an account on GitHub.

github.com

Maybe something changed in LOS source code since i've released last build. But check patches you are using. Maybe some of them removed this flag...

Glad to hear it. So right now GPS is working for you on latest build?
[Nexus 5 Original Android Development] Glonf:
Yes, it works on the latest version.

Version downloaded on September 14

lineage-18.1-20210913-UNOFFICIAL-hammerhead-signed
[Nexus 5 Original Android Development] z3DD3r:
This will not happen. Last builds were released cos of critical problems found by some users. They are fixed now so… I don’t have this device anymore. This ROM is discontinued and i have no plans to restart support
[Nexus 5 Original Android Development] z3DD3r:
Well, everything is possible ;)
[Nexus 5 Original Android Development] am2013:
hi all,

I have an issue with an app and not sure what is causing it. The device is being protected by google's family link. Now only when I install Angry Birds 2 for my kid, it is not possible to update the game when a new updae is available. Update will always download and fail finally. The when I uninstall it and want to install it again it will also fail. It will only install when I erase dalvik cache and cache from TWRP (after uninstalling before). Do not have any issues with any other games or apps. Any idea what is causing it? Is this due to some permissions?
[Nexus 5 Original Android Development] HelmutK.:
I tried to install the last release and get a bootloop.

After I format the device if tried again to install and get:

E1001 Failed to update system image

Failure 1

So I tried the older version but I got still the same message.

If I try to install the last 17.1 version I get the message

E1001 Failed to update system image

Failure 7
[Nexus 5 Original Android Development] z3DD3r:
@HelmutK.

Check that:

1. You are using latest version of TWRP

2. MD5 checksum of roms are valid (MD5 of the zip can be found on sourceforge)

If that will not help then:

1. Try to use sideload in TWRP.

2. Check filesystem of your partitions in TWRP. System should be ext4, data/cache - ext4 or f2fs

3. Check your partitions layout. You can dump partitions layout with TWRP HH.R.
[Nexus 5 Original Android Development] HelmutK.:
Thank you! Now my phone is working again.
[Nexus 5 Original Android Development] eryu5698:
Stopped working wi-fi.
[Nexus 5 Original Android Development] castor_fou:
I have been using 18.1 for a month.

Today I see an update OTA. It is downloaded but fails to update. error 21 (something like signature verification fails)

my 1st guess is that because hammerhead is discontinued, the standard lineageos update cannot find the proper image? I tried by downloading (from https://sourceforge.net/projects/hammerhead-lineageos/files/18.1/ version oct/24)and applying manually but without success.

Don't know if you had better success than me on that update?
[Nexus 5 Original Android Development] ssauger:
I was able to update from the link you posted. I made a full backup in twrp, wiped system cache and installed the rom and gapps. All went fine. October security patch is there.

Edit: the inbuild camera is now able to save photos
[Nexus 5 Original Android Development] bluetooth-bug:
For the build lineage-18.1-20211024-UNOFFICIAL-hammerhead-signed.zip clean install is recommended. According to z3DD3r a clean install is recommended. He posted this build on 4PDA. If you don't then you need to uninstall Magisk by flashing the uninstall zip and removing /data/misc/radio/qcril.db then wiping Cache and Dalvik/ART cache partition. After that you can flash the build. SHA1 hash for the last build was 187076f1c8468266815c70786c2201401ca89ead

I decided to dirty flash and in the process I flashed OpenGapps 21 October 2021 as well. But I have massive battery drain issue. That was the case with the previous build before lineage-18.1-20211024. I'm not sure if this is because of the new build or because of OpenGapps. Currently there was an issue with OpenGapps and Play Services was missing from every build after 21 October 2021.

Also I see some commits on GitHub so safe to say the build was pulled because there were some issues. A new build will be available soon so let's just all be patient.

Edit: I can also confirm that Camera is fixed and images are not corrupted anymore. Can take pictures and can view them on the phone and in IrfanView images are showing as they should.
[Nexus 5 Original Android Development] z3DD3r:
Hello

New build of LOS 18.1/17.1 will be released in 24 hours. Some of you already saw that old builds were removed from sourceforge. This was done intentionally because of bugs with play market and selinux. The last available LOS 18.1/17.1 doesn’t have these problems but also does not includes ZRAM. I will not explain it in details just will say that ZRAM will be enabled again in new release. Also i don’t know why camera started to work without issues because the fix is still not included into LOS source code (but already exists). So maybe i will include these patches into upcoming build.

Will post here when new builds will be ready
[Nexus 5 Original Android Development] bluetooth-bug:
I flashed build 20211101, and had battery drain for the last couple of builds. But I also flashed the previous build that was pulled as well. Before flashing 20211101 I turned off the phone, charged it to 100% via offline charging. I had an updated OpenGapps zip downloaded, but that was pulled as well so I deleted that.

So with OpenGapps from 21 October 2021 I did the dirty flash according to the instructions, then I updated Play Store and Google Play Services and this was about 4 hours ago as the time of writing. But for me the battery drain seems to be resolved. Currently I have 97% battery life, still stock battery. I'd say that's good, but I might be wrong and something else causes the battery drain.
[Nexus 5 Original Android Development] dephekt:
I'm trying to download the latest build from SF. Am I just a total idiot or is it not there anymore? On the Summary page I still see a link (updated 6 hours ago) for https://sourceforge.net/projects/ha...101-UNOFFICIAL-hammerhead-signed.zip/download but when I go to that it's telling me the file doesn't exist.

I also took the OTA JSON file for 18.1 and grabbed the download URL from that and it also doesn't work for me.
[Nexus 5 Original Android Development] z3DD3r:
20211101 still has battery drain issues because of missed CPU low power modes in ROM. This can be reproduced even if you install only ROM without gapps. Just wait for new build

Read my message above. This build was removed. New one is coming soon
[Nexus 5 Original Android Development] bluetooth-bug:
88% right now. Definitely discharging faster than usual. Thank you!
[Nexus 5 Original Android Development] bluetooth-bug:
Battery drain issue confirmed fixed. 2% discharge in 14 hours.
[Nexus 5 Original Android Development] Starbomba:
Definitely my experience as well. Dirty flashed 1102 from one of the July builds that just somehow worked for me, used the instructions provided, and it just worked. Battery wise it's the same experience as well on my Nexus. I did have battery drain issues with 1101, but before installing 1102 i went back to my known good build, and dirty flashed over that one. Thanks goodness for TWRP.

While my Nexus is now my third active phone and is not officially full backup, it did get me out of trouble for a month when i didn't have my A52 and i had broken my Pixel XL screen. ROMs just like this one meant to give a new breath of life to old but still capable phones are always welcome.
[Nexus 5 Original Android Development] ewoks:
Hi, didn't do this for a long time on my Nexus5, so I would need a tip or two.. :/

Flashed the newest twrp-3.5.2_9-0-hammerhead.img, pushed the newest lineage-18.1-20211102-UNOFFICIAL-hammerhead-signed.zip, selecting install in recovery mode and I get "E1001: Failed to update system image." error logged after "patching system image unconditionally..."

What did I forget..? :/

Thanks in advance
[Nexus 5 Original Android Development] ssauger:
I think you missed from second post:

"

To install rom you should increase the /system partition size

This can be done for example with

TWRP HH.R

"
[Nexus 5 Original Android Development] ewoks:
yup, that was it. Thanks a lot!

For others TWRP_HH with terminal command from here https://xdaforums.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead-discontinued.4047653/ is necessary to repartition from legacy system as ssauger suggested
[Nexus 5 Original Android Development] hersh785:
Why doesn't it root with supersu? I flashed supersu from here https://download.chainfire.eu/696/supersu/ and flashed it from TWRP and in TWRP it appeared 'done' but when I reboot I see it's not rooted!
[Nexus 5 Original Android Development] z3DD3r:
I guess because SuperSU is not adopted for Android 11. Use latest Magisk from github for root. It works without issues.

But be aware that root solutions are not a part of ROM and not supported by ROM developers. So you should install them on your own risk.
[Nexus 5 Original Android Development] z3DD3r:
New build (20211111) with November security patch is out!

This build includes a fix for built-in camera
[Nexus 5 Original Android Development] mag01:
Does anyone have issue with incoming message notifications appearing with like 15 min - 1 hour delay when the phone is idle?

I tried the solution mentioned in the last post here https://xdaforums.com/t/delayed-notification-lineage-os-17-1-essential.4122305/ and hope it's going to help. However the com.android.messaging app was already whitelisted as system app so I'm not sure if it's going to actually help.

There's also this Reddit thread about it

https://www.reddit.com/r/LineageOS/comments/dpk7v4
mentioning some cases when whitelisting the messaging app as system app didn't help.
[Nexus 5 Original Android Development] z3DD3r:
Unfortunately this is known issue with native SMS app in LineageOS. And the only way is to whitelist this app. LOS 18.1/17.1/16.0 for N5 doesn't include this patch for whitelisting SMS app so you should do this yourself via adb shell. But as you already said this workaround may not help and nobody knows why.
[Nexus 5 Original Android Development] Starbomba:
Nope. However, i've never used the stock Lineage messaging app, i always replace it with Google Messages with Aroma GAPPS.
[Nexus 5 Original Android Development] Myt7930:
When rooting via magisk, can I than uninstall /system files (like built in browser etc.) ?

Usually, I couldn't (it probably doesn't unmount the /system files). I found this solution online, but I didn't try it yet.

Uninstall System Apps on Android with Debloater Magisk Module - DroidViews

Nearly all Android phones come with useless software pre-installed by manufacturers or carriers. Even Nexus devices are preloaded with many Google-created apps which if you don’t use, are simply bloatware. The situation has been improving over time with OEMs pushing in less and less bloat...

www.droidviews.com
[Nexus 5 Original Android Development] Romain1221:
Hello,

I'm a newbie in LOS and before installing it on my nexus 5 16gb I would like to know what is the size of LOS18 along with Gapps. Why is this information is not accessible? I feel like some people are adjusting their partition in a fail and retry mode using TWRP. Is it not possible to list the different sizes ?

And given that it is 16gb what LOS you would recommend if not 18.1 ?

Thanks !
[Nexus 5 Original Android Development] z3DD3r:
Hello,

Rom installation instructions are in the second post of this thread. The size of rom along with gapps can't be provided cos each new build of rom/gapps may increase or decrease in size. Also your phone variant (16Gb or 32Gb) is not important. The only important thing is that Nexus 5 in stock has 1Gb system partition which is not enough for LineageOS 18.1 even without gapps.
[Nexus 5 Original Android Development] Romain1221:
Thank you for your reply. The 1.4Gb is only for LOS18.1 right ? How do I know how much space I need if I want to add Gapps nano or pico ? Is it more or less the size of the install file ?
[Nexus 5 Original Android Development] z3DD3r:
Why 1.4Gb? Where did you find that info? As i told i can’t tell you the size cos it can be changed and i don’t want to check and update it for each new build. If you want to know how big is latest rom you can view the used/free space on the system partition after rom flash in TWRP.

Also can’t tell you anything about opengapps. Just flash package you want. And if it will not fit then you can search for details in opengapps log (will be created in the same folder with .zip). The only thing i can tell you is that pico can be installed on system increased by TWRP HH.
[Nexus 5 Original Android Development] Romain1221:
The 1.4Gb comes from the link of your second post that explains how to use TWRP for the rom installation. But my guess was that it was only for LOS and that seems to be the case. It's great if twrp does the work for pico but I find strange not to be able to know beforehand how much space I need to set for my system partition since for LOS18.1 Android 11 on gapps there is only one option to download for pico or nano, so only one possible minimum space required for pico or nano But there's probably something I'm missing here and I'll do as you say by checking the amount of space takes the flash.

Thank again for your help.
[Nexus 5 Original Android Development] z3DD3r:
1444Mb is the size of your /system partition after repartition process in TWRP HH. it has nothing to do with the rom size and opengapps size. And TWRP HH is not only for LOS. It is just a simple way to increase your /system size. You can use TWRP HH to increase system partition and install all ROMs (LOS, crDroid, NitrogenOS, HavocOS) based on Android 11 with at least opengapps pico
[Nexus 5 Original Android Development] Romain1221:
Then I'm definitly missing something. The way I understand it is that I have to adjust my system partition using TWRP to make sure I can install LOS using TWRP on my nexus (bc as you said 1gb on my nexus is not enough) but my system partition needs to be large enough to accept my ROM+Gapps. If my rom size is 2Gb, then we agree that on twrp I need to set my system partition at least to 2gb ? And If I add Gapps I need to crank it up a bit more so that I do not get space error right ?
[Nexus 5 Original Android Development] z3DD3r:
You are right. I'm trying to say that /system partition size after repartition process is not the size of ROM or ROM+GAPPS.

For example today LOS may require 1050Mb of free space to install. But tomorrow LOS would required 1040Mb or 1110Mb of free space. The same may happen with GAPPS.

If 1444Mb is not enough for your needs, then you can increase your /system partition even more using the parted tool. But that is another story...
[Nexus 5 Original Android Development] Romain1221:
Yes exactly, which is why I was trying to get the space I need to set because I guessed that the size of ROM and GAPPS is not the same size of the installation of the smartphone.

But if LOS changes in size then it means that it is another version and not 18.1 right ? If so LOS18.1+the corresponding Gapps-nano will always take the same space on the phone no ?
[Nexus 5 Original Android Development] z3DD3r:
No. Even if size of LOS 18.1 and Gapps Nano for Android 11 will increase they will still be LOS 18.1 and Gapps Nano for Android 11. But the chances that this will happen are really low
[Nexus 5 Original Android Development] Romain1221:
oh...I see. Ok, thx for the answers.
[Nexus 5 Original Android Development] s0epkip:
Thanks for reviving my good old Nexus 5 with this Lineage rom! It runs great :D
[Nexus 5 Original Android Development] s0epkip:
By the way, if you are going to install LOS and use TWRP to resize your partitions, please note the following sequence (detailed steps are found in numerous other guides):

- Install Android SDK (ADB USB driver and ADB command line tools) on your computer

- Use ADB to unlock your bootloader (device will be wiped)

- Use Fastboot to push TWRP to your phone (choose the .R version)

- Use TWRP instructions to resize your system partition (your OS will be bricked, you cannot normally boot your phone after this step)

- Use recovery mode (=TWRP) to push the LOS and pico GAPPS to your phones' storage (' /sdcard/ ') with the computer. Just sent the zip files, renamed to short names for ease of use

- Use TWRP to flash both LOS and GAPPS in sequence

- Enjoy LOS :)
[Nexus 5 Original Android Development] Romain1221:
Thanks for the guide ! It will make things easier :)
[Nexus 5 Original Android Development] amosstevens:
i have an issue trying to enable the wifi, it won't turn on, but the mobile data works

i'm on the latest build (2021 11 11), magisk 23.0 and twrp 3.5.2_9 hh.r.15

this is the the log

WifiVendorHal

Failed to create STA iface

WifiNative

Failed to create iface in vendor HAL

WifiClientModeManager

Failed to create ClientInterface. Sit in Idle

any advice ?
[Nexus 5 Original Android Development] MilkisFTW:
I just made a current build of this ROM for myself and it seems to me that the SurfaceFlinger related patches are no longer necessary.

(I already built this thing about a year ago and without applying patches I had massive boot animation lags, which are now gone)
[Nexus 5 Original Android Development] z3DD3r:
Interesting! Anyway this patch will not do any harm. I leave SurfaceFligner patches here because nobody knows what can be changed in the future…
[Nexus 5 Original Android Development] cyclofosfamide:
Found my good old Nexus 5 in the drawer. Installed this LineageOS.. working great!

Even fixed the audiocable problem today!
[Nexus 5 Original Android Development] shane.kelly55:
I have tried everything to get this to work but i cant get past the Error 1 during flash of LineageOS. I have gone thru the fixes online but nothing works. I can flash the official version 6.x from Google but no custom ROMs. I have done Magisk with the modified boot image too.

Any idea how i can get 18.1 on this device?
[Nexus 5 Original Android Development] SirRGB:
Did you repartition? What version of twrp did you install?
[Nexus 5 Original Android Development] brofkims:
I just have built the latest source you applied today. So far so good, but the URI about 'hardware/qcom/display' should be settled. It is not inlined, so applying it via 'copy & paste' should fail. Thanks a lot for your come back!
[Nexus 5 Original Android Development] z3DD3r:
Thanks, i've updated the post with patches

And please don’t think that i returned to development. I’ve just uploaded some changes that was in my private repos…
[Nexus 5 Original Android Development] nykstark98:
So we won't see a lineageos 19.1 for this phone?
[Nexus 5 Original Android Development] SirRGB:
there are msm8974 phones booting A12.1, so it is definitely possible, just someone has to do it...
[Nexus 5 Original Android Development] BigBin1070:
does the phone app crash for any one? or is it just because I don't have sim card installed? I tried the system one as well as the google one
[Nexus 5 Original Android Development] z3DD3r:
Nobody reported such issues. Try to do a clean flash with formatting data
[Nexus 5 Original Android Development] SLS24:
Thank you for updating z3DD3r!! ( I use LineageOS 17.1 & lineageOS 18.1)
[Nexus 5 Original Android Development] JohnDCP:
Hi there, I'm getting stuck into a bootloop after an OTA update last April 16. I was running LineageOS 18.1 in my Nexus 5 very well until this last OTA update. After zip download and update, the system automatically reboot and the phone get stuck into the lineageos logo for 2-3 minutes and then reboot into the TWRP. Please help!