[KERNEL][Nexus 10][04/06/2014][4.4/4.3/4.2] KTManta

Search This thread

espionage724

Senior Member
Feb 8, 2010
2,921
728
wiki.realmofespionage.xyz
OnePlus 6
You're either trolling or a complete idiot. Likely both.

This kernel is fine to flash and will not cause data loss.

Not entirely true. Goes for any 3rd-party thing really (yes, even this kernel, unless it has some some secret to keeping data in-tact that no other kernel has ;)). (Random) reboots can cause data loss. And there is plenty of reports of people having random reboots with their N10's. Now every random reboot won't cause data loss, but that doesn't mean it can't/won't happen.

I had a similar incident a little while back on a different kernel (it locked up, rebooted, tablet was factory reset).

I'm not trying to show negativity towards this kernel though or anything like that, it is a very nice kernel :) But there's a reason for the disclaimer on the bootloader when you unlock your tablet about custom software.
 
Last edited:

omgi0wn

Senior Member
Jun 18, 2010
228
9
Not entirely true. Goes for any 3rd-party thing really (yes, even this kernel, unless it has some some secret to keeping data in-tact that no other kernel has ;)). (Random) reboots can cause data loss. And there is plenty of reports of people having random reboots with their N10's. Now every random reboot won't cause data loss, but that doesn't mean it can't/won't happen.

I had a similar incident a little while back on a different kernel (it locked up, rebooted, tablet was factory reset).

I'm not trying to show negativity towards this kernel though or anything like that, it is a very nice kernel :) But there's a reason for the disclaimer on the bootloader when you unlock your tablet about custom software.

This did happen to me recently actually, and I lost all my widgets, wallpaper settings, etc... Ever since I upgraded to the 02/07 kernel I have been getting random reboots, and the tablet will not turn back on after being asleep for a while. Back to the 01/29 kernel for me.
 

freshlysqueezed

Senior Member
Aug 4, 2010
497
229
Essential Phone
OnePlus 9
Re: [KERNEL][Nexus 10][2/7/2013] KTManta

I also lost data, but it was on the stock kernel. Therefore I recommend that we never flash the stock kernel. :D

In all fairness, I find that the nexus 10,
Is especially easy to corrupt data, regardless of kernel or Rom.

Sent from my EVO using xda app-developers app
 

jrod091

Senior Member
Feb 13, 2012
337
88
Atlanta, GA
Re: [KERNEL][Nexus 10][2/7/2013] KTManta

I followed the instructions just as they were posted. I cleared the cache and fixed permissions. The only thing I changed was the setting from interactive to performance. As I mentioned, I was on CleanROM for weeks with no problems. I was on the stock kernel. Since there were no problems prior to flashing the kernel, it's safe to assume the kernel is the culprit.

I did not change any settings whatsoever. Nor I 'authorize for data be wiped'. That would moronic. I realize there are a lot of devote followers of this kernel and I am sure many are butt-hurt after seeing someone complain. But that was my experience. I've been flashing ROMs and kernels for a long time. I usually never have any problems with a kernel and it never warranted making a backup.

So, while I'm glad that out of 700 downloaders, only 2 were affected, it sucks to be those 2 people.



Says the guy who calls someone a troll for complaining.



I'm neither. Thanks.

If you really have been flashing for as long as you claim, you should know that things *may* go wrong, so it is logical to name a backup every now and then. Also, any important data should be backed up somewhere. So, your claim to others to " stay away from this kernel" shows your own negligence and lack of carrying for your data

Sent from my Nexus 10 using xda app-developers app
 
  • Like
Reactions: ktoonsez
Re: [KERNEL][Nexus 10][2/7/2013] KTManta

I also lost data, but it was on the stock kernel. Therefore I recommend that we never flash the stock kernel. :D

In all fairness, I find that the nexus 10,
Is especially easy to corrupt data, regardless of kernel or Rom.

Sent from my EVO using xda app-developers app

Exactly ^^

EDIT: warning, incoming rant:

