mqtt.io | MQTT over Socket.IO | Socket library

I have been trying to implement mqtt using hivemq in my Android app. Though I have used the same specs and configuration from their docs, I am still unable to establish a successful connection.

I was able to use paho for mqtt earlier, but it doesn't work for android Oreo and above if the app is in background because the library didn't have startServiceForeground update. So moved to HiveMq. I am just trying their sample app using the quick start guides here. 1. https://hivemq.github.io/hivemq-mqtt-client/ 2. https://www.hivemq.com/blog/mqtt-client-library-enyclopedia-hivemq-mqtt-client/ 3. https://github.com/hivemq/hivemq-mqtt-client/blob/develop/README.md Almost wasted a day to figure how to connect to their mqtt, but unsuccessful

I'm trying to set create the client first to test that the MQTT works without errors then I will implement the connect() method. I downloaded the latest version of HiveMQ (an open source MQTT implementation done in Java) and after importing the project properly as a Gradle build in Eclipse and using GIT I was greeted with an error message. It said "DaggerSingletonComponent cannot be resolved." My program can't run at all.

Link to the open source I downloaded: https://github.com/hivemq/hivemq-mqtt-client

I've tried manually editing the build files to see if there was some code left out for dagger in dependencies but there wasn't.

I am currently using EMQ as our MQTT broker. I need to get the latest "online" or simply the connection state of a client as quick as possible. Currently, I let my backend run a single client which subscribes to a $SYS topic, where the connection and disconnection event of a client will be published to as a message. When a client is connected, a connected message will be published to $SYS/.../connected. When it is disconnected, a disconnected message will be published to $SYS/.../disconnected.

The problem with this approach is that the disconnected messages will only be published immediately when the client is disconnected normally. Like, when the client closes the connection by itself intentionally. But if the disconnection is due to unreachable network or power source cut-off, then the message will be published after 3 or more minutes.

I also tried using the LWT (Last Will Testament) approach but the result is similar as the one above. So I guess that if the disconnection happens unintentionally, the client won't have a chance to tell the broker that it will disconnect itself with the broker. So, it will definitely take sometime for the broker to notice that the client is actually disconnected.

So, my question would be, how would I shorten that time? I once suspect that the "keep-alive" thing has something to do with this matter. But after a couple of experiences, it's not.