While developing I wanted to test the situation where the system kills a service. This is because I'm loosing connection when communicating between the Android Wear and the handheld. And I think that it is related with the system killing some services.
Does anyone have a suggestion on how to approach this?
if you're developing in Android Studio while you are running your application in android wear side try to hit the kill button displayed in the console.
When you hit this button all the threads + services + activities from this app will be destroyed. If your service is of type "STICKY" it will start by itself after you kill your application.
cdlc's answer works, but another way is if you're developing in Android Studio you can go to DDMS: Tools->Android->Android Device Monitor and press the stop button there and you will also see a sticky service restart.
If you check the developer options on an Android phone, there will be an option to show the running services. Under that option you can choose to stop any service that is running.
来源：https://stackoverflow.com/questions/33478441/how-to-simulate-a-service-killed-by-the-android-system