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 BluetoothAdapter.ACTION_REQUEST_DISCOVERABLE intent. 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 SCAN_MODE_CONNECTABLE_DISCOVERABLE to SCAN_MODE_CONNECTABLE. 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 secs). Env: Device: SAMSUNG-SGH-I897 Firmware: 2.1-update1 Kernel:2.6.29 Build: ECLAIR.UCJH7 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
