Database Develop

[Q] Linux scheduler optimization works miracles

Way above my skill-set. But when you near 45, I think you tend to get that way.
Seriously, if this could be used on our SGS, can it make for a smoother scrolling experience?

I'll try to merge this patch to the currently used kernel source and see what happens.

Had the low latency patch applied and running for a while since.
Need some changes to get it in Android kernel, but nothing drastic, and judging by the code in tty_io.c, groups are created as per tty, would not work on Android, needs manual grouping, and have not seen any improvements though.
Not worth the trouble.
IMHO, scheduler isn't really the issue here, unless you're running a few CPU intensive programs in background, to which isn't the Android's way of doing things, you would be sharing the CPU intensive foreground app resource with background app, that has neg effect, things get slower instead.
"Low latency, the more responsive UI gets." statement maybe true but UI's 'responsiveness' has more than just a low-latency kernel to it.

[MOD] IncrediControl - Easy GUI Voltage Control

Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. The tab will not show up if your kernel does not have these features. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the voltage adjustment that the kernel you are using has either the HAVS or SVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229

Thanx for sharing!
Keep up the good work!

IncrediControl v1.3
Major changes include:
Ad Free has now been turned into a key that removes the ads from the free version. This allows donors who have downloaded the ad free version from the site to update through the market.
HAVS voltage checking. Minimum voltages can no longer be set higher than maximum voltages.
Boot voltages are now stored in the application’s data directory. Boot settings will now persist if you update your ROM or restore the application and data from a backup.

Been having trouble with this app...
The voltages dont Stick.
Nor is there any real way to see if your adjustments are stable or not...
Also... I am getting values that are not shown in setcpu.

Maedhros said:
Been having trouble with this app...
The voltages dont Stick.
Nor is there any real way to see if your adjustments are stable or not...
Also... I am getting values that are not shown in setcpu.
Click to expand...
Click to collapse
You have to click apply to set the voltages. If you want the voltages to be applied on boot, you have to check set on boot and then click apply. The check on boot box will never be checked when you start the app. Instead there is text that tells you if you have boot settings or not. This is a failsafe so users don't habitually leave the box checked, adjust voltages too low, click apply and end up in a boot loop.
It's impossible to see if the adjustments are stable or not without running them on your phone. Every phone is different, even two phones of the same model. The only test for instability is stressing your phone at each frequency and seeing if it locks or not.
The SVS adjustment shows all frequencies the phone can support. Whether or not your phone ever uses the frequency is dependent on the governor and kernel that you are using

IncrediControl v1.4:
This is mostly a bug fix release but I have also added:
Automatic detection of the minimum and maximum voltages supported by your kernel
Unless any more bugs arise, the next release will have some new goodies to play with...
http://www.incredikernel.com or from the market.

We don't have any havs kernels for now.
Sent from HydrOG3N MOD DHD.

also supports the DeamonOC?

Paradoxxx said:
We don't have any havs kernels for now.
Sent from HydrOG3N MOD DHD.
Click to expand...
Click to collapse
Yeah, it seems only qsd8x50 processors have HAVS, others seem to all be SVS. The app supports both though.
DubelBoom said:
also supports the DeamonOC?
Click to expand...
Click to collapse
I'm unfamiliar with DeamonOC, can you clarify what it is for me?

[Q] Q - Which CPU governor to use.

Does anyone know what the difference between the various CPU governors and I/O schedules are? The recommendations I see vary a bit, but there's never any explanation, beyond "this is what I use, seems good". Thanks!

Horror Business said:
Does anyone know what the difference between the various CPU governors and I/O schedules are? The recommendations I see vary a bit, but there's never any explanation, beyond "this is what I use, seems good". Thanks!
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/showthread.php?t=2017715
For Motorolas, you have to add MotoHotPlug and/or HotPlug governors, which seem to be similar to Interactive, albeit even more aggressive rampup of speed.
For grins, I'll run 3D mark / ice storm (regular) with the various Governors. Here's the results thus far:
CM10.1.2
Hotplug: 1926
Interactive: 1721
OnDemand: 1711
When I have time I'll run it in Icarus / stock and see if it makes a difference.

[CM10] (5Feb13) NC Performance (and) Placebos

