Instant fails on connectivity check

[A1ix]

It appears that in some situations, running a connectivity check which is triggered by a disconnect of wifi results in connectivity check instantly failing instead of waiting until the timeout period expires. This is easily worked around by adding a several second wait beforehand, but it would be nice if the connection check had this built in.

 

[Abalsam]

It appears that in some situations, running a connectivity check which is triggered by a disconnect of wifi results in connectivity check instantly failing instead of waiting until the timeout period expires. This is easily worked around by adding a several second wait beforehand, but it would be nice if the connection check had this built in.

The instant fail could be the result of not having any active connection (so it sounds like it is working as intended).

 

[MacroDroidDev]

Indeed the connectivity check should instant fail if there is no connection at that time. The timeout is for situations where a connection may be very bad (e.g. very low bandwidth or lots of packet loss etc.) so you can specify how long before it gives up and defaults to no connection.