Kernel Settings Reference

From Boeffla WIKI
Jump to: navigation, search

Boeffla-Kernel Settings reference



Important note: This documentation is currently work-in progress and it does NOT yet include everything for the OnePlus phones and the Galaxy S5.


Boeffla-Kernel configuration is spread across multipe tabs in Boeffla-Config:

  • Overview
  • Governor/IO
  • CPU (multiple tabs when multiple cpu clusters)
  • GPU
  • Boeffla-Sound
  • Display+LED
  • Miscellaneous 1
  • Miscellaneous 2
  • Profile Script

Please note, not all configuration options in all tabs are always available. This depends on the capabilities of the installed Boeffla-Kernel and the Boeffla-Config version.


Contents

Tab: Overview

The overview tab mainly shows lots of information of your system, like kernel, rom, modem, bootloader versions etc. Also memory and zRam utilisation (kernel view - this does not neccessarily need to correlate with what you see in other apps!) can be seen here.

Checkbox UMS Mode

Applies to: S3, S5, OPX

Make external phone SD card available as drive on an USB-connected PC. With Android 4.x versions, Google decided to only use the MTP (media transfer protocol) for communication when you connect your device to a PC. This prevents the memory to show up as a drive but only as a device. Checking this checkbox will mount the external sd memory as drive again as long as the function is active. Note: Make sure you do not modify files on the phone at the same time as this can lead to inconsistencies.

Checkbox Doze active

Checkbox SeLinux strict

Tab: Governor / IO

On this tab, you can configure options around governors and IO related things like IO schedulers and memory transfer.

Governor

Multiple sections for governor are possible when device has multiple CPU clusters.

Governor

Applies to: all devices

Expected impact: Differences in performance and battery life

A governor defines the "strategy" how to scale CPU cores up and down across frequencies, based on system load. For general information on governors, follow this LINK. There is nothing such like a "best" governor, this pretty much depends on your personal preferences. Yyou need to test for yourself.

Governor profile

Applies to: all devices

Expected impact: Differences in smoothness and battery savings

A governor profile tweaks the selected governor by changing the governors parameters (tunables). This allows to achieve governors behaving different, based on specific needs you might have (higher performance, better battery life etc.).

Scheduler

Scheduler

Applies to: all devices

Expected impact: Differences in smoothness and potentially battery savings

The I/O scheduler defines the "strategy" for read and write access to your internal and external sd card memory. For further information on scheduler internals, follow this LINK. There is nothing such like a "best" scheduler, you need to test for yourself. Row seems to be favourite for many users though.

Readahead buffer

Readahead buffer

Applies to: all devices

Expected impact: Better performance in accessing your sd card memory

The read ahead buffer defines how much memory is reserved as a cache by Android when reading data from the SD memory. Please note, a higher buffer value is not always good as the ideal buffer size depends a lot on the quality of your SD memory card (and also on your internal SD memory quality). So the only way to find out what your perfect size is, is to test read speed with existing apps and also ensuring there are no side effects (like stuttering when playing mp3 files) for you.

File system tweaks

Ext4 tweaks

Applies to: all devices

Expected impact: Potential battery savings and improved smoothness by less (or better bundled) write access to your sd card memory.

This tweak remounts /data and /cache directories with a commit time of 20 seconds (stock is without commit time).

Dynamic FileSync

Tab: CPU

The CPU tab allows you to configure all kernel settings affecting the phones main processor unit.

CPU frequencies

CPU Max frequency

Applies to: all devices

Expected impact: Battery savings when underclocking, better performance when overclocking

By this setting you can limit the upper frequency the CPU cores should use in order to save battery. At the same time, you can activate slight overclocking for some devices if you wish (S3, S5, OPO, OPX, OP2, OP3) Please note, it is not guaranteed your phone runs stable with overclocking!

CPU Min frequency

Applies to: all devices

Expected impact: Potentially better short-term performance, worse battery life

By this setting you can limit the lower frequency the CPU cores should use in order to avoid the frequency dropping down too much. This avoids the CPU clocking up stepwise from a low frequency when more performance is needed, so the phone might be a bit quicker up to the desired CPU frequency.

Hotplug settings

Hotplug profile

CPU tweaks

CPU idle mode

Applies to: S3, S5

Expected impact: Potentially better battery life

Between screen off and deep sleep states, there are some idle modes supported by cpuidle driver. They are IDLE aka Normal Idle, LPA aka Deep Idle and AFTR aka ARM Off Top Running. In IDLE state, CPU is not clocked anymore, but no hardware is powered down. In deep idle (LPA), a state after IDLE, again, the cpu is not clocked anymore like we guessed but some parts of hardware are powered down. Deep idle brings in real power savings and there is no need of putting a hard limit to frequency during screen-off; using a screen-off profile. ATFR is the cpu idle status that saves most battery and runs fine on the Exynos hardware.</div>

CPU multicore power saving

Applies to: S3, S5

Expected impact: Potentially better battery life

Multicore power saving aims to schedule tasks between multiple cores in the CPU. It can be:

  • Off
  • On - power-save balance by loading first core until it's 100% loaded
  • Aggressive - load balance the CPU cores by keeping the load even between them

Hotplugging does load balancing already by taking care of thresholds, run queues, process priorities, cut-off frequency, etc. So there's no use of setting this to On only. You can however try the Aggressive setting.

Note: If you are using the zzmoove governor, it is recommended to not use this option and keep it on Off.

CPU voltages

Applies to: S3, S5, OPO, OPX

Expected impact: Maybe cooler phone, maybe slightly better battery performance (but not worth the risk of instabilities)

This allows undervolting of your CPU core voltages per frequency. Be careful as too much undervolting will lead to instable systems and random reboots (it will not put any damange to your phones hardware though).

All phones are different due to manufacturing tolerances, so some phones support more undervolting, some less. There is nothing you can do about it than test yourself! Either use the sliders to set the voltage per frequency yourself, or use one of the predefined voltage profiles.


Tab: GPU

The GPU tab allows you to configure all kernel settings affecting the phones graphical processor unit.

GPU frequencies

GPU governor

GPU Max frequency

GPU Min frequency

GPU boost

Freq profile / frequency sliders

Applies to: S3

Expected impact: Battery savings when underclocking, better performance - especially for gaming - when overclocking.

By this setting you can change the clocking speeds for the GPU (graphics processing unit) in your device - so you can do both overclocking or underclocking.

Be careful as phones are different and overclocking GPU can also lead to stability issues and/or graphical artifacts on the screen (it should not put any damange to your phones hardware though).

Please note, if you decide to go for overclocking, you should consider also some slight overvolting of the GPU for more stability. Either use the sliders to set the frequencies of each individual step yourself, or use one of the predefined frequency profiles.

GPU voltages

Volt profile / voltage sliders

Applies to: S3

Expected impact: Maybe cooler phone, maybe slightly better battery performance when undervolting. More stability with overvolting if you also overclock your GPU.

This allows undervolting and overvolting of your GPU (graphics processor) core voltages.

Be careful as too much undervolting will lead to instable systems or artifacts on screen (it will not put any damage to your phones hardware though).

All phones are different due to manufacturing tolerances, so some phones support more undervolting, some less. There is nothing you can do about it than test yourself! Either use the sliders to set the voltage per frequency setp yourself, or use one of the predefined voltage profiles.


Tab: Boeffla-Sound

On this tab you can control all aspects of the Boeffla-Sound audio engine, which allows you to make more usage of the power of the built-in audio hub. The Boeffla-Sound engine controls the audio hub on hardware register level, so it does not rely on any software solutions, which means it does not consume any more battery or causing other interferences.

Boeffla-Sound status

Applies to: all devices

Expected impact: Enable or disable Boeffla-Sound engine

