yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] Vandikito:
You need to have a CAF Recovery for flashing CAF Rims... other way is to download the non CAF and flash it with your actual Recovery.
[Nexus 5 Android Development] Rls4ever12:
Every nougat ROM for n5 has the errors, is nothing. No need for CAF recovery on dark ROM
[Nexus 5 Android Development] Sui77:
2 things are missing for me:

a) working HDR

b) atp-x

I kno that those things are not ROM-related, but maybe there is a way to implement?
[Nexus 5 Android Development] focus-pocus:
HDR works in version 3.2 of Google Camera. Here's resigned apk, so that the app won't appear in Play Store (and hence won't get updated to non-working version):
[Nexus 5 Android Development] Rls4ever12:
[MENTION=5445418]Dark_Eyes_[/MENTION] not sure how hard it would be to implement but something about Bluetooth stack implementation. I don't think it would mess with the ROM but this is what I get when trying to use bluputdroid app to connect to ps3
[Nexus 5 Android Development] midijunkie:
do I have to remove the system camera? I always get the error Apk appears to be corrupted.
[Nexus 5 Android Development] Rls4ever12:
Do it through TWRP
[Nexus 5 Android Development] midijunkie:
sorry, maybe I'm not anymore informed but it's an apk. how do I install it through twrp? just copy somewhere? system?
[Nexus 5 Android Development] Dark_Eyes_:
Yeah, you have to remove any other Google camera that you have installed. They have the same package name but not th same signature, so they will conflict.
[Nexus 5 Android Development] Dark_Eyes_:
Try the aosp version. I don't know much about hardware/device stuff, so I'm not gonna mess around since I'll probably end up screwing everything lol
[Nexus 5 Android Development] Alpha-Retard:
I remember trying this app 2-3 years back. I tried a lot of different roms just to get this working but with no luck. It's useless to try since the developer hasn't updated it in a long long time. AFAIK it doesn't work with any N5 rom (even the kitkat ones).
[Nexus 5 Android Development] Rls4ever12:
Erase the other through twrp.
[Nexus 5 Android Development] Dark_Eyes_:
New build is up!

Guys,

I just pushed a brand new build for both version. Among fixing the suggestion category for dark mode, here is the changelog :

Reboot/recovery tile

Music tile

Fix notification ticker (now works with inverted status bar)

Add dark mode to power menu

Probably a couple things I forgot. I had to come up with original code to fix the ticker for inverted status bar, so that's why it took a bit of time but I'm glad I finally did it :) I know maybe 2 people use it, but now it's a complete feature ! Anyway, the next step will be add dark mode to notification (already started) and rebase on Lineage OS (still to do, but probably easy enough).

Enjoy !
[Nexus 5 Android Development] surubutna:
[MENTION=5445418]Dark_Eyes_[/MENTION] I'm getting a security error/warning on Chrome when I try to download the new zip. Anyone else? screenshot
[Nexus 5 Android Development] drive2droad:
Yes i got the same error too but my AV flagged it as safe !!
[Nexus 5 Android Development] Dark_Eyes_:
It's totally safe guys, no idea why it got flagged like that, but it's no different than any other version I've been pushing.
[Nexus 5 Android Development] Alpha-Retard:
I'm getting a message that's saying that the zip file is corrupt while trying to flash the latest build you uploaded.

Edit: nevermind found the cause, I used airdroid to transfer the zip over but for some reason it failed to transfer it completely hence leaving a bad zip on the phone.
[Nexus 5 Android Development] Sandeep Naik:
Everything is working excellent except the Expanded Desktop . I'm not able to see

per app

expanded settings. Other than that everything is awesome. On the latest build (3-1-2017) even Google assistant is enabled by default. This works excellent. Thanks for the great ROM. Awesome work:good:
[Nexus 5 Android Development] MuhammadHesa:
What's caffeine? Can someone explain?
[Nexus 5 Android Development] razor17:
cm-14.1-20170103-NIGHTLY-hammerheadcaf.zip

Google chrome say "This file is dangerous, so Chrome has blocked it"

Anything wrong with this file?
[Nexus 5 Android Development] Pshemo__:
Dark_Eyes_ said that everything is OK with it

---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------

As far as I know it's just a 5 min timer which lets you now when your coffee is ready to drink :) (not too hot)
[Nexus 5 Android Development] Dark_Eyes_:
Guys,

