android studio debugging causing phone to restart

In that case it's unlikely to find any traces but hopefully this should be reproduced only on particular devices. Also reboot may be caused by hardware issues. Unfortunately it's hard to read those as on most devices console output is disabled and kmsg buffer will be erased on each reboot. You may read it from /dev/kmsg or from ADB shell: adb shell dmesg. Instead it'll write a stack trace into console. As kernel panic happens on the layer beyound Android, it won't produce any logcat output. You may see an example of logcat output by killing the service_manager process with adb shell. In rare cases watchdog can be timed out because of high memory and CPU usage.īoth are quite rare and can be reproduced mostly in monkey-testing, not real-case scenarios.It leads to errors and /data/ partition is mounted as read-only, which produces a bunch of errors. For example, in some cases after factory reset ext2 partitions aren't formatted as follows. Step 1: Hit the tab where you should see your device name but you are currently seeing no device and select Troubleshoot Device Connections from the dropdown list.

However, the actual reason sometimes may be a hardware issue. Fatal exception occured in one of system services.Watchdog killed a system_server process because of deadlock in of services it's running.In that case no reboot happens but Zygote restarts instead.

Android studio debugging causing phone to restart