[KERNEL][Nexus 10] KTManta Version 5.14.2013

[Achtung] Verwendung auf eigene Gefahr! Weder pocketpc.ch noch trigg3r haften für irgendwelche Schäden!


Kernel Features:

•Built with Linaro 4.7 so its 8,000,000,000,000 times faster
•Linux kernel 3.4.24
•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)


DOWNLOADS:

DOWNLOAD Kernel CWM Flash ZIP

Download KTweakerT App 3.3 (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!!!!!!!!!!!! *****)


Nach dem Flashen des Kernels immer folgende Dinge durchführen:

1.I RECOMMEND CLEARING APP DATA FOR KTWEAKER BEFORE FLASHING THE KERNEL!!!!!!!!!!!!!!!!!!!!!!!!!!
2. Clear cache
3. Clear dalvik
4. Fix Permissions



Changelogs:

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......

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
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 so its 8 bazillion times faster (thanks haskerl)
6. A bunch of new -O3 compiler optimization flags added
7. Lots of upstream google updates
8. Thats all I can remember

You can find Battery Level Control under extras. Set a Low and High battery Level (for example: 30 for high and 15 for low) and then pick what Mhz to drop to for the corresponding Low and High Levels. KTweaker will show in RED when the GPU and CPU have been brought down under Battery Control.

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

Change Log 2.18.2013b
1. Fix icon for charging thru USB.

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.29.2013
1. Linux 3.4.28
2. Couple updated values in stock ktoonservative settings
3. Updated KTweaker app to 2.7
4. KTweaker: Fixed constant question about Governor Adjustments when on Interactive governor (I would suggest you clear app data to totally kill the question or at least change 1 value in the governor adjustments screen so it can fix the bad values)
5. KTweaker: Added Minimum Thermal Mhz setting under "Extras->Thermal Throttle Control" (as I stated in an earlier release it will use the value you enter for temps ranging between "Start Throttle" value thru "Start Throttle" +15 degrees)

Change Log 1.27.2013
1. Fixed issue with loading voltage from stock tables

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)

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 Governor as promised
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 for 99% of people.
3. Couple patches to KTweaker
4. If you downloaded tonights test you dont need this.

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.

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 (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


Untervolting stabile Werte:

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



Quelle

Werde mir diesen Kernel gleich flashen, nachdem ich mein Nexus 10 bekommen und unlockt habe

Wie läuft der denn so @trigg3r?
Oder postest du den nur?

Gesendet von meinem Nexus 10 mit Tapatalk 2

ne hab ihn auch drauf. läuft gefühlt besser als der normale und bietet halt auch OC und UV Möglichkeiten. Ich glaube timsah hat ihn auch drauf. Einzig nervige ist. Wenn jetzt CM drauf hast, dann musst nach dem nightly flashen auch immer den Kernel neu flashen. Die nightlies überschreiben den immer.

neue Update:

Quote:
Download CWM flashable KERNEL zip
http://www.mediafire.com/?vleckx3yqqmdsac

Download KTweakerT App (this download is an installable apk file from any File Explorer, not a flashable zip file)
http://www.mediafire.com/download.php?9vsl0ekbe84vigb
Change Log 1.11.2013
1. Linux 3.4.25
2. Tweak to ktoonservative that seems to have killed the crackle while playing music for 99% of people.
3. Couple patches to KTweaker
4. If you downloaded tonights test you dont need this.



erster Post ist upgedatet

Also sollte man zuerst CWM oder den Kernel draufmachen?
Was hast du denn dann nach flashen des Kernels noch an Einstellungen vorgenommen? Bin da nicht so erfahren und wollte da am liebsten ne Version bei der die Einstellungen schon auf "schnell aber sicher" sind

Du brauchst cwm um den Kernel zu flashen. Ich habe nur etwas die CPU und gpu undervoltet (ist bei jedem unterschiedlich, wieviel man kann, muss man testen) und halt ein anderes governer eingestellt

Gesendet von meinem GT-I9300 mit Tapatalk 2

Sorry, hatte mich verschrieben. Ja CWM stimmt, braucht man. Meinte eigentlich CM. Also erst Rom drauf oder erst n neuen Kernenl drauf?
CPU und GPU undervoltet, sorry wenn ich so blöd frage aber wo genau mach ich denn dann das?
Mit den Werten dann?

1700MHz 1100mv, stable (wenn ich mir die Mhz anschaue sollte das ja theoretisch der höchste Wert sein oder?)

Die Werte beziehen sich doch nur auf die CPU oder?

Ist da schon n governor dabei oder muss ich mir den noch besorgen? Hatte mich mal n bissel eingelesen, ist der "ktoonservative" so ein "Conservative Governor" ?

Grüße

Ich würde erst die Rom flashen, weil die Rom sonst den Kernel überschreibt. Du stellst das alles in der ktmanta App ein. Kannst aber auch andere Apps benutzen wie voltage Controle

Gesendet von meinem GT-I9300 mit Tapatalk 2

guten Morgen ********

als Newcomer hätte ich mal eine Frage,oder auch zwei.....

auf welcher Taktrate lasst ihr diesen Kernel laufen,
wie sind eure Erfahrungen,
und mit Paranoid 3 gleichzeitig ?

habe das Gefühl richtig smooth ist er nicht ?????

danke

F

hi,

also bei mir läuft er top. Habe ihn auf dem Takt wie die Standardwerte der CPU sind. Welche Einstellungen hast du den vorgenommen? Habe auch Paranoid 3 drauf. Hast die aktuellste Version von dem Kernel drauf?

p.s. Bitte beim nächsten Mal nicht wieder den kompletten Eröffnungsbeitrag zitieren. Musst erst suchen wo deine Frage ist.

Danke für die schnelle Antwort !

also ich habe jetzt

Paranoid 3.56
3.4.45 KTT Manta
max. 2:000 CPU
io : cfq
gpu govenor : performance
quadrant : 4743

Hatte mal mit CM über 6.000.... komisch, aber das wird das Verhalten des Tablets ("smooth") nicht ausschließlich bestimmen....

Grundsätzlich finde ich das N10 jetzt smooth, hatte vorher 1.700 eingestellt, dabei übersehen, das es sich dabei um untertakten handelt ?

F.

Ne eigentlich handelt es sich nicht um untertakten. Du bist mit 2000 am übertakten. Bei mir sieht es ATM so aus. Und bissel undervoltet

Gesendet von meinem Nexus 10 mit Tapatalk 2

Blöde Frage, installier ich jetzt zuerst diese Ktweaker App oder zuerst den Kernel?
Nachdem der schreibt das man erst den Ktweaker Cache leeren sollte...

installier erst den Kernel dann die App. Den Cache lässt er meist löschen wenn da ein gravierendes Update am Kernel stattgefunden hat, weil die App dann die falschen information im Cache hat.

Zitat von trigg3r

installier erst den Kernel dann die App. Den Cache lässt er meist löschen wenn da ein gravierendes Update am Kernel stattgefunden hat, weil die App dann die falschen information im Cache hat.

Habe mir auch für CM noch die Gapps runtergeladen.
Die scheine ich ja auch über CWM installieren zu müssen.
Sollte ich die vor oder nach dem Kernel draufmachen?
Bin absolut planlos...

erst CM installieren und direkt danach die GAPPS. dann mal das Tab booten lassen. Danach wieder in CWM den kernel flashen, booten lassen und die App installieren

mist jetzt habe ich das gerade einfach mal genau anders herum gemacht. Einfach Kernel neu installieren nachdem ich jetzt die gapps drauf habe?

ne dann ist wurst.... die gapps haben damit eh nix am hut. dachte du installierst gerade CM neu drauf deswegen. dann würde ich halt eher so vorgehen^^

Ok dann lass ich das mit neu installieren.
Der bringt hier grade beim installieren der ktweaker app "your saved i/o scheduler does not match current, apply i/o scheduler."
Ja / nein?