How to Simulate Android Killing My Process

How to simulate Android killing app caused by low memory in AndroidStudio 4

I found the way:

Since AndroidStudio 4, if you run the app from AndroidStudio play button, logcat terminate button will simulate a complete stop of the app, instead of a low memory kill.

The solution is launching the app from the icon in the emulator, them that terminate button will simulate the low memory kill correctly.

How to simulate a service killed by the Android system

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.

Kill app button

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.

Programmatically simulating Android OS killing my app

You could go on your phone to Settings | Developers Options and set 'Don't keep Activities' checkbox. I'm not sure about exact wording.

This way as soon as any your Activity is in background it immediately gets killed.

Simulate killing of activity in emulator

You can pause your application (by pushing the Home button, simulating a call, whatever). Then kill the app's process through adb. Since the docs say that after onPause() returns your app can be killed without any further notice, this is a fair test.

If you don't want to go through the trouble of finding the pid of your app's process, you can use adb shell am kill com.example.package_name to kill your app's process. Make sure that the app is put in the background. The docs say that this command "kills only processes that are safe to kill and that will not impact the user experience." So you might want to launch a couple of other apps before trying this one.

How to kill android app by Android Studio

You can simply kill your app by using adb.

adb shell am force-stop <YOUR_PACKAGE>

How can I simulate Android OS killing off an Activity due to low system resources for testing

There's a section called Apps in the Developer options. Make sure Do not keep activities is on, it'll allow you to test this behavior. Just don't forget to turn it off when you're done or you will be debugging weird lifecycle behavior in your app later.