Boeffla-Config Settings
Boeffla-Config
note: This documentation is currently outdated and does NOT include anything in my OnePlus One and Galaxy S5 kernels!!!
So you will find much
more in the latest kernels than in the documentation!!! I will rework when I find
some time.
Boeffla-Kernel configuration is spread across multipe tabs in Boeffla-Config:
Please note, not all configuration options in all tabs are always
available. This depends on the capabilities of the installed
Boeffla-Kernel version.
1. 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.
1.1 UMS Mode
Default: Off
Expected impact: 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
This prevents the memory to show up as a drive but only as a device.
By toggeling this checkbox, the external SD card gets unmounted
internally (not accessible from the phone anymore) and the protocol is
switched from MTP to UMS (usb mass storage) to make it appear as a
normal USB drive on your PC. This simplifies data transfer a lot.
Please do not forget to untick this again after you finished using the
connection, so it gets mounted and visible on your Android device again.
Note: When this does not properly work, it is most likely an issue with USB drivers installed on your PC.
2. Tab: Governor / IO
On this tab, you can configure options around governors and IO related things like IO schedulers and memory transfer.
2.1 Governor
Default: pegasusq
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 .
There is nothing such like a "best" governor, this pretty much depends
on your personal preferences. you need to test for yourself.
PegasusQ is a very solid standard governor
Lulzactiveq is more focussed on performance
zzmoove on battery savings, but also has a performance mode - it
is derived from the conservative governor and modified to be able to
support multiple CPU cores (hot plugging), more in own thead on XDA
developers:
PegasusQPlus
is a heavily tweaked PegasusQ governor, which has been implemented by
AndreiLux in his Perseus kernel. PegasusQPlus should have a better
balance between performance and battery usage. As the change list would
be too long for this help, please read in his thread.
Intelliactive is focussed on performance, achieving that by avoiding hot-plugging most of the time
2.2 Governor profile
Default: standard
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.).
The following governor profiles are available typically:
PegasusQ profiles:
standard: this is the governors standard stock configuration as it comes out of the box
tunable: this allows you to set each and every parameter of the governor as you like it (for experts, donation app only)
boeffla moderate: this is pegasusq tweaked to most of the time run on two CPU cores only
boeffla battery saving: this is pegasusq tweaked to most of the time run on one CPU core only
boeffla 1 core: this is pegasusq but limits to one CPU core in any case
boeffla 2 cores: this is pegasusq but limits to two CPU cores maximum in any case
speedmod: this is pegasusq with the governor tweaks hardcore uses in his speedmod kernel
zzmoove profiles:
standard: this is the governors standard stock configuration as it comes out of the box
tunable: this allows you to set each and every parameter of the governor as you like it (for experts, donation app only)
optimal: profile created by user ZaneZam to have a slightly tuned governor for nice performance and good battery life
battery:& profile created by user ZaneZam to have strong battery savings (expect some lags however)
battery yank: profile created by user Yank555 to have strong battery savings (less lags than profile before)
battery extreme yank: profile created by user Yank555 to have extreme battery savings
performance: profile created by user ZaneZam with focus on very good performance and less battery life
insane: profile created by user ZaneZam with focus on pure performance
All other governors do (not yet) have
any predefined profiles, however you can always tweak it yourself when
you choose the tunable mode.
2.3 Scheduler
Default: cfq
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 .
There is nothing such like a "best" scheduler, you need to test for yourself. Row seems to be favourite for many users though.
cfq: This loads the CFQ "completely fair scheduler", which is also standard in Samsung stock
deadline: This loads the "deadline" scheduler
noop: This loads the most simple "noop" scheduler
sio: This loads the simple I/O scheduler
row: This loads the "read over write" scheduler
bfq: This loads the "budget fair queuing" scheduler
zen: This is a scheduler based on VR scheduler with changes
2.4 Readahead buffer
Default: 256 kb
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.
The Boeffla-Kernel default of 256 kb (stock is 128 kb) is already a good going-in position for this buffer size.
2.5 Ext4 tweaks
Default: on
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).
3. Tab: CPU
The CPU tab allows you to configure all kernel settings affecting the phones main processor unit.
3.1 Maximal frequency
Default: 1400 MHz
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.
You can specify any frequency between 200 and 1400 MHz for the limit.
At the same time, you can activate slight overclocking up to 1600 Mhz
if you wish. Please note, it is not guaranteed your phone runs stable
with overclocking!
3.2 Minimal frequency
Default: 200 MHz
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.
3.2 CPU idle mode
Default: Idle + LPA
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- using a screen-off profile.
ATFR is the cpu idle status that saves most battery and runs fine on the Exynos hardware.
3.3 CPU multicore power saving
Default: Off
Expected impact: Potentially better battery life
Note: If you are using the zzmoove governor, it is recommended to not use this option and keep it on Off.
Multicore power saving aims to schedule tasks between multiple cores in the CPU. It can be
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
3.4 CPU voltages
Default: None
Expected impact: Cooler phone, maybe slightly better battery performance (but not worth the risk of instabilities)
This allows undervoltung 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
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:
None: this enables the voltage sliders for manual configuration
No undervolting: this resets the voltages back to stock voltages
undervolt -25mV: voltages for all frequencies are reduced by fix -25 mV
undervolt -50mV: voltages for all frequencies are reduced by fix -50 mV
undervolt -75mV: voltages for all frequencies are reduced by fix -75 mV
undervolt -100mV: voltages for all frequencies are reduced by fix -100 mV
undervolt light: voltages are reduced via a pattern throughout the frequencies, only light undervolting
undervolt medium: voltages are reduced via a pattern throughout the frequencies, medium undervolting
undervolt heavy: voltages are reduced via a pattern throughout the frequencies, heavy undervolting
For the latter 3 profiles, see resulting voltages per frequency yourself in the app.
4. Tab: GPU
The GPU tab allows you to configure all kernel settings affecting the phones graphical processor unit.
4.1 GPU frequencies
Default: None
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.
(on the Galaxy S3 I9300 by using the Taiji Free Basemark, I can climb
from standard 38 fps to around 49 fps by overclocking to 700 Mhz)
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 (by 25 or 50 mV) for more
stability.
Either use the sliders to set the frequencies of each individual step
(4 steps with Samsung kernels, 5 steps with CM kernels) yourself, or
use one of the predefined frequency profiles.
Profiles are not listed here as they differ pretty much between Samsung
and CM kernels due to the different number of frequency steps. Easiest
way to find out what every profile does is: Apply it and see how the
sliders and the values get adjusted.
4.1 GPU voltages
Default: None
Expected impact: 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 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 setp yourself, or use one of the predefined voltage profiles.
Profiles are not listed here as they differ pretty much between Samsung
and CM kernels due to the different number of frequency steps. Easiest
way to find out what every profile does is: Apply it and see how the
sliders and the values get adjusted.
5. 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 (Wolfson Micro WM1811 or WM8994). 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.
5.1 Boeffla-Sound status
Default: Off
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.
5.2 Headphone volumes
Default: 50
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 Samsung settings.
Note: This does NOT affect - as all other Boeffla-Sound options as well - any Bluetooth devices connected to your phone!
5.3 Speaker volumes
Default: 57
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 than the standard Samsung settings.
5.4 Equalizer
Default: Off
Expected impact: Better sound quality when using headphones
This setting switches on the hardware headphone equalizer and allows
you either to adjust the sliders for all 5 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.
5.5 Microphone gain general
Default: 28
Expected impact: You can control microphone sensitivity for recording purposes.
This setting allows you to control the microphones sensitivity for all general purposes (recording etc.) apart from calls.
This allows you e.g. to do nice video recordings with proper audio also
in very noisy envirnoments like concerts etc. You could use values
around 5 to 7 to accomodate this.
In short - a higher level means more sensitivity, a lower level reduced sensitivity.
5.6 Microphone gain call
Default: 25
Expected impact: You can control microphone sensitivity for phone call purposes.
This setting allows you to control the microphones sensitivity for
phone calls. Please note, the Boeffla-Sound engine comes with an
inbuilt call-detection which automatically switches from the general to
this call microphone level during calls.
In short - a higher level means more sensitivity, a lower level reduced sensitivity.
5.7 Speaker tuning
Default: Off
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.
5.8 Privacy mode
Default: Off
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.&
5.9 DAC direct
Default: Off
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.
5.10 DAC oversampling
Default: Off
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.
5.11 FLL tuning
Default: Off
Expected impact: Better sound quality when using headphones
This setting changes the FLL configuration of the Wolfson WM1811 or WM8994 audio hub.
5.12 Mono downmix
Default: Off
Expected impact: Mono signal instead of stereo signal in headphones
This setting changes internal signal handling to switch to mono output for headphones.
5.13 Stereo expansion effect
Default: Off
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.
6. Tab: Display + LED
On the Display + LED tab, various different settings regarding display, touch screen and LEDs can be configured.
6.1 LED fading status
Default: Off
Expected impact: LED blinking or fading effect
If this switch is set to off, the notification LED will blink as per
Samsung standard. If you set it to on, it will softly fade in and out
6.2 LED blink/fade speed
Default: 1
Expected impact: Speed of LED blinking or fading
You can configure the speed of the notification LED blinking/fading in 5 levels from 1 (slowest) to 5 (fastest).
6.3 LED brightness
Default: 40
Expected impact: Brightness of the notification LED
You can configure the brightness of the notification LED from 0 (completely off) to 130 (very bright).
6.4 Touch boost status
Default: On
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 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.
6.5 Touch boost frequency
Default: 800 Mhz
Expected impact: Potential battery savings if lower the touch boost frequency
The standard touch boost frequency is 800 MHz when the touch screen
gets touched. Please see "touch boost status" setting for more
explanation.
You can configure this frequency in the typical CPU steps from 200 MHz
MHz. Lower frequencies still give you a smoother user
experience but use slightly less battery. It is something in between
switching touch boost completely off or using the standard frequency.
Please note, this setting has of course only effect when the touch boost status is switched on (see above).
6.6 Touch wake status
Default: Off
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).
6.7 Touch wake charger mode
Default: Off
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.
6.8 Touch wake delay
Default: 45 sec
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. Even with the default of 45
seconds, additional battery consumption is rarely noticeable.
You can configure this time between 0 and 600 seconds.
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!!
6.9 Early suspend delay
Default: 100 ms
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, as with Samsung stock kernel,
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.
6.10 Sharpness tweak
Default: Off
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.
6.11 MDNIE overwrite
Default: Off
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
In theory it works also on Samsung firmwares, but also here the settings are still available in the rom to be configured.
6.12 MDNIE mode
Default: Standard
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.
Example for Samsung based kernel (can differ though):
0 = dynamic, 1 = standard, 2 = nature, 3 = movie, 4 = automatic
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.
Note: Changing the mode in some roms only works after you changed the
MDNIE scenario to specific values (see next point).
6.13 MDNIE scenario
Default: Standard
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,
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.
6.14 MDNIE outdoor mode
Default: Off
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.
6.15 MDNIE negative mode
Default: Off
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
6.16 Touch LED controlled by kernel (for CM)
Default: Off
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.
6.17 Touch LED when touch screen (for CM)
Default: On
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
Note: This only works properly if the kernel is in control of the touch
LEDs (see option "Touch LED controlled by kernel" above).
7. Tab: Miscellaneous
On the miscallaneous tab, various different settings and tweaks for many different areas can be configured.
7.1 System tweaks
Default: Off
Expected impact: Better performance, smoothness, battery life, improved memory handling
Boeffla-Kernel comes with a number of system tweak presets, which
should optimise the system for specific situations (like higher
performance, gaming etc.).
The following presets are available:
Off: No system tweaks in place, everything on stock configuration (I would recommend this)
Boeffla tweaks: this will load the Boeffla-Kernel system tweaks -
smoothness and performance (nowadays I would not recommend this anymore)
Speedmod tweaks: this will load the same tweaks as used in Hardcore's Speedmod kernel
Mattiadj tweaks: Tweak set mainly for settings of the Dalvik VM created by user Mattiadj, specifically for playing heavy games
Boeffla system tweaks were recommended
by me for a very long time, however Samsung did a quite good job in
improving both firmwares and kernels, so nowadays I recommend to not
use system tweaks anymore for daily usage.
Technical details about the various system tweaks and what they exactly do can be found here:
7.2 Charge rate AC
Default: 1100
Expected impact: Battery loading time will be reduced
This configures the charging rate when you load your phone via an AC
charger. Stock value is 1000 mA (Boeffla-Kernel default is 1100 mA),
when you set it to a higher value, the phone will load faster. This
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. And if so, don't care about it and buy a new one a bit
earlier, it is below 15 Dollars typically.
Please refer also to point "Ignore unstable power" below for further important information!
7.3 Charge rate USB
Default: 475
Expected impact: Battery loading time will be reduced
This configures the charging rate when you load your phone via USB.
Stock value is 475 mA, when you set it to a higher value, the phone
will load faster. This should not cause any harm to your USB device.
Note: Charging currents higher than 500 mA are only specified for USB3,
however experience shows many modern USB2 ports can also provide more
than 500 mA. So you will just gain loading speed by this.
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!
7.4 Charge rate wireless
Default: 475
Expected impact: Battery loading time will be reduced
This configures the charging rate when you load your phone via a wireless charging cover.
Stock value is 475 mA, when you set it to a higher value, the phone
will load faster.
Please refer also to point "Ignore unstable power" below for further important information!
7.5 Ignore unstable power
Default: Off
Expected impact: Faster loading workaround for faulty charger devices
There are many faulty 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 !!!
7.6 Ignore safety margin
Default: Off
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 !!!
7.7 zram Status
Default: Off
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
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.
Note: If you switch this option off again, it
can take up to several minutes to unload everything from zRam and put
it either back to normal memory or dump it. Please be patient and wait
until the dialog in the app disappears again.
7.8 Number of zRam devices
Default: maximum supported by kernel
Expected impact: Multipe zRam devices can improve overall zRam performance
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
significantly.
Note: You can only change this setting if you switched zRam to Off before.
7.9 zRam total disk size
Default: 100 MB
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.
In fact, proven good values for the total size are something around
300-600, but also 100 or 200 can also help already when you have memory
You can try which size fits you best, there is no harm in playing with this setting.
Note: You can only change this setting if you switched zRam to Off before.
7.10 Swappiness overwrite
Default: Off
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 is the stock kernel setting without any swap. If you activate zRam
in Boeffla-Kernel, the swappiness will be set to 80 automatically.
However, by enabling this switch you can overwrite with your own rate.
You can set it to higher values like 90 or 95, which many report to use
zRam even more efficiently for them. Others set it down to 30 and are
more happy. It depends on your memory requirements and usage pattern.
7.11 Android Low Memory Killer settings
Default: Kernels default settings (different for Samsung and CM based kernels and versions)
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 .
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 by using the Reset button in the Boeffla-Config
7.12 CIFS module
Default: Off
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.
7.13 NFS module
Default: Off
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.
7.14 XBox module
Default: Off
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.
7.15 Axis module
Default: Off
Expected impact: You can use wired Ethernet by using a 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. DHCP will automatically be used for IP configuration.
Note however, DNS resolution does not always work, so best is to use
the wired connection primarily for accessing your local LAN only.
7.16 exFat module
Default: On for Samsung kernels, Off for CM kernels
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
will not be able to access exFat formatted storage devices anymore
unless you switch the exFat support on again.
Caution: exFat support works fine in Samsung
firmwares, for CM you need to give it a try (be aware you can corrupt your data though!)
7.17 Ntfs module
Default: Off
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.
7.18 Android logger
Default: Off
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.
7.19 Kernel logger
Default: Off
Expected impact: By keeping the logger off, less write access to the sd cards and potential battery savings
Note: This option cannot be switched to Off for CM and Omnirom based kernels, as this would cause weird side effects.
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.
(C) andip71, 11.03.2014
All rights reserved.}