OverviewConnectionsActivity is kind of a god class at the moment since it is responsible for handling all the received messages. This is due to it being a networkcommunicationlistener. However, this system is not needed since we only have one listener for the network. It will be better to let overviewconnectionsactivity mostly be responsible for the UI and handle the further processes of messages in a separate class.
So the networkcommunicationlistener can be removed and replaced by simply calling methods in two different classes: overviewConnectionsActivity for all the UI information and a new class for handling the messages.
OverviewConnectionsActivity is kind of a god class at the moment since it is responsible for handling all the received messages. This is due to it being a networkcommunicationlistener. However, this system is not needed since we only have one listener for the network. It will be better to let overviewconnectionsactivity mostly be responsible for the UI and handle the further processes of messages in a separate class.
So the networkcommunicationlistener can be removed and replaced by simply calling methods in two different classes: overviewConnectionsActivity for all the UI information and a new class for handling the messages.