yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] topgeardave:
Here's my review:

Your latest nightly is AMAZING! Sound quality is second to none and there's one thing you've managed to improve in the process, playing music is much less taxing on the cpu! Look at the screenshot here: 320kpbs streaming on Spotify and cpu is on 300mhz. Can't believe it! Previously it used to stay on at least 1.2ghz so battery life with music playback should be second to none. I can now safely set max screen off cpu to 652mhz with 1 core! Tomorrow I'll report on battery life but so far you have surpassed yourself! :)

Edit: People who use 652mhz screen off, turn off automatic play store updates. Sometimes phone takes a while to turn on when an app is updating in the background :)

Edit2: Bass response in the new kernel is mad, it blows away dsp manager as the software processing doesn't cut it. Bass boost just provides muddy bass so if you guys have a decent pair of cans or buds turn it off and just enjoy the power of raw hardware processing!
[Nexus 5 Original Android Development] sjknight413:
Wow, really that good? Might have to give it a shot :)

This is such an underrated kernel, I've been on cyanogens stock kernel a while as I just wanted it to be easier to update nightlies but I've definitely missed this a lot. Better sound quality seems as good a reason as any to come back!
[Nexus 5 Original Android Development] topgeardave:
I love stock cm kernel because of its battery friendliness. However one thing that put me off it was faux sound. Flash this kernel and set quality in nxtweaks or faux sound (which I use) and I set rnb in dsp manager. Sound is amazing! However I tested my stock HTC Sensation earphones but I didn't notice much of a difference. However on my Sony XBR1000 cans sound quality is world's apart compared to before. Make sure you have a decent pair of earphones or headphones and you'll notice a difference :)
[Nexus 5 Original Android Development] sjknight413:
I thought I recognised your name from somewhere! You're an ex sensation forum inhabitant aren't you? :) I just moved on from the sensation forums a few weeks ago after getting a nexus 5.

Yeah I've only just started getting to know fauxsound and it seems to be pretty great. I use viper4android so it will be interesting to see how these now sound updates affect it. I have a pair of decent Sony in ears that perform well with v4a so hopefully I'll notice the difference here too! Thanks for the review, good to hear other users opinions before flashing a new update :)
[Nexus 5 Original Android Development] topgeardave:
Indeed yes I am :) haha, Got a N5 shortly after launch and been following this kernel since its inception :)

I'd say back up your phone, uninstall v4a age try it. If you don't like it you can always restore the backup. From my experience v4a hits the battery too hard and the sound quality seems to be over processed for my liking. When using 320kpbs I don't think audio reconstruction is needed. I ain't an audiophile, not by a long shot. But I like my music to be clean and natural especially bass.

However if you want to use v4a go for it :)
[Nexus 5 Original Android Development] Dudebowski:
Any thoughts about using viper4android audio mod with this kernel? The optimizations are fantastic, unsure how they would compare yet and not sure how compatible they are together.

On a slightly different note, I've been having issues with my audio randomly and intermittently squelching/buzzing/ killing my ears and nerves for months now. Happens with stock CM, Franco's, and now this kernel, both with and without the viper mod. I've seen some comments here and there but nothing really useful about the fix. I assume it's just a problem with the Qualcomm drivers and noise on the line or something, but the sound is absolutely horrid.
[Nexus 5 Original Android Development] sjknight413:
I've just flashed the new nightly over my CM install with v4a and it all works together brilliantly :) the sound quality is brilliant! You can definitely notice the sound updates making a difference.

I had that buzzing happening with the elementalx kernel but it was solved by the latest update that fixed touchboost. The problem was something to do with CPU scaling as far as I know. If you underclock your CPU or mess with hotplug settings it will probably cause it but if you don't I don't see any reason why you should be experiencing it!
[Nexus 5 Original Android Development] topgeardave:
I've read about this on another thread, could you flash stock rom and play music? If you still get issues then it's a hardware issue with RMA being your only option. If not then we can help you debug it
[Nexus 5 Original Android Development] Dudebowski:
It just might be the UV... I tend to set it early on in my config routines just because I know this hardware can take a good 75 off across the board and still run fine, but that would certainly make sense that it's not getting enough juice to produce consistent analog output, especially when I'm passing it through the viper dsp (moderate cpu usage, right).

I'll give normal voltage a shot tomorrow for my commute (analog tape deck converter) and see how it goes, if it persists I'll run some tests on goo stock. Thanks for the team effort folks :)

Edit: I'm not sure my nx tweaks under volt is even enabled. I set the negative offset to the max, but didn't want to enable the"cpu voltage selector" toggle because the sanity check never matched the values shown in the custom toggles... more tomorrow, time to sleep.
[Nexus 5 Original Android Development] NYCguy2020:
For some reason I can't open NXTweaks on the latest nightly. I get a "Sorry, no kernel support!" message. I'm on AICP 4.0 and was running your previous nightly just fine. Any idea what's going on?? :confused:

Thanks!
[Nexus 5 Original Android Development] kong:
Try re-flashing the kernel.
[Nexus 5 Original Android Development] NYCguy2020:
Done that like 5 times already and still a no go. :(
[Nexus 5 Original Android Development] da900:
Maybe, there is a better solution to provide kernel and NXT app as separate downloads? personally, I prefer Trickster app to control CPU. And always have to delete NXT app from system/priv-app. Thanx.
[Nexus 5 Original Android Development] StrifeSoldierVII:
Awesome! Thanks for the time to respond. I figured something was up with the Sound controls in NXTweaks, and it's really great to know that both Faux sound and gamma apps are 100% working on your kernel. Looking forward to updates. :)
[Nexus 5 Original Android Development] neobuddy89:
There are many interfaces (few coming up) which ca be controlled only by NXTweaks.

Even if you delete NXTweaks from system/priv-app, default values are loaded on boot as it is scripted such way.

So doesn't matter if you keep or delete NXT.
[Nexus 5 Original Android Development] rg2:
Latest CM nightly (12.16) breaks battery stats/status, confirmed?
[Nexus 5 Original Android Development] Wombatino:
Confirmed

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] californiarailroader:
Which is why using nightly's is risky. ;)
[Nexus 5 Original Android Development] neobuddy89:
Breaks on CM Stock kernel too?
[Nexus 5 Original Android Development] mo976:
No just with custom kernel I can confirm that it was broken with chaos 5.1 and others reported it with franco (22?). My guess something in the changed show battery status interface or the battery dock commits is in conflict.
[Nexus 5 Original Android Development] neobuddy89:
Can you post screenshot please?
[Nexus 5 Original Android Development] mo976:
Of the problem or of the changed settings?

Anyhow it won't let me upload pictures from the xda app so here's a drop box folder https://www.dropbox.com/sh/cq6n9c7uhvr2v9s/6WHSxJAMuu

The first two pictures are with stock cm kernel hence the correct percentage in the circle battery icon.
[Nexus 5 Original Android Development] chenleicpp:
neobuddy89,where can I find NXTweaks app?I find every posts but cant find.btw，thanks for your hardword,your kernel very very good!
[Nexus 5 Original Android Development] californiarailroader:
It should have installed it when you flashed the kernel.
[Nexus 5 Original Android Development] chenleicpp:
thanks!
[Nexus 5 Original Android Development] californiarailroader:
No problem! Did you find it okay in your apps?
[Nexus 5 Original Android Development] gavin-phelan:
I get a unexpected error when i launch the app?
[Nexus 5 Original Android Development] neobuddy89:
Unexpected error is shown for fraction of seconds and disappear.

Is this error persistent for you? ROM name? Previous kernel? Busybox? SuperSu?
[Nexus 5 Original Android Development] mo976:
Correct It shows for a fraction of a second but doesn't seem to affect settings or functionality. I have only tried it with CM nightly's and no other previous kernel. Busybox and (CM included) Superuser.
[Nexus 5 Original Android Development] jordirpz:
For me too show for a fraction of second.

Stock rooted/busybox 4.4.2

vía Nexus 7 (2)
[Nexus 5 Original Android Development] ManOnTheMoon:
I tried flashing this on a cm11 based rom and it wouldn't boot. Can anyone shed some light please?
[Nexus 5 Original Android Development] Infinity02:
Try hard reset or wipe and flash.
[Nexus 5 Original Android Development] saramon:
Did you flash any other tweaks, I've had the issue before, and it was due to a tweak that probably broke bash? Not using aicp do I don't know for sure really
[Nexus 5 Original Android Development] neobuddy89:
Have you followed FAQ in post #4 ?
[Nexus 5 Original Android Development] neobuddy89:
ARCH_POWER removed as it was drawing more power when device was idle.

Hope your USB sound issue is resolved.

Thanks for the detailed review. All recent updates for codec driver are from msm-3.10.
[Nexus 5 Original Android Development] HiGhDRo3o5:
Am on latest pacrom dev build 07/16 and latest kernel from 07/16 doesnt flash. Keeps failing but the kernel from 07/11. Also had this issue on pacrom dev build 7/14
[Nexus 5 Original Android Development] fluther:
USB sound working like a dream, and everything else about this latest nightly is great too. Thanks!
[Nexus 5 Original Android Development] cetorr:
This last nightly update is amazing. The sound is finally at a level at which I expect the devices should come. You did it! :laugh:

I can recommend this to everyone, no fooling around with dsp or other extras. It just works!
[Nexus 5 Original Android Development] Unb0rn:
F2FS

Any news on F2FS support?
[Nexus 5 Original Android Development] fluther:
Question for everyone:

I use bootunlocker to lock/relock my bootloader while booted and without wiping. My normal routine is to unlock, reboot to recovery, flash cm, flash chaos, boot, relock. However, I forgot to unlock yesterday and didn't realise and just installed as normal. Both the rom and the kernel installed fine, and everything is working perfectly.

I was under the impression that kernel installation required an unlocked bootloader?
[Nexus 5 Original Android Development] dechronic:
It only needs to be unlocked if you are loading a kernel from the bootloader using fastboot. If you are just flashing it via a custom recovery it does not need to be unlocked. If you want the added security at the recovery level I would recommend using Philz Touch Recovery (cwm based) as you can set a password to enter the recovery if you wish.
[Nexus 5 Original Android Development] fluther:
Oh cool thanks. I use TWRP and I'm encrypted, so I need a password to do anything anyway.
[Nexus 5 Original Android Development] c_86:
Hello Dev

been a long time user of your kernel for my nexus 5

i wanted to let you know of some issues ive been having as of late with your nightlies...

I am running CM11, always the latest nightlies, same with your kernel, as soon as a new nightlie is posted, i download and load...

the late 2 builds have been a disaster for bluetooth... i use a galaxy gear 1 watch, and the last 2 nightlies have had constant connection issues... it will connect, and stay connected for about 10 mins, then disconnect, then 30 secs later reconnect, 2 mins later disconnect, and continues on that pattern.

Its not the watch, its not the app that the watch uses, its not the ROM.

I just rolled back to your nightly on the 10th, and its working again without any issues of disconnecting... been loaded for at least 45 mins now, and not a single disconnect...

can you take a look at this? or let me know how i can help... but either way, something is funky with the BT on your kernel as it stands right now...

thank you for your time, and let me know is there is anything else i can do
[Nexus 5 Original Android Development] NYCguy2020:
Yup that fixed it. Thanks a lot for your hard work.:good:
[Nexus 5 Original Android Development] Dudebowski:
So yeah the new driver and reverting the voltage offset seems to have solved the audio glitches! Much love to you developers that had been a thorn in my ear for such a long time!

Edit: viper mods seem to be at least part of the cause of the digital growl. I installed the driver for the ride home and it got really bad. I have the kernel's optimal sound setting enabled which is good enough for me, is stable, better than stock, and enjoyable.
[Nexus 5 Original Android Development] dechronic:
Chaos-Kernel_v13.0-[07-16]-[03-09] modified to support F2FS-ALL.

EDIT: Download link only had F2FS applied to /system originally. New download has f2fs applied to /system, /data & /cache

Download: http://d-h.st/twy

Chaos-Kernel_v13.0-[07-16]-[03-09] modified to support F2FS-DATA (/data only)

Download: http://d-h.st/llk
[Nexus 5 Original Android Development] topgeardave:
Hey guys thought I'd update you on the kernel after 24 hours. Battery life is amazing on this new kernel! Especially under watching videos on mxplayer with hw+. It can really comfortably play videos with 300mhz on one core. Also with regards to battery life after 1 and half hours of streaming a video on max brightness and volume I only lost 40% battery compared to 50% before!

I have also tweaked the kernel to be more battery friendly without sacrificing an ounce of perceptible performance.

I've changed input event boost frequency to 1267mhz and and sync freq to 1497mhz and disabled wakeup boost and hotplug boost as two cores are powerful enough. When there's extra load needed for things like gaming the kernel can ramp up the freq to max if needed :) I'd post screenshots but I've been rebooting the phone so it wouldn't be accurate to show it. However if you guys want a bit more battery life with max freq at 2.3ghz feel free to try out my settings :)

Edit: Here's a screenshot of my freqs today, half an hour of gaming is what accounts for the 2.3ghz step. Also some screenshots showing battery drain over the last few hours. The big decline is streaming a video via mxplayer on max brightness and volume for one and half hours under H+ which is battery intensive. Also I don't know why but when I rebooted and had that battery drop, it's not actually a battery drop, somehow the stats messed up and went back in time as I know I had an extra half an hour SOT when I checked it before rebooting :)

Edit 2: been using the phone for WhatsApp and YouTube videos and I've got 5hr10min SOT! I know it says 4hr40 but I was robbed half an hour when I rebooted the phone and had a supposed battery loss.
[Nexus 5 Original Android Development] bosna110:
I'm having trouble flashing the newest version of the kernel, keeps giving me a error message that the md5 is not same so I had to go back to cm stock kernel. Is this cm issue, chaos issue, or in this case my issue. Any help welcomed. Thanks a million to the kindest and most importantly the best supporting people
[Nexus 5 Original Android Development] JulianXhokaxhiu:
Probably is your connection or provider that is f*cking up the download :) Try to re-download again, from another PC, from your Smartphone directly and/or using a different connection.
[Nexus 5 Original Android Development] bosna110:
i downloaded it directly from my smartphone and had even Wifi on. it downloaded in 3 seconds sence I have a fast WiFi speed. This started happening within the last 3 weeks
[Nexus 5 Original Android Development] omvir:
Hi neobuddy, I've been experiencing a bug for a while with cyanogen hotplug. After a while with the cyanogen mod hot plug, the phone stops activating cores 1-3. So it basically becomes a single core. It happens randomly, there's no specific situation that activates this problem.
[Nexus 5 Original Android Development] topgeardave:
Update to the latest TWRP or Philz

---------- Post added at 06:25 PM ---------- Previous post was at 06:00 PM ----------

I think msm hotplug is more efficient now. Try using all stock settings with wakeup boost. This is what I've got today on 15% brightness:
[Nexus 5 Original Android Development] omvir:
I appreciate the suggestion, but I don't get nearly the same battery life as I do with the cm hotplug :(
[Nexus 5 Original Android Development] topgeardave:
Maybe it's because all this time it's been acting as a single core and thus resulting in big battery gains? Using system monitor pro, cm hotplug is much more aggressive than msm hotplug now as frequencies don't scale up as fast and race to idle is much quicker. All I'm saying is don't knock it till you try it :)
[Nexus 5 Original Android Development] omvir:
I forgot to say that battery was better on cm kernel (with cm hotplug). Yes you are right, it is more aggressive, but for some reason my battery life is always much better with it. (Maybe its because of the way I use my phone?). And I do love msm hot plug, used it all the time on aosp (code blue kernel) and did for a while when I switched to cm. But after giving cm hot plug a go, I just can't go back [emoji16][emoji16][emoji16].

Edit: I think I've found a temp solution until cm hot plug is fixed. Intelliplug set to 1 core boost, and conservative.
[Nexus 5 Original Android Development] topgeardave:
Btw you use stock frequencies right? There's no point underclocking on msm hotplug as it bottlenecks the phone. On stock frequencies freqs never go higher than 1.5ghz. As shown in this screenshot:

Also proof that msm hotplug races to idle better than cm hotplug, msm hotplug when I've opened Tapatalk and let it settle after a second:

And cm hotplug, as it's only one core the freq scaling seems to be higher as load is pushed to one core:
[Nexus 5 Original Android Development] omvir:
Yup stock frequencies. Yes it does race to idle much better, but as I said I have no idea why I am getting better battery life with the cm hot plug. Its odd...
[Nexus 5 Original Android Development] bosna110:
Stil having problems updating kernel and twrp
[Nexus 5 Original Android Development] topgeardave:
Latest version of TWRP?
[Nexus 5 Original Android Development] Dudebowski:
Sooooo... back to the audio glitch. I think it's a problem with cyanogen's flac decoder now. It seems that mp3 codec plays beautifully, but flac eats it hard. Would make sense that I've seen this problem cropping up across kernels with our without the viper mods installed. Thoughts? I think their codec perform is called stage fright, and I see a lot of continued development in that corridor of the git so...maybe it's a known issue and I'm late to the game.
[Nexus 5 Original Android Development] kong:
Waiting for Chaos with improved Interactive governor by myfluxi [emoji16]
[Nexus 5 Original Android Development] neobuddy89:
I already merged his changes hours back.

Will post in few minutes for review with you guys.

For me, I can see all frequencies are now hit since calculation technique is reverted to old one instead of load-basis.

Other than that, can't find difference in scrolling/performance. Placebo?
[Nexus 5 Original Android Development] myfluxi:
It's a whole new experience. Apollo album view, with/without, jumping freqs finally solved. And no more micro-lagging everywhere.

I tried your kernel as the first kernel besides CMs and mine and found all the glitches that are everywhere over CM/caf derivates like bt, camera mem and micro-lagging stuttering so it's obvious the problems are real and not magically solved by using a zillion upstream patches.

If you want to help to solve problems, revert pm patches until bt maybe works for you users.
[Nexus 5 Original Android Development] neobuddy89:
Reverting PM patches not that easy. It's deeply integrated. :(

With changes in bluesleep.c and serial drivers, bluetooth is much better than that of CM11.

Appreciate you efforts. Uploading now with your changes for interactive and changes for serial driver from msm-3.10.

EDIT: I haven't tested interactive governor changes with Apollo or any apps. Will really like to give this a spin!! Thank you.
[Nexus 5 Original Android Development] myfluxi:
These are actually not too many, give it a try. I don't use car bt and don't have funny bt gadgets but your users do. Involve them.

I built CM with caf hardware repos and see if certain changes make a difference with camera memory usage. Dunno, let's see.
[Nexus 5 Original Android Development] neobuddy89:
New nightly available:

Chaos-Kernel_v13.0-[07-19]-[12-22]

* Interactive governor changes by [MENTION=4152171]myfluxi[/MENTION] for microlag fix.

* Linux 3.4.99 update

* Improved efficiency of serial driver. Backported from msm-3.10. Please test and review bluetooth.

On personal note, I have noticed "Drowsy Bluetooth issue" is completely resolved!
[Nexus 5 Original Android Development] neobuddy89:
Yes, when I said bluetooth is much better than that of CM, it's tested by active user community here!

They reported here as well as over PM that issues like disconnection, memory corruption, and delayed detection are resolved.

I am not much aware about submitting patches to CM gerrit; however, you can try kernel posted above for BT or send same to your tester, if any. :)
[Nexus 5 Original Android Development] RKSoftware:
In last nightly NXTweaks: Sorry, no kernel support. What sould I do?
[Nexus 5 Original Android Development] neobuddy89:
Read FAQ Post #4
[Nexus 5 Original Android Development] RKSoftware:
Thanks a lot!
[Nexus 5 Original Android Development] myfluxi:
I tried with your actual kernel, a bt file transfer stopped. Unfortunately you disabled logcat so no debugging possible...
[Nexus 5 Original Android Development] neobuddy89:
You can enable logcat.

Open NXTweaks, scroll to Tweaks tab, Change Logger Control to "Enabled"
[Nexus 5 Original Android Development] fluther:
Myfluxi I know you're a well-respected member of the community, but your constant sniping at neobuddy and his hard work and your inability to say anything to him without being snide is really tiresome.

What's the deal? Is there some problem between you two?
[Nexus 5 Original Android Development] myfluxi:
It's all fine and I know he's a machine. I really, really wished he fixed/fixes bt, honestly.

Neo: http://pastebin.com/u8BC7Hb3