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 Sat 24 Feb 2018, 08:25
All times are UTC - 4
 Forum index » House Training » HOWTO ( Solutions )
Bluetooth + streaming for tahrpup 6.x
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 9 [130 Posts]   Goto page: Previous 1, 2, 3, 4, ..., 7, 8, 9 Next
Author Message
Philh

Joined: 17 May 2006
Posts: 134
Location: England

PostPosted: Fri 30 Jan 2015, 17:01    Post subject:  

Its like the computer thinks its paired but the amp is waiting for some return.
It times out after 2 minutes and says not connected.

But I have found a way of connecting reliably. Just from searching on the net.
Though Im sure there must be a way without turning the amp off and on.
hciconfig hci0 piscan enables iscan to make the computer dongle discoverable.
Then after I run bluetooth-agent I turn the amp off and on.
It goes into pairing, gets authorized and connects

# hcitool scan
Scanning ...
00:1D:DF:86:67:98 CR-H260i
# bluez-simple-agent hci0 00:1D:DF:86:67:98
RequestPinCode (/org/bluez/31303/hci0/dev_00_1D_DF_86_67_98)
Enter PIN Code: 0000
Release
New device (/org/bluez/31303/hci0/dev_00_1D_DF_86_67_98)
# hciconfig hci0 piscan
# bluetooth-agent 0000
Authorizing request for /org/bluez/31303/hci0/dev_00_1D_DF_86_67_98
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11835
Location: Stratford, Ontario

PostPosted: Fri 30 Jan 2015, 17:26    Post subject:  

Excellent. This is another piece of the puzzle to using BT in Puppy.
Back to top
View user's profile Send private message 
pchan

Joined: 12 Oct 2012
Posts: 130
Location: Kuala Lumpur, Malaysia

PostPosted: Sat 31 Jan 2015, 14:33    Post subject:  

rcrsn51 wrote:
I don't understand that. In Tahrpup NO-PAE, I installed the rtl8192ce_tahrpup_nopae-k3.14.20.pet and the rtl8192ce_btcoexist_tahrpup_nopae-k3.14.20.pet.

I ran "modprobe rtl8192ce" and "modprobe btcoexist". I did NOT get that error. You should not need to run the first modprobe command because the module would automatically load on your machine, since it has the device. Maybe a reboot is necessary?

Boot up a Linux where your BT headphones work and run "lsmod". Is btcoexist being loaded?

Quote:
Bus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

I own two external BT dongles with this identical chip. Both work OOTB. Something is blocking your internal device.


Sorry, I didn't notice that you suggested to run "lsmod" ...

I have been spending my time with LinuxLite instead of puppy these days because i wanted to enjoy my Bluetooth headset.

Anyway, attached is my lsmod of Linux Lite v2.2 (Ubuntu based distro).

It is good to hear that bluetooth dongles do work at least. it gives me hope that i can use puppy and bluetooth headset if I can turn off my in built bluetooth and buy a bluetooth dongle. These dongles are not so expensive these days I think. But, will try whatever possible first to see if the inbuilt bluetooth can be used. In other linux distro it is quite easy to set up the bluetooth headsets, I wonder why it is not so in puppy linux.

I wonder if i am doing something wrong. I noticed that there is a bluetooth Tahr.sfs around somewhere. Should I also load this before installing the bt coexist pet???
lsmod.zip
Description 
zip

 Download 
Filename  lsmod.zip 
Filesize  1.14 KB 
Downloaded  306 Time(s) 
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11835
Location: Stratford, Ontario

PostPosted: Sat 31 Jan 2015, 14:56    Post subject:  

Your LinuxLite is not using btcoexist, so that's not the issue.

Are you also running Tahrpup in Vbox? It's hard to track down hardware problems in that environment.

All you need to test this is a clean install of Tahrpup and the bluez-streaming PET by tempestuous.
Back to top
View user's profile Send private message 
pchan

Joined: 12 Oct 2012
Posts: 130
Location: Kuala Lumpur, Malaysia

PostPosted: Sat 31 Jan 2015, 15:44    Post subject:  

rcrsn51 wrote:
Your LinuxLite is not using btcoexist, so that's not the issue.

Are you also running Tahrpup in Vbox? It's hard to track down hardware problems in that environment.

All you need to test this is a clean install of Tahrpup and the bluez-streaming PET by tempestuous.


No, i am not running tahrpup in a vbox. I think i will give bluez-streaming from tempestuous a good try tomorrow. it did give a positive result when I ran "rfkill" indicating that bluetooth was detected and not blocked. Only problem is no scanning for MAC of headset. What could I have done wrong? Load bluetooth Tahr.sfs together perhaps?

Thanks
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11835
Location: Stratford, Ontario

PostPosted: Sat 31 Jan 2015, 16:38    Post subject:  

