BluetoothAdapter.EXTRA_DISCOVERABLE_DURATION intent Extra does not extend 120 sec discovery interval

by Rockwell » Fri, 04 Feb 2011 05:18:24 GMT

Sponsored Links
 We documented this problem on 12/22/2010 as Issue 13361 in the Android
Issue Tracker.  There has been no response.  Has anyone else seen this
problem, and, if so, can you pls suggest a workaround?  Thanks!


300 secs was specified as the EXTRA_DISCOVERABLE_DURATION for the

As expected, the resultCode subsequently returned via
onActivityResult() was 300 -- indicating success. Also the
Settings>Wireless and network>Bluetooth settings were observed and BT
was found to be 'Visible' and the associated countdown timer started
counting down from 300. All looked fined to this point.  However,
after 120 secs elapsed (when the countdown timer read "Visible for 180
seconds") visibility was lost. At this time, the BroadcastReceiver in
our application received an ACTION_SCAN_MODE_CHANGED message
indicating that the scanmode had changed from

Though the API and the Settings display initially indicated success,
the EXTRA_DISCOVERABLE_DURATION of 300 seconds was not honored by the
system -- it evidently remains fixed at 120 seconds.

If EXTRA_DISCOVERABLE_DURATION is set to 300 seconds and the
resultCode returned in onActivityResult() is 300, then I expect BT to
be in  SCAN_MODE_CONNECTABLE_DISCOVERABLE mode for 300 secs (not 120

Device: SAMSUNG-SGH-I897
Firmware: 2.1-update1


Other Threads

1. Showing the map view before the direction list on android device.


I've been trying to start the google maps directions from my
Set intent with uri="
The defaut setting of the map with direction is to show the direction
list before the map view.
But I'd like to show the map view before showing the list.
Is there any parameter like "?view=map" or "?mode=map"?


2. play video bypass surfaceflinger


When we play a movie, the movie will decode by opencore. for example,
a 720p video will decode to 1280*720 image size. then this frame will
throw to surfaceflinger. and the sufracflinger will change the size to
display size then throw the image to copybit then show on display.

But, we don't want the 720p image to be cut as display size. we want
the 720p still is 720p then could be show on display, even the screen
will be chaos.

How could we do by this case?

Thanks for your big help.

The way we want is

open core(1280*720) -> surfaceflinger(1280*720) -> copybit(1280*720) -
> Display (1280*720)

3. Sample or Tutorial in using OpenGL in a "Live Wallpaper" in SDK 2.1?

4. Problem with ADP sensors

5. Buy one Nexus One in Argentina

6. Launching from the Camera button

7. Alarm Manager Query