yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] myfluxi:
interactive is presently by far the most advanced cpufreq governor for mobile devices. I see no reason to use anything else as it does everything better. Each and every governor that is not in either Android or Linux mainline is bogus. To me it appears that the usual suspects like to see their names somewhere, basically selling snake oil. If you want to improve interactive, work on the tunables to optimize it for your needs (save 2% energy, squeeze 2% in benchmarks or whatever) or just leave it as it is. If you want to save energy, clock it down a bit, switch off subsystems and dim the panel.

The concept of a hotplugging governor is smart and logical. But in practice, it makes more sense to separate cpufreq, hotplugging and touch-boosting. It would save a few cpu cycles though if statistical (load) data would be provided by a single source. Other than that, our kernel are very close to what can be considered "the viable optimum". All the tweaking and patching is snake oil as well. I like Max Wenningers concept of a common touch-boost api/driver, I wouldn't use it though. Max is a really cool guy.

Regarding the atomic stuff, I was making fun of the other hotplug driver which looks really strange. I could strip down my driver to like 150 lines or less and it would still be an awesome solution for the simple task.
[Nexus 5 Original Android Development] neobuddy89:
Agreed 100%. That's only reason I don't mess with interactive... not much even with tunables unless performance is compromised.

Interactive stays default, other "snake oil" governors are added to serve definition of "rich" kernel of many users around.

They are stable but as you said they don't belong to mainstream.

ROFL with your comment on other hotplug driver.

Even logic seemed quite broken to me, I tried fixing logic... it got fixed ... however, there is drop in FPS while 3D tests.

The only thing I liked about that hotplug driver is tuning parameter as I was able to adjust load and trigger frequencies for different cores. Since hotplugging is expensive, we should be able to define triggers... don't you think?

I am in love with your MSM_Hotplug driver... only 1 thing that grabs my attention is below.....

Chaos is tuned to change governor on screen on / off events when power suspend driver changes state...

So when I turn on the screen... I can see all the cores turn on!! This was not the case with other broken hotplug driver...

Can you please suggest, what can be done to avoid this chaos of cores??

My next experiment is to exploit online cores tunable of your hotplug driver to prevent above scenario if I don't get anything else to try with.. Thanks again for this driver. :)

P.S. The most "snake-oil" governors and other hotplug driver belong to your old friends. ;)
[Nexus 5 Original Android Development] myfluxi:
Is there reliable data about cost-effectiveness, number of cores vs. frequency per core for Qualcomm SoCs? I'm not sure if hotplugging is still that expensive compared to baseline cpu load, but of course I cannot be sure. I think total load is a good enough indicator for us. I tested the last known frequency before a cpu was unplugged and it was (almost?) always below 960MHz (which is another nice out-of-ass number :)), so an appropriate check appears unneeded.

You can change thresholds for 2, 3 and 4 cpus in my driver, just make sure they overlap. I pulled threshs 50/100/150 (right?) out of my ass as well because they just worked and I never ever touched them again, not even for testing.

You can remove the lcd callback trigger or remove early-suspend, both do the same thing. If you don't want all cores come online, remove this entirely. If you want to throttle the device a bit during suspend, inject more conservative tunables into the cpufreq driver. I'd say it does not make much sense to switch the governor. We can only guess energy usage and from my experience, it all depends on wifi and radio connectivity and 2G/3G or off. Bad radio connction == more energy usage and vice versa. Independent of all this my device sleeps >95% and rarely uses higher freqs. Percentages are completely erratic, sometimes 0.1%/h, sometimes 0.8/h, so again, it's all guesswork for us mere mortals without development devices to solder and abuse.
[Nexus 5 Original Android Development] NemysysS3:
Noob and in Love with my Nexus

[MENTION=3795148]neobuddy89[/MENTION] thank you for an awesome Kernel. Not use to all the terminologies and words used in Nxtweaks so I most times leave them at stock and still have an great experience. But sometimes I feel like my device could be so much better.

Guys any tips on what can be changed to give that ultimate feel. last two posts made mention of changing some tunables (Clueless) so its more pointing and saying this is safe that is safe, dont touch that and I'll experiment with what works for my device. Sorry for the long post..

Cheers
[Nexus 5 Original Android Development] neobuddy89:
Thanks for the heads up. That will do.

I didn't noticed LCD notifier before in the code. :)

I read in Faux's topic, hotpluggin ... turning CPU on/off is costly in terms of power.

I need to test that if we can save more power by removing notifier.

I recommend you not to download a test/beta build.

Either go for nighlies or stable release.

NXTweaks will help you to tune parameters. Explore it.
[Nexus 5 Original Android Development] Tikerz:
Yes, I'm running your Linaro test kernel and it happened as soon as I connected with Bluetooth with my car this morning.
[Nexus 5 Original Android Development] Vanhoud:
I wasnt on 10.2 long enough to know. I loaded the latest kernel (2-17) this morning before leaving for work, and it did not freeze the phone when bluetooth connected. So it is not a 100% reproducible error, at least to me. Like i said before, this happened to be one other time but im pretty sure it didnt occur in my car with Bluetooth. Also this morning I had a hard time waking the phone up from (screen was off maybe 5 minutes), and when it came back online it was extremely sluggish and I had to do a hard reboot.
[Nexus 5 Original Android Development] myfluxi:
You have to put into perspective, we are talking about almost nothing in terms of saving potentials. Dare I say, literally nothing?
[Nexus 5 Original Android Development] Akeel1994:
[MENTION=3795148]neobuddy89[/MENTION]

Could you add sound profiles to sound controls (like in faux sound app) The qualitiy profile would be great. Thanks!
[Nexus 5 Original Android Development] Vanhoud:
Okay it just happen again when connected to bluetooth. A hard reboot is required and then it can connect successfully without freezing
[Nexus 5 Original Android Development] topgeardave:
Please upload some logs in future or else nothing can be done about it
[Nexus 5 Original Android Development] Vanhoud:
It does not appear to lock up on 10.2

---------- Post added at 03:45 PM ---------- Previous post was at 03:45 PM ----------

I already have, he is aware of the issue
[Nexus 5 Original Android Development] Silentbob999:
Interesting discutions about governor and hotplugin.

For the bluetooth bug. I don't remember not having problems with any "caf" rom... Or at least kernel/rom need to be absolutely sync (like if there was change every freaking day regarding bluetooth). Maybe it was just because I do not use bluetooth everyday and everything was random but that was how it looked.

I had those log on my sdcard. Don't know if it's on DK19 or CM11. Got problem on both.

Basically on call using Fongo (dell voice). Got complain about bad sound. Connect bluetooth headset. Hang...

Hope this helps.

https://www.dropbox.com/s/u0b8bk4xq4h4fu4/bugLog_Hang_BluetoothOnCall.zip

"Envoyé depuis mon Nexus 5 avec Tapatalk"
[Nexus 5 Original Android Development] DREWHAMM974:
How dare you forget Trinity?
[Nexus 5 Original Android Development] kchino:
neobuddy89 thank you for your efforts on this kernel. It's excellent, I haven't looked back since trying it! The latest Linaro nightly isn't as battery friendly as the [05-06] 2-17 or previous versions for me though. Sorry for the lack of screens but in my limited testing I saw a drop from 6-7hrs to 4-5hrs screen on time in my personal usage. Have you or anyone else noticed a similar drop in battery life on the Linaro test build?

Also I noticed that when using the interactive governor on both mentioned kernels I can't get any video in YouTube, sound is fine. Switching to Intelliactive rectifies this for me immediately without wiping data, cache or dalvik. Are you able to reproduce this? I really don't have any gripes just wondering if either of these are reproducible. Thanks again for your exceptional work!
[Nexus 5 Original Android Development] knapz:
Last kmsg from a reboot while using keyboard.

https://www.dropbox.com/s/0j4xgwogy9o1zhy/chaos_last_kmsg
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
snake oil alert!
[Nexus 5 Original Android Development] topgeardave:
I agree, the latest nightly hits the battery harder than previous kernels. I think this is because of the way he changed the hotplugging as I know see that 3 cores are now being utilised instead of 2 when looking at trickstermod
[Nexus 5 Original Android Development] neobuddy89:
No, I haven't touch hotplug mechanism in any versions. Not yet.

It will be kanged to relax more in next version.
[Nexus 5 Original Android Development] tlf55:
Is it possible that the frandom does break the mechanism of battery saving mode GPS ? Like for weather widget .. The widget is getting updated but not the location ..

And last question is it possible to reduce freq of touch boost and increase the duration of the boost ?

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] Akeel1994:
Yes, I can also agree that the battery is draining on the latest nightly
[Nexus 5 Original Android Development] neobuddy89:
Frandom will be removed in next nightly release as I have updates for "random" driver backported.

Frandom was not updated since ages (I guess)

intellidemand is removed as last report submitted in the topic has issue with it.

Battery seems to be an issue on Linaro test build.

Next nightly release will also consist of new suspend code along with better wakelock polling. Testing in process.

MSM_Hotplug changes are done (Thanks [MENTION=4152171]myfluxi[/MENTION] for the idea) These changes will make hotplugging less agressive at screen on/off events.

For those who aren't frequent flashers should stick with stable releases.

Nightly releases are stable for 99% of users (100% for me) however features included are not fixed to sustain.
[Nexus 5 Original Android Development] tlf55:
Okay thanks, so for now if we stick with 02-17 05-06 it's good for battery life ? :)
[Nexus 5 Original Android Development] GragonV:
Humh, I've followed this for my Vanir Rom:

but still cannot flash the 10.2 ver, phone is stuck at the google's first boot image....

reflash the rom and install 9.2 is ok :(
[Nexus 5 Original Android Development] kchino:
Yes I've had a good experience with this version or use the last stable version 10.2 [10-05].
[Nexus 5 Original Android Development] topgeardave:
That ROM is based off AOSP, versions later than 9.2 won't work on it
[Nexus 5 Original Android Development] expertzero1:
a day without flashing these nightly builds is killing me haha :)
[Nexus 5 Original Android Development] TheAtheistOtaku:
are you flashing on a non cyanogen mod based rom? if so, then thats your problem. everything after 9.2 is meant for cm based roms. and before you ask no, he doesnt plan on making his kernel compatible. so its either keep the 9.2 kernel, or switch to a cyanogen based rom
[Nexus 5 Original Android Development] MontAlbert:
I am also getting this hang up with connection of bluetooth and also the very slow wake times from screen off.

Is there a solution to the bluetooth known? Is it particular to a specific governor?
[Nexus 5 Original Android Development] expertzero1:
He acknowledged the issue a couple days ago. Hopefully its fixed :)
[Nexus 5 Original Android Development] neobuddy89:
Please try below nightly and report back:

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

It is compiled with Google GCC 4.8

Still needs finishing, but am using without any issue.

EDIT:

You can see changes done on github source.

It also contains modified hotplug - less aggressive and better audio.
[Nexus 5 Original Android Development] XeYex:
Camera flash problem

Hi, neobuddy89 i'm using your nightly kernel v. 11 of 18th february and i have found an issue when take a photos with camera. In low light situations the flash is over exposed so my pics are whole white :silly: there were same problem in elementalx kernel by flar2, but he fixed this issue in 0.29 release.

Could you take a look to solve the problem please?

For the rest your kernel is awesome!!! :good:
[Nexus 5 Original Android Development] MontAlbert:
Couldn't get it to boot past the Google splash screen mate. I downloaded it a few times. Same md5. Wiped cache etc... Still no boot.
[Nexus 5 Original Android Development] kong:
Did you flash it on CM-based ROM?
[Nexus 5 Original Android Development] expertzero1:
Booted up on cm night 2/19. Will test Bluetooth later when I wake up, 4am ATM. Someone will beat me to it
[Nexus 5 Original Android Development] MontAlbert:
Lol...yes...same ROM that works for previous version...aikp.... Weird it worked for someone else...said it flashed OK in recovery. Nfi

*edit* downloaded again,twice,from different mirrors and still not past Google splash.using aikp which is a caf ROM based on aikp. Previous nightly worked fine (except for Bluetooth)
[Nexus 5 Original Android Development] neobuddy89:
And this is not issue on versions before that?

For what I understand the issue can be is we are using flash on chaos with full power (for better pics) which could be issue.

But this was hacked since initial versions...

Thanks. Please check.

AICP??... Sorry, I don't have bandwidth to debug that.
[Nexus 5 Original Android Development] kong:
Well, then my best guess is that you may have flashed another kernel in between… Try re-flashing the ROM then Chaos right away, it might help.
[Nexus 5 Original Android Development] mo976:
Flashed fine on the latest cm nightly 2/20

Edit:

I noticed you changed the default screen off governor to interactive any specific reason
[Nexus 5 Original Android Development] neobuddy89:
No definite reason.

I was under impression that changing governor while screen on/off triggers all cores to be online.

I was wrong, this commit fixed that:

https://github.com/neobuddy89/hammerhead_kernel_caf/commit/e13ec905cc4dfa36769595007138cd8535e63279

So, you may choose screen off governor to whatever you like.
[Nexus 5 Original Android Development] topgeardave:
Flash this torch:

https://www.dropbox.com/s/wlu8b8zphswhnna/Torch10.2.zip

