yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Slmnj:
Hello [MENTION=4473900]amaces[/MENTION], glad you're here.

I CLEAN flashed the latest NON CAF build. No prob with Calls, Wifi, Cam etc.. but sensors are not working. I have attached Dmesg and Logcat in a single zip. Hope you can provide us a solution soon. Thx.
[Nexus 5 Original Android Development] dracul89:
Nope hotspot doesn't working

Notification light works only with charging and low battery
[Nexus 5 Original Android Development] keretapanau:
Same here...already try clean flash android 8.1 then clean flash latest android 9.0-caf....all sensor not working....
[Nexus 5 Original Android Development] naxomatrix:
I did the same and everything works again but Digital Wellbeing does not appear now in configuration despite having it installed.
[Nexus 5 Original Android Development] keretapanau:
I clean flash revert back to 20181028-caf, all sensor working now. But if i clean flash or dirty flash latest build 20181208-caf from previous build, all sensor not working again.
[Nexus 5 Original Android Development] culespace:
Can you tell me changelog for latest build 20181208 ?
[Nexus 5 Original Android Development] wbedard:
[MENTION=4473900]amaces[/MENTION],

Per your request, I am providing links for the dmesg and logcat output of my device:

dmesg (Pastebin)

logcat_system (Pastebin)

logcat_radio (Pastbin)

logcat_main (Pastebin) [<--here be some sensor-related errors...]

logcat_events (Pastebin)

Additionally, I have included the relevant output from my bootloader for your reference:

VARIANT - hammerhead D820(H) 32GB

HW VERSION - rev_11

BOOTLOADER_VERSION - HHZ20h

BASEBAND VERSION - M8974A-2.0.50.2.30

Let me know if there's anything more I can provide you in support of troubleshooting the issue with sensors in the newer builds. Thanks again for all your continuing support for our device. It is most appreciated!

R/

wbedard
[Nexus 5 Original Android Development] amaces:
The two 20181208 builds were refreshed with Permissive boot images. Before investigating the logs I received, let's check if it's a sepolicy issue, or something more insidious.

Thanks for all the included info. I have the same rev_11 hardware (albeit with the 16GB eMMC). Is your bootloader at HHZ20h?
[Nexus 5 Original Android Development] wbedard:
Sorry for that typo/omission while reading off my bootloader screen. Yes it is and I've corrected the original post for posterity.

R/

wbedard
[Nexus 5 Original Android Development] wbedard:
[MENTION=4473900]amaces[/MENTION],

I just dirty-flashed the new CAF build with the permissive kernel. I appear to have the same sensor results previously posted and I noted (a quick glance...) the same errors in the logcat (main section) related to sensors. Let me know if you would like me to go ahead with posting new dmesg/logcat output.

R/

wbedard
[Nexus 5 Original Android Development] s4ni:
yup, Same on clean flash too.......
[Nexus 5 Original Android Development] bagajohny:
Its nice to see such active community for device this old. I'd like to thank all the members and devs for their contributions. #LegendsNeverDie
[Nexus 5 Original Android Development] M Asad Khilji:
Hope not out

#Nexus5
[Nexus 5 Original Android Development] kamild_:
It's not as active as it used to be though, seems like many devs have moved on to other devices, which is a shame - Nexus 5 might not be as snappy as it used to be for some reason, but it's still a very usable device. amaces seems to be the only active dev left, no news about LineageOS, Dirty Unicorns dropped support for our device...

Which is why I'd also really like to thank amaces for sticking with us for a little bit longer :good:
[Nexus 5 Original Android Development] amaces:
Do you have ADB shell? Normally, you'd obtain the logs with logcat -d -v color (e.g., adb logcat -d -v color > hammerhead.logcat.pie.caf), and dmesg (e.g., adb shell dmesg > hammerhead.aosp.pie.caf). Can you can regenerate them (on the Permissive builds, ideally)? The separate logs you sent are a bit confusing.

