Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange behavior when connected to car bluetooth #1619

Closed
2 tasks done
nate2014jatc opened this issue Aug 22, 2018 · 20 comments
Closed
2 tasks done

Strange behavior when connected to car bluetooth #1619

nate2014jatc opened this issue Aug 22, 2018 · 20 comments
Labels
bug Issue is related to a bug

Comments

@nate2014jatc
Copy link

HI,
Whenever my phone connects to my car's Bluetooth, newpipe spawns a player on its own, that tries to play literally nothing. I can't pause the "playback" and when I kill the player notification, it immediately comes back until I disconnect my phone from my car manually.

@FunctionalHacker
Copy link

FunctionalHacker commented Aug 28, 2018

Do you by chance have a Xiaomi Roidmi bluetooth adapter? I had this same problem and after I removed the Roidmi app, this behaviour disappeared.

@nate2014jatc
Copy link
Author

nate2014jatc commented Aug 28, 2018 via email

@brimston3
Copy link

I get this behavior as well, but it's probably not a NewPipe issue per se. On connect, the last media player I had playing is launched and audio is started from that software (eg, vlc, pocketcasts resumes playback). In the case of NewPipe, the background player launches, but it shows "unknown" as the track info. Mine, on the other hand, does not try to relaunch if I close the newpipe notification -- my guess at @nate2014jatc's issue is buggy AVRCP behavior by the bluetooth sink.

@nate2014jatc
Copy link
Author

nate2014jatc commented Sep 7, 2018 via email

@theScrabi theScrabi added the bug Issue is related to a bug label Sep 7, 2018
@theScrabi
Copy link
Member

Noticed this as well. We need to fix it.

@nate2014jatc
Copy link
Author

Is AVRCP bug likely to be on the OS side or the receiver side?(if that does end up being the issue)

@theScrabi
Copy link
Member

Its propably newpipe itself.

@TaranQ
Copy link

TaranQ commented Sep 15, 2018

Same problem over here Newpipe starts as soon as bluetooth connection to car is made.

@theScrabi
Copy link
Member

But stearing and brakes still work? 🤔

@stale
Copy link

stale bot commented Dec 1, 2018

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.

@stale stale bot added the stale label Dec 1, 2018
@nate2014jatc
Copy link
Author

-cough cough?-

@stale stale bot removed the stale label Dec 2, 2018
@NeoFromMatrix
Copy link

same behavior with moto g5 android 8.1

@jjtParadox
Copy link

I have this same "empty playlist notification" issue with my own phones and Bluetooth devices. This issue does not come up if another media app (i.e. Spotify) is open (either on screen or has a player notification)

@skontar
Copy link

skontar commented Nov 12, 2019

I have the same problem with Samsung A40 and Samsung S10e when they connect to my car Bluetooth. Does not happen with other Bluetooth devices (and any other players for that matter). Anything I can help with?

@Liknus
Copy link

Liknus commented Mar 10, 2020

Same problem: as soon as my OnePlus 6 connect to the Sync2 of my Ford I get an empty notification..
Newpipe v.0.18.4 on Android 10..

@Offerel
Copy link

Offerel commented Apr 29, 2020

I can confirm that behavior on a Galaxy S9 with Android 10. The last audio app is Media Monkey. But when it connected to the car BT, always NewPipe take control. It would be nice, if we could get an option, where we could disable automatic react to BT connects. I have no other idea if there is a workaround

@wb9688
Copy link
Contributor

wb9688 commented Apr 29, 2020

@Offerel: Could you test whether #3178 fixes it by any chance?

@Offerel
Copy link

Offerel commented May 1, 2020

@wb9688 i have re-tested it today with the actual release version an the commit from above. I cant reproduce it either. The issue seems to be gone, after i removed the default associations from all involved apps. After that, i re-added the associations, but the problem seems to be disappeared.

@Stypox Stypox linked a pull request May 2, 2020 that will close this issue
1 task
@Stypox
Copy link
Member

Stypox commented May 17, 2020

Duplicate of #1574

@Stypox Stypox marked this as a duplicate of #1574 May 17, 2020
@Stypox Stypox closed this as completed May 17, 2020
@Stypox Stypox removed a link to a pull request Aug 12, 2020
1 task
@amosnet
Copy link

amosnet commented Dec 30, 2020

I have the same problem with Samsung A40 and Samsung S10e when they connect to my car Bluetooth. Does not happen with other Bluetooth devices (and any other players for that matter). Anything I can help with?

It's been more than a year and the same thing is still there with my Samsung S10, only when it connects to the car, pretty weird.

Not sure if it is affected only to Samsungs when they connect to cars.


NewPipe 0.20.8 (Dec. 27th, 2020)
Samsung S10, Android 10.
bmw NBT stereo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue is related to a bug
Projects
None yet
Development

No branches or pull requests