c458ce98ce
Added a config option to allow the lid switch to turn off the screen. This is a closer match to what a lid switch should be doing. Removed an old feature to bypass keyguard when keyboard is visible because the way it was plumbed in made bad assumptions about the meaning of the lid switch. Also, the last product we shipped that had a physical keyboard turned this config option off. So away it goes. We can bring it back someday if we really want it. It's questionable how useful the feature is anyhow, since it only works when the keyguard is unsecure and when the lid switch is unlikely to be jostled in the user's pocket. Fixed a bug where we would tell the power manager that the keyboard was visible even if the lid switch did not control the keyboard. This used to cause the power manager to try to set the keyboard brightness, which doesn't work. Bug: 6377115 Bug: 6406726 Change-Id: Ic84b71d09563d51c92cd1cf132fa8bdee6509103
Unit tests for runtime resource overlay ======================================= As of this writing, runtime resource overlay is only triggered for /system/framework/framework-res.apk. Because of this, installation of overlay packages require the Android platform be rebooted. However, the regular unit tests (triggered via development/testrunner/runtest.py) cannot handle reboots. As a workaround, this directory contains a shell script which will trigger the tests in a non-standard way. Once runtime resource overlay may be applied to applications, the tests in this directory should be moved to core/tests/coretests. Also, by applying runtime resource overlay to a dedicated test application, the test cases would not need to assume default values for non-overlaid resources.