I just noticed that the ro.product.model line is no longer needed to have Google assistant working, so now it is enabled by default even on the Nexus 5. Now, do you guys feel like I should disable it since it asks over and over for the hotword enrollment? I don't want to force it on anybody since it's not working "as expected"...
[Nexus 5 Android Development] sgtgs:
It keeps your screen awake for 5, 15 or unlimited minutes even if the automatic screen off time is 30 seconds... Pretty good feature:highfive:
[Nexus 5 Android Development] Antares9:
once again, after I flashed the latest update some of my apps are gone. any idea why [MENTION=5445418]Dark_Eyes_[/MENTION]?
[Nexus 5 Android Development] silvertrain78:
I would prefer to not have it enabled by default, especially since it doesn't work correctly. If someone really wants it, they can easily take the initiative to enable it and then sort out the hotword enrollment situation
[Nexus 5 Android Development] macci10:
I like it that way. It's good to play with it. :p
[Nexus 5 Android Development] Dark_Eyes_:
Are they system apps? If so they need a backup script, otherwise they all should survive dirty flashes. What app are we taking about? How did you install them? If you installed them from recovery, you should put the zip in the flashafterupdate folder or flash them by hand every time.
[Nexus 5 Android Development] Globespy:
Loving this ROM.

First time trying CM based ROM and I'm very impressed.

Any way to enable battery percentage in the battery 'ring' icon?

Also, I miss the features of ElementalX kernel that allowed the ability to change the screen color (deeper blacks like AMOLED display). Anything similar for this ROM? The stock kernel seems terrific - only used 3% battery over 7 hours sleep last night which is fantastic so not sure I want to change. Unless there's a recommended kernel that provides same great battery and has screen color profile options like ElementalX?

I was prompted to update to what looks like a new version within hours of installing it. I read that this is the Delta updates feature, but not sure if I should install these if I want a stable daily like this last build (12-29-2016) seems to be? I figured out how to turn off but wondered if I should just let it always update? Not sure if these update prompts require me to set the phone up again or wipe before installing? I read that the nightly file I used to install should be stored in the root of the SD card but doesn't seem the rooted by default - is only the CAF version rooted? I used an app (root checker) and device is not rooted by default unless the app is not compatible with CM based ROM? Several other apps that need root report no root on this ROM.

Do I just copy into the lowest directory I can get in my internal memory (permanent SD card)? I read a post in this thread that suggested it should be pre-rooted and NOT to flash SU?

Or is this from old builds and should SU be flashed? Will this mess with anything like the V4A that works in enforcing (awesome addition)?

OP says exposed features are able to be used but how is this possible if not rooted?

Thanks!
[Nexus 5 Android Development] sghmk12:
Okay so it seems that you are a little confused right now. The Delta updates basically automate the process of dirty flashing the ROM and so your data will stay but any modifications you did to the system partition would be wiped. All the builds dark eyes releases are supposedly stable and he can't say that one is more stable than the other unless in the thread he specifically states that one build is a testing build. Nonetheless I'm pretty sure he doesn't release test builds into opendelta. There is no need to put your original ROM zip into any folder I don't know where you read that, I just deleted mine. However on a personal note I always keep a flashable ROM zip for a known bootable ROM in my downloads folder in case my current ROM corrupts, but that hasn't happened yet. This ROM does not come rooted and I haven't looked at his instructions regarding root but something that I am sure about is that xposed for Android 7 still isn't out yet.
[Nexus 5 Android Development] Globespy:
I got all this info from what looks like another thread for this ROM, this is also where I got the download link for the ROM. You will see in the OP all the info I referenced

https://xdaforums.com/google-nexus-5/development/rom-dark
[Nexus 5 Android Development] Dark_Eyes_:
Yeah, the thread you read was for CM13, which was a marshmallow ROM. Read the OP of the current thread for more info. But to answer a few questions, the ROM comes unrooted, so you have to flash SuperSU or any other root package to get root. That won't affect anything, and V4A will still work ! Secondly, delta updates are only a small packages to help update the ROM without downloading the whole 250+ mb file that contains a lot of unchanged stuff from the last version. To make it work, you need to keep the ROM zip file you downloaded on the root of your sdcard (root of sdcard means the very first folder, not that it has root), so the app can donwload just a small patch and apply it on top of the ROM you already downloaded. Neat isn't it ! Oh and that won't affect anything that you have setup on the phone, and GAPPS will still be in. All you need to flash again is other flashable zips you might want (like SuperSU).

