Jump to content


Approved Members
  • Content Count

  • Joined

  • Last visited

About Phrosh

  • Rank

Recent Profile Visitors

586 profile views
  1. Try to use build 70x (Okay, I should put this in the initial post by now... :D) Wow, this just worked. Big thx
  2. Try using Poweramp 79x When you are in the music section of AA, tap on the music icon again and you can re-select your music app. This is general AA behavior. I stop the music when AA quits, but I don't disconnect BT or anything like that. As far as I know, I don't even use BT permissions. I can't tell why you have these problems, sorry. When the dev options and unknown sources are not enabled, nothing will change. Use Google. To log in to this forum, I ALWAYS have to trigger the "forgot password" function, so I don't always have the time to answer everything ri
  3. Again, this would force the app to appear in the app drawer. You might set a tasker profile to the launch of PowerampAuto itself and change the volume back to 100%. Just the first quick fix that came into my mind . The only reason, I decided not to use max volume is that Google Maps / TTS voice was distorted when I used maximum media volume. I thought this might have an impact on other devices / cars as well. My app only operates within Android Auto and thus can not randomly start itself. Maybe your Android Auto starts in the middle of the night? Does someone use your
  4. Haha, nevermind . We'll find someone with 797 soon enough, I guess . Yes, this is done on purpose - so you don't have to bother with the "internal" phone volume when e.g. your music was quiet before, you turn up the master volume and suddenly your navigation shouts in your face . It's set to 75% (to prevent distortion by overdrive) and the original volume should be restored when you quit AndroidAuto.
  5. So... 1.0.2 *should* work with both APIs. Still not tested with the new one, but as @flyingdutchman found out, the main difference is the change in table names (which is basically your logcat) so I added a try-catch to support both APIs. Let me know if it worked ^^
  6. Not yet, but I'll think about it
  7. Yup, try downgrading to 709 - Since the new version erased a 1000+ entry playlist of mine I am very cautious with the new releases and can not test the "new API" properly. I will TitaniumBackup the hell out of Poweramp and come back to this, supporting 797+. Disappearing buttons also seem an issue of intents not being properly received by the API... Thx for the logcat - My avatar likes it
  8. With the option to keep the service alive, I don't think that I need to start Poweramp at all - so I postponed the options panel to when it is really needed and just removed the part where Poweramp is automatically launched. Enjoy the new release, @fatal
  9. Thanks Actually, I did this on purpose to ensure Poweramp is running when using AA. Most of the users will use AA within their car entertainment system so the opening Poweramp app won't bother them. Maybe I could include a settings screen where you can configure the behavior of Poweramp Auto, but then it will definitely be shown in the app drawer...
  10. I don't use the widget but I certainly experienced everything else you mentioned. 2) can confirm. 3) it just wiped a >1000 song .m3u playlist by just selecting it to be played. This happened not only once. 4) also confirmed, very annoying 6) yes, it should 7) I also share your opinion Everything, using a Sony Xperia XZ Compact on Oreo (Lineage)
  11. It's still called v3 here everywhere ;). No, you are not alone with this - I have the same issue and probably anyone else using the Poweramp API. It is caused by the new Poweramp update, not the Android Auto update. Unfortunately I can't do anything about this, because of the changes made to the app. I made a post about this issue in this thread, where everyone else also complains about the buggyness of the new release ^^. This issue - and the fact that playlist shuffle does not seem to work anymore (which is even more annoying, when you sit in your car and can not skip tracks anymor
  12. - Shuffle does not seem to work anymore (at least not in an m3u playlist, did not try anything else) - intents are not fired anymore, so the API is pretty much useless now - an even smaller list grid size would be awesome
  13. Hey, thank you mate Yes, this would be possible. But Android Auto does not provide a search bar or similar feature in a "media" Auto app and you would have to manually scroll through all your artists / albums. I thought scrolling through artists and albums while driving could be way too dangerous, so I decided to only include playlists into the menu. And if you just want to search for some stuff to listen to while not moving, you are always faster to grab your phone and search in Poweramp itself. @freewee: Oh, I did not know that this is a new feature. Edited my post - t
  14. After months of trying to get my app into the Play Store I finally gave up and posted the .apk here - just to see a few hours later someone else got the same idea and uploaded it in the meantime . Well done . If you like to check out my bridge as well, you are free to do so
  15. This is a bridge to enable support for Poweramp in Android Auto. To make Poweramp visible in Android Auto you need to enter the developer settings in Android Auto and enable "unknown sources": https://9to5google.com/2018/01/12/how-to-enable-android-auto-developer-settings-android-basics Please enable "Alyways Process Album Art" in the Poweramp Settings > Album Cover (feature of Poweramp v3) to ensure the correct album art is shown when the device is in sleep mode. Use Poweramp Build 709 for best support. Anything above might fail. Key features: - Playback control (no s
  • Create New...