[Motorola Droid RAZR] dtrail1:
I decided to write a little guide about tuning JBX-Kernel. I think I wil send it to Placca, so he can add it to the Guide if he likes to. Maybe Neo.Ank could add this to the OP here? I guess I shouldn't open up another thread about JBX.

INSTALLATION GUDE

The following post includes my personal usage and settings from Aroma Installer plus additional detailed explanations about the options in Aroma and more. You can just follow the steps one by one and then compare and share your exprience.

SO it is actually my personal setup - just like I use it:

1. We start Aroma Installer now and first we DESELECT EVERYTHING in Aroma.

* "Explanation notes"

"Init.d Battery Tweaks"

This is a sysctl script file which sets some kernel parameters to be more battery friendly. But it doesn't work fine on all roms. Sometimes it could cause some instability (but this happens very less), but can potentially save some juice - with a slight loss of performance.

"HDMI OFF by default"

If you don't use HDMI most of the time and/or if your phone got the same where it accidently detects a plugged HDMI cable even though no cable is plugged actually - And note: During these times when HDMI is not in use, switch it off via the HDMI_TOGGLE to save some juice.

"Kernel Enhancement" & "DSHT Kernel Tweaker"

Another kernel configuration tools. Trickster Mod doesn't support all features and options which are availbale in JBX-Kernel, so these apps can be used to adjust some more settings which you would have to tweak manually by sysfs/terminal otherwise.

Some of them are:

- Lowmemorykiller tunables and presets (Note: lowmemorykiller is NOT the same like OOM-Killer whose presets you can set in Trickster Mod)

- Some other kernel parameters

- Some sysctl presets (Note: Sysctl Editor is also present in Trickster Mod or also in System tuner (great for presets, NOT included with JBX) - Sysctl can be used to tweak EVERYTHING which exist in the kernel, but be VERY careful when messing with it. Better play with presets, or leave it alone and use generic by app provided options, i.e. Trickster Mod, of you have no idea about Sysctl tuning)

- Some build.prop tweaks

"Powertop"

Powertop is a commandline-based configuration tool only made for power saving, developed by Intel, actually for Linux, but they provide it also for Android / ARM platforms. It incoudes and shows you several cathegories with stats (i.e. CPU stats, frequency stats, memory stats, etc) and one tuning tab where all power eating hw-devices are listed and marked whether with a "GOOD" or "BAD". When seeing an entry marked with "BAD", you can switch it to "GOOD". A short explanation about each entry is directly behind it (i.e. "USB devices suspend", "Power Aware CPU Scheduler", and more).

I use Powertop not for tweaking, because it's a little complicated to make the settings from Powertop stick after reboot, specially because Powertop doesn't show you how it changes the settings and therer is no "on-boot" option available - I use Powertop ONLY for monitoring. Usually I set everything like I want it, then reboot and open Powertop after the device booted up. I just check all the states and if all entries are marked with "GOOD", I close Powertop - because I know that the best power saving options are active and working.

But if I see an entry (or maybe multiple ones) marked with "BAD", then I identify the related option (that's easy, it's all explaned in Powertop, like I mentioned above already) and set it to "GOOD" by use of whether:

- a Kernel settings app (like Trickster Mod)

- Sysfs via initd. scripts or Sysctl (i.e. if no settings app supports tuning of the related feature)

