From: Marcel Holtmann <marcel@holtmann.org>
To: Chanyeol Park <chanyeol.park@samsung.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
편도현 <dh79.pyun@samsung.com>, 서호철 <hocheol.seo@samsung.com>
Subject: Re: How does other application know bt adapter discoverabletimeout ?
Date: Wed, 04 Jan 2012 08:02:08 -0800 [thread overview]
Message-ID: <1325692928.6454.44.camel@aeonflux> (raw)
In-Reply-To: <4F044EC7.6000803@samsung.com>
Hi Chanyeol,
> regarding bluetooth discoverable timeout, I have a question.
>
> As far as I understand, if we set DiscoverableTimeout ,
> setting application should count down DiscoverableTimeout in order to
> display Timeout.
>
> But in case of other application , how could they know exact remained
> timeout?
they don't know and they also should not need know.
If you are designing a system where another application needs to know
the expired seconds of the discoverable timeout, then I would strongly
suggest to rethink the interaction design with the end user.
I would actually not even expose such a setting to the user if you are
building a phone. My current take on this is either you are always
discoverable by user choice or you are only switching on discoverability
when the user is in the Bluetooth settings menu.
The iPhone iOS for example got this part really figured. As soon as you
enter the Bluetooth settings menu, the device makes itself discoverable
and lets the user know that it did. As soon as you leave that menu or
switch to another application/home screen it goes invisible again. That
is pretty much a good design. No extra clutter or confusion for the end
user.
That said, it is not unreasonable to use the discoverable timeout, but
it should only be used from the same UI application. Doing this cross
applications is not going to work out.
Regards
Marcel
prev parent reply other threads:[~2012-01-04 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 13:06 How does other application know bt adapter discoverabletimeout ? Chanyeol Park
2012-01-04 14:47 ` Luiz Augusto von Dentz
2012-01-04 16:02 ` 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=1325692928.6454.44.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=chanyeol.park@samsung.com \
--cc=dh79.pyun@samsung.com \
--cc=hocheol.seo@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).