After getting a little annoyed at the runty, poorly mapped-out, scratchy thicket of real and imagined performance tweaks, I decided to embark on a semi-long term project to determine what's real and what's "zomg mega-booster performance pills".
First project was to evaluate existing performance options on stock CM10 for actual gains using experimental design. (tl;dr: for those geeky enough to want to know, it was a main effects only d-optimal design with 32 design points for the 16 parameters listed, including several lack-of-fit and pure-error replicates. I could go on, but do you really want me to?). I ended up with a list of 16 parameters all together, from the Developer Options and Performance settings, based on their showing up in various performance tweaks discussions.
The main challenge was finding a way to measure actual performance instead of perception. I settled on several benchmarking tools: Antutu, Quadrant, SQL Benchmark, and Chainfire's benchmarking app. One of the parameters being tested ("don't keep activities") actually breaks Antutu at the graphics testing step, so I'm not reporting anything from Antutu.
All told, out of the 16 parameters tested, only 9 showed any kind of effect whatsoever, and combining best settings for all 9 simultaneously, total performance only boosted by ~20%, of which fully half was due to switching max speed from 1000 to 1100. this means the other 8 settings combined for a total boost of ~10%, meaning individually they're peanuts. The remaining 7 settings that showed no effect are only so much fluff and unlikely to do a thing for you performance-wise.
Results are summarized below for your reading/teeth-gnashing pleasure:
Max Speed (1000 versus 1100): Very clear, notable difference between the two settings on all benchmarks. This is the expected result, about 10% improvement in all benchmarks on average. Recommendation: set max speed at 1100.
Governor (convservative vs interactive vs ondemand): This only had any impact on Quadrant benchmark, no other benchmarks appeared to care. In Quadrant, conservative was the worst overall, while interactive provided an ~ 5% boost and ondemand gave ~6% boost. Recommendation: use ondemand.
Scheduler (BFQ, CFQ, noop, deadline): I don't know what schedulers do or the differences between these settings, but the only place they had any effect at all was in the SQL benchmark. There were clear differences here though: BFQ was by far the worst. CFQ and deadline were about the same with a 17% increase in SQL activity performance. noop was the best with ~ 20% increase in SQL activity performance. Recommendation: use noop. [update: some have reported stability issues with noop. If thus us the case for you, CFQ would be the next best choice]
Zram (disabled, 18% default, 26%): Zram effects only showed up in Chainfire's benchmark app, specifically for Java activities. Default 18% setting performed worst but disabled setting wasn't significantly different. 26% setting gave a 4% boost, but again, only for the java-specific benchmark. Recommmendation: use 26% setting.
16-bit transparency (off or on): Turning on the 16-bit transparency setting gave a smallish 3% boost to Chainfire's java benchmark. It did not have a measureable effect anywhere else, and I did not visually see any differences anywhere during testing. Recommendation: turn on 16-bit transparency.
Kernel same-page merge (off or on): This had a *negative* effect when turned on, resulting in a 1% performance hit on Chainfire's native benchmark. It did not have any measurable effect anywhere else. Recommendation: Keep off.
Don't keep activities (off or on): This was very problematic: it provided a distinct improvement in quadrant score (+8%) when turned on, but behaved poorly with other apps (Antutu being one). Since it didn't seem to help anywhere else outside of Quadrant and didnt' play well with others, recommendation is to keep off:
The following list are the settings that had no measureable impact anywhere. Any attempt to claim they have "zomg" status should be summarily whipped with placebo pills, or else they should let me know the exact details in which they supposedly work and I can test.
Placebo hall of shame:
Surface improvement (since it had no effect anywhere, why not just set it on banding/blur and have the best pictures?)
Background process limit
Disable HW overlays
Force GPU setting
Any of the animation scale settings (although they look snappier at lower settings, so it at least *feels* faster)
minimum speed (seriously? people think this has an effect? keep at 300 for best battery life)
Allow purging of assets
Hope you like this, y'all! Let me know if there's any other mad-scientist experiments you'd like to see.

Nicely done. How many times did you run each test? Or perhaps the results were very consistent.
FYI; regarding the governor, scheduler and the like, you may want to have a look at this thread;
http://forum.xda-developers.com/showthread.php?t=1369817
I think gives your tests / results some perspective as well.