Also, what happens on the equivalent AOSP builds (which can still be dirty flashed)? You can include logs from there as well.
[Nexus 5 Original Android Development] GopalKaul:
razorloves is still on probably.. not sure..
[Nexus 5 Original Android Development] Slmnj:
I have attached logs of AOSP build here: https://xdaforums.com/google-nexus-...nlegacy-android-project-t3593425/post78380140

The two logs are a bit lengthy because the sensor services are continuously trying to start but failing....
[Nexus 5 Original Android Development] bagajohny:
Well, its been more than 5 years so we can't really complaint. "A part of the journey is the End".
[Nexus 5 Original Android Development] amaces:
Thanks. Are you installing anything beyond ROM and GApps? Have you modified your partitions somehow? I'm seeing errors and SELinux denials that shouldn't happen on a regular setup. Something very wrong is happening with your /persist. Anyway, there must be an explanation, and once we have that, a fix.
[Nexus 5 Original Android Development] Mgallo:
the last rom marshmallow has an error that does not let me go through the first configuration screen.
[Nexus 5 Original Android Development] kamild_:
True, and yet, when most have abandoned ship, there's still someone left just to show us the journey doesn't have to end here ;)
[Nexus 5 Original Android Development] wbedard:
[MENTION=4473900]amaces[/MENTION],

Sorry for the confusing output. As a matter of fact, I seem to be unable to establish an adb shell btwn my computer and my Nexus 5, even though I have no trouble with the same computer and my other Android devices. Short of pulling a real-time logcat while the device is booting, I was able to dump the requested output from an on-device terminal after bootup...I hope it included everything early enough in the boot process to be helpful. You can find the output from the SELinux Permissive builds at the links below:

dmesg_permissive.txt (Pastebin)

logcat_permissive.txt (Pastebin)

R/

wbedard
[Nexus 5 Original Android Development] Slmnj:
I flashed ROM, then reboot and flashed Magisk. Didn't even flash gapps. I didn't do any other flashing or partition modifications. I'm eager to help so please let me know if you need anything else.
[Nexus 5 Original Android Development] Zaheen Jamil:
I am on 10/28 build with pico gapps + partial gapps( which inculde overlay.zip) + Magisk and I'm using lawnchair with lawnstep Magisk module. I also did change my buildprop. For some reason... Sometimes the pie gestures appear...sometimes it becomes regular navbar. Usually a reboot fixed it but now I'm stuck with the regular navbar. Also the gesture option never actually showed in my settings... When I changed my buildprop... It was enabled by default. Also my them didn't change. My Bluetooth also frequently disconnects and says "Bluetooth has stopped working", and then it fixes itself.

P.S. : A sidenote but, I noticed that I could only change my boot animation via magisk modules. If I flashed in TWRP or manually replaced it... It would either haven't boot animation( just display logo) or have default.)

EDIT : Going into lawnchair settings instantly fixes navbar... Without changing any setting. But still... I don't understand why sometimes it disappears.
[Nexus 5 Original Android Development] amaces:
Thanks, those should help in case sepolicies need more fixes.

This was a weird issue, but I think I have an explanation. It's about the regeneration of /persist/sensors/sns.reg. It seems that sensors.qcom was still looking for sensor_def_hh.conf in /etc (rather than /vendor/etc, where config files were recently moved). I never hit this bug since my sns.reg was never changed from before the /vendor transition, but people who triggered its regeneration would get a generic sns.reg, not tailored for hammerhead. That's why a clean flash coming from previous Oreo builds fixes sensors; it's simply reusing the good sns.reg in /persist (when sensors.qcom likes what it finds in there, otherwise it tries to update it).

The problem now is that, although I have enough room to edit the paths in the blob, it's coded in such a way that only 5 chars get copied in the final path where it looks for sensor_def_*.conf files. I could created another symlink, say /etv, pointing to /vendor/etc, but that means a hacky workaround inside our bootimage. I'd rather avoid that, and since we're not going back to polluting regular /system/etc, I'm still weighting options.

In the meantime, I suggest that everyone who has been having sensor issues since Pie grab a /persist/sensors/sns.reg from a working Oreo build, copy that to current Pie builds, then reboot. You can check that main sensors are working with something like AIDA64, or https://play.google.com/store/apps/details?id=ru.andr7e.sensortest. This is only temporary, and won't be needed once blobs are fixed.
[Nexus 5 Original Android Development] Slmnj:
Tried this on NON CAF build. Unsuccessful. Tried replacing sns.reg from 3 different ROMs (DU, RR, AOSiP). Maybe this method works for CAF but not for NON CAF. Anyone who can clarify?
[Nexus 5 Original Android Development] amaces:
Shouldn't matter as I'm using the same blobs in both series.

It should be the exact sns.reg that you get on my Oreo builds. Any mismatch, and sensors.qcom will clobber it, so yeah, a pretty fragile solution.

Anyway, I'm uploading new builds with an implementation of the symlink/hexedit solution. Please test sensors with something like https://play.google.com/store/apps/details?id=ru.andr7e.sensortest. I don't think you need to remove /persist/sensors/sns.reg, but try that as well in case no improvement.
[Nexus 5 Original Android Development] s4ni:
Clean Flash no Success

Dirty flash on 28/10 no Success......

both issues remain same.

EDIT: Hotspot Fixed

Sensors Still Broken
[Nexus 5 Original Android Development] amaces:
Are you able to remove /persist/sensors before rebooting?

Likely due to Permissive.
[Nexus 5 Original Android Development] s4ni:
Yup, tried (removed /persist/sensors) and rebooted, but no luck
[Nexus 5 Original Android Development] amaces:
What do you get with that sensor tester app? Also, I uploaded separate bootimages with slightly different ramdisks; please test those as well (e.g., fastboot boot) on top of the respective AOSP, or CAF builds.
[Nexus 5 Original Android Development] s4ni:
In Sensor testing app,

0, "No Input Data'

Info.: unsupported

And for Separate Boot image(flashed from twrp) ...

Lol...hotspot ****edup again with broken sensors....

I wonder, older boot IMG work (those from nogut or orio) or not, if yes(or for try) I need to download, as m not with my lapi right now.....
[Nexus 5 Original Android Development] keretapanau:
I try flashing file 20181211-caf, all sensor working now....but hotspot not working
[Nexus 5 Original Android Development] s4ni:
Which ROM u flashed before 11/12?
[Nexus 5 Original Android Development] Sashko98:
Just copy/move sensor_def_hh.conf from /vendor/etc/ to /system/etc/ and then wipe the sensors folder in /persist partition, if you want working sensors, until amaces upload build with a proper workaround.
[Nexus 5 Original Android Development] keretapanau:
20181028-caf
[Nexus 5 Original Android Development] Black_Voltagez:
Already flashing 20181211-CAF, then move sensor_def_hh.conf from /vendor/etc/ to /system/etc/ (forget to test sensor before doing that) , all sensor and hotspot working. thanks [MENTION=4473900]amaces[/MENTION] , really appreciate your efforts to build this nice rom for hammerhead ???
[Nexus 5 Original Android Development] Slmnj:
In case I'm not the only one using the latest NON CAF build, to make sensors work ONLY delete "sensors" folder in /persist. Don't do any other changes and don't forget to reboot. As [MENTION=4473900]amaces[/MENTION] mentioned, this is only temporary and probably will be fixed in future builds.
[Nexus 5 Original Android Development] MrMundy:
quick question, running the october caf build and no gapps installed, rooted. no problems with sensor, can i just dirty flash the latest december build?
[Nexus 5 Original Android Development] Huexxx:
In my case, CAF, I agree with $lmnj.

1st I tried to move sensor_def_hh.conf only, with no results.

