yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] lasser1:
Thanks!

quote from a newly generated error report:

01-03 18:48:37.645 1000 668 1719 I WifiService: getVerboseLoggingLevel uid=1000

01-03 18:48:37.665 1000 668 812 E SupplicantStaIfaceHal: Can't call getMacAddress, ISupplicantStaIface is null

Hardware fault?

EDIT: Hint to myself: READ ADVICES BEFORE REPLYING!

But, my Bluetooth is fine! Works like a charme…
[Nexus 5 Original Android Development] oli004:
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
[Nexus 5 Original Android Development] QQ7Q:
There are some regular updates for Nexus 5. Why isn't Nexus 5 offically supported? What prevents LineageOS to put this phone at https://download.lineageos.org/?
[Nexus 5 Original Android Development] lasser1:
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!
[Nexus 5 Original Android Development] Lughnasadh:
You need to repartition your /system size. See the link in Post #2 on how to do that.
[Nexus 5 Original Android Development] lasser1:
Oh thank you! That did the trick.

And how embarrassing I did not read it up myself…

But for the records:

lineageOS gapps error code 70 -> repartition the device

(https://xdaforums.com/t/rom-unofficial-lineageos-17-1-for-nexus-5-hammerhead.4039273/post-81566257)

works like a charme :)

Thank you for everything!
[Nexus 5 Original Android Development] Lughnasadh:
(y)
[Nexus 5 Original Android Development] oli004:
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
[Nexus 5 Original Android Development] z3DD3r:
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 :(
[Nexus 5 Original Android Development] oli004:
thank you so much :). it worked!. now everything is working as it should. so phantastic :)
[Nexus 5 Original Android Development] Bouquins:
Am I getting confused, or did I see a 18.1 version ?
[Nexus 5 Original Android Development] lasser1:
No, you've your wits together… z3DD3r opened a thread about 18.1 on N5 :)
[Nexus 5 Original Android Development] Juno-First:
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
[Nexus 5 Original Android Development] machineabuse:
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.
[Nexus 5 Original Android Development] Bouquins:
Thank you very much !
[Nexus 5 Original Android Development] ljanzen:
Flashed January 31st build over Lineage 16 from November, then the January 31st Open Gapps. The phone seems to be working well, especially responsiveness on wake. Made an ADB backup then flashed Magisk 20.3 from TWRP, wiped cache/dalvik. Phone booted without issue & I have root.

The only issue I'm experiencing is an inability to connect to my OpenWRT access points. It seems I can connect to an older AP but not these ones, the connection never gets through. This is somewhat confounded by attempting to turn on WPA3 at the same time but even after reverting the security to WPA2 it refuses. I have a modern Windows device that is able to connect to both the older WPA2 SSID & newer WPA3 one. Would it be possible to compile with WPA3 support? source.android.com/devices/tech/connect/wifi-wpa3-owe
[Nexus 5 Original Android Development] anilspice:
@ z3DD3r kindly advise which TWRP is recommended for LOS 17.1.

The current 3rd Feb rom with 31 Jan nano gaaps is working fine on carrier data but WiFi does not scan /search or connect and No Mac address.

Magisk also works. Wifi sometimes connects but then switches off on its own. and the wifi button grays out.

Is this issue related to the

type of TWRP

being used by me?

Which TWRP is recommended: twrp-3.3.1-2.0GB-HH / twrp-3.3.1-HH-hammerhead / twrp-3.3.1-1_UA-hh / twrp-3.3.1-0-hammerhead (with repatriation??).

Any Specific Format Options or steps required during TWRP or ROM install i.e for /system /vendor /data and /cache.

Kindly advise. Thanks in advance.
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Hi,

I would advise to use this version of TWRP --> https://xdaforums.com/google-nexus-5/orig-development/repartition-nexus-5-repartition-t3844395

Carefully read the OP and follow the instructions. It works fine for me. As for the issues you are experiencing, I do not.

Maybe it's due to how you flashed the ROM, Magisk etc.

What I did before installing the ROM was wiping /system, /data, /cache and /dalvik-cache. Then I proceeded to flashing the ROM, Magisk, Criterion Kernel and at last the latest Pico Gapps package.

Following these instructions and flashing everything in that order should work just fine for you too. (Of course flashing the Criterion Kernel is not necessary, just to be clear.)

Hopefully you'll find this helpful.
[Nexus 5 Original Android Development] anilspice:
Thanks, will follow your advise and let you know how it goes :fingers-crossed:
[Nexus 5 Original Android Development] idnaidna:
No problems here with the latest build. Thank you for your dedication.

I was coming from an unofficial 15.1. Installed the TWRP version from page 2 in order to repartition, wiped pretty much everything, installed 17.1, Gapps 10 (pico) and Magisk 20.3 (in this order). No problems so far, everything seems to work as intended (device is mainly used as phone).
[Nexus 5 Original Android Development] bigsupersquid:
Latest build on my device, dirty flash over some Lineage 16 build, official TWRP, is working better for me than the Pie version on (t-mobile MVNO) mobile data. I was getting connection issues in Pie which would show 3G or LTE but have the dot of death in the signal strength triangle, and not ping or connect to anything. I have not seen that once in this ROM yet. Wifi is working fine for me, on an older AP and on one new enough that an iPhone 4 sees it but refuses to connect to it.

I need to test further to see if this has the same battery life issues I was getting in the Pie build. I had to disable background and network in almost everything just to keep it alive during sleep, and trying to use it, it looked like my ancient LG optimus V with a BRCM4325 driver from Hades.... battery meter dropping so fast I could see it. Maybe junk battery from Amazon, maybe issues in the Pie ROM, I dunno yet, but still testing. //edit: nope, it's my battery, drops like flies in a pesticide cloud. Ah well, still fun, I'll try one of my other ones and see if they all have the same drain issues. Not much at all installed but what comes with the ROM, so not thinking that's the issue, though still need to dig further of course.

Thanks for your work, running smooth.
[Nexus 5 Original Android Development] candra yudha tama:
I try install last build successful but when I installed Gapps pico always error 70....can someone fix that...wipe all data /system/chace/ factory reset still error 70 Gapps [Gapps last version 20200131
[Nexus 5 Original Android Development] Somebod y:
Error Code 70: - Insufficient Space Available in System Partition: Your device does not have sufficient space available in the system partition to install the Open GApps package

Did you resize your partition? Check https://xdaforums.com/showpost.php?p=79928889&postcount=190
[Nexus 5 Original Android Development] candra yudha tama:
Ok...I will try it thanks :o
[Nexus 5 Original Android Development] jjsan:
does magisk work for you? not for me :(
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Works fine here, what exactly doesn't work?
[Nexus 5 Original Android Development] jjsan:
Device wont boot up. Just black screen
[Nexus 5 Original Android Development] candra yudha tama:
Is work for me thanks ??
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Strange, what was your installing process, which version of Magisk are you trying to install?
[Nexus 5 Original Android Development] candra yudha tama:
Are you used last version magisk ????
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Yes I'm using Magisk v20.3.
[Nexus 5 Original Android Development] timgoodwin:
Working for me, no problems. I flashed ROM, then GAPPS. I rebooted and then flashed Magisk. I'm using Google Pay and banking apps without any problems.
[Nexus 5 Original Android Development] candra yudha tama:
Anyone used pixel launcher this rom....??? And proximity sensor is not working to wake up feature rom...I used last version 20200205
[Nexus 5 Original Android Development] timgoodwin:
Rootless Pixel Launcher works very well for me. Playstore download. If you want left swipe Google features, you will also need to install Google Bridge apk, available here: https://github.com/amirzaidi/AIDLBridge/releases/tag/v3
[Nexus 5 Original Android Development] candra yudha tama:
I will try it ?
[Nexus 5 Original Android Development] dyabolikarl:
Hi there.

I installed the rom and i am getting a boot loop. The partition was resized by a previous rom. The ROM did install 100% was successful. Then Gapps pico installed OK. I rebooted and it just has the line ball animation then it reboots back to twrp after a few mins. I just tried a factory reset /cache reset and a reflash and same result.

What should i try? Undo the partition and start again? Reflash again? Thanks

After a 3rd reflash it booted to the the main screen.
[Nexus 5 Original Android Development] diggy128:
I have the exact same problem although on a POCO F1.

twrp 3.5.0_10 and all recent lineage builds for POCO F1 and all GApps builds >1/2021

After a failed update, I reflashed LineageOS 17.1 + GApps Pico + Magisk 21.4 on a POCO F1 and now I don't have access to play store (there was a problem communicating with google servers)

I tried: 1) Clear cache,data, 2) factory reset and reflash GApps, 3) Factory reset+system partition wipe+reflash LineageOS+reflash GApps (x3 with different versions) but still can't connect.

