• Announcements

    • andrewilley

      Poweramp v3 Beta-test Build 790 Now Released   04/29/2018

      Poweramp v3 BETA TEST preview build 790, including brand new user interface, has now been released - 30 April 2018. This is not quite feature-complete yet, so only install if you are happy to test with a slightly reduced set of options.  Missing features should be completed during May. Please report any issues in the testing forum thread, and remember to backup your previous build before testing.  


  • Content count

  • Joined

  • Last visited

About andrewilley

  • Rank
    Forum Moderator
  • Birthday 09/26/1962

Profile Information

  • Gender
  • Location
    Birmingham UK

Recent Profile Visitors

75,019 profile views
  1. Just disable autoupdates for the app in the Play Store. And turn beta testing mode off in Store too. Andre
  2. Presumably the main OS does not support high-res, but the extensions added by the audio effects package do. What is the audio_policy.conf file on your device with just the basic ROM? Andre
  3. As far as I know, it's meant to be fixed in the latest test releases (e.g. build 709). Andre
  4. If you didn't clean-format your memory card, it might be an idea to do that (note: internal playlists may be cleared if you do this, as the card might read as a 'new' storage location with new songs on it, so export any internal playlists to real files first). Also worth increasing the buffer and/or audio priority settings in PA. Andre
  5. Looks OK on my test device. You can turn that element off if it's bothering you - PA Settings > Audio > Advanced Tweaks > Volume Panel. Andre
  6. That's what "not yet feature-complete" means. Please read the message from where you downloaded the beta-test file: Andre
  7. That audio policy file doesn't list anything beyond 48000 as being available for your device (on that ROM at least). Andre
  8. From the Downloads tab at the top of the page (or from Google Play if you disable the beta-test option). Yes, the Google Play unlocker will work with either a Play store download or a download from the website here. Andre
  9. Max said he had restored Android 4.3 - 4.4 compatibility for build 709, but didn't mention anything prior to that. I would suggest uninstalling completely and installing the normal release build 588 which is intended to be retained for legacy devices. Andre
  10. I believe so, yes, as Max said there were datebase changes. I think you have to uninstall and then reinstall the previous version. You can export settings and Playlists before you roll-back though (I'm assuming you didn't back up the old version before updating to the beta?) Andre
  11. @maxmp Quite a lot of users report that they see an issue of PA working normally for a long time but suddenly not working on flights/etc (a number in this thread even, for example http://forum.powerampapp.com/topic/9335-why-does-poweramp-need-to-verify-license-through-google-play-when-poweramp-unlocker-is-installed/?do=findComment&comment=47594 ). In the FAQ, you state that once a licence has been validated it is never checked again - apart from if the app is reinstalled, the ROM is updated, or the system is reset (by which the assumption is that you mean a full factory reset, not just a regular power-cycle reboot such as would be done routinely during take-off of a flight for example). That's what I've been telling users anyway, but it doesn't always seem to be the way it works out there in the real world. There would appear to be too many reports of this happening inexplicably for everyone to be wrong. Could you perhaps clarify what you mean by never checked again? Andre
  12. You don't say which build, but basically you need to tap the EQ (v708) or Visualisation (v790) icon, and select Disabled rather than 'Normal' or 'Full Screen'. Andre
  13. See this thread, EMUI does seem to have some issues with lockscreen controls. Search the forums for EMUI pops up a few threads. Andre
  14. No Idea, what ROM are you running - stock or modified? Andre
  15. You won't ever be able to use old Poweamp v2 skins on a v3 release. Once v3 skin support is enabled, you will need to wait until third-party developers start to issue newly written skins for v3. Andre