yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] amaces:
Great, I was worried it might be something beyond filesystem. These fixes would have turned up when we rebase and merge kernel/common and 3.4.113, but I'm glad it's fixed already.

Thanks for replying; I believe you're the author of that patch? What I meant is that you aligned 11j panel loading with rev. 11's, but the DSI on command sequence was not adjusted, so both JDI panels seem to use exact same DTS in the PA kernel (equivalent to straight including rev11 DTSI into 11j DTS). Despite that, J1 panel is probed successfully, and all is good on PA according to my one tester, so am grateful that you worked on it.

Here's my issue now: if I hook up that panel into MDSS/DSI, the system just doesn't boot, no ADB, not even last_kmsg upon warm reboot. But if I hook it up incompletely (e.g., use non-CAF properties), it does boot (w/o screen), ADB works, etc, and it even tells me that panel DTB is wrong. As soon as I fix it (your patch, or my approach), all hell breaks loose, and it seems like only recourse is serial console. I just don't understand what could break so badly, when J1 is only different with regards to one command sequence, and in your case, that doesn't even seem to matter.

Edit: Looks like you have the J1 panel variant, and unfortunately, that last_kmsg is for previous recovery run, like it happened to my other tester. If you're interested in working/testing builds, let me know. I really hope we can avoid UART on this one, but that might the only way to get kernel logs.
[Nexus 5 Original Android Development] Sashko98:
It seems that commit 188c91b causes the issue for some reason. Reverting it solves the problem.
[Nexus 5 Original Android Development] Amy07i:
or add the recoveryonly flag for the /system partition in the fstab.hammerhead. Just like other msm8974 devices. https://github.com/LineageOS/android_device_htc_msm8974-common/commit/ff5a407d7465f158613377b0c6b5d7b24674ebe7#diff-881cfbdebfa6c9606812f4e7f595a4d0
[Nexus 5 Original Android Development] amaces:
I took that change out in the current boot image in Downloads; let me know if it works on rev. 11j. Still, it would be nice to understand why it only breaks there. The "android,*" DT nodes are not even read by kernel, but by userland (init/fs_mgr), which is exactly the same everywhere. Thankfully, we don't really need this change for now.
[Nexus 5 Original Android Development] Sashko98:
I tested it out before posting, but here is a screenshot of it booting successfully.
[Nexus 5 Original Android Development] lulli1:
I'm on your latest 2.5.2018 caf version with latest 5.5.2018 caf boot image and I have a replacement screen. It seems to work here. Thanks a lot.
[Nexus 5 Original Android Development] beast97:
can i use the rom as daily driver???
[Nexus 5 Original Android Development] lulli1:
Depends on what you expect from it. Bt voice calls don't work and [MENTION=4473900]amaces[/MENTION] video flickering bug is gone, but theres no sound from camera. Just a silent brrrrrrrr.

Are logs helpful in that case?

I have magisk 16.4 installed. Maybe anyone without could check if magisk breaks the tone....
[Nexus 5 Original Android Development] HermannSenator:
I'm sorry, but everything works fine on my end. I have the same configuration (i.e. ROM with Magisk 16.4). Anyway, I'm using the built-in camera app, if it is helpful for you. Maybe you can try a clean flash?
[Nexus 5 Original Android Development] lulli1:
Ok thanks a lot. Good to know! Yes I dirty flashed. Will try a new clean flash as soon as a test version or patch for bt voice call bug is available. If you need testers here..... Voila I'm in.... Up to 6 testbuilds per day, with all kinds of logs :p
[Nexus 5 Original Android Development] ryanbin:
Just wanted to report that I switched to the latest caf version today (clean install; 2018-05-05 02:29 boot-hammerhead-caf.img and aosp_hammerhead-8.1.0-20180502.zip with Magisk v16.0) and everything is working great so far. Video flickering in camera is gone. Haven't had a chance to test Bluetooth calls yet, but I think amaces said he hasn't looked at that yet anyway.

Thanks as always for an awesome ROM!
[Nexus 5 Original Android Development] candra yudha tama:
Can you install viper4android ????
[Nexus 5 Original Android Development] ryanbin:
Candra,