Tried to flash via TWRP 3.5.0_10 and lineageOS Recovery but not luck.

Tried with different lineage nightlys, different GApps versions, different Magisk versions, No Magisk at all...

I formatted cache, data, system, internal storage....

Tried using mobile data instead of wifi...

Now I'm trying to flash back Xiami Official ROM to see it it fixes things.

The irony here is that my old phone is a Nexus 5 that works fine with Lineage 15....
[Nexus 5 Original Android Development] lasser1:
Yesterday evening the LOS updater on my N5 popped up and said that there's an Update for LOS 17.1

But the download fails constantly. Internet connection is fine though. Hints?
[Nexus 5 Original Android Development] z3DD3r:
This was done by accident. Now this update should disappear.
[Nexus 5 Original Android Development] jenkinsad0:
Thank you, all 17.1 hammerhead developers for this excellent ROM. Ideal for my old "secondary" device. Version -20210209- works well, installed with the original partitioning using TWRP 3.5.0_9-HH.S.10 and _no_ GApps.
[Nexus 5 Original Android Development] bluetooth-bug:
I've been keeping an eye on the device, kernel and vendor tree and I saw some interesting GPS and GNSS HAL changes. GLONASS is supported now. This has been broken for ages. LineageOS 14.1 was definitely not working for sure. I think this was broken even on stock official firmware as well. Correct me if I am wrong, but I was never been able to get a lock on GLONASS satellites. The legacy LineageOS GNSS HAL and Samsung GPS patches definitely helped.

My question would be if BeiDou is also supported? I saw this patch LineageOS Gerrit: https://review.lineageos.org/c/LineageOS/android_hardware_lineage_interfaces/+/282269

Not sure which android_hardware_lineage_interfaces is built. The one on your GitHub or the LineageOS one. Technically Qualcomm WTR1605L what we have should have BeiDou support hammerhead should have that.

https://www.android-marine.fr/en/nexus-5-se-connecte-a-3-reseaux-gps/

https://xdaforums.com/t/no-galileo-beidou-fix-on-n9005-with-android-7-1.3719762/

Lovely screenshot attached. Haven't used navigation this year so it took quite a while to get a lock, but this should not be an issue. It was like this for a long time. It needs to warm up a little, but once it's going it should be fine.

Edit: Forgot to mention this is lineage-17.1-20210224-unofficial-hammerhead-signed.zip
[Nexus 5 Original Android Development] z3DD3r:
@bluetooth-bug

My fork contains all commits from LineageOS. But i'm using original android_hardware_lineage_interfaces for my builds ;)
[Nexus 5 Original Android Development] gallegonovato:
Good night: I have a nexus 5 with 17.1 lines and the update of December 31st. But if I go to the system, no update comes out. But in the we come two updates come out two of 2021. I do not understand why they do not come out? A hug
[Nexus 5 Original Android Development] z3DD3r:
Because these new builds are signed with different keys. These signed builds doesn't support OTA and can't be installed on top of previous build. Read my post 2 pages below.
[Nexus 5 Original Android Development] gallegonovato:
Good afternoon:

Thank you very much for your help and time.

Best regards
[Nexus 5 Original Android Development] Decuser:
I'm a new xda member and I just flashed twrp, lineageos17.1, and open gapps 10. It all went smoothly, I wasn't sure I totally understood what the twrp install was doing though. Prior to doing all this, I had the latest update to Android 6 factory - hammerhead-m4b30z-factory-625c027b installed. Did the twrp thing delete that and then install or just install 17.1 over it? I guess what I really want to know is - are there old files laying around taking up space other than the two zip files in the internal storage that I installed?
[Nexus 5 Original Android Development] gallegonovato:
Good afternoon @z3DD3r

A question that came up for me.

If I would like to put the new lineageos updates. But I have already root echo and put trwp. With the December version of lineageos. Downloaded by ota.

How could I do? I mean how could I put the new version having the old one.

I do not know if from trwp could delete the contents of the Nexus 5 and then load the new version.

Sorry for the inconvenience caused and be so uneducated on this subject.

Best regards
[Nexus 5 Original Android Development] Shred00:
Should https://sourceforge.net/projects/hammerhead-lineageos/files/lineage-17.1-ota.json/download still have the lineage-17.1-20201231-UNOFFICIAL-hammerhead.zip entry in it or should it have one of the more recent uploads to https://sourceforge.net/p/hammerhead-lineageos/activity/?page=0&limit=100#606b59be96442efc9acca37b in it?
[Nexus 5 Original Android Development] z3DD3r:
Previous builds of LOS 17.1 were signed with test-keys. New builds are signed with private-keys and can't be installed via OTA updater. Thats why ota.json will have links for old builds because. If you want install new builds, then u should do it from scratch.
[Nexus 5 Original Android Development] Shred00:
Oh. That's a real pity. It was really nice being able to update easily with an OTA updater. It was a nice no-noise means of keeping on top of updates. Having to subscribe to a thread as chatty as this just to know when there is an update that then needs to be manually downloaded and manually flashed is just so much less convenient. :(
[Nexus 5 Original Android Development] z3DD3r:
Well, i've stopped LOS 17.1 support some months ago. These new builds are exceptions and were made cos i've found some useful things while worked on LOS 18.1. Nothing new will be added. So i see no reason to add OTA updater support for signed builds...
[Nexus 5 Original Android Development] RosarleathSunny:
how can i enable call recording with this rom?
[Nexus 5 Original Android Development] z3DD3r:
Call recording is not available in this rom because it doesn't work properly. U should use 3rd party apps to record calls...
[Nexus 5 Original Android Development] Shred00:
Just updated to the latest (i.e. the June) build and it's boot-looping between the lineageos splash screen and recovery. :-(

Wrong thread. Didn't see a way to delete a post though.
[Nexus 5 Original Android Development] Ichir0:
Thanks for uploading the last build LOS17.1-0615.

Thank you for your great work and dedication so far @z3DD3r
[Nexus 5 Original Android Development] Xinhdepdiudang:
Hi @z3DD3r ,​

I see so many rom versions and don't know which is the most stable.

Can you suggest one?
[Nexus 5 Original Android Development] z3DD3r:
The latest one from signed folder.

Direct link: LineageOS 17.1
[Nexus 5 Original Android Development] SovietGP:
Anyone else still getting issue with system partition being full and problem writing anything onto it ?
[Nexus 5 Original Android Development] SirRGB:
You can repartition using twrp hh.
[Nexus 5 Original Android Development] SovietGP:
Yea,I looked back further o the treads ad found he HH TWRP, very useful.
[Nexus 5 Original Android Development] apelly:
del
[Nexus 5 Original Android Development] AlexanderDG83:
Updated to this rom from the unofficial lineageos 16: everything works fine! 👍
[Nexus 5 Original Android Development] rajakegelapan:
I read this message, download this version, try to install with twrp-3.5.2_9-HH.R.13.img and beautifully success without problems. Many thanks.
[Nexus 5 Original Android Development] z3DD3r:
New build is out (lineage-17.1-20210917-UNOFFICIAL-hammerhead-signed.zip)

