Newpipe: Audio only player pops up when connected to bluetooth device

[xNS5]

Device: Samsung Galaxy S8+
OS: Latest update
Newpipe Version: Latest build

Issue: Whenever I connect to my car's bluetooth radio, the newpipe audio only player pops up as if it were my default media player (which it isn't).

I've tried clearing defaults, clearing cache, and everything I could think of.

[theScrabi]

Yea thats a known bug.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Offerel]

Is there some workaround for that issue?

[Rorschach1010]

Same here. Whenever I used Newpipe (after my default audio player) and get into my car, it doesn't start my audio player but newpipe and obviously, there is no music starting. I have to force close newpipe and start my default player. I'm running Android 10 btw.

Seeing that this is a pretty old bug, are there plans to get this fixed any time soon or as @Offerel asked, is there some kind of workaround?

[Stypox]

Does #3178 fix this issue? Could you test the apk provided there?

[Rorschach1010]

Does #3178 fix this issue? Could you test the apk provided there?

hmm... seems like the download link expired. I'll ask in #3178 if someone can share it.

[opusforlife2]

_Probably_ fixed by #2907.

[Stypox]

@xNS5 @Offerel @Rorschach1010 could you test this apk (from https://github.com/TeamNewPipe/NewPipe/pull/3178#issuecomment-667724810 )

[Offerel]

At least by testing with a headphone it works.

Update: after re-install the standard version, this also works. I fear I have to re-test it with the car audio also. I will report tomorrow.

[xNS5]

I don't use newpipe anymore because the issue was persisting, however I've installed Newpipe on my phone to see if the issue has been resolved. I'll do some testing tomorrow as well!

[Offerel]

It's me again. Re-test with car audio successfully. Hopefully this will be in the next release.

[xNS5]

Just following up. I tested it a bit and I'm unable to replicate the issue. It appears to have been resolved!