yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] myfluxi:
This might be related to our crappy, slow proximity sensor that already caused a bit of trouble. Learn to live with it :)
[Nexus 5 Original Android Development] rogers11:
No, it does not happen with other ROMs. It's a CM thing.
[Nexus 5 Original Android Development] myfluxi:
Then find out, what it is.
[Nexus 5 Original Android Development] rogers11:
If I could I would do it.

I've only asked if this bug is present also in CAF and mentioned that it is only in CM. That's all.
[Nexus 5 Original Android Development] ssauger:
I had this too some weeks ago. Then I turned off "prevent from wakup ..." under display settings and all was fine. Now some updates later, I turned on again without getting the issue back. Don't know what or if something changed. I use the CAF version. Thanks [MENTION=4152171]myfluxi[/MENTION] for the awesome ROM.

sent from Nexus5
[Nexus 5 Original Android Development] GiusGrec:
I tried another rom (no CM) and I had the same issue.

It is probably the proximity sensor, as already said myfluxi
[Nexus 5 Original Android Development] hikarugo:
Nah. It never happens in stock ROM. Perhaps the ROM you're using has a feature like CM which causes the bug.

This bug annoys me a lot because my power button is not working. The only way to turn on the display is to use the power button, which does not work. So I have to turn it off. But to turn it off, I can't hold the power button till it's off. I have to wait until the phone's battery is 0% or I have to disassemble the phone to disconnect the battery circuit immediately.
[Nexus 5 Original Android Development] myfluxi:
I should revert that stuff anyway as there is no valid use case for this any more on our device (without double tap to wake). The proximity check got removed from the power button some time ago...
[Nexus 5 Original Android Development] myfluxi:
Regarding fastcharge, I see no chance to detect USB3.0 via the otg charger interface - just in host mode. I'd need that to make it fool-froof. :/
[Nexus 5 Original Android Development] namerke:
It is so great to see that our beloved phone still getting so much love and attention from an actual developer (not a script kiddy).

Personally I was sticking with the factory images until now, but as our phone is going out of the official support timeline and N is around the corner I'm willing to experiment in the coming weeks.

Based on the commit history [MENTION=4152171]myfluxi[/MENTION] really put in a great effort to keep our device going strong , thank you for your hard work.
[Nexus 5 Original Android Development] _Vegas:
Same here.
[Nexus 5 Original Android Development] myfluxi:
Would somebody please send https://source.codeaurora.org/quic/.../?id=06e51489061e5473b4e2035c79dcf7c27a6f75a6 to gerrit? I'm on holidays and can only merge stuff.
[Nexus 5 Original Android Development] razorloves:
http://review.cyanogenmod.org/155662

thanks
[Nexus 5 Original Android Development] rogers11:
I'm running CAF from Sunday till now without having to press the Power button twice to switch the device on. :good:
[Nexus 5 Original Android Development] Piero88:
Hey! I'm about to get cyanogenmod back on my phone. Do you guys suggest using the snapshot or nightlies ? Pros/Cons ?
[Nexus 5 Original Android Development] mmo.xda:
Nice team work! It has been merged!!!

Thanks!!!
[Nexus 5 Original Android Development] der_daab:
I'm on todays nightly (11.08.) from nyyu.tk and the quadrooter scanner App (from PlayStore) gives me the error, that my device is still vulnerable to the ashmem vulnerability.

Does anyone have any insight as to whether the app is faulty (scareware?) or the patch didn't work (or did I misunderstand completely and the patch is for something different?)
[Nexus 5 Original Android Development] razorloves:
The "false positive" with cve-5340 that it's showing you is happening on all device that have been patched.

The app is most likely junk trying to sell junk.

I will trust the caf software engineers over that fishy app.

https://www.codeaurora.org/invalid-path-check-ashmem-memory-file-cve-2016-5340
[Nexus 5 Original Android Development] lcrponte:
[MENTION=4318223]der_daab[/MENTION] Get ZoneAlarm Protection.

It's a joke! <-
[Nexus 5 Original Android Development] Resset:
Hi there!

I have a problem with the latest nightly build from nyyu.tk. I have successfully flashed the hammerheadcaf version of TWRP on my Nexus 5, done factory reset and flashed the latest bootloader. Everything was going smooth with installation of the latest build (20160811) until the reboot. My nexus 5 didn't even boot up. Regular Hammerhead cm13 build works just fine. Boot loader and recovery work also fine.

What can be the issue?

I have the latest HHZ20h bootloader and 2.29 radio.

Regards
[Nexus 5 Original Android Development] fleischbanane:
Sorry, can't help you. No problems here so far with the latest build from 11.08.

But I did a clean flash because of some connection drops.

Btw: I like the new boot optimisation.
[Nexus 5 Original Android Development] djalfy:
About the new boot optimisation screen (wich i like very much) after dirty flashing the latest nightly over cm-13.0-20160802-UNOFFICIAL-hammerheadcaf.zip i've been stuck at that screen at the part with "updating contact databases" and the only way out of that screen was to clean flash the latest build. Just a heads up for those of you who want to update from an older build.
[Nexus 5 Original Android Development] xzr3b0rnzx:
i had no issue with the dirty flash, and yes, the new preparing boot screen look so much better haha
[Nexus 5 Original Android Development] otonvm:
Since build cm-13.0-20160812-UNOFFICIAL-hammerheadcaf I've been getting occasional random crashes.
[Nexus 5 Original Android Development] :
Does this actually work for anyone? https://review.cyanogenmod.org/#/c/151480

I'm using an up-to-date build and Nova Launcher but the animation is still slow. Am I missing something? Thanks in advance.

PS: The root-solution has always worked fine though.
[Nexus 5 Original Android Development] ssauger:
Tried it just now on Nova L and its very slow on my phone too.

sent from Nexus5
[Nexus 5 Original Android Development] Jeeza:
Hi! I found this little bug in the latest builds of both nonCAF and CAF...

http://xdaforums.com/showpost.php?p=68283583&postcount=1377

Let me know if I can provide further details that can help fix the problem!
[Nexus 5 Original Android Development] rogers11:
Good morning,

I'm running the builds from https://nyyu.tk/cm13/ for two weeks now (encrypted) without a single problem. Just want to say thanks. :good:
[Nexus 5 Original Android Development] ssauger:
+1

also use his builds and will thank him. He has sensor pick up enabeled cherry picked, which brings up my display in some situations and seems to drain my battery a bit more.

So i created a update surviving script that restores the default setting. I share it here. When you don't need it anymore once you flashed it, just delete in /system/addon.d/72-pickupfalse.sh and flash the ROM again.
[Nexus 5 Original Android Development] amnher:
Isn't that the ambient live display option? is it different if manually turned off?
[Nexus 5 Original Android Development] ssauger:
Yes it is a option for ambient display. If you turn it off completely it doesn't matter if the pickup sensor is enabled. I use ambient display and with enabled pickup sensor the screen goes on sometimes without a reason and in betterbatterystats i can see a significant higher wakelock for doze.

I think the reason for the enabled pickup sensor is that the display goes on faster when you pick the phone up, but i don't feel any difference.
[Nexus 5 Original Android Development] amnher:
So what happens if I run the script while ambient display is on?
[Nexus 5 Original Android Development] ssauger:
It will only set ro.qti.sensors.pick_up=false, which is the default at the moment for our phone. Ambient display will work with and without this option.

http://review.cyanogenmod.org/#/c/133386/
[Nexus 5 Original Android Development] Pelepako:
Sim Toolkit (stk.apk)

Hi, do you people have Sim Toolkit installed? I really need that for mobile identification but cannot find it. Also I don't know how to get it. The one I managed to install doesn't seem to work and it is not even showing up in app drawer...
[Nexus 5 Original Android Development] myfluxi:
Yes, enabling the pick-up sensor (not pick-up gesture) is tricky. It will speed up the slow reacting pick-up in many occasions (~300ms vs. 1000ms or more) but will lead to more unintended wake-ups.

While energy usagage is next to nothing I know that users will whine because all of a sudden "batteriez are sooo badz, plz fix, k thx!!!!!". So I hesitate to enable it in CMs tree (i enable it for myself, of course).
[Nexus 5 Original Android Development] myfluxi:
N changes appear to be reasonable, it already begun. I try to bring as many features as possible.
[Nexus 5 Original Android Development] amnher:
Yey here comes our hero ^_^ Chirayu Desai seems to be also busy with hammerhead
[Nexus 5 Original Android Development] myfluxi:
Everybody picks from current Nexi.

There may be something that takes a bit more work for our old device, looking at this since yesterday. Remember we got all the latest bells and whistles already and that should not change ;)
[Nexus 5 Original Android Development] elitewarrior:
Would additional help be an asset? What is the best way of getting involved in regards to developing for the N5?
[Nexus 5 Original Android Development] :
Is anyone here building on his own? For some reason I'm missing the settings under LiveDisplay where you could adjust saturation, contrast or gamma. Build from today. Anyone else? Thanks in advance.

