pBluetooth 4.0 alpha 7

[mistfire]

pBluetooth 4.0 alpha 4 released

Changes:

• Improved manage paired device features
• Bluetooth remote control now works (If remote device supports it, I tested it by connecting my smartphone and control YouTube app)
• Improved OBEX push. If obexd was not running, it automatically run before sending files. (bt-obex requires obexd running)
• Bluetooth tethering works. But obtaining IP address not yet implemented.
• Some dialog fixes

Download was on the first post of this thread

[mistfire]

pBluetooth 4.0 alpha 5 released

Changes:
* Added applet-tray for quick access bluetooth settings and indicating bluetooth status
(Requires xdg compliant startup)
* Improvements for bluez-alsa

Download was on the first post of this thread

[norgo]

@mistfire
did some tests today and have to say really good work.
Unfortunately there is still following problem:
Some devices expect a PIN for pairing (my mobile phone as example).
In this case usage of option "agent NoInputNoOutput" leads always to pairing failed.
I modified the script for testing with PIN usage.
Now pairing worked without problems.
Connection to my laptop, send and receive of files worked flawless.

thank you very much

tested in ScPup32 and BlueZ-5.47
@TIFTAF most probably interesting for you

pbluetooth-40-a5.png (47.57 KiB) Viewed 2464 times

[mistfire]

@norgo
Wow! you solved the Bluetooth PIN pairing. Could you please send me your code on how you do that PIN pairing?

Thank you

[norgo]

@mistfire
replace the code ( line 370-387 ) of pbluetooth script by this

Code: Select all

### generate pairing PIN ###
		rpin=$(printf '%04d\n' $((1 + RANDOM % 10000)))
		ptxt=$(echo -e "Pairing New Device...\n\n\t PIN \n\t$rpin")

		/usr/lib/gtkdialog/box_splash -close never -text "$ptxt" &
		XPID=$!

	{	printf 'discoverable on\n\n'
		printf 'pairable on\n\n'
		printf 'scan on\n\n'
		sleep 5
		printf '%s\n' "pair $BDA"
		sleep 3
		printf '%s\n' "$rpin" '\n\n'
		sleep 8
	}	| bluetoothctl

[mistfire]

pBluetooth 4.0 alpha 6 released

Changes:
* Added option to use PIN code for device pairing (thanks @norgo)

Download was on the first post of this thread

[TIFTAF]

Hi mistfire.
Thank you very much for all your work in regard to puppy.
I looked at your link supplied:
> and checked whether Bionicpup32 carried all those dependencies required for bluetooth.
> Installed are : hcitool > yad > Xdialog > dbus > libbluetooth.so.3 libbluetooth.so.3.18.16 libbluetooth3
libbluetooth3_5.48.files libbluetooth.so.3 libbluetooth.so.3.18.16 libbluetooth3 libbluetooth3_5.48.files
> I downloaded bluez_5.48 and installed it with the PPM.
> Downloaded pbluetooth-4.0_alpha_6 and installed it.
> Checked with "Check Dependencies"
> Found that bluez-alsa bluez-tools obexd and obexfs were missing.
> Downloaded "bluez-tools_0.2.0~20140808-5build1_i386.deb" and installed it.
> Downloaded "bluez-obexd_5.48-0ubuntu3.4_i386.deb" and installed it.
> Checked again with "Check Dependencies"
> Downloaded "obexfs_0.11-2build1_i386.deb" and installed it.
> There were also "libs" that came with those packages, such as:
> libbfb0_0.24-5build4_i386.deb > installed > bluez-alsa obexd missing
> libbluetooth3_5.48-0ubuntu3.4_i386.deb > installed > bluez-alsa obexd missing
> libdb5.3_5.3.28-13.1ubuntu1.1_i386.deb > installed > bluez-alsa obexd missing
> libical3_3.0.1-5_i386.deb > installed > bluez-alsa obexd missing
> libmulticobex1_0.24-5build4_i386.deb > installed > bluez-alsa obexd missing
> libobexftp0_0.24-5build4_i386.deb > installed > bluez-alsa obexd missing
> libopenobex2_1.7.2-1_i386.deb > installed > bluez-alsa obexd missing
> Checked again with "Check Dependencies" and found "bluez-alsa" and "obexd" still missing.
> Checked with my Huawei Phone and found that it did "pair" with my laptop but did not transfer files.
> Instaed a bluetooth window appeared telling me that "obexd" is still missing.

At this point I am facing 2 problems:

First > I already installed "obexd" and yet the dependency check lists it as missing.

Second > The PPM does not list a "bluez-alsa" package. But ... checking the PPM under "alsa" I found
the following packages already installed :

> alsa-base_1.0.25+dfsg
> als-utils_1.1.3
> libasound2_1.1.3
> libasound2-data_1.1.3
> libasound2-plugins_1.1.1
> libasound2-plugin-equal_0.6-7
> linux-sound-base_1.0.25+dfsg
> apulse_0.1.10+git20171108-gaca334f-2

So, what do you suggest ?
Thanks for your help.

TIFTAF

[mistfire]

Hi mistfire.
Thank you very much for all your work in regard to puppy.
I looked at your link supplied:
> and checked whether Bionicpup32 carried all those dependencies required for bluetooth.
> Installed are : hcitool > yad > Xdialog > dbus > libbluetooth.so.3 libbluetooth.so.3.18.16 libbluetooth3
libbluetooth3_5.48.files libbluetooth.so.3 libbluetooth.so.3.18.16 libbluetooth3 libbluetooth3_5.48.files
> I downloaded bluez_5.48 and installed it with the PPM.
> Downloaded pbluetooth-4.0_alpha_6 and installed it.
> Checked with "Check Dependencies"
> Found that bluez-alsa bluez-tools obexd and obexfs were missing.
> Downloaded "bluez-tools_0.2.0~20140808-5build1_i386.deb" and installed it.
> Downloaded "bluez-obexd_5.48-0ubuntu3.4_i386.deb" and installed it.
> Checked again with "Check Dependencies"
> Downloaded "obexfs_0.11-2build1_i386.deb" and installed it.
> There were also "libs" that came with those packages, such as:
> libbfb0_0.24-5build4_i386.deb > installed > bluez-alsa obexd missing
> libbluetooth3_5.48-0ubuntu3.4_i386.deb > installed > bluez-alsa obexd missing
> libdb5.3_5.3.28-13.1ubuntu1.1_i386.deb > installed > bluez-alsa obexd missing
> libical3_3.0.1-5_i386.deb > installed > bluez-alsa obexd missing
> libmulticobex1_0.24-5build4_i386.deb > installed > bluez-alsa obexd missing
> libobexftp0_0.24-5build4_i386.deb > installed > bluez-alsa obexd missing
> libopenobex2_1.7.2-1_i386.deb > installed > bluez-alsa obexd missing
> Checked again with "Check Dependencies" and found "bluez-alsa" and "obexd" still missing.
> Checked with my Huawei Phone and found that it did "pair" with my laptop but did not transfer files.
> Instaed a bluetooth window appeared telling me that "obexd" is still missing.

At this point I am facing 2 problems:

First > I already installed "obexd" and yet the dependency check lists it as missing.

Second > The PPM does not list a "bluez-alsa" package. But ... checking the PPM under "alsa" I found
the following packages already installed :

> alsa-base_1.0.25+dfsg
> als-utils_1.1.3
> libasound2_1.1.3
> libasound2-data_1.1.3
> libasound2-plugins_1.1.1
> libasound2-plugin-equal_0.6-7
> linux-sound-base_1.0.25+dfsg
> apulse_0.1.10+git20171108-gaca334f-2

So, what do you suggest ?
Thanks for your help.

TIFTAF

Bluez5 includes obexd
In case the package was missing on the repo you need to download those packages on third party sites. pkgs.org is the good start to search third party package

[BarryK]

EDIT: removed. I posted links to bluez-alsa pet, but that is 64-bit and I see above that you want 32-bit.

[TIFTAF]

@ mistfire
Thanks for your reply. I will try it.

@ Barry
You wrote :
EDIT: removed. I posted links to bluez-alsa pet, but that is 64-bit and I see above that you want 32-bit.

Would you post it again please. I would like to try it out on a 64bit laptop.
Thanks.

[BarryK]

Well, I have a PET that was compiled on EasyOS Buster-series, so should work on any pups built with Debian Buster 10 DEBs. Any other distro and you would have to test that it works.

Also, the Buster PET has libs in /usr/lib/x86_64-linux-gnu, which might be a problem with some pups, such as the Slackware-based pups that use /usr/lib64. But some pups just have /usr/lib/x86_64-linux-gnu as a symlink to /usr/lib, so that would be ok.

Anyway, the PET is here:

http://distro.ibiblio.org/easyos/amd64/ ... es-buster/

EasyOS Dunfell-series is built with my compiled-from-source packages, also has bluez-alsa:

http://distro.ibiblio.org/easyos/amd64/ ... -64.tar.xz

...which has libs in /lib and /usr/lib. You would probably need to run 'ldd' on the executable /usr/bin/bluealsa to test that all library dependencies are there.

[TIFTAF]

Hi Barry.
Thank you very much for your reply. I know you are a busy man.
Off Topic
I am also enjoying and admiring your "travel pages" and I am impressed with your success in
collecting items of such a low weight and effective use for traveling light.
Well done.
My wife and I are envious of your ability to travel the Australian Countryside the way you do.
We wish you many more such lovely adventures. Look after yourself and stay healthy.
Have a lovely day.
Ulrich
(TIFTAF)

[BarryK]

Hi Barry.
Thank you very much for your reply. I know you are a busy man.
Off Topic
I am also enjoying and admiring your "travel pages" and I am impressed with your success in
collecting items of such a low weight and effective use for traveling light.
Well done.
My wife and I are envious of your ability to travel the Australian Countryside the way you do.
We wish you many more such lovely adventures. Look after yourself and stay healthy.
Have a lovely day.
Ulrich
(TIFTAF)

Don't want to hijack this thread, but yeah, we are fortunate in Western Australia, being coronavirus-free, able to go anywhere, socialize, etc. The only cases are those of travellers coming from overseas, and they have to go into 2-week hotel quarantine. Unfortunately, there have been some cases of hotel staff getting infected. A couple of weeks ago, a security guard got infected (the UK strain, suspected air-borne), and our Premier put the entire city into lockdown for 5 days, then partial lockdown for another week. Tough measures, but he is credited with our current virus-free situation.

Returning this thread to pBluetooth...

[boof]

have installed latest pet, in upupbb32, with avail dependencies. bluealsa n/a. pin is given, where do i enter it? does pair, but not connect. want to use for speaker.

[mistfire]

have installed latest pet, in upupbb32, with avail dependencies. bluealsa n/a. pin is given, where do i enter it? does pair, but not connect. want to use for speaker.

Sorry for late reply. Did you select pair without PIN?

[mistfire]

In case bluealsa or bluez-alsa is unavailable on your respective repos. You can use pulseaudio. For sound volume and soundcard management on pulseaudio. Install pavucontrol or any pulseaudio gui. Later Puppy builds can manage pulseaudio and all ALSA application will be automatically redirect to pulseaudio

[mistfire]

pBluetooth 4.0 alpha 7 released

Changes:
* Pairing bugfix

Download was on the first post of this thread

[nashtrik]

Hi,
I am able to pair bluetooth earpods but not able to connect them on bionicpup64. Upon clicking the 'connect' button, it flashes a red message 'unable to connect'. Any solutions ? Also, I am able to transfer pictures from Android pgone to Bionic, but not the other way. I do not see any share/move option. I am new to puppy linux. Thanks

[HerrBert]

Hello.

I know that on slackware based Puppies bluetooth audio streaming is a challenge in itself.
Nonethless i tried to get a bluetooth headset up and running in Slacko64 7.0.

I remember having success with slackstream by @greengeek in Sacko 5.7.0. Seems to be ages ago...

Bluetooth in Slackware 14.2 works completely different.

What i had to do:

Install from PPM:

• bluez-5.47-x86_64-1_slack14.2.txz

• sbc-1.3-x86_64-1.txz

Compiled from http://slackbuilds.org/repository/14.2/ ... luez-alsa/

• bluez-alsa-1.3.1-x86_64-1_SBo.tgz

and last but not least installed from here:

• pbluetooth-4.0_alpha_7.pet

What to do with it?
I don't use a savefile/folder, so rebooting doesn't help.

So after some research i started bluetoothd in a terminal with /etc/rc.d/rc.bluetooth start

pbluetooth starts from Menu -> Network -> pBluetooth

Now there i have some issues:

• Not much information about bluetooth status but power is on.

• Pairing a new device without a PIN fails in all cases i tried, even if the bluetooth device doesn't require a PIN.
  With random PIN i can connect to bluetooth speaker or bluetooth headset.

• In managing a paired device, testing audio doesn't work. Streaming to bluetooth headset via audacious works OOTB. Streaming via aplay and mplayer not.
  mplayer needs option -ao alsa but aplay needs more advanced parameters. aplay -D bluealsa:HCI=hci0,DEV=F4:4E:FC:68:06:58,PROFILE=a2dp startup.wav plays my sound on bluetooth headset. After first playing a sound with afore mentioned command, aplay plays sound on bluetooth headset as usual.

• After disconnecting / unpairing my bluetooth headset, /etc/asound.conf locks playback to bluetooth device.

• After running pbluetooth, ps shows a lot of garbadge (several instances or pbluetooth, grep, sh -c, ...)

[greengeek]

Well, I have a PET that was compiled on EasyOS Buster-series, so should work on any pups built with Debian Buster 10 DEBs. Any other distro and you would have to test that it works.

Also, the Buster PET has libs in /usr/lib/x86_64-linux-gnu, which might be a problem with some pups, such as the Slackware-based pups that use /usr/lib64. But some pups just have /usr/lib/x86_64-linux-gnu as a symlink to /usr/lib, so that would be ok.

Anyway, the PET is here:

http://distro.ibiblio.org/easyos/amd64/ ... es-buster/

EasyOS Dunfell-series is built with my compiled-from-source packages, also has bluez-alsa:

http://distro.ibiblio.org/easyos/amd64/ ... -64.tar.xz

...which has libs in /lib and /usr/lib. You would probably need to run 'ldd' on the executable /usr/bin/bluealsa to test that all library dependencies are there.

Are these pets still available for testing? (Showing 404 presently...)
Cheers!

[BarryK]

Well, I have a PET that was compiled on EasyOS Buster-series, so should work on any pups built with Debian Buster 10 DEBs. Any other distro and you would have to test that it works.

Also, the Buster PET has libs in /usr/lib/x86_64-linux-gnu, which might be a problem with some pups, such as the Slackware-based pups that use /usr/lib64. But some pups just have /usr/lib/x86_64-linux-gnu as a symlink to /usr/lib, so that would be ok.

Anyway, the PET is here:

http://distro.ibiblio.org/easyos/amd64/ ... es-buster/

EasyOS Dunfell-series is built with my compiled-from-source packages, also has bluez-alsa:

http://distro.ibiblio.org/easyos/amd64/ ... -64.tar.xz

...which has libs in /lib and /usr/lib. You would probably need to run 'ldd' on the executable /usr/bin/bluealsa to test that all library dependencies are there.

Are these pets still available for testing? (Showing 404 presently...)
Cheers!

bluez-alsa? ...that's going back awhile.
EasyOS moved to pulseaudio and no longer required that package.

No PET, but the compiled tarball is still there:

http://distro.ibiblio.org/easyos/amd64/ ... e/dunfell/

I found the bluez-alsa PET in my local archive, see attached, with false ".gz"

[BarryK]

And just for the record, this is how bluez-alsa was compiled back then:

https://github.com/bkauler/oe-qky-dunfe ... a_3.0.0.bb