Active Topics

 


Reply
Thread Tools
Posts: 185 | Thanked: 5 times | Joined on Dec 2005 @ Texas
#21
Originally Posted by trevarthan View Post
Correct. To see if both a2dpd and mplayer are in fact running in the background you should be able to run `ps auxwww | grep -E 'a2|mp'` in an xterm while kagu is running and the BT button is darkened and a song is playing (check the play time in the middle right of Kagu to see if it's actually playing).



No, pairing the headphones is correct. Before running Kagu, you can check to see if the headphones are in fact connected to the n800 by pressing the bluetooth icon in the task bar at the top of the screen. If they are connected, it should say "Disconnect ..." where "..." is the name of your headphones. If they are not connected, try turning them off then back on. Sometimes the headphones need a reboot too.

Have you successfully completed step 10? If not, go back and try that. If the headphones are connected, but you can't get step 10 to work, then something is probably wrong with your config and you should go back through the steps again.

Kagu's A2DP buttKagu's A2DP button is really just a convenient way to execute step 10.
Thanks for the quick reply, trevarthan...

I figured out the problem, and I'll tell you what it was if you promise not to laugh at me too much - I never took the '#' sign away from the 'address' line where I put in the BT device address.

I knew for sure I had followed your directions, but I kept overlooking that one little symbol. What was confusing matters was that out of three devices that I successfully paired, only my Samsung WEP-200 headset would 'connect' and turn on the BT icon in the main system tray. I kept thinking the other devices were incompatible for some reason.

Anyways, the A2DP works great and the sound quality is fantastic! Much better quality than many other devices I have used. Thanks for making this feature available to us...

One quick question: am I able to add multiple BT device addresses in the prefs file, as long as they are #'ed out? This would make it very easy to switch between different devices, just a quick edit would be all it takes.
 
Posts: 262 | Thanked: 9 times | Joined on Jun 2007
#22
Originally Posted by orbitalcomp View Post
One quick question: am I able to add multiple BT device addresses in the prefs file, as long as they are #'ed out? This would make it very easy to switch between different devices, just a quick edit would be all it takes.
Yes. The '#' sign turns the line into a comment, not a command. So you can comment out any number of additional devices.

Eventually, I want to make a Control Panel configuration system for ~/.a2dprc as that would eliminate user error and make switching devices a bit easier. This howto is just the first step. Glad you got it working!
 
Frankowitz's Avatar
Posts: 218 | Thanked: 4 times | Joined on Apr 2007 @ localhost
#23
Originally Posted by trevarthan View Post
I'm sorry, but for now you'll just have to follow the instructions. They seem to work for everyone else. Perhaps you could tell us what error message `cp` is giving you?
I have no problems whatsoever. If you read carefully, you'll see that I was reacting to the post of VCi15 were he asks what 'cp' stands for.
__________________
The King is dead; long live the King! NIT out, Asus Eee PC 901 3G and BlackBerry Bold in!
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#24
Originally Posted by trevarthan View Post
Yes. The '#' sign turns the line into a comment, not a command. So you can comment out any number of additional devices.

Eventually, I want to make a Control Panel configuration system for ~/.a2dprc as that would eliminate user error and make switching devices a bit easier. This howto is just the first step. Glad you got it working!
See this thread for simplified A2DP installation instructions - please post in the installation thread if experiencing any problems or have suggestions.

EDIT: Removed original scripting instructions and replaced with link to new thread.

Last edited by Milhouse; 2007-08-03 at 18:18.
 
Posts: 185 | Thanked: 5 times | Joined on Dec 2005 @ Texas
#25
Hey Milhouse - where was this script yesterday when I was doing all of this manually? Huh??

That definitely is a good idea, simplifying the A2DP install...

On another note, I wish it was possible to route the audio from Rhapsody thru the A2DP setup...but I seriously doubt this is possible. I don't know if Rhapsody uses its own player or if it is just a front end for something else.

I have been using the BT dongle that came with my Logitech headphones if I need BT for Rhapsody, but it's one more thing for me to remember to charge.
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#26
Sorry for the delay orbitalcomp

For the time being I've hosted the script on my server www.nmacleod.com/a2dp/install.sh so once you have determined the BT Address of your headset the commands to install are as follows:

See this thread for simplified A2DP installation instructions - please post in the installation thread if experiencing any problems or have suggestions.

EDIT: Removed original instructions and replaced with link to new thread.

Last edited by Milhouse; 2007-08-03 at 18:18.
 
Posts: 24 | Thanked: 0 times | Joined on Mar 2007
#27
i got it working yesterday somehow, I think it was the command you gave me Milhouse but I think I will reformat my N800 and start from scratch with the new technique. Does that include the step 7 (Edit hcid.conf) eliminates a lot of skipping during playback
 
Posts: 24 | Thanked: 0 times | Joined on Mar 2007
#28
I remember seeing someone talk about AVCRP? is that working or still needs to be developed
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#29
Originally Posted by VCi15 View Post
Does that include the step 7 (Edit hcid.conf) eliminates a lot of skipping during playback
Yes, that step is completed when you run the script for the second time as root.

The only thing the script doesn't do is step 3 where you have to obtain your BT Address - you need to do that yourself by running "hcitool scan" then pass the relevant address as a parameter on the first invocation of install.sh.

Note that once you have a working a2dp installation you can delete the /home/user/a2dp directory and it's contents (rm -fr /home/user/a2dp).
 
Posts: 24 | Thanked: 0 times | Joined on Mar 2007
#30
so are you saying that it does step 7 if I were to run the script twice? or do you mean in the line # As user "root"
 
Reply


 
Forum Jump


All times are GMT. The time now is 10:11.