AIS targets not working in Android version 5.0

[markskaplan]

The vespar is configured as an access point.
The log file only shows NME sentences, no connection info

[markskaplan]

The vespar is configured as an access point.
The log file only shows NME sentences, no connection info

Will check logs on phones if I can find one ..

[transmitterdan]

Originally Posted by markskaplan

The vespar is configured as an access point.

The log file only shows NME sentences, no connection info



Will check logs on phones if I can find one ..

The O logs should show if connection to the server was made or not. Comparing log messages from working device and non-working ones would be useful.

The issue isn’t about access point or not. The underlying TCP service is what O tries to connect with at a certain IP and port number. That service must allow the connection.

Also, some devices have a firewall built in to prevent outgoing TCP connections on high numeric ports. Maybe your device is blocking O silently. It’s hard to say without seeing the network traffic.

[markskaplan]

The phone has a connection. The NMEA debug window shows data going by, but just no AIS messages.

I compared it to my tablet. The tablet has AIVDM messages along with the GPS ones.
The phone is missing the AIVDM ones ..

The tablet messages have the form

TCP:192.168.15.1:39150) !AIVDM ..
.... $GPGST ......

The phone ones look like this:

(Virtual $GNGGA .....

[markskaplan]

(Virtual : )

[markskaplan]

I am not sure why is says virtual instead of the IP addressort.
Maybe something unique on the pixel?
It is very strange that the AIVDM messages are not there.

[markskaplan]

Pushing off in 2 hours to head south toward bahamas. May not have a connection for a week or more. Will pick up this thread when i can.

Thank for your help.

[markskaplan]

Ignore that part about virtual.
That was the internal GPS I just figured out.
So, indeed there appears to be no connection ..

[markskaplan]

Yes checked the debug window again, nothing arriving at all.
Something strange happening in the TCP stack on the phone it appears.
I am guessing a pixel/Android issue ..