You can define the time for which the device should be discoverable by
using the intent extra tool. Sellectinh 0 as the duration will deactivate
the timeout and leave the device visible indefinitely. (or until bluetooth
is turned off.)
Thank you Gyan for your help.
I was looking into the NDK and I wonder if perhaps I could use the
bluetooth service available there?
Sincerely,
BitsAndroidTeam
On Jun 11, 4:47 pm, Gyan gnanesh@gmail.com wrote:
Two answers:
1. Call the intended service instead of using the DISCOVERABLE
U cant make the device discoverable for more than 300 seconds using any
means.
Based on the constants mentioned in the above link, u basically define whats
ur service using the bluetooth capability for!
If u use to stream audio, you can define the BluetoothClass constant as
Audio.
NDK is also
Thank you again Gyan. I will try to take a look at the
BluetoothClass.Service to see if it is useful for me. I'm not sure
how it is used but I'll try to find out. As for the NDK, I have read
other posts regarding using NDK with bluetooth and I believe that its
not recommended. This is the site:
Have you figured out how to start the discoverable mode without having
to request the user to press YES? I am having a similar problem as
you. I wanted to have my app to be able to use the bluetooth and be
discoverable automatically and without turning off after a certain
amount of time.
Have
Two answers:
1. Call the intended service instead of using the DISCOVERABLE option.
Because every 300 seconds there will be a dialog box asking you make the
device discoverable. If you make a service call, the device need not be
discoverable to use the service.
2. There is an issue in the issue
6 matches
Mail list logo
