You need to be rooted and have TWRP recovery installed on your device to use this feature.

First you need to choose where apps will be restored:

• Internal memory (the default)
• System (only available up-to Android 9, beyond that version, system is read only)

Next you need to specify an option to prepare files for restore:

• Post-boot APK installation and data restore.
  • Compatible with Android up-to 12 (maybe 13)
  • Tested on a Galaxy S7 running Android 12.
• Direct APK installation and post-boot data restore.
  • Compatible with Android 14 and above.
  • Tested on a OnePlus 9 Pro running Android 14.

Note that results may vary depending on Android variant and manufacturer.

You can select both options, but the resulting ZIP will be twice as big to be compatible with most versions of Android.

Considering TWRP becomes less and less available, it is very complicated to test all Android versions and devices. Should you use that feature, don’t hesitate to report your findings sending a request from app’s settings, help and support.

NB: If you believe your kernel supports voltage control but the app is not recognizing it, please send a support request from the app settings. Don’t forget to specify the issue within the request to get noticed.

The most common solution is to calibrate the % reporting, commonly called battery calibration, by running full discharge and charge cycles.

A full discharge cycle is achieved by using the device until it shuts down by itself. It is then required to attempt to restart it unplugged until it won’t restart at all. This determines the real 0%.

A full charge cycle is achieved by charging the phone past the 100%. Charging for 12 hours is one way of doing it, charging for 2 hours past the 100% another way. This determines the real 100%.

However it has been noted that many phones stops charging as soon as they reach 100%, but such phones usually report accurate % in the first place as they use a very different % calculation technology.

Doing one discharge + one charge cycle usually improves % readings dramatically. Doing those cycles a couple of times can also improve it further.

If no improvements can be seen from those cycles, you might be using an extended battery on a device not supporting extended battery properly. Then you can enable the ‘% based on mV‘ in the calibration settings, though it’s only valid if the mV reported by Android OS is consistent.

For example using a 1500mAh capacity battery, a 1% change over one hour = 15mA. a 2% change over 30 minutes = 60mA, a 1% change in 5 minutes = 180mA.

When % is not changing the estimated mA is updated according to the last value.

If current mA = 60mA, and % remains unchanged for 30 minutes, this means current mA <= 30mA, hence the estimated mA is updated accordingly.

Please check how accurate estimated mA is.

For years Google has added restrictions to app running in background, to improve battery consumption, is it successful?

I ran tests with and without task killer for the purpose of verifying this in a real use case, no fluf, no bs.

See the results after months running with and without a task killer (click on screenshot for full-screen):

Look at the avg. on-off line, it shows average run-time when screen’s on or off. 9 hours vs 7 hours, 7 days vs 2 days. Active task killer is a clear winner here, no doubt, no discussions possible.

The process of calibration helps maximize battery life by ‘teaching’ Android the maximum % and voltage range supported by the battery.

This will ensure the longest running time on battery and enhance the life of the battery.

How to to calibrate my battery?

The calibration process does not require any application! It’s a matter of running full charge and discharge cycles. An app can definitely help though!

A full charge cycle starts at near 0% and ends at 100% when the battery is not charging anymore (usually one hour to two hours after reaching 100%).

A full discharge cycle starts at 100% (best after a full charge cycle) and ends at 0% or more realistically when the phone shutdown by itself and it becomes impossible to restart it without plugging it in.

What can I gain from battery calibration?

Simply said, without calibration a device might shutdown at 3% or charge upto 99%. After running calibration a few times it will shutdown at 1 or 0% and charge up-to 100%. Tested on an Iconia A500 and a HTC Sensation!

How can Battery Monitor Widget help calibrate my battery?

The app can help set an alarm for an actual end of charge, and also measure the % and voltage ranges.

It will then measure the aging total battery capacity from a starting value (usually the device’s specs).

How to use the Calibration screen?

You first need to run some full charge and discharge cycles. At least from 100% to 3%. It is best to run the cycles until the % and voltage ranges are maximized. This screen can be used to check range evolution over time.

