java.io.IOException: Service discovery failed

[IanMc]

When you create a virtual serial Com port for bluetooth as an incoming port on the PC you can discover it from your Basic4android app but it would seem that if it is not in use ie: if it is not bound by something like a terminal application then when you try to connect to it you get the error:

java.io.IOException: Service discovery failed

And Amazon reject your app :sign0148:

Is there any way to test for this using Try Catch ?
Then I could display my own error message.

Amazon's helpful rejection email states the error as:

"BTInterfaceFreeTrialBETA Error Connecting: java.io.IOException: read Failed, Socket might closed read ret:-1" appears.


OS/Device(s)/Form Factor: 2.3.3/HTC Desire HD A9191/Phone.
4.2.1/Nexus 7/Tablet.
4.1/Samsung Galaxy Nexus/Phone.

 

[thedesolatesoul]

Yes.
Just use

Try
    SocketMagic
Catch
    If LastException.Contains("java.io.IOException: Service discovery failed") Then
       ToastMessageShow("This app is awesome, but the user is stupid",False)
    End If
End Try

 

[IanMc]

Yes but I've tried putting Try/Catches all over the place and haven't found the right place yet.

It's the same in Erel's Bluetooth Demo app.

If anyone wants to try setting up a Bluetooth serial port on their PC or Laptop then see this thread in my forum.

http://btinterface.com/BTInterface/forum/viewtopic.php?f=2&t=23

It's pretty easy, but if you don't connect the Terminal app up (link provided) then you get that error when you try to connect.

Wonder if we can do anything with the Reflection library?

 

[IanMc]

More Info

Just in case anyone needs more info on this error
and by 'anyone' I of course mean Erel

Here is the output in the log of the error when I uncheck the filter:

java.io.IOException: Service discovery failed
   at android.bluetooth.BluetoothSocket$SdpHelper.doSdp(BluetoothSocket.java:377)
   at android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:201)
   at anywheresoftware.b4a.objects.Serial$1.run(Serial.java:152)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:444)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:306)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581)
   at java.lang.Thread.run(Thread.java:1019)

:sign0188:

 

[IanMc]

Any thoughts?

Any thoughts on this?

I aim to get it fixed coz I know that anything's possible in B4a!!!

Bye the way, has anyone got themselves a nice well-paid job using B4a yet?

I think its merely a matter of time before B4a starts to get the same kudos as Visual BASIC don't you?

:sign0087:

 

[thedesolatesoul]

Can you identify what command is executed last before you get this exception?
Also does it cause the app to crash or the exception stays silently in the logs?
Is it the Listen or Listen2 command? It seems that the serial library should catch this exception.
If it is the ones of Connect methods, I think the lib still catches the exception but prints the stacktrace silenty (maybe that is what Amazon does not like).

 

[IanMc]

You sometimes have to own up to your foolishness

With help from thedesolatesoul on the JonPMs Live b4achat website I figured out... ok 'he' figured out that the error message that I'm seing here is

a) written into Erel's Serial1_Connected subroutine :BangHead: Doh!

and the log 'Error Connecting: java.io.Exception: Service discovery failed
' message is

b) written into Erel's Serial1_Connected subroutine :BangHead: Doh!



In my defence I had hidden that routine away deep in the bowels plus I was thrown by that email from the Amazon testing guys which read:

An error message "BTInterfaceFreeTrialBETA Error Connecting: java.io.IOException: read Failed, Socket might closed read ret:-1" appears.


OS/Device(s)/Form Factor: 2.3.3/HTC Desire HD A9191/Phone.
4.2.1/Nexus 7/Tablet.
4.1/Samsung Galaxy Nexus/Phone.

but hands up, I deserve to be entered into the 'lumox of the month' contest

and

no-wonder Erel didn't answer my thread he's probably just rolling his eyes and saying to himself

'users'

:sign0104:

now.... no-one reply to this thread... just let it slip gently away into oblivion ....

and... take a look at the New error message

 

[Erel]

Sorry I only see this thread now. Was a long weekend...

Is the problem solved?

 

[IanMc]

Ah yes thank you, just me missing the obvious

Thanks

 

[StarinschiAndrei]

Hi, i had a similar problem. On both devices i change the BT settings : Visible time-out = Never time out. So with this settings i didn't had the error message "java.io.IOException:Service discovery failed"

 

[gmartano68]

Hi, I get this error while try to test FileTransfer sample via bluetooth (the error occurr when I select the BT device to connect, as in png posted by Andrei) ...any suggestion to solve? I've tried to set Visible time-out = Never on both device, but error remain

 

[Erel]

I guess that you pressed on the Make Discoverable button in the second device, right?

 

[gmartano68]

Yes I pressed all buttons can be pressed

 

[Erel]

Can you post the error message from the logs (right click on the logs)?

 

[Victor Pavlov]

Hi,
We created POS system. It supports about 20 printers (Fiscal and ESC/POS). Generally it works, but some times Bluetooth connection crashes with message "java.io.IOException: Service discovery failed"

I was trying different reconnection, delays (idle for 1, 2 or 3 sec), closing and reopening the connection, but no success. Here is full source code, information is sent to first paired device. Please, assist how I can solve the problem. The printout crashes on line 94

Tested with 6 different printers, 3 devices, same result. Crash is about 1/20 of the printouts.

 

[Erel]

Have you tried to catch the error and retry to connect later?

 

[Victor Pavlov]

Yes, if you see, there is question "Reconnect", after "Yes" it tries to reconnect. But! Sometimes it cannot reconnect after 3 reties (delay = 1 sec). To check it, comment line 95 and it will reconnect and reconnect and reconnect endlessly. Does not solve the problem.

Question, it is paired device, why we need "Discovery service" ?

 

[Erel]

Question, it is paired device, why we need "Discovery service" ?

This is part of the steps required to establish a connection.

Bluetooth in Android is not perfect. You can try to disable and then enable the Bluetooth adapter to reset it. It can be done from your code (like in B4A-Bridge). It usually solves such issues.

 

[Victor Pavlov]

OK, thanx!

The connection is established with Serail class?
Do I need to re-initialize BTAdmin?

 

[Victor Pavlov]

What is the correct sequence to re-establish connection?