Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 14 Nov 2013 01:28 PM by  steven.eckhoff
Android high power consumption during sleep.
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages
mvly
Basic Member
Basic Member
Posts:104


--
06 Nov 2013 07:11 PM

    I am wondering why android uses much more power during sleep compared to Linux on the DM3730. I am using Wattson to measure the current and during sleep, the Linux can hit 1-2mA current draw for the SOM. But for Android 2.3.4, it is around 15-16mA.

     

    My design requires the absolute lowest power consumption. Is there a way to drop it comparable to the Linux boot?

    steven.eckhoff
    Basic Member
    Basic Member
    Posts:192


    --
    14 Nov 2013 09:05 AM

    Mvly,

    I looked into this and it looks like there were some issues with power in Gingerbread. In the latest Ice Cream Sandwich BSP the suspend number is down to 8.4mW.

    1. Have you tested the ICS BSP?

    2. Are you able to use ICS for your project?

    mvly
    Basic Member
    Basic Member
    Posts:104


    --
    14 Nov 2013 01:23 PM

    I am not sure about Gingerbread power consumption. It seems to work in the sense that it does draw significantly less than its active power. However I cannot use it because I need the 5mW or less power consumption requirement during sleep. Hence why I went to ICS.

    It turns out the culprit to the ICS power consumption bug was the NON wifi module version. I figured this out by monitoring the serial debug ports. It turns out the ICS software was searching for the bluetooth and wifi module and hence it never properly went to sleep. Once I replace the SOM with the wifi+bluetooth SOM, everything performed as expected.

    I also enable the low power sleep option in the init.logic.rc file to further push power consumption down. All in all, I was able to get it to what I wanted. ~5mW during sleep.

    So the simple solution is to use the wifi Torpedo module. I will have to look further to figure out how to turn this "searching for module off" for the non wifi version.

    steven.eckhoff
    Basic Member
    Basic Member
    Posts:192


    --
    14 Nov 2013 01:28 PM
    mvly,

    I am glad you were able to get the power down. I will also take a look into how we could fix the issue on the non WiFi SOM.
    You are not authorized to post a reply.