Puppy Linux Discussion Forum

BluePup is a GUI wrapper around 'bluetoothctl' commandline utility. The first BluePup was in 2016, then it languished. Now, it has been mostly rewritten and has new lease on life.

BluePup is not yet a PET, but the aim is that a PET can be created that will work on all pups. It requires gtkdialog with vte support, bluez and bt-tools packages. I currently have it working in EasyPup, and as bits of infrastructure are required to make it work, such as a special udev rule and a special Multiple Sound Card Wizard, it is probably best to test it in it's known working environment and get any bugs out, before creating a PET for other pups.

That's my thinking anyway. Here is a blog post with snapshots, a mini-tutorial:

https://bkhome.org/news/202011/testing- ... -2491.html

I haven't progressed as far a mistfire with pBluetooth, two-way file transfer, as I don't know anything about obex.

Let's see if I can embed one of those snapshots:

Anyway, testers welcome, bug reports welcome. And if anyone has a few clues about obex, mods to the code very welcome!

Oh, yes, the latest EasyPup is announced here:

https://bkhome.org/news/202011/easypup- ... eased.html

And forum announcement:

viewtopic.php?f=33&t=1355

...let me know if you find any bugs in that too!

Hello.
Thank you for a new release of EasyPup.

I tried BluePup. It worked fine.
transmitter: princeton PTM-UBT3S (usb bluetooth adapter)
receiver: buffalo BSHSBE06 (headset)

Both devices are rather old. I haven't used them for years.

What I used to send a file to my phone over bluetooth using obex, involved creating a serial device and assigning channel. Having the obexd daemon running and choosing target bt device. For receiving files select auto-accept.

#!/bin/sh

		bluetoothd --compat &
		obexd -a &
		obexftpd -b &

		sdptool add OPUSH 
		sdptool add FTP 

		hciconfig hci0 up

function rfcomfn ()} # create serial device, assign channel

[ ! -f 	/etc/bluetooth/rfcomm.conf ] && echo -e "#
# RFCOMM configuration file.
#

rfcomm4 {
#	# Automatically bind the device at startup
	bind yes;
#
#	# Bluetooth address of the device
	device $line;
#
#	# RFCOMM channel for the connection
	channel	4;
#
#	# Description of the connection
	comment \"Bluetooth rfcomm4 $line\";
}
" > /etc/bluetooth/rfcomm.conf
rfcomm connect rfcomm4 4 &
rfcomm listen 4 &

}; export -f rfcomfn




function btserial (){

bash -c rfcomfn
bt-obex -y -c/root/Downloads -a $(bluetoothctl list | cut -f2 -d' ') -s

}; export -f btserial


function btsend (){

bash -c rfcomfn
file-to-send=`yad --file`
rfcomm connect rfcomm4 4 &
rfpid=$!
bt-obex -y -d -b "$target-bt" "$file-to-send" &
wait $!

}; export -f btsend



function btget (){
echo "ftp search"
timeout 8 sdptool search FTP
bash -c rfcomfn
obexfs -b"$target-bt"
cd /
ls /
}; export -f btget

this link seems simpler
https://variwiki.com/index.php?title=IMX_Bluetooth_Obex

thinkpadfreak wrote: ↑Sat Nov 14, 2020 11:24 am

Hello.
Thank you for a new release of EasyPup.

I tried BluePup. It worked fine.
transmitter: princeton PTM-UBT3S (usb bluetooth adapter)
receiver: buffalo BSHSBE06 (headset)

Both devices are rather old. I haven't used them for years.

Good!
USB bluetooth adapters are troublesome with Linux. Apart from there not being Linux drivers for some, there are dongles that use cheap chips from China that are imperfect copies of chips that do work. I know, because I bought a couple of them earlier this year.

So far, have had success reports connecting audio, which is gratifying. In the past, I have had difficulty with using my audio devices, using other connection tools, such as Blueman.

stemsee wrote: ↑Sat Nov 14, 2020 2:01 pm

this link seems simpler
https://variwiki.com/index.php?title=IMX_Bluetooth_Obex

That's interesting. It says that no special action is required to receive a file, but I presume that obexctl or obexd need to be running?

Yes. Obexctl seems to part of the deprecated tools. /i found it in a ubuntu package for bluez5.37, which depends on libread.so.6 , Im using fatdog 811 with libread.so.7 and symlinking didnt work.

I also assume obexd should be running, but maybe obexctl initiates it.

BluePup is also in the latest EasyOS, version 2.4.92, a Release Candidate for 2.5:

https://easyos.org/forum/showthread.php?tid=244

I have fixed file send and receive to/from a phone, see blog post:

https://bkhome.org/news/202011/bluepup- ... works.html

We were discussing the "no default controller" error on the EasyOS forum. Two reports, both cases the problem is missing firmware, and in both cases it looks like installing the 'firmware-atheros' DEB fixes it.

https://easyos.org/forum/showthread.php ... 10#pid1210

It is available as a Debian DEB package. Click on "petget" icon and click the "Configure" button, then tick the "debian-buster-nonfree" checkbox.

Back at the main window, choose the "debian-buster-nonfree" radiobutton, then search for "firmware-atheros"

Barry, I've been tweaking this a bit to work in my current install of MX Linux.

1. Removed the requirements of pupmessage, pupdialog, basichtmlviewer in favor of just using gtkdialog popups in place of them.
2. Used yad or gxmessage popup (if installed otherwise just an echo to install gtkdialog) when gtkdialog not found.
3. Had some issues with the vte display in regards to the ANSI issues that you noted but had to do some other workarounds in some of the scripts to fix those.

Thanks for your work on these scripts, it's very much appreciated. My updates are posted below in case you want to implement any of them.

https://archive.org/download/plinej-pac ... pup.tar.xz

plinej wrote: ↑Wed Feb 23, 2022 2:13 pm

Barry, I've been tweaking this a bit to work in my current install of MX Linux.

1. Removed the requirements of pupmessage, pupdialog, basichtmlviewer in favor of just using gtkdialog popups in place of them.
2. Used yad or gxmessage popup (if installed otherwise just an echo to install gtkdialog) when gtkdialog not found.
3. Had some issues with the vte display in regards to the ANSI issues that you noted but had to do some other workarounds in some of the scripts to fix those.

Thanks for your work on these scripts, it's very much appreciated. My updates are posted below in case you want to implement any of them.

https://archive.org/download/plinej-pac ... pup.tar.xz

That's great, I have just downloaded the tarball. Good that you are generalizing it to run on other distros.

Note, there is also a page on BluePup here:

https://easyos.org/apps/bluepup-easy-bl ... ement.html

...though, needs updating as EasyOS now uses pulseaudio.

Just checked the scripts in /usr/local/bluepup, in current EasyOS, I see some were last updated in November 2021.

I suppose you know that I internationalized 'bluetoothctl':

https://bkhome.org/news/202010/bluetoot ... lized.html

But it will still work without being internationalized.
I did bump the version of bluez to 5.62 and created a new internationalization patch for bluetoothctl, it is in the woofQ tarball:

https://distro.ibiblio.org/easyos/project/oe/dunfell/