Re: [CM10] NC Performance (and) Placebos
NCKevo said:
Nicely done. How many times did you run each test? Or perhaps the results were very consistent.
FYI; regarding the governor, scheduler and the like, you may want to have a look at this thread;
http://forum.xda-developers.com/showthread.php?t=1369817
I think gives your tests / results some perspective as well.
Click to expand...
Click to collapse
Thanks for the link. Very informative.
How familiar are you with factorial designs? All parameters were tested simultaneously in such a way that their individual effects can be partitioned out mathematically. That's what allows me to test all those settings with just 32 runs and still get solid estimates of their effects, and more importantly, the amount of variation around them (a requirement for distinguishing real effects from noise).
I suggest googling "factorial design of experiments" if you're interested.

skwalas said:
Let me know if there's any other mad-scientist experiments you'd like to see.
Click to expand...
Click to collapse
Here are some others you could try gauging:
Seeder
http://forum.xda-developers.com/showthread.php?t=1987032
V6 Supercharger
http://forum.xda-developers.com/showthread.php?t=1191747
Lagfix
http://forum.xda-developers.com/showthread.php?t=2104326
OOM/Sysctl tweaks
http://forum.xda-developers.com/showthread.php?p=34123854#post34123854
http://forum.xda-developers.com/showthread.php?p=34448792#post34448792

Re: [CM10] NC Performance (and) Placebos
Good suggestions. Before trying these third party tweaks would be good to know a few things from actual users:
Has anyone tried any combinations of these tweaks simultaneously? If yes, did they all play well together? If no, details please!
Some of these appear to have device specific settings, can anyone share settings being used on the NC?
I intend to sandbox these, as i have little desire to use then in real life just yet. Can anyone confirm that if i restore my current setup, the restore process will clean out whatever settings these tweaks out in place?
Speaking for all scientists, thank you kindly!

skwalas said:
Good suggestions. Before trying these third party tweaks would be good to know a few things from actual users:
Has anyone tried any combinations of these tweaks simultaneously? If yes, did they all play well together? If no, details please!
Some of these appear to have device specific settings, can anyone share settings being used on the NC?
I intend to sandbox these, as i have little desire to use then in real life just yet. Can anyone confirm that if i restore my current setup, the restore process will clean out whatever settings these tweaks out in place?
Speaking for all scientists, thank you kindly!
Click to expand...
Click to collapse
Have only used V6, from my experiences, restoring a Nandroid or flashing a new nightly will clean out everything it changes other than the files you store on the SDcard. This post details how I set it up http://forum.xda-developers.com/showpost.php?p=34991382&postcount=1234
I never really noticed a huge performance boost from V6, it did reduce the lag that was in the Beta's and early nightlies, mostly seemed to keep memory available and avoid the lag issued in the early builds. Have not used for the last few weeks since performance has improved on the newer builds.

Re: [CM10] NC Performance (and) Placebos
I set all recommendations. I get back to you in a couple of days. I am running 20130120 nightly
Sent from my NookColor using Tapatalk HD

Thank you!
Thank you for your measured and logical approach and recommendations! It is appreciated. I have experimented a little with the third party tweaks and haven't found any that fascinating, honestly.
When I install CM10.1, I also flash a script I made to customize to my preference and delete stuff I don't use like language modules, ringtones, quicksearch, boot animation, etc to free up some RAM. Between that and killing memory hungry apps when I'm done, my old Nook is still holding on reasonably well.

Re: [CM10] NC Performance (and) Placebos
Skwalas:
Got to tell you, your suggestions on settings are paying off. My nook is smooooooth. Is working ok there is sometime that lag liittle bit, but my p3113 also doing the same. I will stay with this 0120 nightly for a while with your settings on perfomance. .
I will report later how i am doing
Sent from my NookColor using Tapatalk HD

Re: [CM10] NC Performance (and) Placebos
performance is ok....
Sent from my NookColor using xda app-developers app

Re: [CM10] NC Performance (and) Placebos
Sometimes mook freezes and I have to leave it until it settles. The rest of the time works good
Sent from my GT-P3113 using Tapatalk HD

