[General Questions and Answers] Lusty Rugnuts:
Ok, I'm running a couple battery drain tests again.

Test1 is a simulation of how I would use the phone at home, except it's unplugged from USB. Typically I'd plug it in, but I can't do a battery drain test with it plugged in.

Conditions:

================================

All the above changes applied to phone

CPU allowed to range in speed from 299 MHz to 1.3 GHz, Interactive throttle scheme

Test starts with battery at 100% (4291 mV)

Podcast Addict running and playing podcasts saved to the SD card

----------

After starting Podcast Addict and getting a podcast playing, I ran 'adb shell dumpsys cpuinfo' and checked for the PIDs of logd (PID 282) and logcat (PIDs 439 and 737), then used ADB to kill those processes:

adb shell

su

kill 439

kill 737

kill 282

exit

exit

{The PID of an app is different each time the app is started, so don't just use the PID numbers above.}

Logd started back up, but it's no longer hogging the CPU. Logcat started back up, but I don't think it's attached to any logging at the moment (it doesn't attach to any logging until I manually start adb logcat on the computer, and it goes back to essentially no CPU usage on the phone after I stop adb logcat on the computer).

The phone will stay in this condition until it's rebooted. This is nice in that you can run the phone in this condition the whole day, but it's also inconvenient because you have to remember to kill logd and logcat after each reboot. I'm considering writing a [ROOT] app to kill logd and logcat automatically. I have to convince Podcast Addict's author to include a setting in Podcast Addict to automatically run another program after PA starts playing a podcast. Or I suppose I could use the same intents as PA uses to trigger the [ROOT] app.

----------

The phone is set up so it automatically goes into Battery Saver mode when the battery hits 99%.

WiFi and Cellular Data is off. Location is off. Airplane Mode is on.

AFWall+ is in 'Lockdown' profile (block all connections).

Bluetooth connected to Bluetooth headset.

No other apps running.

The screen will remain on for the duration of the test.

The phone will run for 1 hour.

Before I discovered how to disconnect logcat and logd from Podcast Addict spamming the logs with AudioThread entries, the CPU would stay at 1.3 GHz if I left it unthrottled, and use 4 or 5 cores. It'd drain the battery at about 8% per hour even with the CPU pinned to 299 MHz maximum and the screen off. The CPU would range up to a temperature of 56C.

Now the CPU throttles back to 1.14 GHz at times when I leave it unthrottled, uses only 2 cores most of the time and 3 cores some of the time. The CPU stays around a temperature of 40C.

================================

Result: After 1 hour, the battery drains to 94% (4163 mV).

In one hour, the phone drained 128 mV from the battery. From my previous battery test, I know that about 10 mV of that can be attributed as the minimum drain with the phone sitting idle, no apps running, screen off. So the phone now lasts longer with the screen on and the CPU allowed to range to its maximum speed, than it used to last with the screen off and the CPU pinned to 299MHz maximum, while playing podcasts.

I'll recharge to 100%, then start the second test.

---------- Post added at 10:40 PM ---------- Previous post was at 10:08 PM ----------

The second test will have the same setup in the phone, the only changes will be that the screen will be off and the CPU pinned to 299MHz maximum. This simulates how I use the phone during the day... yeah, I keep the Airplane Mode on most of the time... if someone calls me, they can leave a voicemail if it's important, and I'll get back to them. If it's not important enough to leave a voicemail, it wasn't important enough to call me in the first place. ;)

Starting voltage: 4300 mV (100%)

Ending voltage: 4227 mV (97%)

Only 73 mV per hour battery drain when playing podcasts, or ~63 mV per hour above the baseline idle battery drain. That's pretty good.