Here's some additional clues:
Logcat says:
01-31 08:26:30.807: INFO/BluetoothEventLoop.cpp(1031):
agent_event_filter: Received method org.bluez.Agent:RequestPinCode
01-31 08:26:50.158: WARN/ActivityManager(1031): Timeout executing
service: ServiceRecord{447e6dc8 com.examples.speedpoll/.speedPoll}
I suppose an INFO diag means it's not a problem, but I'm just curious,
is it asking for a PinCode from the remote device or is the remote
device looking for a PinCode from the local device.
Regarding the WARN diag, is the service timing out on the remote
device or something I should be executing on the local device?
On Jan 27, 8:56 pm, Ron <[email protected]> wrote:
> I'm getting a connect timeout using Android as abluetoothclient
> connecting to a server device. I'm pretty sure the UUID is correct as
> I no longer get the immediate service discovery errors that I got when
> using any other UUID string. So I have two questions:
>
> 1) Is it possible to lengthen the (about) 12 second timeout for the
> socket connect?
> 2) Are there any other settings I need to be looking at to make this
> work?
>
> Thanks.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
