The authentication worker will be responsible for initiating any secondary activities (likely through a navigation controller).

(ViewModel and LiveData are decorating your model -the thing doing the work- of course) The communication (and only that) between the login activity and the authentication check would be done via ViewModel+LiveData (e.g show progress, disable.enable views, etc.).The authentication check would happen on a background worker/ async task.shows an error state and prompts the user to retry.A Login screen that initiates an online authentication check, and.The ViewModel and LiveData classes are there to keep your data and display (activity/fragment/view) in sync with each other, and I'm getting the idea that you are trying to use iot for background processing, when there are better ways of doing that. In fact everything I've read would indicate to me that this is something you should not do. If there is no response, either the service is not running/started or the app is not. I've even looked through the 'googlesamples/android-architecture' repository. This results in the scanner connection state broadcasts as listed above. Which sample did you base your project on? I've looked though all of them and I cannot find one that uses the libraries in the way you have done.

Sorry to take so long but my area has been plagued by power cuts necessitating that I spend the time I had available on my own projects.

Android studio intent not working