I have had my data corrupted twice on my N10. Once with the stock kernel and once with Franco. I would never troll on to a thread and announce to everyone that, 1. It was the kernels fault and, 2. Tell people not to use this kernel. That is way out of line. In my case I take responsibility for even rooting and flashing custom recoveries, custom roms and kernels. This is my choice and my risk I take on. I don't blame others first, especially when they are donating time, skill and expertise well above mine, so I can choose to take the risk to improve my device.

I have lost my data on many occasions on many devices and I almost always have a way to recover and if I don't, it's my fault, not a kernel dev's fault. Way lame of that guy to post blame for not taking on his own personal responsibility.

To all you devs and others that volunteer time to improve my devices, all I can say is thank you.

Sent from my Nexus 10 using Tapatalk HD
 
Last edited:

ayman07

Senior Member
Feb 25, 2010
1,031
441
Re: [KERNEL][Nexus 10][2/7/2013] KTManta

Simply posting my findings and my opinion. You don't have to like it. Personally, I don't recommend it. You don't have to agree. A few people have mentioned that it has happened to them as well. I'm not really all that pissed because I had an old backup of some of my apps. But the developer knew that this was a possible issue since he said a few people have complained. It would have been nice to know beforehand.

There is also no disclaimer nor does it say there are risks in flashing a new kernel. For me, I already knew that I could severely damage my device by overclocking it but I had not been aware of this wiping data bug. I've never had a kernel do that before either. But my point is, we were all newbies at one point and a better explanation of the risks and possible bugs would be beneficial for everyone.
 
Last edited:

ktoonsez

Inactive Recognized Developer
Nov 3, 2011
16,265
43,223
Tempe
Simply posting my findings and my opinion. You don't have to like it. Personally, I don't recommend it. You don't have to agree. A few people have mentioned that it has happened to them as well. I'm not really all that pissed because I had an old backup of some of my apps. But the developer knew that this was a possible issue since he said a few people have complained. It would have been nice to know beforehand.

There is also no disclaimer nor does it say there are risks in flashing a new kernel. For me, I already knew that I could severely damage my device by overclocking it but I had not been aware of this wiping data bug. I've never had a kernel do that before either. But my point is, we were all newbies at one point and a better explanation of the risks and possible bugs would be beneficial for everyone.

When did I say that I knew about it. I have already told you, the chance it is kernel is slim to NONE. Just drop it move on to another thread, if you dont like the kernel you dont have to use it and definitely NO NEED to blame the kernel when many people have just told you that it happens on other kernels too. So it is most likely the 4.2 ROM platform.
 

stev067

Senior Member
Dec 19, 2012
101
32
Kalamazoo, MI
Simply posting my findings and my opinion. You don't have to like it. Personally, I don't recommend it. You don't have to agree. A few people have mentioned that it has happened to them as well. I'm not really all that pissed because I had an old backup of some of my apps. But the developer knew that this was a possible issue since he said a few people have complained. It would have been nice to know beforehand.

There is also no disclaimer nor does it say there are risks in flashing a new kernel. For me, I already knew that I could severely damage my device by overclocking it but I had not been aware of this wiping data bug. I've never had a kernel do that before either. But my point is, we were all newbies at one point and a better explanation of the risks and possible bugs would be beneficial for everyone.

This is not a bug specific to this kernel. This is the risk you take with flashing anything. I think we understand that you are frustrated, and you can't take back your words, and let's just leave it at that.

Lessons learned today:
Don't do any flashing without backing up your valuable data.
Don't go stomping into a thread making bold statements, unless you want 700 happy users to teach you some lessons.
 

EniGmA1987

Senior Member
Sep 21, 2010
2,064
807
But the developer knew that this was a possible issue since he said a few people have complained. It would have been nice to know beforehand.

There is also no disclaimer nor does it say there are risks in flashing a new kernel. For me, I already knew that I could severely damage my device by overclocking it but I had not been aware of this wiping data bug. I've never had a kernel do that before either. But my point is, we were all newbies at one point and a better explanation of the risks and possible bugs would be beneficial for everyone.

