[Nexus 7 (2013) Original Android Development] flar2:
[youtube]WH_amyDmJVk[/youtube]

NOTES:

ElementalX Configuration File

Your choices in the Aroma installer are used to build a configuration file. The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)

If settings are not sticking:

[*]Make sure the file permissions for /etc/init.d/99elementalx are set to execute.

[*]Check to see if any /etc/init.d scripts or apps (such as Kernel Tuner or TricksterMod) are interfering with your settings.

ElementalX Log File

Every boot, a log file is created at /data/local/tmp/elementalx-kernel.log. This file shows the date and time and all settings that have been applied. Use this to verify and troubleshoot configuration options.

ElementalX Governor

The ElementalX CPU governor has been specifically designed and tuned to get the best balance between battery life and performance. By default, it is more conservative than Ondemand. During routine usage, the CPU frequency does not ramp up very often. If gboost is enabled, during gaming or any other graphics intensive situation, the CPU frequencies boost much easier in order to maintain maximum performance. Disabling gboost can increase battery life, but there may be a loss of performance, especially during gaming.

Faux Clock/TricksterMod/Kernel Tuner/etc

You don't need these apps because the ElementalX installer sets everything up automatically, but if you want to check or change settings, you can use these apps. Just be aware that some of them (e.g. Kernel Tuner) are set by default to apply settings on boot, which can interfere with the settings you chose in the ElementalX installer.

Overclocking

Overclocking (or underclocking) is optional. The installer lets you choose the maximum frequency. You can set the maximum frequency individually for each CPU core in the installer. Whatever frequencies you chose in the installer will be set at boot for each CPU. Not all devices can handle overclocking. The stock maximum CPU frequency is 1512MHz. I recommend a mild overclock, like 1728MHz for daily use. Clocking higher creates heat and wastes battery for very little performance gain.

CPU voltages

The installer allows you to choose from several undervolting options. These automatically undervolt the lowest frequency (384MHz) where the CPU spends most of its time. The voltages for other frequencies are assigned based on the PVS bin of your phone. CPU voltages are fully customisable with apps such Kernel Tuner or Trickster Mod, but I recommend leaving these other voltages as-is unless you are prepared to do a lot of testing. Be careful, lowering voltages can cause instability. Generally, having reboots while the phone is asleep or other weird problems is a sign that your minimum voltage is too low. The minimum voltage allowed is 700mV.

GPU Governor

The default GPU govenror is ondemand. It works well and is recommended for best balance between performance and batter life. The simple governor is also available, but ramps up the GPU frequency much quicker than ondemand, so may impact battery life. The governor can be set in /etc/elementalx.conf

fsync

fsync can be disabled if you're looking for the last ounce of performance. I recommend leaving it enabled as there is a slight risk of data loss if your phone shuts off unexpectedly before filesystems are synced.

Max screen off frequency

The default max screen off frequency is 1026MHz, which is a good balance between limiting the voltage/frequency and the time required to complete tasks while the screen is off. This can be changed manually at /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq

Installing a new ROM

If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.

NTFS and exFAT support

This is for anyone who wants to use OTG to connect a USB stick or portable harddrive formatted with Microsoft's NTFS or exFAT filesystems. You will need Stickmount or a similar app.

GPU overclocking

There are two modes: stock and overclocking. If you pick stock GPU freq (400MHz) you won't be able to overclock. Conversely, if you pick one of the overclocking frequencies, you won't be able to use the stock 400MHz frequency. You have to reflash if you want to change this.

These are the frequencies I've added: 450, 477, 490.5, 504, 531, 558, and 585

If you're in overclock mode, you change these on the fly with TricksterMod. I don't recommend 558+ for daily use. Too hot and probably unstable for most.

USB host mode charging

I've added a hack to allow usb host mode charging. Since not that many people are going to be using this, it needs to be enabled manually. This will allow you to charge the tablet while a USB peripheral is hooked up to the OTG cable.

To use it, change /sys/module/msm_otg/parameters/usbhost_charge_mode to 1.

You need a Y-cable and OTG adapter. This will be handy for people who use their tablet in the car and need to keep it charged.

First connect the Y-cable to your OTG adapter and a power source, then attach a USB peripheral. Finally, plug the OTG adapter into the tablet. Both the tablet and the peripheral will be powered by the Y-cable, allowing the tablet to charge

Wake Gestures

This is a new feature similar to the Motion Launch Gestures on the HTC One m8. Requires the following Xposed module:

Wake Gestures: elementalx.org/wake-gestures

Set /sys/android_touch/wake_gestures to 1 to enable input events for wake gesture actions. Set to 0 to use traditional sweep2wake or doubletap2wake (wakes up the phone and turns on the screen only).

Note that if you enable wake_gestures, nothing will happen if you don't install the Wake Gestures Xposed module.

Sweep2wake

Sweep2wake allows you to turn on your phone by swiping your finger across the screen. There are four sweep actions that will work

Gesture........Value

Sweep right......1

Sweep left........2

Sweep up.........4

Sweep down....8

Add up the values for each gesture you want to enable and put the total in /sys/android_touch/sweep2wake. For example, to enable all gestures, the value is 15 (1+2+4+8). To enable sweep right, sweep left and sweep up, the value is 7 (1+2+4)

/sys/android_touch/sweep2wake

Shortsweep

Enabling this makes sweep2wake work with a shorter sweep distance. You can edit /etc/elementalx.conf to change the setting on boot.

/sys/android_touch/shortsweep

0 = disabled

1 = enabled

Doubletap2wake

DoubleTap2Wake (DT2W) allows you to wake the device by double tapping anywhere on the screen. You can edit /etc/elementalx.conf to change the setting on boot.

Still needs some tweaking!

/sys/android_touch/doubletap2wake

0 = disabled

1 = enabled

S2W/DT2W power key toggle

If enabled, turning the screen off with the power button disables s2w and dt2w to save battery (since s2w/dt2w cause significant battery drain). When you turn the screen back on, s2w and dt2w return to their previous settings. If the screen times out, s2w/dt2w are not disabled this is only if you use the power button to turn it off. You can edit /etc/elementalx.conf to change the setting on boot.

Enable/disable Magnetic on/off

This setting allows you to enable or disable the magnetic on/off switch used by some cases. You can edit /etc/elementalx.conf to change the setting on boot.

/sys/module/lid/parameters/enable_lid

0 = disabled

1 = enabled