[Kernel][5.1] M-Kernel - a76/77 [WiFi/3G] [f2fs/ext4] [5/14/15]
- Thread starter Metallice
- Start date
This is not really the place to discuss this, sorry if I upset anyone.
I'm using latest ROM from this thread, it's CM11 with newest security fixes.
http://forum.xda-developers.com/nex...ficial-build-cyanogenmod-11-0-nexus-t3174831/
I converted it to F2FS myself with the tool from this thread
http://forum.xda-developers.com/nexus-7/development/tool-grouper-ext4-to-f2fs-rom-converter-t2801653
Afterwards you have to flash a F2FS compatible kernel -> M-kernel.
PS: I had troubles flashing the kernel with latest TWRP 2.8.7.0, but it worked with older TWRP version 2.8.3.0.
Also I'm using pico OpenGapps, all this together gives me the best experience for my old Nexus.
Here you go, converted it:
http://forum.xda-developers.com/nex...11-0-nexus-t3174831/post63790155#post63790155
Sorry I'm bit out of touch with the situation here. Could you please point out which version of the M kernel you use with CM 11?
Also wonder if latest PA builds have these security patches. I'm asking because PA used to work bit better with this Nexus 7.
I will maybe first try to convert PA 5.1 (what is their last build I think) to f2fs, and if that doesn't work or I found another reason (like lack of security patches) I'll go with CM 11 from the link you kindly provided.
Also could someone please mention what is the latest Android version supported by the latest version of this kernel?
Sent from my Nexus 7 using Tapatalk
M-kernel a69 is the latest kernel for Android 4.4.
I have no idea if PA has the latest security fixes.
For Android version compatibility check the 2nd post of this thread.
Just a silly question that i couldn't find answer in the thread.
for version a77, does it still have doubletap2wake feature?
i don't see it on Trickster MOD anymore.
Please guide me to...thx
Unfortunately not - it was removed in version a74.
Here's the info from the changelog:
It's a pity really, I would really love touch2wake for my tablet as I use at as a music console in my apartment. It would be nice and easy for guests to just tap on the screen and select their songs. Unfortunately, I'm running Lollipop so I can't even revert to the earlier version.
Thanks for pointing out~~!
yea..i think the tou2wake feature is useful feature on this tablet since the power button location is not that convenience to push
by the way, i think you can revert to the earlier version by flash the factory image. Isn't it?
True, but I want to stay on Lollipop.Thanks for pointing out~~!
yea..i think the tou2wake feature is useful feature on this tablet since the power button location is not that convenience to push
by the way, i think you can revert to the earlier version by flash the factory image. Isn't it?
Sent from my SM-G900F using Tapatalk
Hi all,
after few months on Android 5.x.x I came back to SLIMkat ROM (4.4.4). Everything is running well, I'm just not able to flash M-kernel a69 with the ROM. I was using this combination in the past, so I really don't understand why it's not working right now.
I'm using Pico Opengapps 4.4.4, M-Kernel a69. zip, TWRP 2.8.7.0
In recovery the prosess looks OK, ends with 'DONE... pls reboot', but when thy system loads, I still have stock slim kernel.
Any advice, what I'm doing wrong?
after few months on Android 5.x.x I came back to SLIMkat ROM (4.4.4). Everything is running well, I'm just not able to flash M-kernel a69 with the ROM. I was using this combination in the past, so I really don't understand why it's not working right now.
I'm using Pico Opengapps 4.4.4, M-Kernel a69. zip, TWRP 2.8.7.0
In recovery the prosess looks OK, ends with 'DONE... pls reboot', but when thy system loads, I still have stock slim kernel.
Any advice, what I'm doing wrong?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
589Page 1: Information
Page 2: Changelog and Downloads
Page 3: Additional info and FAQ
Instructions:
Make sure you are on the latest bootloader version before flashing this or any other custom kernel. Search for a flashable zip or use fastboot and the google factory images.
Download Kernel to internal SD card. Flash in recovery. Reboot. Congratulate yourself for wisely installing the best nexus 7 kernel.
A complete list of changes is available at my Github.
Source: https://github.com/Metallice/android_kernel_grouper
Recommended Settings:
The only app supported for changing any kernel parameters and settings is TricksterMod - https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
CPU governor - TouchDemand with default parameters (default)
I/O Scheduler -
- ROW for pure read speed. Fast reads which are often the most important on mobile. Similar concerns like deadline.
- BFQ for more consistent performance. Slower than Deadline and ROW, but prevents stutters while downloading in background
Max Frequency - 1.2Ghz (Stock max for 2+ cores) (for lollipop it might be a good idea to use 1.3Ghz)
- Note: Tegra sets the max frequency to 1.5Ghz at boot, make sure to change it manually or have an app set it at boot to avoid battery loss. If you have a program such as
TricksterMod set it at boot make sure to include at least a 60 second "delay" in applying boot settings.
- Note 2: DO NOT USE THE APP "SYSTEM TUNER" TO SET FREQUENCIES. CONFLICTS WITH AUDIO PERFLOCK IN KERNEL. Do NOT use system tuner to set frequencies as it conflicts with audio performance lock in this kernel. Will prevent you from lowering your maximum frequency. Use Trickstermod.
GPU Max Freq - 446Mhz (maintains good battery life while smoothing out some games. Anything greater than 446Mhz is so heavily bottlenecked by RAM that it's essentially worthless. 600Mhz might give you 1 or 2 extra FPS for significantly worse heat, battery life, and stability)
- Possible frequencies - To be completed later
Fsync - On
Dynamic Fsync - On (be aware of data loss concerns, even if they actually are minimal.)
SmartDimmer/PRISM - On (off for a63 and lower)
zRAM - off/none (default) (For lollipop it may help with multitasking at the price of speed, although you really shouldn't be trying to heavily multitasking with a 2012 N7 anyway) (Not very useful on android 4.x with >=1GB RAM, for lollipop it's not really helpful >=3Gb)
Data remounting scripts - already included in ramdisk. Additional scripts not needed.
I DO NOT RECOMMEND, nor will I support, any kind of optimization/superdupercharge/placebo script. All settings are already optimized in kernel and ramdisk. Using these scripts or tweaks will only lead to problems and performance degradation.
__________________________________________
If you'd like to buy me some caffeine so I can continue to fit studying and kernel-ing in my busy schedule, feel free to donate below. Thanks so much for all of your support! Clicking the thanks button is always appreciated too
220Alpha Changelog (stable feature list above):
a77 - remove CM12.1 specific stuff from ramdisk
a76 - Fix for 5.1
a75 - 5.1 Lollipop update and patches
Click to show complete changelog
__________________________________________________
Downloads:
Alphas 5.1 -
- a76 (CM12.1) - https://www.androidfilehost.com/?fid=23991606952601166
Click to show downloads for older versions of Android
131THIS POST/GLOSSARY NO LONGER UPDATED DUE TO TIME CONSTRAINTS
Glossary of terms:
(that one may not be as familiar with as things like CPU and GPU)
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. Faux123 and everyone refers to value as our "variant." 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?38Okay I know you guys must be antsy for some LP so here's an update.
A pre a70 kernel is built. Nothing changed except for merging in the LP kernel/ramdisk changes. I'll be able to test later tonight. Once I can get it booting I can work on adding and testing other changes/updates before a70 is good to go.
New posts
-
Development [ROM][13][OFFICIAL] PixelOS [AOSP][STABLE][10/05/2023]
- Latest: fromsunsetodawn
-
