Jump to content
Poweramp
tdas777

v3 build 823 - High Battery Consumption

maxmp

Before posting here, please try the following:

Settings / Look and Feel / Player UI / Chromecast Button - Disable (Poweramp will restart)
This helps with some un-updated/failing Play services libraries being loaded into Poweramp and increasing battery usage.

Settings / Library / Scanner / Auto-scan - Disable
This helps with some apps constantly/frequently sending file system change event causing Poweramp to rescan frequently and increasing battery usage.

Message added by maxmp

Recommended Posts

25 minutes ago, maxmp said:

@dinfinity thanks for the log, this was helpful. Yes, in this use scenario this thread loops forever, fixed for the next build will which be pushed asap.

@maxmp: That is great news! I look forward to not reproducing the issue with the new build!

Share this post


Link to post
Share on other sites
1 hour ago, andrewilley said:

Please try build 853 folks...

Andre

First tests are positive! I can no longer reproduce the issue!

Thanks @maxmp for the fix and @Crericper and everybody else for the information and cooperation on this issue!

Share this post


Link to post
Share on other sites

The power of community support :)

No worries, I was as frustrated as the rest of you - knew it would eventually be sorted. Now to test my playlists!

Moho

Share this post


Link to post
Share on other sites

If everyone agrees that this issue is now solved (thanks for everyone's help and patience!) I will close this thread at the end of the week, so any new issues that might occur in the future can be reported separately. 

Andre

Share this post


Link to post
Share on other sites

I've used the latest version for a couple of days now and haven't seen any more excessive battery drain. Thanks to everyone who helped fix the issue!

Share this post


Link to post
Share on other sites

@RBEmerson, it was a thread that checks play service, but went into infinity loop, and I think, it is most likely caused by play service not responding. 

Quotes here: 

On 11/7/2019 at 5:05 PM, Crericper said:

After some extra digging, found this: 

Seems like it is waiting for a thread to stop: 


"awakenReason":1,"stack":["java.lang.Thread.join(Thread.java:1268)","com.maxmpz.audioplayer.player.PlayerService.onDestroy","android.app.ActivityThread.handleStopService"...

As: 

On 11/7/2019 at 9:24 PM, dinfinity said:

Nice work! com.maxmpz.audioplayer.player.PlayerService.onDestroy would be the significant bit here. The application generating the log seems to be a MIUI monitor app, but it still gives valuable information about PA.

Looking at "beginTime":3210750," and endTime":3214770",  it seems that the MIUI monitor gives off a warning because the onDestroy method is taking more than 4 seconds. This is probably because something in that onDestroy method is stuck in an infinite loop as hypothesized before.

 

On 11/8/2019 at 8:11 AM, dinfinity said:

@maxmp: Sent you the bug report. I suspect this is the culprit:


"player service thread" prio=5 tid=9 Suspended
  | group="main" sCount=1 dsCount=0 obj=0x12c07340 self=0x7f78b8fc00
  | sysTid=21390 nice=0 cgrp=bg_non_interactive sched=0/0 handle=0x7f7618d3a0
  | state=S schedstat=( 0 0 0 ) utm=3765 stm=66 core=5 HZ=100
  | stack=0x7f7608b000-0x7f7608d000 stackSize=1036KB
  | held mutexes=
  at ׅ.tg$D.D(":702)
  at ׅ.tg$D.ׅ(":696)
  at ׅ.tg$L.ׅ(":759)
  at ׅ.tg.ׅ(":645)
  at ׅ.px.release(":5034)
  at com.maxmpz.audioplayer.player.PlayerService.llll(":3093)
  - locked <0x014f9035> (a java.lang.Object)
  at com.maxmpz.audioplayer.player.PlayerService$v0.ׅ(":1145)
  at ׅ.pz.handleMessage(":29)
  at android.os.Handler.dispatchMessage(Handler.java:102)
  at android.os.Looper.loop(Looper.java:148)
  at android.os.HandlerThread.run(HandlerThread.java:61)

(utm is high and this seems to be the only thread that is not waiting/native waiting)

 

Share this post


Link to post
Share on other sites

@Crericper

Quote

 

@RBEmerson, it was a thread that checks play service, but went into infinity loop, and I think, it is most likely caused by play service not responding. 

Interesting. Play Service was mentioned, more than once, as a possible problem. IIRC, tinkering with it was occasionally useful, but didn't prove to be a certain work-around. 

The infinite loop must have been extremely active to hammer the CPU to the point of heating to the point it did. Of course high battery consumption inevitable in this instance. 

FWIW, I've been using existing playlists with no problems. Battery consumption is well within the expected range. 

Share this post


Link to post
Share on other sites

Before this thread closes, thank you everybody who has been a reason behind this issue being found, pin pointed and fixed, me included. 

So happy! I really don't have a list of usernames, just thanks everybody. :)

I don't need other players now. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...