This is the master switch for the Boeffla-Sound engine. As long as it is switched to off, it does absolutely not hook into any of the audio handling. In case you have any weird, unexplainable issues, switching it to off would return back to stock audio completely.

Volumes

Headphone volumes

Applies to: all devices

Expected impact: Increase/decrease of hardware headphone volume

You can configure the headphone volume by this setting, in fact you can make the headphone louder than the standard settings. Note: This does NOT affect - as all other Boeffla-Sound options as well - any Bluetooth devices connected to your phone! Bluetooth is a purely digital signal path, which is not influenced by the phones audio hub for analo signals.

Speaker volumes

Applies to: S3, S5, OPO, OPX, OP2, OP3, OP5

Expected impact: Increase/decrease of hardware speaker volume

You can configure the speaker volume by this setting, in fact you can make the speaker louder (or in some kernels only quieter) than the standard Samsung settings.

Equalizer

Applies to: S3

Expected impact: Better sound quality when using analog headphones

This setting switches on the hardware headphone equalizer and allows you either to adjust the sliders for all frequency bands yourself, or load one of the predefined equalizer profiles. Best is to try out the presets and find your personal favourite. If you have enabled the equalizer, the saturation prevention feature is automatically enabled as well. It will make sure, the equalizer settings do not end up in saturating the headphone amplifier and causing bad distortion to the signal (which sounds really ugly). At the same time, due to the compression, the volume of the signal is slightly reduced. If you do not like that and want to have full control over saturation yourself, switch this option off.

Microphone gains

General mic level

Applies to: S3

Expected impact: You can control microphone sensitivity for general purposes

This setting allows you to control the microphones sensitivity for all general purposes (recording etc.) apart from calls.

Call mic level

Applies to: S3, OP5

Expected impact: You can control microphone sensitivity for phone call purposes.

This setting allows you to control the microphones sensitivity for phone calls.

Miscellaneous

Speaker tuning

Applies to: S3

Expected impact: Better sound quality when playing media via phone speaker

By this option you can enable the speaker tuning feature, which improves sound quality when you play media via the phone speaker by changing some internal equalizer settings.

Privacy mode

Applies to: S3

Expected impact: Speaker will not play any notification sounds while headphones are connected

This setting causes the speaker to be completely muted for notification sounds, phone ring signals etc. as long as a headphone is plugged in. This avoids people looking at you when you are wearing headphones and receive a notification, which is by standard played via both speaker and headphones. Now, nobody will notice anymore when you get alerts while wearing headphones

DAC direct

Applies to: S3

Expected impact: Better sound quality when using headphones, potentially some minor battery savings

By switching DAC direct to on, you will bypass the output mixer in the signal path and connect the DAC directly to the headphone amplifier.

DAC oversampling

Applies to: S3

Expected impact: Better sound quality when using headphones, potentially some minor additional battery drain

This setting changes the oversampling rate from 64 to 128 bit.

FLL tuning

Applies to: S3

Expected impact: Better sound quality when using headphones

This setting changes the FLL configuration of the audio hub.

Mono downmix

Applies to: S3

Expected impact: Mono signal instead of stereo signal in headphones

This setting changes internal signal handling to switch to mono output for headphones.

Stereo expansion effect

Applies to: S3

Expected impact: Add stereo 3D effect to headphone output

This setting activates a „kind of“ stereo 3D sound effect via the built in hardware DSP for headphones.


Tab: Display + LED

On the Display + LED tab, various different settings regarding display, touch screen and LEDs can be configured.

Notification LED

LED fading status

Applies to: all devices

Expected impact: LED blinking or fading effect

If this switch is set to off, the notification LED will blink as per standard. If you set it to on, it will softly fade in and out instead.

LED blink/fade speed

Applies to: all devices

Expected impact: Speed of LED blinking or fading

You can configure the speed of the notification LED blinking/fading in many levels (0 = steady light)

LED brightness

Applies to: all devices

Expected impact: Brightness of the notification LED