As already noted, all my builds are stable. I don't know why people report better battery life on one or the other, they should all pretty much be the same (might vary on kernel change, but it's been the same for the last couple updates). Read the OP for how to use the opendelta app (especially the updateafterupdate folder where you should put your SuperSU package).

Lastly, xposed was built-in in my cm13 ROM, but it's not available on nougat yet, and to be honest I don't think I'll have it there by default when it gets out. I opted for a more 'install what you like' kind of approach for this version.
[Nexus 5 Android Development] reload05:
After Update 20170103 'OK Google' doesn't work anymore. Til that update is worked perfectly. Always wants training. But after first voice-training it doesn't want the second one, but it starts the training from the beginning. What is to do?
[Nexus 5 Android Development] lynnux:
[MENTION=5445418]Dark_Eyes_[/MENTION] With the official CAF version not seeming to be supported, would you please explain what you'll be doing with your CAF version going forward? If you keep maintaining it, I assume you'll be incorporating the regular LineageOS updates into it. What about any updates that are specifically for CAF? Or is there such a thing?

I'm asking because I've been on the unofficial 14.1 CAF version and it wasn't easy getting it to work on my CDMA network (it's not even supposed to work), so for me it's not a case of just backing up and trying out different roms. Restoring my backups always messes with the data part of my Sprint network connection until I jump through some hoops to get it working again. It's been totally solid, and smooth, that's why I haven't moved on from it. But I'll probably give this a try since it's supported.
[Nexus 5 Android Development] Chandu2105:
Hi All,

I am on the latest 3rd Jan build -> non-caf and I am unable to use the mobile data. I don't see any H+ or LTE symbol when I switch on the mobile data in the status bar. Not working through one tap action of the advanced tile. Any one with the same issue? FYI, I have updated thru the openDelta system from the last build. I use Franco r102 kernel with Naptime.
[Nexus 5 Android Development] alsheron:
I'd say disable it unless it can be "tamed" in some way. Not seen the behaviour you're referring to (asking over and over for hotword enrolment) so no idea if it can be skipped or once the hotword enrolment is done it stops asking? I have to say actually that the "OK Google" detection seems to have been flakey for quite a while now, sometimes working well and responding to the hotword, sometimes not so much for example when navigating in Google Maps now, it doesn't respond to "OK Google" prompts anymore where a while back (again not sure when - not much use sorry!) it would respond flawlessly. I should have said as soon as I noticed this but it seems to keep cropping up for me didn't want to be a "stuck record". I'm just about to do a clean flash of your 20170103 build and see how it goes. Hopefully Assistant will come to all phones as standard soon so no "hacks" will be needed. Maybe the change you mention is preparing for that?
[Nexus 5 Android Development] Pshemo__:
Check if there are correct APN addresses for your network in Settings
[Nexus 5 Android Development] Dark_Eyes_:
Yeah, I will revert the Google Assistant change. I added the eligible prop to all builds thinking it wouldn't work on the Nexus 5 since I didn't change de model name to Pixel, but apparently it's no longer needed. It might be because Google is getting ready to release it to other devices, or simply because having both the eligible prop check and the device model check was redundant and useless. The thing is, Google Assistant works flawlessly on my Nexus 6P, so it's gotta be something device specific about it. Those wishing to keep using it and get rid of the enrollment bug can download Chop Assistant from the PlayStore. I know that it somehow messes the OK Google hotword too, so it will be gone in the next release. If you want to revert this change right now, just open your build.prop and set the ro.opa.eligible_device to false. Hard reboot the phone and you will have the old OK Google enrollment. Sorry about that, I didn't think to specifically test this with my test Nexus 5.
[Nexus 5 Android Development] Dark_Eyes_:
At the moment, I feel the device tree and kernel are pretty solid. Leaving them like that for the time being isn't a bad thing in itself, you should see how static the AOSP tree and kernel have become. I'll add the security updates when needed, and continue to build on those repos for as long as it's stable. Of course, I'll also update against the Lineage repos, but I think there won't be any development there since myfluxi isn't maintaining it anymore. All in all, I'll still build for it, and it will still be as good as it is now. We'll see how things evolve along the way.
[Nexus 5 Android Development] Chandu2105:
Its working now!! I have simply reset the network settings. And by the way I have the correct APN addresses I believe (as it worked in all the previous builds).