I know the situation sucks, but it is an accepted fact that whenever you do anything custom on a phone or tablet there is a chance things can go horribly wrong. You agree to this when you unlock your bootloader. We all know serious issues are incredibly uncommon, but they do happen from time to time. That is why all guides that teach you how to flash say to do a nandroid backup before you flash something new. It sucks that you have this issue, but it is a good reminder to the rest of us that when we dont follow proper flashing procedure there will be at some time, when we least expect it, a problem that we will have to kick ourselves over for not making a backup first.

Also, I dont think Ktoonsez knew or remembered that someone at once time had an issue where the person lost data, especially since that case was found not to have been the kernel at fault in the first place. I am the one who said I remembered one other guy a long time ago, and I am not the dev of this kernel.
 
Last edited:
  • Like
Reactions: ktoonsez

EDNYLaw

Senior Member
Nov 26, 2010
256
204
New York
Re: [KERNEL][Nexus 10][2/7/2013] KTManta

If you need some legalese for a disclaimer, happy to put my law skills to use ;)

Sent from my Nexus 10 using Tapatalk HD
 

stonebear

Senior Member
Sep 26, 2011
2,359
572
Re: [KERNEL][Nexus 10][2/7/2013] KTManta

I just flashed this and installed the app. Nice work, thanks!

I am liking having all these options in the app, though I am gonna stay away from the thermal throttling for now. :)

In the highly unlikely event that anything goes wrong I have a nandroid and TiBu backed up remotely on Box... and if something did go wrong I would never be so gauche as to tell people to avoid the kernel. :p



Sent from my Nexus 10 using Tapatalk HD
 
  • Like
Reactions: djd338 and ktoonsez

Dextis

Senior Member
Dec 2, 2011
62
9
I just realise that things can go wrong sometimes and not being totally egocentric I am aware that as there are hundreds of posts in the thread, most people are using it without issues.

So, if I had a problem I would report it without dissing someones work.

It's just a matter of manners. :)

Sent from my Nexus 10 using Tapatalk HD


You. I like you.
 

Siberian Tiger

Retired Senior Moderator / Tiger's Eye
Dec 4, 2010
4,724
6,930
Piraeus
This is XDA developers.And you know that rooting your phone will void your guarantee plus if something happens to your precious the devs don't take responsibility: FLASH AT YOUR OWN RISK.

If you want to help the dev don't say :mai fone reboots ,is hot etc etc.
Grab a logcat or the last kmsg to see why it happened.

Next time i see such posts they will be deleted and infractions will be issued .

ST
 

ayman07

Senior Member
Feb 25, 2010
1,031
441
Re: [KERNEL][Nexus 10][2/7/2013] KTManta

This is XDA developers.And you know that rooting your phone will void your guarantee plus if something happens to your precious the devs don't take responsibility: FLASH AT YOUR OWN RISK.

If you want to help the dev don't say :mai fone reboots ,is hot etc etc.
Grab a logcat or the last kmsg to see why it happened.

Next time i see such posts they will be deleted and infractions will be issued .

ST

I clearly explained how I received the issue. I explained what steps I took and expressed my concern with the kernel. Its hard to grab a logcat when your device decides it wants to do a factory reset on its own.

I didn't realize saying that you wouldn't recommend something is against the rules.

Sent from my Nexus 10 using Tapatalk HD
 

Matthileo

Senior Member
Apr 19, 2009
288
59
Wichita, KS
Re: [KERNEL][Nexus 10][2/7/2013] KTManta

Any changes in the 4.2.2 kernel source that need to be ported?

[sent from my nexus 10]

---------- Post added at 01:42 AM ---------- Previous post was at 01:24 AM ----------

I've gotten a couple random reboots with the most recent versions of the kernel. Just got one with the 2/12 kernel on 4.2.2, and grabbed the last KMESG.

Always seems to happen when a webpage is downloading in a browser (chrome and the reddit sync built in browser), but not very often.

lkmsg - https://dl.dropbox.com/u/27280974/Logs/lkm.txt
 

