From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RFCOMM connection problem
Date: Sun, 03 Dec 2006 15:05:28 +0100 [thread overview]
Message-ID: <1165154728.19590.51.camel@localhost> (raw)
In-Reply-To: <d7dffb480611280055g6409c2ica54f78d3666674b@mail.gmail.com>
Hi,
> I am new to BlueZ, and i downloaded bluez stack and i am runnig
> test programs. I am running 'hstest.c'. It was working properly. It
> was successfully opening both rfcomm com & sco connection and
> audio(wave file) is redirecting to head set. But the problem is :
>
> AT commands passed by headset are not captured at rfcomm
> socket. Means if i press headset button, as of i understood, it should
> sned 'AT+CKPD=200\r\n'. But it is not caputured at rfcomm socket in
> the program, in the same way even volume controls(AT+VGS/M) also. I am
> not able to get those AT commands from headset. Can anybody say where
> i am wrong.
I have no idea on what you are trying to achieve or what's your problem.
So you must be more specific. However remember that hstest.c is a test
and example program and nothing you should use in production.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-12-03 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 8:55 [Bluez-devel] RFCOMM connection problem VANatFortuna amarnath
2006-12-03 14:05 ` Marcel Holtmann [this message]
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=1165154728.19590.51.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.