Re: [CM10] NC Performance (and) Placebos
Ok. Today my nook wakeup crazy. Rebooted, but it stays changing from settings , battery and some icos. It llok like it retains some touches i did to the screen and created like a loop. I have to rebooted again. Then i change the io scheduler to cfq.
Sent from my NookColor using Tapatalk HD

Re: [CM10] NC Performance (and) Placebos
Lakland said:
Ok. Today my nook wakeup crazy. Rebooted, but it stays changing from settings , battery and some icos. It llok like it retains some touches i did to the screen and created like a loop. I have to rebooted again. Then i change the io scheduler to cfq.
Sent from my NookColor using Tapatalk HD
Click to expand...
Click to collapse
Would be hard to know what is settings specific and what is hardware or OS specific. I've had no issues with the settings as described, so let us know if you are able to resolve your issues.

Re: [CM10] NC Performance (and) Placebos
skwalas said:
Would be hard to know what is settings specific and what is hardware or OS specific. I've had no issues with the settings as described, so let us know if you are able to resolve your issues.
Click to expand...
Click to collapse
I know and I am using your settings as a baseline, rigght now I change de io scheduler to cfq. Is working fine. Keep you posed and thanks!
Sent from my GT-P3113 using Tapatalk HD

Lakland said:
I know and I am using your settings as a baseline, rigght now I change de io scheduler to cfq. Is working fine. Keep you posed and thanks!
Sent from my GT-P3113 using Tapatalk HD
Click to expand...
Click to collapse
I have had erratic behavior from schedulers also, especially BFQ, NOOP is not bad, but have had better luck with CFQ.

skwalas said:
Zram (disabled, 18% default, 26%): Zram effects only showed up in Chainfire's benchmark app, specifically for Java activities. Default 18% setting performed worst but disabled setting wasn't significantly different. 26% setting gave a 4% boost, but again, only for the java-specific benchmark. Recommmendation: use 26% setting.
Click to expand...
Click to collapse
I'm surprised that zram enabled IMPROVED things. So between disabled, 18%, and 26% (no idea what default really is without digging in the code), 26% was the best option?
Interesting. I thought zram would improve multitasking (maintaining background activities) at the expense of potential slowdowns (compressed swap to ramdisk).

khaytsus said:
I'm surprised that zram enabled IMPROVED things. So between disabled, 18%, and 26% (no idea what default really is without digging in the code), 26% was the best option?
Interesting. I thought zram would improve multitasking (maintaining background activities) at the expense of potential slowdowns (compressed swap to ramdisk).
Click to expand...
Click to collapse
It might have that effect, but wasn't apparent in the benchmarks i used. It could be that a different benchmark is needed to detect it, or it could be the negative effects are too small to be measurable compared to the normal "noise" of operation.
Any ideas how we could measure this more explicitly, if there is any interest?

skwalas said:
It might have that effect, but wasn't apparent in the benchmarks i used. It could be that a different benchmark is needed to detect it, or it could be the negative effects are too small to be measurable compared to the normal "noise" of operation.
Any ideas how we could measure this more explicitly, if there is any interest?
Click to expand...
Click to collapse
Good question, I'd think it'd require some way to switch activities around and somehow measure their switch rates, but the environment would be quite difficult to keep consistent.
BTW thanks for the scientific work on this stuff, MUCH better than "OMG THIS TURNED MY TABLET INTO A UNICORN" posts we see a lot on tech forums.

skwalas said:
Any ideas how we could measure this more explicitly, if there is any interest?
Click to expand...
Click to collapse
Since it would help most when memory is low (like it ever isn't), running two memory hogs simultaneously should show an effect if there is one. A custom memory-hog app built under two different names, perhaps?
I have a shell script that creates a swapfile and enables its use that would also be well tested this way, since zram creates an in-memory swapfile. I was never able to see any tangible results except for the output of "free", so I don't use it anymore, and haven't tried it under CM10.1.
Sent from my NookColor using xda premium

[KERNEL] Discontinued: FusterCluck Kernel (39a) CM/AOSP/Stock

Disclaimer:
I'm not responsible for any damage caused to you or your device. If you lose your job because your phone fails to wake you up, I'll sympathize, but take no responsibility. If your phone turns into a transformer and destroys the world, don't point the finger at me. You are flashing this AT YOUR OWN RISK.
Click to expand...
Click to collapse
This should work on all CM/AOSP based roms, stock support has been re-implemented. Use of UKM for synapse to work (at all) requires init.d. Most stock based roms should have this, but a rooted OTA won't unless you added it (lots of methods, Google around a bit).
Hi Everybody. Since I haven't seen anyone making custom kernels yet for us for the 39A base, I decided I'd try pulling in some features that I use on a regular basis into the kernel source.
Most everything in this is pulled from ( in no particular order ) Faux123, Showp1984, flar2, Renderbroken, Dorimanx, Jackpotclavin, xdabbeb, Rashed, Myfluxi, franciscofranco, tsunamical and other sources. So, all credit goes to them.
I've switched over to Synapse/UKM for this, seems that most everything works properly in it. I've changed francosound slightly, so you'll need to use the modified UKM linked at the end of this post, then install synapse from the playstore.
Features:
Added Intelliactive, Intellimm, Smartmax, ElemantalX, Bacon, Imupulse, ZZmove, and Yankactive governors.
Added Intelliplug (Set as default through
Added FrancoFranciso's sound driver. (Mic, Headphone, Speaker, Camera Mic volume control)
Added 389Mhz GPU step
Enabled Extra I/O schedulers and TCP congestion methods
Enabled Kernel Same Page Merging.
All builds are permissive.
Added Bricked Hotplug
Added Bricked Thermal
Added UserSpace CPU Frequency Voltage Table
MsM Limiter from NeoBuddy89
FastCharge from Dorimanx
Added a post boot script that will provide tweaked defaults (basically what I use minus undervolting)
Exposed PVS and SPEED bin values to Synapse for informational purposes.
Misc Tweaks/Optimizations/Battery Saving Optimizations
Screen turn on bug fixed courtesy of JackPotClavin
Stock Builds should work correctly now. (bluetooth and back led issues should be corrected)
F2FS support
Known Issues:
None
I'll work on things as I get time, but I'm not promising anything as this is simply a kernel that I'm making for the features I typically use. A lot of code has changed in the new kernel source making it hard to import features, so it's slow going. Also, sorry for the kernel name, I didn't have anything creative at the time.
Source: Github
CONVERTING DATA TO F2FS WILL WIPE YOUR SDCARD DATA AS WELL. Ensure that you have a backup of everything on your computer before doing so as this is unrecoverable. For R3, with F2FS you'll want this repacked TWRP. It has this kernel packed into it, with better f2fs support libraries (thanks XDABBEB). Also, be aware that encryption is not currently enabled with F2FS partitions in the way that I have it configured.
Downloads:
R3 - Fixed Bluetooth and PowerManagerService.Display Wakelock
CM-R3-B3
Stock-R3-B3
*Caution with R3, I've been running F2FS on the CM build for a couple days now with now issues. Stock booted and mounted for me, but I couldn't find a tester to evaluate it.*
CM-R3-Build1
Stock-R3-Build1
UKM has also been updated (link below). No new functionality, just cleaned up some of the stuff that didn't apply to our phone.
Old Builds:
CM-R2-Build3
Stock-R2-Build3
Modified UKM: 3.8.1-Mod6-Fustercluck (Source) - Apb_Axel's Original Thread Huge Thanks to him for his work making UKM.
Remember to hit the "Thanks" if you're enjoying this kernel.

For anyone who wants to build from this, I've included the toolchain , ramdisk, and a build script in the github repo. As long you have a build environment setup, you should get a flashable zip in the zips folder just from running the included build.sh script.
*edit*
I've removed the toolchain and all git references to it. It was causing the repo to be far larger than it needed to be. It's easy enough to find a toolchain (I've been using sabermod) and place it in the directory the build script expects. The one I use is Sabermod 5.1
Edit:
Development will be halted as my g2 digitizer is failing and I'm likely to upgrade to a nexus 6.

This kernel is SORELY needed. Constantly torn between being on 5.1 vs. 5.0.2 or JB vs. KK aboot, etc. And now I finally feel like I can have it all. Thank you! Working great so far on Euphoria ROM.
Only suggestion would be making the kernel default to be selinux permissive, especially with Google pulling an Apple and banning many of the selinux modifying apps from the playstore.
Thanks again!

bbender716 said:
This kernel is SORELY needed. Constantly torn between being on 5.1 vs. 5.0.2 or JB vs. KK aboot, etc. And now I finally feel like I can have it all. Thank you! Working great so far on Euphoria ROM.
Only suggestion would be making the kernel default to be selinux permissive, especially with Google pulling an Apple and banning many of the selinux modifying apps from the playstore.
Thanks again!
Click to expand...
Click to collapse
Yeah, I'll put up a build that's permissive. But d-h.st is being a pain right now and not actually letting me upload.
I was going to write up a post about the dangers of permissive kernels, then saw avc denials for an init.d script, netmgrd, sensors.qcom, and busybox in my dmesg (of course I was going to check before I posted)...
Just remember though enforcing stops things from running out of context. It's a security features and that's why google's removing the apps that let you change it. Permissive lets everything do whatever it wants and just logs that it should have been denied (dmesg | grep "avc"). So essentially, it's like installing an antivirus on your computer then disabling it but letting the system tray icon give you a warm fuzzy. Antivirus is a bad analog because it's really more like user policies, but you get the point.
*edit*
for now, I'll just attach the permissive build to this post. I'll need to wait till d-h.st gets it together. Maybe, I'll look for a better file server.

Does this have Bacon or smartass? If not is it a possibility in the future?

Yeah, I'll work on grabbing them. I'll need to find a good version of bacon from somewhere though that hasn't been too tweaked/modified.
Also, I'm moving to androidfilehost. for hosting. d-h.st just wasn't working out. I'd like to find somewhere that gives ftp access so that I could just upload builds at the end of my build script, but I guess that's not a huge deal.
Anyway, the new folder will be: https://www.androidfilehost.com/?w=files&flid=29865
The build numbers are just there to help me keep track of what file I'm on and need to flash for testing, don't let them get you confused if there are missing numbers in that folder... they just weren't worth uploading, or the build failed.
Also, how is the fauxsound stuff working out for everyone? I feel like it's pickup up the register values wrong or something... I'm not quite sure yet. But the sound seems too quiet on the low-end, but at least boosting the high-end works.

Just gonna throw this out there since you arm like a hands on dev, what are your personal settings? Default? I'm super excited for this kernel but after using dori for a while, the feature creep became somewhat mind boggling.

BOY_ said:
Just gonna throw this out there since you arm like a hands on dev, what are your personal settings? Default? I'm super excited for this kernel but after using dori for a while, the feature creep became somewhat mind boggling.
Click to expand...
Click to collapse
I'm not really comfortable being called a dev, I have some understanding of what's going on but the real devs are the guys that I gave credit to in the OP. Really, I'm just pulling in their work and making little changes here and there to make it work.
Personally, I run intelliactive with intelliplug and westwood with zen set to 1024 (why I added those) but I don't tweak the settings. I've never really seen a reason to, the governors are pretty smart. Of course, if you know what you're doing you can always fine tune them some based on your personal use types.
As far as feature creep... Read up on the different things. Figure out what works for you, ignore the rest. Really, it's just there because ya know... different strokes for different folks.

That's exactly the answer I was looking for. Thank you!

New build (30) up, sorry for the number jump... took a good few build tries getting the governors to play nice.
This added Smartmax, ZZmove, and Yankactive.
Should also fix GPU freq reporting. Previously, it wasn't reading correctly.
*edit*
Seems some of these new governors don't play so nice under use, at least not for me. They govern, but it seems like my device is locking up or not turning the screen back on with them. Looks like they need a little polishing.

I am using Intelliactive as well, on Euphoria v1.1, which sticks, but Intelliplug does not.
Also, only Smartmax worked for me with the new governors, but the others rebooted my phone almost instantaneously.
~ Sent from my VS980 ~

360Razir said:
I am using Intelliactive as well, on Euphoria v1.1, which sticks, but Intelliplug does not.
Also, only Smartmax worked for me with the new governors, but the others rebooted my phone almost instantaneously.
~ Sent from my VS980 ~
Click to expand...
Click to collapse
Thanks for the feedback.
Yeah, I ended up just removing zzmove and yankactive for now but added bacon and impulse. I'm not sure what exactly is going on with those two, but they kept trying to switch the devfreq governor to one that I shouldn't have included to begin with, the calls it used I don't think are present anymore. Which could very well be the reason they were freezing.
The intelliplug is a little weird too depending on which tuning app you use. Synapse lets it stick, but never shows that mpdecision turned off. Kernel auditor shows both on, but trickstermod shows that it correctly. ...kinda weird and I don't trust the apps to be honest. The sysfs values for intelliplug is toggling and the mpdecision binary stops running (at least with trickster) so those apps could be doing any number of things wrong.

Thanks for continuing to tinker and your analysis. I just did a reboot and checked Kernel Adiutor and even the governor is not sticking. I will try Trickster, as I am used to that app, but agree with you, each can be doing something wonky with your kernel.
~ Sent from my VS980 ~

Phone feels faster after this kernel, loving that. As for synapse, it tells me no UCI support and that's the end of that. I found kernel adiutor and it seems to be alright. The headphone amp doesn't seem to want to change which is annoying since I really want that. I think I'm just gonna clean flash the next euphoria build. Congrats on the first kernel for 39a roms.

joedajoester said:
Phone feels faster after this kernel, loving that. As for synapse, it tells me no UCI support and that's the end of that. I found kernel adiutor and it seems to be alright. The headphone amp doesn't seem to want to change which is annoying since I really want that. I think I'm just gonna clean flash the next euphoria build. Congrats on the first kernel for 39a roms.
Click to expand...
Click to collapse
Yeah, the headphone poweramp is buggy. I still think it's an issue because I pulled Shamu's (Nexus 6) fauxsound. But you still get the volume boost with the headphone volume choice. For synapse to work at all on most kernels now you need to download and flash teh UKM script.
But yeah, there are still things that are buggy. Which is why I'm leaving this labeled as an alpha for awhile.
I've been working on governors most of the day, I'll reply here when I get an update posted.

Yeah, FauxSound thru the speakers just cuts in and out, mostly out.
Xdabbeb's 982.5 on ART for VZW LG G2

jesssiii said:
Yeah, FauxSound thru the speakers just cuts in and out, mostly out.
Xdabbeb's 982.5 on ART for VZW LG G2
Click to expand...
Click to collapse
That's odd, I listened to my phone through the speakers for a good few hours yesterday moving my inlaws. Didn't notice any cutting in and out.
Can you tell me what values you have in: /sys/kernel/sound_countrol_3/gpl_speaker_gain ?
I have "2 2" at the moment, but I have my speakers down... typically I've been holding them at "5 5"
Also, are you using anything like viper? Are you using this on a CM12.1 based 39a rom?
*edit*
Also, New build up. https://www.androidfilehost.com/?fid=96039337900114170
Removed a few of the unused Devfreq governors (for gpu).
Added ElementalX, Bacon, and Impulse Governors. Removed ZZmove and Yankactive
Changed some compile flags, might give better performance.
Misc tweaks.

Another Build: https://www.androidfilehost.com/?fid=96039337900114287
Added in Bricked Hotplug and Bricked Thermal.
I may be a bit slower on adding things and building the next couple days... weekends over.

Yoinx said:
Another Build: https://www.androidfilehost.com/?fid=96039337900114287
Added in Bricked Hotplug and Bricked Thermal.
I may be a bit slower on adding things and building the next couple days... weekends over.
Click to expand...
Click to collapse
You've been busy! So what is your setup now?
~ Sent from my VS980 ~

360Razir said:
You've been busy! So what is your setup now?
~ Sent from my VS980 ~
Click to expand...
Click to collapse
No different, I just prefer bricked thermal over the normal one. I usually set the temp limits 2 or 3 below the defaults.
I'm just trying to get the features added so that people have options. I sent faux a message, I don't really expect a reply because I'm sure he's pretty busy.... But figure is give it a shot to see if he can help with the faux sound issues.
Once that's worked out, everything should be fairly stable. Then I can try to figure out what's up with some of the tuner apps not recognizing things correctly.