Top Liked Posts

  • There are no posts matching your filters.
  • 144
    Ktoonsez presents:
    50b4432ed9977.png


    THIS SOFTWARE IS PROVIDED BY KTOONSEZ ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.

    IN NO EVENT SHALL KTOONSEZ BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
    SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    KTManta kernel features
    Built with Linaro 4.7 so its 8,000,000,000,000 times faster
    •Linux kernel 3.4.86
    •Google/Samsung open source
    •Optimized kernel configuration
    •unsecure root adb
    •init.d support
    •Governors (MSM-DCVS, ABYSSPLUG, BADASS, SUPERBAD,LAGFREE, SLEEPY, SCARY, SMARTASSV2, WHEATLEY, LAZY, ADAPTIVE, INTERACTIVE, PEGASUSQ, LULZACTIVE, KTOONSERVATIVE, CONSERVATIVE, ONDEMAND, USERSPACE, PERFORMANCE) (most of these coming soon)
    •Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE)

    4fb98c4be2161.png

    Android 4.4 Download flashable KERNEL zip
    http://goo.gl/4APCe9

    Android 4.3 Download flashable KERNEL zip
    http://goo.gl/Iqvxxg

    Android 4.2.2 Download flashable KERNEL zip
    http://www.mediafire.com/?spi7ichqvf32dz1

    Download KTweakerT App 3.4
    (This download is an installable apk file from any File Explorer, not a flashable zip file. ***** IF AFTER YOU DOWNLOAD IT YOUR BROWSER CALLS IT COM.ZIP, RENAME IT TO COM.APK AND INSTALL IT!!!!!!!!!!!! *****)

    http://goo.gl/2P7tUY

    WHEN INSTALLING A NEW VERSION OF KTWEAKER MAKE SURE YOU UNINSTALL THE PREVIOUS KTWEAKER APP, BEFORE INSTALLING NEW KERNEL AND KTWEAKER. AND DO NOT RESTORE ANY OLD FILES OR YOU WILL HAVE PROBLEMS

    Always do the following AFTER installing the kernel:
    1. Clear cache
    2. Clear dalvik
    3. Fix Permissions



    Post #2 will be reserved for change logs

    Post #3 will be reserved for Extras and FAQ's

    Sources can be found here:
    https://github.com/ktoonsez
    41
    Change Log 04.06.2014
    1. ktoonservative: Added up_freq_threshold_hotplug from @bosskindern
    2. ktoonservative: Added down_freq_threshold_hotplug from @bosskindern
    3. ARM: appropriate CFLAGS for Exynos5
    4. ARM makefile : CFLAGS updated
    5. CPUFREQ : pegasusq.c updated
    6. Linux 3.4.75
    7. Linux 3.4.76
    8. Linux 3.4.77
    9. Linux 3.4.78
    10. Linux 3.4.79
    11. Linux 3.4.80
    12. Linux 3.4.81
    13. Linux 3.4.82
    14. Linux 3.4.83
    15. Linux 3.4.84
    16. Linux 3.4.85
    17. Linux 3.4.86
    18. Merge in CM latest ramdisk for CM compatibility
    19 Upgraded to latest Linaro.

    Change Log 12.12.2013
    1. Linux 3.4.73
    2. Linux 3.4.74
    3. Merge in source drop from 4.4.1
    4. Merge in ramdisk from 4.4.2


    Change Log 12.08.2013
    1. Created duplicate permissions lines in ramdisk for CPU sysfs items for the stubborn devices.

    Change Log 12.07.2013
    1. Linux 3.4.71
    2. Linux 3.4.72
    3. CM 11 support!!!!!

    Change Log 11.25.2013
    1. Fixed GPU locking at certain frequency

    Change Log 11.24.2013
    1. Linux 3.4.68
    2. Linux 3.4.69
    3. Linux 3.4.70
    4. Updated toolchain

    Change Log 11.23.2013
    1. Merged in Google source for Kitkat version
    2. Upgraded video/gpu drivers
    3. Upgraded wifi to version 1.88.45

    Change Log 10.28.2013
    1. Ramdisk updates for CM and AOKP compatibility
    2. Linux 3.4.48 - 3.4.67
    3. Wifi upgrade to 1.88.45
    4. KTweaker update to 4.3 Google API
    5. Soooo many more...............

    Change Log 8.4.2013
    1. Merged in newest CM10.2 stuff from pulser_g2 so you guys should have full CM10.2 compatibility

    Change Log 7.28.2013
    1. Fully upgraded to 4.3!!!!!!!!!!!!!!!
    2. Linux 3.4.48
    3. Linux 3.4.49
    4. Linux 3.4.50
    5. Linux 3.4.51
    6. Linux 3.4.52
    7. Linux 3.4.53
    8. Linux 3.4.54
    9. Re-linaro source from upgrade
    10. Merge in newest ramdisk

    Change Log 7.28.2013E
    1. Fix GPU Mhz locking at specific Mhz
    2. Fix GPU table BUG_ON issue that caused reboots on set on boot options and "Load Default Settings"

    Change Log 5.14.2013
    1. Linux 3.4.42
    2. Linux 3.4.43
    3. Linux 3.4.44
    4. Linux 3.4.45
    5. A few GPU updates
    6. Monster update for wifi going to version 1.88.16
    7. deadline: Allow 0ms deadline latency, increase the read speed
    8. block: urgent: Fix dispatching of URGENT mechanism
    9. Updates to Interactive gov
    10. Bunch of low level memory/hrtimer patches
    11. Checkout my github for complete list, Im exhausted.......

    Change Log 4.19.2013
    1. FIXED VIDEO ISSUE
    2. Linux 3.4.40
    3. Linux 3.4.41
    4. Updated ROM scheduler
    5. GPU ION updates
    6. SMP updates
    7. Several fs updates
    8. Optimize lib/memcopy functions
    9. bcmdhd: tweaked wakelocks a bit
    10. Thats all I remember...... :laugh:

    Change Log 4.8.2013
    1. NEW GPU OC STEPS!!!! 667 and 720
    2. All steps are now divisible by 25 by default
    3. Changed KTweaker (now version 3.0) to only let you do steps in 25's for GPU
    4. Linux 3.4.35
    5. Linux 3.4.36
    6. Linux 3.4.37
    7. Linux 3.4.38
    8. Linux 3.4.39
    9. New updated scheduler IO settings from Enigma1987, Osmosis and Malaroths
    10. Chipset speed boosts
    11. Higher bus speeds to feed the higher GPU speeds
    12. Too many upstream updates from google to mention, check out my github if you want to know
    13. Make file optimizations

    Change Log 3.2.2013b
    1. REVERT: Ignore disable_hotpluging while screen is OFF
    2. Cleaned up some unnecessary dmessaging
    3. serial: samsung: fix leaked requested irq
    4. Fix under-sized array while mounting external sdcard's

    Change Log 2.28.2013
    1. Linux 3.4.34
    2. Got Screen OFF Governor going.
    3. Added Screen OFF scheduler, this DOES restore your custom settings when screen comes back on :D
    4. KTweaker 2.9 with added "Screen OFF scheduler" option under "Extras"

    Change Log 2.27.2013
    1. Added battery level MAX MHZ setting for CPU and GPU
    2. KTweaker 2.8
    3. Linux 3.4.33
    4. Added FIFO and FIOPS schedulers (thanks haskerl)
    5. Using Ubuntu 12.10 arm-linux-gnueabihf compiler (thanks haskerl)
    6. A bunch of new -O3 compiler optimization flags added
    7. Lots of upstream google updates
    8. ktoonservative will now Ignore disable_hotpluging while screen is off to save some battery
    9. Thats all I can remember

    Change Log 2.20.2013
    1. All the same stuff as 2.18b + THE COLOR TWEAKS RESTORED FROM TEST KERNELS

    Change Log 2.18.2013
    1. Linux 3.4.30
    2. Linux 3.4.31
    3. Linux 3.4.32
    4. Merged in some CM stuff
    5. Compiling CIFS as module
    6. Some GPU optimizations
    7. A few google updates

    Change Log 2.7.2013
    1. net: wireless: bcmdhd: Update to Version 1.28-27
    2. Added ASIX LAN Support
    3. netfilter: xt_qtaguid: Allow tracking loopback
    4. Re-arrange some code on ktoonservative for efficiency

    Change Log 2.4.2013
    1. Linux 3.4.29
    2. Enabled -O3 Linaro optimization flag so it 40 trillion times faster, lol!!!!!!!!!!!!!!!
    3. Upgraded to Linaro 4.7-2013.01-1-2013
    4. sync: don't log wait timeouts when timeout = 0

    Change Log 2.2.2013
    1. KTweakerT update to 2.7.1, fixed issue where settings were not saving in Thermal Throttle screen
    2. block: row: Idling mechanism re-factoring
    3. block: row: Dispatch requests according to their io-priority
    4. CPU/GPU: adjust MIN/MAX for devices regulators (regulator will now take values all the way down to 700)

    Change Log 1.30.2013
    1. Ktoonservative: Added no_2nd_cpu_screen_off setting to give the ability to keep 2nd core off while screen is off.
    2. netfilter: xt_qtaguid: extend iface stat to report protocols
    3. net: wireless: bcmdhd: Fix WD wakelock behavior
    4. net: wireless: bcmdhd: Postpone taking wd_wake lock
    5. net: wireless: bcmdhd: add check for wake_lock_active on wdwake
    6. FIX mismerge from Linux 3.4.8

    Change log 1.25.2013
    1. Brand new thermal throttling routine (I played Beach buggy for about 3 hours straight before it started to stutter a little bit when crashing into things, lol)
    2. You can adjust the minimum Mhz to drop to during thermal throttling, default is 1200000 (1200 Mhz), sysfs file is here (I will get this in KTweaker when I get a chance)
    "/sys/devices/system/cpu/cpufreq/cput_attributes/min_throttle_mhz"
    So, to layout the logic, the throttling will only got down to 1200 Mhz (if necessary) until you reach your set "start_throttle" temp +15, then it allows throttling down to 800 Mhz, if "Tripping" occurs it allows throttling down to 500 Mhz.

    Change log 1.24.2013
    1. MAJOR additions to ktoonservative so it is fully configurable for all different needs
    2. Ktoonservative renamed "boostpulse_value" to "boost_cpu"
    3. Ktoonservative added "boost_turn_on_2nd_core": Set to a 1 to turn on 2nd core during touch boost, 0 to not.
    4. Ktoonservative added "boost_gpu": Set to 0 to NOT boost GPU during touch boost or use, 100 or 266 or 350 or 400 or 450 or 533 or 612 to boost the GPU to that Mhz.
    5. Ktoonservative added "boost_hold_cycles": Set to a value to hold the boost for, as usual 22 = approx 1 second.
    6. Ktoonservative added "disable_hotpluging": Set to a 0 to leave hotplugging enabled, set to 1 to NEVER hotplug which will leave the 2nd core on full time.
    7. Linux 3.4.27
    8. Fix for empty app-mounted directories (This was requested by Kroenen66)
    9. lib: cpu_rmap: avoid flushing all workqueues
    10. Lots of debug code removed to reduce dmesg

    Change Log 1.18.2013
    1. Linux 3.4.26
    2. KTweaker 2.6.2, added GPU current speed to "General"
    3. Couple tweaks to GPU OC/UC control
    4. Added boost-pulse to Ondemand as promised :D :highfive:
    5. About 50 patches from google upstream source
    6. Some tweaks to deadline scheduler
    7. Thats all folks.............. (out of town all this weekend and next week for work so time was limited on this release)

    Change Log 1.11.2013
    1. Linux 3.4.25
    2. Tweak to ktoonservative that seems to have killed the crackle while playing music.
    3. Couple patches to KTweaker

    Change Log 1.6.2013
    1. Update ktoonservative boost pulse to check current Mhz to make sure it doesnt downscale it.
    2. Update pegasusq boost pulse to check current Mhz to make sure it doesnt downscale it.

    Change Log 1.5.2013-F
    1. Linaro optimization compiler flags
    2. Added Touch Booster to ktoonservative to behave just like interactive
    3. FIXED TOUCH BOOSTER LOCK ISSUE
    4. Use boostpulse_value in Governor Adjustments to set the Mhz to boost to. 1000Mhz is default.
    5. Added Touch Booster to pegasusq to behave just like interactive
    6. Lots of build.prop optimizations from EniGmA1987, here they are:

    kernel.random.read_wakeup_threshold=1024
    kernel.random.write_wakeup_threshold=2048
    kernel.shmmax = 256MB
    net.core.rmem_max = 1.0MB
    net.core.wmem_max = 1.0MB
    vm.swappiness = 10
    vm.vfs_cache_pressure = 20

    Change Log 1.2.2013
    1. Raised Thermal Control upper limit to 200!
    2. Ktoonservative tweaks to make it behave better on 4.2.

    Change Log 12.18
    1. JUMP_LABEL patch
    2. Couple Linux patches from my S3 kernel
    3. Improved slide2wake functionality while unplugged
    4. Linux 3.4.24
    5. Vibration interface is now active (valid values are between 0-49, 0 = no vibration, 49 being max stock strength)
    6. Fixed up CPU/GPU tables to be divisible by 5 so they can be tweaked properly.
    7. Load defaults will now load the default voltages according to YOUR specific device chip.
    8. Thermal throttle interface (not implemented in KTweaker yet but can be accessed in "/sys/devices/system/cpu/cpufreq/cput_attributes" folder.
    9. New KTweaker app
    10. Forgot to tell you guys KTWeaker comes with a Widget, so give it a try. *Remember that widgets are very limited to what they can do. *I.E. there are no drop-lists so I can add governor selection and stuff of that nature.

    ****** Thermal throttle interface ******
    1. BE VERY, VERY, VERY CAREFUL GUYS, I TAKE NO RESPONSIBILITY IF YOU OVERHEAT AND OR MELT YOUR CHIP FROM RAISING THESE VALUES!!!!!!!
    2. Stock values are cpu_start_throttle = 80, cpu_stop_throttle = 78, mem_start_throttle = 85, cpu_stop_throttle = 80
    3. Start values should always be higher than stop values by at least 1
    4. I have a hard coded limit of 50-90 (probably as high as anyone wants to go, I set mine at cpu_start_throttle = 85, cpu_stop_throttle = 83 to test and saw temps of 108 for over 1 second a few times running benchmark apps)

    5. You can also get the current temperature from the "cur_temp" file (I will add this and the adjustments to KTweaker as soon as I can)

    Changelog 12.16
    1. Finished GPU OC/voltage control (thanks pushistiky)
    2. Some tweaks to slide2wake

    Change log 12.15
    1. Linux 3.4.22
    2. Linux 3.4.23
    3. Lots of battery savers for wifi
    4. TCP tweaks for extra speed (Im loving this little opto from Babyhuey)
    5. Sweep2wake is born (use KTweaker to enable it. To use it, swipe from far left to far right or top to bottom without letting go and it wakes up)
    6. GPU voltage control (Use KTweaker under Voltage)
    7. Updated KTweakerT
    7. Updated freq table, thanks to AndreiLux for the help
    8. Added ZEN and ROW scheduler

    Change Log 12.03
    1. KtweakerT is born :D (LINK: http://www.mediafire.com/?z5dhzdxw0io1v0z)
    **** Only the screen OFF Mhz setting is active in Extras so far
    2. Added screen off Mhz setting
    3. Linux 3.4.21
    4. mm/compaction.c: fix deferring compaction mistake
    5. lowmemorykiller: Compact memory when killing processes
    6. lowmemorykiller: Use asynchronous compaction
    7. Added some Ramdisk stuff from CM10 to see if CM10 nightly's will behave!
    LINK: http://www.mediafire.com/?ysv8roskclixdsb

    Change Log 11.29
    1. Linux 3.4.9 thru 3.4.20
    2. HDMI audio out fix (thanks craigacgomez)
    3. Added governors (slp, intellidemand, abyssplug, badass, pegasusq)
    4. Overclock/Underclock
    5. Voltage control
    6. That's all I can think of
    LINK: http://www.mediafire.com/?iah1p5ky4j2uwr7

    Change Log 11.26
    1. Initial Release
    LINK: http://www.mediafire.com/download.php?tk0qqvde82fvaqz
    29
    ****** Thermal throttle interface ******
    1. BE VERY, VERY, VERY CAREFUL GUYS, I TAKE NO RESPONSIBILITY IF YOU OVERHEAT AND OR MELT YOUR CHIP FROM RAISING THESE VALUES!!!!!!!
    2. Stock values are cpu_start_throttle = 80, cpu_stop_throttle = 78, mem_start_throttle = 85, cpu_stop_throttle = 80
    3. Start values should always be higher than stop values by at least 1
    4. I have a hard coded limit of 50-90 (probably as high as anyone wants to go, I set mine at cpu_start_throttle = 85, cpu_stop_throttle = 83 to test and saw temps of 108 for over 1 second a few times running benchmark apps)

    5. You can also get the current temperature from the "cur_temp" file (I will add this and the adjustments to KTweaker as soon as I can)

    Governors and schedulers explained:
    http://xdaforums.com/showthread.php?t=1866139
    http://xdaforums.com/showthread.php?t=1687578
    http://xdaforums.com/showthread.php?t=1369817
    http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
    http://xdaforums.com/showpost.php?p=21638852&postcount=56
    http://www.phoronix.com/scan.php?page=news_item&px=MTAzOTU

    Voltage starting point for you UV'ers
    Code:
    1700MHz  1100mv, stable
    1600MHz  1075mv, stable
    1500MHz  1050mv, stable
    1400MHz  1025mv, stable
    1300MHz  1000mv, stable
    1200MHz  975mv,  stable
    1100MHz  950mv,  stable
    1000MHz  925mv,  stable
    900MHz   900mv,  stable
    800MHz   875mv,  stable
    700MHz   850mv,  stable
    600MHz   850mv,  stable
    500MHz   850mv,  stable
    400MHz   850mv,  stable
    300MHz   850mv,  stable
    200MHz   850mv,  stable
    28
    4fb98c4be2161.png


    Change Log 5.14.2013
    1. Linux 3.4.42
    2. Linux 3.4.43
    3. Linux 3.4.44
    4. Linux 3.4.45
    5. A few GPU updates
    6. Monster update for wifi going to version 1.88.16
    7. deadline: Allow 0ms deadline latency, increase the read speed
    8. block: urgent: Fix dispatching of URGENT mechanism
    9. Updates to Interactive gov
    10. Bunch of low level memory/hrtimer patches
    11. Checkout my github for complete list, Im exhausted.......

    ENJOY!!!!!!
    28
    OP Updated

    4fb98c4be2161.png

    Android 4.4 Download flashable KERNEL zip
    http://goo.gl/4APCe9

    Change Log 04.06.2014
    1. ktoonservative: Added up_freq_threshold_hotplug from @bosskindern
    2. ktoonservative: Added down_freq_threshold_hotplug from @bosskindern
    3. ARM: appropriate CFLAGS for Exynos5
    4. ARM makefile : CFLAGS updated
    5. CPUFREQ : pegasusq.c updated
    6. Linux 3.4.75
    7. Linux 3.4.76
    8. Linux 3.4.77
    9. Linux 3.4.78
    10. Linux 3.4.79
    11. Linux 3.4.80
    12. Linux 3.4.81
    13. Linux 3.4.82
    14. Linux 3.4.83
    15. Linux 3.4.84
    16. Linux 3.4.85
    17. Linux 3.4.86
    18. Merge in CM latest ramdisk for CM compatibility
    19 Upgraded to latest Linaro.

    ENJOY GUYS!!!!!!!! If anybody is still out there, lol :good: :highfive: