[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thoughts on the Android System and Battery Drain.

Man! I have not seen any flickering or battery drain in over two weeks of heavy use! Obviously, somethings going on, and I only have one or two theories on it at the moment.

First, all of you that are experiencing the battery drain problems, can you please post what Baseband/Modem you are using? It is possible that one of the modems could be causing the problem, namely LI8. I have had it reported that it was causing some people battery drain, and when flashing to LI6, the drain subsided.

Unfortunately, I am unable to verify this myself. I flashed LI8 Baseband, and though the reported Android System use did increase, it did not increase by a very significant amount. The majority of the time, I was getting 11% - 14% using LH3 modem. (With occasional spikes to 28-29%)

Now on LI8, Android System use has increased to a usual reading of 21%. Haven't been running it long enough to detect any real spikes yet.

Anyway, it is something to try, if you want to test and report, it would be most helpful! The more data, the better the accuracy.

My other theory....

This has to do with flashing Firmware, OTAs, roms....

Ok, first let me explain what happens when you flash Firmware and OTAs.

When you Odin flash the stock firmware (or root66), it does not just flash your system partition, but about 9 other partitions as well.

These are the partitions flashed using the stock Firmware.tar

aboot.mbn...............Apps Boot

boot.img..................Boot/Kernel

cache.img.ext4........Cache

NON-HLOS.bin........Modem/Baseband

recovery.img............Recovery

rpm.mbn.................not sure

sbl2.mbn.................Secondary Bootloader 2

sbl3.mbn.................Secondary Bootloader 3

system.img.ext4......System

tz.mbn....................Trusted Zone (Arm Trusted Zone???)

When you flash an OTA update, it patches the existing files and partitions to bring them to the targeted Build. It does flash 5 of the partitions outright, like Odin, and patches 4 others.

These are the OTA Partitions

aboot.mbn................Apps Boot......................Flashed complete

.

boot.img...................Boot/Kernel....................Patched

.

NON-HLOS.bin.........Modem/Baseband...........Patched

.

recovery.img.............Recovery........................Patched

.

rpm.mbn...................not sure.........................Flashed Complete

.

sbl2.mbn..................Secondary Bootloader 2...............Flashed Complete

.

sbl3.mbn..................Secondary Bootloader 3...............Flashed Complete

.

system.img.ext4.......System......................................Patched

.

tz.mbn.....................Trusted Zone (Arm Trusted Zone???)...............Flashed Complete

Now, when you flash a custom rom, such as this one, it ONLY flashes the System and Boot partitions.

So our differences may come from where we started at.

For Example: If you have NEVER flashed any updated firmware, and never applied an OTA update (manually or automatic), then everything except System, Boot, Recovery, and Modem will all be from build UVALEM!

If the last time you flashed a firmware or OTA you used UVALH2, then that is what the rest of your partitions are still from!

Now also consider the leaked OTAs. If the last time you did any of this, you had flashed the UVDLI8 OTA, then all of those other partitions will still be from the LEAKED build, UVDLI8!

So, if any of you can remember what was the last Firmware or OTA that you flashed, please let me know.

Just so you guys know, the last firmware I flashed was the FULL Firmware file for UVALJ4 (root66).

REMEMBER!!!! This is only a theory!!!

I do not know if this will really have an impact here. but I am really trying to figure out what is so different between your phones and mine.

Those of you who have been here for a while may remember Wildchld and I went through all of this when our first JB leaks came out! It turned into such a huge ordeal trying over and over and over and over to make every noob that wanted JB understand what we wanted them to do, and why. Eventually we just dropped the more complicated steps altogether in favor of "just flash it".

I am really just mentioning this to see if you guys have any input either for or against this idea, or maybe itll spark something completely different! I just keep thinking there has to be something different for you to have such a different experience than I do.

Anyway, just wanted to throw that out there! I do not plan on going into complicated flashing requirements right now. But if after discussing it a little, anyone wants to try it, I will tell you what to do, step by step.

Thats all for the moment. I am currently waiting for my Bluetooth Headset to charge....Yes!!! I found it!!! :good::laugh:

Thanks to all of you for sticking with it and reporting your results! I love this forum! :cowboy: :highfive: :cool: