Skip to contentSkip to conversation

How does other application know bt adapter discoverabletimeout ?

DISCUSSION Chanyeol Park 3 participants 3 messages Jan 4, 2012 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

Hello

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?

BR
Chanyeol Park

#1 lore raw

Hi Chanyeol,

2012/1/4 Chanyeol Park <[email protected]>:

Quoted 10 lines

Hello

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?

Currently we don't emit the count down and you have to be more specific about such use case, because I don't see much of a point for e.g. a phone or IVI system to have such behavior, DiscoverableTimeout is useful for system where you dont want to set discoverable property persistently e.g. no display/ui systems such as headset or routers then you basically press some buttons and it will be discoverable for some fixed amount of time.

Signature · 1 line
Luiz Augusto von Dentz
maintainer
#2 lore raw
In reply to Chanyeol Park

Hi Chanyeol,

Quoted 8 lines

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