yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] neobuddy89:
Chaos 15.0 now available here:

https://www.mediafire.com/folder/077pf1da5u0br/Chaos_15.0

There are two variants - one for "myfluxi"'s builds and other for official CM11 nightlies.

New 15.0 builds available:

* Reduced i2c freq

* SELinux updates

* Minor performance updates from upstream.

* Fix messed up stock thermal engine service

* Highly improved Synapse user interface. Special thanks to @Apbaxel. His source is bible of implementation ideas; his most controls already cover up interfaces developed by Chaos and Dorimanx kernels. However, there are couple of broken controls which are fixed by me with better grouping and eye-candy UI.

Current to-do list:

* Add fast charge and its controls.

* Try Kernel-space thermal engine with controls exposed in Synapse.

* Build and upload new toolchain.

Have a nice day!

(OT: Did Antutu benchmark just for app popularity sake... and for first time crossed 37k for me..)
[Nexus 5 Original Android Development] Audioboxer:
And back from AOSP to CM I go :) The thermal issues were what needed fixed for me and they should be now.
[Nexus 5 Original Android Development] joecool666:
thank's man going to try both of them lol, kind regard's joe
[Nexus 5 Original Android Development] Audioboxer:
Synapse is force closing when I try to choose a gamma profile.

On myfluxi build.
[Nexus 5 Original Android Development] topgeardave:
Heads up [MENTION=3795148]neobuddy89[/MENTION], a whole shed load of audio updates are added to cm hammerhead kernel :)
[Nexus 5 Original Android Development] rg2:
I am running the latest CM nightly and I am not able to charge my phone when any of the Chaos kernals are flashed; when I flash back to stock CM it charges fine. Never had this issue before. Any help is appreciated.
[Nexus 5 Original Android Development] neobuddy89:
I think most of them are already part of both 14.0 and 15.0.

Anyaways, here is updated toolchain used for Chaos:

https://www.mediafire.com/folder/tkpa3pjrfanp5/Toolchains
[Nexus 5 Original Android Development] neobuddy89:
Which version of Chaos?

What charger are you using?

Are you using multirom?

Can you please share kernel log? (dmesg)
[Nexus 5 Original Android Development] lolobarjo:
I think V.15 is not compatible with F2FS.

In V.14 i replace this line :

/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=continue wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/metadata

by this line :

/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,flush_merge,errors=recover wait,nonremovable,encryptable=/dev/block/platform/msm_sdcc.1/by-name/metadata

And it work but not for V.15. I have also try "Nexus 5 F2FS tool : http://xdaforums.com/google-nexus-5/development/nexus-5-f2fs-tools-t2801977" and it don't work either
[Nexus 5 Original Android Development] neobuddy89:
If you are ready to make said changes and test... I am willing to import f2fs from Chaos 14.0 instead other gits.
[Nexus 5 Original Android Development] lolobarjo:
Sorry I don't understand your first sentence, my English is bad ^^

Envoyé de mon Nexus 5
[Nexus 5 Original Android Development] Unb0rn:
Yes, please do it. I can edit fstab.hammerhead and test it. Maybe it's a good idea to switch to anykernel format to modify ramdisk on install, according to partition filesystems?

P.S. I don't want to appear impolite, but are there any news on Diag mode on any (v14/v15) version? ;)
[Nexus 5 Original Android Development] lolobarjo:
I think i have read somewhere is it possible to make the kernel check the format of the partition and mount it properly. I will try to find where i have seen this

Envoyé de mon Nexus 5
[Nexus 5 Original Android Development] fluther:
Just had a nasty crash and bootloop on latest 15 neo.

Went into synapse, applied yorici, cycled the display, and straightaway it booted me to the bootlogo, and it wouldn't go any further.

No logs, sorry.

Will try again now and see what happens.

