yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] abemore:
Simplify your life man. Only one rom to maintain. I fully support it.

I dirty flashed from CAF to AOSP a month or two ago and I haven't looked back.

Feelings are a terrible way to gauge rom performance. We need to learn to eliminate variables and measure. According to the data, there doesn't appear to be any reason to maintain two versions.

CAF vs AOSP battery life & benchmark comparison: https://xdaforums.com/google-nexus-5/help/caf-vs-caf-t3341502/page3
[Nexus 5 Android Development] jacomail95:
I simply found the link in another thread, follow the link and you can download them
[Nexus 5 Android Development] xsniperx1895:
yes but ,i want the link for the thread too ?
[Nexus 5 Android Development] jacomail95:
It was a post in the Euclidean OS thread, a HC kernel thread for Nexus 5 never was created
[Nexus 5 Android Development] krombopulos:
me too
[Nexus 5 Android Development] szakalq:
Here is something: https://xdaforums.com/google-nexus-5/help/support-hells-core-kernel-nexus-5-t2873942/page189 and http://hc-kernel.blogspot.com/2017/03/n5-b23.html?m=1
[Nexus 5 Android Development] Dark_Eyes_:
New build is up!

Guys,

I'm pushing a brand new build as I write. It is quite a big one with some nice new features and bug fixes that have been there for a while. Here is the detailed changelog

- Merged June security patch (7.1.2_r17)

- Fixed bluetooth not displaying song metadata (allegedly, thanks Lineage)

- Fixed sRGB on compatible devices

- Re-added some LiveDisplay options (color calibration)

- Added custom clear all button in recents

- Added button to reset battery stats

- Added support for battery Usage alerts (3 dots menu in the battery screen)

- Added double tap everywhere in the lockscreen to sleep (thanks Lineage)

As always, I put a lot of time and hard work into this build, so consider a donation if you can spare a few bucks. Hit my PayPal here.

By the way, CAF is dead!

Enjoy!
[Nexus 5 Android Development] aciupapa:
CAF is dead?!? Wtf :eek: oh no :(
[Nexus 5 Android Development] dhruvdiatm:
I have successfully downloaded & dirty flashed 9th June'17 update.

Just informing for those who may be waiting for reviews.
[Nexus 5 Android Development] GR3AC:
Sorry that I have to ask this "noob" question​, but do I have to flash (in my case ElementalX) every time after an update or not, meaning that it will still be installed after the update?
[Nexus 5 Android Development] GopalKaul:
You need to, or else you will get the stock kernel
[Nexus 5 Android Development] focus-pocus:
Dirty flash will install its own stock kernel. You need to flash ElementalX after update. In order to automate, you can just put kernel flashable zip into FlashAftrtUpdate folder.
[Nexus 5 Android Development] GR3AC:
Ok, thank you very much.
[Nexus 5 Android Development] twili9ht:
Does Lineage and this rom support Substratum OMS? I've always been using the legacy Substratum and I was just wondering. Don't know if it makes much difference either.
[Nexus 5 Android Development] edi194:
[ROM][LOS14.1][7.1.2_r17] DARK ROM [OMS][Pixel features][Delta updates]

Standard Lineage doesn't support OMS
[Nexus 5 Android Development] AFU_Ra:
Just dirty flashed the new r17 update, from caf it was a smooth upgrade. But I did notice that the settings app crashes on color calibration, might be something to look into? Do you have any plans adding a quick tile for expanded desktop? It's the only thing I miss on this rom. Good job and thanks for the quick update!

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Android Development] GopalKaul:
Are you on stock kernel?Try elementalX for color calibration..
[Nexus 5 Android Development] Dark_Eyes_:
I'll look into that. It's working fine on my end, but it's probably device related. Thanks for the feedback!
[Nexus 5 Android Development] Dark_Eyes_:
By the way, bullhead build is up on the server :

https://darkrom.ca/bullhead

Please report how it goes. I'll start a thread if everything is fine! Thanks.
[Nexus 5 Android Development] AFU_Ra:
Yes I was. It does not seem to be kernel related (now on elementalX) maybe a clean flash would fix?.. but I'm not going to bother, it's not a biggy for me [emoji14] can still change color in a kernel settings app.
[Nexus 5 Android Development] jordanl68:
Guys, anyone having the problem with the system profiles of Lineage OS that disappear when restarting the phone? Need some help here
[Nexus 5 Android Development] krombopulos:
Haha, everywhere except where we used to put the lockscreen to sleep! That's gonna take some getting used to! Thanks for the update man, all is working splendidly.
[Nexus 5 Android Development] herbie13:
It boots, i'll have a play and PM feedback. Cheers :)
[Nexus 5 Android Development] Dark_Eyes_:
Lol, do you want me to add it back? It's easy, I just thought it wasn't needed anymore. But I agree it's weird when you are used to it.
[Nexus 5 Android Development] krombopulos:
I'm actually a bit surprised you removed it, I know it was one of your unique additions. I'm also surprised that the lock key on the lock screen is excluded from the double tap to sleep from the merge lineage has made. It won't take long to get used to :)
[Nexus 5 Android Development] coyote1071:
Hello [MENTION=2525031]dark.[/MENTION]..is this update only for AOSP?

