Extending life the smartphone battery

One morning, I was commenting to an iPhone user that his battery is nearly flat. He is trying to prolong the battery life by not charging overnight, reducing the charge cycles. The battery is currently a third party replacement as the original got worn out.

That got me thinking. My phone with Oreo 8.1, the overnight drain is around 0.5 to 0.8%. Why don’t I stop charging during the night and only when needed?  Battery life is a function of the number of recharge cycles. By reducing this, it would make the life of my OnePlus 3T last longer.

So today starts this little experiment. This is going to be interesting.

Running with Android Oreo Part 2

I was curious about Android 8.1’s Neural Network API, so I upgraded my from Oxygen OS 5.02 to OmniRom.

After 2 days on it, I realized that the apps must be able to support the API and I wasn’t even sure if the stock camera app is able to do any machine learning.

Then stuff started breaking. The first thing I noticed was Llama stopped detecting the cells stations, which means no profiles and actions were activated. Whatsapp replies using Pushbullet don’t get posted. Strangely Pushbullet’s messages work. A reinstall of Pushbullet restored all functionality.

That leaves Llama. The lost of this functionality was grinding on me, so I installed E-robot to take over. Surprise surprise, it could not consistently read the cell information too. I thought maybe it is the OmniRom, not me. I flashed NitrogenOS, an Android Oreo build that is in part based on OmniRom. Everything came back. Llama is back to work, toiling silently in the background, turning on and off WiFi, changing sound profiles.

NitrogenOS is not without its faults. Some builds have a strange behaviour that I am trying to figure out.  The annoying bit is the /data partition is now encrypted.

Android Oreo is not without its quirks.  The Battery History Details screen is now highly summarized.  The cell, WiFi, Awake graphical info is no longer available.  These are all summarized as figures.

At least I am having Feb 18 security updates.

OnePlus 3T and DM_Verity

I was editing the OnePlus 3T build.prop file when I encountered the DM-verity warning.  This is part of the verified boot process.  More details can be read here.

There were several posts to use the following to turn off and turn on DM-verity as a reset.  Unfortunately, that only gives an error, “FAILED remote:unknown command”

fastboot oem disable_dm_verity

fastboot oem enable_dm_verity

After some searching, some on recommended,

adb reboot “dm-verity enforcing”

That caused the device to restart.

I have found by accident, even with the dm_verity error, if I don’t do anything the phone eventually boot.