The time now is Thu 12 Dec 2019, 16:31
All times are UTC - 4 |
Author |
Message |
rufwoof

Joined: 24 Feb 2014 Posts: 3675
|
Posted: Fri 18 Dec 2015, 03:52 Post subject:
|
|
Celeron D single core running Tahr 6.0.2 with 6.0.3 patch applied and kernel swapped out for Emsee 4.3.2 (32 bit PAE)
I've no BT headset, but a mobile phone that supports bluetooth so plugged in a USB bluetooth dongle and followed the clear/concise instructions in the first post and managed to pair the phone with puppy OK.
On asking for a password I tried 0000 first and that failed, 1234 next and that worked ok (and opened a window on the phone into which I entered the same).
The cars not in range and outside works are preventing it being brought into range at present, but when I can I'll see if I can pair to the car's bluetooth as that is a form of 'BT headphone' of sorts (I think). That could prove useful i.e. puppy detecting when the car was approaching/at home - as part of home automation.
|
Back to top
|
|
 |
Smithy

Joined: 12 Dec 2011 Posts: 1076
|
Posted: Mon 21 Dec 2015, 09:38 Post subject:
|
|
You might need this in the distribution, rename to.ko
(lib/modules/kernel version xx/kernel/net/bluetooth)
to get two way voice streaming.
Unless there is a newer way, but the whole BLUEZ bluetooth thing has been sadly UNDOCUMENTED
Description |
|

Download |
Filename |
sco.png |
Filesize |
16.82 KB |
Downloaded |
238 Time(s) |
Last edited by Smithy on Tue 22 Dec 2015, 14:47; edited 1 time in total
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 12805 Location: Stratford, Ontario
|
Posted: Mon 21 Dec 2015, 11:02 Post subject:
|
|
Where did you get this module? It needs to be compiled against each kernel.
I suspect that the big-boy Linuxes can do this through pulse-audio.
Last edited by rcrsn51 on Tue 22 Dec 2015, 07:24; edited 1 time in total
|
Back to top
|
|
 |
Smithy

Joined: 12 Dec 2011 Posts: 1076
|
Posted: Mon 21 Dec 2015, 12:14 Post subject:
|
|
I mixed a hybrid of Dpup 3.5.2.11 and Jemimah Fluppy 13 kernel (which contains bt sco.ko she compiled). I saw the sco-bt had loaded, but that was as far as I got.
Just a test.
Yes, as far as I can tell Rcrsn51, that module (compiled) with asound rc should produce an option in voips to send and receive sound over bluetooth. Max 98kbs, telephone quality, we're not talking Apt-X quality but fine for voice. And a good complement to the A2DP streaming.
Like in XP with the Toshiba Suite.
But better because it's a Puppy!
A few links here:
http://blog.encomiabile.it/2010/01/02/skype-linux-alsa-bluetooth/
http://www.alsa-project.org/main/index.php/Matrix:Module-bt-sco
http://www.gargan.org/linux/snd-bt-sco/
I also found these things, not sure if they are any good, but might as well post them before I forget; rename to .deb
Description |
|

Download |
Filename |
gbtsco_0.1.1-0ubuntu1_all.png |
Filesize |
5.12 KB |
Downloaded |
258 Time(s) |
Description |
|

Download |
Filename |
bluez-btsco_0.50-0ubuntu6_i386.png |
Filesize |
45.43 KB |
Downloaded |
215 Time(s) |
Last edited by Smithy on Tue 22 Dec 2015, 14:50; edited 1 time in total
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 12805 Location: Stratford, Ontario
|
Posted: Tue 22 Dec 2015, 07:22 Post subject:
|
|
It looks to me like this bt-sco stuff is obsolete. There is lots of modern information available for using Skype and Bluetooth in Linux. But people are doing it through Pulse Audio. I can't tell if they are using HSP or A2DP headsets.
I own some BT headphones with a built-in mic and I tried to get the mic detected by ALSA, with no luck.
I have taken this project as far as I can/want.
|
Back to top
|
|
 |
Smithy

Joined: 12 Dec 2011 Posts: 1076
|
Posted: Tue 22 Dec 2015, 14:46 Post subject:
|
|
I was coming to the same conclusion, I gather that the new method is to use Alsa space for a plugin, geez it is hard to find this undocumented stuff.
So if there was a Pulse Audio based Puppy... there again I don't think Apt-X is supported in Bluez yet, only been going since the 1990's. No rush lol!
If I get two way streaming from Alsa I will let ya know.
|
Back to top
|
|
 |