Will be fine afterwards
[Nexus 5 Original Android Development] ngydna:
What's better for battery life? Intellidemand or smartassH3?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] GragonV:
I see :(, thank you

So sad since vanir is still my best rom due to it's amazing useful added features (especially the quick title)

any recommended rom btw :P
[Nexus 5 Original Android Development] A_Button117:
I like DroidKang

Studying Computer Science and Forensic Science @ UCO

Using XDA Premium 4
[Nexus 5 Original Android Development] topgeardave:
Kernel has neither. And I would say of the two intellidemand
[Nexus 5 Original Android Development] XeYex:
Thank you a lot :good:

I hope it will help :D
[Nexus 5 Original Android Development] neobuddy89:
Wow.. it's long time since last nightly...

Here is next nightly:

Download HERE

Chaos-Kernel_v11.0-[02-21]-[03-00]

* Update linux version to 3.4.81

* Removed interactiveF and intellidemand governors (both were creating chaos within chaos)

* Clean up audio codecs (better sound)

* Remove old Frandom driver and update Random driver with backported updates

* Improve MSM_Hotplug driver - less aggressive at screen on/off events

* Fix flash light adding over white to picture in low light mode / Sync with LGE-CAF

* Update misc drivers

* Update BFQ to v7r2

* Misc updates and fixes from CAF

* Update Piereligio TrueRGB color profile to v5

* Add input boost controls to NXTweaks (Don't mess with it unless you are sure else you may slow down your device)

* SELinux updates from Google kernel-common branch, CAF and upstream

* Blah blah blah - no one is reading changelog

Tested on DKv19 with default settings.

Reviews welcome.
[Nexus 5 Original Android Development] expertzero1:
Is this the same one that was posted last night ? Bluetooth is still wonky. Connects then screen becomes non responsive. Have to hard reboot to connect.
[Nexus 5 Original Android Development] neobuddy89:
This is different from last night with lot of config changes.

Please test on this one and share logs if any issue.

I have ordered a bluetooth headset to test this issue as well.
[Nexus 5 Original Android Development] Silentbob999:
We read blah blah

Tapatalked with SlimKat NexusFive
[Nexus 5 Original Android Development] Vanhoud:
What's interesting for me is that I no longer lock up via bluetooth with the latest nightly
[Nexus 5 Original Android Development] neobuddy89:
In last night build, a SELINUX config was misconfigured which created issues like partitions were mounted with null options.

So as bluetooth can be one of effect of this. This misconfiguration has been fixed in latest nightly.

Have you tested?
[Nexus 5 Original Android Development] Jur1nator:
I actually love the changelog Bla Bla Bla :D
[Nexus 5 Original Android Development] Akeel1994:
is the battery drain fixed on this build?
[Nexus 5 Original Android Development] expertzero1:
Bluetooth is fixed wooo
[Nexus 5 Original Android Development] mo976:
I think the blah blah is the best new kernel feature...?
[Nexus 5 Original Android Development] A_Button117:
Ya blah blah has increased my battery life.... But seriously, [MENTION=3795148]neobuddy89[/MENTION], no problems here with the latest nightly on DK v19, thanks :)

Studying Computer Science and Forensic Science @ UCO

Using XDA Premium 4
[Nexus 5 Original Android Development] Vanhoud:
Yes, works as it should now thanks
[Nexus 5 Original Android Development] neobuddy89:
Thank you all for reviews.

Another nightly before anyone asks.

Chaos-Kernel_v11.0-[02-21]-[10-49]

* Update Video playback driver from CAF (Sync with CM11)

* Update Video driver from CAF to handle memory overflow.

* Fixes for Faux Sound app - Thanks [MENTION=4152171]myfluxi[/MENTION] (This app is not recommended yet since we have inbuilt sound control)

I will be adding master switch to NXTweaks Sound Control section just like one in Voltage Control.
[Nexus 5 Original Android Development] neobuddy89:
---- Duplicate message removed -----
[Nexus 5 Original Android Development] mathew1234:
Yeah!!! Finally because of the latest update, I can watch Facebook videos without a problem....
[Nexus 5 Original Android Development] manny05:
Hoping this fixes the bluetooth problem where once it connects my screen freezes.

Edit : dam problem is still present in the latest nightly :/ do you want a kernel log?
[Nexus 5 Original Android Development] topgeardave:
Flash latest nightly or a euroskank nightly
[Nexus 5 Original Android Development] manny05:
I did. I'm on the latest nightly and it's still happening. But which euroskank nightly are you referring to? I'm not familiar with that kernel
[Nexus 5 Original Android Development] topgeardave:
It's a separate build of cm where certain bits are cherry picked to fix the rom like bluetooth.
[Nexus 5 Original Android Development] manny05:
Where can I find it at?
[Nexus 5 Original Android Development] topgeardave:
http://xdaforums.com/showthread.php?t=2528235

[CM11] [KitKang] Hammerhead Nightly Kangs

Before that try the stock cm kernel and see if it's the same. If not then the kernel will definitely be at fault. If it is the same try euroskank
[Nexus 5 Original Android Development] manny05:
I'll give it a try. But I'm pretty sure it's the kernel. I been using this kernel for a month now and it just started happening with the last couple of nightlies. I'm using Droid Kang Btw
[Nexus 5 Original Android Development] topgeardave:
Oh use the kernel before the 8th, DK hasn't been updated in ages
[Nexus 5 Original Android Development] Vanhoud:
Just had a reboot while watching YouTube videos

https://www.dropbox.com/s/yuqz6m6z1xwhpk6/chaos_last_kmsg
[Nexus 5 Original Android Development] willybarca:
is this intelliactive different to faux one, because this kernel ramps to the max freq a lot even while on home screen, and yes I have disabled the cpu boost , also is there anyway to control the Governor
[Nexus 5 Original Android Development] expertzero1:
i think you should be able to control it using trickster if anything -_- maybe havnt really tried it yet tho
[Nexus 5 Original Android Development] neobuddy89:
Did you tried 3 or 3.1?? Its not even a day since both are released and lot of WiFi fixes were included.

Till now kernel aimed merging available features and latest of code. I will look into where we can get more juice. :)
[Nexus 5 Original Android Development] bilago:
I installed your kernel yesterday morning and had my device @ 100%. Did not touch my phone the entire day at work. Got home and used the phone for a few minutes. Went to sleep with 60% battery. Woke up 6 hours later at 35%, went back to sleep and woke up 4 hours later at 20%. Checked the battery stats and Wifi was the #1 culprit, SOT was only at around 14 minutes.