Best Regards

Jürgen
[Nexus 5 Android Development] Green Daddy:
My Settings App also crashes on color calibration - I also came from CAF using dirty flash.

So if it's not reproducable for you I guess it's because of the dirty switch from CAF to AOSP. Did we even have color calibration on CAF?

-> do not bother for now...

.cc [MENTION=2665877]AFU_Ra[/MENTION]
[Nexus 5 Android Development] xsniperx1895:
Clean flashed and everything works (color calibration too) ,nice update !
[Nexus 5 Android Development] coyote1071:
ahhhhh ****...my fault sry. caf is gone...
[Nexus 5 Android Development] synkus:
The download link for CAF https://darkrom.ca/hammerheadcaf does not work. Thanks
[Nexus 5 Android Development] szakalq:
Read previous posts: "By the way, CAF is dead!"

Wysłane z mojego Nexus 5 przy użyciu Tapatalka
[Nexus 5 Android Development] Dark_Eyes_:
Apparently clean flash works, so maybe those who dirty flashed AOSP over CAF didn't have that much luck (unless you don't care about color calibration...). I'm still interested in a logcat, maybe there is something I can do to fix it.
[Nexus 5 Android Development] Green Daddy:
Here you go :)
[Nexus 5 Android Development] spibbs:
Persistent boot animation

Is there any way to include a boot animation in the open delta flashafterupdate folder, or have the bootanimation protected and not overwritten when I do an update?

Thanks,

I clean flashed the AOSP version, after using CAF for the last few months, can't tell the difference. Great ROM, thanks again.
[Nexus 5 Android Development] mystique47:
Flashed aosp over caf, color calibration crashes but who cares? :D

Flashed blu spark kernel (stock lineage kernel seems a mess!) and edited with kernel adiutor; performance is the same as caf: this phone remains always really fast. The really only thing which lags is facebook.

I hope you'll port this rom on oneplus 5 :P
[Nexus 5 Android Development] AFU_Ra:
messages from the loghttp://cloud.tapatalk.com/s/593c9411d1b6f/loglady.txt
[Nexus 5 Android Development] Dark_Eyes_:
Can you send me the complete log. There doesn't seem to have any errors in there. What exactly happens? The settings app force closes?
[Nexus 5 Android Development] Dark_Eyes_:
Go to system/addon.d, open 70-gapps.sh. You'll see a lot of app/xxxx in the middle of the file. Simply add a line and write media/bootanimation.zip. It will keep the same bootanimation that you had before dirty flashing.
[Nexus 5 Android Development] AFU_Ra:
my bad didn't do a proper logcat I suppose. (first time used the terminal) here's the complete log from Matlog with errors (settings app force closes on calibration yes) http://cloud.tapatalk.com/s/593ca8266694d/logcat.txt
[Nexus 5 Android Development] mobile_sensei:
Haven't been here to the forums for a bit & just logged in to grab 6/9 update... Are the CAF builds gone?
[Nexus 5 Android Development] focus-pocus:
Guys, please, read the author posts before asking. Yes, CAF is dead.

Also, [MENTION=5445418]Dark_Eyes_[/MENTION], you should probably remove mentions of CAF from key features list.
[Nexus 5 Android Development] hamimi:
may i know which magisk version is suitable for latest rom update. quite confusing
[Nexus 5 Android Development] GH0SТ:
Magisk v12.0 + Magisk Manager v4.3.3
[Nexus 5 Android Development] vurey:
I switched to Facebook Lite (sideloaded APK). Ugly as hell, but uses barely any memory
[Nexus 5 Android Development] sgtEN3RGY:
Battery has been very good compared to other ROMs, mostly on Wi-Fi for now.

This ROM combined with Blu kernel and forcedoze is just a pleasure to use, it's super smooth.

Best ROM out there and no wonder everyone is recommending it. Keep up the great work!
[Nexus 5 Android Development] amit_chapala:
[MENTION=5445418]Dark_Eyes_[/MENTION]