Once the ranges are maximized, this can be used as initial real-life specifications (which may slightly differ from manufacturer’s specs), except the actual battery capacity which usually follows specifications.

Over time, the calibration screen will provide information on battery aging and it’s new total capacity.

Please refer to that page for more details.

An example?

Let’s consider an example with a HTC Sensation device. A battery having a voltage from 3200 to 4200 with a capacity of 1520mAh. That’s the manufacturer’s specs but real-life shows it’s different (for every phone).

On that phone I initially got a voltage ranging from 3353 upto 4206, capacity from 3% upto 100%.

After 3 full charge/discharge cycles ranges went to 3170-4212 and 1% upto 100%!

If in the future voltage ranges from only 3230 upto 4196 (as it happened with an old HD2 battery), then the actual capacity will be reduced accordingly.

First, it’s important to differentiate the 2 types of phones:

• Phones providing real mA measures
• Phones not providing mA measures while charging (main screen shows “Estimated: xx mA” while charging)

The first category of phones, with real mA measures, will calculate real battery capacity mAh no matter how the app is configured.

The second category requires special attention and the app need to be configured in this way:

• A battery profile must be created with the manufacturer’s specified battery capacity (mAh) and the AC charger output power or
• The in-use capacity must be set to the manufacturer’s specs
• The AC charger output power must be set matching charger’s specs.

The app will then use 3 simple facts to determine the real battery capacity:

• Charging can’t go over the charger output power (frequently 1000mA).
• From 0% to 50%, phone uses the maximum charger capacity.
• Above 50% charging rate is lowered to protect battery from aging faster.

If the charging consistently goes over the charger power, it means the defined mAh is over-estimated and the app will adjust the results accordingly.

If the charging consistenly stays lower than charger power while screen is off, it means the defined mAh is under-estimated and the app will adjust the results accordingly.

So it’s important to set the original battery capacity when using extended battery as it is easier to adjust over-estimated values than adjust under-estimated because the later requires the screen to be switched off. While screen is on charging is always lower than charger power hence the need to have the screen off.

Whether the battery capacity is set to 2000mAh or 20.000mAh the app will easily discover a lower battery capacity because the charging (mA) will consistently be above actual charging power between 0% and 50%.

Here is a way to correlate the results: Charging times increase with battery capacity, eg a 3500mAh battery must take longer to charge than a 2100mAh battery.

Battery manufacturers make battery safe range from 2800mV up-to 4300mV, while it’s considered empty at 3200mV on Android (that’s kinda 40% remaining capacity). So going there won’t hurt any battery (well, no guarantees obviously).

There are 2 factors that degrade batteries:

1. Batteries have limited cycles, so the more cycles the sooner the battery will age, deteriorate or even die.
2. Charging and heat are not welcome either for batteries. Above 70%, heat accelerates battery aging.

The second factor is often dealt with by manufacturers by offering an option to limit the maximum charge level while plugged.

This is what the Battery Life eXtender mod from XDA member Ezekeel is all about!  And 3C All-in-One Toolbox allows you to configure it when available in your custom kernel, see here for more information.

For more information on how to extend your battery life, here is an interesting Wiki (see battery life chapter). 

The important points are those:

-Keep battery cool, and avoid charging past 70% while using the device possibly causing over-heating.

-You can discharge your battery fully (voltage going down to 3200mV) it won’t hurt as 3200mV is the safe threshold mentioned in the Wiki above!

Android Firewall requires specific support from the Android kernel. If not implemented, it will not work.

Most custom Kernels do implement required support for IP filtering, eg the Firewall.

Unlocking issues, please read here.

Since beginning of 2020, Pro APK are only unlock keys to the main apps. On Android 10 and below you can hide unlock key icon to only have app’s main icon in your app drawer.

Since 2024, Pro APK do not have app icon, but you can open their UI from Play Store’s app page.

To benefit from the full potential of these apps you need to install the main app and its unlock key.

All apps links are provided above.