But there is one trivial issue though. I see LTE symbol on the status bar when wifi is OFF, whereas I don't see it (though it is switched on) on the status bar when wifi is ON. I can see the LTE symbol when wifi is ON in the collapsed quick tile settings though.
[Nexus 5 Android Development] Pshemo__:
That's normal, cause it indicates on what you're currently working
[Nexus 5 Android Development] MuhammadHesa:
NFC likes to turned off automatically and i used on trusted devices to unlock my phone. Please fix this

---------- Post added at 10:10 PM ---------- Previous post was at 09:54 PM ----------

NOTE: The NFC is turned on but I can't use it to unlock my phone, it recognise my card when the phone is unlocked but it won't when the phone is locked
[Nexus 5 Android Development] 4hp007:
Google assistant works perfectly for me without the enrollment bug. I know about this bug cause I had used the hack to enable it couple months ago but I kept getting the enrollment screen so I uninstalled it. After this update it seems to be working fine without any additional hacks.

ROM: Dark ROM AOSP 20170103

Kernel: ElementalX 7.09

Google app: 6.10.33.21.arm (beta tester ;) )

Default language: English (United States)

I had enabled hotword detection on my Google now prior to the update.

I didn't add anything extra to my system other than SuperSU and BusyBox after this update. Neither did I delete data or cache. Updated using opendelta.
[Nexus 5 Android Development] Dark_Eyes_:
I guess it's been fixed in the beta version... I'll try it out!

EDIT: yeah, it's fixed in the beta update. Everybody go to apk mirror, get the latest Google App beta and enjoy Google Assistant!
[Nexus 5 Android Development] Dark_Eyes_:
Sounds like a security feature to me, not a bug. If you ever lose your phone, nobody can use nfc while the phone is locked to buy stuff for example, which would be exactly the desired behavior... Can anybody confirm that?
[Nexus 5 Android Development] MuhammadHesa:
​

It's not like that, I mean the NFC tag to unlock phone feature is not worked after idling my phone for minutes, it only works once
[Nexus 5 Android Development] bravesoul349:
That's amazing :laugh:

When we will get the latest android version 7.1.1_r12
[Nexus 5 Android Development] MuhammadHesa:
By the way dev, keep the google assistant:) cause if you revert back the Google app the name changed to launcher3
[Nexus 5 Android Development] macci10:
Can you please tell me what configuration you used for EX? I have installed EX with some tweaks like overclocking and enable DT2W option and it bootloops.

I also enabled usb fastcharge option.
[Nexus 5 Android Development] GopalKaul:
[MENTION=3870481]Dark eyes[/MENTION] please can we get volte compatible ROM? I am flashing it now , after coming from Fake Nexus because the dudes there are too rude...
[Nexus 5 Android Development] MuhammadHesa:
False alarm....
[Nexus 5 Android Development] mc.cerny:
no, working...

Odesláno z mého Nexus 5 CAF pomocí Tapatalk
[Nexus 5 Android Development] Dark_Eyes_:
Never used that feature or heard of it. Can you explain a bit more? What can I do to reproduce?
[Nexus 5 Android Development] kozopulo:
[MENTION=3870481]Dark eyes[/MENTION], the new build of TrueSight kernel is up, would you implement it to the rom?
[Nexus 5 Android Development] MuhammadHesa:
Well it's smart lock feature from Google when you can add devices that can unlock yout phone when nearby, i add my nfc tag as mu trusted device so i can unlock my phone with it, but it only works once after the set up
[Nexus 5 Android Development] username1234321:
What do you mean by hotword enrollment? I am not getting anything like that.

Edit: I am using beta Google app.
[Nexus 5 Android Development] mc.cerny:
hi,

what is better? update via flashing zip or update via system updates?

Odesláno z mého Nexus 5 CAF pomocí Tapatalk
[Nexus 5 Android Development] 4hp007:
Are you using AOSP? Elementalx only supports AOSP base.
[Nexus 5 Android Development] macci10:
yes bro. That's why asked about it.

---------- Post added at 08:03 PM ---------- Previous post was at 07:57 PM ----------

