yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] neobuddy89:
About the tests, I am conducting for new version:

Seems like disabling mpdecision via init code and enabling intelliplug hotplug driver causes bootloop sometimes (stucl at bootloader screen).

We won't be taking that risk. So mpdecision will be enabled by default.

So, to conclude, v3.1 is the most stable and the best release.
[Nexus 5 Original Android Development] neobuddy89:
An update available:

Changelog for v3.2:

CPU Idle for C0, C1 and C3 enabled. Idle for C2 disabled. [Better deep sleep?]

Use SIMPLE governor as default for GPU.

Added simple GPU governor controls to NXTweaks

Better loading of NXTweaks config on boot

Updated and cleaned ramdisk

Better mount options for performance
[Nexus 5 Original Android Development] Jur1nator:
Wow, you are really pumping out these updates :) very nice to see
[Nexus 5 Original Android Development] yuuzhantar:
So we will have to wait a better implementation ?
[Nexus 5 Original Android Development] tomciopaluch357:
Thank you downloading right now and will play for couple days, now i need to find out which Rom will give me the best performance and battery life . Any suggestions?
[Nexus 5 Original Android Development] KingBeike:
Purity or cataclysm ;)
[Nexus 5 Original Android Development] absoluterebirth:
[MENTION=3795148]neobuddy89[/MENTION] I'm having a bit of an issue. I'm on Cataclysm ROM and it seems that whenever I switch kernels, per say from Chaos to Trinity and then back to Chaos, I get set back to the Dalvik runtime, from my previous ART runtime. Is it something to do with the ramdisk on your kernel?
[Nexus 5 Original Android Development] neobuddy89:
On further investigation, this kind of behavior is because of mpdecision.

mpdecision changes the scaling frequencies depending on the load and temperature of device.

I tried disabling mpdecision at the boot from init code in ramdisk and replace it with intelliplug hotplug driver.

But this wasn't good idea as there was slight decrease in performace and 1 out of 5 device would have bootloop issue.

To conclude your question, if you don't like this stock behavior.... you can either get app like FauxClock and disable mpdecision.

Or use following set of commands in terminal emulator after device has been booted properly:

stop mpdecision

echo "1" > /sys/module/intelli_plug/parameters/intelli_plug_active

I would suggest to keep it stock behavior for best performance. We will see, in future, if we have any better alternative.
[Nexus 5 Original Android Development] neobuddy89:
Nope. I didn't touch any part of code that affects runtime library.
[Nexus 5 Original Android Development] neobuddy89:
I have reviewed 1500 commits and cleaned old irrelevant and buggy ones.

Also added new tweaks and sync with CAF latest patches.

"Custom" sound profile is still not working in NXTweaks, didn't got time to fix that yet.

Here is test build:

http://www.androidfilehost.com/?fid=23329332407576956

Thanks for reviews. :)

:highfive:
[Nexus 5 Original Android Development] nikr123:
Everything seems to work very well so fast! Thanks!
[Nexus 5 Original Android Development] Jur1nator:
let the device unattendet after flashing.. it literally drained the battery empte from 50% within an hour.. and got super hot doing nothing...

i even though i bricked my phone because nothing worked until i put in on the charger..

don`t know if this is just a strange bug happening to me.. but i am going back to an ealier kernel for now
[Nexus 5 Original Android Development] neobuddy89:
Seems some rogue background process kept your device working.

What ROM are you using? I am testing on CM nightly and no such issue.
[Nexus 5 Original Android Development] Jur1nator:
I am on the 1.3. Cm nightly... Maybe some caf changes in this week, that are needed for the kernel to work properly?

Rogue app seems plausible, but I never had such a problem and it only started right after flashing.. Earlier kernel version work fine..

I'll try to find the problem source and report back if I find something
[Nexus 5 Original Android Development] kronflux:
okay, had posted about not experiencing the overheating issues, but I just tested the latest build with the latest nightly of CM11, and I did experience it.
[Nexus 5 Original Android Development] neobuddy89:
Temperature Core control is enabled in latest test build (not enabled on Chaos 10.2) maybe causing issue for you.

I will switch it off in next one.
[Nexus 5 Original Android Development] kronflux:
I wiped my device and reinstalled CM11 nightly, PA GApps and that Chaos test build.

I'm no longer experiencing the overheating. no idea what was causing it.
[Nexus 5 Original Android Development] neobuddy89:
Test Build #2:

* Enabled RWSEM optimizations

* Temp tunings

http://www.androidfilehost.com/?fid=23329332407577024

I am not sure what's with PAC, PAC doesn't seem to suit well with Chaos.

CM Nightly seems to work smooth.
[Nexus 5 Original Android Development] GianniDPC:
I'm getting bootloops and Android.process.acore has stopped, com.android.phone has stopped errors, with the latest M4 build, Can you take a look into this? Thanks in advance! :)
[Nexus 5 Original Android Development] neobuddy89:
Please fresh install your ROM.

I will recommend to use latest nightly.

Currently, am busy backporting kernel generic scheduler code. :)
[Nexus 5 Original Android Development] jsylvia007:
I had that as well, and it doesn't appear to be linked to the kernel... A quick google pointed at the Contacts Storage being an issue. I went into APPS --> ALL --> Contacts Storage and cleared data... All was fixed.

I lost contacts but they resynced from Google without an issue.
[Nexus 5 Original Android Development] atrus5:
I'm not sure what you mean by not suiting well. Have had no errors in pac and 39 hours of battery life in previous build. It's best to flash rom first then kernel though on every new build and let it sit for a few minutes after boot. Thanks for great kernel. Oh I'm on pac 0306
[Nexus 5 Original Android Development] neobuddy89:
When I tested on PAC, I am facing heavy scroll lag.

On CM, this scroll lag is negligible. (not zero because we have disabled battery hogger touch_boost) (It totally goes away on CM if boosted CPU set to 4)

I have no issue anyone using Chaos with PAC. It's just my device not letting me keep PAC for now.
[Nexus 5 Original Android Development] Tommy-Geenexus:
Thanks for the blazing kernel [MENTION=3795148]neobuddy89[/MENTION]

This will be my daily driver for now

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] neobuddy89:
Thanks for testing out test builds.

A new nighly build is now available:

Download HERE.

Chaos-Kernel_v11.0-[03-09]-[00-18]

* Complete clean code with all necessary merges and sync with CAF. (Removed conflicting faux source merges - to initiate new backports)

* Fixed CAF Sound controls in NXTweaks (all profiles working as expected - please test)

* Squashed bugs of previous nightlies

* Initiate backport of scheduler code from 3.11 (experience will get better once merge is complete in upcoming builds)

* Driver updates from CAF

On personal note, the sound has got better than ever! Even without DSP manager, bass and treble are so clear.. :)
[Nexus 5 Original Android Development] topgeardave:
Latest kernel is rock solid! One feature request if it's not too much trouble. Any chance you could add governor control to NXTweaks where you can change the parameters of the governor? This is the only reason why I use trickstermod, if it was implemented in NX Tweaks I would have no need for it.

Regards

Dave
[Nexus 5 Original Android Development] neobuddy89:
I will check if feasible. The only issue I see is that it cannot be generic across all governors (unless code changes are done),

meaning that I can provide control only for selective governors.

Let's add this feature request to to-do list for v12 (right after F2FS request). :)

You can discuss and share best settings for a governor. If good enough, I can set them default for builds.
[Nexus 5 Original Android Development] topgeardave:
Apps like trickstermod only enables it specific Governors like ondemand, interactive and intellidemand. I'm still messing about with interactive parameters and once I find an ideal one, I'll share them on here :)
[Nexus 5 Original Android Development] Akeel1994:
I think the intelliactive governor should be default ;) Amazing performance and good battery on the other side.
[Nexus 5 Original Android Development] EnginEAR:
Works flawlessly!!!
[Nexus 5 Original Android Development] mohammed510:
I think that a clean install is required for the latest nightly to run. otherwise, you'll see a lot of FCs. Just a heads up.
[Nexus 5 Original Android Development] zimlokks:
Didn't require any effort whatsoever installing on CM's latest nightly, running latest kernel release.
[Nexus 5 Original Android Development] mohammed510:
Hmm.. Maybe because I'm using the latest M4 snapshot version.
[Nexus 5 Original Android Development] rachanta:
Great work. Everything including sound control settings surviving reboots, works perfectly.
[Nexus 5 Original Android Development] topgeardave:
If you left auto sync on, there was a chance that your contacts became corrupt. That's all it was with m4 dirty flash
[Nexus 5 Original Android Development] mo976:
M4 code is older then latest nightly by probably about a week, that means that the latest CAF stuff and drivers that neobuddy includes in the kernel might cause conflicts. However there is no reason not to use the latest nightly, though I recommend heading over to the Nexus 5 CM11 forum here on XDA http://xdaforums.com/showthread.php?t=2584004 before installing the latest nightly's to see if anyone reports problems and avoid bad builds.
[Nexus 5 Original Android Development] t1.8matt:
I cannot get Chaos v10.2 or v11.0-[03-09]-[00-18] to boot on Carbon unofficial nightlies which are now CAF based. It just sits at the Google logo. I'm using Multirom but I know this kernel is compatible with Multirom.
[Nexus 5 Original Android Development] neobuddy89:
Chaos won't boot if you flash it on Secondary ROM.

MultiROM feature is just to test new ROMs and not kernels.

Moreover, it's not actually a feature but a hack.
[Nexus 5 Original Android Development] t1.8matt:
Is this just a Chaos deal, cause I haven't had that problem using other kernels on secondary ROM.
[Nexus 5 Original Android Development] topgeardave:
Hey guys, just thought I'd share my settings for battery life/performance combination so it lasts you a day. Anything I've missed out means I've kept it as stock

In NXTweaks:

Power Efficient Workqueues: On

Screen On: 300-1497mhz

Screen Off:300-1190mhz

CPU Boost Duration: 20ms

Input Event Boost Duration: 40ms

Input Event Boost Frequency: 1190mhz

Sync Threshold: 1497mhz

Boost CPU's: 2 (For battery life use 1)

Max CPU'S Online: 4 (For battery life use 2)

Screen on Governor: Intelliactive

Screen off Governor:Conservative

Screen on/off IO Scheduler: FIOPS

UV: -10mv

GPU Frequency: 200-320mhz

Polling Interval: 16ms

CAF Sound Control: Quality

Colour Tweak: Vivid

Vibrator Strength: 50

Fast Charge: 1200mah

Cron: On

DB Optimisation

Clean APP Cache

In TricksterMod:

General-> Governor Control

above_highspeed_delay: 2000

Boost:0

boostpulse_duration:250000

go_highspeed_load: 95

hispeed_freq: 1190400

io_is_busy: 1

min_sample_time: 25000

samling_down_factor: 120000

sync_freq: 960000 (729600 for better battery)

target_loads: 85

timer_rate: 30000

timer_slack: 75000

two_phase_freq: 300000

up_threshold_any_cpu_freq: 1267200

up_threshold_any_cpu_load: 95 (70 for more performance)

If anyone can add to this in any way, feel free to contribute :)
[Nexus 5 Original Android Development] D-m-x:
Same here, tried this Kernel because Carbon switched to CAF, but I couldn't get it past the Google Logo. No Multirom here, have never used it. Maybe a Clean Flash would work, no clue but i dont have the time right now to test that :(
[Nexus 5 Original Android Development] t1.8matt:
Yep, I knew it had to be something else cause I've gotten roms to boot with 3rd party kernels as secondary rom, and you're saying it won't boot with no multirom so i'm guessing it's an issue with the rom, not the kernel though if other people aren't having issues with v11 on other CAF roms. I'm going to try latest official Carbon nightly with this kernel again as primary rom and see if it boots then.
[Nexus 5 Original Android Development] D-m-x:
Yep, i too think its Rom related. You could try v11.0-[03-09]-[00-18] with the latest Official Carbon Nightly, thats the only Version i haven't tried yet. The Others, including Stable didn't work, i tried them myself :)
[Nexus 5 Original Android Development] neobuddy89:
I will check Carbon ROM and fix compatibility if possible tomorrow.

New nightly release is available HERE.

Chaos-Kernel_v11.0-[03-10]-[02-20]

* Kernel Task Scheduler complete backport from 3.13 mainline kernel

* Merged new task scheduler SCHED_DEADLINE

More Info =>

Not to be confused with the iosched deadline, Sched_deadline is a scheduling class that implements a real-time CPU scheduling algorithm; EDF (Earliest Deadline First), augmented with a bandwidth isolation mechanism (called Constant Bandwidth Server, CBS) that makes it possible to isolate the behaviour of tasks between each other. SCHED_DEADLINE allows the CPU to reserve a portion of the CPU time to a specific application very accurately. A key feature is that it ensures "temporal isolation", which means that the temporal behavior of each task (i.e., its ability to meet its deadlines) is not affected by the behavior of any other task in the system. In other words, even if a task misbehaves, it is not able to exploit larger execution times than the amount it has been allocated. When a task tries to execute more than its budget, it is slowed down, by stopping it until the time instant of its next deadline. When, at that time, it is made runnable again, its budget is refilled and a new deadline is computed.

* Optimized RB Tree (Red-Black Tree) algorithm backported from 3.13 mainline kernel

* Backports from 3.13 for IRQ (interrupt/reqst) and CPUTIME optimized updates

* Performance optimizations

* CAF Updates for MSM Board

* Removed ZRam and Swap (not needed; rarely someone uses it)
[Nexus 5 Original Android Development] topgeardave:
The build you uploaded on the CarbonROM thread via your dropbox, that one is AOSP as I just tried it with this kernel and it did not boot. However it booted fine with francos r32 kernel which was lying around on my phone.
[Nexus 5 Original Android Development] expertzero1:
Here's the last k msg when connecting to Bluetooth and the screen being non responsive . have to hard reboot to reconnect

http://www37.zippyshare.com/v/8532514/file.html
[Nexus 5 Original Android Development] nikr123:
Does it improve performance when you remove ZRam and Swap at all or is it just because it is not really useful on a device with this much RAM?
[Nexus 5 Original Android Development] zimlokks:
It's basically useless with the nexus 5, has anyone used the new deadline scheduler?
[Nexus 5 Original Android Development] nikr123:
Yea but is there any if just a slight performance improvement?
[Nexus 5 Original Android Development] zimlokks:
There shouldn't be a difference.
[Nexus 5 Original Android Development] Vanhoud:
This problem again? Damn I guess I'll see this in the morning :)
[Nexus 5 Original Android Development] nikr123:
[MENTION=3795148]neobuddy89[/MENTION]

Since there is no performance boost I think zRAM and/or should be reimplemented since some might run a big Linux system over terminal and vnc. I would think that could take up some RAM and instead of killing apps running in the background some might want to use some of those features.
[Nexus 5 Original Android Development] zimlokks:
Kernel samepage merging is still enabled and helps conserve ram, zRAM should be reimplemented, unless there's a reason why not to.
[Nexus 5 Original Android Development] neobuddy89:
Yes, it will be implemented but after some debugging.

I was checking logs previously and found that zRAM got switched on without turning it on from NXTweaks.

Maybe some app caused this but need to make sure that kernel is not turning it on explicitly.

Do you use zRAM? If yes, what performance improvement you get?
[Nexus 5 Original Android Development] D-m-x:
I did try it with Franco but got constant crashes and never even made it to the Homescreen.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] neobuddy89:
You can help me testing and resolving same.

Q) Did you get same issue on previous nightly build? Please check and be 100% sure for same.

If yes, then please try following:

Open Terminal Emulator

Type following

su

(Yes to superuser permission)

setenforce 1

(this should turn on SELinux in enforcing mode)

Now try to replicate the issue and report back.
[Nexus 5 Original Android Development] expertzero1:
No clue, been using my lg g2 for two weeks. Just went back to the n5 yesterday lol.

Fresh install with crdroid, with the 3/9 kernel build.

Flashed the 3/10 build during work and connected to bluetooth in the car, it didnt freeze. I will check it out tomorrow when im driving to school. I will let you know if it occurs again.
[Nexus 5 Original Android Development] ed2975:
google dialer

Hey, so the google dialer problem seems to be giving everyone on post 03/02 CM nightlies headaches, but the one of the devs at PA 0 day Gapps suggested the error may be kernel related in conflicts with code for multi sim support

here is the post: http://xdaforums.com/showpost.php?p=50875268&postcount=3546

Is this a possible avenue for investigation?

Is there another way to get google dialer back working on CM nightlies, Ive tried wiping the data of contacts storage and everything remotely phone related and cant get past it, so now stuck using AOSP dialer
[Nexus 5 Original Android Development] neobuddy89:
I don't think its only the kernel.

A path entry was recently added to ramdisk to point newly compiled msism telephony.

Nothing was removed from kernel ramdisk.

This as such shouldn't give any issue from kernel point of view.

Can you please ask PA maintainer what fix are they expecting in kernel ramdisk?
[Nexus 5 Original Android Development] Vanhoud:
https://www.dropbox.com/s/yuqz6m6z1xwhpk6/chaos_last_kmsg

So my phone somehow turned off overnight (late for work now lol)

---------- Post added at 06:24 AM ---------- Previous post was at 06:20 AM ----------

I also had my phone in airplane mode by battery stats show differently

Looks like I had some massive battery drain or something causing the phone to shut off (but not completely die)
[Nexus 5 Original Android Development] neobuddy89:
Reason shows: Reboot By Key

Which means it's not kernel but power key was long-pressed for reboot, maybe your grip cover or flip cover or by mistake long pressed by you.
[Nexus 5 Original Android Development] Vanhoud:
Wow really? That's strange. I don't even see how that's possible but I guess it happened. Why would it wake up with such a gigantic difference in battery level?
[Nexus 5 Original Android Development] TheBenz:
I had exact the same last night, i put it in airplane mode with around 70% and in the morning it was dead.

after boot it said 1 % battery. I plugged in the charger and after a few seconds the battery went up to 60%...
[Nexus 5 Original Android Development] Vanhoud:
Yeah, mine booted at about 10% battery but it didn't have a big spike back up like yours. I charged it back to 100% like normal
[Nexus 5 Original Android Development] A_Button117:
I get a "Com.android.phone has crashed" on Pac with the latest nightly of this kernel and the ROM, any advice? I cleared cache and dalvik, and I also cleared the data for the dialer...

Studying Computer Science and Forensic Science @ UCO

Using XDA Premium 4
[Nexus 5 Original Android Development] mathew1234:
For some reason I can't overclock the CPU.... Anyone else?

I'm on the latest version of this kernel!!
[Nexus 5 Original Android Development] zimlokks:
Personally don't use zRAM, why would a high ram device need it? I used to use on my Droid Incredible, which only had about 512mb of ram. It doesn't really have any performance improvements.
[Nexus 5 Original Android Development] DenyDarko:
[MENTION=3795148]neobuddy89[/MENTION]

Could you please consider this experiment if supported by our kernel? :)
[Nexus 5 Original Android Development] topgeardave:
It already is, Android 4.3 included trim support. If you want to trim manually just download the lagfix (fstrim) app from playstore
[Nexus 5 Original Android Development] DenyDarko:
By using this option there is no need for any application as the trimming is happening in realtime...
[Nexus 5 Original Android Development] t1.8matt:
If you feel the need to use trim manually you can also use terminal and type "su" "fstrim -v /data".
[Nexus 5 Original Android Development] neobuddy89:
A good read: https://patrick-nagel.net/blog/archives/337

"discard" may affect performance. So maybe I can program good CRON job to do this job?

Next nightly to feature:

RBTree implementation for LMK + LMK optimizations (much faster and better now)

Performance optimizations

More smoothness
[Nexus 5 Original Android Development] DenyDarko:
It may affect the performance.

Could you at least consider the possibility to add it as an optional setting in NXTweaks to see how much? :)
[Nexus 5 Original Android Development] Skysurfer77:
Just wanted to say, latest Chaos Kernel Nightly plus todays CM Nightly is smooth as hell!!! Thanks!

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] expertzero1:
Did what you asked on latest nightly.

Oops nvm it went back to permitted when I rebooted it before I connected to Bluetooth lol

http://www35.zippyshare.com/v/32943734/file.html
[Nexus 5 Original Android Development] Vanhoud:
[MENTION=3795148]neobuddy89[/MENTION]

Was there any change to the p v6 color profile on the latest nightly? Color are more "contrasty'
[Nexus 5 Original Android Development] lightningstalon:
Has anyone tried the latest nightly with Carbon ROM?
[Nexus 5 Original Android Development] MontAlbert:
this fixed my issue. It was weird, every time i hooked onto a different BT device (eg. car) the device would hang. reboot and it would then connect no worries. . eg. got into car, hooked onto BT, screen hung. rebooted then it connected no worries. Got to gymconnected to bluetooth headphones, it hung again. rebooted then fine until i got in the car again.. another reboot required.

I actually used an App SELinux Mode Changer to change the mode to enforcing mode. This did indeed fix the problem with the screen freezing.
[Nexus 5 Original Android Development] neobuddy89:
Testing still in progress, maybe couple of hours more.

Maybe. Let's see.

Thanks for your words.

This profile is predefined by its owner.

If you have suggestion, you can discuss it here:

http://xdaforums.com/showthread.php?t=2424467

Also app there can help you customizing with your own needs and more profiles!

NXTweaks aim providing pre-defined good profiles; you can suggest me profile of you like and I may add it NXTweaks.

I don't think Carbon is CAF yet, is it?

Thanks for testing out. It will be set to Enforcing by default in next builds.
[Nexus 5 Original Android Development] kkk-sgs2:
Carbon use now CAF "frandom" , but it seems its different, not booting with latest Chaos.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] cgjjaf:
com.android.phone error "loop"

I have the same problem as the first post, tried the possible solution in the second post and nothing, I continue to get the com.android.phone error "loop". I also tried flashing the kernel after reflashing my rom and from a clean install and got the same error. I am running CM11 latest nightlies. Any suggestions will be greatly appreciated. Thanks.
[Nexus 5 Original Android Development] lightningstalon:
Carbon is CAF Frandom I think with the latest builds. You can tell from the amount of complaining that's on that thread haha