Edit: This time before changing anything I went into tools and tried relaunching synapse. Instant reboot. Kmsg: https://www.dropbox.com/s/iorhjf9xucoj578/chaos-last_kmsg-2014-09-13.17.27.36.txt?dl=0
[Nexus 5 Original Android Development] neobuddy89:
Which 15.0 are you?
[Nexus 5 Original Android Development] fluther:
Official cm
[Nexus 5 Original Android Development] neobuddy89:
Only note I can make is thermal reaching its threshold followed by hw_reset.
[Nexus 5 Original Android Development] fluther:
Funny you should say that, because this thing is running *hot*. Seems to stay around 50° with just basic usage.
[Nexus 5 Original Android Development] fluther:
Here
[Nexus 5 Original Android Development] neobuddy89:
Ahh.. I was thinking to post a build without thermal update for now..

Will work on this now... we definitely need kernel-space thermal driver.
[Nexus 5 Original Android Development] zimlokks:
Yeah overheating is a problem with v15,i work inside an industrial size freezer temperatures in there are usually 10-25° F needless to say that chaos v14 used to let the temps go down to 40-50° F, now with v15 it runs around 60-70° F without much usage inside the freezer. The attachment is just me typing this post it went from 80° F to 101° F
[Nexus 5 Original Android Development] Audioboxer:
Do you ever sleep? :p
[Nexus 5 Original Android Development] topgeardave:
There has to be a reason why it's getting so hot? Voltage regulator maybe an issue?
[Nexus 5 Original Android Development] Audioboxer:
Are you running on myfluxi's latest or still the nightlies? Myfluxi said he sorted thermal issues in his latest build.
[Nexus 5 Original Android Development] fluther:
Is the current build safe or should we downgrade to 14 till it's fixed?
[Nexus 5 Original Android Development] topgeardave:
Official cm mate, battery life is better with chaos v14 3/9 nightly. 9/9 v14 is too unstable for me, keeps freezing and pretty much unusable on my phone.

From the cm thread, people have mentioned battery temps are still high even though it's not at 48 degrees levels. More like 40 degrees idle temp compared to 36 normal temp on official cm

And neobuddy89 could you take the Base or 3/9 kernel and patch in the latest sound commits from cm kernel. I can't use 15.0 just because the battery is too hot when idle.
[Nexus 5 Original Android Development] neobuddy89:
Meh.. here we go..

https://www.mediafire.com/folder/077pf1da5u0br/Chaos_15.0

New build available:

* Add and activate by default new thermal driver. Controls added to Synapse.

* UI improvements and new interfaces for Synapse.

* Add USB fast charge.

* Audio driver updates

* Misc updates from 3.4.y linux.

Audio is better than ever... tested on CAF CM11.. will test with official CM11 in sometime.

Side note:

Some stress testing resulted in gpu ion panic. I was messing up busybox, mounting/unmounting partitions, scrolling my files.. and boom the gpu ion panicked.

I thought driver was messed by me, but when checked it was untouched - nothing updated with GPU ion driver.

So, that calls for next in to-do list.

To-do:

* Bring mem allocation of 15.0 upto 14.0 level. (This includes GPU ion mainstream updates as well)
[Nexus 5 Original Android Development] mo976:
I just flashed the latest cm official chaos 15 dated 14-9. I flashed while on the charger, battery was at 115°f CPU was about the same perhaps its a reporting error in synapse? The second more worrying thing the phone was fully charged but it was discharging 100% 99% 98% despite showing that its charging...

Edit I'm on latest cm nightly 13-9.
[Nexus 5 Original Android Development] Audioboxer:
I'm going to try going back to official and trying the new kernel Neo just posted below. Issue with CM is I need Bluetooth to work in my car. Will test it again. Only ever worked on myfluxi build....
[Nexus 5 Original Android Development] lolobarjo:
This build work good with F2FS :D

Envoyé de mon Nexus 5
[Nexus 5 Original Android Development] Audioboxer:
By the way [MENTION=3795148]neobuddy89[/MENTION] I think faux updated his sound drivers :laugh:

---------- Post added 14th September 2014 at 12:35 AM ---------- Previous post was 13th September 2014 at 11:39 PM ----------

Hey [MENTION=1240571]neobudy[/MENTION]89 any idea what myfluxi means with fancy audio kernel? http://xdaforums.com/showthread.php?p=55432163
[Nexus 5 Original Android Development] Circaflex:
Most likely this from Steve http://review.cyanogenmod.org/#/c/72905/
[Nexus 5 Original Android Development] mo976:
Try it out sound quality even on stock cm kernel is much much better. Its like the quality setting on chaos.
[Nexus 5 Original Android Development] Audioboxer:
That's not kernel based right, meaning neobuddy shouldn't need to integrate it?
[Nexus 5 Original Android Development] neobuddy89:
We do define our own audio policy since CM11 had stopped updating it;

However, all latest updates are merged in last version.
[Nexus 5 Original Android Development] fluther:
Crashes while rendering HDR+ photos: https://www.dropbox.com/s/tpy4cojuv8a1p18/chaos-last_kmsg-2014-09-14.14.24.05.txt?dl=0
[Nexus 5 Original Android Development] Audioboxer:
Do you still think the Dalvik/Bionic helps? I've noticed on CM gerrit they've been tweaking their own dalvik recently.

I've been trying the new CAF combo one (1+1/Z3)
[Nexus 5 Original Android Development] topgeardave:
Personally in terms of real life I find them both equally as snappy now, I don't use dalvik/Bionic patches anymore because I feel they make no difference except in benchmark scores.

Is there any chance you could patch the sound updates to the 3/9 v14 nightly? I'm still using that nightly as it's the most stable one for my phone with official cm.
[Nexus 5 Original Android Development] Audioboxer:
What issues are you having with - http://xdaforums.com/showpost.php?p=55430120&postcount=3832

I just went back to official nightlies. PM'ing myfluxi to keep in touch, but I'll try nightlies for a while and see if BT can remain stable in my car. The higher temps aren't ideal.
[Nexus 5 Original Android Development] topgeardave:
Battery temp is the main one, as a chemical engineer battery temps are crucial to the health of the cells. Prolonged exposure to higher temps increases cell degradation. Stock temps should be 36/37 degree mark (human temps). Even though temps have decreased from 48 to 44 degrees whilst idle its still too high.

Another gripe with v15 on official cm is that the vibration strength is much lower on stock even though they're both on 63.

And finally battery life isn't as good as v14.

I don't want to sound like I'm having a moan but I'm just stating why v14 3/9 is more stable than v15. But I have to say that v14 9/9 nightly is very unstable. Phone is more laggy and constant freezes where apps end up FC'ing
[Nexus 5 Original Android Development] Audioboxer:
Strange as I would have thought the thermal issues would just have been linked to myfluxi's CAF builds. Unless neobuddy89 tried to backport his changes to the official nightlies. We'll see.

I'm going to stick on stock kernel till we hear from our CM kernel god neobuddy.
[Nexus 5 Original Android Development] topgeardave:
It's the kernel mate, I'll just attach a photo of temps on 3/9, v15, and 3/9 kernels so you'll see the huge difference in battery temps on official cm in one graph
[Nexus 5 Original Android Development] Audioboxer:
Shame that, let's see what neo can do. I don't want to lose out on these new sound updates Steve committed, so I don't want to drop back to v14.
[Nexus 5 Original Android Development] topgeardave:
That's why I want the sound updates on v14 because that would be perfection. And here's a screenshot, v14, v15, v14. Battery temp shoots up
[Nexus 5 Original Android Development] Circaflex:
this was one of his comments
[Nexus 5 Original Android Development] neobuddy89:
Chaos had all those merges long back.

Reviving 14.0.
[Nexus 5 Original Android Development] Audioboxer:
Unfortunately, notification sound corruption is back on the latest nightly, maybe do to with those commits?