Do the builds from nyyu.tk still provide these features?
[Nexus 5 Original Android Development] Green Daddy:
I just switched from a June build by Myfluxi to nyyu.tk from today using dirty flashing (no risk no fun ;) )

My livedisplay settings allow for

Screen Mode (4 settings)

Colour Temperature (Kelvin)

Screen Colour calibration (R, G, B)

So I guess it's the same as your's.
[Nexus 5 Original Android Development] morphvale:
I've been getting that for a few weeks now. It started after some commits from Steve regarding color control.
[Nexus 5 Original Android Development] amnher:
Has anyone encountered problem when switching APN? Wherein it does not switch not unless i delete the default apn?
[Nexus 5 Original Android Development] Allen_Walker:
[MENTION=4152171]myfluxi[/MENTION]

Hi Holy Knight. :o :highfive:

You can change kernel for working this terminal command?

iptables -t mangle -A POSTROUTING -j TTL --ttl-set 64

Target TTL not working :(
[Nexus 5 Original Android Development] amnher:
Oh no tyyu.tk is not anymore available. Anyone has nightly builds for caf?
[Nexus 5 Original Android Development] ssauger:
https://nyyu.tk/cm13/ still there. not tyyu.tk
[Nexus 5 Original Android Development] :
nyyu.tk/cm13

EDIT: Too late :D
[Nexus 5 Original Android Development] swapnildixit3:
Hey Our Nexus SuperHero [MENTION=4152171]myfluxi[/MENTION],

Are you working on CM 14 for our be loved Nexus 5 CAF?
[Nexus 5 Original Android Development] myfluxi:
There is not even a QCOM source drop, let alone a full cm-14.0 branch, I would only be wasting my time. I watch what is going on, people running here and there, doing things. Every second commit title is "hax", "DNM" or "workaround". Some early builds pop up, you would not want to use them, these are not CM as you know it (as always with every new Android version).

We need like 20 commits to compile and run N, the rest just takes time which I do not plan to waste for anyone's curiosity.
[Nexus 5 Original Android Development] Fihlvein:
Regarding the ability to change the display to produce more vivid color output (cannot remember the exact option names) being gone - is it something that is a result of some core CM changes (somebody mentioned Steve pushing some stuff regarding color controls) that just broke this feature from our CAF? In other words, is there hope of getting that lovely stuff back? The colors are so washed out compared the beauty in the past.

And also thanks for the status update for how CM14 is progressing!
[Nexus 5 Original Android Development] samsyr:
There is problem with Google tts it failed to install language packages.. It worked normally in non caf build any solution..
[Nexus 5 Original Android Development] namerke:
Dear [MENTION=4152171]myfluxi[/MENTION]

Would you please be so kind and elaborate on these lines to enlighten a fellow member?

Just out of curiosity,I'm not pushing for a build here or anything: for example you are mentioning QCOM source drop.

I tought we already have all of our blobs updated to a very recent version and this will be an advantage for us. Am I confusing this with something else?

Also, "need like 20 commits to compile and run N, the rest just takes time". By "the rest" you mean all the cm specific features ?

I, personally in love with your kernel ever since I've started using it, therefore I would love to use it even with a plain old AOSP-like ROM.

If someone can point out the commits I would even build it for myself.

Anyway, thanks for your continuous support, it's highly appreciated.
[Nexus 5 Original Android Development] myfluxi:
If I answered your question in a way that you'd be able to use it to build your N-dream, I would have already wasted my time which I refused to do earlier ;)

Watch gerrit, it's all there already. I didn't even sync cm-14.0.
[Nexus 5 Original Android Development] namerke:
Fair enough :o . Although I still find the QCOM part interesting.

Anyway, thanks again for all your efforts.

Cheers :good:
[Nexus 5 Original Android Development] h31:
Hi, myfluxi!

Thank you very much for your awesome work on Hammerhead CAF!

Looks like CIFS support is not currently enabled in the kernel. Can you fix it?

I think it will be enough to enable these options:

CONFIG_CIFS=y
CONFIG_CIFS_POSIX=y
CONFIG_CIFS_STATS=y
CONFIG_CIFS_ACL=y

I think NFS support will be also useful, but I don't certainly know if the following set of options enabled will be enough:

CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_COMMON=y
CONFIG_NFS_USE_KERNEL_DNS=y

UP: Looks like CIFS support is enabled in cm-13.0 branch, so you can just grab values from it's config. Personally I haven't tried cm-13.0 branch, but it mentions CIFS in cyanogenmod_hammerhead_defconfig. NFS support is not enabled in both branches, but still may be useful for some users.
[Nexus 5 Original Android Development] neobuddy89:
I was here for CAF build of CM13, got it. Thanks!

Update on CM14:

Many hax have been removed/abandoned (except one for sound trigger) :)

RIL is big issue on CM14 since framework_opt_telephony and related projects are CAF iteration and not AOSP.
[Nexus 5 Original Android Development] santi1993:
G2 is having a AOSP CAF CM14, maybe can we cherry pick?
[Nexus 5 Original Android Development] spaniard:
It looks like Qualcomm will not release graphics drivers for 800/801 CPUs, so no big hopes...

http://www.androidauthority.com/android-7-0-snapdragon-800-801-712930/
[Nexus 5 Original Android Development] santi1993:
Kang vulcan, save 8974
[Nexus 5 Original Android Development] eternal70:
Of course there's still hopes. Our last official build is MM. We're not far behind. Even galaxy nexus is still getting nougat
[Nexus 5 Original Android Development] spaniard:
I mean just for CAF :)
[Nexus 5 Original Android Development] santi1993:
Lg g2 is having a aosp-caf cm14 rom...
[Nexus 5 Original Android Development] razorloves:
geezus dude... nobody gives a flying f what the g2 has.

we got myfluxi :p

he will deliver unto us some delicious nougat when it's good and ready.

http://xdaforums.com/showpost.php?p=68542151&postcount=1864
[Nexus 5 Original Android Development] santi1993:
dont we share features?
[Nexus 5 Original Android Development] sunanulh:
Is there any step that should I do before installing this rom if I came from non-CAF rom?

Or I just have to flash hammerheadcaf twrp?

Thanks
[Nexus 5 Original Android Development] G3Denver:
Yes. Also, you can wipe /system, if you want.
[Nexus 5 Original Android Development] sunanulh:
Thanks mate. I really miss all cm features and I want to go to caf.
[Nexus 5 Original Android Development] somadsul:
How you solved this I am also getting error for this
[Nexus 5 Original Android Development] Jaizu:
Thanks for the ROM, working good. However I have 2 questions.

Is CM updater working in the CAF builds?

Can you merge the spanish translation? Is completed but cm mods(in Crowdin) have months without approving it, can you merge them or tell me how to install them? Spanish translation here: https://crowdin.com/project/cyanogenmod/es-ES
[Nexus 5 Original Android Development] spaniard:
First question, no