You can configure the brightness of the notification LED from completely off very bright. Note: Depending on the device, this behaviour is different. On OPX, OP2, OP3 and OP5 it only has effect on non-blinking notifications (i.e. battery status indicator)

Input boost

Input boost frequency

Input boost status

Input boost duration

Touch boost

Touch boost status

Applies to: all devices (some exceptions)

Expected impact: Potential battery savings if touch boost is switched off

This setting allows you to switch off touch boost functionality which is by default switched on. Touch boost (for some platforms called CPU boost) means, the CPU frequency is boosted to a higher level when the touch screen is being used. This increases smoothness of the user interface, but also consumes slightly more power. With good launchers, touchboost can be switched off without having negative impact.

Touch boost frequency

Applies to: all devices (some exceptions)

Expected impact: Potential battery savings if lower the touch boost frequency

Configure the frequency which will be boosted to when screen gets touched. Lower frequencies are better for battery life but impact smoothness.

Touch wake

Touch wake status

Applies to: S3

Expected impact: Touch-to-wake functionality master switch

Touch to wake is a feature with which you can reactivate the display after it gone black automatically due to a time out again. The touch screen will still react on touch events for a configurable time after the display went off. A quick touch will enable the display again. This is a very handy feature when you move your eyes away for a while and notice the display went black. Instead of pressing one of the hardware buttons, a quick touch does the job.If you configure to not directly lock the device after the display goes black, you are directly back to where you were before.Please note: This can cause minor additional battery consumption as the device will not go to deep sleep until the touch-to-wake time is over (see touch wake delay setting below).

Touch wake charger mode

Applies to: S3

Expected impact: Enable or disable charger mode

If this option is enabled, touch wake is active for an infinite time and not the configured touch wake delay time, as long as the device is connected to a charger or USB port.Please note, this option is only available when the touch wake master switch is set to on.

Touch wake delay

Applies to: S3

Expected impact: Device will react during this time on touch events after screen went off already

This is the time, the touch screen will still react on touch events after the display went off already. Note: 0 is a special case called infinity mode = touch screen will react forever, but be aware of battery drain as your device will not enter deep sleep again!!

Gestures

Swipe dock R-L to sleep

Swipe dock L-R to sleep

Swipe screen gesture to sleep

Early suspend

Early suspend delay

Applies to: S3

Expected impact: Enable screen off animations

Early suspend is a mechanism that Android introduced into Linux kernel. This state is beween really suspend, and turn off screen. After screen is off, several device such as LCD backlight, gsensor, touchscreen will stop for battery life and functional requirement. Having an early suspend time of 0 ms, CRT-Off animations will have no time anymore to display. By increasing this time this will be enabled again. 100 ms is the Boeffla-Kernel standard value and should fit almost all needs.

Color control

Color control active

Red / Green / Blue

Saturation

Hue

Display value

Contrast

MDNIE settings

Sharpness tweak

Applies to: S3

Expected impact: Change readability of text by softening it

This setting changes some MDNIE settings in order to increase readability for letters and reduce oversharpness of Samsung stock configuration. This tweak has been invented by Hardcore in his well-known Speedmod kernel already during Galaxy S1 times.

MDNIE overwrite

Applies to: S3

Expected impact: This will overwrite the MDNIE settings of the Rom

If you want to use Boeffla-Config to overwrite MDNIE mode, scenario, outdoor mode and negative mode, set this switch to On. MDNIE stands for "Mobile Digital Natural Image Engine" and is basically a layer of the display driver. It takes care about brightness, sharpness, contrast etc. - so basically all aspects of the display. There are some parameters to configure the MDNIE (various modes, predefined scenarios, outdoor mode and negative mode for instance), which is typically controlled by settings in the Rom. However, Cyanogenmod team obviously decided to drop these configuration in the settings pages in some of their 10.2 roms, so it has been added in the Boeffla-Config app again. Whilst the MDNIE configuration via the Boeffla-Config app works fine on CM10.2 roms, you should not use it on CM10.1 as the settings are still available in the CM10.1 roms and the roms will overwrite themselves again. In theory it works also on Samsung firmwares, but also here the settings are still available in the rom to be configured.

MDNIE mode

Applies to: S3

Expected impact: Change display colours

This option is primarily meant for roms that do not support MDNIE configuration in their settings. Setting this option allows you to select from a few predefined MDNIE modes via their values between 0 and 9. Depending on kernel, rom and platform, different values are being supported and also their meaning is different. Note: Changing the mode in some roms only works after you changed the MDNIE scenario to specific values (see next point).

MDNIE scenario

Applies to: S3

Expected impact: Change display colours

Setting this option allows you to select from a few predefined MDNIE scenarios via their values between 0 and 9. Depending on kernel, rom and platform, different values are being supported and also their meaning is different. Best is to try all of them and choose the one that creates the perfect display experience for you in terms of colours and contrast.

MDNIE outdoor mode

Applies to: S3

Expected impact: Increase brightness and contrast

Setting this option to On enables the so called "outdoor mode" which increases brightness and contrast of your display in order to make it better readable in outdoor situations. Note: This mode is also implemented with a glitch in the standard MDNIE driver. As soon as you toggle the MDNIE negative mode once, it sometimes behaves weird when switching the outdoor mode as it then also by fault influences the negative mode internally. Just be aware of this.

MDNIE negative mode

Applies to: S3

Expected impact: Display negative colours

Switching this option to on will revert all colours of your display and show everything with negative colours. So, white will become black and vice versa. All colour values actually change. This can be sometimes useful if you have an app that can only work with white background and you would prefer a black background to save battery (AMOLED displays use more battery when they display white or bright dots!).

Touch key LED settings

Touch LED full disable

Touch LED when screen touch

Touch LED timeout

Touch LED controlled by kernel (for CM)

Applies to: S3

Expected impact: Define if kernel or rom should control Touch LEDs

Up until mid of September 2013, there was the rule the kernel controls the Soft key touch LEDs (backlight) on the devices. However, the CM team changed this philosophy with their latest CM10.2 roms in a way, not the kernel but the rom controls the touch LEDs in future. This leads to all possible kind of issues when you use a improper combination of old/new kernel with older/newer CM rom. In order to avoid it, this switch lets you define who should be in charge of controlling the LEDs:

  • Off = Rom controls the LEDs, to be used with newer CM10.2 roms
  • On = Kernel controls the LEDs, to be used with oder CM10.2 roms

If you are unsure, just try both options and find out which one works for you.

Touch LED when touch screen (for CM)

Applies to: S3

Expected impact: Touch LED triggered (or not) by touching the screen

Default CM behaviour is to switch on the Touch LEDs once you touch the screen. If you do not like this, you can switch this off with this option. Then the touch LEDs will only be activated if you touch them directly. Note: This only works properly if the kernel is in control of the touch LEDs (see option "Touch LED controlled by kernel" above).

Display backlight

Minimum brightness

Maximum brightness

Backlight dimmer

Miscellaneous

Hardware buttons off during touch

Tab: Miscellaneous 1

On the miscallaneous tab, various different settings and tweaks for many different areas can be configured.

Charge rates

Charge rate AC

Applies to: S3, S5, OPO, OPX

Expected impact: Battery loading time will be reduced or prologned

This configures the charging rate when you load your phone via an AC charger. Increasing the default rate will usually not cause any harm to your charger. Also due to manufacturing tolerances no damage for your battery is expected when it loads faster. Please refer also to point "Ignore unstable power" below for further important information!

Charge rate USB

Applies to: S3, S5, OPO, OPX

Expected impact: Battery loading time will be reduced or prolonged

