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. Does android has tomtom alike application?


I have never seen Android phone in my hands so sorry for asking silly
question but does Android phone with Google Maps and GPS provide
TomTom alike software where nice voice tells you to turn right or
left? If not is it possible to get via third party software?


2. Openintents simulator porting on TI Zoom board.


This has reference to the sensor-simulator available @http://
I use the open intents simulator to move the compass in my
application. This works perfectly fine when i install the openintents
apk on emulator.

Now, I tried to port the openintents.apk on the Texas Instrument
"Zoom" board. The board was uploaded with Kernel & Android
file system version 1.5.

BUT ....Due to some reasons the openintents apk is not appearing on
the device(the other apks are getting loaded using the same
procedure). Using ls command to view the apks installed on the device
(through PC connected to device) I do see the openintents apk, yet,
the apk is not getting visible on Zoom.

Can you please help me with this??


Best Regards,

3. About android branches (master, cupcake, ...)

4. "R cannot be resolved" after updating to 1.5 SDK Pre, and trying to compile for 1.1

5. "R cannot be resolved" after updating to 1.5 SDK Pre, and trying to compile for 1.1

6. HTTP Unnkown socket error

7. can't play wma file on a server