With Franco's Kernel I literally lose 1-3% of battery overnight, but he doesn't support CM11

Edit: Since you just updated to 3.1 I guess I'll give it another go , but on stock this time once I charge my phone up. I'll let you know how it goes :)
[Nexus 5 Original Android Development] neobuddy89:
And one more thing, kernel solely doesn't play role of battery drain, but yes we will get it tamed whatever we can.
[Nexus 5 Original Android Development] DesignGrits:
So, does anyone else get this when they click on the download button on the host download site for this kernel? I'm trying to figuire out if it is the site, or dolphin browser, or i'm clicking on the adds by mistake, or something.
[Nexus 5 Original Android Development] lomniom:
Where is the maximum-minimum CPU scale in the NX app? I used to limit my max to 1.7 Ghz to economize the battery, as I don’t play games on my phone.
[Nexus 5 Original Android Development] Incredible_Culp:
BAHAHAHAHAHAHHA!!!!!!!!! :laugh::laugh::laugh:

Was going to say something about that post, but I'm glad I didn't cause your reply was way funnier :good::highfive:
[Nexus 5 Original Android Development] Jur1nator:
Jup it's ads or some ****ty software you don't want..
[Nexus 5 Original Android Development] Mtk87:
Sorry, no kernel support!

Hi,

after having some problems with the phone i made a complete reset of the device, after having back my out-of-the-box like nexus 5 i proceeded with OTA sideload installation to have a pure 4.4.1 without recovery or root, then installed twrp recovery and rooted.

After this I proceeded in downloading the kernel and installing it via recovery, installation went fine and 3.1 kernel is now in place but the NXtweaks app says that the kernel is not supported so I can't tweak it.

Did i do something wrong with the installation steps?

Thanks in advance for the help :)
[Nexus 5 Original Android Development] neobuddy89:
OTA? Kernel doesn't provide Superuser app since Cyanogenmod has inbuilt and other Roms are gifted SU by their chefs.

You need to flash SuperSu zip.

And then flash kernel.
[Nexus 5 Original Android Development] pert_S:
So far so good, no rogue WIFI problems here.

At 38% after 11h 20m with 2h46m SOT heavy usage.

It's pretty good.

On v3.0

Going to flash v3.1 after next charge :good:
[Nexus 5 Original Android Development] Mtk87:
I totally restored my phone (no data on it, totally blank), installed the ota (with adb sideload update.zip on the stock recovery) , the twrp recovery, gained root by installing the superSU.zip and then installed kernel. My rom atm is a rooted (with superSU) stock