Search the Community
Showing results for tags '802'.
As a battery-optimization nerd, I keep track of what apps run in the background, and how much RAM they use. In PA v3, I've noticed a repeatable scenario where the PA process RAM usage skyrockets. To convey why this is a realistic issue for me, I must explain that I listen to music "freestyle", one track at a time. I think, "I'll listen to that song now," then I search for and find it. "Now that one." Search, find. Search, find. So with this "search, find" approach to listening, I've noticed that the longer I listen, the larger the PA process becomes - consistently. With my settings, PA starts out about 45-50MB. To test and illustrate how high I could get the process, I spent about 4 minutes of intentionally "search, find"-ing. I made it over 130MB, by simply accelerating the way I do a listening session. About triple RAM usage (see screenshots) I experience a similar climb when going in and out of PA settings to change/check things. If I just start a list and let it play (without "search, find"), the RAM doesn't climb much, if at all. I realize RAM usage doesn't always directly reflect battery usage... but still. Just thought I'd point it out in case this is not intentional/desired behavior for the app. Moto E4 Plus, Android 7.1.1, PA 802 & 803 last.Poweramp-settings (Many competing music apps start OUT at the 130MB-ish mark. PA is awesome - for music lovers, AND battery lovers.) EDIT: Just noticed weirdly that Wear OS went BACK in time between the screenshots... The screenshots are genuine, though.
Almost every time I resume playback after pausing, there is a single, tiny pop mixed into the music a split second after resuming. It's not very loud, but definitely present. This originally happened over a Bluetooth speaker, but I just tested for it over wired headphones and got the same result. Oddly and specifically enough, the glitch often sounds more like a pop when pausing/resuming using controls on the BT speaker/headphones, but sounds more like a tiny skip when using PA's own pause/resume button. I never noticed this glitch before recently turning off "Beep" in PA's Bluetooth settings, but after turning "Beep" back on, I can definitely still hear it (right AFTER the beep), so they don't seem related. While writing this, I just noticed that the glitch is also present while manually seeking through a track (I'm using Static Seekbar). Moto E4 Plus, Android 7.1.1, PA 801 & 802 last.poweramp-settings
Version: v3-build-802-play Note: I've already turned on "Auto-Advance From Queue". Problem: After one queue has finished on playing it's last track, Poweramp starts the queue again, and does not return to the playlist where I started from. Hypothesis: This issue is likely to be caused as Poweramp treats queues as playlists and uses the same Repeat & Shuffling settings from the previous playlist. Possible Solution: If possible, please let Poweramp remember those Repeat & Shuffling settings independently for queues. Thanks!