It was in CM a few months back and then was fixed. It's when the notification sort of skips at the start of it playing. Happens fairly rarely.
[Nexus 5 Original Android Development] fluther:
My sound was completely effed on latest 15, unlistenable. I've reverted to stock for now.

Also I love your avatar. Saor Alba!
[Nexus 5 Original Android Development] nick123ablxx32:
could someone please explain to me why everyone hates v15? ...seems pretty stable to me no problems,lag or overheating apart from sound jumping wildly when using the latest nightlies :confused:
[Nexus 5 Original Android Development] neobuddy89:
@all:

Sound is confirmed issue with latest nightlies of Chaos and CM11.

Seems like some calculation derp (due to changes in device tree) by NXTweaks/Synapse.

Only one way I can make sound sane, currently, is using Synapse on v15.0 and changing profile to LG Stock. (workaround; sliders will reset -- do not click on tick again)

Nevertheless, will resolve this madness today.

Even for me 15.0 seems all-good. Even thermal working as expected.

Temp limit of MSM SOC is 110 c. Limits we set for throttling is around 76 c. (In new thermal of 15.0)

Ofcourse, you can lower this to 65 c (or even less) before posting thermal is buggy. No, it's not... for us userspace thermal didn't work as expected but kernel-space thermal driver is different story.

Memory updates on 15.0 is complete. Will sync up camera updates with myfluxi build just to be on safer side (camera working good for me though; no restarts/reboots) All 3 builds (14.0, 15.0, 15.0 CAF) will be available tonight (IST) once sound is fixed to sane state in kernel.

Meanwhile you may switch to stock OR use above workaround to combat sound issue.

Also, NXTweaks will MAY get removed and ramdisk will be injected with Synapse backend(unifying ramdisk for all versions.)
[Nexus 5 Original Android Development] saramon:
It's not a hate, it's that I'm limited to one rom I can use, and stock CM requires a lot of xposed to pull off things baked into other roms
[Nexus 5 Original Android Development] topgeardave:
Download trickstermod and check your battery temps, for me 44-47 degrees idle temp is too dangerous :(
[Nexus 5 Original Android Development] nick123ablxx32:
I'm currently at 42.4° it does ramp up from time to time :good:

Thanks for the info :)
[Nexus 5 Original Android Development] kong:
There's also battery temp in the first tab of Synapse ;)
[Nexus 5 Original Android Development] neobuddy89:
Need to check idle temp of Chaos 14.0 with synapse....
[Nexus 5 Original Android Development] neobuddy89:
yes, Chaos 14.0 shows lower idle battery temp.. 34 ~ 35 c while its 42 c on Chaos 15.0

But CPU temp is same 44 c.
[Nexus 5 Original Android Development] salonluden:
Is someone here running crDroid. I can't manage to get it to boot with 13.2 or 14....

Any ideas
[Nexus 5 Original Android Development] topgeardave:
Last I heard was that it went aosp? Flash an aosp kernel and see if it boots
[Nexus 5 Original Android Development] salonluden:
You think? The title still says CAF and on all updates it says merge with newest CM sources.

I don't think so and I'm not so much in the mood to work on it now - I'll check it out tomorrow.

Lets hope it works!
[Nexus 5 Original Android Development] neobuddy89:
New 14.0 nightly available on Mediafire mirror!!

Chaos-Kernel_v14.0-[09-16]-[00-22]

* Rebased on Chaos 09/03 nightly

* Fixed high power drain due to i2c suspend failure.

* NXTweaks Removed! T_T

* Added Synapse interface support. Install Synapse app from store!!

* F2FS updates

* Sound control driver updates to fix compatibility with new sound updates of CM11.

* Misc updates!

Let me know if any imp feature is missed to port from NXTweaks to Synapse.

Chaos 15.0 --- temperature issue still persists. Even with driver from Chaos 14.0, battery temp remains 44 c at idle.

Perhaps current draw is high? Will check later.
[Nexus 5 Original Android Development] lolobarjo:
I don't see the these features in synapse (V15) :

-Vivid color screen

-Strength vibrator

-Mode for intelliplug

I will see in V14

Envoyé de mon Nexus 5
[Nexus 5 Original Android Development] _MirageX_:
am I the only one who isn't able to reproduce video on latest v15 nightly?
[Nexus 5 Original Android Development] fluther:
My CPU seems always to reset to 1036ghz max. Any ideas?

Further investigation: something to do with the thermal engine. I can go above the sticky limit (which now varies, but always around 1036ghz) if I disable msm thermal, but it won't let me enable Qualcomm thermal.
[Nexus 5 Original Android Development] Unb0rn:
neobuddy, I am really sorry for being so annoying, but I really want to know, is there a point in waiting working diag mode in your kernel?
[Nexus 5 Original Android Development] topgeardave:
Works fine here with synapse :) No issues to be reported as I have no lockups or freezes. Battery life is fine also and battery temps are normal at 36 degrees as reported by synapse :)

I changed frequency throttle temp to 60 degrees as I hardly game and I don't think I've been throttled in the two hours of flashing this kernel :) You could get set 2.3ghz in performance settings in cm settings and set it as boot. Should stop the throttle from getting stuck if that's the case :)
[Nexus 5 Original Android Development] neobuddy89:
New nightly** available (Only UI updates)

Chaos-Kernel_v14.0-[09-16]-[07-39]

* Add vibrator strength control to Synapse

* Add Intelliplug full mode profile control to Synapse

* Add vivid color tweak control to Synapse

* Remove stock thermal option from thermal control of Synapse (will check later why it's not switching on; kernel space thermal driver is working fine.)

About diag mode, I am still searching on that.... Will try to update next nightly of 14.0.

@fluther: Use MSM limiter driver. If MSM limiter driver is not enabled, Synapse can't control max freq.

Also clean install your ROM once.

Anyone willing to translate Synapse UI to their language, let me know. We can do this now!

**Do not use above nightly with CAF build releases.
[Nexus 5 Original Android Development] kong:
Currently on v14. Not sure if a sound slider is missing or not :|
[Nexus 5 Original Android Development] neobuddy89:
PowerAmp gain is removed.

It's now dynamically changed by system.

https://github.com/neobuddy89/hammerhead_kernel_caf/commit/6fb6f45eb503ff28c34aa5480f901d80fd4d58a3
[Nexus 5 Original Android Development] topgeardave:
Any chance you can include a test interactive governor based on myfluxis new commits in the cm kernel? Thanks
[Nexus 5 Original Android Development] neobuddy89:
I have tested that long back and liked our current governor more.

I can't implement it as separate governor (since configuring both same time is not clean job). So you need to choose one.. ;)

Both governors were tested for freq jumping -- new one comparatively changed freq aggressively all the time.. whereas old one is changing freq aggressively only when load is high.. (technically we use fast_timer_rate at high load!)

Both were tested when screen off and music on -- our old one remained at lowest frequency all the time!

These are my personal reviews... not trying to sabotage new development.
[Nexus 5 Original Android Development] Cristiano Matos:
Thanks [MENTION=3795148]neobuddy89[/MENTION] for your kernel.

Latest nightly is rocking beautifully here with crDroid. Synapse is the best tweek app IMHO
[Nexus 5 Original Android Development] neobuddy89:
Unable to find crDroid latest download link since google plus is blocked in my corporate. :(
[Nexus 5 Original Android Development] Cristiano Matos:
Here you go: http://www.mediafire.com/?ozn80tnizsccnbt
[Nexus 5 Original Android Development] topgeardave:
Quote above shows it boots with latest nightly, my bad for saying it's aosp :)

---------- Post added at 02:56 PM ---------- Previous post was at 02:54 PM ----------

Thank you for your input and based on the commit messages it falls inline with what you say about aggressive freq jumping. The current interactive governor is awesome for battery and performance (I changed fast timer rate to 10000 for best balance between battery life and performance :))
[Nexus 5 Original Android Development] neobuddy89:
New nightly build on MediaFire mirror available for official CM:

Chaos-Kernel_v14.0-[09-17]-[07-38]

* Fix diag mode. (Please test @Unb0rn)

* Audio driver minor updates

* Add "CyanogenMod" hotplug option to Synapse. (This is optimized mpdecision. Why optimized? This)
[Nexus 5 Original Android Development] Unb0rn:
Diag works great! Thanks! It's just awesome! :)
[Nexus 5 Original Android Development] mo976:
Does this include the new interactive governor bits and bobs from myfluxi?
[Nexus 5 Original Android Development] neobuddy89:
No. We are allergic to cleanliness. ;)

