Xian55 Posted November 23, 2018 Share Posted November 23, 2018 Dear Developers! i would like to report a bug about the Poweramp. I've tested it with and without "Use Wakelock" and "Keep Service". Worth to mention i gave full permission access to Poweramp what MIUI permission app is shown. Im using Xiamo Mi Mix 2S with MIUI global 10.0 | Stable 10.0.4.0(PDGMIFH) Android Version 9 PKQ1.180729.001 I've starting the music while the screen is active. Then lock the screen and about exactly 60 second of off screen play the music suddenly stops. Can't resume the music via headset buttons. Without headset the problem still occurs. At the end i can't use the app to listen to music. I've managed to extract the log: 11-23 13:15:38.428 1365 8191 W ActivityManager: Background start not allowed: service Intent { cmp=com.maxmpz.audioplayer/.player.HeadsetMicroService } to com.maxmpz.audioplayer/.player.HeadsetMicroService from pid=8179 uid=10147 pkg=com.maxmpz.audioplayer startFg?=false 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.maxmpz.audioplayer/.player.HeadsetMicroService }: app is in background uid UidRecord{aa29f17 u0a147 SVC bg:+1m0s216ms idle change:idle procs:1 seq(0,0,0)} 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1587) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at android.app.ContextImpl.startService(ContextImpl.java:1542) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at android.content.ContextWrapper.startService(ContextWrapper.java:674) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at com.maxmpz.audioplayer.player.HeadsetMicroService.null(":34) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at com.maxmpz.audioplayer.player.PlayerService.onDestroy(":2519) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at android.app.ActivityThread.handleStopService(ActivityThread.java:3733) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at android.app.ActivityThread.access$1800(ActivityThread.java:200) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1709) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at android.os.Handler.dispatchMessage(Handler.java:106) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at android.os.Looper.loop(Looper.java:193) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at android.app.ActivityThread.main(ActivityThread.java:6806) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at java.lang.reflect.Method.invoke(Native Method) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547) 11-23 13:15:38.429 8179 8179 W HeadsetMicroService: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873) 11-23 13:15:38.433 1365 6233 D MediaSessionService: Media button session is changed to null 11-23 13:15:38.433 1365 2872 I MediaFocusControl: abandonAudioFocus() from uid/pid 10147/8179 clientId=android.media.AudioManager@7c815bfcom.maxmpz.audioplayer.player.PlayerService$11@bcdd51c 11-23 13:15:38.435 8179 8179 W PlayerService: Poweramp Player Service leaves the scene Link to comment Share on other sites More sharing options...
maxmp Posted November 23, 2018 Share Posted November 23, 2018 Thanks for the report, but this is by design (of Android 8.0+). On Android 8 microservice works more-or-less only after Poweramp UI was successfully started once and it still can be killed later, esp. on devices with aggressive non-standard task killers (e.g. all chinese brands). Link to comment Share on other sites More sharing options...
Xian55 Posted November 24, 2018 Author Share Posted November 24, 2018 After your response it was not clear for me. If you can fix this behaviour, how long shall i wait for the update ? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.