yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] mathexa:
Hi! Thanks for your feedback. Unfortunately the application you indicated is not useful for my old Nexus 5, when I run it no sensors are detected :)

The previous custom rom that I used was this one "aosp_hammerhead-9-20181003.CAF.zip" and I had no issues with the proximity sensor. I decided to stay with this custom rom "aosp_hammerhead-9-20190417.CAF-edit.zip" because it seems to be very stable, except the issue with the proximity sensor. Maybe the developer [MENTION=4473900]amaces[/MENTION] will notice this issue. A temporary solution is to press the power button after I started the call, just to not keep on the display during the conversation :)
[Nexus 5 Original Android Development] Zachary_Foxx:
Well.... the ROM is fantastic, but unfortunately somethings doesn't work, like Face Unlock and I had some softreboots.

Because the Nougat version is very outdated, I am returning to Lineage 14.1.
[Nexus 5 Original Android Development] hamed_forum:
after flash this rom my bluetooth keeps stopping and wifi dont work the mac 02:00:00:00:00

what must do?i downgrade to andprid 6 but wifi bluetooth not work
[Nexus 5 Original Android Development] diviloria:
Tested to share wifi, ok

Tested to share wifi by bloutooh, ok

I was wrong
[Nexus 5 Original Android Development] Zachary_Foxx:
Ahnnn.... What?
[Nexus 5 Original Android Development] teothecool:
For those that have the "Bluetooth stopped working" issue, your BT address was probably erased from the /persist partition at some point. Check out this guide, it helped me restore BT functionality: https://xdaforums.com/showpost.php?p=52441901&postcount=47.
[Nexus 5 Original Android Development] eupalino:
OMG !!!

I've been plagued with this error since October 2018, and I thought Amaces had forgotten something. He had not!

My apologies to Amaces for thinking so, but I didn't know this simple fix existed.

Everybody who has this issue, please bookmark the post above.

The pictures are gone, but by checking the various passages, you'll get all the steps right. It really is a piece of cake.

A big thank you to Teothecool for bringing it up!

M.
[Nexus 5 Original Android Development] matusala:
I installed newest 9.0 CAF ROM at fresh boot i turned of NFC in pulldown menu. Now NFC option is gone from that pulldown menu. I can't add it it's just not there. I still can turn on and off NFC from settings menu.
[Nexus 5 Original Android Development] mads339:
Is this also applicable to the new 04/17/2019 or has the issue been fixed?
[Nexus 5 Original Android Development] mandayugana:
Installed UA-CAF 9 with stock gapps. No random reboot. Could random reboot be caused by apps in the ROM which gets replaced by apps from stock gapps?
[Nexus 5 Original Android Development] chmbrnl:
I've always wanted to ask what's up with the stock internet browser? It works like the first two times after flashing and crashes from there on out till kingdom come. How to fix that
[Nexus 5 Original Android Development] Mark_8:
I also noticed this; not only with browser but all the stock apps generally. They are the "stock android aosp " ones, but i noticed that some are too much stock :) and maybe incompatible at some point with google account and the build also.

Infact the clock app (alarm) on oreo doesnt work, email and calendar apps dont sincronyse well and browser lacks common features
[Nexus 5 Original Android Development] riza.pasha:
why all UA now get random restart especially when load much
[Nexus 5 Original Android Development] mandayugana:
In my experience, UA-CAF with stock gapps was more stable than UA-CAF with pico/nano gapps. May be, some apps in the ROM trigger the random reboot.
[Nexus 5 Original Android Development] Rabittek:
Just a feedback for 0417 build of the CAF 9. with OpenGapps Pico. Pixel Launcher used - all original apps disabled and Google ones installed as pointed on the first page of this topic. As far all works fine for last week with no reboots or any other malfunctions. I use it as the main and only phone. The only untested is the BT sound. Battery is even slightly better then with previous 7.1 Pure Nexus I had used. Only a bit odd behavior is for automatic brightness set up as it sometimes does not remember the last set value - goes too bright, but it can be Pie native behaviour. I also had a problem with autorotation not working, deleting the content (3files) of the /persist/sensors using TWRP files browser direcly solved the issue. Dark mode is the last "issue" as it gets it from backround image, not forced. So, at the end thank you all who are behind UA project so much for keepeng the N5 alive! You made amazing job and I do not see the reason why 9. builds are still marked as Beta! They works fine. At least the CAF one.
[Nexus 5 Original Android Development] mandayugana:
Are you able to send videos (especially long videos) in Whatsapp in UA-CAF Pie?
[Nexus 5 Original Android Development] lulli1:
Yes, I am.... Tested it right now. Video was 40 sec. Long.

But my microphone is a bit lame. Sometimes works, and sometimes not. No calls, no WhatsApp calls not Telegramm calls. Just some noise to hear but no clear tone. Does someone experience the same? Any workarounds? I'm on pie caf.
[Nexus 5 Original Android Development] mandayugana:
Wow. You are right. I just back to UA-CAF, Whatsapp video is working fine. I tried several ROMs (O and P) and all of them have issue sending video in Whatsapp.

I don't know if this has correlation, when I install Whatsapp on UA-CAF, my name is already there after restoring messages, unlike on another ROMs.

So far I never had microphone issue.
[Nexus 5 Original Android Development] aqua22:
Thanks for this beautiful ROM. I migrated from LOS14.1. I did

1.5GB /system, aosp_hammerhead-9-20190417.CAF.zip and open_gapps-arm-9.0-micro-20190504.zip, then

enabled immerse mode for navigation bar from adb settings. Tel/Wifi OK, Connecting to bluetooth/OBDII ok. The only thing I had is that pixel launcher kept crashing. So I will stay with the default launcher and this ROM. Cheers.

Update: deleting the 3 files mentioned here (using adb shell) solved the auto-rotation problem:

https://xdaforums.com/showpost.php?p=79455435&postcount=3504

Thanks Rabittek!
[Nexus 5 Original Android Development] mandayugana:
For those who want to safely replace AOSP Dialer with Google Dialer, flash this zip file. It will remove AOSP Dialer and install overlays to make emergency call working with Google Dialer.
[Nexus 5 Original Android Development] mandayugana:
[MENTION=4473900]amaces[/MENTION], I provide attachments showing notification buttons container space is too wide that the buttons hit the end of notification. It is better on density 420.

The other image showing that there are useless options on USB preferences.
[Nexus 5 Original Android Development] chmbrnl:
Can you do for messages and contacts too? :laugh:
[Nexus 5 Original Android Development] Rabittek:
Another observation - the BT setting for connection to the BT Parrot handsfree. The popup window for password key entry just blinks on my Nexus 5 and the Parrot says wrong key entered. There is no time to enter the 1234 key in thios popup. It works fine for connection where the key is set by other site. All on 9. CAF with Pixel launcher.
[Nexus 5 Original Android Development] mandayugana:
I don't see the point of making overlay for Google Contacts and Google Messaging.

OpenGapps (stock) doesn't delete AOSP Dialer for compatibility reason. Thus, it left our phone two dialer apps: AOSP Dialer and Google Dialer. Disabling/deleting AOSP Dialer on some ROMs breaks UI on emergency call. This can be a matter of life and death for some people. But, having two dialer apps is quite annoying. So I created the overlays for those who want to completely replace AOSP Dialer with Google Dialer.

The zip should be flashed on ROMs with stock gapps (Google Dialer installed in as system app). If Google Dialer installed as user app, don't flash the zip as it could make errors after a factory reset.
[Nexus 5 Original Android Development] chmbrnl:
Really wanted for those two
[Nexus 5 Original Android Development] Jacq1212:
Here a proud user of Nexus 5 on unlegacy rom.

I will probably move to newer pixel 3a (or 3a xl still undecided any thoughts?) soon.

I just want to thank [MENTION=4473900]amaces[/MENTION] team for this great rom, their great work and essentially to bring this 2013 device up to nearly the 2020 age!

Nexus 5 was really a memorable device, it is difficult nowadays to find such a great release for an Android device giving this much for soo few, still loving it's design.

Cheers,
[Nexus 5 Original Android Development] ksteczk:
Sounds & notifications

I got the problem with sounds in my device since the first release of Unlegacy ver.9, a problem which is still present:

Notifications sound level is always quite high - it doesn't react when I turn ring volume at its minimum. Moreover, when I put some custom notification's sounds files in appropriate folders using a computer, they weren't listed as sounds to be used in the phone itself. Also, the sound service (can't remember the exact name for now) crashes regularly. Where the problem might be?

I migrated from Lineage14.1. The device is Nexus 5. Open GAPPS pico. Before each Unlegacy Pie installation, I go through all possible TWRP wipes and formats.
[Nexus 5 Original Android Development] Rohit7011:
good rom. better than others. tried aosip pie, was unstable and laggy n ate more battery n my phone was always warm with that rom. gonna try this now.
[Nexus 5 Original Android Development] xyz_969:
Is it possible to get Face Unlock working on the latest 8.1 ROM? I have GApps nano, the system app is installed and running, but the option is not visible in the Smart Lock menu.
[Nexus 5 Original Android Development] Sashko98:
[MENTION=4380992]lulli1[/MENTION] if you still use this ROM would you try to flash the boot image and checkout the output from handsfree device link.