Second, It`s already translated to spanish, this is CM13 for HammerheadCAF
[Nexus 5 Original Android Development] Jaizu:
Thanks for the support, translation problems got fixed rebooting the phone lol
[Nexus 5 Original Android Development] Jaizu:
Where can I see the changelogs?
[Nexus 5 Original Android Development] :
review.cyanogenmod.org
[Nexus 5 Original Android Development] frauhottelmann:
Is the Caf version still a lot better than the normal one? Is it up to date concerning security patches? Thanks in advance...
[Nexus 5 Original Android Development] RoarAbelson:
Changelog for 26-Sep-2016 build?
[Nexus 5 Original Android Development] simplicio11:
No changes from CM in the last 2 days ;)
[Nexus 5 Original Android Development] RoarAbelson:
Okay, thanks. I was just curious why there is 25, 26-Sep builds if there is no any change. :)
[Nexus 5 Original Android Development] myfluxi:
I updated cm-14.0 branches on my git, if anyone is interested. This might even build and run - I didn't check either.

Edit: Both cm-13.0-caf and cm-14.0-caf received a security patchbomb as well, I'll update cm's repos soon.
[Nexus 5 Original Android Development] simplicio11:
[MENTION=4152171]myfluxi[/MENTION] = Nexus 5's legend [emoji16]
[Nexus 5 Original Android Development] namerke:
And here i am, stuck on a windows laptop without admin priv.

Seriously have to dig a box with linux on it from somewhere.

Been waiting for these news since nougat source drop , thank you for your effort [MENTION=4152171]myfluxi[/MENTION] , my fingers are crossed for someone to have the ability and the will to compile it.

Rock on N5
[Nexus 5 Original Android Development] myfluxi:
QCOM did not release final sources yet, apparently everybody waits for 7.1. CM people including Kondik already did a great job with what's available.

CM will not be decently usable until December or so, this is how it is.
[Nexus 5 Original Android Development] phoval:
I made a build from myfluxi cm14 sources, available on https://nyyu.tk/cm/, I have not tested it.

Errors fixed during the build:

device/lge/hammerheadcaf/overlay/frameworks/base/core/res/res/values/config.xml:352: error: Resource at config_ui_blur_enabled appears in overlay but not in the base package; use <add-resource> to add.
=> repopick 161304

device/lge/hammerheadcaf/cmhw/org/cyanogenmod/hardware/DisplayColorCalibration.java:19: error: package org.cyanogenmod.hardware.util does not exist
import org.cyanogenmod.hardware.util.FileUtils;
=> modify import to org.cyanogenmod.internal.util.FileUtils;

In file included from device/lge/hammerheadcaf/recovery/recovery_updater.c:28:
bootable/recovery/edify/expr.h:46:5: error: must use 'enum' tag to refer to type 'ErrorCode'
=> recovery_updater.c rename to .cpp and modify Android.mk

device/lge/hammerheadcaf/recovery/recovery_updater.cpp:171:9: error: use of undeclared identifier 'uiPrintf'
=> add #include "updater/install.h"
[Nexus 5 Original Android Development] simplicio11:
[MENTION=2833355]phoval[/MENTION] thanks for your builds, I use them since months. Thanks for keep CAF alive on N5... Now CM 14 [emoji322] [emoji322] [emoji322]
[Nexus 5 Original Android Development] jerunk:
Thanks for everything you're doing and have already done with the Nexus 5, really great work and we all appreciate it.
[Nexus 5 Original Android Development] mkoev:
[MENTION=2833355]phoval[/MENTION] thank you for providing the ROM. It boots fine, there are a couple of force closes at the beginning, bluetooth and camera don't work. It's extremely snappy! :) I did not test telephony coz it's 1:00 AM here :D I will be happy to test the builds if you keep on building them. I've been using your CM 13 CAF builds and I am very happy with them!
[Nexus 5 Original Android Development] 7drlclk:
ummm.. very dumb question, I can't find the link to download the latest build (24 Sep). I can only find the 4 Aug Build on Google Drive.

got it! it's on https://nyyu.tk/cm/ Thanks!
[Nexus 5 Original Android Development] mmo.xda:
Your effort is commendable.

You deserve the best

Thank you for your dedication and time.

Thank you very much

Best regards
[Nexus 5 Original Android Development] myfluxi:
[MENTION=2833355]phoval[/MENTION]: Add http://review.cyanogenmod.org/#/c/158551/ and set the flag in BoardConfig, this will likely fix the camera.
[Nexus 5 Original Android Development] phoval:
Made new build, camera and bluetooth should be fixed : https://nyyu.tk/jenkins/job/cm14_hammerheadcaf/8/

[MENTION=4152171]myfluxi[/MENTION], I forked your repo and committed the changes.
[Nexus 5 Original Android Development] nexzor:
[MENTION=4145479]experience7[/MENTION] could you please create a CM14 CAF Thread and tell the mods to copy the last posts over there. it could be realy confusing the way it is now.
[Nexus 5 Original Android Development] mkoev:
Camera does not work on build from 28th.Maybe you should create a CM 14 thread coz we are totally spamming this one :)
[Nexus 5 Original Android Development] :
They are already open! For now they are in the general section but will be moved to Original Development soon. Use the links at the end of this threads opening post :)

Much fun discussing about CM14! :P
[Nexus 5 Original Android Development] RoarAbelson:
Is the HH cm14 CAF going to be official? I'm really exited about this that my socks are spinning !
[Nexus 5 Original Android Development] xzr3b0rnzx:
[MENTION=2833355]phoval[/MENTION] I am on your 28 sept cm 14 build can i dirty flash your cm14 latest build just like on cm13?

will it messed up the app data and permission if i dirty flash, can anyone verify this? i really dont want to go thru another full wipe.
[Nexus 5 Original Android Development] morphvale:
Just take a full backup before you flash, and restore it if anything goes wrong..
[Nexus 5 Original Android Development] santi1993:
Can i dual boot this rom with an AOSP one?

Enviado desde mi MS-82fx [MENTION=1401799]CM13[/MENTION] mediante Tapatalk
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Yes you can, just make sure that you first have TwrpCaf installed in order to flash the Caf version of CM. After you have flashed the Caf version of CM you have to install the multiROM recovery and move CM Caf (which is your primary ROM at that moment) to secondary ROMs. Now you can just flash the "Normal" version of CM as your primary ROM and after that you have to flash a kernel with the kexec-hardboot patch to be able to dual boot between them. Thats it. :good:
[Nexus 5 Original Android Development] santi1993:
So many thanks!

Enviado desde mi MS-82fx [MENTION=1401799]CM13[/MENTION] mediante Tapatalk