|
Bluetooth headset help still needed
Ok, so I've now attempted to get my 3rd bluetooth headset to work with no luck. The latest is a Nokia BH-208. The pairing process seems to work fine, but in trying to switch from internal speaker to bluetooth, my bluetooth icon goes blue for a split second, then nothing. Does anyone have a step by step to clear out the registers? Any ideas would be greatly appreciated. My N810 is only 3 weeks old.
Thanks |
Re: Bluetooth headset help still needed
I've scoured all applicable posts and have tried everything to include removal of the /var/lib/bluetooth/mac address/ files, battery removal and and reboot, device renaming with out spaces... and no joy. I've even tried Nokia customer service for a go at troubleshooting and after an hour with no fix, was encouraged to send it in to the repair facility. If nobody can offer any final advice, I guess I'll just have to take my chances and send in (this brand new unit) and hope I don't get back a refurbished one.
Thanks |
Re: Bluetooth headset help still needed
Well there's not really going to be anything wrong with the N810 (unless you can't use bluetooth to do other things - talk to your phone for example). Likewise can you test your headset with your phone?
For me, the headphone pairs up when I don't want it to - in fact as soon as I switch the headset on it connects and sound is output through it. |
Re: Bluetooth headset help still needed
All three headsets work just fine when paired to my Razr. They all pair to the N810, just no sound. I did notice this. When I click on “Edit” on one of the paired devices, the “disconnect” button is always grayed out.
|
Re: Bluetooth headset help still needed
I have used 2-BH-101 headsets, and 1-BH-703 headset to pair with the N810 WiMax. The results are about the same. They pair and work on the first attempt, and after that the device is recognized, but it wont allow for sound. I think there is some sort a code issue in the driver that is getting stuck. I am totally lost as to what to do. Hope there is a solution that is feasable. Otherwise, I will have to walk around with wires around my neck. Wish I had the answer. Patiently waiting.
|
Re: Bluetooth headset help still needed
Are you saying that the bluetooth works with you N810 or just the phone?
|
Re: Bluetooth headset help still needed
Although I have been able to pair several headsets to my N810, I have never heard a single sound through the headsets. Also, I've never been able to get the headset icon to pop up.
|
Re: Bluetooth headset help still needed
Have you installed any a2dp stuff by chance?
|
Re: Bluetooth headset help still needed
Do you have FMradio installed, perchance? That can break BT HSP pretty royally. (I know the N810 has no radio, but thought you might have mistakenly installed it anyway...)
|
Re: Bluetooth headset help still needed
I'm kind of curious. Can you go to your "Control Panel" application, open "Bluetooth", tap on "Devices"? Highlight your headphone's entry in the menu and tap on "Edit".
What "Device type" and "Supported profiles" do you see listed? My thinking: I know that I had this problem ONCE. I ended up trying to fix it by deleted the device from my list on my N800, telling the headphones to completely blow away its own list of recognized trusted devices (both of my bluetooth stereo headphones have this, so I assume they all must... check your headset's manual) and then re-introduced the headphones to my N800. It then correctly identified them as capable of HFP and HSP. |
Re: Bluetooth headset help still needed
lardman: Yes. The first thing I tried to install was my Altec Lansing SoundBlade Bluetooth (a2dp) speaker.
Benson: I have verified FMradio is not installed. I only use Rhapsody and Media Player. danramos: Control panel / Bluetooth device details: Device name: PLT 510 Trusted device: (check marked) Device type: Audio/Video Supported profiles: HSP Bluetooth address: 00:03:89:FB:A5:E2 That's everything. Thanks in advance. |
Re: Bluetooth headset help still needed
right, well you might need to try disabling a2dp (e.g. "a2dp disable" in the terminal).
If I have a2dp enabled, my headset is grabbed and connected to as an a2dp device, not sure what this would do for a device which doesn't support a2dp, but no sound coming out sounds like the sort of thing. I also get the icon flashing blue then going away (which means it's doing a2dp stuff, or at least that's how I judge it) |
Re: Bluetooth headset help still needed
I had a sneaking suspicion a2dp might be the problem. Could you possibly point out the procedure for disabling it?
Thanks |
Re: Bluetooth headset help still needed
Um, not altogether sure off the top of my head, but looking at the a2dp script (in /usr/bin I imagine) which johnx's package installed should give you some clues. Look at the section which handles the "runfirst" switch and see what it changes.
Simply running "a2dp toggle" from the command line and trying the headset (if it doesn't work try toggling again) should get you up and running, though you may need to re-pair to get it working (I have to do that when developing, seems to get its knickers in a twist and not let you know why). |
Re: Bluetooth headset help still needed
Well, that was worth a try but still no joy. I downloaded and ran Johnx's a2dp-support file. I ran "a2dp runfirst" and entered my bluetooth address. Ran "a2dp enable" and enabled it. Then ran "a2dp disable" and disabled it. Then tried "a2dp toggle" a few times. Also deleted and repaired the headset a few times. Still, only sound through the N810 speakers. The bluetooth icon does however turn blue when my headset is on. I don't know how to get into the a2dp script to report what's going on there. Any other suggestions?
Thanks |
Re: Bluetooth headset help still needed
Hmm, well at least a change in behaviour. I've got a couple of non-a2dp headsets around the house, I'm not about this weekend but will take a look for you early next week and see if I can reproduce your problem (no guarantee I can fix it of course ;))
Kick me via email/irc if I don't do anything :) |
Re: Bluetooth headset help still needed
Actually you can apparently ignore the a2dp stuff, I just installed my gf's bt headset (Plantronics 360) which is not a2dp enabled and it works fine using hsp, despite the fact that a2dp is setup for my other headset (Jabra 320, something like that).
What happens when you change autostart to =true in /etc/bluetooth/audio.service (and then reboot)? |
Re: Bluetooth headset help still needed
Right, this is my process list, with the headset attached and working correctly, note the couple of bluetooth related processes. Do you have these running?
Nokia-N810-23-14:/etc/bluetooth# ps PID Uid VSZ Stat Command 1 root 1468 SW init [2] 2 root SWN [ksoftirqd/0] 3 root SW [watchdog/0] 4 root SW< [events/0] 5 root SW< [khelper] 6 root SW< [kthread] 16 root SW< [dvfs/0] 68 root SW< [kblockd/0] 69 root SW< [kseriod] 82 root SW< [OMAP McSPI/0] 90 root SW< [ksuspend_usbd] 93 root SW< [khubd] 117 root SW [pdflush] 118 root SW [pdflush] 119 root SW< [kswapd0] 120 root SW< [aio/0] 123 root SW< [mipid_esd] 248 root SW [mtdblockd] 289 root SW< [kondemand/0] 290 root SW< [kmmcd] 302 root SW< [krfcommd] 313 root SW< [mmcqd] 322 root SW< [mmcqd] 351 root 1108 SW< dsme -d -l syslog -v 4 -p /usr/lib/dsme/libstartup.so 359 root 804 SW /usr/bin/bme_RX-44 361 root 564 SW /usr/sbin/kicker 435 root DW< [cx3110x] 455 root SWN [jffs2_gcd_mtd4] 484 root 1580 SW< /sbin/udevd --daemon 690 messagebus 2440 SW< /usr/bin/dbus-daemon --system 740 root 2652 SW avahi-daemon: running [Nokia-N810-23-14.local] 746 root 2524 SW avahi-daemon: chroot helper 770 root 1708 SW /usr/sbin/avahi-dnsconfd -D 789 haldaemon 3988 SW /usr/sbin/hald 802 root 2824 SW hald-runner 812 root 2980 SW /usr/lib/hal/hald-addon-bme 814 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio 815 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio 816 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio 817 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio 818 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio 819 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio 820 root 2972 SW hald-addon-input: Listening on /dev/input/event2 /dev 821 root 2468 SW /usr/lib/hal/hald-addon-mmc 822 root 2468 SW /usr/lib/hal/hald-addon-mmc 824 root 2984 SW /usr/lib/hal/hald-addon-cpufreq 837 root 3124 SW /usr/sbin/sshd 844 root 3788 SW< /sbin/mce --force-syslog 846 messagebus 3484 SW /usr/lib/gconf2/gconfd-2 850 root 12376 SW< /usr/bin/Xomap -mouse tslib -nozap -dpi 96 -wr -nolis 877 user 1444 SW< /usr/sbin/temp-reaper 880 user 2164 SW< /usr/bin/dbus-daemon --session 884 user 7248 SW< /usr/lib/sapwood/sapwood-server 888 user 9040 SW< /usr/bin/matchbox-window-manager -theme default -use_ 896 root SW< [dsp/0] 899 root SW< [dsp/0] 902 root 3668 SW /usr/sbin/dsp_dld -p --disable-restart -c /lib/dsp/ds 959 root 4832 SW /usr/sbin/multimediad 969 root 2168 SW< /usr/bin/esd 1018 root SW< [file-storage-ga] 1022 haldaemon 2540 SW hald-addon-usb-cable: listening on /sys/devices/plat 1030 root 7884 SW< /usr/sbin/ke-recv 1048 user 21256 SW< /usr/bin/maemo-launcher --daemon --booster gtk --quie 1077 user 1448 SW< /usr/bin/hildon-input-method 1078 user 37548 SW< /usr/bin/hildon-input-method 1081 user 3944 SW< /usr/bin/clipboard-manager 1129 user 1448 SW< /usr/bin/hildon-desktop 1130 user 72716 SW< /usr/bin/hildon-desktop 1197 nobody 1808 SW< /usr/sbin/dnsmasq -k -i lo -a 127.0.0.1 -z 1200 root 5880 SW /usr/sbin/gpsdriver 1210 root 1668 SW /usr/sbin/supllistenerd 1213 root 2588 SW< /usr/sbin/hcid -n -x -s 1218 root 2508 SW< /usr/lib/bluetooth/bluetoothd-service-audio 1220 root 2444 SW< /usr/lib/bluetooth/bluetoothd-service-input 1223 root 2948 SW< /usr/bin/btcond -l 1228 root 3604 SW< /usr/sbin/wlancond 1232 root 4148 SW< /usr/sbin/icd2 -l0 1250 user 1448 SW< /usr/bin/osso-connectivity-ui-conndlgs 1251 user 31228 SW< /usr/bin/osso-connectivity-ui-conndlgs 1255 user 43344 SW< /usr/bin/osso-media-server 1279 systemui 24364 SW< /usr/bin/systemui 1283 user 3208 SW< /usr/bin/obexsrv -l 1303 user 5252 SW /usr/bin/alarmd 1321 root 5108 SW< /usr/sbin/hulda 1322 root 3060 SW< /usr/sbin/hulda 1342 user 16856 SW /usr/bin/mediaplayer-engine 1348 user 16532 SWN /usr/bin/metalayer-crawler -F 1365 user 40636 SW /usr/sbin/browserd -d 1380 user 34888 SW /usr/libexec/gnome-vfs-daemon 6319 root 14752 SW /usr/bin/eapd 6321 root 1472 SW< /sbin/udhcpc -i wlan0 -s /etc/udhcpc/libicd_network_i 6382 user 8688 SW /usr/bin/mission-control 6392 user 3168 SW /usr/libexec/galago-daemon 6394 user 5636 SW /usr/bin/telepathy-gabble 6396 user 3464 SW /usr/lib/galago/telepathy-feed 6398 user 6384 SW /usr/lib/telepathy/telepathy-salut 6411 user 6076 SW /usr/libexec/eds-sync 6419 user 22948 SW /usr/lib/evolution-data-server/e-addressbook-factory 6477 user 1448 SW /usr/bin/osso_rss_feed_reader --iconify 6478 user 30016 SW /usr/bin/osso_rss_feed_reader 6511 root 5684 SW sshd: root@pts/1 6513 root 1964 SW -sh 6530 root 1960 RW ps |
Re: Bluetooth headset help still needed
and FWIW, my (gf's) headset shows up with Trusted Device ticked, Device Type: Audio/Video and Supported Profiles: HSP.
|
Re: Bluetooth headset help still needed
Hallelujah brother! I went into etc/bluetooth/audio.service, changed autostart to =true, did a reboot, and it all works as it should. Sound through the N810 speakers goes off, sound comes through the headset, and I now for the first time get a headset icon on the screen. The sound quality is average at best, but this is what I expected as I primarily use the headset for news/talk radio.
Thanks to all! |
Re: Bluetooth headset help still needed
I'm going to add a bug about this (or you can do so), which should get some information about why it's setup like this. But, I need to know your software version (Control Panel > General > About product).
|
Re: Bluetooth headset help still needed
lardman, I'll let you add the bug report. Software version: 5.2008.43-7 and that's on a N810 WiMAX Edition.
Thanks |
Re: Bluetooth headset help still needed
Thanks :)
https://bugs.maemo.org/show_bug.cgi?id=4012 We'll wait and see if this was a mistake, or if there's some reason why it's disabled. |
Re: Bluetooth headset help still needed
Does anybody have just a set of clear instructions and packages for a2dp with Diablo that I could try to implement on my N800? I get the impression that a lot of this is early to late 2007 stuff and I'm not sure that I should be doing anything with Diablo. What about DSP SBC? Should I try that? I see they're newish but are there any clear instructions anywhere for that?
|
Re: Bluetooth headset help still needed
Holy cow! a WiMAX edition having HSP disabled... I've been wondering about this; if it had been stated that this case was a WiMAX, I overlooked it until now. And now I guess we have an explanation on why.
Does make me wonder about Nokia's spec page, though; No, my bad. The profiles list on the N810W page actually has a null element where HSP is on the N810 page. :rolleyes: |
Re: Bluetooth headset help still needed
Quote:
Quote:
|
Re: Bluetooth headset help still needed
Hello, I'm new here (as well as to linux) and have the same exact problem the original poster had. I've managed to figure out how to get to the /etc/bluetooth folder but I don't see the audio.service file. The files that I find are the following:
audio.conf hcid.conf input.service network.service serial.service Where is the audio.service file? If it makes any difference, I have an N810 wimax running the latest diablo, bluetooth turned on, no fm radio, and no a2dp. Also, how would I go about changing the autostart attribute to true? Keep in mind this is the second day that I've started looking at linux. |
Re: Bluetooth headset help still needed
I am also a newbie and having the same problem with my N810 Wimax. I go to Web and type in the etc/bluetooth/audio.service and it comes up with the following data:
[Bluetooth Service] Identifier=audio Name=Audio service Description=Bluetooth Audio service Autostart=false How do I edit the file from Autostart=false to Autostart=true and save it? I appreciate the help! Kimberly |
Re: Bluetooth headset help still needed
@kmyck1:
Well first of all check and see if the file exists: Open the terminal, then use the "cd" command to change to the correct directory. I.e. cd /etc/bluetooth/ Then use the "ls" command to list the files which are in there: ls Then you'll need to enable gainroot somehow (any suggestions anyone, I'd say go for R&D mode, but that's probably not for beginners) and use "vi" to edit the file (again, not really for beginners). There must be an easier way though, for users to use. @Kunfuscious: That's interesting. Have you tried pairing with a headset? Perhaps the file is only created once you've tried that? |
Re: Bluetooth headset help still needed
Quote:
If you have rootsh: sudo gainroot apt-get install mc mc Or install from appmanger and start from menu, but you have to be root to edit things in /etc (the step with sudo gainroot) so the command line way is recommended then browse to your file. With F4 you can edit this file. In the editor you can save with F2 and leave with F10. |
Re: Bluetooth headset help still needed
I find it kinda funny that I'm learning so much about linux just so I can pair my bluetooth headset with my N810.
lardman - Yes, I've tried pairing with my headset. I can manage to register the headset as a trusted device, but everytime I try pairing it the bluetooth icon turns blue for a second then goes back to white. After a few days I've managed to learn a lot about how linux is layed out through the command line. I've explored the files in the /var/lib/bluetooth/NN:... folder and find my headset's mac address registered. Using nano, I tried creating a new audio.service file wih what just about everyone finds in the file but then hit the non-root access limit. Today I'll try gaining root and tell you all if anything changes. |
Re: Bluetooth headset help still needed
To make your life easy, I'd install ssh from the application manager (secure shell, so you can get a terminal remotely), then you can type from a PC (Putty is a Windows app which includes an ssh client - I assume you use Windows).
With ssh you can just log straight in as root (password is "rootme" by default). |
Re: Bluetooth headset help still needed
I am way super newbie here, so please bare with me :D - I am unable to load the mc program - application manager states that it is corrupt. I have tried for hours to locate various other apps - i.e., GetRoot - with no luck.
I can get to X Terminal - but at that point, I am at a loss. If I type: sudo gainroot It states that I need to enable RD mode...???:confused: How is that done???:confused: ...I've also look for SSH in the Application Manager - don't see it there to load up...uuugghh....:eek: I agree, it does seem silly to spend this much time to get a headset to work, but I bought the unit mainly to use with Skype...so a headset is important. I really appreciate all of the help!!! Thank you!!! Kimberly |
Re: Bluetooth headset help still needed
Yeah!!! I got root!!! I was finally able to install easyroot and am in X Terminal.
Now, what command do I type to edit the etc/bluetooth/audio.services file to change the false to true??? Thanks! |
Re: Bluetooth headset help still needed
I recommend you install "sudser" to get the ability work with files that are owned by root. Also get http://nitapps.com/dists/chinook/use....0.6_armel.deb to get nano a terminal editor. You would then, in a terminal, run "sudo nano /etc/bluetooth/audio.services". Nano's editor commands are displayed at the bottom of the nano screen.
|
Re: Bluetooth headset help still needed
+1 to installing something like nano, vi (which comes out of the box) is difficult (try Googling for it and see what I mean ;))
To answer your previous questions, just fyi: Quote:
Quote:
Quote:
|
Re: Bluetooth headset help still needed
Hazzah, it actually works!
After using easyroot to gain root access, I used nano to create the audio.service file that everyone else seems to have. After a reboot, I tried pairing the headset and everything seems to be working in perfect order. As many headaches it caused, this headset problem has taught me a great deal about linux. Nano is definitely a much better editor than vi, too. I think I'll keep going on with my linux education and start learning about this whole ssh deal; it seems to pop up in quite a bit of the forum threads. Any other suggestions on what I should be researching? Don't really have a goal in mind, just would like more general knowledge. |
Re: Bluetooth headset help still needed
Things are best learned when you have a real application for them. Come up with a list of information or communication need you have and work on those. Being new to Linux I recommend that you learn CLI by examining things. For the most part make changes with the GUI. It will all come together for you over time. Another good thing to do is to scan forums like this one to see if anything posts interest or apply to you. One thing you'll learn is that not all people that offer help actually understand what they're suggesting or are pehaps offering help that applied to a different problem or release of Linux than you are using. When ever you take advice fully reseach it to make you understand what your actions will do.
|
Re: Bluetooth headset help still needed
SUCCESS!!! I want to thank you all for the awesome support and guidance! I would never have been able to do this without it!!! :D
Linux is very interesting and if I weren't facing six classes this semester, I'd love to delve into it a lot more - but for now that'll have to wait. I have one more question - how do I delete files that I created while trying to figure this out??? Thank you all again!!! Kimberly |
Re: Bluetooth headset help still needed
The most straitforward way is to install emelFM2 which is a GUI file manager that can deal with the entire disk structure unlike the File Manager that comes with the N810 and only shows you files created with the GUI. On the CLI you can use "rm {file}" to remove a file. rmdir is for deleting empty folders. You can get emelFM2 at http://wardenclyffetower.com/MaemoFi...-rev29.all.deb
|
| All times are GMT. The time now is 08:14. |
vBulletin® Version 3.8.8