Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 19 Jan 2017, 00:46
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
PuppyBT - a Bluetooth Manager for Various Puppies
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 5 [67 Posts]   Goto page: 1, 2, 3, 4, 5 Next
Author Message
fr33land

Joined: 25 Jun 2015
Posts: 45

PostPosted: Mon 12 Dec 2016, 08:30    Post subject:  PuppyBT - a Bluetooth Manager for Various Puppies  

Project withdrawn due to insufficient testing.
Last edited by fr33land on Sun 08 Jan 2017, 08:31; edited 34 times in total
Back to top
View user's profile Send private message 
TeX Dog

Joined: 06 Jul 2016
Posts: 317

PostPosted: Mon 12 Dec 2016, 11:47    Post subject:  

This sounds cool, May need to clear my schedule.. oh wait, did not see a FatDog64 or Raspberry version Crying or Very sad
Back to top
View user's profile Send private message 
fr33land

Joined: 25 Jun 2015
Posts: 45

PostPosted: Mon 12 Dec 2016, 17:56    Post subject:  

TeX Dog wrote:
. oh wait, did not see a FatDog64...

Fatdog already has Bluetooth. But if you want to use this system instead, it is now part of the combo package. You will have to convert the PET to Fatdog's txz format.

Be aware that it disables the service /etc/init.d/85-bluetooth.

This version has the Speaker option.
Back to top
View user's profile Send private message 
zigbert


Joined: 29 Mar 2006
Posts: 6380
Location: Valåmoen, Norway

PostPosted: Tue 13 Dec 2016, 09:57    Post subject:  

I don't have any bluetooth devices - it seems the time has come.
Thumbs up !
Thank you

_________________
Stardust resources
Back to top
View user's profile Send private message Visit poster's website 
fr33land

Joined: 25 Jun 2015
Posts: 45

PostPosted: Tue 13 Dec 2016, 10:05    Post subject:  

@zigbert: I was able to make pMusic work by disabling the stuff that controls pequalizer.
Back to top
View user's profile Send private message 
zigbert


Joined: 29 Mar 2006
Posts: 6380
Location: Valåmoen, Norway

PostPosted: Tue 13 Dec 2016, 12:02    Post subject:  

Yes, it's pequalizer that uses /root/.asoundrc. I wonder how we could avoid this conflict...
_________________
Stardust resources
Back to top
View user's profile Send private message Visit poster's website 
fr33land

Joined: 25 Jun 2015
Posts: 45

PostPosted: Thu 15 Dec 2016, 16:25    Post subject:  

PuppyBT final posted above.
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7972
Location: Perth, Western Australia

PostPosted: Fri 16 Dec 2016, 10:53    Post subject:  

Puppy is an open source project.

The puppybt PETs contain binary executables. Will you be posting the source code?

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
fr33land

Joined: 25 Jun 2015
Posts: 45

PostPosted: Fri 16 Dec 2016, 11:49    Post subject:  

.
Last edited by fr33land on Sun 08 Jan 2017, 08:33; edited 1 time in total
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7972
Location: Perth, Western Australia

PostPosted: Sat 17 Dec 2016, 06:26    Post subject:  

fr33land wrote:
BarryK wrote:
Puppy is an open source project.

The puppybt PETs contain binary executables. Will you be posting the source code?


The sources for bluetooth_tray are attached below. The other binaries come from well-known Debian packages, like

bluez_4.99-2_i386.deb
bluez-alsa_4.99-2_i386.deb
bluez-compat_4.99-2_i386.deb
bluez-tools_0.1.38+git662e-3_i386.deb

The a2dp-alsa app is from jamesbond's blog at http://www.lightofdawn.org/wiki/wiki.cgi/files/a2dp-alsa-2016-01-02.tar.bz2


Thanks very much for that!

I will put this onto my to-do list to compile for the Raspberry Pi2 and Pi3.

I have got Quirky Linux (fork of Puppy) running on the Pi, and it is under very active development right now. Latest version is 8.1.4.
It does have a bluetooth GUI app that I knocked up, with limited testing, named BluePup, but it is a bit crude.

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
mistfire

Joined: 04 Nov 2008
Posts: 418

PostPosted: Sat 17 Dec 2016, 20:34    Post subject:  

@fr33land does the package that you given can access bluetooth HID devices and bluetooth audio devices? By the way you forgot the obexd package
Back to top
View user's profile Send private message 
fr33land

Joined: 25 Jun 2015
Posts: 45

PostPosted: Sat 17 Dec 2016, 20:59    Post subject:  

mistfire wrote:
@fr33land does the package that you given can access bluetooth HID devices and bluetooth audio devices?

1. stream audio to a portable BT speaker or headphones
2. connect BT mice and keyboards
3. tether to an Internet connection via BT

Quote:
By the way you forgot the obexd package

No I didn't. I left it out on purpose. There are better ways than obex to download files off your portable device.
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8597
Location: qld

PostPosted: Sat 17 Dec 2016, 23:06    Post subject:  

Works for me .. however I compiled all the apps natively using bluez-4.101, james a2dp source, bluez-tools (from google-code - only for bt-device) and the source supplied for the icon.

I tested a bluetooth speaker and it works. The test sound failed but who cares when gnome-mplayer played an audio track just fine.

Also streamed audio from my phone to the computer.

(later) Also tried tethering over bt with my phone, Xperia z3+ and works fine! Using it now (screen cap attached).

I have no mouse or keyboard bt devices to try .. yet.

Perhaps you could include a help file in the package for the various setup routines.

I'm trying to think of a way to get around the .asoundrc conflict with pequaliser. I was already aware of it as rcrsn51 informed me. Maybe pequaliser can detect what is in the rc file and offer the user to either overwrite the rc or disable pequaliser as a user choice with appropriate warnings.

Thanks.

Note to Barry;

Code:
./configure --prefix=/usr \
            --libdir=/usr/${LIBDIR} \
            --sysconfdir=/etc \
            --localstatedir=/var \
            --enable-alsa \
            --enable-tools \
            --enable-pand \
            --enable-hidd \
            --enable-usb \
            --enable-test


That is my configure line for bluez-4.101. (You can't use bluez-5 because it requires pulse-audio.)

You have to cherry pick 'agent' from test/ in the bluez package and rename it to bluetooth-agent. It also requires 'check' (see https://sourceforge.net/projects/check/) for the test suite to build. You can probably trim out some of the utilities that may not be needed.
bt-tether.png
 Description   bnep0 shown in tooltip
 Filesize   15.39 KB
 Viewed   579 Time(s)

bt-tether.png


_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
fr33land

Joined: 25 Jun 2015
Posts: 45

PostPosted: Sun 18 Dec 2016, 08:33    Post subject:  

@01micko: Thank you for testing. What kind of BT adapter do you have - internal or external USB?

FYI, the puppybt_slacko_570-2.1.pet and puppybt_slacko_630-2.1.pet versions were built from Slackware packages.

Puppybt_slacko64-2.1.pet is basically a clone of puppybt_tahr64-2.1.pet, which was built from Debian amd64 packages. This works fine and was easier than tracking down the 64bit Slackware stuff. The two PETs have their own compiles of a2dp-alsa.
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8597
Location: qld

PostPosted: Mon 19 Dec 2016, 02:48    Post subject:  

fr33land wrote:
@01micko: Thank you for testing. What kind of BT adapter do you have - internal or external USB?


A really cheap external model. (I have another computer with internal to test later)
Code:
# lsusb|grep -i bluetooth
Bus 005 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)


----

fr33land wrote:
FYI, the puppybt_slacko_570-2.1.pet and puppybt_slacko_630-2.1.pet versions were built from Slackware packages.


I appreciate that. I am running slacko64-6.9.6.4 (with mods) and considered it an exercise to compile what is necessary. And I made it a 'petbuild' (though not yet commited).

----

fr33land wrote:
Puppybt_slacko64-2.1.pet is basically a clone of puppybt_tahr64-2.1.pet, which was built from Debian amd64 packages. This works fine and was easier than tracking down the 64bit Slackware stuff. The two PETs have their own compiles of a2dp-alsa.


Sure. You've done well. If we can polish the gui a bit (zigbert needs bluetooth!) then it it will be a great default app in future puppy distributions, whether it be included by default or as an addition to the puppy repository.

Cheers!

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 5 [67 Posts]   Goto page: 1, 2, 3, 4, 5 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
Jump to:  

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
[ Time: 0.0515s ][ Queries: 12 (0.0047s) ][ GZIP on ]