Sir cleaned flash from CAf to AOSP but still problem with colour calibration it crashes all times. Plz do something for that. And can't find tap everywhere to sleep. Thanks
[Nexus 5 Android Development] rizqi_ir:
anyone has a problem with the bluetooth? it can paired but won't connected?

---------- Post added at 10:54 AM ---------- Previous post was at 10:47 AM ----------

can i do this as well as to keep emoji font?
[Nexus 5 Android Development] Dark_Eyes_:
I'll see what I can do about color calibration, but it's very weird that a clean flash didn't work. I also can't reproduce that bug myself on my n5. Double tap everywhere is in settings/security gear icon besides screen lock.

I'd like others to chime in about the Bluetooth problem. Is it a general problem?

As for emoji, if it is a file placed in the system partition, it can be done the same way. Adding any files in the 70-gapps.sh will prevent it from being deleted/overwritten during dirty flashes.
[Nexus 5 Android Development] Dark_Eyes_:
I found the bug about color calibration. It has nothing to do with flashing aosp over caf. It's a translation issue. Everybody not using English will have that bug, whether or not you clean flashed/dirty flashed. It will be fixed in the next update.

Also, I finally decided to release my sources. It's on my github here https://github.com/darkeyes84. If you want to do translations, simply make a pull request and I'll merge them. Thanks in advance!
[Nexus 5 Android Development] kmem:
I dirty flashed from CAF to AOSP and color calibration doesn't crash for me. I am on English though.
[Nexus 5 Android Development] Green Daddy:
Thanks! Even if it seems obvious, I'd like to confirm that setting primary language to English is a valid workaround for the time being, no reboot required.
[Nexus 5 Android Development] BazingaOG:
Hello, as far as I understand, there will be no future updates for CAF version. What is correct way to switch to AOSP? Just clean flash it? Do I need to change my recovery? (I remember something about using a CAF-compatible recovery, I might just confuse that with something else though).

As a side question: what was the reason to abbandon CAF? I always thought that that was the better option for Nexus 5.

And as always: thanks for your hard work!
[Nexus 5 Android Development] willyinpr4u:
You can try dirty flashing, if you see any problems at all, then clean flash, so far, people has post dirty flashing successfully. For CAF a TWRP hammerheadcaf was needed, not anymore with Dark_Rom, the latest TWRP works​ fine for CAF and AOSP.

Dark_Eyes decided to stop the development of CAF mainly because of security reason and the kernel hadn't bring updated in a long time. If you go back a few pages you can the post where he explain the reasons why.
[Nexus 5 Android Development] kmem:
I recently dirty flashed from CAF to AOSP. Several people in this thread had commented that AOSP felt "less snappy" than the CAF counterpart. For my admittedly minimal usage, I don't notice any slowdowns nor anything that appears less snappy on AOSP as opposed to CAF. Might be my use case or might be placebo. Didn't bench either as I don't really see the point but I do have both still installed via multirom. For what it's worth, it did run slower for about 10 mins right after flashing. Thanks again [MENTION=4347954]Dark_Eyes[/MENTION] for the fantastic work.
[Nexus 5 Android Development] TomiLynch:
The correct way to switch to AOSP is by clean flashing it:

First you'll have to download the normal hammerhead TWRP.img and install that through fastboot (i don't know if just flashing it in the current hammerheadcaf twrp will work, probably someone can comment on that).

Then wipe System, Data, dalvik, and cache (remember to create a backup first, just in case).

Finally install DarkRom's zip, then DarkGapps and then magisk or whatever root you want.

Reboot and you're ready to go.

You can also dirty flash AOSP over CAF, but you asked for the correct way to switch, and that is clean flashing.

