From: Ramagudi Naziir <naziirr@gmail.com>
To: marjnkl@comcast.net
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluetooth audio fails
Date: Tue, 17 Nov 2009 09:56:57 +0200 [thread overview]
Message-ID: <dfb262380911162356g750dfdbfu4d0b67ae3ce567c4@mail.gmail.com> (raw)
In-Reply-To: <830792141.4253161258419999163.JavaMail.root@sz0149a.westchester.pa.mail.comcast.net>
Hi Mark,
On Tue, Nov 17, 2009 at 3:06 AM, <marjnkl@comcast.net> wrote:
> Is this the agent that comes with bluez?
yes: bluez-git/test/agent.c
> You should have a directory in /var/lib/bluetooth with the mac address of your bluetooth device.
for some reason it is not being created. weird.
>> (bluetoothd:1260): GLib-CRITICAL **: g_key_file_get_boolean:
>> assertion
>> `key_file != NULL' failed
>> ...
>
> I do not get anything like this. Do you get this when you run hciconfig hci0 up?
yes
> It really seems that your bluetooth device is not fully recognized by the OS. Do you have all the drivers needed for the bluetooth device? How is your device attached (e.g usb, pci)?
it's a UART device. and it looks like it works pretty good - I got
rfcomm to work with my laptop (which means scan, connect, pair worked,
and I got a binded /dev/rfcomm0 that I could write to and read from
and see the laptop data).
Thank you!
naziir
next parent reply other threads:[~2009-11-17 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <232854869.4251721258419865790.JavaMail.root@sz0149a.westchester.pa.mail.comcast.net>
[not found] ` <830792141.4253161258419999163.JavaMail.root@sz0149a.westchester.pa.mail.comcast.net>
2009-11-17 7:56 ` Ramagudi Naziir [this message]
2009-11-14 18:26 bluetooth audio fails Ramagudi Naziir
2009-11-15 12:31 ` Ramagudi Naziir
2009-11-16 10:09 ` Ramagudi Naziir
[not found] ` <1080565272.3913901258382253455.JavaMail.root@sz0149a.westchester.pa.mail.comcast.net>
2009-11-16 19:46 ` Ramagudi Naziir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dfb262380911162356g750dfdbfu4d0b67ae3ce567c4@mail.gmail.com \
--to=naziirr@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marjnkl@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox