Jump to content

papete

Approved Members
  • Content Count

    43
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Gallery

Downloads

Knowledge Base

База знаний

知识库

Everything posted by papete

  1. I think you have you have your answer in your question. Why don't you set a variable where you extract the playlist info from the track changed intent?
  2. I think I posted in the wrong place so I'm starting a new thread. I used to use the search API command with Tasker using this action: Send Intent [ Action:com.maxmpz.audioplayer.API_COMMAND Cat:None  Mime Type: Data:content://com.maxmpz.audioplayer.data/files?flt=search string  Extra: cmd:20 Extra: Package: Class: Target:Service ] It used to work like a charm, but since I don't know when this command does not work anymore. I checked the API documentation and it seems that the command changed. Accordingly, I updated my Tasker action to the following: Send Intent [ Action:com.maxmpz.audioplayer.API_COMMAND Cat:None  Mime Type: Data:content://com.maxmpz.audioplayer.data/search?flt=search string  Extra: cmd:20 Extra: Package: Class: Target:Service ] But the above command does nothing. Looking at the forums, I found that I can use an Android intent for the same purpose: Send Intent [ Action:android.media.action.MEDIA_PLAY_FROM_SEARCH Cat:None  Mime Type: Data:  Extra: query: YOUR SEARCH STRING HERE Extra: android.intent.extra.user_query: shuffle Package: com.maxmpz.audioplayer Class: com.maxmpz.audioplayer.ListActivity Target:Activity ] And the above intent works, however it is way slower and does bring Poweramp to the front, which is a behavior that I don't want for the situation I'll be using it (while driving). Is the native Poweramp API search command not working or am I doing something wrong? Thanks
  3. Hi Max, I tried this and it works, however, if I try the Poweramp API method, nothing happens. The intent I'm using is this: Send Intent [ Action:com.maxmpz.audioplayer.API_COMMAND Cat:None  Mime Type: Data: content://com.maxmpz.audioplayer.data/search?flt= search string Extra: cmd:20 Extra: Package: Class: Target:Service ] What am I doing wrong?? Thanks Edit: it used to work in the past with Data:content://com.maxmpz.audioplayer.data/files?flt=search string
  4. Thanks max, actually after I found the direct SQL read method this method was mentioned in the reddit post I opened looking for help. Thanks a lot for such a complete api!!
  5. Posting here too as this is the most appropriate thread... OK, I figured out the way to get the Poweramp playlist IDs with Tasker. It only works with a rooted device: use the SQL query action. Mode: raw, file:/data/data/com.maxmpz.audioplayer/databases/folders.db Query: SELECT _id, playlist FROM playlists This action will return an array with the playlists names and id’s. Remember to check root on the action to work.
  6. OK, I figured out the way to get the Poweramp playlist IDs with Tasker. It only works with a rooted device: use the SQL query action. Mode: raw, file:/data/data/com.maxmpz.audioplayer/databases/folders.db Query: SELECT _id, playlist FROM playlists This action will return an array with the playlists names and id’s. Remember to check root on the action to work.
  7. @flyingdutchman in my case I just need an automated way to get the playlists ID's. Ideally, I would send an intent to your app and your app would broadcast an intent that Tasker can listen to, and receive an array or comma separated list of playlists names and id's. For the folders, something similar could work, but it is not a priority for me. Also a file could be generated, it is not ideal but it would work too, as Tasker can read the file and get the info required.
  8. Really? Wow thanks. Tell me what should I do to get this working and/or help in the process of testing
  9. Hello flyngdutchman, thanks a lot for your answer. What I’m looking for is a process without any human intervention. An intent to query the playlists would be sent to either your app or Poweramp, and in return Tasker would receive an array with the playlists names and probably a different intent to receive an array with the Poweramp IDs. Can I achieve this with your app?
  10. I don't know if it can be done, but right now to play a playlist I use Tasker with the following in the data field: content://com.maxmpz.audioplayer.data/playlists/##/files Where ## is the number Poweramp assigned the playlist. I have to find this number by trial and error. It would be nice if there were an intent that would return something like an array with all the playlists names with their corresponding Poweramp ids.
  11. Tag edit of streams causes app to force close on Android Pie. Report sent to Max already
  12. I don't know if it has been reported, I'm on latest beta and the Poweramp notification is gone. Everything is working well except that no Poweramp notification is shown. I tried changing notification type to legacy, etc but no luck. I'm running stock Android P on an Asus Zenfone 6.
  13. Thanks, I thought the upgrade broke something... I don't know why but the upgrade moved my playlist numbers... Found them and working again
  14. Since 805 I can not use com.maxmpz.audioplayer.API_COMMAND Data:content://com.maxmpz.audioplayer.data/playlists/#/files To play playlists. Was working fine before
  15. Rowan, is this working for you? Since 805 (I think) it is not working for me...
  16. Thanks Rowan! Works like a charm. It would have been useful to get the currently playing playlist info, but this works for my needs. Thanks again!
  17. I'm interested in this Rowan. Could you post the actions to achieve this? Regards, Manuel
  18. This was asked at the 792 thread but was lost in the flood of comments. Do we have an API documentation available for 792?
  19. Do we have api documentation available for this beta?
  20. For once? After 2 years with non met dev issued deadlines you have the nerve to say "for once". In my case I'm not waiting for it simply because I don't believe dev's deadlines anymore. But I can clearly understand the tension of some, specially now that the stable version is not even running properly on new devices.
  21. The problem is that 3.0 is getting into a vicious cycle. App is almost ready but delayed to fix bugs on a few phones, then new Android system is out, rework has to be done, app is delayed to fix bugs on a few phones, then new Android system is out, rewor…
×
×
  • Create New...