To dirty flash you must install the normal twrp as well first, and then just install the latest release (you can wipe dalvik and cache if you want to, but it's not mandatory).
[Nexus 5 Android Development] focus-pocus:
Latest TWRP hammerhead supports both AOSP and CAF. So no need to switch between different flavors, if you're already on latest TWRP hammerhead. It's been like that for a while now (may be since version 3.0.1 was released?).
[Nexus 5 Android Development] TomiLynch:
As far as I know, this is correct but only if you have non-caf hammerhead twrp installed. With this recovery you can flash both AOSP and CAF roms as you said. But if you've got the latest hammerheadcaf twrp (sounded like he was on the caf version), you can only flash CAF roms, meaning that if you want to flash an AOSP rom, you'll have to install the normal non-caf hammerhead twrp.

Please correct me if I'm wrong.
[Nexus 5 Android Development] focus-pocus:
Yeah, probably, see my edited post. You posted, while I realized that, lol.
[Nexus 5 Android Development] Green Daddy:
Correct. You can flash hammerhead TWRP directly from TWRP app running on CAF. Thats the easiest way imho
[Nexus 5 Android Development] krombopulos:
unimportant bug report: if I'm connected to Bluetooth headphones, and disable Bluetooth through quick settings or regular Bluetooth settings, the connected icon with headphones battery indicator remains.
[Nexus 5 Android Development] AN649HD:
I flashed the 0528 version of the rom along with provided gapps, magisk and bluspark. I've tried wiping everything and flashing again from pen drive but the rom lags a lot. After a boot its good for a little while but soon everything starts lagging, sometimes it takes 10 seconds for a click to register and something to happen, even the keyboard becomes unresponsive. Running f2fs right now thinking it might solve the problem but it didnt. I checked the forum and I dont think any one else has this problem. I was running caf for a long time and till the april updates it was smooth but then it also started lagging and eventually shifted to non-caf.

Any solutions to this lag problem? After a reboot the phone does work properly for some time but in an hour or more it starts lagging like hell.
[Nexus 5 Android Development] pWEN:
Weird thing... I used the updater in the rom to pull down 06/09 (I'm on 05/28 AOSP), but the updater said it was grabbing the 05/28 files (screenshot attached). When it finished, I told it to flash, and it rebooted and *seemed* to do something, but once it was back up and running, it was still on the 05/28 version. I checked in the OpenDelta folder and the 06/09 zip is in there, so I'm not sure what happened. I also have the latest TWRP installed.

I'm just going to do a clean flash for now, but thought I'd mention this.
[Nexus 5 Android Development] herbie13:
Have you considered a manual dirty flash in twrp as the interim step before going the whole hog of a clean install? I.e. download full ROM from link in OP.
[Nexus 5 Android Development] pWEN:
Of course. This isn't my daily driver so I don't care if I clean flash it.
[Nexus 5 Android Development] Dark_Eyes_:
It most likely is normal. The update file that is downloaded by OpenDelta is always named after the version that you actually have, not the version it will be updated to. So, if you are on 0528, OpenDelta will fetch the 0528.update file (otherwise there is no way for it to know what the new version is...) You should look into settings/about phone to know what version you really are on. OpenDelta will also tell you after a reboot. I bet you are on the latest 0609 as we speak ;)
[Nexus 5 Android Development] willyinpr4u:
Flash another kernel.
[Nexus 5 Android Development] pWEN:
I am on 06/09 as we speak because I clean flashed. ;) And I did check what version it was on after it rebooted and it still said the previous version, I just neglected to get a screenshot of it showing that. I've done the OpenDelta updates before and never noticed it say it was downloading the version it was already on. It's certainly never failed to update the few times I did it that way before, and I follow the same steps to install every time. If it's a one-time fluke, then whatever. Thought I would mention it in case it's not. *shrug*
[Nexus 5 Android Development] Dark_Eyes_:
Ok, thanks for reporting. I'll be on the lookout for that kind of weird behavior then!
[Nexus 5 Android Development] Mepo78:
Is anyone else having issues with passing SafetyNet now?

It was working fine for me playing PoGo yesterday, but today it doesn't allow me to login.

I'm currently using the newest DarkRom AOSP with Blu Spark #129, Magisk v12.0.

