[Verizon Samsung Galaxy Note II] mikeyxda:
Two Battery Display Options

Display color circle battery meter with text % (default):

From the home screen, press "Menu"

Select "Display"

Scroll down and UNcheck the "Display battery percentage" checkbox

Reboot (reboot is required to update the status bar and add the circle battery meter)

Display text percentage only (no meter):

From the home screen, press "Menu"

Select "Display"

Scroll down and check the "Display battery percentage" checkbox

Reboot (reboot is required to update the status bar and remove the circle battery meter)

Sticky Debloating (v1.06 and up)

Sticky debloating is done using a simple install script located in /data/MeanBean.blt. Here are the instructions on how to use sticky debloating:

First time you use sticky debloating

We set up sticky debloating by flashing the bloat definitions template which contains a list of common bloat items:

Reboot to TWRP and flash /sdcard/MeanBean/stickybloat.zip (also located in /data/MeanBean/stickybloat.zip if not on your SD card)

The bloat definitions file (/data/MeanBean.blt) will be created

This file does nothing until you edit it (below)

Boot normally and continue below to edit the bloat definitions

Each time you change the bloat definitions

We simply edit the /data/MeanBean.blt definitions to our liking:

Use Root Explorer or the included ES File Explorer in root mode and open /data/MeanBean.blt (don't use a PC to pull/push the file else it may be corrupted)

Follow the directions at the top of the file, editing each line as appropriate for your debloating

Back out of Root Explorer/ES File Explorer, saving the file on the way out

If you used ES File Explorer, it fouls up permissions on the saved file: long hold on the file after saving it, then scroll to "Properties" at the bottom, click "Change" and check ALL permission boxes!

Reboot to TWRP and relfash the ROM! You must reflash the ROM to make the changes stick

Now each time you dirty flash an updated version of the ROM, it will be debloated

Notes on debloating

Debloating is done via a simple script that removes what you don't like: the ROM install script runs this debloating script each time as part of the install process, so installing a new ROM version 1.06 or later will result in the ROM automatically being debloated. Obviously if you get creative and do other stuff in this debloating script, adding items that are not in the standard template. If you run into trouble though, you can always reflash /sdcard/MeanBean/stickybloat.zip (or /data/MeanBean/stickybloat.zip) to "nullify" the debloating and start over.

Debloating example - debloating Zappos

Original code in the MeanBean.blt file:

## Amazon Zappos
#rm /system/app/Amazon_Zappos.apk

To debloat, simply remove the hashtag on the code line like this:

## Amazon Zappos
rm /system/app/Amazon_Zappos.apk

Sticky Settings

Options that affect ROM performance and appearance can be found in the sticky settings Aroma installer. This file can be found on /sdcard/MeanBean/stickysettings.zip after flashing the ROM. Simply flash the file via TWRP recovery and select the options you desire. Once you make your selections, your selections will survive dirty flashes (for example, when you flash updates without wiping data)... hence the name "sticky settings". Just select what you want once and forget about it!

Note about the version number that displays on sticky settings install

The version number that displays when you run the sticky settings corresponds to the last version of MeanBean where the sticky settings had to be changed. As a result, the version number of the sticky settings will rarely match the version number of the ROM because the sticky settings are not changed with every ROM version.

Available sticky settings

4x4 or 4x5 launcher (default 4x4)

Infinite scrolling - whether or not the launcher wraps around at the end points

Choice of dim/bright status bar icons (If using the bright status bar, test for potential screen burn-in from time to time to be sure bright mode isn't causing image retention)

Screen on w/new SMS/MMS - whether or not the screen wakes with incoming new text messages (default no screen wake)

Keyboard auto-correct - auto correct for the Samsung keyboard

Palm swipe (R to L) to sleep

Palm swipe (down or up) to go home

4 finger touch to go home

Ringer fade - whether or not the ringer starts out at low volume, then changes to full volume (default no volume fading)

Display AM/PM - whether or not "AM" or "PM" is displayed with the clock on the status bar (default no AM/PM)

Toggles - display the stock toggles/quick settings or no toggles (default no toggles: use included Power Toggles or some other choice if you like)

Zero wake lag - whether or not to get rid of screen-on lag (default: get rid of the lag - see below for full details on what this does)

SD card read-ahead - set your SD card read ahead buffer (default 2048K)

De-ASEC - decrypts encrypted apps and places them in the normal /data/app location. Once enabled, just turn screen off/on to de-ASEC installed apps.

Notes on Zero Wake Lag

While most of the options in the sticky settings are pretty self explanatory, I would like to explain wake lag and how to use the zero wake lag option. The zero wake lag option s turned ON by default: meaning you will not get any wake lag. Read on, however, should you feel like controlling this option yourself.

What is wake lag?

Wake lag is a delay (usually between a half second and 2 full seconds) between when you press the power button and when the screen actually turns on from a "sleeping" state. Contrary to what I found in various forums about this popular topic, wake lag is not caused solely by the amount of time it takes for the processors to wake from a deep sleep, nor do the dozens of suggestions that I found make much of a difference: things like turning off the ripple effect, pop up note, ink, or even freezing certain processes. Processor wake time is only part of the equation. In going through system logs in detail, I found many factors that actually added to the amount of delay you get between when you press the power button and the phone is actually usable. Other things such as sensors powering up (accelerometer and light sensor for example) and whether or not you have an external SD card installed drastically affect how much delay is present on any particular phone. I measured the lag on my own phone at 1.7 seconds which, as you can imagine, got old pretty quickly.

But I don't have any lag at all. What's up with that?

If you don't have lag, your phone is never going into a deep sleep. In my own investigation, I found that it takes nothing more than a single misplaced wakelock.acquire command after the screen turns off to keep your phone from going into deep sleep. For your phone to enter deep sleep, each and every wakelock.acquire must be followed by a wakelock.release. That means every app you have installed must behave perfectly and never have an "acquire" without a paired (and properly timed) "release" for deep sleep to occur. Because the processors do take some time (I found about 750ms) to come back on from deep sleep, if you have no wake lag at all, it's safe to say something is misbehaving and creating a wake lock on your phone. If that's the case, the zero wake lag option will have no noticeable effect on your phone.

I turned on the zero wake lag option and I have no more wake lag, but won't my battery die quickly now?

The zero wake lock fix does create a wake lock that prevents your phone from going into deep sleep, but read on: from what I've found, I think this is a good thing! MeanBean already underclocks the processors when the screen is off, which means with your screen off, you only have one core activated and it is running at a maximum of 1 Ghz. In addition, the governor is set to not ramp up frequency as quickly as when the screen is on. This means with the screen off, you have one processor running at slow speed (usually around 200 Mhz) at a very low voltage, using very little juice, but up to 1 Ghz of processing power is still available if something needs to run with the screen off like a media server. The radio in your phone will use far more power than the CPU that is left running to satisfy the wake lock.

Also consider this! With the zero wake lag option turned off, your phone goes into deep sleep in less than one second when you press the power button to turn the screen off! That may sound like a good idea at first glance, but from what I've seen in the logs, I doubt it. I ran the phone normally (allowing deep sleep) and I found that particularly for someone like me who gets a lot of pushed emails, the phone was being forced to wake up hundreds of times each hour! That means if you leave your phone unplugged overnight for example, by the time you wake up, your phone will have shut down and then reactivated and re-powered-up the processors and sensors potentially thousands of times! Is all that waking/sleeping/waking/sleeping good for the sensors and the system in general? I'm not going to say for sure but logic would tell me no, particularly when other processes like maps/google location is already pinging those sensors every few minutes. In fact, I tested the phone over an 8 hour time period with zero wake lag both on and off and my battery life actually got significantly better with the zero wake lag option turned on. Presumably this is because the phone wasn't constantly powering down (and back up) a bunch of circuitry. In the 8 hour time period, I lost 10% battery with zero wake lag turned off and only 6% with it turned on!

Now, if you put your phone in airplane mode and you have nothing running that tends to wake the system a lot, maybe your battery will do better with zero wake lag turned off. It's safe to say YMMV but the option is there to switch zero wake lag off if you wish.