Jump to content


Approved Members
  • Content Count

  • Joined

  • Last visited

About smiller

  • Rank
  1. Ah, understood, thanks. Knowing this, in my case the easiest solution would probably be to simply eliminate any non-standard ASCII characters in filenames since the number of non-compliant files is not large. Thanks for the prompt response.
  2. I have entered a formal bug report on this but am mentioning it here in case anyone has any input. I have noticed that when importing .m3u playlists, any filename containing foreign characters will be skipped and not populated into the playlist. For example, if the filename contains Dvořák the file will be skipped during the playlist import scan, but simply changing the name to Dvorak will result in the file being properly included in the playlist. This is with v3-841on Android 10, but I have a suspicion that the bug is present on all versions. Has anyone else come up against this?
  3. Thanks for the response. I didn't see the other post, sorry for the duplicate request. I'll hope to see this option show up someday.
  4. Is there a way to prevent display timeout only while visualization is active? I realize that I can set the display to stay on while Poweramp is running, but the only time I really need it to stay on is when visualizations are active. Is there a way to do this without having to continuously toggle the global 'keep display on' setting? If not... seems like a worthwhile feature.
  5. As a followup, I tried another Android 9 phone and everything worked OK so I then uninstalled and reinstalled Poweramp v3-828 on the problem phone and it then worked as well, so apparently a complete reinstall of Poweramp cured the problem.
  6. Hi, I am using a known-working Poweramp Tasker task (Poweramp v3-828 and Android 7 on a Moto X Pure) on an Android 9 device (Pixel 3 XL) and am seeing it fail with the following Poweramp log entry: 21:27:57.318 PlayerService OPEN_TO_PLAY content://com.maxmpz.audioplayer.data/playlists/16/files?shf=2 IGNORED On the Android 7 device I see the same log entry, but without the 'IGNORED' on the end, and the command works properly (loads a playlist and starts playback.) Other than the OS everything is the same (same Tasker config, same Poweramp version, both restored from th
  7. In that case there is a minor bug in build 826. The long-press-to-skip option is absent from the 'Misc' menu (which apparently is correct since I am running Android 7.0 and thus the feature is unsupported), however the option is available under the Headset/Bluetooth menu, which sends you to the Misc menu, where it is missing. If the option is absent from the Misc menu on pre-8.0 phones (because it is not supported) then it should also be absent from the Headset/Bluetooth menu.
  8. My phone is not rooted and I don't believe that root is required for this permission (although unfortunately it looks as though Android 8.0 or above is ). To run the command you need to install the adb application on your PC and enable USB debugging on your phone. The process is a bit long to include in a post but there are many online tutorials available that describe the procedure. I'm not 100% certain that it is even required but there doesn't seem to be any documentation available on this new Poweramp feature so ...
  9. I'm on build 826 (Moto X Pure running Android 7.0) but I do not see the 'change track by long volume key press' option on the Misc menu or anywhere else (well, there is a selection in the Headset/Bluetooth menu for that function that in turn redirects me to the Misc menu, but again the option is not there.) I tried using the 'adb shell pm grant com.maxmpz.audioplayer android.permission SET_VOLUME_KEY_LONG_PRESS_LISTENER' command listed earlier in the thread but SET_VOLUME_KEY_LONG_PRESS_LISTENER does not appear to be a valid command as the attempt fails with: Bad argument: java.lang.Illeg
  10. I can confirm that Music Boss worked for me too, now have track selection ability with the Pebble back with v3! From what I read on the forum many/most smartwatch's control functionality (Garmin, etc., not just Pebble) is broken in v3 so hopefully they will eventually fix it for all.
  11. Thanks for this. I use a Pebble Classic mounted on my motorcycle to control music playback and have been unable to get track selection to work with v3. Given that the Pebble has been discontinued and all the other v3 development priorities I had assumed that there was near zero chance of getting v3 working with the Pebble anytime soon, if ever. I'll give Music Boss a try! If possible you might want to change the subject line of the thread to include 'Pebble' so other Pebble users can find it more easily.
  12. Thanks for the prompt response. I had tried deleting Android/data/_com.maxmpz.audioplayer prior to reinstall of v2 but there was no improvement, and was considering updating back to v3 and uninstalling as a next step but in the interim have possibly found the problem... it seems that Android 6.0 is installing Poweramp to my SD card by default (instead of internal device memory.) I have manually moved the Poweramp v2 main and unlocker app to internal memory and since then it has survived several reboots, so perhaps the issue is resolved. If this is in fact related to storage location it w
  13. I have determined that restarting the device will cause the Poweramp app to disappear. I can then reinstall the Poweramp app and it will work normally until the next power cycle, and after the device reboots the Poweramp app will be completely gone from the device (both the Poweramp trial and Full Version Unlocker apps are gone.). The behavior did not appear until after i joined and then left the alpha test so i believe the problem is related. Am I the only one who has experienced this? And since it is now repeatable at will are there any instructions from the developer as to how I might troub
  14. I entered the v3 alpha test program but was forced to leave due to the number of bugs at this point (not a complaint, just a statement.) Now after reverting back to V2 the Poweramp app disappears from the device after some random period of time and the only thing I can do to restore is a full reinstall (losing all of my settings and custom eq of course.) This has occurred three times now over that last two months (I have been unable to determine any specific condition that triggers it, the app just disappears.) I have tried completely deleting the app directory from the phone prior to a reinst
  15. I had to revert back to v2 since Bluetooth functionality is critical to me and as soon as I re-loaded v2 full functionality was restored, so the problem is definitely related to v3. I'd like to participate in the beta so I'll watch this thread and change logs to see when the bug has been resolved. When it is resolved if someone could note it in this thread I'd appreciate it.
  • Create New...