Strona 1: Informacje
Strona 2: Lista zmian i Linki
Strona 3: Dodatkowe informacje i FAQ
Instrukcje:
Upewnij się, że posiadasz ostatnią wersję bootloadera (4.18 dla Androida4.2.2) lub (4.23 dla Androida 4.3)przed wgraniem tego lub innego kernela. Poszukaj flaszowalnego zip'a lub użyj bootloadera i obrazu google. Metoda przy użyciu fastboota jest bardziej rekomendowana.
Pobierz i skopiuj kernel na kartę SD. Wgraj przy pomocy recovery. Zresetuj. Pogratuluj sobie mądrej instalacji najlepszego kernela na Nexus 7.
Podstawowa lista zmian:
Milestone Release 2 (mr2)
•bazuje na ostatnim źródle kernela aosp google tegra mr2 dla androida 4.3
•kompatybilny ze wszystkimi ROMAMI bazującymi na 4.3.x
•wszystkie zmiany z mr1 + takie których autor nie wypisał 🙂
Milestone Release 1 (mr1)
•bazuje na ostatnim źródle google aosp kernela tegra soaurce mr1.1 dla androida 4.2.2
•kompatybilny ze wszystkimi ROMAMI bazującymi na 4.2.x
•podkręcanie CPU do 1.7GHz
•podkręcanie GPU do 700MHz
•LP core podkręcony do 666MHz
•Możliwość kontroli napięcia dla CPU i komponentów rdzenia takich jak EMC, GPU i LP (faux123)
•CIFS, NFS, NTFS, HFS, ZRAM, i wiele więcej.
•Przełączanie się do wyższej jakości ditheringu dla lepszej jakości gradientu (Rozpraszanie błędów)
•wyłaczenie KSM i zagęszczenia dla wydajności.
•Usunięcie bezużytecznego Debugowania.
•Kontrola FSync (Ezekeel)
•Konfiguracja Wifi tryb zarządzania mocą(PMFAST/PMMAX)
•Zawiera ramdisk z zoptymalizowanymi opcjami montowania takimi jak 'discard' i 'noauto_da_alloc' (nie potrzeba więcej skryptów init.d)
•Zawiera ramdisk z zoptymalizowanymi ustawieniami VM
•zoptymalizowany kompilator flag
•Ostatnie linaro 2013 gcc toolchain
•Dynamiczne EDP - włączone edp cpu maksymalne taktowanie limitowane tylko powyżej pewnej temperatury(motley)
•wyłączenie obniżania maksymalnego taktowania o 100MHz kiedy aktywny jest więcej niż jeden rdzeń
•Domyślne napięcia CPU ustawione dla 3 poziomów
•Działające wątki hot pluggingu
•Glibc memcpy i memmove
•ulepszenia Deadline dla solidnego stanu sterowników
•Wymuszanie wysokiego aktualnego ładowania przez USB (imoseyon)
•Proporcjonalne redukcje dla TCP
•poprawiona nieruchomość dla oglądalności obecnych aplikacji
•Zoptymalizowany SLUB i użycie SLUB przez domyślne zamiast SLAB
•wariant wyświetlaniaTegra 3 (faux123)
•Szybsze przejście LP -> G
•Zoptymalizowany pomocnik swahb32 byteswap
•Asynchroniczne opóźnienie I/O poprawione przez usunięcie wtyczki w do_io_submit()
•zamanipulowane parametry CFS
•Zoptymalizowany algorytm ARM RWSEM
•Zablokowanie: rekurencyjnych wywołań scalających
•regulator czasowy: zoptymalizowany aplpy_slack()
•Wyłaczony GENTLE_FAIR_SLEEPERS dla poprawy wydajności
•zbalansowany EDP limitów taktowań dla bycia takich samych na wszystkich rdzeniach
•LowMemoryKiller asynchroniczne zagęszczenie i zagęszczenie gdy zabijane są procesy
•umożliwianie korzystania z kontrolera natywnej wielkości bloku max
•Zoptymalizowane algorytmy crypto
•Zoptymalizowane rutyny AES i SHA1•Better hotplugging delays
•Zwiększenie boost_up_threshold dla zegara AVP
•wsparcie kexec-hardboot dla multirom
•minimalna wydajność cpu dla otwarzania audio (faux123) z dodanymi poprawkami
•obniżenie minimalnego poziomu podświetlania dla lepszego mniejszego widzenia światła
•przełączenie do_fsync() do fget_light()
•Dodane ostatnie BFQ I/O scheduler
•Naprawienie błędu gdy następuje odłączenie urządzeń OTG (intersectRaven)
•Dodano Tegra sterownik wysokiej wydajności pamięci AHB z poprawkami i ulepszeniami
•Wejście: wysyłanie jednego pakietu na raz
•wsparcie dla wbudowanego OTG
•Dodano ostatni ROW scheduler z poprawkami i ulepszeniami
•Ustawione napięcie jądra na 0.95V w trybie pierwszym dla znacznych oszczędności baterii w pół uśpieniu
•kontrola przeciążenia TCP z Westwood jako domyślny
• Wyłączona kompresja zakresu dynamiki głośników dla lepszej jakości dźwięku głośnika
• Regulator wydajności wszystkich 4 rdzeni
• poprawki LowMemoryKiller i ulepszenia
• Wiele ulepszeń scheduler i optymalizacje
• Miliony innych poprawek i ulepszeń, na które nie ma czasu ani miejsca 🙂
Polecane ustawienia:
Jedyną aplikacją wspierającą jakiekolwiek zmiany parametrów kernela i ustawień jest TricksterMod - https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
Zarządca CPU - TouchDemand z domyślnymi parametrami (ustawiony domyślnie)
I/O Scheduler -
- Deadline (domyślnie) dla czystej szybkości I/O.Szybsze prędkości odczyty i zapisu. Może powodować okazlonalne lagi przy instalowaniu/pobieraniu w tle
- ROW dla czystej prędkości odczytu.Szybkie odczyty co jest często najważniejsze w urządzeniu mobilnym. Bardzo podobne do Deadline.
- BFQ dla ogólnej smukłosci. wolniejszy od Deadline i ROW, ale zapobiega zacinaniu podczas instalacji/pobierania w tle
Maxymalne taktowanie - 1.2Ghz (Domyślne dla więcej niż dwóch rdzeni)
- Notatka: Tegra ustawia maksymalne taktowanie na 1.5Ghz przy starcie, upewnij się, aby zmienić to ręcznie lub miej aplikację do zmiany tego na starcie, by uniknąć szybszego zużycia baterii.
- Notatka druga: NIE UŻYWAJ SYSTEMOWYCH APLIKACJI DO ZMIANY TAKTOWANIA. NIE WSPÓŁPRACUJĄ Z AUDIO PERFLOCK W KERNELU. NIE używaj systemowej aplikacji do ustawiania taktowania jak nie współpracuje z wydajnością dźwięku, która jest w tym kernelu. Uniemozliwi obniżenie maksymalnej częstotliwości. Używaj Trickstermod.
Maksymalne taktowanie GPU - 446Mhz (utrzymuje dobrą żywotność baterii przy jednoczesnej wydajności w grach THD)
- Możliwe częstotliwości -
Fsync - Właczone
Dynamic Fsync - Włączone (zdawajcie sobie sprawę z utraty danych, nawet jeśli w rzeczywistości są minimalne)
SmartDimmer/PRISM - Wyłączone
zRAM - Wyłączone/Brak (Domyślne) (Absolutnie bezużyteczne na android 4.0+ i powyżej 1GB RAM)
Dane montazu - aktualnie zawarte w ramdisk. Dodawanie skryptów nie wymagane.
NIE POLECAM, ani nie popieram żadnego rodzaju optymalizacji / supercharger / skryptów placebo. Wsyztskie ustawienia są optymalne i są w jadrze lub ramdisku. Korzystanie z innych skryptów może doprowadzić do problemów i spadku wydajności.
LINK DO NAJNOWSZEJ WERSJI
M-Kernel a67
LISTA ZMIAN I LINKI:
Alpha Changelog (stable feature list above):
a67 - Update + sync ramdisk from cm11 to enable native USB OTG. Add thermal charging shut off. Some kconfig tweaks.
a66 - Only hold wakelock is touch/slide to wake is enabled. Tweak default BFQ values a bit.
a65 - Update BFQ from 5.1 to 6r2. Set BFQ as default for testing. Tweak Deadline and CFQ (Franco's CFQ values). If CFQ is still causing reboots for some, I will revert it to stock in next build. Cgroups timer slack controller. Enable RCU priority boosting for testing.
a64 - merge 4.4 kernel changes. Update ramdisk for 4.4
a63.1 - CM hotfix
a63 - Add Tegra 4 SmartDimmer (ported from TripNRaVeR's port for the One X). It either works much better or is completely broken. Either way, it's an improvement from the old SmartDimmer. Add necessary ramdisk change for PAC rom. Add dm9620 usb ethernet support. Switch back to linaro 4.7 toolchain from google 4.6 (used in mr2 for stability reasons).
a62 - Add double tap to wake thanks to flar2 and sgt. meow. Add configurable timer to keep double tap to wake active after screen shut off. Remove Fsync toggle. Pointless and confusing with Dynamic Fsync available now. Update Dynamic Fsync from faux123. Set backlight levels back to defaults and disable otf_scaling. Some random stuffs.
New sysfs:
/sys/android_touch/wake_timeout
Value is in seconds. Defaults to 60. Set to 0 to keep double tap to wake permanently active at the price of battery.
a61 - Enable compass driver. Add Dynamic Fsync by Faux123. Disable Fsync off at boot. Enable Dynamic Fsync at boot. Remove wifi pm fast/max toggle as it is now pointless and won't work since 4.3 kernel update. Add an older, but simpler, version of usb host mode by mehrvarz. Fixed and enabled many 4.3 config options relating to things like selinux.
a60 - More ramdisk fixes
a59 - Update cm10.2 ramdisk to fix storage issues. Fix 00su init.d.
a58 - Incorporate cm10.2 ramdisk.
a57 - Update to 4.3 kernel base. 4.3 stock only. Ramdisk base courtesy of Francisco Franco. Fsync off at boot since the internal storage is just so appallingly slow.
a56 - Add back some missing config options removed in a55 to support various features. No CIFS support. Couldn't get it to boot for some reason.
a55 - Add v2 of Tegra AHB patch set. Remove and revert USBHOST patches. Revert to almost stock kernel config for testing (will probably revert back later). Revert to stock PA ramdisk for testing. Tweak default TouchDemand parameters for bettter performance. Hard-code deadline and cfq tuneables thanks to the work by those in Franco's thread - details in commitlog on github. Set deadline as default I/O scheduler. Add core hotplugging lock during touch boost/input to interactive governor based on implementation in stock interactive governor (not fully tested). Other minor, inconsequential changes.
a54 - Remove AHB bus drivers and patches.
a53 - USBHOST support and patches. WiFi adhoc IBSS support.
a52 - revert voltage table changes
a51 - fix flickering at brightness level 13 when smartdimmer was enabled by setting SD min to 10. Re-enable a 3g modem reset assignment fix. It was disabled in a49/a50; let's see if re-enabling it causes 3g drops to return (Otherwise TCP proportional rate reduction was the cause). Re-enable wifi p2p patch that was disabled in a49 under the impression it wasn't included in the stock kernel when it actually is (whoops). Increase the some DVFS voltages so that that they are at least as high pre-a50 (according to DVFS debug showing actual running voltage) and not more than 25mV greater than pre-a50. Hard-code default pm_qos_max_cpus as 4 instead of ULONG_MAX. Fixes aesthetic bug where the default tegra hotplug max_cores was 2147483647 (For the curious - it is 2^31 − 1, the maximum value for a 32-bit signed integer in computing).
Oh, and change thread title to accord with new XDA requirements.
a50 - re-enable dynamic edp. Rework some edp limits. Rework DVFS voltage tables to better match frequencies, YMMV. Removed 1.7GHz max frequency option as it was pretty split whether your device could run it or not. If people were more responsible and wouldn't complain about issues when running 1.7 or higher I would leave it in, but unfortunately that's just not the case. So it saves me headaches in the future. Sorry. It's a minor increase from 1.6GHz and most can do 1.6 just fine.
a49 - add some rwsem patches. Revert TCP proportional patch. Revert a wifi p2p patch. Fully stock /net and drivers/net in source now. Add custom min/max backlight interface. I'll add more info when I'm not so busy. Removed zRam support.
Change your max backlight (min - 255) - /sys/module/board_grouper_panel/parameters/max_backlight
Change your min backlight (1 - max) - /sys/module/board_grouper_panel/parameters/min_backlight
Enable/Disable on-the-fly backlight level redistribution through available brightness slots based on new min/max using math below (0/1) - /sys/module/board_grouper_panel/parameters/otf_scaling
- brightness = min_backlight + DIV_ROUND_CLOSEST(((max_backlight - min_backlight) * max((brightness - 10),0)),245);
a48 - actually upload a kernel that is mr1 + row patches + flash fix
a47 - mr1 + row patches + flash fix accidentally uploaded old kernel version...
a46 - disable have_efficient_unaligned_access. Add USB Host mode charging patches.
a45 - Fix adobe flash corruption. Add ARM unaligned access and enable have efficient unaligned access. Make sure slider min brightness and auto-brightness min have the same backlight value.
a44 - Start over at mr1. Add ROW patches. Add LZ4 compression.
a43 - revert all network and wireless patches since mr1.
a42 - revert some config options. Fix fixed_mode on boot for multiboot. Sched_mc_power_savings set to 0 instead of 2 to see how it affects wakeup.
a41 - ARM cpu topology and relevant patches. Enable multi-core scheduling. Enable maximum multi-core scheduling power savings for testing. Switch back to LZ4 ramdisk compression as Multiboot supports it now. Increase touchdemand sampling down factor since sampling rate was decreased previously.
a40 - Revert SLQB. Add latest usb host mode charging from mehrvarz's repo. Force detect/report usb as ac, no apparent benefit. Enabled a config SVIPC or something... I forget. Enabled rndis support from CM.
a39 - SLQB allocator. Switch back to Gzip ramdisk compression for multirom.
a38 - Fix adobe flash playback. Super fast Lz4 compressed for ramdisk and kernel. Arm unaligned efficient memory access. Some misc. wifi and network patches. Many other changes. No guarantees.
__________________________________________________
Downloads:
Alphas 4.4 -
•a67 - http://goo.im/devs/Metallice/Nexus7/...Kernel_a67.zip
•a66 - http://goo.im/devs/Metallice/Nexus7/...Kernel_a66.zip
•a65 - http://goo.im/devs/Metallice/Nexus7/...Kernel_a65.zip
•a64 - http://goo.im/devs/Metallice/Nexus7/...Kernel_a64.zip
Milestone 4.3.x Releases -
•mr2 (4.3.x)
http://goo.im/devs/Metallice/Nexus7/...Kernel_mr2.zip
Alphas 4.3 (post mr2) -
•a63.1 - http://goo.im/devs/Metallice/Nexus7/...rnel_a63.1.zip
•a63 - http://goo.im/devs/Metallice/Nexus7/...Kernel_a63.zip
•a62 - http://goo.im/devs/Metallice/Nexus7/...Kernel_a62.zip
Milestone 4.3.x Releases -
• mr2 (4.3.x)• Goo.im Downloads - Browsing ...Kernel_mr2.zip
Alphas 4.3 -
•a61 - Goo.im Downloads - Browsing ...Kernel_a61.zip
•a60 - Goo.im Downloads - Browsing ...Kernel_a60.zip
•a59 - Goo.im Downloads - Browsing ...Kernel_a59.zip
•a58 - Goo.im Downloads - Browsing ...Kernel_a58.zip
•a57 - Goo.im Downloads - Browsing ...Kernel_a57.zip
Milestone 4.2.x Releases -
• mr1 (4.2.x)• Goo.im Downloads - Browsing ...Kernel_mr1.zip
Alphas 4.2.x -
•a56 - Goo.im Downloads - Browsing ...Kernel_a56.zip
•a55 - Goo.im Downloads - Browsing ...Kernel_a55.zip
•a54 - Goo.im Downloads - Browsing ...Kernel_a54.zip
•a53 - Goo.im Downloads - Browsing ...Kernel_a53.zip
•a52 - Goo.im Downloads - Browsing ...Kernel_a52.zip
FAQ:
THIS ENTIRE POST IS A WIP THAT I WILL FINISH LATER.
Glossary of terms:
(that one may not be as familiar with as things like CPU and GPU)
SoC - A System on a Chip, which the Tegra 3 is, is an integrated circuit that includes all the important components of a computer, such as CPU, GPU, RAM, etc into a single chip
Hotplugging - the process of turning CPU cores on and off.
G core(s) - One of four ARM A9 CPU cores found in the Tegra 3 SoC
LP (core) - The ARM A9 "Low-Power" CPU core found in the Tegra 3 SoC in addition to the 4 G cores. The LP core, contrary to what many seem to believe, does not run in tandem with the 4 G cores.
Runnable Threads (hot plugging) - Limits turning on more cpu cores based on the average number of running threads
Touchdemand - A modified ondemand-based governor that I designed and configured to better suit the Tegra 3 and android based on my observations
Variant -
Scheduler -
Other things
FAQ:
What's the difference between the mr(#) version/download and the a(#) version/download? Which should i download? What do these acronyms mean/stand for?
The mr# (ex. mr1) stands for milestone release number #. The milestone builds are the stable, bug-free, and thoroughly, extensively, and expansively tested builds of m-kernel.
The a# (ex. a38) stands for alpha build number #. The alpha builds listed under downloads are all of the alpha builds after the latest milestone build listed in reverse chronological and "morphological" (? FIX) order. It is the continuation of the "alpha branch" of m-kernel, and is basically the latest milestone with a ton of patches, fixes, and changes that are completely UNTESTED by anyone but me. The number and substantiality of changes since the latest milestone obviously vary and also depends on the number of alpha builds since the latest milestone release. An alpha build isn't guaranteed to be stable, working, and bug-free. They are testing builds leading up to the next milestone
Do you recommend setting the maximum number of cores to 2?
I don't necessarily recommend everyone do this, for it really comes down to personal preference. However, limiting the maximum cores to two is a very simple change to make that will slightly improve battery, with little to no impact on performance. Android 4.x is highly optimized for dual-core processing. There is no part of the Android 4.x OS that needs more than 2 cores for a smooth experience, and likewise there are few to no android applications that need 2 cores.
For the most part, the 3rd and 4th g cores are only activated during time sensitive actions such as opening an app for the first time (i.e. not previously opened and cached in RAM) and during screen rotation. These are short lived operations meaning those 3rd and 4th g cores are quickly turned off afterwards. In essence a small hit to battery life for even smaller benefits.
Why won't my minimum frequency go below 340MHz?!?
As long as you don't use system tuner, the minimum frequency does go below 340MHz. The minimum frequency is temporarily raised to 340MHz during an audio event to prevent audio playback problems when using ondemand and similar governors. The minimum frequency returns to the previous value afterwards. Some apps may show the minimum frequency as 340MHz because clicking the app to open it created a sound causing the minimum to temporarily rise. The app does not change when the minimum frequency goes back to its previous value.
Why can't over clock the GPU as high as I can on other kernels!?!
You can. You have to raise the voltage for the top GPU slot. Other kernels do this automatically and to fixed values. The amount necessary depends on the GPU frequency you are trying to run and your device. No devices are alike and the voltage necessary at whatever frequency will vary considerably from device to devices. Be aware that having to overvolt to run a certain frequency may mean suggest that you shouldn't run that frequency anyway. Raising the GPU frequency and voltage has risks to consider
What is this tegra 3 "variant" or whatever? How do I find it? What does it meeeeaaaannnn??!!?
You can find this info in /sys/kernel/debug/t3_variant
In the stock kernel/source, each device sku is recognized and assigned four ID values. For the CPU there is a primary "cpu speedo id" and a secondary "cpu process id". For the SOC, or core (think LP core, RAM, GPU, etc), there is a primary "soc speedo id" and a secondary "soc process id."
Each "pair" of ids is used to choose the respective voltage tables for the components they represent. I'm going to ignore the soc/core ids as they aren't relevant to my point and are the same for all our devices.
The CPU voltage tables are represented by ( cpu_speedo_id # , cpu_process_id #). The voltage tables that share the same first number, the cpu_speedo_id, all end with the same MHz value. To make things simple, Tegra uses the maximum frequency in the voltage table to determine the maximum frequency. All of our Nexus 7 Tegra 3s share the same cpu_speed_id, corresponding to a maximum frequency of 1.3GHz.
The second number, the cpu_process_id, differs between all of our N7 T3's. For whatever reason, Faux123 and everyone refers to value as our "variant." Why Faux123 calls this your "variant" instead of the true name cpu_process_id I don't know. Regardless, this value, cpu_process_id determines the voltages for each frequency in the table. For each increase in cpu_process_id, the RANGE of voltages for the voltage table is compressed by 25mV (i.e. the voltage for the top frequency is decreased by 25mV while the bottom stays at 800mV and the middle frequency voltages are adjusted accordingly).
Therefore, in a direct sense, the cpu_process_id, or "variant", HAS NOTHING TO DO WITH CPU FREQUENCY. I'll repeat this. YOUR CPU_PROCESS_ID OR VARIANT HAS NO DIRECT CONNECTION TO THE MAXIMUM FREQUENCY CAPABILITIES OF YOUR CHIP. Variant/cpu_process_id refers to the voltage tolerance of your cpu. While there may be correlation or secondary connection to the maximum frequency capabilities of your chip, there is not direct connection. Additionally, cpu_process_id HAS NOTHING TO DO WITH YOUR SOC/CORE AT ALL, WHICH INCLUDES YOUR GPU/LP/RAM. A high cpu_process_id tells you nothing about your core and how high you can clock your GPU.
TL;DR - Variant, or more accurately cpu_process_id, refers to voltage tolerance, and has no direct connection to the max frequency abilities of your chip, and definitely has absolutely no relationship to your core/GPU.
To do:
Core voltages quirks.
Max freq delay necessity.
Why doesn't the kernel come with recommended settings?
POZOSTAŁĄ CZĘŚĆ TEKSTU PRZETŁUMACZĘ PRZY CHWILI WOLNEGO CZASU 🙂!