Smithy

Joined: 12 Dec 2011 Posts: 1076
|
Posted: Sun 27 Dec 2015, 09:51 Post subject:
|
|
http://www.gentoo-wiki.info/Bluetooth_headset#Software_installation. Hmmm.
Well I gave pulse a good try, but it is very complicated with the bluetooth audio module, gallons of dependencies and I couldn't get that flipping daemon to start up. Leaving that for a while for sure..
Make me wonder if Apulse might be able to accomodate some kind of "Slip in" module for HSP mode. Might be a neater solution for Puppy and voips over bluetooth. Some kind of bridge between the Tempestuous Bluez and Skype.
Well I don't want to divert the thread because I gather this is principally for streaming stereo>> to>> headphones.
I did pick up one of those little bluetooth dongles with CSR chip in it.
This package picks it up just fine and paired ok. Easy Peasy.
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 12805 Location: Stratford, Ontario
|
Posted: Sun 27 Dec 2015, 09:58 Post subject:
|
|
Smithy wrote: | Well I gave pulse a good try, but it is very complicated with the bluetooth audio module |
No kidding. I have been playing around with ways to stream audio from your phone out your computer speakers over BT. You are supposed to be able to do this via pulse audio but it's like pulling teeth in Puppy.
[Edit] I have this working using code from a project by jamesbond.
|
Back to top
|
|
 |
Smithy

Joined: 12 Dec 2011 Posts: 1076
|
Posted: Mon 28 Dec 2015, 18:22 Post subject:
|
|
Oh, that's a bit of puppy progress then!
Just a heads up on the beautify aspect. This ping (and scaleable svg) looks clearer and bigger (on a tint 2/ openbox desktop 48x48) than the one in there. I got it from the precise bluez pet, no Off button in there though.
Description |
|
Filesize |
2.93 KB |
Viewed |
1011 Time(s) |

|
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 12805 Location: Stratford, Ontario
|
Posted: Tue 29 Dec 2015, 11:11 Post subject:
|
|
Thanks. I have assigned your PNG icon to the .desktop file and left the two XPM tray icons as they are.
|
Back to top
|
|
 |
Smithy

Joined: 12 Dec 2011 Posts: 1076
|
Posted: Sun 03 Jan 2016, 04:22 Post subject:
|
|
rcrsn51 wrote: |
I own some BT headphones with a built-in mic and I tried to get the mic detected by ALSA, with no luck.
|
Did you try that in Fatdog rcrsn51?
JamesBond wrote: |
b) supports audio-streaming (bluetooth speakers). After you pair them you need to enable them using Fatdog Default Soundcard settings available in Sound section of Fatdog Control Panel.
Note that I have not tried two-way audio using a bluetooth headset.
|
I noticed a few differences in the Fatdog vs Tahrpup etc/bluetooth/audio.conf.
I presume this is where some of the action takes place.
Code: | # Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
[General]
Enable=Socket
# Switch to master role for incoming connections (defaults to true)
#Master=true
# If we want to disable support for specific services
# Defaults to supporting all implemented services
#Disable=Gateway,Source,Socket
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
[Headset]
# Set to true to support HFP, false means only HSP is supported
# Defaults to true
HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
MaxConnected=1
# Set to true to enable use of fast connectable mode (faster page scanning)
# for HFP when incoming call starts. Default settings are restored after
# call is answered or rejected. Page scan interval is much shorter and page
# scan type changed to interlaced. Such allows faster connection initiated
# by a headset.
FastConnectable=false
# Just an example of potential config options for the other interfaces
#[A2DP]
#SBCSources=1
#MPEG12Sources=0
|
FatDog unfortunately will not boot with older Atom cpus.
I did try on another 64 bit capable cpu to create a "virtual" default bluetooth sound card in the control panel, but no alsamixer or volume control showed up.
At least it offers that option though.
FatDog Bluetooth did beep some far away external bluetooth equipment though, so something's going on!
|
Back to top
|
|
 |
charlie6

Joined: 30 Jun 2008 Posts: 1221 Location: Saint-Gérard / Walloon part of Belgium
|
Posted: Sun 10 Jan 2016, 15:21 Post subject:
|
|
Hi,
some devices such as recent smartphone are featured with "Bluetooth-4.0 Smart" i.e. having low energy needs. This is no longer compatible with earlier bluetooth version.
To detect such device from a PC, one has to do
instead ( "le" standing for low energy )
This comment
Code: | # hcitool lescan
Set scan parameters failed: Input/output error |
means that the BT adapter (= dongle or built-in) does not support the BT smart or low energy standard.
in such case, doing
does not report anything (= not any comment nor error message)
here a relevant link
http://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root
one also need the option --lescan option with hcitool (coming with bluez_4.101-0ubuntu13.1_i386.deb)
HTH
Charlie
|
Back to top
|
|
 |
Dopy25
Joined: 12 Apr 2016 Posts: 1
|
Posted: Fri 15 Apr 2016, 10:23 Post subject:
Re: PeasyBT Bluetooth Manager |
|
rcrsn51 wrote: | Note: This package needs testing and feedback, not anonymous downloads. Please send me a PM.
|
May I give it a try? I am running Arcade Puppy which is slacko 593. I got Bluetooth working with the streaming pet from the first page but I would like to give your Peasy BT GUI a shot.
I tried PMing you but I'm not sure if you got it or not since I am a new member.
|
Back to top
|
|
 |
gcmartin
Joined: 14 Oct 2005 Posts: 6730 Location: Earth
|
Posted: Mon 16 May 2016, 13:37 Post subject:
|
|
RasberryPi latest release indicates a new-better Bluetooth utility.
Raspians wrote: | We've just released a new version of our Raspbian image with some (hopefully) useful features. When the Pi 3 launched back in February, we'd not had time to do much in terms of getting access to the new on-board Bluetooth hardware. There was a working software stack, but the UI was non-existent. I'd hoped to be able to use one of the existing Linux Bluetooth UIs, but on trying them all, none were really what I was looking for in terms of usability and integration with the look and feel of the desktop. I really didn't want to write one from scratch, but that ended up being what I did, which meant a fun few weeks trying to make head or tail of the mysteries of BlueZ and D-Bus. After a few false starts, I finally got something I felt was usable, and so there is now a Bluetooth plugin for the LXPanel taskbar." | Simple as it looks, I wonder if it would be adaptable or useful to Puppy Linux users.
_________________ Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engines or use DogPile
|
Back to top
|
|
 |
ktat
Joined: 07 Oct 2013 Posts: 19
|
Posted: Tue 21 Jun 2016, 05:39 Post subject:
Subject description: trying to solve my bluetooth problem |
|
Hi, Thanks for this thread. I am hoping that by working through this I may be able to get my bluetooth speaker working again.
I say again because it worked briefly and then, I messed around with something and I can't get it going again.
I have installed http://www.smokey01.com/tempestuous/bluez_4.101-streaming.pet.
My icon appeared and it was black, I clicked it and it did turn blue. And that was good.
Code: | root# rfkill list
0: phy0: wlan
Soft blocked: no
Hard blocked: no
1: hci0: bluetooth
Soft blocked: no
Hard blocked: no |
I turned on my bluetooth speaker and entered the following:
Code: | root# hcitool scan
Device is not available: No such device
|
this was not good, I read further along your thread...
and tried:
Code: | root# bluez-test-device list
Traceback (most recent call last):
File "/usr/bin/bluez-test-device", line 17, in <module>
manager = dbus.Interface(bus.get_object("org.bluez", "/"), "org.bluez.Manager")
File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files |
then:
Code: | root# lsusb
Bus 001 Device 004: ID 05e3:0505 Genesys Logic, Inc.
Bus 001 Device 002: ID 0781:5170 SanDisk Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0b05:b700 ASUSTek Computer, Inc. Broadcom Bluetooth 2.1
|
I'm afraid I don't know the driver for my wifi card. I can tell you this though:
Code: | root# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] (rev 02)
01:00.0 Network controller: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe
03:00.0 Ethernet controller: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0) |
Version-
Kernel : Linux 3.14.56 (i686)
Version : #1 SMP PREEMPT Mon Dec 21 14:52:08 GMT 2015
Computer-
Operating System : tahrpup - 6.0.5
I have also posted in the cutting edge thread with a similar issue. I am trying to tackle this problem from two ends at once. So I have 2 sticks with the same tahr pup installed - but different bluetooth software.
|
Back to top
|
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|