Anyways, read this:

http://xdaforums.com/showpost.php?p=55477515&postcount=3875

However, let me check if that can be introduced as separate governor.
[Nexus 5 Original Android Development] mo976:
I saw that but wasn't sure if it included the latest build. Thanks for the clarification. Carry on...
[Nexus 5 Original Android Development] fluther:
Latest 14 still stuck at 1.2ghz for me. Haven't had the time to do a full wipe yet, I will once I can.

Reverted to 13.2, still works great with the 17/9 CM nightly.
[Nexus 5 Original Android Development] neobuddy89:
Please do that and report back.

Most likely for init.d script or background app changing this value.
[Nexus 5 Original Android Development] likonvampire:
Are we getting a new stable anytime soon now that CM M10 is out ?
[Nexus 5 Original Android Development] topgeardave:
Latest 14.0 nightly is pretty stable for me, no lockups or reboots for me
[Nexus 5 Original Android Development] montbazon:
Sounds cool. I wanna try myfluxinteractive[emoji6].

IMHO users may help reduce your time to research.
[Nexus 5 Original Android Development] EnginEAR:
Bug

I have a problem with selecting profiles in the Gamma section of Synapse and the latest kernel nightly...

It says:

SOoptionList has failed:

com.af.synapse.utils.RunCommandFailedException: /res/synapse/actions/restorebackup[470]: can't create /res/synapse/files/gamma_prof: Read-only file system
[Nexus 5 Original Android Development] unknvvn:
Today i had 4 reboots. I upped CPU voltages and it seems to be resolved.

For some reason default cpu voltages are too low by default for my PVS2 with latest nightlies with Synapse.

There was the same issue some time ago but it was fixed by increasing default voltages, now it seems to be back.
[Nexus 5 Original Android Development] topgeardave:
I don't know why but this kernel is weird with voltages, it just uses one voltage for all phones. I use FKU to set my voltage so it's kept during all flashes. I used this voltage table to change voltage from stock to pvs2 tables when my phone is a pvs0. http://xdaforums.com/showpost.php?p=47425927&postcount=193

Neobuddy any chance you could include the voltage tables as an option in synapse like how you can select hotplugging method?
[Nexus 5 Original Android Development] neobuddy89:
Voltages were reset.
[Nexus 5 Original Android Development] fluther:
Can anyone say how well 14 is working with M10? It's the start of term so I'm going to be sticking with m releases from now on I think.

Just backing up for a full wipe now.
[Nexus 5 Original Android Development] montbazon:
You mean those are qualcomm's default and doesn't touched as well?
[Nexus 5 Original Android Development] neobuddy89:
I meant they were reset to values given by CAF for new voltage structure.

Let me build using our old voltages for all PVS.

https://github.com/neobuddy89/hammerhead_kernel_caf/commit/5684beadb36f6f6252990b5c7f0f934c0a686384
[Nexus 5 Original Android Development] neobuddy89:
New nightly build:

Chaos-Kernel_v14.0-[09-18]-[00-16]

* Use old voltage structure for ALL pvs.

* Add PVS info in Synapse app.

Please report your PVS and stability if not already reported.

PVS1 tested with OC. Stable.