Jump to content
Poweramp
Sign in to follow this  
SledgeHammer

Wakelock caused by com.maxmpz.audioplayer.player.PlayerService temp (UID)

Recommended Posts

Hi there,

 

i am a registered Poweramp user. I am running Poweramp 2.0.9-build-548-play as full version on a Samsung GT-7275R (Galaxy Ace 3) with rooted stock 4.2.2.

 

Till yesterday Poweramp behaved relatively well. But now it is giving me headaches, and increased my battery drain by 1%/h.

 

It seems as the service

 

com.maxmpz.audioplayer.player.PlayerService temp (UID)

 

is running in the background, I have never experienced such a behavior of Poweramp before. I tried reeboting, but it seems to sit in my memory.

 

Is there something i can do? I do not want to abandon Poweramp, but i am very strict with my apps and battery consumption. I was used to have a drain of about 0.3% to 0.4% per hour when the phone was sleeping. Now it's going up to 1.2%/h to 1.5%/h which really annoys me, because i do not even use the phone.

 

Any help appreciated!

 

Greets

 

Sledge

Share this post


Link to post
Share on other sites

 

did you activate wakelock in the settings?

No, is there a setting for this? At the moment i disabled all automatic scanning. This stops the wakelock completely. It's a workaround, but no solution.

/Edit: I found the setting. This is disabled. Also the service keepalive is disabled. At the meantime i did a full reinstall, this did not help eighter. Only thing that helps is setting automatic scanning to off. I just don't get it. I use Poweramp for 3 months now, but never had any issues with it.

Share this post


Link to post
Share on other sites

I also have this problem with same build version. I use Samsung Galaxy S4 SHV-E330K(Korean model), and Android version is 4.4.2. I don't know Whether this bug causes by android 4.4.2 or Poweramp build 548, but since I updated my device firmware to 4.4.2 and Downloaded last updated version of Poweramp(build 548) via Google playstore, the "com.maxmpz.audioplayer" always keeps running on the background and the battery drains much more than before. Of caurse, I always disabled the Wakelock mode which is in the settings.

Share this post


Link to post
Share on other sites

I have a bbs log from last night. This one has the Poweramp scanner turned off (Manual scanning). As you can see this is ok. What confuses me, iss that the scanner is still there, where it should not be. If you are interested, i can attach another one with the scanner on from the night before in the evening, where the scanner behaved very bad.

===================General Information===================BetterBatteryStats version: 1.15.0.0Creation Date: 2014-02-17 07:28:27Statistic Type: Custom to CurrentSince 10 h 38 m 34 s VERSION.RELEASE: 4.2.2BRAND: samsungDEVICE: loganrelteMANUFACTURER: samsungMODEL: GT-S7275ROS.VERSION: 3.4.0-1654536BOOTLOADER: S7275RXXUAML1HARDWARE: qcomFINGERPRINT: samsung/loganreltexx/loganrelte:4.2.2/JDQ39/S7275RXXUAML1:user/release-keysID: JDQ39TAGS: release-keysUSER: dpiPRODUCT: loganreltexxRADIO: S7275RXXUAML1Rooted: true============Battery Info============Level lost [%]: Bat.: -3% (99% to 96%) [0,3%/h]Voltage lost [mV]: (4316-4273) [4,0%/h]===========Other Usage===========Deep Sleep (): 10 h 35 m 51 s (38151 s) Ratio: 99,6%Awake (): 2 m 42 s (162 s) Ratio: 0,4%Screen On (): 27 s (27 s) Ratio: 0,1%No Data Connection (): 10 h 38 m 34 s (38314 s) Ratio: 100,0%No or Unknown Signal (): 10 h 38 m 34 s (38314 s) Ratio: 100,0%Screen medium (): 27 s (27 s) Ratio: 0,1%=========Wakelocks=========com.maxmpz.audioplayer.player.PlayerService temp (UID): 39 s (39 s) Count:1 0,1%AlarmManager (Android-System): 15 s (15 s) Count:162 0,0%AlarmManager (org.zooper.zwpro.Zooper Widget Pro): 5 s (5 s) Count:68 0,0%Event Log Service (Google-Dienste): 3 s (3 s) Count:21 0,0%AlarmManager (Google-Dienste): 3 s (3 s) Count:73 0,0%ActivityManager-Launch (Android-System): 2 s (2 s) Count:30 0,0%BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 1 s (1 s) Count:1 0,0%================Kernel Wakelocks ================"PowerManagerService" (): 59 s (59 s) Cnt:(c/wc/ec)106/0/0 0,2%"alarm_rtc" (): 18 s (18 s) Cnt:(c/wc/ec)95/86/0 0,0%"alarm" (): 11 s (11 s) Cnt:(c/wc/ec)123/0/0 0,0%"mmc1_detect" (): 6 s (6 s) Cnt:(c/wc/ec)105/0/0 0,0%"pm8921_soc_lock" (): 2 s (2 s) Cnt:(c/wc/ec)90/1/0 0,0%"sec-charger-monitor" (): 2 s (2 s) Cnt:(c/wc/ec)100/0/0 0,0%"power-supply" (): 1 s (1 s) Cnt:(c/wc/ec)184/0/0 0,0%"PowerManagerService.Broadcasts" (): (0 s) Cnt:(c/wc/ec)2/0/0 0,0%"rmt_storage_1103154936" (): (0 s) Cnt:(c/wc/ec)3/0/0 0,0%"event8-847" (system, com.sec.android.sCloudRelayData, com.sec.android.pagebuddynotisvc): (0 s) Cnt:(c/wc/ec)3/0/0 0,0%"msm_ipc_read00000001:00000001" (): (0 s) Cnt:(c/wc/ec)1/0/0 0,0%"KeyEvents" (): (0 s) Cnt:(c/wc/ec)183/0/0 0,0%"qcril" (): (0 s) Cnt:(c/wc/ec)6/0/0 0,0%"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)105/0/0 0,0%"qmuxd_port_wl_0" (): (0 s) Cnt:(c/wc/ec)20/0/0 0,0%"smdcntl0" (): (0 s) Cnt:(c/wc/ec)20/0/0 0,0%=========Processes=========kcompcached (0): Uid: 0 Sys: 3 s (3 s) Us: (0 s) Starts: 0kworker/u:6 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0kworker/u:1 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0kworker/u:0 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0mmcqd/0 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0surfaceflinger (Android-System): Uid: 1000 Sys: (0 s) Us: (0 s) Starts: 0mpdecision (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0mediaserver (1013): Uid: 1013 Sys: (0 s) Us: (0 s) Starts: 0kworker/0:0 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0kworker/0:3 (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0com.asksven.betterbatterystats (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10224 Sys: (0 s) Us: (0 s) Starts: 1======================Alarms (requires root)======================android (): Wakeups: 45 Alarms: 0, Intent: android.intent.action.TIME_TICK Alarms: 0, Intent: com.android.server.ThrottleManager.action.POLL Alarms: 1, Intent: com.android.internal.policy.impl.Keyguard.LANDSCAPE_WAKE_TIME_LIMIT_EXPIRED Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL Alarms: 13, Intent: android.appwidget.action.APPWIDGET_UPDATE Alarms: 13, Intent: android.appwidget.action.APPWIDGET_UPDATE Alarms: 0, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD Alarms: 0, Intent: edm.intent.action.elm.cleanrecords Alarms: 1, Intent: com.android.server.BatteryService.action.DORMANT_START Alarms: 1, Intent: com.android.server.BatteryService.action.DORMANT_END Alarms: 0, Intent: android.content.syncmanager.SYNC_ALARMcom.google.android.gsf (): Wakeups: 22 Alarms: 21, Intent: {com.google.android.gsf Alarms: 1, Intent: com.google.android.intent.action.SEND_IDLE Alarms: 0, Intent: com.google.android.intent.action.GTALK_RECONNECT Alarms: 0, Intent: com.google.android.intent.action.MCS_HEARTBEATcom.google.android.gms (): Wakeups: 2 Alarms: 1, Intent: com.google.android.intent.action.SEND_IDLE Alarms: 0, Intent: {com.google.android.gms Alarms: 0, Intent: {com.google.android.gms Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCEcom.android.systemui (): Wakeups: 2 Alarms: 2, Intent: android.intent.action.DORMANT_MODE_UPDATEcom.sec.esdk.elm (): Wakeups: 1 Alarms: 1, Intent: com.sec.esdk.elm.alarm.SAVE_APICALLLOG======================Network (requires root)================================CPU States==========384 MHz (): 1 m 34 s 0,2%486 MHz (): 3 s 0,0%594 MHz (): 1 s 0,0%702 MHz (): 2 s 0,0%810 MHz (): 7 s 0,0%918 MHz (): 1 s 0,0%1,03 GHz (): 1 s 0,0%1,13 GHz (): 2 s 0,0%1,19 GHz (): 48 s 0,1%Deep Sleep (): 10 h 35 m 51 s 99,6%========Services========Active since: The time when the service was first made active, either by someone starting or binding to it.Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.htmlcom.android.phone (com.android.phone.TelephonyDebugService) Active since: 31 s Last activity: 31 s Crash count:0com.google.process.gapps (com.google.android.gms.gcm.GcmService) Active since: 42 s Last activity: 1 h 5 m 18 s Crash count:0system (com.android.server.DrmEventService) Active since: 44 s Last activity: 44 s Crash count:0com.android.bluetooth (com.android.bluetooth.pan.PanService) Active since: 23 s Last activity: 9 m 13 s Crash count:0com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkServiceProxy) Active since: 6 m 28 s Last activity: 1 h 5 m 17 s Crash count:0com.sec.android.app.keyguard (com.sec.android.app.keyguard.KeyguardClockWidgetService) Active since: 1 m 28 s Last activity: 2 h 29 m 7 s Crash count:0com.android.bluetooth (com.android.bluetooth.a2dp.A2dpService) Active since: 36 s Last activity: 36 s Crash count:0com.android.systemui (com.android.systemui.SystemUIService) Active since: 28 s Last activity: 28 s Crash count:0com.android.phone (com.sec.enterprise.mdm.services.simpin.EnterpriseSimPin) Active since: 33 s Last activity: 33 s Crash count:0com.samsung.android.providers.context (com.samsung.android.providers.context.ContextService) Active since: 45 s Last activity: 45 s Crash count:0com.touchtype.swiftkey (com.touchtype.KeyboardService) Active since: 1 m 49 s Last activity: 1 h 4 m 7 s Crash count:0com.android.phone (com.sec.android.app.bluetoothtest.BluetoothBDTestService) Active since: 45 s Last activity: 45 s Crash count:0com.google.process.location (com.google.android.location.geocode.GeocodeService) Active since: 31 s Last activity: 31 s Crash count:0com.qihoo.security (com.qihoo.security.service.SecurityService) Active since: 43 s Last activity: 43 s Crash count:0com.android.systemui (com.android.systemui.ImageWallpaper) Active since: 29 s Last activity: 29 s Crash count:0com.maxmpz.audioplayer (com.maxmpz.audioplayer.player.PlayerService) Active since: 2 h 59 m 47 s Last activity: 2 h 5 m 13 s Crash count:0com.android.phone (com.android.phone.BluetoothPhoneService) Active since: 31 s Last activity: 31 s Crash count:0com.sec.enterprise.mdm.services.sysscope:remote (com.sec.enterprise.mdm.services.sysscope.EnterpriseSysScope) Active since: 30 s Last activity: 30 s Crash count:0com.sec.esdk.elm (com.sec.esdk.elm.service.ElmAgentService) Active since: 46 s Last activity: 2 h 30 m 5 s Crash count:0com.google.process.location (com.google.android.location.internal.GoogleLocationManagerService) Active since: 43 s Last activity: 44 s Crash count:0com.android.bluetooth (com.android.bluetooth.pbap.BluetoothPbapService) Active since: 2 m 34 s Last activity: 2 m 6 s Crash count:0com.fmm.dm (com.fmm.dm.XDMService) Active since: 37 s Last activity: 2 h 3 m 13 s Crash count:0com.android.location.fused (com.android.location.fused.FusedLocationService) Active since: 30 s Last activity: 30 s Crash count:0com.sec.enterprise.mdm.services.vpn:remote (com.sec.enterprise.mdm.services.vpn.EnterpriseVpnAnyconnect) Active since: 35 s Last activity: 35 s Crash count:0com.google.android.gms (com.google.android.gms.playlog.service.PlayLogBrokerService) Active since: 43 s Last activity: 2 h 30 m 41 s Crash count:0com.android.phone (com.android.phone.BluetoothVoIPService) Active since: 31 s Last activity: 31 s Crash count:0com.sec.phone (com.sec.phone.SecPhoneService) Active since: 43 s Last activity: 2 h 3 m 23 s Crash count:0com.google.process.location (com.google.android.location.NetworkLocationService) Active since: 30 s Last activity: 30 s Crash count:0com.google.process.location (com.google.android.location.fused.NlpLocationReceiverService) Active since: 43 s Last activity: 43 s Crash count:0com.teslacoilsw.notifier (com.teslacoilsw.notifier.NotificationService) Active since: 4 h 33 m 44 s Last activity: 2 h 31 m 27 s Crash count:0com.wssyncmldm (com.wssyncmldm.XDMService) Active since: 1 m 20 s Last activity: 2 h 5 m 33 s Crash count:0org.simalliance.openmobileapi.service:remote (org.simalliance.openmobileapi.service.SmartcardService) Active since: 30 s Last activity: 52 s Crash count:0com.vlingo.midas (com.vlingo.core.internal.safereader.SafeReaderService) Active since: 1 m 17 s Last activity: 2 h 3 m 34 s Crash count:0com.google.process.location (com.google.android.location.internal.server.NetworkLocationService) Active since: 32 s Last activity: 32 s Crash count:0com.touchtype.swiftkey (com.touchtype_fluency.service.FluencyServiceImpl) Active since: 1 m 50 s Last activity: 1 m 22 s Crash count:0com.sec.android.daemonapp (com.sec.android.daemonapp.ap.yahoostock.stockclock.activity.DaemonService) Active since: 1 m 21 s Last activity: 2 h 8 m 13 s Crash count:0com.qihoo.security (com.qihoo.security.locale.LocaleManagerService) Active since: 43 s Last activity: 18 m 56 s Crash count:0com.sec.android.pagebuddynotisvc (com.sec.android.pagebuddynotisvc.PageBuddyNotiSvc) Active since: 1 m 17 s Last activity: 49 s Crash count:0com.android.phone (com.samsung.sec.android.application.csc.CscUpdateService) Active since: 45 s Last activity: 1 m 38 s Crash count:0com.android.phone (com.android.stk.StkAppService) Active since: 1 m 20 s Last activity: 52 s Crash count:0com.android.nfc:handover (com.android.nfc.handover.HandoverService) Active since: 30 s Last activity: 30 s Crash count:0system (com.google.android.backup.BackupTransportService) Active since: 25 s Last activity: 25 s Crash count:0com.mapfactor.navigator:Notifications (com.mapfactor.navigator.notifications.NotificationsService) Active since: 1 m 49 s Last activity: 2 h 31 m 27 s Crash count:0com.google.process.location (com.google.android.location.reporting.service.DispatchingService) Active since: 42 s Last activity: 3 m 14 s Crash count:0com.oasisfeng.greenify:service (com.oasisfeng.greenify.CleanerService) Active since: 1 m 24 s Last activity: 2 h 31 m 19 s Crash count:0com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService) Active since: 6 m 28 s Last activity: 20 m 7 s Crash count:0org.zooper.zwpro (org.zooper.zwlib.UpdateService) Active since: 1 m 30 s Last activity: 2 h 31 m 22 s Crash count:0com.android.bluetooth (com.android.bluetooth.hfp.HeadsetService) Active since: 31 s Last activity: 36 s Crash count:0com.maxmpz.audioplayer (com.maxmpz.audioplayer.widgetpackcommon.WidgetUpdaterService) Active since: 2 h 59 m 47 s Last activity: 2 h 5 m 14 s Crash count:0==================Reference overview==================ref_boot: Reference ref_boot created 1 m 29 s (Wl: 10 elements; KWl: 7elements; NetS: 0 elements; Alrm: 1 elements; Proc: 6 elements; Oth: 4 elements; CPU: 10 elements)ref_unplugged: Reference ref_unplugged created 4 h 33 m 30 s (Wl: 1 elements; KWl: 20elements; NetS: 22 elements; Alrm: 6 elements; Proc: 0 elements; Oth: 6 elements; CPU: 10 elements)ref_charged: Reference ref_charged created 4 h 33 m 30 s (Wl: 1 elements; KWl: 20elements; NetS: 22 elements; Alrm: 6 elements; Proc: 0 elements; Oth: 6 elements; CPU: 10 elements)ref_custom: Reference ref_

Share this post


Link to post
Share on other sites

This *temp wakelock is temporarily (with automatical time-out) wakelock used for Android event handling, such as hardware buttons presses, pause on calls, etc.

It has 5s to 30s range, so after max. 30 seconds it automatically goes away (30 seconds is in case of incoming call).

 

Thanks!

Share this post


Link to post
Share on other sites

Thanks, but this doesn't help much.

Can i disable the service completely? I checked all my bbs logs, but i've never had any com.maxmpz.audioplayer.player.PlayerService temp (UID) calls in it until last weekend.

I love Poweramp, but i have to say i hate this kind of apps that violate my phone in this way.

If you take a look at my log, you see the bbs log was taken when i was asleep, so no reason for Poweramp to do ANYTHING on my phone. I mean Poweramp kept my phone awake 39s of 162s. Thats about 24% of the awake time for what reason?

Anyway, i have a two step solution to regain control of my battery again:

- Disable all scanning activity. That seems to reduce the wake time of the service to a minimum.

- Greenify Poweramp.

With this solution the wakelock is gone and i have no side effects by now. If i want to hear music, i open Poweramp. If i don't want to hear music, i close Poweramp. And if Poweramp is closed and no music is playing, there is no need that it consumes even 0.1% of my battery. It simply has to stay out of my phones memory until i need it again.

Regards!

Share this post


Link to post
Share on other sites

Sorry, but I don't see anything wrong with the behavior you're describing (e.g. keeping phone awake when needed).

 

Poweramp uses (partial - e.g. no screen on) wakes locks where it's absolutely required for Poweramp functionality - e.g. if you remove this wake lock, there will be a clear bug, and people don't generally like bugs ))) --  e.g. Poweramp won't resume after call/notification, won't resume on buttons press, won't scan files when screen is off, or do other expected functionality).

 

Thanks!

Share this post


Link to post
Share on other sites

Thank you Max!

Beside the side effects (which i think i can really live with), how can you explain, why the process never occures in my log over a time span from 2 months? So, was it there before, but not logged in bbs? Or wasn't it there? I an 100% sure i never had this wakelock before this weekend and i can prove it with a lot of bbs logs, believe me. Where, all of a sudden, this thing comes crawling in my logs? And why, all of a sudden, it consumes a hell lot of my battery?

Greetings.

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.

Sign in to follow this  

×
×
  • Create New...