pchan wrote:
What could I have done wrong? Load bluetooth Tahr.sfs together perhaps?

rcrsn51 wrote:
All you need to test this is a clean install of Tahrpup and the bluez-streaming PET by tempestuous.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5468
Location: Australia

PostPosted: Sun 01 Feb 2015, 02:42    Post subject:  

pchan wrote:
# lsusb
Bus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

# hcitool scan
Device is not available: No such device

Yes, I don't think the problem is related to a conflict with the wifi device.
A Google search for that USB device ID reveals many failures under Linux, and a variety of patches to the bluetooth kernel modules to fix the problems ... although tahrpup's 3.14.20 kernel should be OK ??

pchan, I wonder if you can't bring your USB interface to life just with this command -
Code:
hciconfig hci0 up

If that appears to fail, try these more comprehensive options -
Code:
hciconfig hci0 down
hciconfig hci0 reset
hciconfig hci0 up

If any of that appears successful, go ahead and try -
Code:
hcitool scan
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11835
Location: Stratford, Ontario

PostPosted: Sun 01 Feb 2015, 10:59    Post subject:  

tempestuous wrote:
pchan, I wonder if you can't bring your USB interface to life just with this command -
Code:
hciconfig hci0 up

I can confirm the following with my external adapter. If I run "hiconfig hci0 down", the adapter disappears from "hcitool dev" and nothing else works. Once I bring it back up, things start working again. Hopefully, that's all that pchan needs.

I suspect that if your BT adapter does not appear in "rfkill list", you are out of luck. You have an incompatible adapter.

I found that bluez-simple-agent is a bit fragile. It will survive several reboots, then quit connecting. So I wrote a little re-pair script that may help.

Code:
#!/bin/sh
echo 0000 | bluez-simple-agent hci0 XX:XX:XX remove
aplay -D btheadset /usr/share/audio/2barks.wav
Back to top
View user's profile Send private message 
pchan

Joined: 12 Oct 2012
Posts: 130
Location: Kuala Lumpur, Malaysia

PostPosted: Sun 01 Feb 2015, 18:23    Post subject:  

[quote="tempestuous"]
pchan wrote:


pchan, I wonder if you can't bring your USB interface to life just with this command -
Code:
hciconfig hci0 up

If that appears to fail, try these more comprehensive options -
Code:
hciconfig hci0 down
hciconfig hci0 reset
hciconfig hci0 up

If any of that appears successful, go ahead and try -
Code:
hcitool scan


tempestuous and rcrsn51,


NOTE : Testing done in LxTahr 14.12 no Pae (will try in Tahr 6.01 no pae testing tomorrow)

Okay. Some progress here.

I ran " hcicinfig hci0 up
Then
"Hcitool scan"

Scanning started ....

Located headset MAC (14:07:24:33:08:2A) !!!

Next
"bluez-simple-agent hci0 14:07:24:33:08:2A"

.................
.....................
.................
connection refused. (oh Oh!)

Tried
tempestuous wrote:

hciconfig hci0 piscan
bluetooth-agent 0000

then power-off / power-on your bluetooth receiver. Hopefully it will now show that it is paired.


But not successful ...

Positive development : scanning is OK.
Issue : connection refused.
scan.zip
Description 
zip

 Download 
Filename  scan.zip 
Filesize  562 Bytes 
Downloaded  291 Time(s) 
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5468
Location: Australia

PostPosted: Sun 01 Feb 2015, 21:53    Post subject:  

OK, some good progress.
pchan wrote:
"bluez-simple-agent hci0 14:07:24:33:08:2A"
.................
connection refused.

It sounds like your bluetooth headset needs to authorise the pairing. Is there an instruction manual that came with that device? Maybe there's some particular button you need to press at that point?
I would make a guess there's an LED on the headset which might flash or remain on to indicate pairing status.
Back to top
View user's profile Send private message 
pchan

Joined: 12 Oct 2012
Posts: 130
Location: Kuala Lumpur, Malaysia

PostPosted: Mon 02 Feb 2015, 05:28    Post subject:  

tempestuous and rcrsn51,

I am too excited to write this report.

Very happy indeed!

I tried again "bluez_4.101-streaming.pet" using fresh Tahrpup 6.01 testing no pae.

Straightaway > "hciconfig hci0 up" before "hcitool scan"

sh-4.3# rfkill list
0: phy0: wlan
Soft blocked: no
Hard blocked: no
1: hci0: bluetooth
Soft blocked: no
Hard blocked: no
sh-4.3# hciconfig hci0 up
sh-4.3# hcitool scan
Scanning ...
14:07:24:33:08:2A H
88:53:2E:33:75:D3 YUYI-VAIO
30:A8:DB:02:95:69 Xperia E1
sh-4.3# bluez-simple-agent hci0 14:07:24:33:08:2A
Release
New device (/org/bluez/30268/hci0/dev_14_07_24_33_08_2A)



PAIRING SUCCESS!

Edited /etc/asound.conf : "XX:XX:XX:XX:XX:XX" -- > "14:07:24:33:08:2A"

Open Dead beef > edit . preference > bluetooth headset >

music.mp3 played successfully through bluetooth headset!!!!

The impossible (to me) became possible once again thanks to

tempestuous and rcrsn51,

Now, I am so scared to lose this setup.

I like distros like Linux lite but there is something so nice about puppies.

Installations in case of mess up is just a matter of extracting ISO and setting up grub. If i mess up my Linux lite, ..... (hopefully i won't) , I have to go through all the reinstall, updates, etc etc. (ie unless I keep on remastersys it up to date)

So, it looks like I can stay with Puppy after all.

Of course, thanks also to barryK, 666philb, peebee, rg66 whose puppies i follow closely.
Back to top
View user's profile Send private message 
pchan

Joined: 12 Oct 2012
Posts: 130
Location: Kuala Lumpur, Malaysia

PostPosted: Mon 02 Feb 2015, 05:41    Post subject:  

rcrsn51 wrote:


Code:
#!/bin/sh
echo 0000 | bluez-simple-agent hci0 XX:XX:XX remove
aplay -D btheadset /usr/share/audio/2barks.wav


rcrsn51,

How do i use this re pair script in case i need it?

Change "hci0 XX.XX.XX" to "hci0 my.bt headeset mac" ?
then run the whole script in terminal?

right click in rox manager > new script > add the folowing lines >

#!/bin/sh
echo 0000 | bluez-simple-agent hci0 14:07:24:33:08:2A remove
aplay -D btheadset /usr/share/audio/2barks.wav

named it "pair_again"

Why the word, "remove" if it is to pair again? Does it mean - after this need to run

"bluez-simple-agent hci0 14:07:24:33:08:2A" again ???

sorry to ask but I am a complete dummy on computer technology matters.

Thanks

Last edited by pchan on Mon 02 Feb 2015, 08:56; edited 2 times in total
Back to top
View user's profile Send private message 
pchan

Joined: 12 Oct 2012
Posts: 130
Location: Kuala Lumpur, Malaysia

PostPosted: Mon 02 Feb 2015, 06:13    Post subject:  

Oh no,

Another issue cropped up.

Deadbeef was OK. Even after restart, pairing was maintained.

smplayer 14.9.0 > under preference > audio output > options to choose bluetooth headset never showed up.

In VLC 2.1.4 > tried alsa audio output > bt headset > nothing.
(Difficult to understand why DeadBeef can but VLC cannot ... )

In my multi soundcard system , i can only get sound using wired headset and speaker if I select card 2. SB (HDA ATI SB) device 0: ALC269VB Analog [ALC269VB Analog]

will have to download and try gnome mplayer or something maybe.

>
EDIT : (SOLVED FOR VLC) > preference > all > Audio > output modules > ALSA > Audio output channels > change from stereo to mono > Successful transfer of sound to bluetooth headset!
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5468
Location: Australia

PostPosted: Mon 02 Feb 2015, 10:09    Post subject:  

pchan wrote:
smplayer 14.9.0 > under preference > audio output > options to choose bluetooth headset never showed up.

It might be that the authors of the smplayer gui failed to accommodate all possible options.
But you should be able to "hard-code" the smplayer configuration file - open /root/.config/smplayer/smplayer.ini in Geany, and find the line that starts with -
Code:
driver\audio_output=...

change it to -
Code:
driver\audio_output="alsa:device=bluetooth"

Make sure you include the quotation marks. Save.
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11835
Location: Stratford, Ontario

PostPosted: Mon 02 Feb 2015, 10:19    Post subject:  

@pchan: This is great news! I was starting to worry.

I did some testing in LxTahrpup and also had flaky results. I don't know why it would be different.

I also had some trouble with VLC. In the post here there is an asound.conf with some "default" sections. It may work better for you.

I actually had some bad experiences with my external BT dongle. At one point, it got confused and needed the hciconfig up|down|reset procedure. But then bluez-simple-agent would crash! It needed a full COLD reboot to get working again. But once I had a successful pairing, it was stable.

Regarding the re-pair script.

1. Go to your /root/my-applications/bin folder.
2. Start a script called btrepair.
3. Add the code, but replace XX:XX:XX with the address that you used to set up the pairing.
4. To run it, open a terminal and type: btrepair

"Remove" is needed to remove the old pairing from the database before adding the new pairing.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 9 [130 Posts]   Goto page: Previous 1, 2, 3, 4, ..., 7, 8, 9 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » HOWTO ( Solutions )
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.0777s ][ Queries: 13 (0.0203s) ][ GZIP on ]