Short change log:

September security patch

Some fixes for device overlays

Fixed connection to Wi-Fi with enabled (not enforced) PMF

Added fast charge in battery settings as in LineageOS 18.1

Charging currents are reduced to stock values as on android 6.0.1

Tweaks for CPU governor and I/O scheduler

Added 5th row with numbers in keyboard

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

Maybe something else that i've forgot to mention)
[Nexus 5 Original Android Development] gallegonovato:
good afternoon @ z3DD3r

the new update for Nexus 5 and Lineageos 17.1: https://sourceforge.net/projects/ha...615-UNOFFICIAL-hammerhead-signed.zip/download Can it be downloaded from the option to update on the phone having installed lineageos 17.1?

because I have tried and it does not come out. The last one I have installed is 17.1-20201231-UNOFFICIAL-hammer head. that is:

20210917-223428 hosted at ImgBB

Image 20210917-223428 hosted in ImgBB

ibb.co

20210917-222950 hosted at ImgBB

Image 20210917-222950 hosted in ImgBB

ibb.co

I don't know if I can download the 2021 version and install it on top of the other one?

A hug
[Nexus 5 Original Android Development] z3DD3r:
Hey

I’ve explained it earlier in this thread. This new build is signed with different keys (release keys) thats why u didn’t see this update in updater app. Simply you can’t install/update builds signed with different keys. U can try to use an instruction from this post which should work for LOS 17.1 as well:

https://xdaforums.com/t/rom-unoffic...hammerhead-discontinued.4214367/post-84271085

If it will not work then only way is clean flash.

PS: Link you have posted is not the link for latest build. Just open link from the first post in this thread and go to “signed” folder ;)
[Nexus 5 Original Android Development] gallegonovato:
Good afternoon @z3DD3r

Thanks a million for your explanation and help.

Best regards
[Nexus 5 Original Android Development] z3DD3r:
Build build (20211101) with October security patch is out!

Build 20211101 was removed cos of abnormal battery drain! New build will be uploaded in 24 hours!
[Nexus 5 Original Android Development] z3DD3r:
Build build (20211102) with October security patch is out!

Clean flash is recommended! If you u can’t do a clean flash then boot into TWRP, uninstall magisk using the uninstaller.zip, mount /data partition, remove /data/misc/radio/qcril.db file, install new update, wipe cache + dalvik/art cache and boot into system. After that u can reinstall magisk again.
[Nexus 5 Original Android Development] Bouquins:
Thank you very much for the amount of work, z3DD3r !
[Nexus 5 Original Android Development] z3DD3r:
New build (20211111) with November security patch is out!
[Nexus 5 Original Android Development] AlphaCentaurus:
Hello! I just installed on my old Nexus 5 the last version of LineageOS 17.1. It''s ok but the proximity sensor not working. When I call number and put the phone to my head the screen stay active and not turning off. Previosly I was with Resurrection Remix (Android 8.1) and the phone working fine. Thank you for your time!
[Nexus 5 Original Android Development] z3DD3r:
Remove /persist/sensors folder and reboot your phone
[Nexus 5 Original Android Development] AlphaCentaurus:
Thank you for you fast answer. After removing the folder with Root Explorer and rebooting the sensor working again as expected. Thank you for your great job making our old phones still work!
[Nexus 5 Original Android Development] Me,You,and Daigorou:
Thank you for updating...!!
[Nexus 5 Original Android Development] Bouquins:
Thank you very much for updating !
[Nexus 5 Original Android Development] heisenberge89:
hi, I have a problem, I can install roms and gapps without problems but when it tries to check for updates, despite being connected to wifi, it fails to get them and gives an error. I also tried with hotspot from another phone and I also tried to insert a sim from which, however, the 4g network does not go. is it a problem with my phone? is there something I need to set up from recovery? the problem also occurs with other rom
[Nexus 5 Original Android Development] Redshadow.om:
Hi guys

what is this error when i install rom?