Quote: Originally Posted by lcrponte Originally Posted by Well... Wonder no more, as I said previously, AOSP has the most stable kernel. And CAF will "never" be as stable. Therefore, if you opt to flash the CAF flavour, you'll be acknowledging beforehand that you're opting for something that will have it's minor glitches here and there from time to time.

AOSP is more stable because unlike CAF it has nothing of current top devices, no AmbientDisplay, no energy saving features for gfx/video, no hardware based encryption, no offloading of more audio formats, not nearly as good audio experience, nothing. And it's more stable because there are entire very well paid, full-time teams at Google/LGE for it who had almost 3 years to make it run decent; not a free-time one-man-show like here. And if you are whining here or in the AOSP thread, you should always consider this or just gtfo.I'll focus on the watchdog stuff now. This is the worst to happen as debugging is hell, unless you're running a 3.10 kernel that allows for much better tracing.Current leathal bug list (CM/CAF/AOSP wide, so framwork stuff):* slight glitches in landscape mode (most likely HWC), no workaround* massive glitches e.g. in Catlog when slowly scrolling with HWC enabled, workaround is to tick gpu compositioning in developer options* screen occasionally stays on with Ambient Display enabled, I was finally able to track it down and repro at will, it's framework stuff as somebody on a OnePlus One confirmed. Start an app that keeps the screen on like youtube, play a vid, switch to recents, wait for the screen to switch off. It will flicker/switch on again and go off with the backlight remaining on. I put together a ghetto kernel patch until the root cause is being fixed. If you have a N5X, N6, N6P I'd be happy if you can test this.