1. Are you ready for the Galaxy S20? Here is everything we know so far!

Help understanding battery usage

Discussion in 'Android Devices' started by LHR, Apr 16, 2012.

  1. LHR

    LHR Newbie
    Thread Starter

    Hi all,

    My battery has started draining extremely quickly (from 100% to 24% in 8 hours -- I've hardly used it beyond just "being on") and I'd like some help understanding why. My phone also feels quite warm when I remove it from my pocket after two hours of apparently sitting there unused.

    If I look at my battery usage, it says:

    Android OS - 40%
    Screen - 17% (time on: 18 minutes)
    Cell standby - 16%
    Wi-Fo - 12%
    Phone idle 9%

    Everything else is <= 2%.

    If I press Android OS, it says:

    CPU total: 1h 6m 50s
    Keep awake: 6h 1m 40s

    The "Keep awake" stat is a bit suspicious. What is going on here? Does anyone notice anything strange with these numbers?

    Before today, screen usually took up around 50% of the battery.

    Thanks!

    LHR
     



    1. Download the Forums for Android™ app!


      Download

       
  2. LHR

    LHR Newbie
    Thread Starter

    I've done some more research on this issue and found:

    - This thread on the Google product forums
    - This Android bug repot

    I will try some of the suggestions and post what I find.

    Has anyone else come across this issue? It does seem to be an ICS issue and not HTC One X specific (this post could be merged or closed if I found another thread in a different forum).
     
  3. s.m.knipe

    s.m.knipe Android Expert

    The inflated Android OS stat is artificial- the Google engineer confirmed that on her Google+ account, and it is supposed to be resolved in Android versions 4.0.4 and above (apparently it didn't make it into HTC's build for the One X, 4.0.3). In essence, that number is inflated because certain system processes get counted twice, so she fixed the algorithm. The algorithm determines how the OS communicates with the battery (and vice-versa) so the fix should improve battery life.
     
    LHR likes this.
  4. LHR

    LHR Newbie
    Thread Starter

    Interesting.

    I'm a new Android user so I don't really know about manufacturer updates. How often does HTC issue them? Can we expect an update soon?

    I've uninstalled Google Reader and my battery usage seems to have normalized (screen is becoming a higher percentage of battery usage). The problem started around the time I installed Google Reader so hopefully that is the problem.

    I will post an update after a recharge.
     
  5. s.m.knipe

    s.m.knipe Android Expert

    There are three levels to Android OS updates, and there are two different types ("Updates" versus "Upgrades," to use Motorola's terminology). "Upgrades" are movements to a new OS release (think from Windows Vista to 7, Mac OSX Snow Leopard to Lion, etc. except in the mobile world, this is provided from the manufacturers if feasible because they often include important enhancements and security improvements), while "Updates" are minor releases that (usually) address specific issues/bugs/features that need more immediate attention.
    Now, the three levels I spoke about are:
    1. Google (actually not really Google but the Android Open Source Project, a division of the Open Handset Alliance that is housed & funded by Google)
    2. The Manufacturers
    3. The Carriers

    1. Google/AOSP fixes issues and comes up with cool stuff all the time, so they add these "patches" into the online repository for what is the cutting edge of Android as an OS. Once enough of (or sufficiently critical) these accumulate in the newest version of that online repository (or "fork"), a "release" is generated and goes into testing and eventually gets packaged into an OTA release candidate. This is pure "vanilla" Android at this point, no Sense, Touchwiz, Blur, etc. Typically the OTA will then go to testing for release to the Nexus (pure Android) devices and then get pushed out via OTA. That is the limit of Google/AOSP's involvement.
    2. The Manufacturers watch this online repository and pull down the patches and pieces of relevant code to their devices. Then they begin re-working them so that they work on their devices (make sure they have the correct drivers for the specific hardware and such), and then begin adding their "enhancements" to the OS (i.e. Sense and Touchwiz, and Blur, etc.). Then they test their additions to the code, and eventually package it and get it ready for release to their devices. Typically at this level there are several devices with different hardware, so each device is developed for individually (motorola is supposedly working on pushing updates that formulaic-ally call on the drivers, so they can code the update for all their devices and thereby speed up the process, but I think they were hitting issues), and so it can take a bit of time, but usually they release each update/upgrade as they complete it. Unlocked International devices (not carrier-branded/ carrier-specific) get their updates at this time.
    3. Lastly, if it is a carrier-branded device the Carrier can decide whether they want to add any of their specific applications ("bloatware") and also test the updates/upgrades themselves (usually there are little tweaks to their proprietary radio and baseband code), beofre okaying the release and sending it out to their devices.

    The releases usually sit on a server at Google once completes, and everyone should install a LogCat app (or similar) so that when you get a notification for an official release coming to you OTA, you can grab the URL and share it, then others can point their browsers to the URL and grab the release themselves prior to waiting for the notification. Notifications to download the OTA releases are sent out in batches, based on your IMEI number (think serial number for the device) and chosen randomly.

    Also, if you decide to root and install custom ROMs, most of those developers are writing their code based off the "AOSP drops" just like the manufacturers, so they tend to "bake" features into their ROMs much faster than you will get it via official OTA, but there is the process of rooting (not hard but will probably void your warranty), and almost weekly (typically) flashing of an update to the ROM (for new goodies) as trade-offs for getting the latest and greatest. I've lived in both worlds, and I now prefer to just wait for the OTAs simply for time reasons...
    Hopefully. Sometimes a poorly-coded or rogue app can hijack a few processes and really push that number up there. If it was the official Google Reader app, I would wager that its issue was that it was trying to do something (check for updates) but was being blocked/interrupted for some reason and so never closing out that process...

    Always read the reviews of apps to see if there are known issues that haven't been patched yet (read the reviews back at least to the last update date for the app)!
     
    El Presidente and LHR like this.
  6. LHR

    LHR Newbie
    Thread Starter

    Wow! That was tremendously helpful.

    Is it possible to cherry pick any level of update? I.e. can I initiate Google OTA updates without having rooted my phone?

    Or do I have to wait until the carrier approves the update? 1->2->3->me Rather than 1->me via OTA update URL.

    I'm thinking about rooting my phone and will probably do so after four months or so.

    Thanks again!
     
  7. s.m.knipe

    s.m.knipe Android Expert

    Good thinking! But unfortunately not, because the OTA releases are incremental in nature, and written so as to update a certain software version number to another software version number. To jump backwards (firstly would not work because the bootloader would not know what to do with the file) would be bad because an update might change the way a system calls a process and where the code for that process is stored, going back to the old software version would create an issue because it would be looking for code that isn't where it thinks it is. Going forwards likewise might skip important steps (each update is written with the presumption that the device is on the previous version), and likewise cause issues. So yeah, short of rooting you are locked to the full path releases have to follow for your device.
    You can revert back to previous official versions, but you have to use the full ROM image to do so and it is a bit more complicated than the update process (it is done like rooting/flashing ROMS). The release files are not (usually) complete ROM images...
     
  8. LHR

    LHR Newbie
    Thread Starter

    Thanks for all the info.

    After uninstalling Google Reader, Screen is now using double the battery the kernel is using, as it was before.

    Thanks for all your help.
     

HTC One X Forum

The HTC One X release date was May 2012. Features and Specs include a 4.7" inch screen, 8MP camera, 1GB RAM, Nvidia Tegra 3 processor, and 1800mAh battery.

May 2012
Release Date
0
Reviews
Loading...

Share This Page

Loading...