summaryrefslogtreecommitdiff
path: root/startop/scripts/lib/cmd_utils.py
diff options
context:
space:
mode:
authorRemi NGUYEN VAN <reminv@google.com>2019-05-28 17:29:11 +0900
committerRemi NGUYEN VAN <reminv@google.com>2019-05-30 21:52:40 +0900
commit5855ce28cff87ee35e0533c840fbce3ec5690e27 (patch)
treee9b1d1803064cd2ea7300db232691c0903f03f27 /startop/scripts/lib/cmd_utils.py
parent2966db7c0a12ecb8c8fba9edc6322515fa740b72 (diff)
Proper handling of NetworkStack crash
Instead of always crashing on userdebug builds, do the following on all builds: - If the device did not observe a NetworkStack crash in the last 6h crash the system server. This is to handle spurious crashes of the NetworkStack, so that the system can recover instead of staying without connectivity. - Otherwise, the device has had a recent crash. Notify the listeners (watchdog listener to be added) that something is seriously wrong, but do not crash to avoid bootlooping the device. This allows the watchdog to do its job, and avoids bricking the device in situations where the user could need to make emergency calls. Bug: 133725814 Test: Killed the network stack, observe reboot of framework. Test: Kill network stack again, observe nothing. Test: Wipe data, install new network stack, kill it twice: rollback. (with patch on top applied) Change-Id: If1fa00bed769eb60ca4832609006bdf15ceddb80
Diffstat (limited to 'startop/scripts/lib/cmd_utils.py')
0 files changed, 0 insertions, 0 deletions