Haven't tested the boot image at all , so if there is any issue feel free to PM me.

Edit: Added CAF image just in case
[Nexus 5 Original Android Development] mertzi:
If someone wonders, dirty flash of aosp_hammerhead-9-20190417.CAF over aosp_hammerhead-9-20190115.CAF seems to work fine. I only had to add debug.hwui.renderer=opengl in build.prop again (maybe it's not necessary anymore?) and of course re-flash gapps and Magisk but that's expected. Awesome work with this ROM!
[Nexus 5 Original Android Development] thang_legend:
i can't access https://builds.unlegacy-android.org/ :( what happened to the web page?
[Nexus 5 Original Android Development] lulli1:
Downloading....

You mean amaces`s UA "aosp_hammerhead-9-20190417" Rom as a base, correct?

[MENTION=4473900]amaces[/MENTION] what are those files? Did you test BT voice calls as well?
[Nexus 5 Original Android Development] thang_legend:
with caf 8.1.0, sensors don't work
[Nexus 5 Original Android Development] lelik67:
I can't access unlegacy-android.org either.:confused:
[Nexus 5 Original Android Development] Android-Andi:
Power source dead. Takes some days to be replaced.
[Nexus 5 Original Android Development] riza.pasha:
Suffering random reboot when Nexus got high load.

How to resolve it??

---------- Post added at 04:30 PM ---------- Previous post was at 04:30 PM ----------

Wow why they forget to maintain it??
[Nexus 5 Original Android Development] lulli1:
[MENTION=7412373]Sashko98[/MENTION] flashed the non caf version and your boot IMG afterwards and tested in my car without gapps and without magisk, naked ROM and kernel. And sorry the distortion is still there. But thanks a lot for not giving up trying to fix this bug. You will get that bastard ... I'm sure :D

If you think I should try it with the caf version as well, let me know. Will do that if there is a chance to get a better result.
[Nexus 5 Original Android Development] M Asad Khilji:
[MENTION=7412373]Sashko98[/MENTION] Keep it up Bro. You can do it and become a Legend in History Books of Nexus 5 :D
[Nexus 5 Original Android Development] mandayugana:
Not working on 20190417 CAF Pie. Phone call is still distorted.
[Nexus 5 Original Android Development] creeve4:
Anyone have a mirror?
[Nexus 5 Original Android Development] xrad:
Yes, they seem to be broken with the 20190417 build. I updated from 20181002 in which they still worked. Any chance this will be fixed?

Edit:

To clarify: I'm talking about the CAF builds here.

"broken" meaning there is absolutely no sensor to be found. The logcat contains a number of message like this:

06-10 15:39:43.712 5916 5936 E Sensors : sns_debug_main.c(436):Debug Config File missing in EFS!
06-10 15:39:43.724 5916 5916 E Sensors : sns_init_la.c(239):Error 5 initializing sns_file_init
06-10 15:39:43.724 5916 5916 E Sensors : sns_main.c(1692):Exiting! sensor1_init failed with 5

Let me know if you need more information.

Edit 2: I'm seem to be a bit trigger happy today, and only now realized that [MENTION=6674134]thang_legend[/MENTION] referred to the 8.1 builds, while I refer to 9.0 builds. They may even suffer from the same (CAF?) regression, but it was definitely confusing to reply that way. Sorry for that.

Edit 3: Solution: I really haven't been following this thread too closely. Turns out this is a known issue, all that's needed is to delete the /persist/sensors folder. I did that from TWRP.

[MENTION=6674134]thang_legend[/MENTION]: I guess this should fix it for 8.1 as well.
[Nexus 5 Original Android Development] riccardo9101:
Hi! I've just tried to flash new 8.1 caf rom, but I still have Error 7. I've flashed TWRP CAF, so how can I solve this problem?

Thanks!
[Nexus 5 Original Android Development] gxfuzion92:
https://xdaforums.com/showthread.php?t=2522762
[Nexus 5 Original Android Development] creeve4:
Can someone please share the latest non-caf version? The server is still down.
[Nexus 5 Original Android Development] Android-Andi:
Still takes some days. Replacement parts got shipped yesterday, now it needs to arrive.
[Nexus 5 Original Android Development] MrMundy:
Why did the dev build a oreo version dated june instead of a pie version?
[Nexus 5 Original Android Development] xrad:
Details on the builds are found in the original and the third post.
[Nexus 5 Original Android Development] riza.pasha:
How to Upgrade from UA 8.1 to UA 9.0 without loosing the apps without backing up, just like major update
[Nexus 5 Original Android Development] GopalKaul:
Use migrate app
[Nexus 5 Original Android Development] riza.pasha:
why not make it update automatically like the Google did to All their device?
[Nexus 5 Original Android Development] Android-Andi:
Source is open. Everyone can help making it better. ;)
[Nexus 5 Original Android Development] GopalKaul:
Because there are major change in sources.. you can try but don't blame me for App FCs
[Nexus 5 Original Android Development] Tornado15550:
I upgraded from 8.1 to 9.0 without formatting /data. Everything worked fine for me. Just erase /system, /cache and then flash UA 9.0 with whatever add-ons such as gapps etc. Then boot. As long as the packages are present on 9.0 things should be fine. For example, if you're using pico gapps on 8.1, use pico gapps on 9.0 before booting back into the OS.
[Nexus 5 Original Android Development] canpolat28:
hi guys, should i move to new caf oreo build ?
[Nexus 5 Original Android Development] riza.pasha:
what about flashing from 8.1 non CAF to 9.0 CAF

and is there any possibility that Hammerhead support Fuchsia OS ?
[Nexus 5 Original Android Development] Tornado15550:
Use 9.0 CAF Pie.

It should still work. I don't see any reason why it wouldn't. I would suggest to backup your data just in case things go wrong.
[Nexus 5 Original Android Development] riza.pasha:
Upgrading from 8.1 to 9.0 is easy and even no problem, there is no more random reboot anymore

And the problem is changing build.prop from test-keys to release-keys

Please in the next update change it, because it detected as root device
[Nexus 5 Original Android Development] Sytis:
I like the minimalistic and stable feeling this ROM gives. But just a question, as you said most of the builds are made by a buildbot: Is 7.1.2 unmaintained and not receiving any security related updates anymore? I'm asking because I would need to build myself a custom kernel for a few features on 8.1 or 9 myself, and whilst building and patching those for regular Linux machines is easy, I haven't managed to do it for Android yet.
[Nexus 5 Original Android Development] Android-Andi:
I'll care about 7.1 ASB patches if I find time. Private life crazy atm...

Kernel stuff is up to device maintainer.

Builds are compiled by Jenkins, but we only trigger new builds if important stuff changes (e.g. security updates) - It's only half-automated ;)
[Nexus 5 Original Android Development] Sytis:
Alright, thanks for the heads-up. Take your time then :)
[Nexus 5 Original Android Development] mandayugana:
Oreo CAF is amazing. It seems more stable than Pie CAF. As a workaround for BT-call I use libbt-vendor.so from LOS16. Everything is working.

I just want to share my setup to make this ROM close to stock.

1. Repartition system to 1674MB (cache partition shrinked to 50MB)

2. Flash the ROM (CAF version of Oreo or Pie)

3. Flash Gapps (stock version)

4. Remove /system/priv-app/Eleven from TWRP. Gapps provides Google Music as a replacement.

5. Install overlays (flash GappsGooglePhone.zip) to completely replace AOSP Dialer with Google Dialer. Just ignore the error in TWRP.

6. Copy libbt-vendor.so from LOS 16 as a workaround for BT-call, chmod it to "644", and chcon it to "u:object_r:vendor_file:s0"

7. Replace Google Camera with Google Camera Legacy

8. Replace Google Photos with version 4.11

9. Reboot
[Nexus 5 Original Android Development] Tornado15550:
Can you post the libbt-vendor.so from LOS16 please? :)
[Nexus 5 Original Android Development] canpolat28:
Hi guys wifi suddenly gone. sometimes coming after reboot but going again later. help me please
[Nexus 5 Original Android Development] Tornado15550:
Are you using DFS channels in your 5Ghz frequency? Set the 5ghz channel manually on your router and see if you can connect to it again. The Nexus 5 does not support DFS channels.
[Nexus 5 Original Android Development] canpolat28:
not this. wifi button not responding. mac address 02:00:00:00:00:00
[Nexus 5 Original Android Development] lulli1:
Sorry but it seems like your WiFi hardware is broken. Same on my side with one of my n5's. Flash back stock ROM and try if it works. If not, you know why.
[Nexus 5 Original Android Development] canpolat28:
my legend fully dead no longer. shutdown suddenly no any response power button and charge :(
[Nexus 5 Original Android Development] vaibhavnegi:
Hi 8.1 vs 9.0 which has less bugs? Or they almost same now?
[Nexus 5 Original Android Development] Tornado15550:
9.0 Pie.
[Nexus 5 Original Android Development] Buiatti:
I have installed it yesterday, but I'm not being able to get the superuser access to work.

I first tried Magisk, but I get an error message while trying to flash the ZIP file that it downloads.

Then, I tried using SuperSU links available in the second message from this thread, but they bricked my phone, so I restarted the process.

After the phone was up and running properly, I tried KingRoot, also, with no success (the app crashes every time I try to use it).

How can I have the SuperSU access with this build on version 8.1?
[Nexus 5 Original Android Development] riza.pasha:
Why still detected as rooted device when open banking apps, even i already change build.prop from test-keys into release-keys
[Nexus 5 Original Android Development] riza.pasha:
9.0 nonCAF is better

install 8.1 first then update to 9.0, it will be perfect no more random booting
[Nexus 5 Original Android Development] riza.pasha:
I don't do that i flashed from 8.1 to 9.0 , now i am facing random camera cannot connect should be restarted.

But fortunately i don't have random reboot like in 8.1
[Nexus 5 Original Android Development] Smart-X:
I've used FirstEver ROM 9.0 for months. Everything's good, but the dev stopped updating 'cause the birth of his first baby. Yesterday I tried the latest version of UA and LOS and I faced the same problem: popup message never stopped telling me "bluetooth stopped working", even when BT is disabled. When I enter settings, I found BT address unavailable. However the file ".bdaddr" exists in the folder "/persist/bluetooth", and the same file works fine on FirstEver ROM which is based on UA ROM. How can this happen? Is there anything I missed?
[Nexus 5 Original Android Development] lister86:
Are the permissions right? It should look like below, if not you can change it by running the following commands.

chown bluetooth:system .bdaddr

chmod 660 .bdaddr
[Nexus 5 Original Android Development] Smart-X:
Yes, the permissions are right. I've checked the post: https://xdaforums.com/showpost.php?p=52441901&postcount=47. Everything seems right, and in FirstEver ROM the same file works fine. I just don't understand why.
[Nexus 5 Original Android Development] Tornado15550:
This "FirstEver" guy is not a dev. He stole UnlegacyAndroid builds and tossed in free apps and tools such as Magisk that you can install yourself, and called it "his rom" all the while plastering donate buttons all over his website. He was banned from XDA for this behaviour but kept making new accounts to promote that stolen ROM. I'd recommend not supporting such people who have such blatant disregard for other people's hard work.
[Nexus 5 Original Android Development] Smart-X:
Well you're right. I didn't know that before. Anyway, I'm using another ROM now. Just wanna solve this BT issue.
[Nexus 5 Original Android Development] srepole:
Caf Pie project sounds abandoned.It's a pity,for me great rom.Any chance to have an update?
[Nexus 5 Original Android Development] Mark_8:
Does this ROM will receive new builds (at least with August security patch)?:good:
[Nexus 5 Original Android Development] riza.pasha:
Yeah First Ever Guy is better in solving the problem of Bluetooth Audio Grabbled, why this Devs not interested to solve this basic thing?
[Nexus 5 Original Android Development] Syaani:
Isn't that bluetooth issue solved already? https://review.lineageos.org/c/LineageOS/android_hardware_broadcom_libbt/+/250445
[Nexus 5 Original Android Development] Android-Andi:
Some user from time to time forget that some things aren't because one ist "Not interested", it's more like "it's an hobby".... and even devs have a private life and sometimes a full time job to pay bills.
[Nexus 5 Original Android Development] riza.pasha:
How to fix in Pie, AOSP?

Is there any? Bluetooth Audio Call still terrible
[Nexus 5 Original Android Development] Mark_8:
guys be patient, because the strike of this rom is to guarantee an experience clean as possible as the original one from google sdk package (like pixel phones..)
[Nexus 5 Original Android Development] Tornado15550:
Only thing "FirstEver" is good at is stealing other devs work. He hasn't solved a single thing. The only thing he knows how to do is copy and paste and call it his own. Let's end this OT discussion here.
[Nexus 5 Original Android Development] Poor Grammar:
This person riza.pasha is a Troll anyway... Always disrespecting people work...
[Nexus 5 Original Android Development] riza.pasha:
Don't you want the Bluetooth Grabbled Audio Solved? I have solution, because Music is not grabbling could you route Audio into Stereo?

And why after flashing from Oreo into Pie, Google Lens Not Working
[Nexus 5 Original Android Development] Vegeta IV:
Volume button wakeup is kernel or rom feature?
[Nexus 5 Original Android Development] ze7zez:
Thank you [MENTION=4473900]amaces[/MENTION] for your long support and today's ROM. :good: