diff options
author | Ken Sumrall <ksumrall@android.com> | 2011-01-30 19:06:03 -0800 |
---|---|---|
committer | Ken Sumrall <ksumrall@android.com> | 2011-01-30 19:10:07 -0800 |
commit | 5d4c68e40700424b65a4331be75620706a0dd49c (patch) | |
tree | f19cf38b6b8b1e3588501ae424f9726f99f54e8a /Android.mk | |
parent | 3f476690eaef3b824255813ed335284ef9a90e91 (diff) | |
download | system_vold-5d4c68e40700424b65a4331be75620706a0dd49c.tar.gz system_vold-5d4c68e40700424b65a4331be75620706a0dd49c.tar.bz2 system_vold-5d4c68e40700424b65a4331be75620706a0dd49c.zip |
Have vold grab a partial wakelock when encrypting
The Progress bar UI grabs a full wakelock when encrypting, but we've seen
a case where it looks like the progress bar UI crashes, and the wakelock is
lost, and then all hell breaks loose. The enablecrypto command has a lot of
work to do, and it will take some time, so it should grab a wakelock to
ensure it can finish without being interrupted and put to sleep.
It grabs a partial wake lock, as it doesn't need the screen to be on to do
its work. If the UI wants to keep it on, it should also grab a full wakelock,
which it does. If the UI crashes, the screen may turn off, but the encryption
will keep going, and vold will reboot the device when it's done.
Change-Id: I51d3a72b8c77383044a3facb1604c1ee510733ae
Diffstat (limited to 'Android.mk')
-rw-r--r-- | Android.mk | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -33,6 +33,7 @@ common_shared_libraries := \ libsysutils \ libcutils \ libdiskconfig \ + libhardware_legacy \ libcrypto include $(CLEAR_VARS) |