Edit: Seems like SafetyNet was updated today? :(
[Nexus 5 Android Development] Barbiox Dogg:
How to use OpenDelta update? I have copied the full nightly file on my sdcard root, I have gone to the System update and select "Check" nothing happened. Am I missing something here?
[Nexus 5 Android Development] willyinpr4u:
Try disabling wifi and use your data, tap check again while on data, if it starts to check for an update, then you can go back to wifi. That's what I do.
[Nexus 5 Android Development] mikebeatrice:
Crap. Same problem here.
[Nexus 5 Android Development] aarnthrpe:
I'm also having issues​ passing SafetyNet. Something about "CTS profile mismatch."
[Nexus 5 Android Development] mikebeatrice:
I enabled "core mode only" in magisk manager's settings and after a reboot I'm passing again....

Confirmed that Pokemon Go launches okay as well.

I'm using the June ElementalX kernel from today, just fyi.
[Nexus 5 Android Development] aarnthrpe:
Can confirm that this worked for me as well.
[Nexus 5 Android Development] Nevermindthelabel:
Google figured something out on their end. Play services where updated today, and all Magisk setups with modules now trip. Core only mode seems to be the only way to go for now
[Nexus 5 Android Development] TheToto318:
SaftyNet work well on my Nexus 5
[Nexus 5 Android Development] AN649HD:
Which one? Shouldn't bluspark do the job?
[Nexus 5 Android Development] mikebeatrice:
Edit: whoops, misread what I quoted.

...nothing to see here.
[Nexus 5 Android Development] willyinpr4u:
Yup, it should do the job. I had that very same problem when I switched to AOSP, but once I flashed Hellscore kernel the problem was gone.
[Nexus 5 Android Development] kmem:
It seems that a lot of folks strongly prefer one kernel to another but not many seem to state why. I have yet to see a kernel comparison from a darkROM user. Any particular reason you prefer hellscoreto Blu or EX?
[Nexus 5 Android Development] willyinpr4u:
Just for testing purposes. I use Dark_Rom as my daily driver, and was using Liquid Smooth as a secondary ROM with Bluespark. So I just wanted to know how Hellscore would work with Dark_Rom. So far can't complaint with very good battery life. Liquid Smooth drain 20 to 30% in a 7 hours doze.
[Nexus 5 Android Development] m4tt72:
Also facing this problem, any fix???
[Nexus 5 Android Development] AN649HD:
Hellscore dosen't support f2fs? Also it hasn't been updated since March.
[Nexus 5 Android Development] ndarkside93:
Currently just there basic wake function. If it's working in myfluxi's CAF 14.1 build you can request the feature, and you might get a cherry pick. He didn't like to clutter up and add extra stuff to bog down the ROM. So the answer is, that is currently not supported.
[Nexus 5 Android Development] Dark_Eyes_:
No, it doesn't have it, I removed it cause I don't feel it works as it should. In fact, tilt and proximity sensors should be active only when having a pending notification, and right now it is active all the time. Which means it wakes your screen every time you tilt the phone or take it out of your pocket, and it also means that the phone is ALWAYS active and waiting for such behavior. I didn't test it much, but obviously that can't be good for battery... It's on my to-do list to look at the code and see if I can modify it a bit too be triggered only by notifications... Until then I won't add it in the rom, but if you really want it I can make a flashable zip for it...
[Nexus 5 Android Development] sazaesang:
Thanks so much for the prompt reply.

I'd rather let you focus on other important priority (but appreciate your generosity!), so it's definitely not urgent, however it be nice to have one in the future. (Cause it can be disabled for user's choice)

I guess this feature is more up to the user's preference and I find the current Myfluxi's implementation to be working quite well. I tested alot of N-Roms and only ones I found working was Myfluxi's CM14.1 (CAF) and Euclidean OS (the response isn't very good yet.)

I often leave my nexus5 facing down on the table as I work and lift my phone to use it and tilt feature is kinda nice because I can just swipe without pushing physical button. However I do understand the aspect of battery consumption and that it should be off by default. (I've been testing this for few days in actual use situation and if I setup the Truesight kernel tweaked properly I getting an actuate battery with the feature enabled.)

In anycase thanks for providing us the ROM, I honestly admire your approach on bringing Pixel feature out of the box while keeping the OS de-bloated. (Keep it up! :good:)
[Nexus 5 Android Development] AndroZeek:
after flashing SuperSu its working. Thanks

Can you please include Data Trasfer status in Status Bar in next update.
[Nexus 5 Android Development] krombopulos:
Can confirm delta update worked fine for me.

Can anyone direct me on how to get the cmactions.zip, for gestures, to survive an update?

I figure the wave to wake function is preferable to DT2W in terms of battery usage. - My N5 has a dodgy power button so I try to use it as little as possible and use the proximity sensor to wake my phone. I also make use of the power button on screen off for torch because it gives me a warning that my phone is about to turn itself off!
[Nexus 5 Android Development] Sui77:
Which GAPPS should I use?

The build in, or openGAPPS?

Will the delta update also update the built in GAPPS.
[Nexus 5 Android Development] Deeps66:
Refer Page#1, post#2, you will get the answer.

Will the delta update also update the built in GAPPS: I don't think it will update(not 100% sure)

Regarding Opengapps refer this http://xdaforums.com/showpost.php?p=69502371&postcount=151
[Nexus 5 Android Development] Passaralho:
Forgive me if I'm confusing it, but isn't this working by flashing CM Actions zip?

Thanks,
[Nexus 5 Android Development] sazaesang:
Not totally sure... (cause I'm currently on different CM14.1 with built-in working Ambient Display so I can't install CMAction3 MOD.)

If that MOD support Tilt Sensor "Pick up" then I think it's the same thing.

First time I saw this, it was running on Nougat - Nexus 6P and I felt it was quite useful for my needs.