This configures the charging rate when you load your phone via USB. On some phones, a speciality is if you configure this value to zero: Then you can connect a PC to your device via USB without charging the battery. This could be good for battery life as you can follow your normal loading cycles without impact. However, on a number of PCs it causes the device not being recognized anymore. So you have to try yourself. Please refer also to point "Ignore unstable power" below for further important information!

Charge rate wireless

Applies to: S3, S5, OPO, OPX

Expected impact: Battery loading time will be reduced or prolonged

This configures the charging rate when you load your phone via a wireless charging cover. Please refer also to point "Ignore unstable power" below for further important information!

Ignore unstable power

Applies to: S3

Expected impact: Faster loading workaround for faulty charger devices

There are many faulty S3 chargers around, that are not able to provide a stable charging current to the device. A prominent example is for instance the Samsung stock charger delivered with the Galaxy S3. In the Galaxy S3, the charging logic recognizes unstable power and reduces the charging current in 100 mA steps until it detects the power to become stable. Then it deducts another 100 mA as a safety margin to be in a controlled situation (also see below the "ignore safety margin feature") This causes sometimes extremely long loading times as in fact the load cycle is performed with only 400 or 500 mA. This switch disables this logic on your own risk. So even if the charger cannot supply a stable power, the charging logic will not reduce the current back. This setting might damage your charger long-term, but for the majority of the users it just fixes the problem. Use at your own risk !!!

Ignore safety margin

Applies to: S3

Expected impact: Faster loading workaround for faulty charger devices

See explanation above about the instable power setting. By switching this option to on, the further deduction of 100 mA after detecting a stable charging power will not be done. This should not cause any damage to a healthy charger, but again please use at your own risk only !!!

Swappiness

Swappiness overwrite

Applies to: all devices

Expected impact: Control how zRam is used - memory handling / smoothness

Linux swappiness is the rate at which a Linux kernel moves pages into and out of active memory. In our case, zRam uses swap partitions in a compressed memory area. So the swappiness parameter determines how aggressively zRam will be used by the system. 60 (or 120 for vnswap) is the stock kernel setting without any swap. By enabling this switch you can overwrite with your own rate.

Android Low Memory Killer

Android Low Memory Killer settings

Applies to: all devices

Expected impact: Changing internal memory handling of Android OS

The Android Low Memory Killer is an extremely complex topic to understand. For those that want to learn more about it, please follow this LINK.In short, it is clearly an expert configuration function which lets you configure at which point Android removes a process out of the memory when total memory is getting low. Processes are classified into 5 different groups for this purpose, and based on the individual group, different memory thresholds values are taken into consideration. The memory thresholds can be configured for each of the 5 different groups:

  • Active process
  • Visible process
  • Started system service
  • Background process
  • Empty process

Please do not mess around with this values if you do not know exactly what you do. It can cause weird effects and in this case, you should return to stock values.

System tweaks

System tweaks

Applies to: all devices

System tweaks behave differently for every device, as it is something very device specific. I.e. on most devices it tunes the settings of the Android VM (Dalvik or Art) to perform a bit different. On other phones it influences the thermal profile used by the system.

zRam / vnSwap

zram Status / vnswap Status

Applies to: some kernels for some devices

Expected impact: Improve multitasking by adding virtual zRam memory

zRam is a concept to tackle the limited internal memory (like 1GB only in the Galaxy S3 I9300) by compressing parts of it. Technically, zRam is an area in the devices memory that is defined to be compressed. This memory area will be used to create a swap device in it. In the end, this adds to your overall memory and with average compression rates of around 35%, can help significantly to overcome the limits. Note: This has nothing to do with usual swap where the swap device is located on storage! So it does not put any wear on your storage, means, it will NOT be dangerous for your device at all! By switching this option to on, one or multiple zRam devices will be created with the configured total size (see below) and activated. zRam is fully dynamic, this means not used parts of the zRam do not consume any physical memory.

Number of zRam devices

Applies to: some kernels for some devices

Expected impact: Multipe zRam devices can improve overall zRam performance (unproven)

Original zRam implementations always used one single zRam device, however it seems spreading this to a number of zRam devices improves the overall performance as multiple CPU cores can balance this work out when they are anyway activated. This becomes especially apparent when you are using heavy games that require lots of memory, as during games all CPU cores are assumed to be active anyways. For normal daily usage, a single zRam device might be perfectly fitting your needs, however there is nothing wrong to have multiple devices always. For gaming persons, multiple devices are reported to help. Note: You can only change this setting if you switched zRam to Off before.

zRam total disk size / vnswap total disk size

Applies to: some kernels for some devices

Expected impact: Define total size of zRam used

This value defines how many MB of physical ram should be reserved to be used for zRam. zRam is fully dynamic, this means not used parts of the zRam do not consume any physical memory. This size is the total size for zRam, so if you configured multiple zRam devices, this total size is automatically be divided by the number of devices and activated accordingly. Example: you configured to use 4 zRam devices and set the total size to 600 - this will result automatically in 4 zRam devices with 150 MB each. Note: You can only change this setting if you switched zRam to Off before.</div>

Tab: Miscellaneous 1

TCP settings

TCP congestion

Modules

CIFS module

Applies to: all devices

Expected impact: You can access windows share drives in your local network

By switching this to on, the kernel will load the required cifs.ko module to support access to Windows network shares (SMB protocol) from the device. You can then simply use apps like „CIFS Manager“ to access your network drives. Note: This is different to how many file manager access CIFS/SMB shares! The file managers have their own implementation which is significantly slower than this native implementation in the kernel.

NFS module

Applies to: all devices

Expected impact: You can access Unix/Linux share drives in your local network

By switching this to on, the kernel will load the required NFS modules to support access to Unix/Linux network shares from the device. You can then mount your NFS share into your local file system by e.g. using a mount command in a terminal session.

XBox module

Applies to: all devices

Expected impact: You can use a wired XBox controller to play games on your device

By switching this to on, the kernel will load the required XPAD module to support a wired XBox controller pad which is connected via micro USB to the device.

Axis module

Applies to: all devices

Expected impact: You can use wired Ethernet by using a specific USB OTG network adapter

By switching this to on, the kernel will load the required Axis module to enable a wired USB Ethernet adapter, which is supported by Axis driver. Note however, due to many limitations in Android for wired networks, DNS resolution does not always work. So best is to use the wired connection primarily for accessing your local LAN only.

exFat module

Applies to: some kernels for some devices

Expected impact: Saving some memory which is wasted when you do not need exFat support

If you are not using an exFat formatted sd storage in your device (e.g. external SD Card which is formatted with exFat), you can prevent the proprietary exFat drivers from being loaded. Please bear in mind, you may not be able to access exFat formatted storage devices anymore unless you switch the exFat support on again. Nowadays many roms use FUSE drivers to access exFat, which does not require this driver anymore but is also significantly less performant.

Ntfs module

Applies to: all devices

Expected impact: You can access storage devices formatted in the Windows-defacto Standard NTFS

By switching this to on, the kernel will load the required ntfs.ko module to support access to NTFS formatted storage media on the device. As Android does not natively support it, you still need an app that mounts the device once plugged in, Chainfires Stickmount app from Google playstore is one example.

Entropy settings

Threshold read

Threshold write

Logging

Android logger

Applies to: some kernels for some devices

Expected impact: By keeping the logger off, less write access to the sd cards and potential battery savings

This setting lets you enable the Android Logger again, which tools like aLogCat and some security tools need. Also this is an important tool for developers for debugging and bug fixing.

Kernel logger

Applies to: some kernels for some devices

Expected impact: By keeping the logger off, less write access to the sd cards and potential battery savings

This setting lets you enable the Linux Kernel Logger (printk) again. This is an important log for developers for debugging and bug fixing of kernel related issues. Also this is required to produce the file /proc/last_kmesg which is required to analyze crashes and reboots afterwards.


Tab: Profile script