2nd tried to remove /persist/sensors folder, with no results.

3rd and last, removed /persist/sensors folder and moved sensor_def_hh.conf back to original place... everything works fine!

Then, the solution is to remove /persist/sensors folder... if you make it just after flashing the new ROM you get it!
[Nexus 5 Original Android Development] Santosh B:
Guys i'm facing some serious issue with my nexus 5 i dont know what is happening my phone stuck on Google after I'm flashing stock factory image (latest Marshmallow OS) also tried latest Pie Unlegacy ROM but it gets reboot all the time not working properly....tried kitkat factory image still nothing happened ???

What to do? It Keeps rebooting all the time ??
[Nexus 5 Original Android Development] cink40:
Maybe power button problem? Usual problem on n5. Try to press power button realy fast for several times.

Sent from Outer Space
[Nexus 5 Original Android Development] Acocasb:
I'm sorry, but where can I find the persist folder that I need to remove?
[Nexus 5 Original Android Development] s4ni:
It is on ur root folder.(u need root explorer)

Remove only 'sensor' folder not whole "persist"

/persist/etc/sensor

FYI: none of the above fix worked for me, I m waiting for next build.
[Nexus 5 Original Android Development] JackyGundam:
i have flashing problem, when i am using the latest twrp to flash latest 11/12 CAF rom, it said comparing baseband version "……30" to "……29"

assert failed hammerhead baseband version "……30" ==1

anyone can help me? i am able to flash previous CAF pie rom before
[Nexus 5 Original Android Development] KevMetal:
*simple solution

_install mixplorer

_install mix atchiver addon

_open rom zip DON'T EXTRACT JUST BROWse

_search for the updater script with search function

or browse to META-INF>com>google>android

_open it as text file

_delete all the assert lines

*all the lines until "mount"

_save

_exit & reboot recovery

_flash zip

BE AWARE I'M NOT RESPONSIBLE FOR DAMAGE TO YOUR RADIO / BASEBAND / IMEI

BE AWARE IF YOUR BASEBAND VERSION IS incompatible you won't get signal ...
[Nexus 5 Original Android Development] wbedard:
Don't be afraid to search the forum. It's often the case that you're not the first to experience a particular problem.

https://xdaforums.com/showthread.php?p=78374838
[Nexus 5 Original Android Development] JekaPinsk:
Boot into recovery. When you get to the "no command" screen hold down the power button for 3-5 seconds and then press and release the Volume up button.

Then wipe data/cache and reboot.
[Nexus 5 Original Android Development] cocogendut:
Finally,sensor working on UAP 1112 ?

Clean flash from UAP 1028 no need flash boot.img ? or move or delete folder or file sensor in system. ?
[Nexus 5 Original Android Development] wbedard:
Is this build SELinux permissive or enforcing?

R/

wbedard
[Nexus 5 Original Android Development] Santosh B:
Still not working tried everything...

