pBluetooth 3.2 - the bluetooth manager
pBluetooth 3.2 - the bluetooth manager
This a fork of the abandoned PuppyBT by fr33land. It manages almost the whole bluetooth adapters and its connectivity. It is improved and more user friendly than PuppyBT
This app requires the following packages:
- bluez (https://drive.google.com/open?id=0B2FRk ... VBhaDgwUzA)
- bluez-tools (https://drive.google.com/open?id=0B2FRk ... lpXZTFBS1U)
- obexd
- openobex
- obexftp
- a2dp-alsa by jamesbond (already included in the package, Source code: http://www.lightofdawn.org/wiki/wiki.cg ... 02.tar.bz2)
New features:
* Adaptive daemon. If there is no bluetooth adapter detected. all bluetooth daemons will not run. If they are running, they will kill automatically. This will save more ram
* With paired device management
* With serial communication
Currently tested:
* Streaming sounds on bluetooth speaker (Set the sound output of a player to alsa)
* Basic pairing and device management
* Establishing serial port communication on bluetooth
* Receiving files over bluetooth
* Sending files over bluetooth
Need to be tested:
* Bluetooth tethering
* Receive sound input from the mic of the bluetooth headset
* Sound input from bluetooth headset
* a2dp audio stearming
Need to be added or change in the future:
* Bluetooth FTP
* Shift user interface from dialog to Xdialog
If you want to contribute on this project just upload your changes here (in PET package format)
This app requires the following packages:
- bluez (https://drive.google.com/open?id=0B2FRk ... VBhaDgwUzA)
- bluez-tools (https://drive.google.com/open?id=0B2FRk ... lpXZTFBS1U)
- obexd
- openobex
- obexftp
- a2dp-alsa by jamesbond (already included in the package, Source code: http://www.lightofdawn.org/wiki/wiki.cg ... 02.tar.bz2)
New features:
* Adaptive daemon. If there is no bluetooth adapter detected. all bluetooth daemons will not run. If they are running, they will kill automatically. This will save more ram
* With paired device management
* With serial communication
Currently tested:
* Streaming sounds on bluetooth speaker (Set the sound output of a player to alsa)
* Basic pairing and device management
* Establishing serial port communication on bluetooth
* Receiving files over bluetooth
* Sending files over bluetooth
Need to be tested:
* Bluetooth tethering
* Receive sound input from the mic of the bluetooth headset
* Sound input from bluetooth headset
* a2dp audio stearming
Need to be added or change in the future:
* Bluetooth FTP
* Shift user interface from dialog to Xdialog
If you want to contribute on this project just upload your changes here (in PET package format)
- Attachments
-
- pbluetooth-3.2.png
- (35.33 KiB) Downloaded 5519 times
-
- pBluetooth-3.2.pet
- Smart detection of bluetooth devices
Sending file over bluetooth works - (51.69 KiB) Downloaded 1995 times
Last edited by mistfire on Thu 30 May 2019, 08:12, edited 6 times in total.
@mistfire
Regards,
Ken.
I used fr33lands version with some success but needed quite a lot of help along the way (see from page two of thread). I'm using the most up to date version of lucid 287s2. I'd like to try your pet but have one question. Are the above packages available as pets?This app requires the following packages:
- bluez
- bluez-alsa
- bluez-compat
- bluez-tools
- obexd
- a2dp-alsa by jamesbond (Source code: http://www.lightofdawn.org/wiki/wiki.cg ... 02.tar.bz2)
Regards,
Ken.
- bluez (yes, version 4.99)keniv wrote: Are the above packages available as pets?
- bluez-alsa (already included in the package)
- bluez-tools (as deb file)
- obexd (yes)
PuppyBT thread was deleted because fr33land withdrew the project. If you are currently using PuppyBT then the pBluetooth should work. It is already stated on the first post of this thread which component is not yet tested. I already tested its functionality.
UPDATE:
I repacked bluez-tools into pet package complete with its dependencies
Download here: https://drive.google.com/open?id=0B2FRk ... lpXZTFBS1U
I made a new save file to test this as I remember it took quite a lot for me to get fr33lands to work and I don't want to remove it until I have yours working. However I cannot find a pet for bluez 4.99.
Can you please post a link to it. Do I still need this?
If this is source code do I have to compile this. I don't know how to do this. I have installed the other packages.
Regards,
Ken.
Can you please post a link to it. Do I still need this?
Code: Select all
- a2dp-alsa by jamesbond (Source code: http://www.lightofdawn.org/wiki/wiki.cgi/files/a2dp-alsa-2016-01-02.tar.bz2)
Regards,
Ken.
@ mistfire
I gave up trying to find a suitable copy of bleuz and deleted the test save file I made to try it.
Regards,
Ken.
I gave up trying to find a suitable copy of bleuz and deleted the test save file I made to try it.
I then tried pBluetooth with PuppyBT installed. It ran and detected the external bt dongle and external bt speakers that had paired without a problem before but would not pair. I uninstalled pBluetooth. This appeared to break PuppyBT as well as remove the icons. I reinstalled PuppyBT and all is well again. I think I'll wait to see how others get on.If you are currently using PuppyBT then the pBluetooth should work. It is already stated on the first post of this thread which component is not yet tested. I already tested its functionality.
Regards,
Ken.
@keniv
a2dp-alsa is already included in the package
Here is the bluez-4.99 package. I repacked it from slackware
Download link: https://drive.google.com/open?id=0B2FRk ... VBhaDgwUzA
Thats strange, pBluetooth uses the same component and files as PuppyBTkeniv wrote:@ mistfire
I then tried pBluetooth with PuppyBT installed. It ran and detected the external bt dongle and external bt speakers that had paired without a problem before but would not pair. I uninstalled pBluetooth. This appeared to break PuppyBT as well as remove the icons. I reinstalled PuppyBT and all is well again. I think I'll wait to see how others get on.
Regards,
Ken.
a2dp-alsa is already included in the package
Here is the bluez-4.99 package. I repacked it from slackware
Download link: https://drive.google.com/open?id=0B2FRk ... VBhaDgwUzA
I still have problems. If I click on pBluetooth in the network menu the window appears. If I select "Adapter" then "Check local bluetooth device" then click OK nothing happens but the app freezes. Mouse still works but nothing can be clicked. Have to shut machine off using Cnrl-Alt-BkSp then poweroff to shut down. If I don't click OK I can shut the window by clicking "x". The only thing I'm using that you have not provided is obexd-0.21-i485.pet. Is this OK?keniv wrote:I will make a new test lucid save file to test. I'll report back and let you know how it goes.
Ken.
-
- Posts: 4
- Joined: Wed 19 Apr 2017, 12:28
Hello,
Thank you for your hard work with this bluetooth manager.
I am currently running tahr6.0.5. I have installed all the pets that you included.
My bluetooth dongle is recognized however I still cant get it to work.
It says that it is paired with my bluetooth speaker but I dont hear anything out of the bluetooth speaker.
I was able to connect my bluetooth keyboard and gamepad.
Any help is appreciated.
Thanks
Blu.js7914
Thank you for your hard work with this bluetooth manager.
I am currently running tahr6.0.5. I have installed all the pets that you included.
My bluetooth dongle is recognized however I still cant get it to work.
It says that it is paired with my bluetooth speaker but I dont hear anything out of the bluetooth speaker.
I was able to connect my bluetooth keyboard and gamepad.
Any help is appreciated.
Thanks
Blu.js7914
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonjour mistfire,
As I didn't succeed in making pBluetooth work on my Puppy, I noticed that the /root/Startup/bluetooth and the /usr/sbin/pbluetooth scripts both exit:
"My" command lsusb currently returns:
and...
... is my adapter: duly present/identified, but not described as "bluetooth" or "Bluetooth" device...
So, replacing these lines with: makes the scripts both work, I should rather say, makes my device to be taken into account and the main interface be displayed.
Now, everything remains to be done!
I thought it was important to point this out.
Cordialement.
As I didn't succeed in making pBluetooth work on my Puppy, I noticed that the /root/Startup/bluetooth and the /usr/sbin/pbluetooth scripts both exit:
Code: Select all
if [ "$(lsusb | grep bluetooth)" == "" ] && [ "$(lsusb | grep Bluetooth)" == "" ][...]
Code: Select all
Bus 001 Device 002: ID 04f2:b14e Chicony Electronics Co., Ltd
Bus 006 Device 002: ID 0b05:17cb ASUSTek Computer, Inc.
Bus 007 Device 002: ID 1267:0210 Logic3 / SpectraVideo plc LG Optical Mouse 3D-310
[...]
Code: Select all
Bus 006 Device 002: ITheD 0b05:17cb ASUSTek Computer, Inc.
So, replacing these lines with:
Code: Select all
if [ "`rfkill list | grep luetooth`" = "" ];
Now, everything remains to be done!
I thought it was important to point this out.
Cordialement.
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonsoir et merci!
Is it possible to have some explanations about the "Comm" tab?
What are "Network" and "Serial" used for? Please, what does it mean exactly?
[EDIT]:
Cordialement.
Is it possible to have some explanations about the "Comm" tab?
What are "Network" and "Serial" used for? Please, what does it mean exactly?
[EDIT]:
I just discover this point... and I previously took the liberty to do it for an adapted version of pBlutooth for Puppy Precise/ToOpPy users, with some "cosmetics" to make the interface match with ToOpPy...Shift user interface from dialog to Xdialog
Cordialement.
- Attachments
-
- 180126_191547_566x385_easyshot.jpg
- (22.77 KiB) Downloaded 4694 times
-
- Posts: 168
- Joined: Fri 26 Jan 2018, 20:54
mistfire, thanks for this set of packages.
I managed to pair my bluetooth speaker with the Xenial32 devx, bluez and bluez-tools loaded. DeaDBeeF was a little finicky until I made this asound.conf edit, then the connection went through. It's good because I've been struggling with this for a few days now until I decided to try with a clean save file, then low and behold, "sound!" Now, thanks to your time investment, I can get back to more favorable activities.
mp
I managed to pair my bluetooth speaker with the Xenial32 devx, bluez and bluez-tools loaded. DeaDBeeF was a little finicky until I made this asound.conf edit, then the connection went through. It's good because I've been struggling with this for a few days now until I decided to try with a clean save file, then low and behold, "sound!" Now, thanks to your time investment, I can get back to more favorable activities.
mp
@matchpoint, youre welcome.
@Argolance
Network - Bluetooth can establish networking to other bluetooth device like LAN called Personal Area Network (PAN)
Serial - Serial communication via bluetooth. It is used for accessing the contents of an feature phone or smartphone. It is sometimes used to sync between pc and the phone
Nice interface that you made
@Argolance
Network - Bluetooth can establish networking to other bluetooth device like LAN called Personal Area Network (PAN)
Serial - Serial communication via bluetooth. It is used for accessing the contents of an feature phone or smartphone. It is sometimes used to sync between pc and the phone
Nice interface that you made
-
- Posts: 168
- Joined: Fri 26 Jan 2018, 20:54
mistfire,
The routine is not the same running 32b Tahr 6.0.5.
Once I go to pair with my discovered device, I make the selection, then hit enter leaving the passkey blank. At this point it instantaneously goes to "Pairing... Done." and there is no conformation or connection.
My previous setup utilized bluez-simple-agent. Which binary of your package is trying to connect?
The routine is not the same running 32b Tahr 6.0.5.
Once I go to pair with my discovered device, I make the selection, then hit enter leaving the passkey blank. At this point it instantaneously goes to "Pairing... Done." and there is no conformation or connection.
My previous setup utilized bluez-simple-agent. Which binary of your package is trying to connect?
-
- Posts: 168
- Joined: Fri 26 Jan 2018, 20:54
Okay. This pairs my device:
I'll invest some time and give it a closer look.
Code: Select all
bt-audio -c <dev-mac-address>