Looks like this developer has a version of Viper that works with Magisk. Just flashed viper4android-v6.1.1-Magisk-1500.zip from TWRP and it works fine. Didn't have to install Busybox or mess with SELinux at all.
[Nexus 5 Original Android Development] candra yudha tama:
Ok I will try ;)
[Nexus 5 Original Android Development] candra yudha tama:
yuuuppp.....viper4android work fine :D on my nexus 5.... thank you very much ;)
[Nexus 5 Original Android Development] :
Hey Amaces, when you will upload new build 7.1.2 with may security patch? I want to flash new version with the latest security patch. Thank you :)
[Nexus 5 Original Android Development] zozanyo:
Is anybody working on bluetooth calling? I think it has something to do with mono and stereo bluetooth audio channels because normal music und stereo apps work fine over bluetooth. I really need bluetooth calling which is distorted in all 8.1 roms for nexus 5. Is there a work around or something to force mono audio for calls and voice chats to go through media stereo und not mono calls. This might solve the issue but I have no idea how
[Nexus 5 Original Android Development] cocogendut:
Test new build ? caf/noncaf
[Nexus 5 Original Android Development] Android-Andi:
We'll update once we have time - like always.
[Nexus 5 Original Android Development] lakija:
Anyone else has bad sound on recorded video?
[Nexus 5 Original Android Development] s4ni:
New Build is UP.....:)

flashing right now....
[Nexus 5 Original Android Development] archish:
What's new?
[Nexus 5 Original Android Development] s4ni:
May 5 Security Patch....;))))
[Nexus 5 Original Android Development] anilspice:
Hi Amacess, Missing the useful "Ambient Display" in the settings on newest 8.1.0 rom of 09th May....Could this function be added separately or has to be part of the rom build?

Hope next build incorporates this..
[Nexus 5 Original Android Development] amaces:
I'll just refer you to this post, where the Nougat security updates are discussed.

Basically, security updates below Oreo always take longer since they're cobbled manually. We usually trigger builds when meaningful updates are available.

Please add some detail to your report (e.g., UA (non-CAF) build or the more experimental CAF ones, which camera app, etc). Posting a sample might also help since I can't reproduce with built-in or Google camera.

That component requires a Lineage repo (https://github.com/LineageOS/android_packages_resources_devicesettings), and was built temporarily. I'm not sure it's appropriate to use that code in an AOSP build. The HammerheadDoze code itself would also require cleanup and refactoring to reintegrate it properly into Settings. Were you actually changing anything with that UI? If it's important to you, you could extract the APK from the older experimental build, and try to install it on the current ones.
[Nexus 5 Original Android Development] anilspice:
Thanks for the reply, yes this option of ambient display was useful to me. Anyhow I do understand, tried extracting hammerheadDoze APK and installing but it did not work and was force closing. So now I am on your old 5th may ROM with boot image of 9th. This way I am able to retain the option BUT missing the May security updates.

Thanks for the information.
[Nexus 5 Original Android Development] crisis_trustee:
Dear amaces,

What TWRP is better to use for flashing your AOSP-hammerhead (caf) build - TWRP for hammerhead or TWRP for hammerheadcaf? :confused:
[Nexus 5 Original Android Development] mike9976:
Hello is anybody else's having problems signing into Facebook or message hvnt been able to sign in since the last 2 builds thx
[Nexus 5 Original Android Development] lulli1:
Latest 3.2.1.1 was perfect.
[Nexus 5 Original Android Development] crisis_trustee:
And one more question: What fs is better for AOSP (caf) hammerhead - f2fs or ext4? :confused:
[Nexus 5 Original Android Development] lulli1:
Would always use ext4. No problem with any ROM, and benefit of f2fs is really small
[Nexus 5 Original Android Development] :
can explain about the "few more filesystem fixes" as i have similar issue with AOSP rom for condor ( a.k.a moto e). The magisk hide cause the apps to be uninstallable.
[Nexus 5 Original Android Development] losl1946:
Hi, dear lulli1, May i know which 2 Android 8.1 versions installed in your third N5? Were they installed as secondary roms in the multirom system?

I using "multirom-20170314-v33a-UNOFFICIAL-hammerhead" and "TWRP_3.1.0-0_multirom_hammerhead_20170314-03 by Captain_Throwback". I have darkrom 7.1.2 los based as my primary rom at the internal storage and works fine. I tried installing some 8.1 from this list "https://xdaforums.com/google-nexus-5/general/list-roms-hammerhead-oreo-roms-01-09-18-t3733094" as secondary rom, but all failed.

1) LineageOS 15.1(by Krizthian&by P4Block) have systemUI stopped error.

2) Dark Rom 15.1 not working too "https://xdaforums.com/showpost.php?p=76594492&postcount=6455".

3) This rom AOSP Unlegacy Android 8.1 feezing with Google logo and not booting at all, seems that the storge not mounted. I am quite frustration on these. Do you have any advice for these installations?

Sorry for the long post and thanks to everyone!

Regards.

SLo
[Nexus 5 Original Android Development] lulli1:
Don't use multirom on my 3rd n5 anymore. My mentioned post was ages ago... Your problem is the old TWRP version on multirom. For all newer 8.1 Oreo roms you need multirom TWRP 3.2.1.1 and there's none for our device so far.

BTW you are in the wrong thread. Please head over to the multirom thread for your issue.
[Nexus 5 Original Android Development] losl1946:
Thank you!. It seems that i have to give up multorom. Just for curious how can you flash 5 different roms (OS's) on your3rd n5, are you using "EFIDroid"?

Regards

SLo
[Nexus 5 Original Android Development] lulli1:
No. It was by using multirom. If you edit the flashing script for each 8.1 ROM, you were able to flash it with old multirom twrp in the early 8.1 times. Don't know if you will succeed any longer. But if I got you right, the flashing worked for you without mistakes, but it doesn't boot, correct?
[Nexus 5 Original Android Development] GopalKaul:
Is it a 32 GB one or 16?
[Nexus 5 Original Android Development] Mark_8:
Hi guys!,

Im just a new member of XDA, but im following this website from 2012 when i bought the galaxy s2.

Now, its already 2 years and 6 months that i have my refurbished nexus 5 32gb (european model) and im in the hope i will finally install oreo on my device.

I already flashed a previous one 8.1 (april release,if i remember correctly) build but it had the video recording bug.

So I would like to flash the caf version but im afraid of the display problem.

I noticed the creator of the rom has also relesed a non caf build but i dont undertand if it has vid recording fixed or not.

Im waiting for a more stable release .

I also saw the resurrection remix thread but for now im in the doubt :confused::confused:

Anyway congrat to the devs who porting these awesome roms to our phone!:silly::good:
[Nexus 5 Original Android Development] losl1946:
You are correct. The flashing worked perfect, (some roms got an error 7 during flashing after i modifying the updater-script in META-INF/com/google/android the flashing steps completed as expected. ) And the booting process failed.

SLo
[Nexus 5 Original Android Development] lulli1:
16 in that case my other 2 ones are 32.

But no problem to drive 7 diff. Roms on a 16 gb phone. You simply mustn't install lots of apps and use Pico gapps or no gapps if you don't need to.

You can use the latest caf build without problems, I did so and have a replaced screen as well.

Yes, but that booting error is due to the TWRP version as allready mentioned. Maybe [MENTION=268386]blade[/MENTION] could help you. Head over to the multirom thread, please.
[Nexus 5 Original Android Development] bagajohny:
Does this ROM support signature sproofing? Can microG be used with this ROM?
[Nexus 5 Original Android Development] Android-Andi:
Only UnifiedNlp
[Nexus 5 Original Android Development] kotfilon:
Does Elemental X work? :) How is battery life?
[Nexus 5 Original Android Development] :
ElementalX kernel won't work. caf or non-caf version. Oreo is still in beta so selinux is permissive by default which elementalX doesn't allow.
[Nexus 5 Original Android Development] Mark_8:
Ok, thank you:good:
[Nexus 5 Original Android Development] mattx89:
Has anyone noticed lags on scrolling in the latest CAF version? With the previous NON-CAF version it was ok.
[Nexus 5 Original Android Development] namerke:
I guess this would really heavily depend on the app you try to scroll in, also the number of background processes that are eating away resources , but overall i didn't find any difference in this regard compared with earlier builds. Latest CAF build is all fine on my side :good: .
[Nexus 5 Original Android Development] ThePiGuy:
[MENTION=4473900]amaces[/MENTION] would it be possible for you to share the details of how you managed to get the BT calling audio to work?

Ugly or not, it would be very helpful for the community if you could share it because then other devs can assist to help get the problem solved for everyone (then all the pressure is not only on you ;))
[Nexus 5 Original Android Development] jineshpatel30:
find it in this thread's Download section...btw it's not pure CAF, it's CAFied AOSP

https://xdaforums.com/devdb/project/?id=20312#downloads

Also black screen issue was related to noguat-camera-fix zip, normal GC apk installation works properly

---------- Post added at 01:20 PM ---------- Previous post was at 12:28 PM ----------

@amaces any major change in 1/6 CAF build ?
[Nexus 5 Original Android Development] Disrupthor:
Is it possible to have one build of Unlegacy Marshmallow for the Nexus 5 ?
[Nexus 5 Original Android Development] Tornado15550:
Why are you running 6.0? You can run 7.1.2 with 0 issues or 8.1 with the only issue being Bluetooth hands Free calling not working. Both are just as fast (if not faster than) 6.0 with the latest features and security updates.
[Nexus 5 Original Android Development] jineshpatel30:
I have been on 7.1.2 for more than a year just before i fed up and decided to go back to MM two weeks ago and i must say, 0 bug/problems on N for hammerhead is myth.

The biggest difference, there is no hidden battery drain on MM & much better performance, which you may not notice at first due to less fancy animation of MM than N but within a week you will see the difference in performance in almost every step. So, In my opinion N is just trade off for fancy looking over stability for N5. (this goes for every device/ROM which has no official support for that version)

PS: No offence to hard work of custom ROM devs, this is just some differences i noticed
[Nexus 5 Original Android Development] lulli1:
Would you please tell us on which security patch level you are on MM? ?

That was the main reason for me to update to N as Google decided to left us us alone without official N support and without security updates for MM in that fragile Android world. Now even N isn't updated any more...

If someone would update stock MM every month just by merging the monthly security patches, I would be the first who would downgrade to MM.

And to be honest, maybe destroi my argumentation again by rooting and installing Xposed and gravity box ??
[Nexus 5 Original Android Development] jineshpatel30:
From which serious theft does newest security patch protected you over the years? It's good to have latest one but it's not like that your are missing out something.

I would rather have rock stable ROM than security patch number on my device info screen.

Btw I'm on PureNexus without root. Don't find any use of root since most of my desired customisation are already covered by PN.

Cheers.
[Nexus 5 Original Android Development] mike9976:
Hello could someone tell me where I could find the bootloader I looked on Google those was the old ones I can't install the rom thx
[Nexus 5 Original Android Development] dm1980:
I have a problem with the clock application in the last two compilations. I set a specific time for it to sound, but it never sounds. I do not know if it just happens to me or is a problem in general of the compilation.
[Nexus 5 Original Android Development] amaces:
Recording Artifacts in AOSP Builds

People using the regular AOSP Oreo builds (or ua_hammerhead-7.1.2-EXPERIMENTAL-20180529-1011.zip), are video recording glitches gone?

Mostly kernel changes, including all missing changes from kernel/common, plus 3.4.113 merged for initial testing. This had to happened before I start rebuilding the kernel on a common CAF base.

Either should work for basic operations.

I think the Magisk issue people had here was different. Look at e88fe786438d (ecryptfs: don't allow mmap when the lower fs doesn't support it) through 27c44f7051d7 (BACKPORT: KEYS: potential uninitialized variable) in the current CAF tree.

As Andi mentioned, UnifiedNlp should always work in UA builds. I've also enabled full signature spoofing in recent experimental or personal builds. The latter will likely keep it, but non-experimental UA builds will skip that support.

The bigger issue is 64-bit Binder support, which is not a given with third party kernels. Lineage requires it for example, so that early decision seems validated. Either way, third-party kernels might eventually work on regular AOSP builds, but very unlikely on CAF builds.

There were some HWC changes before the first June build. The current builds (latest includes June security updates) should be back to normal.

I mainly hardcoded a few sampling rates in some audio HAL paths, but they ended up breaking other audio functionality. Look at the changes introduced in https://android.googlesource.com/platform/hardware/qcom/audio/+/8c03e67b.

They proved to be an unacceptable trade-off, and only worked in some VoIP apps (e.g., CSipSimple, but not Hangouts Dialer). I'm sure other people tried similar changes, then gave up on them since breaking primary audio functionality is worse. I'm sure we'll fix it eventually, but I need to finish new kernel and device tree work before getting burned out with BT/audio HAL again.

I guess nothing stops us, but it'll require a bit of work in device tree since we'd be using same kernel everywhere. Is Marshmallow something you plan to stick with longterm?

Just curious, have you tried current CAF builds? Battery drain (idle or active) seems improved to me.

Actually, we keep Marshmallow branches up-to-date (currently, May level), so there would be benefits to new 6.0.1 builds (beyond the many kernel improvements we'd get with the Oreo kernel). I just never worked on it since there was an AOSP port already; will look at it next few days.

Alarms in the AOSP clock app are supposed to be broken in all Oreo branches, and we've debated forking yet another repo where Google delays fixes… In the meantime, the solution is to use Google's clock app on Play Store.
[Nexus 5 Original Android Development] jineshpatel30:
I last tried 09/05 build and yes there's Less battery drain compared to N builds of LOS based ROMs but it's still higher in AndroidOS/SystemOS part compared to MM for some reason.

May be WiFi or Doze service are keeping this drain higher than MM. For comparison on MM this computed power usage in a day for these two are less than half of that's on 7.1.2 (Sorry i don't remember values for Oreo CAF build so can't compere with MM)

That's great :) But i wish some Dev or You guys can include some essential feature (like Pure Nexus) in Older Unlegacy Builds because most devs will choose latest Android (Oreo) as base to add feature/new ROMs. So, these older version won't get any attention and ultimately we have to use Xposed to get some of bare minimum customization over Unlegacy which is not a very good idea in my opinion.
[Nexus 5 Original Android Development] Ahkah:
au contraire

There has ever been and still is much hidden battery drain in the original OS. There are many reports for this "feature", even a bug database entry that always has been ignored by Google.

For example see here: blöng and bläng.
[Nexus 5 Original Android Development] jineshpatel30:
May be there is Issue on Google side as well but to be fair, since i went back to MM i see Flat curves in Battery usage every night for 6-8 hrs with max 1% battery drain.

Edit : check SS for confirmation.. ignore 51-54 increase in battery % as it's effect of doze not actual increase do over night it stayed merely at 51% only
[Nexus 5 Original Android Development] Ahkah:
I ran many tests over the years, and the problem even occurs with both WLAN off and mobile data off. I first saw the phenomenon when I inserted the SIM card, not before. In most cases I can avoid it by neither using the camera nor navigation. A workaround is to reboot the device after having taken a picture.
[Nexus 5 Original Android Development] jineshpatel30:
Check my edit in last post

---------- Post added at 03:57 PM ---------- Previous post was at 03:53 PM ----------

Well I don't use camera/Navigation that much to notice this behavior but i'll keep an eye when i use next time.

What i was comparing before is my normal usage on both MM & N. Even with same use on both i see much more drain on N than MM
[Nexus 5 Original Android Development] forb'S:
Like [MENTION=4942685]jineshpatel30[/MENTION] I am on last PureNexus with blue_spark. This little included features in PN are very helpful to have. I use XPrivacy and it is for me a necessary tool. I am using FOSS apps out of F-Droid instead of Google Play but I want to have control which apps are taking permissions. The new XPrivacyLua is _not_ that great update for the newer Android version. So I would be glad to have an updated MM version and for me personally stick with MM longterm too.
[Nexus 5 Original Android Development] Disrupthor:
Yep, at least until my other devices get up to date too ...
[Nexus 5 Original Android Development] bagajohny:
Where is the link to CAF builds? Are the ones named 'EXPERIMENTAL' CAF ones?
[Nexus 5 Original Android Development] :
It is in Downloads tab available in this thread (not visible in mobile view).
[Nexus 5 Original Android Development] bagajohny:
Thanks a lot man. I was gonna put my head through the wall:p
[Nexus 5 Original Android Development] amaces:
I triggered an experimental/untested Marshmallow build (https://builds.unlegacy-android.org/aosp-6.0/hammerhead). It might not even boot, so please collect logs with any issue. Keep in mind that we're using the same Binder improvements, so other M kernels won't work.

The spirit of UA builds is to keep as close as possible to AOSP UI and behaviors, so we tend to work only on features or improvements that benefit already existing functionality. Changes to kernel or device tree are feasible, while system-wide/UI alterations are pretty unlikely, especially given the existing M port in AOSP.

Suggestions and improvements are certainly taken into account, with the proviso above.