It stuck at Google and also the boot image not load properly :(:confused:
[Nexus 5 Original Android Development] JekaPinsk:
fastboot boot twrp.img

Then do wipes
[Nexus 5 Original Android Development] keretapanau:
Hotspot working?
[Nexus 5 Original Android Development] hbenz2008:
Working ok here. Full wipe, flash Rom, reboot recovery, flash unofficial Pico.

Booted up fast about 3min,LTE working

Wireless
[Nexus 5 Original Android Development] sickest:
GSM network here

umm..APN? ok i'll try to set it up manually, i haven't take a look at it

thanks mate :good::laugh:

edited: it works! thaaaanks :D
[Nexus 5 Original Android Development] manojks256:
Can anyone let me know the steps to flash this ROM. I am currently on LOS 14.1

Thanks
[Nexus 5 Original Android Development] GopalKaul:
Any Indian can tell me if with mobile data Jio4GVoice app works?

And [MENTION=4473900]amaces[/MENTION], great work there!!!
[Nexus 5 Original Android Development] sickest:
full wipe, flash rom, reboot recovery, flash gapps, reboot system :fingers-crossed:
[Nexus 5 Original Android Development] manojks256:
If I do full wipe how can I copy the ROM and Gapps files to phone?

Thank you.
[Nexus 5 Original Android Development] Pjotr91:
If you leave your device plugged to the PC via USB cable, after the full wipe with TWRP, you can see your storage and then you can copy the zip files that you want and procede like [MENTION=3535120]sickest[/MENTION] said.

I do it every time.

Be sure that you have all the drivers installed into the PC you use.
[Nexus 5 Original Android Development] manojks256:
Thank you, should I format System as well?
[Nexus 5 Original Android Development] Pjotr91:
Yes, but do a backup first.

Happy flash :D
[Nexus 5 Original Android Development] HermannSenator:
Hey guys!

I can also confirm that Data is fixed, dev did a superb work. A big thank you and let's enjoy Oreo!
[Nexus 5 Original Android Development] MoistPicklez:
Congrats [MENTION=4473900]amaces[/MENTION] !

You beat down the bugs and got us an 8.0 build with data! Thank you so much for all your effort!! You sir, are a legend!
[Nexus 5 Original Android Development] WildKitsune:
I'm unable to add a google account with the unofficial opengapps 20171002 suggested in this thread or the official opengapps. I start the play store and get stuck at "Checking Info..." until Google Play Services crash at some point.
[Nexus 5 Original Android Development] hbenz2008:
Skip Wi-Fi set up and all in the first launch, do it afterwards it works

Wireless
[Nexus 5 Original Android Development] ydv21yash:
which gapps need to be flash?? 7.1.2 or 8.0?
[Nexus 5 Original Android Development] WildKitsune:
Unfortunally this didn't change anything
[Nexus 5 Original Android Development] PresidentMcCain:
Try this:
[Nexus 5 Original Android Development] swapnildixit3:
Super work [MENTION=4473900]amaces[/MENTION]!!!

This ROM can be a daily driver for all of us and its because of you only.

Thanks again [emoji4]
[Nexus 5 Original Android Development] WildKitsune:
No luck again. I also wasn't expecting a change because I used pico packages without Webview or Chrome before, but tried anyways. Didn't change anything.
[Nexus 5 Original Android Development] Mr.ABDRABU:
which gapps should i use ??
[Nexus 5 Original Android Development] Pjotr91:
Sorry for my bad english to you all.

Dear [MENTION=4473900]amaces[/MENTION] here is my list of remaining bugs that i've found:

(dear users, please verify if it only happens to me. I want to point out that they are not serious bugs, at least for me, and the rom right now is fully usable.)

1. Bluetooth - it is on when i install a new build. It's a normal behaviour or can it be disabled by default?;

2. APN - is there any way to add automatically an APN? Because right now every user should create an APN to get mobile data to work;

3. Data Roaming - is enabled by default, should be disabled?;

4. Flash Toggle - you already know that;

5. Keybord (any type, even the aosp one) - if i'm writing something and i press the home button, keyboard it's still on the screen even if the app that i use to write text is gone. (Attached Image)

6. Multiwindow - when i try to go in multi windows mode, if there is only one app on the recent apps, if i press any key back, home or recent apps, something strange happens (Attached Image)

7. AOSP Keyboard - it crash when i try to use numbers from the toggle numbers. I mean not the one inside the letters. (By the way, this is something that can be solved by installing the GBoard, google's one)

8. Video Flickering - When i try to record a video, with the camera that comes with the rom, it seems to be good, but if i go to the gallery and try to reproduce it, it's like there is a flickering thing at the bottom of the screen. (This is something that i solved by installing the google camera suggested by:

9. Stock Browser - when i download something it cause package installer to crash. (I've solved installing google Chrome)

10. GPS - well, a user posted an image and the problem is happen to me too. When i use google maps and try to travel with the navigator this popup shows up even if gps permission is on. I've enconutered this error in Waze too. See it's post to look at the attachment:

11. Led notification - i really don't like, but it's me, the led notification for battery. Would you like to implement a way to let the user disable it?

12. because i don't like odd numbers (i'm joking)

So, thank you for your work and for this introduction to android 8 Oreo. I think that it is not an experimental version anymore, it's like a beta.

Happy download everyone.
[Nexus 5 Original Android Development] bagajohny:
I'm experiencing a strange bug. I'm getting 'No SIM card' error frequently. My signal gets lost and I have to reboot to get it back. Any possible solutions?
[Nexus 5 Original Android Development] cocogendut:
from SD Maid
[Nexus 5 Original Android Development] canpolat28:
Hi guys oreo rom have any bug ?
[Nexus 5 Original Android Development] Tornado15550:
BT HFP Bug. Best to just use 9.0
[Nexus 5 Original Android Development] VMCR:
I can"t flash the 1211 build why?

look at image below.

Edit: I have the lastest recovery.
[Nexus 5 Original Android Development] KevMetal:
:p:silly:

__________could you not read post

*simple solution

_install mixplorer

_install mix atchiver addon

_open rom zip DON'T EXTRACT JUST BROWse

_search for the updater script with search function

or browse to META-INF>com>google>android

_open it as text file

_delete all the assert lines

*all the lines until "mount"

_save

_exit & reboot recovery

_flash zip

BE AWARE I'M NOT RESPONSIBLE FOR DAMAGE TO YOUR RADIO / BASEBAND / IMEI

BE AWARE IF YOUR BASEBAND VERSION IS incompatible you won't get signal ...

ALSO_______could you not read post

QUOTE=JackyGundam;78423674]i have flashing problem... [/QUOTE]

Don't be afraid to search the forum. It's often the case that you're not the first to experience a particular problem.

https://xdaforums.com/showthread.php?p=78374838

READ THE THREAD / READ THE RULES / READ THE OP FLASHING INSTRUCTIONS / STOP ASKING THE SAME QUESTION LITERALLY 5 POSTS DOWN .....
[Nexus 5 Original Android Development] Huexxx:
I doesn't work... seems to be related to selinux permissions.
[Nexus 5 Original Android Development] riThviK995871:
Theme name please? :silly:
[Nexus 5 Original Android Development] cocogendut:
Theme?i'm not use custom theme
[Nexus 5 Original Android Development] VMCR:
Don't be afraid to search the forum. It's often the case that you're not the first to experience a particular problem.

https://xdaforums.com/showthread.php?p=78374838

READ THE THREAD / READ THE RULES / READ THE OP FLASHING INSTRUCTIONS / STOP ASKING THE SAME QUESTION LITERALLY 5 POSTS DOWN .....[/QUOTE]

You don't have to be so rude! I read all of that but that guy had a different issue.
[Nexus 5 Original Android Development] Skorpion96:
Try selinux changer

Inviato dal mio Nexus+5 utilizzando Tapatalk
[Nexus 5 Original Android Development] civikakias:
On the build 28/10 that i am using some weeks now, i have seen that there is some delay when i open some apps (fb/messenger/tapatalk) and when i open google maps is impossible to use another app, cause the phone is lagging a lot.

Anyone have these problems?
[Nexus 5 Original Android Development] naxomatrix:
Something strange is happening, I used the October 28 and I was doing very well, after installing the December and have the sensor problem, return to the 28/10 again and now it is constantly restarted, the installation was completely clean .
[Nexus 5 Original Android Development] wallefclima:
I installed Android 9 ROM on 11/12 and the proximity sensor does not work and the screen rotates. already on 28/10 was working, now it is not anymore when I installed it again.
[Nexus 5 Original Android Development] iliuweiming:
Thanks[/url]
[Nexus 5 Original Android Development] Tornado15550:
Did anyone get the swipe up to multitasking gesture working on the latest build?