From: Johan Hedberg <johan.hedberg@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Battery information
Date: Fri, 6 Nov 2009 21:58:19 +0200 [thread overview]
Message-ID: <20091106195819.GA15510@jh-x301> (raw)
In-Reply-To: <1257533769.23167.194.camel@localhost.localdomain>
Hi Bastien,
On Fri, Nov 06, 2009, Bastien Nocera wrote:
> A colleague has a Samsung WEP470 headset which triggers an error from
> bluetoothd.
>
> Attached is a minimal patch to avoid the error. Would be nice if we
> could export that property through bluetoothd.
I don't really see the point of this patch. What's the benefit of
returning "OK" instead of "ERROR" in this case, especially since the
added command handler doesn't do anything? As far as I see returning
"ERROR" is the right behavior for us when we encounter a command which
we don't understand (there are also no other side effects on our side
when we send an error, i.e. the connection is allowed proceed normally).
As far as exporting the battery charge info goes, yes we could consider
that. However, I'm a bit hesitant about this since AT+CBC isn't part of
the HFP spec. It is in the 3GPP AT-command spec (TS 07.07), but even
there it's only specified to be used for querying the ME's (BlueZ in
this case) battery level. I.e. the way this headset uses it doesn't seem
to conform to any standard (or at least any that I'm aware of).
Johan
next prev parent reply other threads:[~2009-11-06 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 18:56 Battery information Bastien Nocera
2009-11-06 19:58 ` Johan Hedberg [this message]
2009-11-06 20:15 ` Bastien Nocera
2009-11-06 20:54 ` Johan Hedberg
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=20091106195819.GA15510@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/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