705ffd1efe529bb291e90fa06e92c8090ee98627 |
|
22-Jul-2015 |
Yusuke Sato <yusukes@google.com> |
Distinguish user-requested shutdown from power-related ones With this patch, when the user requested shutdown, PowerManagerService sets sys.powerctl is set to "shutdown,userrequested", and init runs fsck on shutdown. When shutdown is triggered due to a low power state etc., the service sets the property to "shutdown,", and init immediately shuts down the system without running the command. This is a follow-up CL for http://r.android.com/158525. Bug: 21853106 Change-Id: Iae72990130fe9aa479c802f77301438190dbbfb3
/frameworks/base/core/java/com/android/internal/app/ShutdownActivity.java
|
b182955a1eabc30d3cf70856f838b46a91c34569 |
|
05-Jan-2015 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #18901214: APR: Frequent crash in android The ShutdownActivity was implemented in the system server code, which is no longer part of the boot class path. This would work fine when requesting a shutdown from the primary user, since in that case the activity would be loaded in to the main system process which also has the system service code loaded. However, when executed from a secondary user, we need to spin up a new system process for it; that system process is just a regular app process, without the system service code, so *boom*. To fix this, move ShutdownActivity to the framework jar. Change-Id: Icb831cd6ed619da5feede5605c45ef177a892fbc
/frameworks/base/core/java/com/android/internal/app/ShutdownActivity.java
|