- Terminal or Root Explorer (if I don't need tje related option to stick after next reboot)

"Xposed Framework"

I guess you know what Xposed is - but for those of you who don't:

Xposed Framework is a very powerful Open Source Android tweaking tool (better saying: a whole tweaking framework) which lets you tweak almost everything in Android on-the-fly - means: mostly there's no reboot rerquired to activate the tweaks. Those tweaks can be i.e.:

- Android SystemUI tweaks (colors, outfit, themes, clock style and alignment, battery icon style, many many more)

- Android System tweaks and functions (Auto 2G/3G, POwer related options, performance related stuff, many more)

- Android Hacks (for Apps, for Android system, for Roms, etc, etc)

- etc, etc, etc, etc

It works by loading specific modules directly into the framework. These modules are developed by users, devs and people like us, like you & me, and many others... Everone with some dev skills can create modules for use with Xposed. It's so beloved by devs and users, because it allows a lot of hacks (and kinda such stuff) to be injected into Android without changing or modifying anything on the Rom/System itself. So you don't have to mess with Android source code and you are protected against messing up your system, which means again that you just can disable a module in case of appearing issues instead performing a full wipe and restore your system by backups or reflash.

It's also so genius because it can even apply all these tweaks to running stock roms! So you can tweaks your stock rom with all the famous features only known from custom roms - without the need to use a custom rom. The only thing which cannot be "hacked" by Xposed: The kernel. But therefor you're here now :D

There are so many modules available, I can't count or list them here.

Just select Xposed Framework in Aroma, flash the kernel and open the Xposed Installer App after booted up. Follow the first steps (just install the actual Xposed FW by one single button tap, then head to the "Download" section (also in the Xposed Installer App) and take your time to scroll through the modules list to find whatever you're looking for, or just browse and I dare you will find something you like. When downloaded and installed some module(s) (the installation of Xposed Modules works like installing a normal App) head to the "Modules" section and enable those modules you like to use (just set a hook in front of them), reboot the phone, profit. But don't forget to open the related module (just open it like an App - assuming the module allows user actions, setting options, etc) and set the feratures you want or and the way you want it to be set.

To give you an example: Android Tuner app - I guess most of you might know it - has support for XPosed too. I remember there are two versions: One for use as Xposed module, and one standalone app. The one for Xposed has some more functions and features. So you just open it and start tweaking the hell out of your phone. :)

"Motorola 10%-Battery Indicator"

This option will install a modified Ramdisk.img for the kexec kernel which includes another reading path parameter for libhealthd (the lib which shows battd binary where to read/write the charging state, voltages, temperature, etc). The RAZR (and all other Moto OMAP phones) usually use the 10% increment. Why? Simply because these devices don't include a hardware battery meter (also known as "Fuel Gauge Meter"). It has to calculate the charging state by software (battery driver in the kernel & mainly by the battd binary which is part of each Android rom). When using the 1% indication, our phones are calculating the charging state (percentage) based on a "bad value", as there is no hw chip watching the battery voltage, percentage, etc, it uses sth like an algorithm (which is part of battd binary) to calculate the acutal percentage. This algorithm is though very accurate and working fine as long as it uses the common 10% increment - but when switching to the 1% method, it has to kinda "guess" the values between the 10%-Steps, which potentially can lead to wrong calculated values after some time. Therefor you have to keep in mind that in 10% mode the charging state rounds up on each value reaching a "5" (means: when battwery os charged to 35%, the status bar/battery icon will display 40%, and so on..) Now, when using 1%b mod, the percentage can be "confused" and then it tries to correct itself, by jumping down suddenly, i.e. from 60% to 40% or sth (or in less cases even jumping up). usually this stops by itself after next charging cycle, but if it happens on each sycle (still getting drops), a manually calibration must be performed (NOT just wiping battery stats, etc, but read my following post to see how this works). After a calibration process (it takes a few days until it takes full effect) you might want consider using the 10% indication method as it mostly prevents from such bad cases and is just more accurate. You can still use i.e. an app like Battery Indicator Pro (with support for Motorola devices) which shows the battery in 1% steps (or also you could use an Xposed module for that).

NOTE: If you ALWAYS handle your battery the right way (the way you charge, when you charge and how long as well as how often you charge your battery), you shouldn't get too much problems with it, also when using the 1% indication.

But if you see that a full calibration doesn't help anymore, or whatever method you tried else already to get your battery back acting normal again, it's a true sign for your battery is already broken.

Our RAZR includes a Li-Polymer battery - more capacity, better lasting time - compared to common Li-Ion batteries - (because they include a materia and not liquid acid, so they can be formed much thinner in example, and its cells can safe more juice - or at least they can safe the juice more effective), but more sensible against temperature drops (up and down) and also overcharging (Yes, modern batteries/devices usually do include a protection against overcharging, but don't be too sure about that and better try to take care of your battery as much as you can, and it will live AND last long!

How to handle such batteries the right way? GOOGLE! :)

"Battery Friend DISABLE", "RIL tweaks for battery life" & "MISC Rom build.prop tweaks"

Battery Friend is working fine and helps saving power for sure - but if you want to use features like overclocking, you will have to disable it. But therefor you don't need to use the Aroma option. You can simply switch BF state by Trickster Mod, and also control its tunables (frequencies) there.

The RIL tweaks were doing a great job in D-WiZ Rom 1.0.4 (Stock based) - but so far I couldn't notify any true improvement in KitKat custom roms by using this feature - but also couldn't see any disadvantages. This really needs to be tested by more people, then share your experiences and let's see if this can help to save battery.

The same like above (about RIL tweaks). These tweaks were also working fine in D-WiZ 1.0.4. Just test and report it.

I am very interested in difference between your and my settings and experiences. You can try my setup if you want, and then after one week of running, please tell me if your settings were better for battery and/or performance.

I hope this helps you a bit. Keep on being a great community! ;)