-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[BUG] Bluetooth device not discovered by LE settings on WeTek Play2 #8900
Comments
While issue seems a clone of Realtek firmware missing #8853 It goes without saying one expect native Bluetooth dongle to be supported by native Wetek Play 2 image. Didn't try LE11 WeTek Play2 build yet. |
Please test following #8853 (comment) if it works then this will be closed with #8853 |
LE includes the firmware and the device/driver is probed and working from the console:
and the card is active:
However LE settings does indeed show "No Bluetooth device found." so I'm wondering if we have an issue with the d-bus agent or however else the device is detected? TL/DR: the workaround will be to pair/connect things using |
Thank you for checking. Will try the workaround via SSH, but can’t tell my parents to pair headphones that way. Lucky me, @chewitt has his old Play 2 unit :) |
Out of curiosity I got TP-Link UB500 USB dongle connected: On LE12 UB500 seems to work without extra drivers, yet Play2 add-on still shows “no device found”. LibreELEC:~ # dmesg | grep -i blue LibreELEC:~ # btmon
|
Describe the bug
Original Bluetooth module doesn't work on stock 12.0 WetekPlay2 firmware:
https://releases.libreelec.tv/LibreELEC-AMLGX.aarch64-12.0.0-wetek-play2.img.gz
"No Bluetooth device found"
How to reproduce
Steps to reproduce the behavior:
Information
https://wiki.libreelec.tv/hardware/amlogic/wetek-hub-play2
Log file
PasteKodi: https://paste.libreelec.tv/smooth-cod.log
dmesg output: https://paste.libreelec.tv/prompt-grouper.log
Context
Bluetooth original module inside the unit was working fine on latest CoreELEC 9.2.8 before LE12 clean install.
The text was updated successfully, but these errors were encountered: