I do not understand this behavior at all but I have noted on the same set 
of devices as I have moved from OS 4.3 to 6.0 that discovery of Bluetooth 
Low Energy devices using the 'settings/bluetooth' option is progressively 
worse. In 5.1 and 6.0 it is so bad that there are certain devices I do not 
even discover anymore, whereas in pre-5 I have no problem discovering the 
devices.

On the other hand if I write my own scanner app I discover things fine.

The reason for using the settings/Bluetooth option (even inside my app) is 
that I need to work and pair with both classic and BTLE devices. There is 
no API for pairing in classic BT (without doing something unreliable like 
reflection). However, there is a bonding method that has been added to gatt.

Has Google made the scan rate increasingly infrequent in the 
'settings/bluetooth' option that it is practically useless? I am wondering 
if I will need to write a completely separate 'activity' for discovering 
and pairing to BTLE devices. Any info is greatly appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/c999e93a-535a-424d-9c3f-144d0837563e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to