Android Question TCP Socket Keepalive?

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Sep 11, 2014

• #2

You should use a timer to send a "ping" request every second.

 

Upvote 0

techknight

Well-Known Member

Licensed User

Longtime User

• Sep 11, 2014

• #3

Well if the socket closes. it wont pick back up again unless I completely reinit everything.

how do I ping the socket? Also is there a way I can test if the socket is closed? Logging Socket1.Connected shows that it is true, when clearly the server kicked the socket.

 

Last edited: Sep 11, 2014

Upvote 0

Computersmith64

Well-Known Member

Licensed User

Longtime User

• Sep 12, 2014

• #4

techknight said:

Well if the socket closes. it wont pick back up again unless I completely reinit everything.

how do I ping the socket? Also is there a way I can test if the socket is closed? Logging Socket1.Connected shows that it is true, when clearly the server kicked the socket.

Click to expand...

As Erel said, just ping it at a regular interval. Just send a "dummy" packet every x seconds (just write a single character to the AsyncStream). That should stop the connection being dropped at the other end due to inactivity.

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Sep 12, 2014

• #5

Also make sure to handle AsyncStreams Error and Terminated events. However it is possible that the connection is broken and the device doesn't yet know that the connection broke.

 

Upvote 0

techknight

Well-Known Member

Licensed User

Longtime User

• Sep 12, 2014

• #6

Well, I figured that out.

But I just got a Galaxy Tab 4, and I cant open multiple sockets for some reason. Always makes the first connection, then fails with the rest.

and the TCP performance of the first socket is overall slow.

edit: increasing socket timeout to 2500ms helped a bit. A far cry from my consistant socket of 500ms on my Tab 2.

 

Last edited: Sep 12, 2014

Upvote 0

techknight

Well-Known Member

Licensed User

Longtime User

• Sep 12, 2014

• #7

Another issue I ran across and its different across different phones/tablets.

Is this:

Astream.Write(data)
Astream.close
Socket1.Close

This code works. Most of the time. But with different hardware, especially this one, sometimes the Astream.Write doesnt finish, or doesnt get started at all before the Astream.Close event happens, or the socket close. killing off the ability to send the packet.

any ideas how to check for successful transmission before close?

 

Upvote 0

Computersmith64

Well-Known Member

Licensed User

Longtime User

• Sep 13, 2014

• #8

Are you doing this every time you write to the stream? I generally keep the stream open until I want to close the socket - but that's in a real-time game that's sending messages to & fro pretty much constantly. Dunno - perhaps try a Doevents after the Astream.Write(data) call? Or possibly move the Astream.Close & Socket1.Close to a separate sub & then call it using CallSubDelayed?

 

Upvote 0