The only difference is download size and flashing update by hand. For flashing zip you have to download whole rom again while system updates patches the previous build(if previous zip is already in Opendelta folder).
[Nexus 5 Android Development] Dark_Eyes_:
Humm, it's weird that it works sometimes, but not all the time. Get me some logs because I can't reproduce it myself (no NFC tags here).
[Nexus 5 Android Development] sghmk12:
on nexus 5 caf assistant is working perfect for me with no bugs. Keeping in mind I'm using google app beta
[Nexus 5 Android Development] MuhammadHesa:
How can I get the logs?
[Nexus 5 Android Development] Dark_Eyes_:
Search around for how to get logcats. Basically, what I need you to do is take a logcat of you trying to unlock the phone with your NFC tag when it fails. Hopefully, the reason why it'sfailing will appear in the log, so I know what's wrong and try to fix it. Other than that, there is no way I can know where to look or what is the problem.
[Nexus 5 Android Development] kozopulo:
[MENTION=3870481]Dark eyes[/MENTION], please update the kernel version, the fixed 4.3.1 is up: https://xdaforums.com/showpost.php?p=70379612&postcount=315

https://www.androidfilehost.com/?w=files&flid=129611
[Nexus 5 Android Development] alsheron:
So it looks like with the Google App beta version the Google assistant works (according to a couple of posts here). I've gone into the play store, gone to the Google app page scrolled to the bottom and enrolled in the beta program (easier than sideloading apk from apk mirror). I'll see if the assistant works now and report back. If it does, looks like maybe worth keeping recent changes relating to the assistant after all since Google will eventually push the Google app update to which fixes it to the main branch?
[Nexus 5 Android Development] Dark_Eyes_:
Yep, I'll keep the Google Assistant in the Rom, since it's working correctly now and it's a pixel feature.
[Nexus 5 Android Development] alsheron:
Thanks. Tested it and seems to be working quite well although it does seem to ask for enrollment a couple of times and the set up isn't as smooth as expected (could be to do with my attempts with previous non beta Google app) but it ends up working fine. Great stuff!
[Nexus 5 Android Development] focus-pocus:
I've got a weird problem with OpenDelta, when I'm on WiFi. It sometimes says "No internet connection" when I check updates, even though I have one. I have to disable and then enable WiFi to fix this problem. Sometimes it loses connection in the middle of download. It happened not only at home, but at work. No problems on LTE though. Any ideas?
[Nexus 5 Android Development] 4hp007:
Well I don't remember exactly but here it is.

Most of the settings were default except -

Sweep2lock left and right

Overclock 2496

Fast charge USB

Backlight dimmer

Disable max screen off frequency

I haven't set dt2w.
[Nexus 5 Android Development] Hugo9191:
Oh btw Dark, I'd like to request for a feature - DPI Changer (I'm sorry if there's already one in place, I haven't found it yet)
[Nexus 5 Android Development] Stevica Smederevac:
Display-display size i belive is the new way of changing DPI.
[Nexus 5 Android Development] tall0:
Confirmed

U just have to go into display section and change the size of if.
[Nexus 5 Android Development] Hugo9191:
Yeah, I found it, thanks!
[Nexus 5 Android Development] GopalKaul:
Can we port TrueSight kernel to non-caf ROMs?
[Nexus 5 Android Development] Dark_Eyes_:
Short answer: no. The device tree and blobs are too different. What you could do is ask the TrueSight dev to create an aosp version of his kernel. But, keep in mind that by design it can't be the same. CAF has some optimizations and patches that are not used in the aosp kernel, so you will never get the exact same experience on an aosp version.
[Nexus 5 Android Development] kamild_:
Anybody here with some experience in undervolting?

I was able to get the voltage to be 50 mV smaller, but quite often when I'm waking up my phone, it just reboots. I kept increasing back the voltage but it keeps doing that. There are no restarts when I'm using a stress testing app for like an hour. In fact, I also updated the ROM to the latest version right before I underclocked, maybe it could be the update that's actually causing it - if that's the case, I'll test it first.

Also could someone show me their CPU settings in Synapse? I used one of those aforementioned stress test apps and it messed with the CPU governor. But I feel like it changed something else too...
[Nexus 5 Android Development] treehugger38294:
The default Nexus 5 voltage is 800 mV on the lowest frequency. Check if you get reboots at the default voltages.

My device is poorly binned so I get reboots if I go below 785 mV.
[Nexus 5 Android Development] kamild_:
Yeah that's what I'm doing, I brought them back to default and now I'm going to check if it happens again.

I was using "CPU Global Voltage" to do the job. Looks like by default, the lowest frequency is running on 775 mV. No reboots on it. Or maybe I should leave the voltage on lower frequencies alone and only try to reduce the ones on higher freqs?