Related
[KERNEL] [2.6.32.24] [HAVS] [BFS] [BFQ] KiNgxKernel #11/#11 "Con is an Artist"
I DO NOT have an HTC Evo, but would LOVE to have one for development, and am saving for one. Bear with me until then I just wanted to say thank you to the few who have donated. I am almost there, any help is appreciated!!! I plan to have my HTC Evo fairly soon
DO NOT FORGET TO READ THE ENTIRE POST ON MY SITE, THERE IS IMPORTANT INFO
So, just as the name implies, this is an Evo kernel with SVS (Static Voltage Scaling) & HAVS (Hybrid Adaptive Voltage Scaling.) A huge thanks to estes for the havs code and raven for being the first to implement it into the nexus kernel. What this does is provide SUPERIOR BATTERY life with stability to boot. Just flash the .zip in your favorite recovery image. Enjoy and post any bugs with a logcat please.
This is compatible with any 2.2 Sense ROM
Code:
Also, a little info on HAVS and AVS:
The purpose of HAVS is to minimize the power used by the CPU by determining
and setting the optimal voltage. At the same time, the maximum voltage by
which HAVS can scale to is fixed to a specified voltage depending on the
CPU frequency in order to prevent scaling to a higher voltage than what is
normally used at a specified voltage. The optimal voltage is actively determined
for each frequency and temperature. HAVS actively adjusts the CPU voltage as the
CPU frequency and temperature changes.
Code:
While we are at it, some info on BFS:
What is BFS(Brain **** Scheduler):http://ck.kolivas.org/patches/bfs/sched-BFS.txt
FAQS about BFS:http://ck.kolivas.org/patches/bfs/bfs-faq.txt
nugzo said:
I have full adb. I didnt have it when i upgraded from previous king kernels. Had to do a full wipe. Reinstalled rom and installed kernel before rebooting. adb works perfect. full access.
Click to expand...
Click to collapse
ENJOY!
Credits: Cyanogen, Netarchy (epson fps panel fix), toastcfh, ffolkes - all for bits of their code (see changelog), Koush for his any kernel .zip, AssasinsLaminent (nova fix), and most importantly, HTC for their kernel source
Download: CFS Kernel #11 & BFS Kernel #11[/URL] Date: 10/28/10 9:40 PM PST
If you Like my work follow me on twitter:
All my code is on github:
I am not responsible for anything that happens to your device
ChEeRs
BFS Changelog
Kernel #11
- HAVS is now OUT. We are not currently using it
- Using SVS for voltage regulation at the moment
- Battery life should be great now
- I forgot about an awful lot of longs and ints that will overflow on 32 bit now with u64 deadlines. Fix them.
- Add some macro tidiness
- Make sched_clock sanity checking robust and standardised, using jiffy
difference as upper limit, and use nominal 1us when difference cannot be
trusted.
- In layman's terms these are all MAJOR fixes to his BFS scheduler
- These fixes will provide a performance and stability boost
- Higher clockspeeds are more stable!
- More I will add
Kernel #10
- Performance boost!
- More stable due to BFS overhaul
- Patched up BFS scheduler to BFS 330
- Patched in *NEW* BFS TEST patch that applies over 330 (from CKolivas himself)
* Major overhaul of queued changes
* Micooptimise multiplications/divisions to be shifts where suitable
* Drop the "skip_clock_update" concept as we update the niffies each time we
update the rq clocks, thus we want to update it more often
* Add a local last_task variable to each runqueue which keeps a copy of the
last non-idle task that ran on this CPU. Use this value to determine that a
task is still cache warm on this CPU even if it has run elsewhere in the
meantime. This improves throughput on relatively idle systems with >2 logical
CPUs
* Change SCHED_BATCH tasks to refill timeslices and reset deadline every time
they're descheduled as they've been flagged as latency insensitive, likely
fully CPU bound tasks. This should decrease the impact running batch tasks
has on other tasks
* Bypass rechecking deadline when we know that prev will run again in schedule
* Change all deadline accounting to use nanosecond values
* Rework try_preempt
* MUCH MUCH more check my patch code if you please
- Voltage tweaks for stability
- Compiled with toolchain optimizations
- Neon optimizations this time around
Kernel #9
- Finally released
- Board files fixed to allow lower undervolt
- Undervolted to 825Mhz for safe frequencies
- Higher clockspeeds WILL be more stable now
- Compiled CIFS module per request
- Regulator tweaks
- Removed some bloat
- Now using ondemand governor by default, feel free to change it
- Battery charging tweaks (like my inc kernel)
- You guys are going to like this one
Kernel #8
- Reverted BFS Scheduler to 318
- Reverted GPU changes causing stutters
- Other minor fixes
Kernel #7
- Updated BFS Scheduler all the way up to 330
- MANY fixes to HAVS code *thanks for some of them netarchy*
- Regulator being properly used now
- Usleep fixes for sleep mode *via nnode*
- Longer battery life as a result of these major changes
- Volume boost tweaks
- Torture test disabled
- Torture test support disabled
- More I will add
Kernel #6
- Minor code cleanup
- Now undervolted to 825Mv! *Longer batter life*
- Ksgl tweaks for performance
- Higher clock speeds should now be more stable
- Wifi module tweaks
- Other things I will add
Kernel #5
- Rpc changes/tweaks
- V4L2 code disabled now for media interface
- Vmalloced tweaks via @cyanogen *PERFORMANCE BOOST*
- Tweaks for stability
- More I will add
Kernel #4
- BIG update
- Code cleanup
- Undervolted even more (Battery life is LONG)
- Compiled with neon optimizations
- Conservative governor threshold tweaked (via netarchy)
- Conservative Governor sampling rate tweaked per user request
- GPU edits for performance
- 5MB of memory reserved for the Adreno GPU
- Kernel will boot faster as a result of "set read ahead" changes
- Various wifi module tweaks
- Packet Filtering set to turn off after 1s
- Bluetooth sleep bug fixed *via kmobs via kernelzilla*
- More I will add
Kernel #3
- Added BFQ I/O Scheduler
- Default scheduler is bfq
- Fixed atomic functions in bfq *thanks cyanogen and co*
- Cleaned up/removed unneeded code
- HAVS is still included and functioning
Kernel #2
- Updated BFS Scheduler all the way up to 318
- Manual patches made by me to successfully get it working 100%
- Minor bug fixes
- Things I'll add
Kernel #1
- Fresh sources
- FAST
- Based off of CFS Kernel #7
- Applied BFS 313 (Brain **** Scheduler by Con Kolivas)
- HAVS implemented
- Minor bug fixes
CFS Changelog
Kernel #11
- Kernel now patched up to 2.6.32.24
- Bug fix causing battery drain
- Reverted some UV levels causing instability
- CFS updates
* Implement different treatment for idle shares
* Fix CFS 'Over-scheduling' bug
* sched: Fix granularity of task_u/stime()
* sched, cputime: Introduce thread_group_times()
* sched: Fix select_idle_sibling()
* sched: cpuacct: Use bigger percpu counter batch values for stats counters
* sched: fix racy fair sched*trq
* sched: Cleanup select_task_rq_fair()
- EXT4 support now!
- EXT4 compiled as a module
- EXT4 filesystem bug fixes
* ext4: Fix potential quota deadlock
* ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode
* ext4: fix memory leaks in error path handling of ext4_ext_zeroout()
* ext4: Prevent creation of files larger than RLIMIT_FSIZE using fallocate
* ext4: Ensure zeroout blocks have no dirty metadata
* ext4: Consolidate inlign pages
- CIFS bug fixes for stability and security
* cifs: Fix a malicious redirect problem in the DNS lookup code
* cifs: don't attempt busy-file rename unless it's in same directory
* cifs: remove bogus first_time check in NTLMv2 session setup code
- Netfilter IPv6 bug fixes
- Memory leak fixed in firmware
- CPU Governor fixes
- Mutex bug fix
* mutex: Don't spin when the owner CPU is offline or other weird cases
- Using xen_clocksource_read now for scheduler (part of 2.6.32.18 patchset)
- vmscan: raise the bar to PAGEOUT_IO_SYNC stalls
- SLAB fixes
- drm: Only decouple the old_fb from the crtc is we call mode_set*
- arm fixes: arm: fix really nasty sigreturn bug
- RDS memory leak fixed
- mm: page allocator: update free page counters after pages are placed on the free list
- mm: page allocator: calculate a better estimate of NR_FREE_PAGES when memory is low and kswapd is awake
- So much more, check my code if you please
Kernel #10
- Patched up to Linux Kernel version 2.6.32.17 (all commits an android kernel would need, no extra bloat) *All credit goes to the linux project, check my github for authors please*
- CFS updates
* Implement different treatment for idle shares
* Fix CFS 'Over-scheduling' bug
- EXT4 support now!
- EXT4 compiled as a module
- EXT4 filesystem bug fixes
* ext4: Fix potential quota deadlock
* ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode
* ext4: fix memory leaks in error path handling of ext4_ext_zeroout()
* ext4: Prevent creation of files larger than RLIMIT_FSIZE using fallocate
* ext4: Ensure zeroout blocks have no dirty metadata
- CIFS bug fixes for stability and security
* cifs: Fix a malicious redirect problem in the DNS lookup code
* cifs: don't attempt busy-file rename unless it's in same directory
* cifs: remove bogus first_time check in NTLMv2 session setup code
- Netfilter IPv6 bug fixes
- Memory leak fixed in firmware
- CPU Governor fixes
- Mutex bug fix
- Using xen_clocksource_read now for scheduler (part of 2.6.32.18 patchset)
- Much more I will add
Kernel #9
- Board files fixed to allow lower undervolt
- Undervolted to 825Mhz for safe frequencies
- Higher clockspeeds WILL be more stable now
- Compiled CIFS module per request
- Regulator tweaks
- Removed some bloat
- Now using ondemand governor by default, feel free to change it
- Battery charging tweaks (like my inc kernel)
- MANY fixes to HAVS code *thanks for some of them netarchy*
- Regulator being properly used now
- Usleep fixes for sleep mode *via nnode*
- Longer battery life as a result of these major changes
- Volume boost tweaks
- Torture test disabled
- Torture test support disabled
- Ksgl tweaks for performance
- Higher clock speeds should now be more stable
- Wifi module tweaks
- More I will add
Kernel #8
- Added BFQ I/O Scheduler
- Default scheduler is bfq
- Fixed atomic functions in bfq *thanks cyanogen and co*
- Cleaned up/removed unneeded code
- HAVS is still included and functioning
- Code cleanup
- Undervolted even more (Battery life is LONG)
- Compiled with neon optimizations
- Conservative governor threshold tweaked (via netarchy)
- Conservative Governor sampling rate tweaked per user request
- GPU edits for performance
- 5MB of memory reserved for the Adreno GPU
- Kernel will boot faster as a result of "set read ahead" changes
- Various wifi module tweaks
- Packet Filtering set to turn off after 1s
- Bluetooth sleep bug fixed *via kmobs via kernelzilla*
- Rpc changes/tweaks
- V4L2 code disabled now for media interface
- Vmalloced tweaks via @cyanogen *PERFORMANCE BOOST*
- Tweaks for stability
- Now undervolted to 825Mv! *Longer batter life*
- Ksgl tweaks for performance
- Higher clock speeds should now be more stable
- Wifi module tweaks
- More I will add
Kernel #7
- Added new CPU Governor - 'Interactive Governor' thanks Mike Chan @google
- Still using Conservative Governor
- Now overclockable to speeds up to 1.26Ghz (Not all phones can run 1.26, if your phone locks up, OC lower)
- Bluetooth tweaks (double check that bluetooth works for me please)
- Even more undervolted
- Wireless 'n' support
- Switched to 'cfq' scheduler
- Open VPN Modules
- Other things I will add
Kernel #6
- Overclocking should be 100% functioning
- SetCPU works now
- Overclockable up to 1.113 (Will raise this number soon )
- Added CPU Governor "OnDemand"
- Added CPU Governor "UserSpace"
- Added CPU Governor "Performance"
- Added CPU Governor "Conservative"
- Default CPU governor changed to "Conservative"
Kernel #5
- Five point multitouch (thanks for the code ffolkes)
- ADB working for most.... (wierd)
- Speed tweaks
- CPU Governors updated
- CPU tables updated
- Code is live
Kernel #4
- Much faster
- Much smaller kernel, removed all bloat
- ADB should work now, let me know
- Overclocking should work, let me know
- Switched scheduler to deadline
- More audio tweaks (per request, I forget who asked)
- Included a slew of modules, should cover any module you'd need
- More I will add
Kernel #3
- OC capability should work via terminal
- Netfilter (Wifi tether) built into the kernel
- Added OnDemand CPU governor
- Added UserSpace CPU governor
- Added Conservative CPU governor
- Default governor is currently OnDemand
Kernel #2
- Speed boost
- Five point multi touch support (believe this was ffolkes, thank you)
- FPS unlocked now! (thanks toast)
- Audio Boost Tweaks (LOUD)
- Integrated code to use 3 point for sensors that do not support 5 (thank you ffolkes)
- Kernel should work on CM6 now (let me know)
- Kernel should now detect screen arch on boot (thanks cyanogen)
- Should support both epson and n
- OC Capable now - up to 1.26 Ghz!
- Voltages lowered significantly for even better battery life
- Changed default scheduler to cfq
- Cleaned up unneeded code
- More I will add
Kernel #1
- First kernel for the HTC Evo
- Based off of the HTC source code - 2.6.32.12
- Added drivers for Static Voltage Scaling (SVS)
- Added drivers for Hybrid Adaptive Voltage Scaling (HAVS)
- Using CFS
- No OC capabilities as of now
- Cameras should work fine
- WiFI should work fine
- Bluetooth should work fine
- All things you would expect to work should be working, let me know
Any chance we could see some of the Desire's audio values in this kernel?
neckface said:
Any chance we could see some of the Desire's audio values in this kernel?
Click to expand...
Click to collapse
if I can find the code for it, yes.
You evo users have no idea what HAVS is like
I can't wait to see the feedback
kingklick said:
You evo users have no idea what HAVS is like
Click to expand...
Click to collapse
Well, for me, I have no idea what it is at all lol
Mind explaining what it does plz? =P
kingklick said:
if I can find the code for it, yes.
You evo users have no idea what HAVS is like
I can't wait to see the feedback
Click to expand...
Click to collapse
If you don't find it before I get home, I'll pm the directory to you.
And yeah, I haven't a clue what that is. Lol
This is interesting... any more details?
- Sent via my EVO 2.2 (Fresh 3.1.0.1) from the back seat of your Momma's car.
What on Earth is HAVS?
after a little googling...
Hybrid Adaptive Voltage Scaling (HAVS)
david279 said:
after a little googling...
Hybrid Adaptive Voltage Scaling (HAVS)
Click to expand...
Click to collapse
MMhhh can't wait to try this one out
Is FPS unlocked on this?
Does this work for all 2.2 roms?
bigant262 said:
Is FPS unlocked on this?
Click to expand...
Click to collapse
as of now, most likely not. It can easily be implemented
jaysmi32 said:
Does this work for all 2.2 roms?
Click to expand...
Click to collapse
YUP! should have no issues
If one was to push this to their device on top of whatever custom kernel/rom running.. would things start to get messy?
whats the best recommendation ?
kingklick said:
as of now, most likely not. It can easily be implemented
YUP! should have no issues
Click to expand...
Click to collapse
Thanks for the quick reply. I'll wait until you put it in. Will look forward to updates on this.
ok guys kernel is live =)
let me know if you have any other questions
I'm done playing for the day but I'm def keeping an eye on this thread. I can't wait to see some real world test results. I have a feeling this thread is going to blow up by the time I get up in the morning.
While I would absolutely love HAVS, I also don't want to lose the modifications in netarchy's kernel with the FPS cap unlocked. Any way you could possibly integrate that into your kernel?
An update.zip would be grand, too.
I have netarchy kernel 4.0.3a with Fresh 3.1.0.1... can i simply flash this over it?
- Sent via my EVO 2.2 (Fresh 3.1.0.1) from the back seat of your Momma's car.
cosine83 said:
While I would absolutely love HAVS, I also don't want to lose the modifications in netarchy's kernel with the FPS cap unlocked. Any way you could possibly integrate that into your kernel?
An update.zip would be grand, too.
Click to expand...
Click to collapse
Yup, if he sends me his code
HondaCop said:
I have netarchy kernel 4.0.3a with Fresh 3.1.0.1... can i simply flash this over it?
- Sent via my EVO 2.2 (Fresh 3.1.0.1) from the back seat of your Momma's car.
Click to expand...
Click to collapse
yes, use fastboot to flash the kernel itself, then adb push the modules
Disclaimer: By downloading and installing this kernel, you are assuming all risk. There are no implied warranties of any kind.
It seems to be working for me but try this at your own risk... Don't come crying to anyone here if you fry your phone... Don't overclock if you don't feel comfortable taking the risk!
This is based on Isaac's latest kernel code in his MIUI build with the OC tables and Voltage controls as in the CM7 kernel. All credit goes to Isaac, Tickerguy, b_randon14, Napstar, DoomLord, CyanogenMod and the Tiamat devs. If I missed anyone, let me know and I'll add it.
Instructions:
Flash Zip file in CWM.
mOCkv1.7.14
http://www.mediafire.com/?8p1n398mfd9w1fb
changelog:
mOCkv1.7.14.zip
A small update to bring this kernel in line with the cm9 kernel.
-Linux version 2.6.32.59
-updated to latest whyzor touchscreen driver
-includes most of Whyzor's kernel updates
-changed default io scheduler to sio
-changed default goveror to interactive
-does NOT use the same kgsl drivers as in the cm9 kernel. They decreased the performance in this GB miui.
mOCkv1.6.12.zip
- Allocated the extra memory to the GPU so HD games will play properly
- Updated Interactive governor with all of the latest updates from CM
and reduced the transition latency so it will transition faster.
- added Whyzor's wakelock fix to try and prevent times when deep sleep mode is never entered.
- added 2way calling patch. Thanks to avs333 for the patch and DoomLord for the port of the patch. I know that MIUI already has in-call recording but if you were using another ROM and already had the app, you can now use it in MIUI also.
Need to use CallRecorder app from skvalex or rVoix.apk from avs333. More info can be found on this thread on xda:
[DEV] Two-way call recording on Desire [ALMOST SOLVED][Sept. 7 update] - xda-developers
Here's the post by skvalex listing his latest trial version of CallRecorder:
xda-developers - View Single Post - [DEV] Two-way call recording on Desire [ALMOST SOLVED][Sept. 7 update]
Here's the market link for CallRecorder:
https://market.android.com/details?id=com.skvalex.callrecorder
I tested the CallRecorder app and the sound quality was excellent for a recording--if you're into that sort of thing. I did not test the rVoix.apk yet at this time.
- enabled 61 MHz clock frequency.
- Added lower voltage regulator settings down to 600. It looks like 600 is the min that our boards can go from what the specs look like.
- changed default IO scheduler to NOOP.
- reverted memcopy update.
mOCkv1.5-wip-6.zip
http://tinyurl.com/c74vzlj
- Updated for MIUI 1.11.25-11-30-11 build. Native WIFI AP should work properly.
- added a few more governors: InteractiveX, Scary, smartass, SavagedZen
- memory tweaks
- tweaked vmalloc allocation slightly - not as much as Isaac's HD fix though- so there should still be more available memory
- added Isaac's updated touchscreen driver
mOCkv1-wip-4.zip
http://tinyurl.com/c999gva
It's basically the same as the cm7 kernel but for MIUI.
- Added I/O schedulers cfq, vr, and sio. Go ahead and try them out if you want. I was able to set them using No Frills CPU control -- available free on the market.
Here's a link to a pretty good description of what seems to be most or all of the known available governors and IO schedulers in use in Android kernels by knzo at xda:
http://forum.xda-developers.com/showthread.php?t=1242323
Governor:
To sum up:
(in my (knzo's) humble opinion)
Battery: 1st place - InteractiveX | 2nd place - Smartass | 3rd place - SavagedZen
Performance: 1st place - Minmax | 2nd place - Smartass2 | 3rd place - SavagedZen
IO Scheduler:
To sum up:
(in my (knzo's) humble opinion)
Performance: 1st place - VR
Reliability: 1st place - Simple
-Enabled detailed frequency translation statistics just so I can see the detailed stats of frequency usage.
-Added SVS for voltage control. You can set the voltage in one of 3 ways:
1. manually edit the vdd_levels file in /sys/devices/system/cpu/cpu0/cpufreq/ using either adb or a file manager.
2. Set up a script and put it into init.d to set the file upon boot.
3. The simplest way - use the IncrediControl app to set the voltage. You can read about it from this post on xda and a download link is also provided there or download it from the Market:
http://forum.xda-developers.com/showthread.php?t=1201466
Thanks to b_randon14, chad0989, DoomLord, and Napstar whose code, posts, links and info helped a lot as well as the million posts from everyone that I read over the last few days...
- I'm using the following undervolt table on my phone in IncrediControl and it seems pretty stable; try out your own settings and see. The higher frequencies > 1.7 GHz would not undervolt for me without locking up and rebooting but your phone might fare better. I suggest that you DO NOT APPLY the settings on Boot until you are sure your phone is stable.
***If you undervolt too much and hose your phone, you can download this flashable zip in CWM to reset the Incredicontrol settings. Zip was provided by Incredicontrol site that is linked and I updated the script for the Triumph.
http://tinyurl.com/7g26rtp
More aggressive undervolting table:
Code:
61440: 675
122880: 700
245760: 750
368640: 800
460800: 875
576000: 925
652800: 975
768000: 975
806400: 1075
921600: 1125
1024000: 1175
1113000: 1175
1209600: 1175
1305600: 1225
1401600: 1225
1516800: 1275
1612800: 1275
1708800: 1350
1804800: 1400
1900800: 1475
2016000: 1500
Less aggressive table:
Code:
61440: 800
122880: 800
245760: 850
368640: 850
460800: 900
576000: 950
652800: 1000
768000: 1000
806400: 1075
921600: 1125
1024000: 1175
1113000: 1175
1209600: 1175
1305600: 1225
1401600: 1225
1516800: 1275
1612800: 1275
1708800: 1350
1804800: 1400
1900800: 1475
2016000: 1525
-set default max freq to 1024 MHz - hopefully oddball phones will now boot - thanks to b_randon and pwnyourace for the advice
-added 2 GHz frequency line - thanks to b_randon14, DooMLoRD, Napstar and FPX
-Changed default governor to OnDemand
-turned off kernel debugging
-added tun.ko support
-added cifs support as a module
-the cifs.ko module that you can unzip and copy to /system/lib/modules using adb or es file explorer or another file manager with root read/write access can be downloaded from here:
http://tinyurl.com/6rg4hqx
source:
https://github.com/mantera/triumph-kernel-msm7x30
ive never messed with over clocking...whats the steps after i flash the zip?
crxmax said:
ive never messed with over clocking...whats the steps after i flash the zip?
Click to expand...
Click to collapse
1. You can either download No Frills CPU -- free on the Market-- or SetCPU - paid on the market or also available on XDA (just do a search). These apps will allow you to change the clock frequency. I would suggest going up a little at a time and then run some benchmarking/stress testing to make sure your phone can handle that. Once you figure out what your phone can't handle, then drop down to a stable clock frequency that you're comfortable with. Remember, there's always a risk with overclocking.
2. If you also want to undervolt your processor, then download IncrediControl from the market or from the link in the OP and try changing your voltage. Don't set it to apply on boot until you are sure your phone won't have problems; and by problems, I mean force closes, reboots, lockups, etc.
V1.5 is released.
Updated OP:
changelog:
mOCkv1.5-wip-6.zip
- Updated for new MIUI version whenever that is available. Native WIFI AP should work properly.
- added a few more governors: InteractiveX, Scary, smartass, SavagedZen
- memory tweaks
- tweaked vmalloc allocation slightly - not as much as Isaac's HD fix though- so there should still be more available memory
- added Isaac's updated touchscreen driver
Updated OP.
changelog:
mOCkv1.6.12.zip
- Allocated the extra memory to the GPU so HD games will play properly
- Updated Interactive governor with all of the latest updates from CM
and reduced the transition latency so it will transition faster.
- added Whyzor's wakelock fix to try and prevent times when deep sleep mode is never entered.
- added 2way calling patch. Thanks to avs333 for the patch and DoomLord for the port of the patch. I know that MIUI already has in-call recording but if you were using another ROM and already had the app, you can now use it in MIUI also.
Need to use CallRecorder app from skvalex or rVoix.apk from avs333. More info can be found on this thread on xda:
[DEV] Two-way call recording on Desire [ALMOST SOLVED][Sept. 7 update] - xda-developers
Here's the post by skvalex listing his latest trial version of CallRecorder:
xda-developers - View Single Post - [DEV] Two-way call recording on Desire [ALMOST SOLVED][Sept. 7 update]
Here's the market link for CallRecorder:
https://market.android.com/details?i...x.callrecorder
I tested the CallRecorder app and the sound quality was excellent for a recording--if you're into that sort of thing. I did not test the rVoix.apk yet at this time.
- enabled 61 MHz clock frequency.
- Added lower voltage regulator settings down to 600. It looks like 600 is the min that our boards can go from what the specs look like.
- changed default IO scheduler to NOOP.
- reverted memcopy update.
Hey llorn.
Thank you for this excellent kernel. Have been using it on MIUI 2.2.3 on my MI-410.
Can you please compile it for MIUIv4 (ICS)?
I am using this rom
v1.7.14
changelog:
mOCkv1.7.14.zip
A small update to bring this kernel in line with the cm9 kernel.
-Linux version 2.6.32.59
-updated to latest whyzor touchscreen driver
-includes most of Whyzor's kernel updates
-changed default io scheduler to sio
-changed default goveror to interactive
-does NOT use the same kgsl drivers as in the cm9 kernel. They decreased the performance in this GB miui.
llorn said:
changelog:
mOCkv1.7.14.zip
A small update to bring this kernel in line with the cm9 kernel.
-Linux version 2.6.32.59
-updated to latest whyzor touchscreen driver
-includes most of Whyzor's kernel updates
-changed default io scheduler to sio
-changed default goveror to interactive
-does NOT use the same kgsl drivers as in the cm9 kernel. They decreased the performance in this GB miui.
Click to expand...
Click to collapse
anyone tested this on their GB roms yet? how is it?
Been using it for the last couple of days.
Working great.
Now that I am up and running back again, expect a MIUI gb update soon
@llorn
Please make a .35 kernel for MIUIv4 too.
That's like the only thing stopping me from trying out MIUI ics
Sent from my Spice MI-410 on my MIUI 2.4.6 port
Sorry if I repeatedly questions
But I want to know,,is this kernel support for mount linux swap and ext4 SD Card Partition?,,last tried I using MIUI 2.4.20 using this kernel,and got issue when mounting ext4 SDCard
Please anyone explain me about kernel details
Thanks
Hey guys. This is Badass Kernel, a modified version of AU Kernel with a little bit too many additions to fit in the Original Development section.
Logs are disabled in this kernel. This is not a bug, it's a feature.
Compatibility:
Android 4.2.2
CM10.1
AOSPA
PAC
AOKP
Android 4.0.4/4.1.2
CM9
CM9.2
AOSP
Touchwiz ICS V5
So.. new stuff:
1.0
CPU Undervolt down to (0-1-2-4-6).
A_U's bootsplash
Added Badass CPU Governor
Added Badass GPU control
Replace ZRAM LZO compression with Google Snappy compression which is a lot faster
Kernel Samepage Merging enabled by default
Writeback tweaked to do the work only when the screen is off
Added ROW I/O scheduler
Tweaked smartassV2 for more battery saving
Tweaked CFQ and Deadline
1.1
Added frandom support for CrossBreeder to finally work properly
Fixed memory leak in android binder
Restored and updated Lazy CPU Governor (expected: smooth UI, much better battery life and some lag in the first 20-30 seconds after boot)
Filesystem tweaks
Memory tweaks
Added SFB net scheduler and Veno TCP congestion algorithm for better use of internet
Disabled a lot of debugging
1.2
Implemented Dynamic Filesync and enabled by default
Proportional Rate Reduction for TCP
Correct AXI bus values for CPU
Re-added 825 and 844 MHz frequencies (be careful with these as they're not stable, they were left out with a reason)
Trimming /cache every 15 minutes if media playback is stopped.
Updated LowMemoryKiller driver (if you use ram manager or scripts for setting minfree, here are some really good values:3072,4096,12800,14336,15360,19200)
New bootsplash (HTC-alike)
1.2.1
Fixed Snappy
Further UV (0-1-2-3-6)
1.2.2
Enabled Compaction and linked it to LowMemoryKiller
Updated Deadline(now it's better than ROW)
Changed kernel compressor/decompressor from GZIP to the much faster LZ4.
Writeback tweaks from Linus Torvalds
Added TCP congestion algorithms: Hybla, Westwood, Highspeed-TCP. Default is Hybla because in tests, performed better than the rest.
1.3
Enabled Triple Buffering (component of Project Butter by Google)
Added Tiny RCU for smaller memory footprint
Added BoostPulse interface for SmartassV2
1.3.1
Added BoostPulse interface for SmartassH3 and updated it with a new variable(boost_freq) to suit the governors ramping policy
1.4
Lots of code optimizations
AHB Overclocking for faster R/W operations[787 MHz and higher don't have this kind of overclocking because of instability)
New 652 MHz undervolted frequency
CPU Unaligned Access (much faster booting time because of better kernel decompression)
Buffer values updated from Samsung original sources(Triple Buffering, Camera)
SmartassH3 and KSM parameters tweaked for better battery life
1.5
CPU clocks rework
Modified AXI Bus to allow lower CPU frequencies
Added completely stable 68 MHz frequency
New undervolt settings (0-0-1-2-3-5-6-7)
Rewritten Badass CPU and GPU control driver to make more use of 68 MHz frequency
Tuned SmartassH3 to make more use of low frequencies
Added fully functional zCache and ZsmAlloc, backported from 3.4 kernel
1.5.1
Added LowBattery Powersave feature for Badass governor
Badass parameters are more performance biased now
Recalculated Frame Buffer Size for Triple Buffering
Clean-up(remove deprecated CPU governors)
1.6
Add newest Adaptive RED Net Scheduler from 3.4 kernel and make it default.
Replace Snappy Compression with LZ4 Compressor(this is the fastest compressor on the market)
Make our kernel probably the first 2.6 kernel to have these two features
1.6.1
Update LZ4 Compressor from original sources and make it fully functionable
1.7
Replace zRam XvmAlloc with the better ZsmAlloc integration
Update zRam from 3.0 drivers
Make zRam LZ4 decompressor work faster in the same CPU cycles
1.8
Add SIOPlus scheduler (finally something equal or better than deadline)
Add CPU Idle driver to support C4 Deeper Sleep state
Add Wheatley governor to make more use of the new C4 state.
Change Bootsplash
1.9
New governor: WheatleyPlus
Reworked scaling down logic for less calculation
Added BoostPulse interface
Linked BoostPulse to the touchscreen driver (now the governor can really "sense" a touch and boost the frequency after a specific time threshold)
Added Triphasic scaling up logic from Badass (Phase2 is 360 MHz and Phase3 is 480 MHz)
Fixed the Deep Sleep states verification for scaling
Added GPU Control Driver
Added Sampling Down Momentum for dinamically changing the factor for scaling down
Updated OnDemand governor (it's pretty good at the moment)
Remove Badass and Lazy as they were deprecated
Link BoostPulse to the touchscreen driver for SmartassH3 and OnDemand
Optimize the CPU clock structure for WheatleyPlus
Update SIOPlus and add fluid tunables
Introduce Dynamic Cache Pressure
Revise Dynamic Writeback algorithm
Introduce Timer Slack Controller (aka Timer Coalescing, explanation below)
Deep Sleep tweaks
Backport OOM Killing algorithm from 3.8 kernel
Backport LowMemoryKiller and Timed GPIO drivers from 3.8 kernel
Add Whitelist feature to LowMemoryKiller (you can write PIDs of the processes you want to whitelist, in this file > /sys/module/lowmemorykiller/parameters/w_list ~ below you'll find the script for doing this at boot)
Android Binder update
CFS kernel scheduler optimizations
GPU driver optimizations and code cleanup
Make sure that the GPU turns off when the screen is off
Make the sleep states transitions faster
1.9.1
Finetune WheatleyPlus for better responsiveness
Optimize WheatleyPlus for overclocking on 652 MHz and 768 MHz
Fixed graphical glitches(hopefully)
1.9.2
Every bug fixed
Removed WheatleyPlus
Updated Interactive governor to the latest version from 3.8 sources
Add Dynamic Interactive governor (98% the same as Interactive, but it dynamically changes its parameters according to the load)
Dynamic PLL Overclock
Further undervolt until 768 MHz (the latter allows us to do this without losing performance)
Predefine minfree and adj values
Fully functional App Whitelist (example script here)
Forced unaligned access
Fast Charge (use this to enable it: FastCharge.apk - 1.29 MB) [Disconnect USB Cable - Turn ON - Connect USB Cable]
Timer Slack Controller: (this is a copy-paste from boype's thread)
What does the timer slack feature do?
Timer slacking aims to synchronize applications' and processes' CPU requests. The goal is to wake up the CPU less often in oder to save battery. What you need to know here is the following: waking the CPU up and putting it back to sleep again consumes power. Imagine that four apps wake the CPU up four times each in one second. While without timer slacking the CPU would be woken up 16 times, it is desirable to coordinate the wakeups. If done right, the CPU would wake up less often, effectively allowing power savings and longer sleep periods. This is what timer slacking does.
I have activated timer slacking only for background applications, so that everything else stays as responsive as you know it.
Apple has recently introduced this feature under the name 'timer coalescing' with their Mac OSX Maverick (link).
More information: How Apple does timer slacking ('Timer coalescing') (Scroll a little down to the diagrams)
LZ4 Compressor:
LZ4 is a very fast compressor, based on well-known
LZ77 (Lempel-Ziv) algorithm. Originally a fork from LZP2, it provides
better compression ratio for text files and reaches impressive decompression
speed, in the range and beyond 1GB/s per core (!), especially for binary files.
These speeds are scalable with multi-threading modes, quickly reaching
RAM speed limits on multi-core systems.
ROW I/O scheduler:
The ROW scheduling algorithm will be used in mobile devices as default
block layer IO scheduling algorithm. ROW stands for "READ Over WRITE" which
is the main requests dispatch policy of this algorithm.
The ROW IO scheduler was developed with the mobile devices needs in mind.
In mobile devices we favor user experience upon everything else, thus we want
to give READ IO requests as much priority as possible. The main idea of the ROW
scheduling policy is just that: - If there are READ requests in pipe - dispatch them,
while write starvation is considered.
Download:
AOKP/AOSP ICS:BadassKernel-AICS.zip - 4.78 MB
AOKP:BadassKernel-AOKP.zip - 4.79 MB
CyanogenMod 9.2BadassKernel-ICS.zip - 4.76 MB
AOSPA:BadassKernel-PA.zip - 4.79 MB
CyanogenMod 10:BadassKernel-CM10.zip - 7.03 MB
CyanogenMod 10.1:BadassKernel-JB.zip - 4.79 MB
Various tweaks
Script for adding apps to LowMemoryKiller's whitelist:Whitelist
(you have to edit it to add your own apps, then move it to init.d and set correct permissions. right now you can only add one app, I'll fix this in the next version)
Script to enable zRam with optimized disksize for Fit: View attachment zRamV2.zip (flashable zip) [UPDATED]
Jeeko's PureAudio fixed for CM10.1 and AOKP: View attachment PureAudio__1.0_-_STUDIO.zip [ Please thank Jeeko for this awesome mod. ]
NOTE: This version of PureAudio is compatible with absolutely any equalizer or player.
If you have Titanium Backup installed, in the menu you'll find an option named "Integrate sys Dalvik into ROM". Use it.
This is something like odexing your system, but keeps the classes.dex files inside the apps. Don't worry if you don't have a lot of system space, Titanium will odex as much as it can until the free space runs out.
TIP: So in latest version of CrossBreeder, the OP added some system tweaking which interferes with our kernel. So I edited those parts to match our settings and device limits.
If anyone wants to install CrossBreeder:
-First uninstall by flashing this file: CrossBreeder_Uninstall_7.2.13.zip - 943.12 KB
-Then install this custom version: CrossBreeder_7.2.13-Badass.zip - 1.59 MB
Sources:
GitHub
Credits:
A_U for compiling the base kernel
franco for the various tweaks I cherry-picked from his source
androidarmv6 for fixing bluetooth
Ezekeel for his Wheatley governor
How to install the kernel?
Subdin said:
How to install the kernel?
Click to expand...
Click to collapse
Flash the zip.....
Sent from my GT-S5670 using xda premium
droider007 said:
Flash the zip.....
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
to install cm(9,10,10.1)
and just flash the kernel??????
CM 10.1 kernel isn't a zip...
NM99 said:
CM 10.1 kernel isn't a zip...
Click to expand...
Click to collapse
rename it to .zip
---------- Post added at 11:50 PM ---------- Previous post was at 11:49 PM ----------
droider007 said:
rename it to .zip
Click to expand...
Click to collapse
but don't try its not booting.......wait for a fix....:good:
I'll wait for the fix.
NM99 said:
I'll wait for the fix.
Click to expand...
Click to collapse
Changed the ramdisk, now it should boot. All versions are flashable zips, you don't have to reinstall the ROM for installing a kernel.
Keep a flashable zip with your original kernel on sd in case this doesn't boot.
I flashed kernel for CM10.1 RC6 of erikcas and it works without problems for me.
ZmisiS said:
I flashed kernel for CM10.1 RC6 of erikcas and it works without problems for me.
Click to expand...
Click to collapse
Alright, good to hear that.
Thanks for reporting. This means that the other versions will work too.
alin.p said:
Changed the ramdisk, now it should boot. All versions are flashable zips, you don't have to reinstall the ROM for installing a kernel.
Keep a flashable zip with your original kernel on sd in case this doesn't boot.
Click to expand...
Click to collapse
I'll be sure to flash it soon.
Just a question, I flashed the tweaks on this thread and Fly-On Scripts.. After flashing the kernel, do I need to flash them again?
---------- Post added at 06:33 PM ---------- Previous post was at 05:34 PM ----------
Just a little update, just flashed the kernel. No problems at all, it feels smooth as it can be. I'm running it 68-768Mhz with no problems.
Wake up in the morning..
Open xda (5670 forum)..
see something new anddd..
ohmyglob! FINALLY! SIR ALIN.P's KERNEL!
Best morning news and goodness in the morning! ooohh yeah! Time to test this baby out! By the way, I'd love to see your ROM here sir Alin! THANKYOU!
Kernel works perfectly at 768Mhz, something that I couldn't OC to before. I tryed to OC to 806Mhz and my Fit rebooted automatically. :lol:
Now I'm trying to use 787Mhz to see what can happen.
EDIT: Can't OC over 768Mhz. At 787 the G-Fit keeps running for 15 mins until it locks at whatever it's doing for forever and from 806 onwards it just reboots automtically. At least that's what my G-Fit does, don't know what about the others. Just sharing my personal experience so far with the Badass Kernel.
NM99 said:
I'll be sure to flash it soon.
Just a question, I flashed the tweaks on this thread and Fly-On Scripts.. After flashing the kernel, do I need to flash them again?
---------- Post added at 06:33 PM ---------- Previous post was at 05:34 PM ----------
Just a little update, just flashed the kernel. No problems at all, it feels smooth as it can be. I'm running it 68-768Mhz with no problems.
Click to expand...
Click to collapse
The kernel installs in its own partitions, it doesn't mess with the /system or /data. So you don't need to reinstall anything, only the kernel will be modified when flashing.
About the OC, the kernel uses the same clocks as the stock kernel, with a little tweaks for stability and battery life(Undervolt and refined AXI bus). I was expecting 768 to be the maximum, that's a physical limit. I can't do anything about it. Anyway, I added 748 MHz in case 768 is unstable for some of you.
Jhayzt said:
Wake up in the morning..
Open xda (5670 forum)..
see something new anddd..
ohmyglob! FINALLY! SIR ALIN.P's KERNEL!
Best morning news and goodness in the morning! ooohh yeah! Time to test this baby out! By the way, I'd love to see your ROM here sir Alin! THANKYOU!
Click to expand...
Click to collapse
Thank you too!
I just ported my ROM too. The no-gapps might still have some problems, not sure about it. I had only two reports and 30 downloads, maybe the errors are /data related and individual.
I'll be away for two weeks to prepare for my exams, so I'll answer your questions then.
alin.p said:
The kernel installs in its own partitions, it doesn't mess with the /system or /data. So you don't need to reinstall anything, only the kernel will be modified when flashing.
About the OC, the kernel uses the same clocks as the stock kernel, with a little tweaks for stability and battery life(Undervolt and refined AXI bus). I was expecting 768 to be the maximum, that's a physical limit. I can't do anything about it. Anyway, I added 748 MHz in case 768 is unstable for some of you.
Thank you too!
I just ported my ROM too. The no-gapps might still have some problems, not sure about it. I had only two reports and 30 downloads, maybe the errors are /data related and individual.
I'll be away for two weeks to prepare for my exams, so I'll answer your questions then.
Click to expand...
Click to collapse
For 768 MHz which governor, minimum and maximum CPU frequency?
camera!
video camera dont work on cm9!
with this kernel!
[/url][/IMG]On CM10.1 RC6 of erikcas all works except Skype.
Please answer the question: For 768 MHz which governor and minimum CPU frequency?
ZmisiS said:
On CM10.1 RC6 of erikcas all works except Skype.
Please answer the question: For 768 MHz which governor and minimum CPU frequency?
Click to expand...
Click to collapse
Governor....smartassH3 or badass
Min freq......122 or 68.....
Sent from my GT-S5670 using xda premium
alin.p said:
Alright, good to hear that.
Thanks for reporting. This means that the other versions will work too.
Click to expand...
Click to collapse
Thanks for such a speedy update... :good:
Hey guys, a new version of Crossbreeder has been released.. Can I install it or it can give problems with the kernel?
Aurora Kernel - N900xxx TW
This kernel is intended for battery-saving with keeping maximal possible performance
based newest NE6 sources
Linux 3.4.93 Update
Optimized Cortex-A15 4.10 LINARO Toolchain
see Features for details
Features:
- based on newest NE6 sources
- Linux upstream patches to 3.4.93
- SELINUX permissive
- Synapse support
- init.d support
- OC up to 2.8GHZ
- GPU OC from Snapdragon 801 (up to 587MHz)
- complete dts based kernels Voltage control by faux123
- IntelliPlug driver (for mpdecision replacement) by faux123
- IntelliThermal control driver (better than stock thermal control) by faux123
- Hardlimit CPU control interface by yank555:
- TouchWake by yank555
- PowerSuspend driver by yank555 with default set to hybrid-mode (autosleep and panel hook)
- FauxSound
- UKSM
- FastCharge Support
- LED Control
- mdnie Control by wootever
- Many governors: nightmare, dancedance, intelliactive, intellidemand, uberdemand, wheatley, smartmax, smartmax_eps, lionheart, pegasusq, darkness, hyper, badass, abyssplugv2, adaptive, conservative, ondemand, userpsace, powersave, interactive, performance
- More schedulers: noop, deadline, row, cfg, bfq, fiops, sio, zen
- enabled all TCP congestion controls: veno, westwood, cubic, reno, bic, highspeed, hybla, htcp, vegas, scalable, lp, yeah, illinois
- TCP congestion control default to veno
- new ARMv7 l2 cache
- Filesystem support: Ext2, Ext3, Ext4, FAT32, NTFS, USB OTG, exFAT with many fixes and optimizations (AIO, etc...)
- added multiple compression support for example LZ4, many patches
- F2FS support
- faster glibc
- frandom
- faster crypto libs
- Kernel XZ
- Ramdisk LZ4
- many fixes, updates, patches and enhancements from many sources
- many I already forgot
Check Synapse and thread to know all features
Changelog:
this post
Synapse profiles:
this post
DOWNLOADS
Direct downloads, look at my hosting:
mojosmirror.com
Downloads @ dev-host
Source: Github
Credits and many thanks to:
Much thanks to faux123 and yank555 for their great kernel
thanks to wootever for having always nice and useful commits
thanks to Imoseyon for having always nice and useful commits, too
thanks to civato for helping me starting here with studying his code
thanks to Myfluxi, labodj and Cl3Kener for commits
thanks to UpInTheAir for all his work with his Synapse interface
thanks to GuneetAtwal for some single picks
thanks to franciscofranco, zamcum, ZaneZam, CM-team, Codeaurora, ... and everyone else I forgot!
PM me, if you find your work not mentioned here
XDA:DevDB Information
Aurora Kernel Note 3, Kernel for the Samsung Galaxy Note 3
Contributors
MojoManagement
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R11v2
Stable Release Date: 2014-06-15
Created 2014-05-09
Last Updated 2014-08-29
Reserved
Reserved
Changelog
R11 (aka Synapse release)
NOTICE:
Due to heave Synapse changes again, I recommend to clear Synapse data, before you flash
If you feel unsnappy, raise Touchboost values, completely set both down to 300MHz at init
Synapse settings added & reworked (spent whole day into Synapse primarily)
Synapse can now make a flashable zip from your backup profile to share with others (look under tab Synapse)
Removed some sound pre-settings and removed FauxSound control for now to prevent still unknown issues
a few more fixes
R10 (beta)
NOTICE:
I recommend to clear Synapse data!!!
Synapse should now have enough options for daily settings
So please dont mix apps for setting kernel features
Synapse settings added (very hard work.....half day wasted here...)
S-Browser crash fixed on S5 ports
Sound issues fixed and quality should be improved
completely switched to UKSM now
a few more fixes and patches from different sources again
PS:
Please dont complain about voltage control in Synapse
If you want to experiment with voltages, you can set them one by one yourself
R9 (beta)
NOTICE: this will break some of Faux Control App functions, especially frequency setting, until Faux updates
If you dont want to run a beta, stick with R8 until stable release
There is currently not voltage, thermal, screen, zswap control in Synapse!
update to Linux 3.4.92
Synapse is back (but not everything is implemented), check yourself, big thanks to UpInTheAir, which made a very detailed Synapse layout, which I used as base
Hardlimit Interface update to 2.0a, you can now set screen on and screen off max/min frequencies separately, wakeup kicks, touchboosts, DVFS lock... check Synapse
GPU OC with Snapdragon 801 values (up to 587MHz)
Ramdisk is now LZ4 compressed (need to check kernel for LZ4, too)
Led Control updated to V1.2
IntelliPlug updated to newest version
Logger can be enabled/disabled through sysfs interface
many fixes and patches from different sources again
R8
finally working NE6 base with all known features
R7
updates base to NE6
same as R6
R6
switched to faux123-yank555 kernel as new base
over 300 commits added, patches, fixes, enhancements, etc...
see features
r5
lower power frequency 268,8MHz should work now as expected
lowered voltage for 268,8MHz (its really low, report if unstable)
new govs: lagfree and smartassv2, both tuned
updated and optimized fiops scheduler (which I recommend for internal)
optimized BFQ scheduler (which I recommend for external...)
linux update to 3.4.91
CIFS support (experimental)
enabled ksm (experimental)
swap support
updated toolchain to Linaro 4.9.1 05/2014
LZ4/LZO updates
some sound patches
many arm patches
some memory patches
more I forgot ...
r4
more fixes and enhancements
more govs: intelliactive, abyssplugv2, conservativex, adaptive
Dynamic FSYNC is back
permanent async FSYNC from HTC
PowerSuspend updates: hooked to AutoSleep and Panel, first sleep hook wins
experimental low power frequence
zen scheduler added
few more things
r3
over 60 fixes, patches and enhancements since r2
LZ4
crypto optimizations
faster glibc
very fast random generation (10-50 times faster)
gpu patches
linux update
many more
r2
over 50 fixes, patches and enhancements at all from beta
support for N900T
updated busybox (problems fixed)
updated ramdisk
mpdecision improved (also recommend Intelli Hotplug)
more compiler improvements
scheduler patches
dynamic fsync disabled (more later)
cpu patches for msm
enabled last kernel message
many more
Community profiles for Synapse:
How to use shared profile?
Flash shared profile in recovery
Reboot to system
OpenSynapse
Go to tab "Synapse"
Check if last backup says "flashed" at the end (time buggy at the moment sorry)
Press "Restore & Close Synapse"
Open Synapse
Press X[ Cancel/B] at the top to use restored settings (if you press "✓ Apply" your last settings will be restored)
R11:
gianton:
Here's my current setup I'm testing on r11. It's more for battery saving, if you play lots of games set the governor to intelliactive.
Click to expand...
Click to collapse
Link to post for download
Tried to download but link empty
Sent from my SM-N9005 using Tapatalk
Does it have ntfs r/w support?
Sent from Hacker OS
IzArsha said:
Does it have ntfs r/w support?
Sent from Hacker OS
Click to expand...
Click to collapse
Should work if I did not make any mistake
panjaby said:
Tried to download but link empty
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Downloads tested, all links should be working
Awesome kernel. Just one question, does it support GPU OC?
blogslogger said:
Awesome kernel. Just one question, does it support GPU OC?
Click to expand...
Click to collapse
Not yet, because I remember problems with frequencies are not used and also decrease performance with gpu set to 550
I just find the correspondending post by sorg
sorg said:
http://forum.xda-developers.com/member.php?u=3986004
About GPU overclock:
My phone is Samsung SHV-E330S, which is basically GT-N9005 in S4 case, so 99% hardware is the same.
According to my investigation in GPU overclocking, frequencies are handled fully inside RPM firmware. Frequencies in .dtsi files aren't used. RPM uses its own frequency table and cannot be changed from linux side. So, your GPU OC simply doesn't affect actual GPU frequencies. Linux GPU governor will think it uses new frequencies and will actually switch to a wrong frequency (because RPM will use hardcoded unmatched freq table) - so everything will go wrong (as you already noticed, probably).
I've monitored GPU/PLL hardware registers and saw, they work according RPM's table and not affected by .dtsi settings.
There is the only way to overclock SD800 GPU is by modifying PLL settings (as it was done for SD600 GPU). There is PLL for highest GPU powerlevel's frequency which used solely by GPU (just like in SD600). But performance increase is not so high as it could be from increasing RAM frequency OC (which i didn't manage to tweak yet).
P.S.: I don't know about N9005, but in E330S standard highest frequency is 550MHz (according to PLL settings) instead of 450MHz as advertized in MSM8974 (not AB or AC), although in .dtsi files max frequency is 450MHz. Good bonus from Samsung
Probably, in N9005 it's the same.
Click to expand...
Click to collapse
I might have a look into that in the future
Does it work with ND5 update
bhasg1007 said:
Does it work with ND5 update
Click to expand...
Click to collapse
Yeah, I am on ND5 rom with ND5 bl and NC2 modem
Downloaded Thanks for the reply will try now
Can I flash this kernel over lean kernel?
Tia
Sent from my SM-N9005 using XDA Premium 4 mobile app
Cool! A new kernel! gonna try it now and will be back with results in a day or two
Sent from my SM-N9005 using XDA Premium 4 mobile app
ghalib87 said:
Can I flash this kernel over lean kernel?
Tia
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Of course
MojoManagement said:
Downloads tested, all links should be working
Click to expand...
Click to collapse
Apologies. The fault must be on my end.
If I open the first link with chrome it goes blank with mojo wesite bit if I open the link directly with es downloader it downloads
Sent from my SM-N9005 using Tapatalk
MojoManagement said:
Not yet, because I remember problems with frequencies are not used and also decrease performance with gpu set to 550
I just find the correspondending post by sorg
I might have a look into that in the future
Click to expand...
Click to collapse
Thankyou for your patience. It was quite helpful to learn a new thing.
I have got a problem when put on usb charge it stays on high frequency and instead of charging, the phone battery gets dischaged slowly. anything i have to do.
****Ares-Kernel****
****By****
****The~Skater~187****
This kernel is a combination of SmartPack/Boeffla-Venom Samsung Galaxy S5 Lineage OS kernel, with some tweaks and additions from around the net. I have decided that since SmartPack was EOL and with sunilpaulmathews ok, I would just combine our two kernels (since fbs has Boeffla-Kernels covered) to make it easier for me to maintain his work and my own.
/* DISCLAIMER! *\
*I am not responsible for any damage to your device*
* Everything you are doing on your device is at your own risk*
*Don't forget to make a back up before flashing*
~~~~~~~~~~~~~~~Flash at own risk~~~~~~~~~~~~~~~~~~
/* Supported devices *\
klte: SM-G900F, SM-G900AZ, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
kltekor: SM-G900K/L/S
kltedv: SM-G900P/I
klteduos: SM-G900FD, SM-G900MD
kltekdi: SCL23
/* Compatibility *\
DO NOT FLASH OVER CUSTOM KERNELS!
This kernel is only meant to work on Lineage-OS 15.1/16 and nothing else. However, it may work on other LOS-15.1/16 (and AOSP) based Oreo/Pie ROMs
This kernel will NOT work in Samsung Stock and other TW ROMs.
/* How-to-Install *\
*Download Kernel*
1. Go to recovery (TWRP recommend)
2. Flash Kernel
3. Reboot and enjoy
/* Incorporated SmartPack Features *\
Build from latest Lineage OS source code.
Built using latest GCC-8.x.
Anykernel for compatibility with maximum devices.
Linux Kernel version is updated to 3.4.113
Kernel tweaker app recommend: SmartPack-Kernel Manager (Please note: official Kernel Adiutor is NOT fully compatible with this kernel).
Added features include...
CPU voltage control
CPU Freq Gov: INTELLIDEMAND, INTELLIACTIVE, SMARTMAX, LIONHEART, NIGHTMARE, ADAPTIVE, ALUCARD, ZZMOVE, etc.
(for those who want to use zzzmove, I strongly suggest to carefully read this forum post by @Saber)
CPU hotplugs: Lazyplug, Alucard, and mako hotplug.
Full control over AC, USB and Wireless charging rate in SmartPack-Kernel Manager (Default charging rates: AC: 1800 mA; USB 700 mA; Wireless: 900 mA).
Boeffla Sound to control speaker and headphone volume.
(for official KA users, follow these instructions by @Exzu to create respective custom controllers for Boeffla Sound and Fast Charge.)
Adreno_Idler
CPU Input boost (configurable in SmartPack-Kernel Manager)
IO schedulers: FIOPS, SIO, VR, ZEN, FIFO, TRIPNDROID.
TCP congestion algorithms: Westwood, reno, cubic etc.
FRandom
Dynamic sync control 2.0
Boeffla Generic Wakelock Blocker
268 MHz CPU underclocked frequency cycle
Additional 27 MHz GPU frequency step (idle frequency)
KCAL v2
SELinux "Enforcing" by default (can be switched to "Permissive" in SmartPack-Kernel Manager)
a lot more...
/* Incorporated Boeffla-Venom Features *\
*Enable OC to 2995:
-DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. (I AM NOT RESPOSIBLE FOR YOUR DEVICE)
*Fast Charge
*ZZmoove adjusted to acommodate Overclocking (Thanks to Legitsu)
*Tweak bandwith on higher OC steps (Thanks to ktoonsz)
*Deadline I/O Tweaks (Ktoonsz)
*Fix memory leak with sysfs when stats table are freed (Ktoonsz)
*Bump up Max Voltage (Adjusted for higher OC) (Ktoonsz)
*Dirty Writeback Tweaks
*Increased VM_MAX_READAHEAD to 512 (default)
*Increased default entropy levels (both read and write)
*Optimized Kernel Samepage Merging
*QuickWakeup (Thanks CrazyGamer)
*PowerSuspend (Thanks Faux123)
*Cortex_A15 Optimizations (Fusion-Rom Dev Team)
*Slimbus Overclock (Ktoonsz)
*Slimbus Optimized Overclocking Of Master Component (CrazyGamer)
*VFP Tweaks (Ktoonsz)
*EXT4 Tweaks(Ktoonsz)
*GPU Overclocked up to 657 (Ktoonsz)
*Disable Swap Readahead
*Increase Maximum Swappiness
*Kernel mode neon (ShinySide)
*Disable Direct Reclaim File Pages
*Enable Unaligned Capability For ARM (CrazyGamerGR)
*Update min-default adreno frequency to be 200 MHz (kholk)
*Fixed memory entry leak when calling Adreno Convertaddr (Shubhraprakash Das)
*Changed clock rates to 19.2 MHz (Faux123/Qualcomm)
*Optimized Sched/Fair a bit (Faux123)
*Applied many new compiler optimizations (Synergy kernel Team & Decimalman)
*Zswap: Uses LZ4 now (if available)
*Support for LZ4-compressed kernel
*Fix memory leak in Mass Storage
*Added back Intellithermal V.2 Thermal Engine (for those who prefer it)
*Modified LowMemoryKiller (fbs)
/* Downloads Can Be Found Here *\
https://app.box.com/s/nx7nuf7vb2eubd5sfrr5rerjsatcp42i
/* Special note to Korean S5 users *\
(Thanks to sunilpaulmathews defconfig files)
Flashing this kernel after AOSP/LOS based Oreo/Pie ROMs originally build for the klte (SM-G900F) variant SHOULD allow the use of those ROMs on SM-G900S/K/L.
/* Acknowledgements *\
@haggertk for LineageOS for Galaxy S5
@Lord Boeffla
@franciscofranco
@Sultanxda
@arter97
@faux123
@CrazyGamerGR
@Saber
@nathanchance
@ZaneZam
@osm0sis for AnyKernel project
@Grarak for Kernel Adiutor
@sunilpaulmathew
@justjr for SmartPack efficiency profile
@ktoonsez
@KazuDante
@fbs
@kholk
@decimalman
@Synergy Kernel Team
Many other XDA developers
XDA:DevDB Information
Ares-Kernel, Kernel for the Sprint Samsung Galaxy S5
Contributors
The~Skater~187, sunilpaulmathew
Source Code: https://github.com/187MoD/Ares-Kernel
Kernel Special Features: Boeffla-Venom + SmartPack Kernels
Version Information
Status: Beta
Current Beta Version: Beta-v1.6
Beta Release Date: 2019-02-15
Created 2019-02-15
Last Updated 2019-08-26
***Ares Kernel Changelog***
~~~~~Beta-v1.7~~~~~
*Up-to-date with Lineage-OS source as of 01.01.2020
*Update Intelli-plug to version 3.9 (Compliments of Pascua28)
*sound: Compiled with -Os optimization (Compliments of Pascua28)
*A few other optimizations
~~~~~Beta-v1.6~~~~~
*Up-to-date with Lineage-OS source as of 08.25.2019
*Compiled using Bleeding-Edge Toolchain 9.2
*Cortex A-15 MSM-memutil optimizations for better memory performance
*GPU compiler optimizations
*Enable: Frontswap
*Enable: Runtime compcache
*Removed un-supported SOC features (Thanks pascua28)
*Fix possible memory leak in slub.c (Thanks pascua28)
*Add Missing xor-neon file
*Compiled with many new compiler optimizations
*Plus more
~~~~~Beta-v1.5~~~~~
*Up-to-date with Lineage-OS source as of 07.15.2019
~~~~~Beta-v1.4~~~~~
*Up-to-date with Lineage-OS source as of 05.27.2019
*Compiled with "Bleeding-Edge-Toolchain" 9.1
*Compiled with 03 compiler optimizations
~~~~~Beta-v1.3~~~~~
*revert: disabled "CAF" cpu policy save code (Fixed cores not scaling properly)
*MSM Limiter updated
~~~~~Beta-v1.2~~~~~
*Up-to-date with Lineage-OS source as of 03.19.2019
*reverted to stock Lineage-OS LMK (Low Memory Killer)
*bumped OC up to 3072 -DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. I AM NOT RESPONSIBLE FOR YOUR DEVICE!)
*bumped up voltage overhead to hopefully help stabilize new OC step
*added Intelliplug_hotplug driver (Now default hotplug service)
*added Touchboost driver (adjusted for 3072 oc)
*added MSM CPU Limiter (adjusted for 3072 oc)
*enabled Arch Power
*added the ability to Toggle Arch Power And Sleepers (compatible with SmartPack Manager)
*disabled "CAF" cpu policy save code (Faux123)
*added msm_mem_utils for added memory performance
*disabled constant spam in dmesg from 'undefined instruction' print statement in traps.c
*ZZmoove: adjusted to acommodate Overclocking to 3072
*added Boeffla-compiled In-Kernel Busybox
*some other things
~~~~~Beta-v1.1~~~~~
*Up-to-date with Lineage-OS source as of 03.02.2019
*Ares-Kernel boot script: update default profile settings (credits: justjr)
*import Core Control fix (sunilpaulmathew)
*import "Hotspot" fix (sunilpaulmathew)
*added a compatible version of "Tuned" LowMemoryKiller (fbs)
*added support for lz4 compressed kernel
*added some compression tweaks to help with boot performance
*driver/char: add missing frandom commits
*fs/sdcardfs/mmap.c: add AIO optimization flag compatibility fix up
*kernel/power: add missing quickwakeup commit
*Optimized ARM RWSEM Algorithm (Faux123)
*Tuned thermal management a bit
*Some other stuff
~~~~~Beta-v1.0~~~~~
-Initial Merge of SmartPack/Venom Sources
*Synced With latest LineageOS Sources as of 02.13.19
*Built with Latest 8.2.1 toolchain using SunilPaulMathews build Framework
*Compatible With Kernel Auditor & Should Be Compatible SmartPack-Kernel Manager
*Enable OC to 2995:
-DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. I AM NOT RESPOSIBLE FOR YOUR DEVICE)
*Boeffla Sound
*Fast Charge
*ZZmoove: adjusted to acommodate Overclocking (Thanks to Legitsu)
*Enable 268 mhz underclock (Thanks to SunilPaulMatthew)
*Tweak bandwith on higher OC steps (Thanks to ktoonsz)
*Tweak deadline: Allow 0ms deadline latency, increase the read speed (Ktoonsz)
*Set audience sleep delay to 0 to fix delay upon making phone calls
*Async I/O latency to a ssd greatly increased (34% gain,kleikamp & Ktoonsz)
*Fix possible memory leak with sysfs when stats table are freed (Ktoonsz)
*Bump up Max Voltage (Adjusted for higher OC) (Ktoonsz)
*Dirty Writeback Tweaks
*Increased VM_MAX_READAHEAD to 512
*Increased default entropy levels (both read and write)
*Optimized Kernel Samepage Merging
*QuickWakeup (Thanks CrazyGamer)
*PowerSuspend (Thanks Faux123)
*Cortex_A15 Optimizations (Fusion-Rom Dev Team)
*Add Missing Graphite Define (Ktoonsz)
*Slimbus Overclock (Ktoonsz)
*Slimbus Optimized Overclocking Of Master Component (CrazyGamer)
*VFP Tweaks (Ktoonsz)
*EXT4 Tweaks(Ktoonsz)
*GPU Overclock up to 657 (Ktoonsz)
*Disable Swap Readahead
*Boeffla wakelock blocker (Thanks to sunilpaulmathew & franciscofranco)
*Increase Maximum Swappiness
*Kernel mode neon (ShinySide)
*Disable Direct Reclaim File Pages
*Enable Unaligned Capability For ARM (CrazyGamerGR)
*Update min-default adreno frequency to be 200 MHz (kholk)
*Fixed memory entry leak when calling Adreno Convertaddr (Shubhraprakash Das)
*Change clock rates to 19.2 MHz (Faux123/Qualcomm)
*Optimize Sched/Fair a bit (Faux123)
*Applied many new compiler optimizations (Synergy kernel Team & Decimalman)
*Zswap: Uses LZ4 now (if available)
*Support for LZ4-compressed kernel
*Fix memory leak in Mass Storage
*Alucard, LazyPlug & Mako Hotplugging
*Enabled VNSWAP
*Added back Intellithermal V.2 Thermal Engine (for those who prefer it)
*Modified LowMemoryKiller (fbs)
# All Changes
# Signed Off
# By
# The~Skater~187
Reserved
~~~~~~~~~~~ Please note~~~~~~~~~~~
If you need support, please supply the following or support will not be given:
*Device Variant
*Current Rom & Android Version
*Bootloader & Baseband version
*Recovery & Version
*Recovery Log
I can't help if the only details given are "It didn't work" or "I can't flash this".
One More For Good Measure
YES.!!!!
sdfat code have syntax errors, aren't even compiling here.. humm
ok, fixed it and stealed it
Thanks for ur good kernel. Flashed on haggertk android pie no problem so far. At first I was getting random reboots,it caused by my magisk modules. I disable them and the problem fix. Thanks again.
LKT magisk module on this kernel cause random reboots.
Thanks for your work
So I popped over to this thread you linked to from the Venom thread and want to make sure I'm clear. This kernel (Ares-Kernel) should not be used on a Resurrection Nougat based ROM? I think that Resurrection Nougat ROM is a Lineage 14 based ROM, correct? Or even though it is Lineage 14 based, can the Areas-Kernel still be used because it is based off Lineage.
Thanks for any clarification. Left this post in other thread to just to make sure I got it in right spot. Disregard which ever one is posted in wrong spot. Thanks.
awesome dude!!! thank you so much! i'm really glad that someone continues the smart-pack kernel!
:laugh: big, Big, BIG Thank you @The~Skater~187! Really appreciate your effort and dedication in helping to keep this old phone alive and competitive! :highfive:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as the tunable io_is_busy 0 to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
justjr said:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
Click to expand...
Click to collapse
I do apologize about the credit issue, I thought I had put your name in the acknowledgment section right before ktoonsz last night, as I noticed your name on a few of the files in the RamDisk. I will definitely straighten that out and thank you for pointing that out. You are correct, I so far have just synced SmartPack source, then started applying things from my other kernel for now. I wanted to get something up-to-date and stable out for you guys before I started diving deeper into other kernel related things.
As for the rest of your suggestions, I will look into them for sure. Feel free to p.m. me with any thoughts or other suggestions.
Sent from my kltespr using Tapatalk
The~Skater~187 said:
I do apologize about the credit issue, I thought I had put your name in the acknowledgment section right before ktoonsz last night, as I noticed your name on a few of the files in the RamDisk. I will definitely straighten that out and thank you for pointing that out. You are correct, I so far have just synced SmartPack source, then started applying things from my other kernel for now. I wanted to get something up-to-date and stable out for you guys before I started diving deeper into other kernel related things.
As for the rest of your suggestions, I will look into them for sure. Feel free to p.m. me with any thoughts or other suggestions.
Sent from my kltespr using Tapatalk
Click to expand...
Click to collapse
Many thanks!
On other news, I was getting some random reboots, and found out that it was because of my undervolt settings. It's super weird, because they never gave me any problems since 3~4 months with the smartpack kernel, and it should be a setting particular to my specific device/cpu, and have the same limits across any kernel. I used the same across lots of roms, and different versions of smartpack, for nougat, oreo and pie, so, I hope you can see why I find this very weird.
But, I don't know if it's actually a 'bug', I will find some time to fine tune it, raise some voltages to see where I can go with Ares kernel without crashing. For now I'm using the default voltages.
justjr said:
Many thanks!
On other news, I was getting some random reboots, and found out that it was because of my undervolt settings. It's super weird, because they never gave me any problems since 3~4 months with the smartpack kernel, and it should be a setting particular to my specific device/cpu, and have the same limits across any kernel. I used the same across lots of roms, and different versions of smartpack, for nougat, oreo and pie, so, I hope you can see why I find this very weird.
But, I don't know if it's actually a 'bug', I will find some time to fine tune it, raise some voltages to see where I can go with Ares kernel without crashing. For now I'm using the default voltages.
Click to expand...
Click to collapse
I did do a bit of an overhaul on the voltage table when I added the higher oc steps, due to the fact that on my other kernel lower voltages stock we're causing problems and random freezes.
Sent from my kltespr using Tapatalk
Yeah, I'm sure you know, undervolting need to be done step by step, making sure the lowest you can go, device specific, so risking repeating myself, same voltages should probably 99,99% of the time works across any kernel/rom on a given device. I don't think it is the undervolt anymore.
It took a while but I still had some reboots with default voltage, once I was finally able to press up and home right after it, so it rebooted directly to TWRP and I copied the last_kmsg, it's attached, all configs were on default. I hope it helps to find out what it may be.
I'm back on smartpack for now, cause the same setup and profile runs without no problems, so I think it should not be a problem just on my end, is it? Anybody else?
Fun fact, I was are able to dirty install smartpack kernel over ares and vice-versa and it detected and updated itself without any problems.
I'm able to go kinda low here with no crashes:
660
670
680
690
700
710
720
730
745
750
775
795
825
865
925
965
990
1005
1035
1060
@The~Skater~187 edit: oh, I just noticed, there's no option to input 268 MHz voltage. My voltages are getting placed on the wrong frequency because of that, found the problem!
I recovered the backup I just made before installing the kernel, I had installed the shushified bootleggers 3.0 on top of the unshushified 3.0, they are the same rom except for official (shushified) status, but anyway, that may be the cause of some of my problems, adding up to the 268 missing voltage that was overlooked by me.
After that I installed Ares kernel again with no undervolt and gone to sleep. Woke up today, and no reboots, then I was trying to test undervolting it and found out about the missing 268 voltage, so every previous voltage I used was getting used on 1 clock step above, so, not enough power for sure.
Just put my exactly same volts on their correspondent freq and no reboots until now!
It also seems that Core Control is staying enabled and VD Restrictions is disabled correctly now too. So, if you experience the same you may disregard it as well.
Thanks for this!!
Great so far, this with Pie ROMs is the best battery life I've had since stock.
4-5 hours sot, 7h active, 12h idle..(gsam stats) on this original 2800mah. I've gone from 4-5 charges a day to 1-2.
And kernel brightness control keeps the flickers away.
Edit: did notice both vdd and core thermals being active, didn't cause any overheating/reboots (i often run cpu info as overlay) but I stuck with core control only to be safe. It doesn't stick after reboot.
S5 klte
Latako said:
Edit: did notice both vdd and core thermals being active, didn't cause any overheating/reboots (i often run cpu info as overlay) but I stuck with core control only to be safe. It doesn't stick after reboot.
S5 klte
Click to expand...
Click to collapse
Yeah, after some further analysis, I came to find out exactly the same.
After a reboot both VDD and CC come back up, and I have to do a little dance, like, disable vdd and cc, enable intellithermal, then enable only cc, or something like that, then it will stick with only cc until the next reboot.
Ok, so I decided I'm going keep an "unofficial" SmartPack kernel going (nothing more than source updates will be applied) as well as my off shoot kernel project. I will have it available for you guys tomorrow evening.
Sent from my kltespr using Tapatalk
justjr said:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as the tunable io_is_busy 0 to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
Click to expand...
Click to collapse
So is it possible to use your profile without any errors?