Please see the Note here.
This is a testing package and currently only exists for Tahrpup.
Bluetooth + streaming for tahrpup 6.x
-
april
All your links go back to that post. What I want to know is where do I getrcrsn51 wrote:Please see the Note here.
This is a testing package and currently only exists for Tahrpup.
"requires the bluez_4.101-streaming.pet by tempestuous" and can that be used with Puppy precise 5.7.1 or not?
I just want a front end that allows me to connect my bluetooth devices . Can you suggest a solution or two?
Use a bluetooth mouse on an Acer c720-2844 running Tahrpup 6
Hello,
Tahrpup 6.x may be used with a bluetooth mouse on an Acer c720-2844 if one installs the packages/files listed below:
1) AthrBT_0x11020000.dfu firmware. It is included in the "linux-firmware" package that one may download/install via the "Puppy Package Manager".
(dmesg had shown:
"Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
usb 2-4: Direct firmware load failed with error -2
usb 2-4: Falling back to user helper
Bluetooth: Patch file not found ar3k/AthrBT_0x11020000.dfu
Bluetooth: Loading patch file failed
ath3k: probe of 2-4:1.0 failed with error -2")
(The firmware package is huge. Just download, unpack and copy ar3k/AthrBT_0x11020000.dfu to /lib/firmware for the c720-2844)
2) The “bluez_4.101-streaming.pet
Tahrpup 6.x may be used with a bluetooth mouse on an Acer c720-2844 if one installs the packages/files listed below:
1) AthrBT_0x11020000.dfu firmware. It is included in the "linux-firmware" package that one may download/install via the "Puppy Package Manager".
(dmesg had shown:
"Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
usb 2-4: Direct firmware load failed with error -2
usb 2-4: Falling back to user helper
Bluetooth: Patch file not found ar3k/AthrBT_0x11020000.dfu
Bluetooth: Loading patch file failed
ath3k: probe of 2-4:1.0 failed with error -2")
(The firmware package is huge. Just download, unpack and copy ar3k/AthrBT_0x11020000.dfu to /lib/firmware for the c720-2844)
2) The “bluez_4.101-streaming.pet
Thank you for this important information.
Regarding the devx: This is a bug in Tahrpup's urxvt terminal emulator, which is looking for some Perl files that are only in the devx. The warning appears when PeasyBT opens some terminal windows, and should not affect the actual BT operations.
I have not seen a problem with my BT devices, but I will test it again with the devx loaded and see if there is a change. BT is quite hardware specific and I am not disputing your observation.
I once tried to track down the missing urxvt files so I could move them into regular Tahrpup. I will look at this again.
Regarding the firmware: Other users with built-in BT adapters may need these extra steps. Thank you for all your work on this.
BTW, you shouldn't need to run "bluetooth start". If the BT icon in the system tray is blue, you are good to go.
Regarding the devx: This is a bug in Tahrpup's urxvt terminal emulator, which is looking for some Perl files that are only in the devx. The warning appears when PeasyBT opens some terminal windows, and should not affect the actual BT operations.
I have not seen a problem with my BT devices, but I will test it again with the devx loaded and see if there is a change. BT is quite hardware specific and I am not disputing your observation.
I once tried to track down the missing urxvt files so I could move them into regular Tahrpup. I will look at this again.
Regarding the firmware: Other users with built-in BT adapters may need these extra steps. Thank you for all your work on this.
BTW, you shouldn't need to run "bluetooth start". If the BT icon in the system tray is blue, you are good to go.
-
charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
About bluetooth files transfer ...
Hi Bill,
many thanks for your latest PM !
got PeasyBT a try -without success-: on Tahrpup64 as first and aftwrds on Puppy Wheezy 3.5.2.11:
- firstable, i installed from respective repos all components that are in Tempestuous's pet (tons of thanks to him !); as also respective devx files to get python running as also missing python-gobject dependency (to get bluetooth-agent runing)
My purpose is only to transfer files from my cellular phone to my computer. That's not so relevant from this threads purpose.
So some missing dependencies might be still missing.
I meanwhile applied the "howto" you gave in page 5 above for files transfer.
- both computer and phone could detect ("discover") each other, and report the phones MAC code.
- i installed obexftp as also obexfs (infos collected from other bluetooth related threads)
Result: as now no success: the file transfer starts from phone, but stops a few seconfs later with «failed to connect» message on my phones display.
I next tried this pet with OOTB success, on a fresh frugal install of Puppy Wheezy 3.5.2.11: this pet is intented to run on Precise (From past experiences, I've assumed Precise apps to also run on Wheezy).
http://murga-linux.com/puppy/viewtopic. ... 261#799261
and
http://murga-linux.com/puppy/viewtopic. ... 705#868705
That pet is to be downloaded from:
https://drive.google.com/file/d/0B6M1io ... sp=sharing (click on the arrow in the above-center of the screen to start download)
(! i suspect this link to not be permanent ==> so download it while still «alive»
)
HTH for further developments of PeasyBT
Thanks again,
Cheers, Charlie
many thanks for your latest PM !
got PeasyBT a try -without success-: on Tahrpup64 as first and aftwrds on Puppy Wheezy 3.5.2.11:
- firstable, i installed from respective repos all components that are in Tempestuous's pet (tons of thanks to him !); as also respective devx files to get python running as also missing python-gobject dependency (to get bluetooth-agent runing)
My purpose is only to transfer files from my cellular phone to my computer. That's not so relevant from this threads purpose.
So some missing dependencies might be still missing.
I meanwhile applied the "howto" you gave in page 5 above for files transfer.
- both computer and phone could detect ("discover") each other, and report the phones MAC code.
- i installed obexftp as also obexfs (infos collected from other bluetooth related threads)
Result: as now no success: the file transfer starts from phone, but stops a few seconfs later with «failed to connect» message on my phones display.
I next tried this pet with OOTB success, on a fresh frugal install of Puppy Wheezy 3.5.2.11: this pet is intented to run on Precise (From past experiences, I've assumed Precise apps to also run on Wheezy).
http://murga-linux.com/puppy/viewtopic. ... 261#799261
and
http://murga-linux.com/puppy/viewtopic. ... 705#868705
That pet is to be downloaded from:
https://drive.google.com/file/d/0B6M1io ... sp=sharing (click on the arrow in the above-center of the screen to start download)
(! i suspect this link to not be permanent ==> so download it while still «alive»
)HTH for further developments of PeasyBT
Thanks again,
Cheers, Charlie
Yes, I got the above Precise Bluetooth pet to find a headset in Dpup 3.5.2.11.
Is it missing an asound file or something?
The multiple sound card just shows alc realtek, no headset or anything else.
At least Bluetooth actually does something now. And this is on a netbook with the combined BT/Wifi Atheros thing!
Could it not be fixed up so it just picks up BT devices and assigns them to the sound options in etc?
There is a file in etc but it just looks generic or unfinished,
If you pm me the Peasy Rcrsn51 I will have a go with the original Tempestuous setup, again, but it 'aint that peasy!
Is it missing an asound file or something?
The multiple sound card just shows alc realtek, no headset or anything else.
At least Bluetooth actually does something now. And this is on a netbook with the combined BT/Wifi Atheros thing!
Could it not be fixed up so it just picks up BT devices and assigns them to the sound options in etc?
There is a file in etc but it just looks generic or unfinished,
If you pm me the Peasy Rcrsn51 I will have a go with the original Tempestuous setup, again, but it 'aint that peasy!
Last edited by Smithy on Tue 15 Dec 2015, 18:27, edited 1 time in total.
Ok thanks, I have tahr-5.8.3.rc1 to hand, presumably this will do in the ever changing world of Puppy? Edit, picked up tahr-6.0.2.pae.
Will build the bluez and peasy into it and see if I can get it to function.
Will build the bluez and peasy into it and see if I can get it to function.
Last edited by Smithy on Wed 16 Dec 2015, 17:58, edited 1 time in total.
Libgirepository is contained in tempestuous' bluez PET, so I have no idea what is going wrong.
1. I set up a frugal install of Tahrpup with a savefolder.
2. I installed the two PETs.
3. I ran PeasyBT, which is just a front-end for the commands in the main PET, like bluez-simple-agent.
4. I paired with several audio devices.
5. It all worked correctly and there were no error messages.
BTW, a Jabra BT2046 is a headset designed to pair with cellphones. IIRC, it does not support the protocol for Bluetooth streaming audio as needed by this project. But it should still pair.
1. I set up a frugal install of Tahrpup with a savefolder.
2. I installed the two PETs.
3. I ran PeasyBT, which is just a front-end for the commands in the main PET, like bluez-simple-agent.
4. I paired with several audio devices.
5. It all worked correctly and there were no error messages.
BTW, a Jabra BT2046 is a headset designed to pair with cellphones. IIRC, it does not support the protocol for Bluetooth streaming audio as needed by this project. But it should still pair.
Yes it's fine now, I made a mistake on the usr libs and missed a couple of libs.
All built in now and the peasy buttons do the functions.
The Jabra succesfully turns a music track from Deadbeef into a series of beeps.
So will a headset with mic work with Skype and Linphone under the Bluez/ Peasy setup? It did seem stable, not disconnecting the pairing.
All built in now and the peasy buttons do the functions.
The Jabra succesfully turns a music track from Deadbeef into a series of beeps.
So will a headset with mic work with Skype and Linphone under the Bluez/ Peasy setup? It did seem stable, not disconnecting the pairing.
That was my experience. To stream audio, you need a BT device that handles the A2DP profile - like a portable speaker or BT headphones.Smithy wrote:The Jabra succesfully turns a music track from Deadbeef into a series of beeps.
It depends on the device and how it interfaces with ALSA. But I don't think that there is any support in this system for microphones.So will a headset with mic work with Skype and Linphone under the Bluez/ Peasy setup?
Please explain. The PET should install correctly on its own.I made a mistake on the usr libs and missed a couple of libs.
Regarding audio players: I like PeasyMP3 because it automatically plays to the default ALSA device, which you can control from PeasyBT. So you don't have to mess around with your player's setup. It's one click to switch between wired speakers and BT output.
I installed both pets by hand into the extracted tahr, and packed it up again.
Your Peasy MP3 sounds like it is perfect for BT and Analogue switching.
I use XMPlay because I sometimes like to see the frequencies.
Ah so a bit like the old days of half duplex.
Or even just one way transmission.
I noticed the A2DP transmitters/receivers have an either/or caveat
and two independent devices could produce unacceptable latency.
So basically this package is just for one way streaming.
I havent got bluetooth mice, so I can't test that aspect.
But what I did test (after the dumbass omission lol) seems to work very nicely
and the Peasy front end is vital for ease of use.
There are skype users who are using bluetooth stereo cans and mono mic, but I am not exactly sure what operating systems they are using.
As I plug yet another dangly cable in
EDIT: Bluez up to Version 4 does include the HSF HEADSET Profile
Bluez 5 has dropped it.
A link to some TESTS i.e Sony MDR-ZX330BT fully functioning Nokia BT etc
https://wiki.archlinux.org/index.php/Bl ... SA_Devices
Would be good if this project of Tempestuous and yours becomes the definitive plug and play go to implementation of Bluetooth on Linux.
Needs a lot more people to plug in their bluetooth apparatus though!
Your Peasy MP3 sounds like it is perfect for BT and Analogue switching.
I use XMPlay because I sometimes like to see the frequencies.
Ah so a bit like the old days of half duplex.
Or even just one way transmission.
I noticed the A2DP transmitters/receivers have an either/or caveat
and two independent devices could produce unacceptable latency.
So basically this package is just for one way streaming.
I havent got bluetooth mice, so I can't test that aspect.
But what I did test (after the dumbass omission lol) seems to work very nicely
and the Peasy front end is vital for ease of use.
There are skype users who are using bluetooth stereo cans and mono mic, but I am not exactly sure what operating systems they are using.
As I plug yet another dangly cable in
EDIT: Bluez up to Version 4 does include the HSF HEADSET Profile
Bluez 5 has dropped it.
A link to some TESTS i.e Sony MDR-ZX330BT fully functioning Nokia BT etc
https://wiki.archlinux.org/index.php/Bl ... SA_Devices
Would be good if this project of Tempestuous and yours becomes the definitive plug and play go to implementation of Bluetooth on Linux.
Needs a lot more people to plug in their bluetooth apparatus though!
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.
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.
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
(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
- Attachments
-
- sco.png
- (16.82 KiB) Downloaded 263 times
Last edited by Smithy on Tue 22 Dec 2015, 18:47, edited 1 time in total.
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.
I suspect that the big-boy Linuxes can do this through pulse-audio.
Last edited by rcrsn51 on Tue 22 Dec 2015, 11:24, edited 1 time in total.
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/s ... bluetooth/
http://www.alsa-project.org/main/index. ... ule-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
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/s ... bluetooth/
http://www.alsa-project.org/main/index. ... ule-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
- Attachments
-
- gbtsco_0.1.1-0ubuntu1_all.png
- (5.12 KiB) Downloaded 285 times
-
- bluez-btsco_0.50-0ubuntu6_i386.png
- (45.43 KiB) Downloaded 238 times
Last edited by Smithy on Tue 22 Dec 2015, 18:50, edited 1 time in total.
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.
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.