+- PINE64 (https://forum.pine64.org)
+-- Forum: PineTab (https://forum.pine64.org/forumdisplay.php?fid=140)
+--- Forum: General Discussion on PineTab (https://forum.pine64.org/forumdisplay.php?fid=141)
+--- Thread: PineTab Bluetooth (/showthread.php?tid=19260)
PineTab Bluetooth - PimpDiCaprio - 05-29-2024
Hello all,
I was wondering if anyone had a fix to the following problem I ran into when setting up WIFI and Bluetooth functionality on the PineTab. I got through the WIFI setup without issue and it works great, but when running the following to setup Bluetooth:
Code:
sudo pacman -S bluez-deprecated-tools
sudo -i
echo ifname:bt cmd:BT_ON > /dev/bes2600
rfkill unblock bluetooth
hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep
hciconfig hci0 up
exit
sudo systemctl enable bluetoothi run into an error right after running hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep
the error is as follows:
Code:
hciattch -s 1500000 /dev/ttyS1 any 1500000 flow nosleep
Can't get port settings: Input/output error
Can't initialize device: Input/output errorI did see the one resolution using UART but it did not work, plus the main use of setting up the Bluetooth was to use Bluetooth mouse and barcode scanner.
if anyone has a fix, or an idea when this may be fixed it would be greatly appreciated.
Kernel: 6.8.6-danctnix2-1-pinetab2
RE: PineTab Bluetooth - elix - 07-18-2024
I came here for the exact same issue. Any resolutions?
RE: PineTab Bluetooth - elix - 07-20-2024
(07-18-2024, 12:30 PM)elix Wrote: I came here for the exact same issue. Any resolutions?
I got a little further when I changed ttyS1 to ttyS2 but ended up getting a no device error when running the next command.
RE: PineTab Bluetooth - spaesani - 11-01-2024
I find the whole bluetooth issues ominous.
For one the bes2600 driver's source headers show
/*
* ..
* Copyright © 2022, Bestechnic
* ..
*/
Which means they wrote the driver
They being the makers and suppliers of the bes2600 module.
All of the commands in the op table except for powering on and off wifi and bluetooth
are not implemented.
What's of note is that the power on / off commands that are implemented use the sdio interface
and not the uart interface which is what is used to communicate with the bluetooth transceiver (except for powering on/off which uses sdio).
This means the driver does not talk at all to the uart. The bluetooth transceiver.
Which is strange since the module has a bluetooth transceiver on the uart interface and the driver, as mentioned,
is developed by the module supplier.
It seems they left it out on purpose.
From my research Linux uses Bluez for all things bluetooth and Linux can support bluetooth controllers
out of the box without 3rd party drivers. If this is true the driver not having any substantial bluetooth
implementation save for powering on and off the transceivers makes sense.
However when trying bluetoothctl list, there is nothing output. This indicates that the bluetooth controller
is not supported by bluetoothctl and hence it seems bluez.
Of course I could be getting Bluez and it's capabilitites all wrong here and 3rd party drivers are needed for Bluez to do it's thing and the bes2600 driver written by Bestechnic is in fact incomplete, but that's just too far fetched.
Something is not being said about the bes2600 bluetooth driver, bluez, their place on the pinetab2 and what is entailed exaclty to get bluetooth working.
The makers of the pinetab2 need to speak up here and say what's going on beyond just a simple "the bluetooth driver needs to be implemented".
I am hard pressed to believe that Bestechnic didn't leave the driver incomplete by design and that the kernel takes care of what they left out. At least on most devices.
??
RE: PineTab Bluetooth - spaesani - 11-02-2024
Pine64 is shutting down discussion on this topic.
Weird.
RE: PineTab Bluetooth - Kevin Kofler - 11-02-2024
The current version of the driver does actually support Bluetooth. Otherwise, there would not be the instructions (which are not working for the OP for whatever reason). The issue is that the driver as a whole is apparently not reliable, which is unfortunately fairly typical for vendor-provided out-of-tree drivers.