I've also been quite frustrated by this issue since I'm also doing activities that depend on a device being always discoverable. There is an open issue on the Android project page about this - if you (and others) would like to see this implemented please star it!
http://code.google.com/p/android/issues/detail?id=6348&q=bluetooth%20discovery&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars Moneytoo - what you say is interesting - do you mean that if my app has a specific service registered then it will respond to any peer requesting it even when it is not discoverable? However, even if it does work, from my prior experience working with BT, polling for specific services is much slower than doing regular BT discovery (and possibly more power consuming?) Nadav On Mar 16, 4:26 pm, moneytoo <m...@seznam.cz> wrote: > You can't. Try creating and connecting to specific service instead of > using discoverable mode. > > On Mar 15, 5:09 am, Rafal Z <rzaj...@gmail.com> wrote: > > > I have written a small app that puts my bluetooth in discoverable mode > > for a long time (G1 - API 1.6). I use that along with small program on > > windows to lock/unlock the computer if the phone is close by. Recently > > i try to port this app to my nexus one but it seems like i have to pop > > up the message every 300s to enable device to go to discoverable mode. > > does anyone know how i can suppress that? -- 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