Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: battery drain issue - always "awake" when playing?

  1. #1
    Junior Member
    Join Date
    Oct 2012
    Posts
    6

    battery drain issue - always "awake" when playing?

    I noticed that when I'm using beyondpod with the internal player, it always keeps my phone "awake", even when the screen is off. This causes the battery to drain faster than if I was using other music playing apps that don't keep the phone "awake". See the attached screenshot - whenever beyondpod is running, System *wakelock* is also running. I forgot to take a screenshot, but on the battery graph, this looks like a big bar of "awake" that doesn't correspond to "screen on". I feel like maybe it has to do with the internal player having controls on the lock screen? While this is a nice feature, not worth it to consume more battery. Any ideas? Should I try using the external player or something? Anyone else experience this? I have a samsung galaxy s3.
    Screenshot_2012-10-08-23-27-07.jpg

  2. #2
    BeyondPod Team
    Join Date
    Mar 2012
    Location
    UK (BP Team member from Jun 2012 to Mar 2017), http://blog.juwlz.co.uk/
    Posts
    4,169
    I have an S3, but almost all of my podcast listening is done in circumstances where my phone is charging, so I haven't seen this.

    Does the same thing happen if you use the music player? What version of BeyondPod are you using?

    Assuming you don't have a JB ROM installed, could you please install CatLog, fully charge the battery (to reset the stats), and then unplug from the charger and use BeyondPod straight away for a while to reproduce the issue, and then IMMEDIATELY run CatLog and email the full log and new screenshots to support@beyondpod.mobi, with a link to this thread.

    BTW, I've just tried it, leaving BP playing for 60 minutes on battery after charging, there's no sign whatsoever of Wakelock:



    I was using the latest beta - 3.0.35

    Julie
    Last edited by juwlz; 10-14-2012 at 03:30 PM. Reason: Correct typo

  3. #3
    Junior Member
    Join Date
    Oct 2012
    Posts
    6
    I'm using ICS (4.0.4), and beyondpod version 3.0.19.
    To see whether wake is being held by an app, you have to either touch the battery graph at the top of the screen you were on, so you see something like this:
    Screenshot_2012-10-14-15-58-36.jpg
    or by using another app like gsam, https://play.google.com/store/apps/d...labs.bbm&hl=en

    Actually it seems like any media app seems to hold wakelock so maybe this isn't a beyondpod issue but an android issue (or maybe wakelock is necessary when playing media?)

  4. #4
    Senior Member
    Join Date
    Mar 2012
    Posts
    109
    I have noticed the battery use on the high side % wise, generally i find the media server (is this the default player) is above BP and then beyondpod is below it at a lower % ,I'll try that app and see what it says on my SGS.
    Nexus 4| The L Preview | BP evo

  5. #5
    Junior Member
    Join Date
    Oct 2012
    Posts
    6
    did a bit more googling, and it seems like this is a mediaplayer thing that can't be avoided:
    http://forum.xda-developers.com/show....php?t=1682958

    and here is some insight into wakelocks and media players, and why this is a bad programming decision:
    http://blog.wbkang.net/tag/wakelock/
    In my opinion, one of the biggest mess in Android right now is the existence of the Wakelock. The wakelock has caused quite a scene in Linux kernel development before. The wakelock is a simple power management mechanism where obtaining the lock would prevent the phone from going to lower power state as long as the lock is held. In my opinion, the wakelock is rightfully one of the worst ideas in Android now that gives Android a lot of bad names with regards to battery life. There are a couple reasons why this is a bad idea.

    On Android, all music players keep the CPU alive 100% of the time while the music is played. Thatís including when your phone is in your pocket with the screen off. I am not making this up! Initially, I discovered this by inspecting the CPU sleep time from Spare Parts app. And, I confirmed my suspicion by reading the source code of MediaPlayer. Thatís more than 90% CPU time and battery wasted for nothing.
    more info than you ever wanted to know about wakelock:
    http://forum.xda-developers.com/show....php?t=1462020

  6. #6
    BeyondPod Team
    Join Date
    Feb 2012
    Posts
    1,033
    As far as Android and Media Players, for now Wake Locks can't be avoided. If you don't get a Wake Lock during playback the playback will randomly stop when the whole device goes to sleep. This has been the case since the early days of Android, but may change in the future (it is rumored that next version of Android 4.2 will focus on optimizing power management - similar to the way Jelly Bean focused on the smoothness of the UI).

  7. #7
    Junior Member
    Join Date
    Oct 2012
    Posts
    3
    Agreed, Beyondpod has recently started eating battery. Like everyone else I am seeing a stay awake time equal to the time I have used the player. BP is using about 10% of the phones battery per hour. Needless to say I can't really use it anymore when traveling. Any ideas?

    Currently on 3.0.3.7 installed on a Sprint Samsung Galaxy S3 running Jellybean 4.1.1 rooted Stock

  8. #8
    Junior Member
    Join Date
    Oct 2012
    Posts
    6
    I thought I posted a detailed explanation of this, but that post seems to have been lost. Anyways, this is not a beyondpod issue, but a mediaserver / android issue.

    http://blog.wbkang.net/tag/wakelock/

    In my opinion, one of the biggest mess in Android right now is the existence of the Wakelock. The wakelock has caused quite a scene in Linux kernel development before. The wakelock is a simple power management mechanism where obtaining the lock would prevent the phone from going to lower power state as long as the lock is held.

    On Android, all music players keep the CPU alive 100% of the time while the music is played. That’s including when your phone is in your pocket with the screen off. I am not making this up! Initially, I discovered this by inspecting the CPU sleep time from Spare Parts app. And, I confirmed my suspicion by reading the source code of MediaPlayer. That’s more than 90% CPU time and battery wasted for nothing.
    For more information:
    http://forum.xda-developers.com/show....php?t=1462020
    http://www.doggcatcher.com/node/2776

  9. #9
    BeyondPod Team
    Join Date
    Mar 2012
    Location
    UK (BP Team member from Jun 2012 to Mar 2017), http://blog.juwlz.co.uk/
    Posts
    4,169
    Quote Originally Posted by odoyle81 View Post
    I thought I posted a detailed explanation of this, but that post seems to have been lost. Anyways, this is not a beyondpod issue, but a mediaserver / android issue.
    You had, but all the links meant that the forum had marked all the posts as awaiting moderation. Unfortunately, it's a little too subtle about this, so it's easy to miss the ones that need approval. All now done.

    Julie

  10. #10
    Junior Member
    Join Date
    Oct 2012
    Posts
    3
    Quote Originally Posted by odoyle81 View Post
    did a bit more googling, and it seems like this is a mediaplayer thing that can't be avoided:
    http://forum.xda-developers.com/show....php?t=1682958

    and here is some insight into wakelocks and media players, and why this is a bad programming decision:
    http://blog.wbkang.net/tag/wakelock/


    more info than you ever wanted to know about wakelock:
    http://forum.xda-developers.com/show....php?t=1462020
    That's useful and interesting, but I think there is more going on. I just uninstalled Beyondpod and installed Google Listen as a test. When I'm using Beyondpod, I see both a Media server and a Beyondpod entry in the battery list, each is listed as awake the entire time the podcast is being played. It can drain battery at about 10% an hour.

    With the same item being played on Google Listen the Media Server entry still shows up with a wakelock and pretty high drain, but the Listen app shows up way down the list. After listening to a 35 minute podcast there is a 35 minute stay awake time on Media Server, but only 5 seconds stay awake on Google Listen. The actual battery drain is less than half of what I was getting using BeyondPod.

    So, while there is clearly an issue with wakelocks on MediaServer, BeyondPod is creating it's own wakelock, stays awake the entire time a clip is playing and using significantly more battery than Google Listen.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •