http://ift.tt/17ui51i

The above is a link to a picture of the typical Android App Lifecycle.

I would assume that Android Wear follows the same Lifecycle, but I have been noticing some odd behaviors when trying to develop on Wear.

First off, I am testing using my Moto360 with the Wear Launcher installed, so this MAY play a part in it, although when I launch my app the normal way the issue still occurs.

The biggest issue I have is that multiple instances of my Main activity seem to pile on top of each other when I launch the app. On mobile, this will just bring the activity to front if it was paused, not create a new instance and put it on top of the old one.

The second issue I have is that onResume() isn't functioning as expected. To test, in the onResume() method on Wear I request a piece of data from the Mobile, then update the Wear's UI using that data. However that is never handled properly, even though the structure I have set up elsewhere works fine.

Any thoughts?