1d146e4493b208e2dcdd201c1a1948d3558cd5a8 |
04-Jun-2018 |
Makoto Onuki <omakoto@google.com> |
Ensure automatic battery saver won't stick Fixes: 80527470 Test: Manual tests: Test 1: (make sure automatic BS won't stick) - Set up automatic battery saver at N% - Wait until the battery goes below N% -> Battery saver will turn on - Turn off the device - Charge it until the battery goes above N% - Turn on the device - Make sure battery saver is off. Test 1: (make sure manual BS will stick) - Make sure the battery level is above the automatic threshold - Manually enable BS - Reboot - Make sure battery saver is on. Change-Id: I677fd586f6b25d0200392941cac2d13b57fe10b3
atterysaver/BatterySaverStateMachine.java
|
a50bf78fdeecedb646a5bb34fe42343c68e25c96 |
25-May-2018 |
Makoto Onuki <omakoto@google.com> |
Disable battery saver tron log by default Test: Make sure not logs are written on: logcat -b events | grep -w 1302 Test: Re-anble tron log with settings put global battery_saver_constants send_tron_log=true and make sure logs are written on: logcat -b events | grep -w 1302 Bug: 74742911 Change-Id: I1f4159b7194fbc29be7f76669aa4e53084ed27e7
atterySaverPolicy.java
|
df9f36da19ab42bb1c44dc61a8300aecea0a840d |
09-May-2018 |
Beverly <beverlyt@google.com> |
(Behind flag) Wireless charging vibration feedback - to turn vibration feedback on wireless charging: adb shell settings put global charging_vibration_enabled 1 Test: manual Bug: 74505795 Change-Id: I177bc05e75bb9e66a88b45432eee778ab619e28f
otifier.java
|
bd7a62538901e256148186006f60bd4dfa35469a |
10-May-2018 |
Makoto Onuki <omakoto@google.com> |
Rework battery saver synchronization logic - Stop using individual lock instances and use use the power manager lock. - Make sure not to access external components with the lock held, *except for settings provider*, which is already touched by the power manager and the battery service (I'm planning to re-organize things for Q: b/79580230) Fixes: 79486713 Test: atest /android/pi-dev/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/Battery*Test.java /android/pi-dev/frameworks/base/services/tests/servicestests/src/com/android/server/power/*Test.java Test: Manual test with ./development/scripts/battery_simulator.py with toggling battery saver on and off and then watch adb logcat -b all | grep -P '(battery_saving_stats|battery_saver_mode)' Change-Id: I8ecdfefe978de348ee979d765c82e3d8f0280082
atterySaverPolicy.java
owerManagerService.java
atterysaver/BatterySaverController.java
atterysaver/BatterySaverStateMachine.java
atterysaver/BatterySavingStats.java
|
a3e0e0cc6b993e98cbcfe42a85d3ab07d9857576 |
08-May-2018 |
Makoto Onuki <omakoto@google.com> |
Fix BatterySaverPolicyTest and add more accessibility test Change-Id: I90fd6cb4980d540f77c749f987678de2852d2a47 Bug: 78174280 Fixes: 79123174 Test: atest ${ANDROID_BUILD_TOP}/frameworks/base/services/tests/servicestests/src/com/android/server/power/BatterySaverPolicyTest.java Test: Manual test -- enable battery saver, enable accessibility, make sure vibration still works.
atterySaverPolicy.java
|
ebd2421c733f2bc56928f9ac2e583cac20db020b |
07-May-2018 |
Makoto Onuki <omakoto@google.com> |
EBS: Don't disable vibration when accessibility is on Note the unit test is a bit stale; I'll fix that separately, which is tracked in b/79123174. Bug: 78174280 Test: Manual test with accessibility ON/OFF Change-Id: I60aa130bbda7d7cd5bfa1146e8ab1c2b63f2c60a
atterySaverPolicy.java
|
639602ef116155834eca6d4408dfbac0c7afc24d |
01-May-2018 |
Makoto Onuki <omakoto@google.com> |
Merge "Enhance battery saver event log" into pi-dev
|
5b66df1a367c7679018e61991c6a241ba9973e6b |
30-Apr-2018 |
android-build-team Robot <android-build-team-robot@google.com> |
Merge "Revert "All users will hear charging sounds."" into pi-dev
|
431d6b4464dfa1cc52dd4118a4412579dcd4ae4d |
30-Apr-2018 |
Beverly Tai <beverlyt@google.com> |
Revert "All users will hear charging sounds." Bug: 77912907 This reverts commit 6cf3e7c41116b890104afe31c2688ccf9fadf449. Reason for revert: negative dogfood feedback Change-Id: I83873286424b93fd9994dfad2e385048cfe6e478
otifier.java
|
0f8617a646ebc33e2e85a6c61c9533393318d204 |
30-Apr-2018 |
Makoto Onuki <omakoto@google.com> |
Enhance battery saver event log - Add reason to on/off log - Add "threshold changed" event log Bug: 78833408 Test: Manual test + logcat Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/BatterySaverStateMachineTest.java Change-Id: Iddaff8dfa585923c3581552200ea2734b2c1a16d
atterysaver/BatterySaverController.java
atterysaver/BatterySaverStateMachine.java
|
6d07baf4d918ea7c8acf2292da08b0f0eedd3391 |
20-Apr-2018 |
Andrew Zeng <zenga@google.com> |
Add null check for wireless charging animation. StatusBarManagerService is not started in SystemServer on wearable devices. Bug: 78357692 Change-Id: I0e30a4996addb599b8c90aa86b5ccb5ee7d80490
otifier.java
|
6cf3e7c41116b890104afe31c2688ccf9fadf449 |
16-Apr-2018 |
Beverly <beverlyt@google.com> |
All users will hear charging sounds. Users will always hear charging sounds UNLESS the ringer is on silent/vibrate OR if dnd is on. Test: manual Bug: 77912907 Change-Id: Ia4e8de0f9de8bbbaf79cd2af8746a269ecb2e8b0
otifier.java
|
6e5eb1dfa6b73e0f6f4dc98baf88a9826e2f1d25 |
31-Mar-2018 |
Makoto Onuki <omakoto@google.com> |
Fix dead lock between AM and BatterySaverStateMachine Change-Id: If641ad1a0961376de65fdb9d557e7e2e601af389 Fixes: 77308319 Test: Boot, toggle battery saver Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/BatterySaverStateMachineTest.java
atterysaver/BatterySaverStateMachine.java
|
a3cd7b9d53cdc98952365b12a8f9d5623726ed52 |
19-Mar-2018 |
Makoto Onuki <omakoto@google.com> |
Sticky battery saver - When battery saver is enabled manually (i.e. via PM.setPowerSaveMode()), it'll stick, and we'll re-enable battery saver even after a reboot or a charge. - Extracted all battery saver state transition logic into a separate class. Fix: 75033216 Bug: 74120126 Test: Manual test with "dumpsys battery set ...." Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/BatterySaverStateMachineTest.java Change-Id: If020cd48f341b339783fe09dd35bc7199e737a52 Test: dumpsys power Test: incident_report power Test: atest CtsBatterySavingTestCases
owerManagerService.java
atterysaver/BatterySaverStateMachine.java
|
129349c8f0530765db65ded6f3975fe350938405 |
22-Mar-2018 |
Makoto Onuki <omakoto@google.com> |
Remove EBS notification Bug: 76099413 Fix: 76099413 Bug: 76020920 Fix: 76020920 Test: manual test with ./development/scripts/battery_simulator.py Change-Id: Ic51cae63703f6216224ecf00fcdabf5a325cb6ce
atterysaver/BatterySaverController.java
|
425812c8b476e302853167e5505a28155c58dd72 |
21-Mar-2018 |
Lucas Dupin <dupin@google.com> |
Merge "Renamed config_dozeAfterScreenOff" into pi-dev
|
34730143deadbccd8a81263eaaee2d0790b7bfe2 |
21-Mar-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Get rid of upperbound on wireless charging anim" into pi-dev
|
fcaab29a663cc2b18c626464e1ceae6b44e51be6 |
19-Mar-2018 |
Beverly <beverlyt@google.com> |
Get rid of upperbound on wireless charging anim Previously, if the battery percentage was above 95%, then wireless charging wouldn't turn the screen on nor play the wireless charging animation. Now the charging animation will trigger even if battery percentage is above 95%. Test: manual Change-Id: I531334548d41cba8a1a4c28dff484d3f2dfefe01 Fixes: 75029514
owerManagerService.java
irelessChargerDetector.java
|
5354cc07eb2f54783d241cf63db66f43da30d18d |
21-Mar-2018 |
Lucas Dupin <dupin@google.com> |
Renamed config_dozeAfterScreenOff New name is config_dozeAfterScreenOffByDefault Bug: 73178121 Test: make Change-Id: I6633d995e93c91a36aa5b4b153ff924964cb3595
owerManagerService.java
|
16cfe45dec96154d37b36364f67cedce16ca2484 |
08-Feb-2018 |
Lucas Dupin <dupin@google.com> |
Screen off animation SysUI can now control the screen off animation as long as config_dozeAfterScreenOff is set to false. The current implementation collapses the notification shade and moves the clock whenever the use is on the lock screen, or will fade the scrims and show the clock when the keyguard is occluded. Display state change (on, doze, doze_suspended) is delayed to let the animations occur at 60Hz. Test: atest packages/SystemUI/tests/src/com/android/systemui/doze/DozeUiTest.java Test: atest packages/SystemUI/tests/src/com/android/systemui/doze/DozeWallpaperStateTest.java Test: atest packages/SystemUI/tests/src/com/android/systemui/statusbar/phone/ScrimControllerTest.java Test: atest tests/src/com/android/systemui/statusbar/phone/DozeScrimControllerTest.java Test: atest tests/src/com/android/systemui/statusbar/phone/DozeParametersTest.java Test: atest packages/SystemUI/tests/src/com/android/systemui/keyguard/WakefulnessLifecycleTest.java Fixes: 73178121 Change-Id: Id5d964452f342d4e97bedf1084efa808604e602c
owerManagerService.java
|
7025c3c391d06de07dc7e12ab7ca033c35dd6599 |
16-Mar-2018 |
Makoto Onuki <omakoto@google.com> |
Also show "last BS off time" in dumpsys power Change-Id: I53d7727847b84b29bdc8285c50ce59def4378684 Fix: 75024658 Bug: 75024658 Test: Manual test with dumpsys power Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/BatterySavingStatsTest.java
atterysaver/BatterySavingStats.java
|
c733500d1de3db256f5f97b71920f55878b2156f |
16-Mar-2018 |
Makoto Onuki <omakoto@google.com> |
Add phenotype flag to disable battery saver tron log - Also improve dumpsys power output. Example: =============================================================================== Battery saving stats: Battery Saver state: OFF Times enabled: 4 Drain stats: Battery saver OFF ON NonDoze NonIntr: 0m 0mAh( 0%) 0.0mAh/h 0m 0mAh( 0%) 0.0mAh/h Intr: 0m 0mAh( 0%) 0.0mAh/h 0m 0mAh( 0%) 0.0mAh/h Deep NonIntr: 0m 0mAh( 0%) 0.0mAh/h 0m 0mAh( 0%) 0.0mAh/h Intr: 0m 0mAh( 0%) 0.0mAh/h 0m 0mAh( 0%) 0.0mAh/h Light NonIntr: 0m 0mAh( 0%) 0.0mAh/h 0m 0mAh( 0%) 0.0mAh/h Intr: 0m 0mAh( 0%) 0.0mAh/h 0m 0mAh( 0%) 0.0mAh/h Battery saver policy (*NOTE* they only apply when battery saver is ON): Settings: battery_saver_constants value: send_tron_log=true Settings: (overlay) value: vibration_disabled=true animation_disabled=false fullbackup_deferred=true keyvaluebackup_deferred=true firewall_disabled=false datasaver_disabled=true launch_boost_disabled=true : =============================================================================== Bug: 74742911 Fix: 75024658 Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/BatterySavingStatsTest.java Test: Manual test with "settings put global battery_saver_constants send_tron_log=true" and "settings put global battery_saver_constants send_tron_log=false" with logcat | grep 'sysui_multi.*,1302,' Change-Id: If0593273e21ace7899ac95642dc9feef2515eea1
atterySaverPolicy.java
atterysaver/BatterySavingStats.java
|
5e9f40a30e297a29f85f1fc64db0ccb6ee4ebaaf |
13-Mar-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge changes from topic "dnd_touch_sounds" into pi-dev * changes: DND touch sounds toggle does not toggle vibrations Charging sounds won't play when dnd is on
|
a71712dfa88d6b29730a1c6ab92b62e62b41b643 |
12-Mar-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Avoid changing display power state on draw wake lock" into pi-dev
|
a4539c5cf183d76db25ba3e4986c9e14720409df |
12-Mar-2018 |
Beverly <beverlyt@google.com> |
Charging sounds won't play when dnd is on Test: atest frameworks/base/services/tests/uiservicestests/src/com/android/server/notification/ZenModeHelperTest.java Bug: 74441602 Change-Id: I74e803e7fda15d6cae9dd9247261c374cb2ece8d
otifier.java
|
b55e3a126ef5a33e23176b1ac2fbe74f590cbcaa |
06-Mar-2018 |
Michael Wright <michaelwr@google.com> |
Add logging for screen timeout override. Bug: 72312560 Test: flash, see log Change-Id: I85662b567059d3c9bc2777670cef9a8f47af7465
owerManagerService.java
|
56bc6d0a479077cd4613f6deeec8be00910c24d3 |
26-Feb-2018 |
Ivan Podogov <ginkage@google.com> |
Avoid changing display power state on draw wake lock When Sidekick is controlling the display, any draw wake lock can cause a sequence of endDisplayControl/setDisplayPowerState/beginDisplayControl twice, because of DOZE_SUSPEND -> DOZE -> DOZE_SUSPEND transitions. We can avoid that by telling power manager that display is controlled by Sidekick, and draw wake locks shouldn't change the display power state. Bug: 70574675 Test: build, flash Sardine, run Stopwatch, observe logcat Change-Id: Ie4dac76606e45f0d3b62bc5890841f4f24d454d7
owerManagerService.java
|
21508865f029eb3869f112fca7d05710e62d7aad |
01-Mar-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Send ACTION_POWER_SAVE_MODE_CHANGING to secondary users too"
|
06b1df657a9fcc93a2541fca4495559dc950798e |
01-Mar-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Use start/finish app ops in window manager"
|
217f5abe76abe4735b3d67d9ad1370cf67a332e1 |
01-Mar-2018 |
Makoto Onuki <omakoto@google.com> |
Send ACTION_POWER_SAVE_MODE_CHANGING to secondary users too Change-Id: I161506575390f8e28cdfbb2d684c18e10aab5aa5 Fix: 73963359 Test: manual test on a guest user on the BS setting screen.
atterysaver/BatterySaverController.java
|
92a62e5533e816d05b8342f20114d56ddab18fc3 |
31-Jan-2018 |
Lucas Dupin <dupin@google.com> |
Add AOD to BatterySaverPolicy Test: activate/deactivate battery saver, look at AOD Test: atest packages/SystemUI/tests/src/com/android/systemui/statusbar/policy/BatteryControllerTest.java Fixes: 62797110 Change-Id: I9fc5f4fc5aa9cfd45e90e602251e4c2c863dfbcc
atterySaverPolicy.java
|
f7b4725375dfb5f6b65433f1679c44501c2478e3 |
26-Feb-2018 |
Svet Ganov <svetoslavganov@google.com> |
Use start/finish app ops in window manager Add infrastructure to app ops to specify how to treat mode_default (for now only for startOp) allowing the caller to decide of this mode should be treated as success - this is useful if the caller already performed the default permission checks which determined that the caller would perform the operation if the mode is default. This way there is a record in the app ops history that this op was performed. This is now used by the window manager service which starts/finishes ops when an alert window is shown/hidden. The window manager allows adding the window if the mode is default but the caller has the fallback permission. In this case the alert window would be shown and we want that noted in the op history. Now the window manager properly starts/finishes alert window op when an alert window is shown/hidden. This is required to allow SystemUI to badge notifications from apps showing alert windows or add a dedicated notification if the app has no notifications. Test: cts-tradefed run cts-dev -m CtsWindowManagerDeviceTestCases Added android.server.wm.AppOpAlertWindowAppOpsTest cts-tradefed run cts-dev -m CtsPermissionTestCases -t android.permission.cts.AppOpsTest bug:64085448 Change-Id: I9041b1ac287bc5f9ed11d39bb203beba80f3f0f6
otifier.java
owerManagerService.java
|
607223f3b7a1c4dc3ac995f742f8d2da50d85ffc |
19-Feb-2018 |
Narayan Kamath <narayan@google.com> |
Remove uses of libcore.util.Objects.hashCode / equals. Use public API in java.util.Objects instead. Test: make Change-Id: I413280f254743a2efa2640a2194693aeb5980605
owerManagerService.java
|
698f7a068fafa22cae782faf419ab0f6e8a31328 |
14-Feb-2018 |
Makoto Onuki <omakoto@google.com> |
Switch to tron events for battery saver logging Bug: 73293341 Bug: 73296226 Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/BatterySavingStatsTest.java Test: manual test Change-Id: I2230a4968b985a2a357b535c980deb1f8adb64df
atterysaver/BatterySavingStats.java
|
08eabcf8d57083812f8e3f9ed9f0843b779d5d6f |
13-Feb-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Send SHUTDOWN bc to registered receivers only"
|
efd14bf5a5d53be86ca1bfa81890a1bbcc75ddcb |
09-Feb-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Wireless charging on aod and lockscreen"
|
ac32c9acc3d3a09f98c6cc5d4a054daa3aa681ec |
31-Jan-2018 |
Beverly <beverlyt@google.com> |
Wireless charging on aod and lockscreen - wireless charging animation plays on aod + lockscreen - timing changes on animation based on design spec - charging feedback only given if phone is not just booted Test: manual Bug: 67598445 Change-Id: I009ff6016141bcdfe9f0392bb9a1c220ea88dfe5
owerManagerService.java
|
a36dc621ef0b86a0bd46f1d4f5a719a466ba1800 |
06-Feb-2018 |
Andreas Gampe <agampe@google.com> |
Frameworks: Annotate trivial @GuardedBy in services/core Add @GuardedBy for simple functions that require a single lock and are named XYZLocked. Derived by errorprone. Bug: 73000847 Test: m Test: m javac-check-framework RUN_ERROR_PRONE=true Change-Id: I6993325b11c71a4ec27c21935fb54a954d95455f
atterySaverPolicy.java
atterysaver/BatterySavingStats.java
atterysaver/FileUpdater.java
|
b76ed132d4758a19de38135b4faa151ca8b97116 |
08-Feb-2018 |
Makoto Onuki <omakoto@google.com> |
Update battery saving stats labels Test: build & boot Change-Id: Icd869e3bf841dee5d0cd11fefe02b966dcffb346
atterysaver/BatterySavingStats.java
|
c1313eb44d01285983975bd57f010c526ca2ff56 |
01-Feb-2018 |
Beverly <beverlyt@google.com> |
Wireless charging sound used for wired charging Test: manual (plug/unplug with charging sounds enabled) Change-Id: Ic97cd15421804ff4b6edacfc20dd81515835d58d Fixes: 70259821 Bug: 29737261
otifier.java
owerManagerService.java
|
1fc6260065697e66d755ca0ea9b2bbca62d94314 |
02-Feb-2018 |
Fyodor Kupolov <fkupolov@google.com> |
Send SHUTDOWN bc to registered receivers only Test: adb shell svc power reboot Bug: 65174075 Change-Id: I652c7564b989736c9deabd0989abdb1e44f3b78a
hutdownThread.java
|
472d8e34c9b5d68f444b72139d4afef500d73491 |
31-Jan-2018 |
Makoto Onuki <omakoto@google.com> |
Add tron counter for battery % too Bug: 72229630 Test: manual test with dumpsys power, etc Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/BatterySavingStatsTest.java Change-Id: Iec9972a65f8a71bbcc85a1c177b268e91f90c434
atterysaver/BatterySavingStats.java
|
b78bb44a87db5788a946434195483c92e3410064 |
31-Jan-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Atom: Shutdown sequence event"
|
04e9dc91d8005160fe4dcc003d61d9504dd75886 |
29-Jan-2018 |
Makoto Onuki <omakoto@google.com> |
Tron counters for battery saving stats. It adds 4 sets of the following two counters: - battery_saver_stats_seconds_XY Time spent in the current mode, in seconds. - battery_saver_stats_milliamps_XY Battery spent in the current mode, in mA. Where X = "1":battery saver ON or "0": battery saver OFF. Y = "1":device interactive or "0": device not interactive. Which are sent when either of the above states is about to change. For example, when the user turns on the screen, and turns it off in 60 seconds, and the battery level dropped 1mA during this (w/ assuming battery saver OFF), we'd send the following two values: - battery_saver_stats_seconds_01 = 60 - battery_saver_stats_milliamps_01 = 1 Bug: 72229630 Test: manual test with dumpsys power, etc Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/BatterySavingStatsTest.java Change-Id: I8ab8c395ca17b64638b2b164211528ac74e49023
atterysaver/BatterySavingStats.java
|
076218bfc0094c17f95c2e8afa4d5b2480f03f73 |
26-Jan-2018 |
Makoto Onuki <omakoto@google.com> |
Keep track of battery drain rate in various states... ... and print in dumpsys power. Bug: 72229630 Test: manual test with dumpsys power, etc Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/BatterySavingStatsTest.java Change-Id: I43949129ff03c1e0b0fa3aa603e0678b728538ee
atterySaverPolicy.java
atterysaver/BatterySaverController.java
atterysaver/BatterySavingStats.java
|
a77e198ea83ce29da50d548c03f8404ba15395c2 |
29-Jan-2018 |
Pavel Grafov <pgrafov@google.com> |
Merge "Log additional events in security log."
|
1ea4289b4d7c0feaa2a0d495d6a2266b0816bc72 |
19-Jan-2018 |
Tej Singh <singhtejinder@google.com> |
Atom: Shutdown sequence event Records start and duration of shutdown, along with reason and if it was a reboot. Test: manually verified statsd received atom. CTS test for this will be difficult, and I will investigate further later. Change-Id: I0f6b595e0e251fd0a8b38127182d055885460a55
hutdownThread.java
|
ce72ef0f5701db6848760a56b908ff66375f0efe |
10-Jan-2018 |
Pavel Grafov <pgrafov@google.com> |
Log additional events in security log. These events are required for US NIAP MDFPP v3.1 compliance. Bug: 70886042 Test: manual Change-Id: I1752469cf4c7ff499eb4356fa1c94f3146d4c9b8
hutdownThread.java
|
b93b7971994d507052ba33c54a775f33062ee5d0 |
25-Jan-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Update to the ActivityManager proto"
|
8b4e2ddc414ac9420f95487377eb83ddf22da324 |
24-Jan-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Slider always represents absolute brightness"
|
db026a28aa56d725ef40e9f785d7582f6cd774b8 |
11-Jan-2018 |
Bookatz <bookatz@google.com> |
Update to the ActivityManager proto Rename the activitymanager.proto to enums.proto, in accordance with the new convention on naming these protos. Also, changes processStateAmToProto from simplying multiplying by 100 to a switch statement, to be more future-proof. Also, changes the values of the proto's process state, to reflect that the values will not be kept in sync with ActivityManager. Note that this cl was originally started in ag/3008434, and partially fulfilled in ag/3114337. Bug: 69478930 Test: run cts-dev -m CtsStatsdHostTestCases -t android.cts.statsd.ProcStateAtomTests Change-Id: I2b3bf2552b879c74d8985338df5a57c01850cb91
owerManagerService.java
|
d846023804ddadcd692666152db420c54594ddb9 |
16-Jan-2018 |
Michael Wright <michaelwr@google.com> |
Slider always represents absolute brightness Currently the slider represents a gamma adjustment to the brightness curve when auto brightness is enabled and the absolute screen brightness when it's not. This is a fairly confusing behavior to most people, so this consolidates them to a single behavior: the slider always represents the current brightness and auto-brightness will automatically adjust it. This also moves a bunch of the brightness methods from PowerManager over to DisplayManager, since it's really the DisplayPowerController that's responsible for determining and setting the display brightness. Test: atest com.android.server.display.BrightnessMappingStrategyTest Bug: 69406898 Change-Id: I73b5982809a94cd50d563426a72d7965e923c994
owerManagerService.java
|
ae79ab9d87afcb02c0ea66493ee4c8f56b44a9e1 |
11-Dec-2017 |
Beverly <beverlyt@google.com> |
Basic workspace wireless charging animation (No animation on ambient or lockscreen yet) Test: manual (testing w/o wireless charger, set DEBUG_WIRELESS=true) Bug: 67598445 Change-Id: Ifeef72805930187b8f78e72fd44bd7da25724e0c
otifier.java
owerManagerService.java
|
82c264e0f27961523e4bd3511890bfd35a01fd7e |
12-Jan-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Battery saver: Expose location power save mode as system API"
|
84c699a4b97afdde27e9ebb0da78e14e47a51b5f |
10-Jan-2018 |
Dianne Hackborn <hackbod@google.com> |
Merge "Swap "foreground service" and "bound foreground service" proc states."
|
4ea22a2b3a83b0f34cf8c648f503cc61ac8ff228 |
10-Jan-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "ShutdownThread: Don't wait for Bluetooth"
|
10fc4fdd133c89347c38155475a3863bd12b94c4 |
20-Dec-2017 |
Dianne Hackborn <hackbod@google.com> |
Swap "foreground service" and "bound foreground service" proc states. It has become apparent that apps running foreground services is a much more important (and less common) state than all the various ways apps run in the foreground because of the system being bound to them or whatever else. So push this up about the bound foreground service state, right after the explicit TOP state. Then we can keep these together as "the app is explicitly running in the foreground for some reason", etc. Bug: 70808931 Test: CtsAppTestCases Change-Id: Icfc1905b8e3eb60ddf26118c61ec1ef095659436
owerManagerService.java
|
1f7fa067a534cd5afe1df387b8eb66932f60b9eb |
06-Jan-2018 |
Myles Watson <mylesgw@google.com> |
ShutdownThread: Don't wait for Bluetooth Bluetooth doesn't need to be shut down cleanly; shutting it down just slows down the shutdown process. Bug: 70855323 Test: Boot, shut down, boot, shut down. Change-Id: Ic2ed89dd618806adc6646066ab0956dea4a94d8e
hutdownThread.java
|
96a9256fd81857c00bb014b8e00f7d552a0ed50a |
02-Jan-2018 |
Narayan Kamath <narayan@google.com> |
Notifier: Chained attribution support for noteLongPartialWakeLock[finish|start] Test: BatteryStatsNoteTest Bug: 62390666 Change-Id: I1f393b475cb18171f4d24f8774f3509a00e2a404
otifier.java
|
01b2f0e1c856832ad2ba61a686df28ae31d38562 |
04-Jan-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Track brightness changes in nits rather than backlight values."
|
144aac9dfeb4e3f48af874b438a84261202affe1 |
21-Dec-2017 |
Michael Wright <michaelwr@google.com> |
Track brightness changes in nits rather than backlight values. For the moment, the only one that actually knows the true brightness value is the DisplayPowerController, so have that tell the BrightnessTracker directly when brightness changes. Bug: 69405990 Test: atest com.android.server.display.BrightnessTrackerTest atest com.android.server.display.BrightnessMappingStrategyTest Change-Id: Ibf4e501ce2f7b071360bfac501dbbafb3ba55fa5
owerManagerService.java
|
2f916edf5ab86075e0207e473a7158b89bf61472 |
29-Dec-2017 |
Narayan Kamath <narayan@google.com> |
PowerManagerService: Account for WorkChains in wakeLockAffectsUser. Test: Manual Bug: 62390666 Change-Id: I66274027428996a7e0f58f1cd5833de76317fd73
owerManagerService.java
|
8182202ac884331a8f0a8d5094d5aad7d9323c08 |
08-Dec-2017 |
Narayan Kamath <narayan@google.com> |
Support WorkChains for WakeLock start / stop / change events. Log WorkChains associated with a given WorkSource to statsd whenever a wakelock is acquired / released or changes. Test: WorkSourceTest, manual. Bug: 62390666 Change-Id: I1720ba8b1778d38067398caac7cf92c4d375f816
owerManagerService.java
|
af5bac3d2350dc60f645ef6ece93d6a5417c50a9 |
21-Dec-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Profile lock timeout."
|
57f0f5513b593c206d8410922a667c8c5f79b2b8 |
11-Dec-2017 |
Makoto Onuki <omakoto@google.com> |
Battery saver: Expose location power save mode as system API - Expose the location power save mode as a system API for the fuse provider to change the behavior. - Didn't choose to expose PowerManager.getPoserSaveState() because the result class seems to be a bit ugly... - Not all the modes are exposed since the two existing saving modes are implemented within the system server and system apps don't need to know them. Bug: 68769804 Test: Manual test with a test app Change-Id: I25d8e68bfb79ebbeefbc241479077389c01e0f25
atterySaverPolicy.java
atterysaver/BatterySaverLocationPlugin.java
|
4de1ad7061039aee9905a302753ee8d22cca7c72 |
06-Dec-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: do not disable animation Bug:68769804 Test: manual Change-Id: I82fefa5045258ec1adee0f4ab27d31b7950e4a8e
atterySaverPolicy.java
|
28939988f0da2f37bac87a6929a1584ad18fdeba |
03-Oct-2017 |
Pavel Grafov <pgrafov@google.com> |
Profile lock timeout. When a managed profile has separate lock (a.k.a work challenge) and maximum screen off timeout set by admin, this timeout will only cause the profile to get locked, not the whole device. PowerManagerService now tracks some per-profile state for profiles that have lock timeout set by admin and have separate lock: 1. timeout set by admin. 2. wake lock summary 3. last activity time 4. whether the profile is considered active 5. whether the profile got locked last time it went inactive. Wake lock summaries and last activity times are updated at the same time as global wake lock summary/user activity is updated. Test: cts-tradefed run commandAndExit cts-dev -a armeabi-v7a -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.ManagedProfileTest Test: runtest -c com.android.server.devicepolicy.DevicePolicyManagerTest frameworks-services Bug: 63908311 Change-Id: Ief7be4e0bf12bdbedef94a129a13d07a9f98e75c
otifier.java
owerManagerService.java
|
2b186fa2142087cb3bb5d5996febe66b2aaf7aa3 |
29-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: Disable location when screen is off. Bug: 68769804 Test: manual test Change-Id: Id93e250e5d189136dd267b21a3977ac95392c50b
atterySaverPolicy.java
atterysaver/BatterySaverController.java
atterysaver/BatterySaverLocationPlugin.java
|
9e0aba647c81a174ec5e80a902fa3748b0202bc3 |
04-Dec-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Extreme battery saver: Log BS state in the event log."
|
e3def31ec007711865bd0720d6e08cf55342ef9e |
04-Dec-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Extreme battery saver: Do not lower screen brightness"
|
85dd0852fe506bcf800bea99aeb7af401e1485c4 |
01-Dec-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: Log BS state in the event log. Test: manual test (adb logcat -b events | grep battery_saver_mode) Bug: 68769804 Change-Id: I93b26e3434a60dcae1efaa7ab8c78da2ba73192c
atterySaverPolicy.java
atterysaver/BatterySaverController.java
|
97e5a71838f07721a6622e4de837ffbbdf9ba7f7 |
01-Dec-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: Do not lower screen brightness - Auto-awesome brightness should handle it better. Test: manual test Bug: 68769804 Change-Id: Ic9e620520c509948a7685e95c8a4d2db76399008
atterySaverPolicy.java
|
f27dd76fa9f78eb116d3b425e9896d458aaf96fc |
01-Dec-2017 |
Makoto Onuki <omakoto@google.com> |
Merge "Extreme battery saver: Show warning notification instead of toast"
|
afd6ff30816afc545cde4191d4eb56527ce207d6 |
30-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: Remove spammy WTF. Bug: 68769804 Test: manual test (boot and check logcat) Change-Id: I3dc0e13a0191f3825f7f5257ae0dd2fdc52d68cc
atterysaver/CpuFrequencies.java
|
036cc818a9dea2383d1841133798ba83dbcaec03 |
30-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: Show warning notification instead of toast (Just for now; we'll remove it before shipping.) Bug: 68769804 Test: manual test Change-Id: Ib1d58fbc88f79a62030a2e59d1dce15e9ff1323a
atterysaver/BatterySaverController.java
|
46d88da64e30e2592c56c838a8875bb27ae739a2 |
30-Nov-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Merge "Remove shutdown of StorageManager"
|
684cae74e343a3abb3b28ce8ebb3683939704723 |
29-Nov-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Extreme battery saver: Force background check on all apps"
|
e7ec72a5dfff1d199de5a77b5818478c3e29d825 |
22-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: Force background check on all apps - Power-saver whitelisted (including temp whitelist) apps and system UIDs are exempted. - Otherwise, background services and manifest receivers will be restricted as if OP_RUN_IN_BACKGROUND is set to IGNORE. Test: manual test Bug: 68769804 Change-Id: I49e7d32357ffc177ace38a064f943643f4f71058
atterySaverPolicy.java
|
ae435372865f66cf473ec620de7afab1d6dc1fad |
16-Nov-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Remove shutdown of StorageManager Init is always shutting down vold afterwards. Bug: 65174075 Bug: 64143519 Test: manual - verified that VolumeManager::shutdown is called Change-Id: I3893af3877e78e0193b15813f37ece46a378e075
WNERS
hutdownThread.java
|
e098b7595a0ab4341a828a356e4dbfec333a6cdd |
28-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: Tweak to file saver - Restore the default values after a runtime restart. - debug.batterysaver.no_write_files sysprop to avoid writing max_freq Bug 63527520 Test: manual Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/FileUpdaterTest.java Change-Id: Ic4783f181252b063cfe7ea6fee47b9241f1688cc
atterysaver/BatterySaverController.java
atterysaver/FileUpdater.java
|
1ecaf7c777cdf303e91ecc636af7814fb381f9af |
27-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Don't show the battery saver toast when the screen turns on Bug 68769804 Test: manual test Change-Id: I4eca183f5e61d31d162d3d0914fe2dc94bb8a11e
atterysaver/BatterySaverController.java
|
e99bc0501a288735d337f2ff64f8fa47f766a59b |
20-Nov-2017 |
Adrian Roos <roosa@google.com> |
WM: Move WindowManagerPolicy, DisplayFrames and WindowManagerInternal into services Splits WindowManagerPolicy into a framework and a services part, preventing concepts that are internal to the window manager from leaking out into the framework. Test: make droid Change-Id: I7b6a54f55f76f6fbb5f27090981b8f1d4d8be88b
otifier.java
owerManagerService.java
|
7e79be857e5415928a44d56388b538bc62ed8b52 |
22-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Merge "Extreme battery saver: Disable launch boost"
|
1e7010087727848a715ecfbc97be9d569dc36868 |
21-Nov-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Add OWNERS to system_server services."
|
a7d8c4d9ca619c2565aa7994305cdd8aa52fefc1 |
21-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: Disable launch boost Bug: 68769804 Test: manual test with debug log in nativeSendPowerHint(). Change-Id: I7ce61463215400379e0aa0d1782b2372495fe97e
atterySaverPolicy.java
owerManagerService.java
atterysaver/BatterySaverController.java
|
fe731413dad2cc28cf28b8acb4fd8d1a39a849b6 |
21-Nov-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Global a11y action to lock screen"
|
9fc31ee1f85e13a03bb15c435c98c6d3101c309e |
21-Nov-2017 |
Michael Wright <michaelwr@google.com> |
Add OWNERS to system_server services. Test: N/A Change-Id: I60174fcbbf2a061df2961239ec1b45df2e6b20ed
WNERS
atterysaver/OWNERS
|
ce643a309e8d414395ec36188523d10eb64d6618 |
20-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Extreme battery saver: Cap max cpu frequency. - Lower the max CPU frequency on battery saver. - We have different sets of frequencies for screen-on and screen-off. - The frequency configuration is from R.string.config_batterySaverDeviceSpecificConfig. Bug: 68769804 Test: Manual test with settings put global battery_saver_device_specific_constants cpufreq-n=0:1324800/4:1497600,cpufreq-i=0:1900800/4:1958400 using cat_repeat /sys/devices/system/cpu/cpu{0,4}/cpufreq/{cpuinfo_cur,scaling_max}_freq Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/CpuFrequenciesTest.java Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/power/batterysaver/FileUpdaterTest.java Change-Id: Ie1bb11c46c0d4730129fe9d82e86d8acebe0b560
atterySaverPolicy.java
atterysaver/BatterySaverController.java
atterysaver/CpuFrequencies.java
atterysaver/FileUpdater.java
|
fb5b96b4afd2dd255552e7c32f2d0adf3fcb62f6 |
17-Nov-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Follow-up for Ife38c2cd94ac9902911b005dbbca8b0d0a62e6d7"
|
f9a651d64c687297c0739982bedc7a8a34c778cf |
11-Oct-2017 |
Eugene Susla <eugenesusla@google.com> |
Global a11y action to lock screen Fixes: 25567237 Test: ensure API works using TestBack Change-Id: I335fd6b44d2c67b53a2c1f6224d16bd798276c8b
owerManagerService.java
|
fb9ec66ef025fed04b12c90a0c279a8b0296cfb8 |
16-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Merge "Implement force-all-apps-standly in job scheduler."
|
3aaed2912be642d306fa223edcb58278b0e45795 |
16-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Follow-up for Ife38c2cd94ac9902911b005dbbca8b0d0a62e6d7 Address review comments on the previous CL. (Plus a couple bug fixes.) Test: atest BatterySaverPolicyTest Test: manual test Bug: 68769804 Change-Id: If2de9148d1b8175a9f0d66bc3a7ecd02ce7a620b
atterySaverPolicy.java
owerManagerService.java
atterysaver/BatterySaverController.java
|
9be0140c1474dfd23d46121c51e636040a8080df |
10-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Implement force-all-apps-standly in job scheduler. Bug: 68769804 Test: Manual test Change-Id: I70c28b7841165414cc8d27bf3466401c541d0569
atterySaverPolicy.java
|
dec3eb8b755ea81c5465dc81ef02be91bae5aade |
16-Nov-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Merge "Decrease radios poll interval"
|
231d57deafd9b61b90eb28acad5ea14e81420ade |
15-Nov-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Decrease radios poll interval Polling with wait() calls is OK, but sleep-based should be as short as possible. Test: manual Bug: 65174075 Change-Id: I6ce3bb46b6f6fb932fd4b9500a5854df2ebf8058
hutdownThread.java
|
66a7812bc90b5be7702fe5743d257fddcdb48201 |
15-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Refactor battery saver logic + add "per device" setting - Extract the battery saver mode transition logic to BatterySaverController. This now also supports running different code when screen turns on and off. - BatterySaverPolicy now takes a "per-device configuration" from config.xml, which can be overwritten via a global setting. We'll use this to set up max CPU frequencies. - The actual part to write max CPU frequencies is not finished yet. Test: atest BatterySaverPolicyTest Bug: 68769804 Change-Id: Ife38c2cd94ac9902911b005dbbca8b0d0a62e6d7
atterySaverPolicy.java
owerManagerService.java
atterysaver/BatterySaverController.java
atterysaver/FileUpdater.java
|
1e3212ebda4e3c6e50e49b4ee369bec7ff213ec0 |
09-Nov-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Battery saver preliminary changes for P."
|
aae89531c0e8fce575d97fc887cd1fbd3055de19 |
08-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Battery saver preliminary changes for P. - Flags for force app standby for jobs and alarms, and sensors. - Don't disable GPS when the screen is off. Bug: 68769804 Test: manual Change-Id: I13661498dbc25051f2be0423cb50a55e4e592dc4
atterySaverPolicy.java
owerManagerService.java
|
7fe465a9e77292e358d36e79f92d6360649758d0 |
07-Nov-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "SidekickService (base)"
|
2eccd0262827259d15ceaa0fca975d3243c3a699 |
01-Nov-2017 |
Makoto Onuki <omakoto@google.com> |
Make the battery saver knobs hidden public, so other components (system UI, settings, etc) can use them. Bug: 68769804 Test: Build & presubmit Change-Id: I30fe78e49d2187bee7c7aeba735cd9c26fc332a5
atterySaverPolicy.java
owerManagerService.java
|
10a4a64bcc046ca0429069ad6dc2d20b65279bc6 |
25-Sep-2017 |
Chris Phoenix <cphoenix@google.com> |
SidekickService (base) Test: builds; Sidekick watch face animates in Ambient Change-Id: I5946dbf7194653ac4707b6c186b0a9197d125d5f
owerManagerService.java
|
321985263304e01c003920965cacfd17bb1d9e52 |
26-Oct-2017 |
Kweku Adams <kwekua@google.com> |
Updating some PowerManagerService proto messages. Added some extra comments. Bug: 65750826 Test: it builds Change-Id: I0469b636376628bb53a3d549367528b573a957c4
owerManagerService.java
|
e6b00c2a1698386dcc26f1b152e7e4b2393c4238 |
24-Oct-2017 |
Kweku Adams <kwekua@google.com> |
incidentd: Updating PowerManagerService proto files. Moving to the proto/.../server directory since PowerManagerService is in com.android.server. Extracting enums from other components into their own files. Bug: 65750826 Bug: 65750806 Test: flash device and check incident.proto output Change-Id: Ib91b7c08142fa66adf18b6e85106d4cbb5adf660
owerManagerService.java
irelessChargerDetector.java
|
20bc30f4cedff1043c4c665cfe68f7d7fd16a801 |
18-Oct-2017 |
Ruchi Kandoi <kandoiruchi@google.com> |
Don't wait for NFC when shutting down. NFC doesn't store any state before powering off, and hence it is okay to not wait for it while shutting down. Bug: 65761561 Test: Boot and shutdown Change-Id: Ic8243bdb9c6d12daf6cff5784046286bfa8f4d53
hutdownThread.java
|
06aea9df52f50dadd0e95416632a6c0ff00bd075 |
07-Oct-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Do not send SHUTDOWN broadcast to manifest receivers Test: adb shell svc power reboot Test: SendShutdownBroadcast should take << 10 seconds (no timeout) Bug: 66783517 Change-Id: I01d3dab6c24add323ee0ec990c3f7a7864ce4ad7
hutdownThread.java
|
f39df68b7176fac3187e882e61145dcbfb1e96ac |
25-Sep-2017 |
Sudheer Shanka <sudheersai@google.com> |
Merge "Add shutdown reason as extra when triggering ACTION_REQUEST_SHUTDOWN."
|
292637f51ac26dc4328d01ef5fc76fa36279f913 |
25-Sep-2017 |
Sudheer Shanka <sudheersai@google.com> |
Add shutdown reason as extra when triggering ACTION_REQUEST_SHUTDOWN. When BatteryService triggers ACTION_REQUEST_SHUTDOWN intent, add the reason for shutdown as extra to indicate low battery or critical battery thermal state. Bug: 63736262 Test: 1/ adb shell cmd battery unplug && adb shell cmd battery set level 0 2/ Power on the device 3/ Verify sys.boot.reason == shutdown,battery Test: 1/ adb shell cmd battery set temp 700 2/ Power on the device 3/ Verify sys.boot.reason == shutdown,thermal,battery Change-Id: If20a36ef53f8bcbfae4114df08f741ec1dcd7df9
owerManagerService.java
|
9fc6d1fe898867e3df3df44812cfef79c16f79bb |
22-Sep-2017 |
Santos Cordon <santoscordon@google.com> |
Merge "Remove debug logging from PowerManagerService." into oc-mr1-dev am: 73e6ff1925 Change-Id: I095f84243b1e9d9e75ffd8747fb69942d12a3ee5
|
4ddb801ed2d64a64bec11a4b032bcd78127c5e36 |
21-Sep-2017 |
Santos Cordon <santoscordon@google.com> |
Remove debug logging from PowerManagerService. Previously set to true accidentally. Bug: 66209945 Test: Manual Change-Id: Ie34ff30b43107897cbffc6258cb6c3e867d5da2e
owerManagerService.java
|
211cd1bd3da2eaa9b0f2316691f651cf17305fda |
19-Sep-2017 |
Santos Cordon <santoscordon@google.com> |
Merge "Move VR Display Policy check to after wakefulness." into oc-mr1-dev am: bbd01422d3 Change-Id: I41c6869f6514496a5dfc615ef7763f06b6fe1dbd
|
21e9f2b2dbb0d01fc53a576a72f02809eab9736d |
13-Sep-2017 |
Santos Cordon <santoscordon@google.com> |
Move VR Display Policy check to after wakefulness. Being in VR was preventing sleep and doze functionalities to function. Sleep and doze is what commonly happens when the user hits power button and without this fix hitting the power button resulted in PowerManager not turning off the display. Bug: 65635259 Test: Manual. Ensure that hitting power button while in 2D-in-VR turns screen off on smartphones. Test: runtest --path frameworks/base/services/tests/servicestests/src/com/android/server/power/PowerManagerServiceTest.java Change-Id: If3a14a5a423b0394926b323b97ed11b98177e43b
owerManagerService.java
|
0abd36a19f7f28d47e13ff6c69f3cb16a8ad1d94 |
30-Aug-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Merge "Make shutdown logging thread-safe" into oc-mr1-dev am: 9328cb9fdf Change-Id: I862810d4b0f13180e1126db1fdd90e9adf539d9c
|
58815ea939f3830e82e7afd2f0dd10173ab04f65 |
29-Aug-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Make shutdown logging thread-safe Previously TRON_METRICS/SHUTDOWN_TIMINGS_LOG were accessed from different threads. Now all access is properly synchronized. Important: Moved saveMetrics from rebootOrShutdown. rebootOrShutdown can be called directly from SystemServer class after reboot when no metrics were collected. Test: manual reboot/shutdown and verify that metrics are logged Bug: 64815357 Change-Id: I7b02c9c6b10b920ce3532a0808ab71a0d6e07d2b
hutdownThread.java
|
8908b418eedfb60c92a14b4034dcde614119bb7c |
28-Aug-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Merge "Added tron metrics for shutdown time" into oc-mr1-dev am: 30c565d399 Change-Id: I10d4479c79c1997325f74477a94e4f74eb043f46
|
291f63bb548473a75d3053927c0a94c9af11e28b |
26-Aug-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Added tron metrics for shutdown time The metrics are persisted in /data/system/shutdown-metrics.txt file property and logged after reboot. MetricsLogger API cannot be directly used during shutdown since event log is cleared on reboot/power off. Test: manual reboot/shutdown and verify that metrics are logged Bug: 64815357 Change-Id: I7fa1af8be58a80a3d5bae26d55c1ed40bf98f4c0
hutdownThread.java
|
fe35ec5daf7ae7d08d069083cf401887ca3cd06a |
25-Aug-2017 |
Mark Salyzyn <salyzyn@google.com> |
Merge "Switch /data/misc/reboot/last_reboot_reason to persistent property" am: 0172ce8dbf am: cf5fa80fbf am: 7be29cab70 Change-Id: I0c10c44b33af31a0fcae30c2f617dd832788899e
|
cf5fa80fbfa3b43875fd5fae1b6c06cf6c6364d2 |
25-Aug-2017 |
Mark Salyzyn <salyzyn@google.com> |
Merge "Switch /data/misc/reboot/last_reboot_reason to persistent property" am: 0172ce8dbf Change-Id: I69a9c17fc8594dee564e8c64e9d85f2afe60607b
|
e65c0c61b771f05e9712cbd546f675aa7c380265 |
15-Aug-2017 |
Mark Salyzyn <salyzyn@google.com> |
Switch /data/misc/reboot/last_reboot_reason to persistent property Switch from /data/misc/reboot/last_reboot_reason to persistent Android property persist.sys.boot.reason for indicating why the device is rebooted or shutdown. persist.sys.boot.reason has a standard as outlined in b/63736262 and the associated investigation. Made adjustments to the values so that we did not create a problem even before we started. Compliance is part of the tests in boot_reason_test.sh. Test: system/core/bootstat/boot_reason_test.sh Bug: 64687998 Change-Id: Iba69acf2105f4446411d86cdb8097a1755a20f15
owerManagerService.java
|
49b41328b0a35f862869b02d1522761e4719d894 |
16-Aug-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Log SystemServerShutdown earlier Otherwise it wouldn't get logged in the reboot case. Test: adb shell svc power reboot Bug: 64569080 Change-Id: Ib69bb78f682847fbdf9735bdee9cc8406e491463
hutdownThread.java
|
6e3461b67cae27a42a4d77fa277ba2d844ea0cde |
11-Aug-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Log timings for shutdown stages Renamed BootTimingsTraceLog to TimingsTraceLog. It is now used for boot and shutdown logging. Added measurements for main stages of shutdown in the system server: ShutdownTiming: SendShutdownBroadcast took to complete: 734ms ShutdownTiming: ShutdownActivityManager took to complete: 203ms ShutdownTiming: ShutdownPackageManager took to complete: 17ms ShutdownTiming: ShutdownBt took to complete: 533ms ShutdownTiming: ShutdownRadio took to complete: 534ms ShutdownTiming: ShutdownNfc took to complete: 1536ms ShutdownTiming: ShutdownRadios took to complete: 1538ms ShutdownTiming: ShutdownStorageManager took to complete: 906ms ShutdownTiming: SystemServerShutdown took to complete: 3918ms Bug: 64569080 Test: shutdown/reboot and check logs Change-Id: I636c045852cd1ed6be1c58af6608f70e95756389
hutdownThread.java
|
9b0b6a6b802cbfb6656b6ef91eb113e5458bfe27 |
08-Aug-2017 |
Wei Wang <wvw@google.com> |
Shutdown: Continue shutdown with BLE only mode Bug: 64213593 Test: shutdown no timeout Change-Id: I5007e7cfc00ab22fce3b6ef13bacbcc951197b9e (cherry picked from commit 4d282544c3ebf5ade44d56963c23a474916e61ba)
hutdownThread.java
|
0b99402f87ce1d8275dc60d98c2c12ccc0d9aceb |
08-Aug-2017 |
Jason Monk <jmonk@google.com> |
resolve merge conflicts of de0c539dd4f1 to oc-mr1-dev Test: I solemnly swear I tested this conflict resolution. Change-Id: I3f5eb2a0481fb09b98c0c522c82c233350c06375
|
23c0668a3f6b24c29fb2d63b8fc6f28e3b7e7df9 |
08-Aug-2017 |
Wei Wang <wvw@google.com> |
Merge "Shutdown: Continue shutdown with BLE only mode" into oc-mr1-dev
|
b4302182bc916ba0f5ee08756c1b2d15cb845874 |
04-Aug-2017 |
Jason Monk <jmonk@google.com> |
Move shutdown UI to sysui (when possible) Test: click restart or power off in global actions Change-Id: I0dc30a9772bbfb3cd3c3568f157e854fef87bf87 Fixes: 63576195 Fixes: 64125291
hutdownThread.java
|
4d282544c3ebf5ade44d56963c23a474916e61ba |
08-Aug-2017 |
Wei Wang <wvw@google.com> |
Shutdown: Continue shutdown with BLE only mode Bug: 64213593 Test: shutdown no timeout Change-Id: I5007e7cfc00ab22fce3b6ef13bacbcc951197b9e
hutdownThread.java
|
b4f3697ef8b3f272e5fbb3b6a0d9b63825532299 |
02-Aug-2017 |
Jeff Sharkey <jsharkey@android.com> |
Don't show scary UI when rescue party kicks in. We're not actually doing a factory reset yet; we're rebooting to ask the user if they'd like to reset, so give them a less scary message. Test: builds, boots Bug: 63000721 Change-Id: Ibbf5eeb6e21d25dee2d6723b4ba4e42d9ff5c2fd
hutdownThread.java
|
12445498582b90302852f9d6a52f3e82f6a2af0b |
26-Jul-2017 |
Lucas Dupin <dupin@google.com> |
Merge "Text color of "shutdown" after removing overlay" into oc-dr1-dev am: c1edefc059 Change-Id: I9771f6c14fca2768b7b455792f6f62a1855ac4ec
|
c1edefc0590136e5ff46d634621d8f69d40f8053 |
26-Jul-2017 |
Lucas Dupin <dupin@google.com> |
Merge "Text color of "shutdown" after removing overlay" into oc-dr1-dev
|
527aad1b1753e6f3299383c8b646e66ac989b764 |
21-Jul-2017 |
Lucas Dupin <dupin@google.com> |
Text color of "shutdown" after removing overlay Bug: 63751714 Fixes: 64079315 Test: Visual, turn off device with white wallpaper set Change-Id: I667d40135c8c7b4f498bc89f695cbfde5657588c
hutdownThread.java
|
e9e9fb257fbd074eddf7c2b97ff8e9e9dbfd6fe6 |
20-Jul-2017 |
Christine Franks <christyfranks@google.com> |
Remove RetailDemoModeServiceInternal Bug: 62712426 Test: make -j100 Change-Id: I0b852aef30a8cadcda08fcff1dcf861aac2a4d7e
otifier.java
|
f66a377785e9a70c2408f49b892eb351b136edc5 |
20-Jul-2017 |
Christine Franks <christyfranks@google.com> |
DO NOT MERGE - Remove RetailDemoModeServiceInternal Bug: 62712426 Test: make -j100 Change-Id: I0b852aef30a8cadcda08fcff1dcf861aac2a4d7e
otifier.java
|
b7c929977c60f0a33fc5bd8339ca7c1770f0980f |
24-Jun-2017 |
Christine Franks <christyfranks@google.com> |
DO NOT MERGE - Remove RetailDemoModeService Bug: 62712426 Test: make -j100 Change-Id: I483f2e3518a48fbc833562e71c3acd17ad565881 Merged-In: I483f2e3518a48fbc833562e71c3acd17ad565881
owerManagerService.java
|
732c0439e7453c64bbb7555df90b595522f60ffe |
24-Jun-2017 |
Christine Franks <christyfranks@google.com> |
Remove RetailDemoModeService Bug: 62712426 Test: make -j100 Change-Id: I483f2e3518a48fbc833562e71c3acd17ad565881
owerManagerService.java
|
3e99f654fbf56d3b7ef7130658b8ef83d2d0cdbd |
06-Jul-2017 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #34471029: Don't allow audio use from background apps. This is becoming a common pattern (keeping track of which processes are cached and not allowing them to do stuff in that state), so I am turning this in to a general mechanism for monitoring this state through the activity manager's IUidObserver. Now we can just have AudoService implement its own IUidObserver to get this state and update which uids it is blocking. This required making some changes to uid change reports so that the integer is now a bit mask instead of an enumerations, but that is what it was already turning in to anyway. (This gets rid of the crazy GONE_IDLE constant that we'd needed to add before because it wasn't a bit mask). Eventually the power manager should be changed to be told about these changes to cached state instead of listening to every proc state change, but we'll do that later, it is more disruption than I want to take for now. However, while working on this, I noticed that the power manager had regressed in the cached uids it would actually block, because the activity manager was no longer telling it about all uids that are idle. (I think this happened when I had to change the default idle state of UidRecord to true.) So I am adding a bit of new code to keep track of what idle state we last reported to observers, to make sure we tell it about newly created uids that are idle but have never actually become active. Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services Change-Id: I7bfd46bacadd4cab2a69f40e6e52afb4e67b456a
owerManagerService.java
|
fd27966b59a8d1d8c049083949086fd952186eb1 |
30-Jun-2017 |
Jason Monk <jmonk@google.com> |
Update power menu + dialog - Update power menu to handle seascape properly - Update shutting down dialog, the gradient is covered by the global actions dialog not going away completely, everything else is still in ShutdownThread. Test: visual Change-Id: I06a2fdd2652bf006dc5c0b45e3bc922e43093301 Fixes: 62391660
hutdownThread.java
|
f03738d877b43deea2a3cc6cf72c9364e9f5ad43 |
13-Jun-2017 |
Christopher Tate <ctate@google.com> |
Merge "Send ACTION_SHUTDOWN broadcast to manifest receivers" into oc-dev am: 630a49aa4e Change-Id: Ib2a4229a6b00810b9dd73733421f3ac7e57f2112
|
98946b9f72e03a550ec8a63186c463015c6ef78e |
13-Jun-2017 |
Christopher Tate <ctate@google.com> |
Send ACTION_SHUTDOWN broadcast to manifest receivers Fix #36767224 Test: manual Change-Id: If8f1fa986b9b8f3c426e4c0623bbca6f96b7199c
hutdownThread.java
|
c7fed4240323383a12fd10adad91cc767404e2f0 |
13-Jun-2017 |
Tianjie Xu <xunchang@google.com> |
Merge "Fix the issue that uncrypt isn't called under quiescent mode" into oc-dev am: f40f297546 Change-Id: Id60cf7cf4b82f17fd094fa011bb54a543e636f48
|
3a66fc41e3b1341af37254554610b9e72da4675a |
10-Jun-2017 |
Tianjie Xu <xunchang@google.com> |
Fix the issue that uncrypt isn't called under quiescent mode OTA fails on fugu under quiescent mode because the reboot reason changes from "recovery-update" to "recovery-update,quiescent". The new reason isn't checked in shutdown thread so that shutdown thread doesn't call uncrypt properly before rebooting into recovery. Bug: 62324707 Test: Recreated and fixed the "block.map" missing failure on fugu. Change-Id: I110653cd64dbbdc71e89ead2197bf023a7c054e8
hutdownThread.java
|
ffc8f650d00c09b34dcfa3ce45b9ea34cb7479b6 |
31-May-2017 |
Michael Wright <michaelwr@google.com> |
Merge "Change the thread for handling shutdown of PowerManagerService." into oc-dev am: 614636e926 am: 1a66f77647 Change-Id: I9484e5763bf02e2236e40c538f0486288c3e45a4
|
614636e9263c0d87c8c738dccf298bd16c5fec75 |
31-May-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Change the thread for handling shutdown of PowerManagerService." into oc-dev
|
5454bac39164081dabe7be7a60e572ade74c6e2a |
30-May-2017 |
Andrii Kulian <akulian@google.com> |
Merge "Refresh screen off timeout when screen lock is released in VR" into oc-dev am: e63965cef5 am: 83876c735e Change-Id: I843e2469694c31ee23148ae09cb7b9c5d7506bfc
|
e63965cef516777dae682103e0813b7f024dab62 |
27-May-2017 |
Andrii Kulian <akulian@google.com> |
Merge "Refresh screen off timeout when screen lock is released in VR" into oc-dev
|
9407a6b52cd9b98e714ceb7b699e5c453a252386 |
24-May-2017 |
Andrii Kulian <akulian@google.com> |
Refresh screen off timeout when screen lock is released in VR When evaluating conditions for user activity with no lights change, treat POLICY_VR the same way as for POLICY_BRIGHT, so new activity timeout will be set. Bug: 37968591 Test: Set screen timeout to 15s, launch Daydream, wait, launch Welcome flow. Change-Id: I3185cc97364ae5631ef53906958b16d41f326c3b
owerManagerService.java
|
9ff9b9afbb9cf4a89145f7ae5791f77879b6ab04 |
25-May-2017 |
Dmitri Plotnikov <dplotnikov@google.com> |
Merge "Triggering quiescent reboot during OTA" into oc-dev am: d9417c53e0 am: a376eed263 Change-Id: I9796f43fc6dd78f40883c154f0e77f5b438e6bd8
|
690c6bd9a371bd9f1f6562728368ab3e2c2e8cb3 |
11-May-2017 |
Dmitri Plotnikov <dplotnikov@google.com> |
Triggering quiescent reboot during OTA Bug: 34201965 Test: follow instructions in https://docs.google.com/document/d/1RjvUGRi_Ys5-BRoJz6_SnixuipFiF-GAs6CNc7w-Qj0/edit and use fake-ota Change-Id: I540f86cf11746faefc25bc74319512eba6d0d783
owerManagerService.java
|
64c820d3d4510b4953a8e888eb792a367b52eaa0 |
21-Mar-2017 |
Michael Wright <michaelwr@google.com> |
Change the thread for handling shutdown of PowerManagerService. Symptom: Watchdog due to blocked handler PowerManagerService during shutdown sequence. Root cause: While creating the dialogue for shutdown, HashMap object is accessed by createView() at LayoutInflater. This object is not excluded at multi threads. When this issue is occurred, multiple threads accesses this object. As the result, invalid state is generated inside HashMap object. And circulating reference is occurred at getEntry method. So system cannot get out of "for" loop. It blockes the processing of PowerManagerService thread and causes watchdog. That thing is happening. Solution: Change the thread for handling shutdown from "PowerManagerService" to "android.ui" thread. As the result, exclusive control is not needed. Bug: 35791029 Test: Manual Change-Id: Icbc12fb2706fb3c7e859f53bbb4c65f488850ce6
owerManagerService.java
|
7ac5a0b49ff8f3aa34d75b50119cf8ffbdf891e6 |
17-May-2017 |
Adrian Roos <roosa@google.com> |
PowerManager: Log wake up reason Bug: 38352929 Test: adb logcat -s PowerManagerService Change-Id: I3234f90895af5774fb215863e59a7035315dbbfe
owerManagerService.java
|
9199d0c1ffed3ff3e10c3e20fd7efad10798dc9a |
10-May-2017 |
Michael Wright <michaelwr@google.com> |
Avoid NPE when getting last shutdown reason. This can be null if there is a file but it's totally empty, and the switch statement will throw an NPE when switching on a null string (thanks Java!) Bug: 38195795 Test: none Change-Id: I86901e001b088a4a9b14f15c82b763e12d11875f
owerManagerService.java
|
251894b134a3d1d2bcba5ff9db7e3a4014cd369a |
03-May-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Fix lock contention: Call into power manager service from handler" into oc-dev
|
86c39f9edee88baa912c694061010483c7da9daf |
02-May-2017 |
Jorim Jaggi <jjaggi@google.com> |
Fix lock contention: Call into power manager service from handler Make sure to not hold the wm lock when calling into power manager service, because PWM will acquire a lock that might be contended. Test: Make sure user activity timeout is still respected on Keyguard Test: Have activity with screenBrightness=1.0, make sure screen is fully bright when opened Bug: 37888898 Bug: 36631902 Change-Id: I4b5433dbaf8aa151465ae32232d3b3b8597715df
owerManagerService.java
|
a6f7b25c3d160be02cb7384f154a1f77a8faaffa |
10-Apr-2017 |
Salvador Martinez <dehboxturtle@google.com> |
Added dialog to notify user of thermal shutdown tldr; Have the phone check when it reboots if it last shut down due to heat. If so, we should show the user an notification and dialog giving them more details. - Added hidden api to allow apps to query system_server for the reason the phone last rebooted - Added notification that is shown when the phone is booted if the last shutdown was due to excessive heat. - Added dialog to provide more details about the shutdown if the notification is tapped. - Added tests to verify that file is read and as expected. - Updated code for high temperature warning that is shown while the phone is running to avoid mixups in the future. Test: FrameworksServiceTests Bug: 30994946 Change-Id: Ic25f42539911c89ba7f1834e206f7931d65c2865
owerManagerService.java
|
694f24581ac4f14cc961c6b96368330ed6740772 |
20-Apr-2017 |
Tony Mak <tonymak@google.com> |
Send ACTION_POWER_SAVE_MODE_CHANGED to all user Fix: 36174715 Test: Install an app that listens to ACTION_POWER_SAVE_MODE_CHANGED in work profile. Make sure it receives the broadcast. Change-Id: I26df6710bc996792212d52189cd04bd2d30ac6d1
owerManagerService.java
|
5ab5e1d9514bde75beaf87f46d45b6ffcaac9891 |
15-Apr-2017 |
Makoto Onuki <omakoto@google.com> |
Log screen-on latency with tron Bug: 36776886 Test: manual test with "adb logcat -b all" and systrace. Change-Id: I9e7188475a79899569046892e6f08c9005b84303
otifier.java
owerManagerService.java
|
f2c38c130f113600a5363d124723302da9fccade |
31-Mar-2017 |
Jocelyn Dang <jocelyndang@google.com> |
Add set-mode command to turn battery saver mode on and off. Affected test will be modified in ag/2101279 Test: adb shell cmd battery unplug && adb shell cmd power set-mode 0 Bug: 31944272 Change-Id: Ia88e7e164aa9b8b4d0ab51f607a64b35e2159273
owerManagerService.java
owerManagerShellCommand.java
|
a52fc49845d1103dea2380f34b96e2a22ea1801e |
04-Apr-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Themes: Apply themes to system_server safely" into oc-dev
|
fe9a53bc45fd0124a876dc0a49680aaf86641d3e |
31-Mar-2017 |
Jeff Sharkey <jsharkey@android.com> |
Consistent dump() permission checking. This change introduces new methods on DumpUtils that can check if the caller has DUMP and/or PACKAGE_USAGE_STATS access. It then moves all existing dump() methods to use these checks so that we emit consistent error messages. Test: cts-tradefed run commandAndExit cts-dev -m CtsSecurityTestCases -t android.security.cts.ServicePermissionsTest Bug: 32806790 Change-Id: Iaff6b9506818ee082b1e169c89ebe1001b3bfeca
owerManagerService.java
|
a82b62678a0e1eaba50ec5adce93862683dac065 |
22-Mar-2017 |
Adam Lesinski <adamlesinski@google.com> |
Themes: Apply themes to system_server safely Creates a new UI Context for UI based operations. This UI Context is wired up the same way a normal app Context would be, and is subject to change when overlays are enabled/disabled. For this reason, only UI should be using this new Context. All other operations should be using the original system Context so that changing themes don't impact the regular operations of system_server. Also added some sanity checks at key places where we show UI (ShutdownThread, BaseErrorDialog). Bug: 36059431 Test: $ adb shell am crash com.android.settings Test: Observe crash and power off dialogs are blue with PixelTheme Change-Id: I87227ee2e0be1e72dcde8f482b37725cb687260b
owerManagerService.java
hutdownThread.java
|
29c82ab242d50000d22e593c27153751c8c6b44a |
10-Mar-2017 |
jackqdyulei <jackqdyulei@google.com> |
Hook up data saver to battery saver. 1. Add globalBatterySaverEnabled in PowerSaveState, which stores the real battery saver mode, not the one for specific service. 2. Add "mRestrictBackgroundChangedInBsm" and "mRestrictBackgroundBeforeBsm" to restore the mRestrictBackground if necessary. 3. If user toggles the data saver when battery saver is on, don't restore the data saver when battery saver is off. Bug: 34693888 Test: FrameworksServicesTests Change-Id: Ic50c1cae3fb110a228e59e5d1fd04c164e4b7274
atterySaverPolicy.java
|
291df4fc0c3fc7a28bf0d89619b7e7bc0ea672e1 |
14-Mar-2017 |
Chad Brubaker <cbrubaker@google.com> |
Expose Intents to Instant Apps This exposes Intents used by Android widgets to Instant Apps. The following Intents are exposed: Intent.ACTION_TIME_TICK Intent.ACTION_DATE_CHANGED Intent.ACTION_TIMEZONE_CHANGED Intent.ACTION_TIME_CHANGED Intent.ACTION_CONFIGURATION_CHANGED Intent.ACTION_LOCALE_CHANGED Intent.ACTION_SCREEN_OFF Intent.ACTION_SCREEN_ON Intent.ACTION_USER_PRESENT Bug: 33350280 Test: Manually verified that broadcasts are received. Change-Id: Ife94f594c1ff30f2625a57e1cc69f36cc00d1f34
otifier.java
|
5f3e93451e87d72c513e75c5d5459a4bd2cc41b2 |
13-Mar-2017 |
Jeff Sharkey <jsharkey@android.com> |
Lower-overhead version of LockGuard. Instead of building up a giant set of all locks inside the system server, there are only a handful that we're interested in watching: specifically those below the ActivityManagerService lock. This change adds a index-based variant of lock registering and checking, which has much lower overhead that doesn't bring a device to its knees. It's disabled by default, but can be enabled on local development builds. Currently uses the boostPriorityForLockedSection() hook in AMS to check for lock inversions when enabled. Test: builds, boots, no AMS lock inversions detected Bug: 35410906 Change-Id: I473d634d23c08538029412a1254bf4f92b96fb84
owerManagerService.java
|
5602189a6dec401bfa2e22247a23fb25dd3393f8 |
27-Feb-2017 |
Adrian Roos <roosa@google.com> |
AOD: Show charging status on AOD1 - Change PowerManager to not turn on display when on AOD - Add charging icon to AOD1 - Add transient charging indication when plugged in Bug: 30876804 Bug: 35850304 Test: runtest systemui; enable AOD, plug in phone, verify charging indicator shows, verify charging text shows and goes away after a few seconds Change-Id: Icb80843a12c56c7e2abeca78115a366b4d508d4f
owerManagerService.java
|
92681e8cfbbae58b00a80bb1e60f5444cf53fbdd |
28-Feb-2017 |
jackqdyulei <jackqdyulei@google.com> |
Hook up screen brightness knob to DisplayPowerController. This knob is designed to effectively tune the battery saver. Bug: 34693888 Test: FrameworksServicesTests Change-Id: I9fd7896f59fabd9baf649cdb12f01b1baaf4c34b
owerManagerService.java
|
455e90add22835d0744fc0f5c2feb5fcaf03b28f |
10-Feb-2017 |
jackqdyulei <jackqdyulei@google.com> |
Add BatterySaverPolicy for power save mode The BatterySaverPolicy is designed to consolidate all battery saver knobs into a central location. Usually it is consistent to mLowPowerModeEnabled unless it gets different data for specific service. By adding these knobs, we can effectively tune the battery saver. This cl sets up the framework for BatterySaverPolicy and updates following service to get battery saver data from BatterySaverPolicy 1. GnssLocationProvider 2. VibratorService 3. WindowManagerService 4. BackupManagerService 5. SoundTriggerService 6. NetworkPolicyManagerService Screen brightness will come in a following cl. Bug: 34693888 Test: FrameworksServicesTests Change-Id: I6b040e93391614b44d136a485faa4a332c396e51
atterySaverPolicy.java
owerManagerService.java
|
958d0a503699840f8f4b85cafa62f3793c89ac73 |
07-Feb-2017 |
Netta P <nettap@google.com> |
Protobufferize PowerManager dumpsys Bug: 34230125 Test: cts-tradefed run cts-dev -m CtsIncidentHostTestCase -t com.android.server.cts.PowerIncidentTest Change-Id: Ib71563cfc9ca95c297111430d8bbe2ce88d7a41d
owerManagerService.java
uspendBlocker.java
irelessChargerDetector.java
|
6e544617c63ca1d60ed0a1a01630557958de093b |
20-Feb-2017 |
Jeff Sharkey <jsharkey@android.com> |
Guard against possible AMS/PMS deadlock. PMS can't call into AMS while holding its local lock. Test: builds, boots Bug: 35410906 Change-Id: Ib80bbee5c0c3e5fb39ffef324e8176027da83f2f
owerManagerService.java
|
8deb67cb64b0cd93be545caf7887a12ed3611841 |
08-Feb-2017 |
Craig Donner <cdonner@google.com> |
Use the Context name to publish and use vrmanager Bug: 34736524 Test: build Change-Id: I8aabb4d242fb2378b24dd30a972c382a7f8f4934
owerManagerService.java
|
5483cea67a60d3c5012fa7120f62e6eacc6ad3ba |
02-Feb-2017 |
Justin Klaassen <justinklaassen@google.com> |
Remove experimental twilight-based automatic brightness Bug: 31602449 Test: verified adaptive brightness no longer varies with twilight with "brightness_use_twilight" set to "1". Change-Id: I6b5f7310020b2128c2b292414a205b6052270a0a
owerManagerService.java
|
a3c064d104613b901387399591dc98e2e6f63cf3 |
31-Jan-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Migrate Tron logs for power to multimetric format."
|
5c38fc2b97cba8a275a24bdf201073d68b101e7a |
25-Jan-2017 |
Alison Cichowlas <asc@google.com> |
Migrate Tron logs for power to multimetric format. As best I can tell, values 3 & 4 (theoretically totalTouchDownTime & touchCycles, per PowerScreenStateParser) were always set to 0; I have not migrated these fields. Test: Manually checked old vs new logs side by side in event log. Change-Id: Ifbc32cd2006cc94327301bae7541ca25b14f0a40
otifier.java
|
0ef403e53e2762d077750dd0a50b73c2125cadb0 |
25-Jan-2017 |
Dianne Hackborn <hackbod@google.com> |
Add some new experiment constants for activity and power manager. Activity manager now has constants, starting with two: bg check and process limit. Power manager now has constants, starting with one: controlling disabling of wake locks from cached processes. Test: manual Change-Id: I05db42e2104e9d31584f85251412df2d5efb34b6
owerManagerService.java
|
fe6f85cac9e823fd33a134f7129fdf7310703293 |
20-Jan-2017 |
Jeff Sharkey <jsharkey@android.com> |
Introduce RescueParty. When a device gets stuck in a crash loop, it's pretty much unusable and impossible for users to recover from. To help rescue devices from this state, this change introduces a new feature that watches for runtime restart loops and persistent app crash loops, and escalates through a series of increasingly aggressive rescue operations. Currently these rescue levels walk through clearing any experiments in SettingsProvider before finally rebooting and prompting the user to wipe data. Crash loops are detected based on a number of events in a specific window of time. App stats can be stored in memory, but boot stats need to be stored in system properties to be more robust. Start up RecoveryService much earlier during the boot so we can reboot into recovery when needed. Add properties tha push system_server or SystemUI into a crash loops for testing purposes. Test: builds, boots, forced crashing walks through modes Bug: 24872457, 30951331 Change-Id: I6cdd37682973fe18de0f08521e88f70ee7d7728b
owerManagerService.java
|
3107d29c8f6f40b98533978a7e19e5c328f73d24 |
21-Sep-2016 |
Santos Cordon <santoscordon@google.com> |
Add Brightness setting for VR Mode. This change saves and loads a different brightness setting when the user goes in and out of VR Mode. Test: runtests frameworks-core Test: Turn vr mode on and change brightness (should remain separate from normal brightness) Bug: 30984614 Change-Id: If3c3e81b592e0c6fd037e5783559683e5cb58379
owerManagerService.java
|
7e96654f1b2e7c97f52cdc68d343139a5186d54d |
27-Dec-2016 |
Ian Pedowitz <ijpedowitz@google.com> |
Revert "Add Brightness setting for VR Mode." This reverts commit c7e853f51110b9b6893d526f1f7340b2966f928a. Bug: 33895226 Bug: 30984614 Change-Id: Icca320e02651b7dd7b8db84ab414f41edee32760
owerManagerService.java
|
c7e853f51110b9b6893d526f1f7340b2966f928a |
21-Sep-2016 |
Santos Cordon <santoscordon@google.com> |
Add Brightness setting for VR Mode. This change saves and loads a different brightness setting when the user goes in and out of VR Mode. Bug: 30984614 Change-Id: Ie5578bbd6ea346f0eb34fe4abbfd604a5d7c0c93
owerManagerService.java
|
a8d2c6457fe339acaae256510afbe63e39147d62 |
08-Dec-2016 |
Dmitri Plotnikov <dplotnikov@google.com> |
Adding "quiescent" reboot mechanism to support STB operators Bug: 31681185 Change-Id: Iada4dd4624f0221e5b59440da2718da980742720 Test: with SampleLeanbackDeviceAdmin. CTS test forthcoming
owerManagerService.java
|
cd941213a237073fea567f0faf0098ec23459fb5 |
27-Nov-2016 |
Nick Kralevich <nnk@google.com> |
Revert more integrity check changes. The integrity checking features never shipped as part of a release. Delete the stale code. This conceptually reverts the following commits: * c7d64c134ae786cc41af78a3e7dfbfeda8be4287 * ee2b49283261f7b4518ec7c98f568f883f817c9d Test: Device boots and no obvious problems. Change-Id: I8d1589b38ddbcdf26f5132476b8cdfba7ef439cd
hutdownThread.java
|
2250d56a0b47b93016018340c8f4040325aa5611 |
08-Nov-2016 |
Sudheer Shanka <sudheersai@google.com> |
Rename MountService to StorageManagerService. Bug: 30977067 Test: Existing tests pass Change-Id: Ieac0f11c2b249dcd60441b14c1f391e6f8131d42
hutdownThread.java
|
dc589ac82b5fe2063f4cfd94c8ae26d43d5420a0 |
11-Nov-2016 |
Sudheer Shanka <sudheersai@google.com> |
Update usage of ActivityManagerNative. - Remove references to ActivityManagerProxy. - Add isSystemReady to ActivityManager. Bug: 30977067 Test: cts/hostsidetests/services/activityandwindowmanager/util/run-test android.server.cts adb shell am instrument -e class com.android.server.am.ActivityManagerTest,com.android.server.am.TaskStackChangedListenerTest \ -w com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner Change-Id: I07390b6124fb1515821f5c0b37baf6ae74adc8fa
otifier.java
|
5614bf5a1ae4522dfc1a041f003cebc9b25c8b93 |
08-Nov-2016 |
Dianne Hackborn <hackbod@google.com> |
Move code for handling uid obs "cutoff" to activity manager To do this, I had to fix the PROCESS_STATE_NONEXISTENT constant to be the last value (instead of the special magical -1 value) so it semantically matches the public importance constants. I think this is better anyway. Also this fixes a big problem in the implementation, where we weren't keeping track of the last proc state per uid...! Duh. Test: manually ran testUidImportanceListener Change-Id: Ie3008f824446089840f896885e6033472abb065e
owerManagerService.java
|
fc46e9b643881b7b2ab76854f3a0ac077e9def8d |
22-Oct-2016 |
Sudheer Shanka <sudheersai@google.com> |
Move IActivityManager to aidl. Bug: 30977067 Test: Existing tests are passing, dump commands still working. Change-Id: I9cf81c4d381ebce14a6c701e409cbb269f2ff1fb
otifier.java
hutdownThread.java
|
951ea6907c6cc01ce3f9ec4859d65a184c7ce785 |
02-Nov-2016 |
Dianne Hackborn <hackbod@google.com> |
Power manager always needs to allow wake locks for services, receivers The change to not allow wake locks for idle apps was a little too aggressive, since we allow apps that are currently executing services or receivers to be idle. (Idle means that it hasn't been in the foreground for X amount of time, but services and receivers don't count as being in the foreground.) So this takes in to account the actual procstate of the uid to determine if it should actually respect the current idle state. Test: manual Change-Id: I32949124b37875b13233478719abccb8369e47f6
owerManagerService.java
|
d33c7cd87a8ca6ede8622392601f8ce9df7694ad |
26-Oct-2016 |
Dianne Hackborn <hackbod@google.com> |
Power manager now prevents wake locks from idle uids. The activity manager now pushes the idle/active state down in to the power manager. The power manager now tracks a structure of data about each uid: how many wake locks it holds, whether it is active, and (as before) its current process state. Now when apps are inactive, we always disable wake locks they hold, regardless of the system's device idle or other state. Test: none Change-Id: I2cd4077e4d8a8572525406ae9747f0a2435764da
owerManagerService.java
|
0d43404a07c1372fef71181ab9daa8fa960fdd4c |
03-Oct-2016 |
Ruchi Kandoi <kandoiruchi@google.com> |
power: PowerHAL support for HIDL interfaces. Bug: 31177288 Change-Id: I3ce5a71958f47d26855513cf7523922e80dd25d2 Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
owerManagerService.java
|
0939ddf6f30d6e52e360222ce56a0e7fd56ff5e9 |
28-Sep-2016 |
Tianjie Xu <xunchang@google.com> |
Merge "Log the error when uncrypt timeouts" am: c1973ecbd2 am: c68e6d6708 am: 3aeade44a9 am: 96ce9d16ed Change-Id: Ideb0ba7ea8d251dae5a23c8fda7e777bbea784ac
|
96ce9d16ed84d2f50cafbf74dfd30d88271aa60b |
28-Sep-2016 |
Tianjie Xu <xunchang@google.com> |
Merge "Log the error when uncrypt timeouts" am: c1973ecbd2 am: c68e6d6708 am: 3aeade44a9 Change-Id: I913474dbf87b30683267d8f6a458927b7d331c4c
|
036d08638e6a5f849847a32d794ad34d7dec1368 |
25-Sep-2016 |
Tianjie Xu <xunchang@google.com> |
Log the error when uncrypt timeouts Log the error code to uncrypt_status if uncrypt gets killed because of timeout. Test: We log the error code correctly in uncrypt_status when uncrypt timeouts. Bug: 31603820 Change-Id: Ia623c333714295e68f4269257fbb4297a867e42b
hutdownThread.java
|
a2f01d04877b4521b9e991d77f945c1b83957265 |
26-Sep-2016 |
Michael Wright <michaelwr@google.com> |
Disable battery saver when booting with sufficient battery am: 2763c2ba6c am: 994c5722d6 am: 804a1d266a Change-Id: Ife535ae4d6854109a27b680f902b5fc0ace21db1
|
804a1d266a25c07bb1b60e4e355ea14fefb22c2f |
26-Sep-2016 |
Michael Wright <michaelwr@google.com> |
Disable battery saver when booting with sufficient battery am: 2763c2ba6c am: 994c5722d6 Change-Id: I0f150a292f3e5415fe18dc54143dcd5bb0ee74b1
|
994c5722d66f3b9cd3b814dc89dcace4ab9a76d8 |
26-Sep-2016 |
Michael Wright <michaelwr@google.com> |
Disable battery saver when booting with sufficient battery am: 2763c2ba6c Change-Id: I7b94bc0ce1c370d456cc9275aa1067929d4d95d0
|
03d0a367cf8b229c12e51dc5f452deb710093b20 |
20-Sep-2016 |
Wei Liu <luciferleo@google.com> |
resolve merge conflicts of 82d5fc1 to master Test: device boots Change-Id: I78e5667577e413763b6be3b06a2feda99ef0d739
|
82d5fc17b5f19b1fcd4533beb489b35b7ff58606 |
20-Sep-2016 |
Wei Liu <luciferleo@google.com> |
Make VrManager service optional. am: ef89d21a1b Change-Id: Ia0a194d34b19ca89e5acdb110a87479187fa4d85
|
ef89d21a1bf9a8b11befd9b55130816ccf9fb4fb |
20-Sep-2016 |
Wei Liu <luciferleo@google.com> |
Make VrManager service optional. b/31244699 Change-Id: I7d276e6945f19b575f880df16f140b84b03052a9
owerManagerService.java
|
1cedf00b09515c8027d99b1dc287a4b069183647 |
09-Sep-2016 |
Felipe Leme <felipeal@google.com> |
Move EventLogTags.writeDeviceIdle calls outside synchronized block. am: ea01439ef2 am: c2df6afdec am: e892b57e02 Change-Id: I26248764113b52deb10a14a7989cb4538016ae95
|
e892b57e025cf5becf630e7b588df785753a745e |
09-Sep-2016 |
Felipe Leme <felipeal@google.com> |
Move EventLogTags.writeDeviceIdle calls outside synchronized block. am: ea01439ef2 am: c2df6afdec Change-Id: I70335305b9accb01eb09f002668bbb7dbc1eba9d
|
ea01439ef2c6eb278b1b92fcdedc9e3d78a323b2 |
06-Sep-2016 |
Felipe Leme <felipeal@google.com> |
Move EventLogTags.writeDeviceIdle calls outside synchronized block. BUG: 31281543 Change-Id: I1cf5f80dda7ef0801a9fa9d0b5a5b207fc684cd5
owerManagerService.java
|
2dd30c89e2b01dd0e3aaef9432d908e66f74527c |
01-Sep-2016 |
Adam Seaton <aseaton@google.com> |
Revert "Bump up the uncrypt timeout to 30 min." Creates Null Build to test OTA failure fix. This reverts commit 8abcfed8a42a1ca517ee3c8d0448fda669ff9ded. am: b57e6560d0 am: e245037327 am: f11acea915 am: 8aa8342ee0 Change-Id: Id2a6f65eaffd27f99f41cdacb428b0c81b63be33
|
dc009e1428fab5ce9a880a5a512a3734c8796683 |
31-Aug-2016 |
Tao Bao <tbao@google.com> |
Bump up the uncrypt timeout to 30 min. am: 8abcfed8a4 am: c5a17fc39f am: 8c682f8441 am: ae71436bb0 Change-Id: I09edf5ac8289347e977b273156a7b5f85906a097
|
8aa8342ee03beac28d7988a532c4608e2c28810e |
31-Aug-2016 |
Adam Seaton <aseaton@google.com> |
Revert "Bump up the uncrypt timeout to 30 min." Creates Null Build to test OTA failure fix. This reverts commit 8abcfed8a42a1ca517ee3c8d0448fda669ff9ded. am: b57e6560d0 am: e245037327 am: f11acea915 Change-Id: I3cb97b4e58b04cc916e3c959b7b829881a0417c0
|
f11acea91531e78af19717d4aca091fba2c7c993 |
31-Aug-2016 |
Adam Seaton <aseaton@google.com> |
Revert "Bump up the uncrypt timeout to 30 min." Creates Null Build to test OTA failure fix. This reverts commit 8abcfed8a42a1ca517ee3c8d0448fda669ff9ded. am: b57e6560d0 am: e245037327 Change-Id: Ib46ce4c0e12a313f3b376634a85ae1050d655c34
|
1ceb0fcf3a61cd1eb903473b7084cbb1158d3e6f |
31-Aug-2016 |
Adam Seaton <aseaton@google.com> |
Revert "Bump up the uncrypt timeout to 30 min." Creates Null Build to test OTA failure fix. This reverts commit 8abcfed8a42a1ca517ee3c8d0448fda669ff9ded. am: b57e6560d0 am: e245037327 Change-Id: I477f3e1c5e685df2ef2a335790ab49aac6c13eef
|
e245037327738fbc82b538086c88378dc608cf15 |
31-Aug-2016 |
Adam Seaton <aseaton@google.com> |
Revert "Bump up the uncrypt timeout to 30 min." Creates Null Build to test OTA failure fix. This reverts commit 8abcfed8a42a1ca517ee3c8d0448fda669ff9ded. am: b57e6560d0 Change-Id: Idaafcb7c835aa7b7b83bb7382900ef3d18fa551f
|
b57e6560d0cc8d11b0845296831e4421d85d4441 |
31-Aug-2016 |
Adam Seaton <aseaton@google.com> |
Revert "Bump up the uncrypt timeout to 30 min." Creates Null Build to test OTA failure fix. This reverts commit 8abcfed8a42a1ca517ee3c8d0448fda669ff9ded. Change-Id: I64474dad467ce8d8e379e0e2c47814d76ac0ee0d
hutdownThread.java
|
ae71436bb02e8174d87074d83fb5521078b5dcf3 |
29-Aug-2016 |
Tao Bao <tbao@google.com> |
Bump up the uncrypt timeout to 30 min. am: 8abcfed8a4 am: c5a17fc39f am: 8c682f8441 Change-Id: I5002fd9efaaefcd63f25dcddc8e4603d6280b46b
|
18f9533910d019c844b8105faba08b9a8a0e02b4 |
29-Aug-2016 |
Tao Bao <tbao@google.com> |
Bump up the uncrypt timeout to 30 min. am: 8abcfed8a4 am: c5a17fc39f Change-Id: Ib637e1f00ddebbac5a3bea6ff31f08854a95b7ea
|
8c682f84415f9430ce58f5d7a8eedd49c1794c70 |
29-Aug-2016 |
Tao Bao <tbao@google.com> |
Bump up the uncrypt timeout to 30 min. am: 8abcfed8a4 am: c5a17fc39f Change-Id: Ie634af4f18044ffaf98c21149c1635b6ad8b9a3f
|
c5a17fc39fd22cd1dbf7483bbfd7e76f101d99c2 |
29-Aug-2016 |
Tao Bao <tbao@google.com> |
Bump up the uncrypt timeout to 30 min. am: 8abcfed8a4 Change-Id: I35340614fe09f96f8c31cc53a99e366580294490
|
8abcfed8a42a1ca517ee3c8d0448fda669ff9ded |
27-Aug-2016 |
Tao Bao <tbao@google.com> |
Bump up the uncrypt timeout to 30 min. Bug: 30490464 Change-Id: I9b65afb10134d79b2f5b5275a6d81065a04e91b9
hutdownThread.java
|
2763c2ba6c41c348920679dac20b7b4cce718408 |
11-Aug-2016 |
Michael Wright <michaelwr@google.com> |
Disable battery saver when booting with sufficient battery Bug: 29994369 Change-Id: I01d437c884e62e73dba3c1881544cfc36f953137
owerManagerService.java
|
3678d54a3f066e22c0a773e25e30c9f06039832f |
01-Aug-2016 |
Michael Wright <michaelwr@google.com> |
Prevent brightness changes before boot complete. am: 9f818ea463 am: 16890dd980 am: 3905506938 Change-Id: Ie6f3b6d55acb0e4eae40518962c1afbd70a947c2
|
39055069386dddaac929383eabc04214d1f72105 |
01-Aug-2016 |
Michael Wright <michaelwr@google.com> |
Prevent brightness changes before boot complete. am: 9f818ea463 am: 16890dd980 Change-Id: I8241a67326b055c8cabc261d5671553ff056e198
|
9f818ea463af7083fed619a7159c93905169503e |
29-Jul-2016 |
Michael Wright <michaelwr@google.com> |
Prevent brightness changes before boot complete. Bug: 29837667 Change-Id: I6385236786f6a73c64a61e1a5181c3787b68ed36
owerManagerService.java
|
ac69be543f89ea6e9a27204492e0a170d9b3450e |
30-Jun-2016 |
Svetoslav Ganov <svetoslavganov@google.com> |
Add Bluetooth toggle prompts - framework If permission review is enabled toggling bluetoth on or off results in a user prompt to collect consent. This applies only to legacy apps, i.e. ones that don't support runtime permissions as they target SDK 22. Also added a configuration resource which controls whether permission review mode is enabled. By default it is not and an OEM can change this via an overlay. For now we also keep the old mechanism to toggle review mode via a build property which is still used and will be removed when clients have transitioned. bug:28715749 Change-Id: I94c5828ad6c8aa6b363622a26ff9da4fc2e2fac7
hutdownThread.java
|
e0b1f592a0bf9334a5acfc408b6f2ac1a31c9150 |
20-Jul-2016 |
Dianne Hackborn <hackbod@google.com> |
Merge \\"Add reporting of long wake locks.\\" into nyc-mr1-dev am: ca37695ebc am: af52a9d1bf Change-Id: I29451b3dc161e29804f42f40aa9e15836979cd4a
|
af52a9d1bf5d5501d1260bfaa2807b926b1b4ed9 |
20-Jul-2016 |
Dianne Hackborn <hackbod@google.com> |
Merge \"Add reporting of long wake locks.\" into nyc-mr1-dev am: ca37695ebc Change-Id: I98b06d561945fddef5be4b749b5b2128b8622add
|
d0db6f00435b83c88f041ccf0cfcb9986ae8e6ef |
18-Jul-2016 |
Dianne Hackborn <hackbod@google.com> |
Add reporting of long wake locks. These appear as a new event in the battery stats history, "longwake" in the long version and "Elw" in the checkin. The power manager keeps track of which wake locks are held for a long time and reports them to battery stats. Long is currently considered 1 minute or more. Once it is long, the start event will appear, and once if is released the event will end. In the case of a wake lock changing (typically its work source changing), for purposes of this accounting this is considering a pure release of the old state and start of the new state... so the timer will reset back to one minute until the wake lock is considered long. This is done to prevent things that make lots of changes to wake lock work sources from spamming the log. Bug: 28753137 Change-Id: I33b6168c57a7ea6ea558273dec731704123124a5
otifier.java
owerManagerService.java
|
084c4d73e7099b3d0c5d9ba73d6d68f85da23ed8 |
07-Jul-2016 |
Shibin George <shibing@codeaurora.org> |
Merge \\\\"Resolve deadlock between ActivityManagerService and PowerManagerService\\\\" am: 06561db207 am: 2c565826ba am: 26a0b16da8 am: 43e8af64c2 Change-Id: I9c261e2c4223069f8cfa8d16a5e96babc4522af0
|
43e8af64c26677207260009850c11e6b2a9138ac |
07-Jul-2016 |
Shibin George <shibing@codeaurora.org> |
Merge \\\"Resolve deadlock between ActivityManagerService and PowerManagerService\\\" am: 06561db207 am: 2c565826ba am: 26a0b16da8 Change-Id: Ib90892556fde2bf8c53a7074b5d2702059adff65
|
2c565826bac683a59cdcf4694077d75e5adf0670 |
07-Jul-2016 |
Shibin George <shibing@codeaurora.org> |
Merge \"Resolve deadlock between ActivityManagerService and PowerManagerService\" am: 06561db207 Change-Id: I7f78cf1ef0c490aceb527dbc82228d00fae2f7e4
|
43f5de0125a22e9bcc4cf675034116f754f3bfc2 |
05-Jul-2016 |
Shibin George <shibing@codeaurora.org> |
Resolve deadlock between ActivityManagerService and PowerManagerService ActivityManagerService lock and PowerManagerService.mLock can be acquired in different threads in different orders. registerReceiver() here tries to acquire ActivityManagerService internally while holding mLock. A particular call from WindowManagerService acquires these locks in reverse order. This deadlock can be resolved by moving registerReceiver() to another thread. https://code.google.com/p/android/issues/detail?id=215254 Change-Id: I12cd610e61f212a3fb5e441f2c7a557c90afbda4 Signed-off-by: Shibin George <shibing@codeaurora.org>
owerManagerService.java
|
2e33e0df3c1017b865c2fd6662325a9d203ad4ec |
24-Jun-2016 |
Amith Yamasani <yamasani@google.com> |
Merge \\"Resetting some settings on starting a new demo session\\" into nyc-mr1-dev am: bb1fb395ca am: 5c451c08bc Change-Id: I7e44f3ec7c29d0e1adfd5e4baff1cbfba7368bcc
|
6472501f2e7ba018d8aa43c61e55874d756cecb8 |
15-Jun-2016 |
Suprabh Shukla <suprabh@google.com> |
Resetting some settings on starting a new demo session Muting ringer and media volume and turning off the flashlight before starting a new session. Also, resetting the configuration of any new demo user to the configuration of user 0 on the device. Moved RetailDemoModeService and RetailDemoModeServiceInternal to more appropriate new packages Bug: 29519612 Change-Id: Ib65f89ce61afab2d2f1b2dd0c761f5d35a466181
otifier.java
|
296a6319b586730fa636ade9ac0b005def50e2e6 |
03-Jun-2016 |
Suprabh Shukla <suprabh@google.com> |
Merge "Adding an idle timeout to restart demo session" into nyc-mr1-dev am: 67f82d16ea am: 0f4ae5e1a6 * commit '0f4ae5e1a6600763a6ac0180b4bde7e20b041a97': Adding an idle timeout to restart demo session Change-Id: Ib0c2b6641134c91a03b374a2c59d7b3642b6385e
|
5915d1b7567c07506651df2349eca0f6e35f7538 |
02-Jun-2016 |
Suprabh Shukla <suprabh@google.com> |
Adding an idle timeout to restart demo session Tracking user activity from RetailModeManagerService to start and switch to a new demo user when there has been no activity for a long time and the demo video player has been disabled. Bug: 27280140 Change-Id: Iebf37b5d04a659e4bfda0e4016111c7b9e5f4eb9
otifier.java
|
f44d5bcf4fecc1c51dc47bdd241c5bcf19b00ad2 |
27-May-2016 |
Christine Hallstrom <hallstrom@google.com> |
Merge "Properly check if BT is off when shutting down radios" into nyc-mr1-dev am: 0f760e0815 am: fa72d4caff * commit 'fa72d4caffce6f1b7adf5e04f8643fc8e2ebb243': Properly check if BT is off when shutting down radios Change-Id: I16d921e8aac53b21c4007e697dc4d5e2f2a4fa4f
|
995c90aa1856e8ef7b3397b775720941d3dcb133 |
26-May-2016 |
Christine Hallstrom <hallstrom@google.com> |
Properly check if BT is off when shutting down radios Use BluetoothAdapter#getState() instead of BluetoothAdapter#isEnabled() when checking if Bluetooth has turned off, as isEnabled() is set to false early in the shutdown process and getState() provides a better indication of the state of BT. Bug: 27354612 Change-Id: Ic7828f0726491d49c9a14ba5d654b24f66743662
hutdownThread.java
|
a2b96b1c8c6b11e21bc16d8ea2c29e0e214b3f39 |
21-Apr-2016 |
Ruchi Kandoi <kandoiruchi@google.com> |
Merge "Revert "PowerManager: Adds the Sustained performance API."" into nyc-dev am: 0fea8ad am: 4c24df5 am: d84169a92f * commit 'd84169a92ffe2137a7e53c2debcde42cf2eb1878': Revert "PowerManager: Adds the Sustained performance API." Change-Id: Iadb804137b77b1fd9f20da6b03c2b8e30617ed0c
|
9c36c02f0ea5f54bcb7cdf2a6175f4b8f92205a2 |
20-Apr-2016 |
Ruchi Kandoi <kandoiruchi@google.com> |
Revert "PowerManager: Adds the Sustained performance API." This reverts commit 0abc001275d6cf0af4990f521ccff7346a7cd2bf. Bug: 28150358 Change-Id: I99c71b3d6641310a33e898d6fd475d37c79ba9d0 Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
owerManagerService.java
|
56c682d7c1fe121d8c879525a23f7aa1cbb3b776 |
08-Apr-2016 |
Paul Lawrence <paullawrence@google.com> |
Merge "Add setting and detection of ro.sys.safemode property." into nyc-dev am: c0a8fa8 am: 8aa6242 * commit '8aa6242cb547806bdbff4e7e873bde1d563f40ab': Add setting and detection of ro.sys.safemode property. Change-Id: I640b31ccd802f6c1cec57e24f913d3757ebbd804
|
f44f5a460e9610e027a3b6257b1cf904dc3afbc7 |
03-Mar-2016 |
dcashman <dcashman@google.com> |
Add setting and detection of ro.sys.safemode property. Bug: 28008032 Change-Id: I6b19b32df615becd88a56a337c999b57011c6200
hutdownThread.java
|
4a49791ef97226b08d9ce4977b5212074f8e160d |
06-Apr-2016 |
Ruben Brunk <rubenbrunk@google.com> |
Merge "Add VrManager AIDL interface for use by system apps." into nyc-dev am: 50e229f am: bc783e0 * commit 'bc783e038c17524c5182ad6b5e17ba95d0e1a319': Add VrManager AIDL interface for use by system apps. Change-Id: Ie3aaad8ef509f69c643638f8974a95e1f33a7a60
|
c7be3beced4ade05466a4a77c003ea81c2429f74 |
02-Apr-2016 |
Ruben Brunk <rubenbrunk@google.com> |
Add VrManager AIDL interface for use by system apps. Bug: 27884853 Change-Id: I6de0d291deafe5003070d60866c60d6599312e79
owerManagerService.java
|
a823c4e27151d99ebbc855c22604312745759e87 |
03-Apr-2016 |
Jeff Sharkey <jsharkey@android.com> |
Merge "Support direct-boot tests." into nyc-dev am: 7d718bb am: 7fc8b9c * commit '7fc8b9ce48a74011befdaf3be15a2cc952398433': Support direct-boot tests. Change-Id: I946f2a960ab0cfb0f56477a3d5e6da07d17aa5bd
|
b5e89c6debca90be92bf5bc2e0e79d109de6d08f |
02-Apr-2016 |
Jeff Sharkey <jsharkey@android.com> |
Support direct-boot tests. Add shell commands to check on current FBE status and system ready status. Mark variables without first-class locking as volatile. Fix bug where UI automation would crash while device was locked by marking it as forced direct-boot aware. Bug: 26498834 Change-Id: Ib4dfb9350925e5413f93a09baacf84c62f2ba0ea
owerManagerService.java
|
defdd7bd34be0d6c2ca49205e05d08f2268f871a |
21-Mar-2016 |
Ruchi Kandoi <kandoiruchi@google.com> |
Merge "PowerManagerService: Adds a VrStateListener to track Vr Mode state changes." into nyc-dev am: fb811aa am: 98c1972 * commit '98c1972a7277fc551219c2cbf7a1d9e78e32e2ce': PowerManagerService: Adds a VrStateListener to track Vr Mode state changes.
|
fb811aaf4dd062c1ef3581522acb523680f081f3 |
21-Mar-2016 |
Ruchi Kandoi <kandoiruchi@google.com> |
Merge "PowerManagerService: Adds a VrStateListener to track Vr Mode state changes." into nyc-dev
|
2f69f042e0ace7687d2b56e23e24b4711c0b4cfd |
18-Mar-2016 |
Tony Mantler <nicoya@google.com> |
Merge "Add safe-mode reboot to PowerManager" into nyc-dev am: e6e08b4 am: 6f61fd5 * commit '6f61fd538ece71095c686d73991d91138bb5e011': Add safe-mode reboot to PowerManager
|
b8009fddd85aa5ecd6b2321f92a1ae0568089a54 |
14-Mar-2016 |
Tony Mantler <nicoya@google.com> |
Add safe-mode reboot to PowerManager b/12787723 Change-Id: If7e6ff63532b49b9e758db290a877f7dbfa8a8b7
owerManagerService.java
|
03a0428ed3857d1881def7c2767a15acfacfa999 |
15-Mar-2016 |
Ruchi Kandoi <kandoiruchi@google.com> |
PowerManagerService: Adds a VrStateListener to track Vr Mode state changes. PowerManagerService sends VR_MODE hints to the powerHAL for device-specific power tunings. Bug: 27659731 Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com> Change-Id: I152d9b6adfbae5d3df8d131fdd16e33fb14b64d3
owerManagerService.java
|
3a103655835702a227fffa8fcc41525e145b00f9 |
08-Mar-2016 |
Daichi Hirono <hirono@google.com> |
Merge "Add a new key to Settings.Global to obtain the number of boot." into nyc-dev am: d517e6aeed am: e07d5b62ed * commit 'e07d5b62ed6d58f8f81383e6ecde03b1181e08f3': Add a new key to Settings.Global to obtain the number of boot.
|
82ab9801ebebe8e4783ad327ad02686b44ab87f1 |
02-Mar-2016 |
Daichi Hirono <hirono@google.com> |
Add a new key to Settings.Global to obtain the number of boot. BUG=26212981 Change-Id: I5ca51ca624a30dc2d96e547a85a712e273af1931
owerManagerService.java
|
e50adc8e464f80802d80f32b9f3476e860b9f297 |
02-Mar-2016 |
Jeff Sharkey <jsharkey@android.com> |
Merge "Delay power broadcasts until system is booted." into nyc-dev am: c9a91cc050 am: 99723c720d * commit '99723c720dfd009c05ef4717cb6597ae245a98d8': Delay power broadcasts until system is booted.
|
3dee8d6787617a7d3da4faef2ad88c08151ea3eb |
02-Mar-2016 |
Jeff Sharkey <jsharkey@android.com> |
Delay power broadcasts until system is booted. When the system isn't booted yet, enqueue any early broadcasts to be sent after the system is ready. Bug: 27449137 Change-Id: I5a93be3a2cf4d038149b54e0510b040fd69d3579
owerManagerService.java
|
a6e9e24be53d2516138f487e340e46b8d0212d86 |
05-Feb-2016 |
Sami Tolvanen <samitolvanen@google.com> |
Support persist.sys.audit_safemode Don't leave safe more if persist.sys.audit_safemode is set, unless the current build date is newer than the specified value. This allows us to keep the device in safe mode across reboots until an OTA has been applied or user data is wiped. Bug: 26902605 Change-Id: I781c3059ea8d4fb2f0c923e4488b1932d69678d3 (cherry picked from commit ee2b49283261f7b4518ec7c98f568f883f817c9d)
hutdownThread.java
|
69d01e2376da87a358c15d79222ef4f8f67a0a65 |
22-Feb-2016 |
Tao Bao <tbao@google.com> |
Merge "Add support for update-on-boot feature." into nyc-dev am: 9de7952aa9 am: 3dd23af6a0 * commit '3dd23af6a0fb58ce7d1f6f078c765890ca839bd3': Add support for update-on-boot feature.
|
3dd23af6a0fb58ce7d1f6f078c765890ca839bd3 |
22-Feb-2016 |
Tao Bao <tbao@google.com> |
Merge "Add support for update-on-boot feature." into nyc-dev am: 9de7952aa9 * commit '9de7952aa945eb06148f82b9f30d7d11a2de5d74': Add support for update-on-boot feature.
|
e8a403d57c8ea540f8287cdaee8b90f0cf9626a3 |
31-Dec-2015 |
Tao Bao <tbao@google.com> |
Add support for update-on-boot feature. Add a separate system service RecoverySystemService to handle recovery related requests (calling uncrypt to de-encrypt the OTA package on the /data partition, setting up bootloader control block (aka BCB) and etc). We used to trigger uncrypt in ShutdownThread before rebooting into recovery. Now we expose new SystemApi (RecoverySystem.processPackage()) to allow the caller (e.g. GmsCore) to call that upfront before initiating a reboot. This will reduce the reboot time and get rid of the progress bar ("processing update package"). However, we need to reserve the functionality in ShutdownThread to optionally call uncrypt if finding that's still needed. In order to support the update-on-boot feature, we also add new SystemApis scheduleUpdateOnBoot() and cancelScheduledUpdate() into android.os.RecoverySystem. They allow the caller (e.g. GmsCore) to schedule / cancel an update by setting up the BCB, which will be read by the bootloader and the recovery image. With the new SystemApis, an update package can be processed (uncrypt'd) in the background and scheduled to be installed at the next boot. Bug: 26830925 Change-Id: Ic606fcf5b31c54ce54f0ab12c1768fef0fa64560
owerManagerService.java
hutdownThread.java
|
9e4f241ba454b5778b47c8b91f43d8b76cd41870 |
19-Feb-2016 |
Jason Monk <jmonk@google.com> |
Merge changes Ie427a2d8,I213f1f76 into nyc-dev am: ea168d229d am: 0aecf08207 * commit '0aecf08207267bcbf36af9c8f4dd8daad0f14283': SysUI Tuner: UI cleanup and grouping SysUI Tuner: Night mode v3
|
0aecf08207267bcbf36af9c8f4dd8daad0f14283 |
19-Feb-2016 |
Jason Monk <jmonk@google.com> |
Merge changes Ie427a2d8,I213f1f76 into nyc-dev am: ea168d229d * commit 'ea168d229d316c84652e88ad0f19adbaa884d731': SysUI Tuner: UI cleanup and grouping SysUI Tuner: Night mode v3
|
5dbd4aad809e6fec51df62280bcc1bfe05cc7df5 |
07-Feb-2016 |
Jason Monk <jmonk@google.com> |
SysUI Tuner: Night mode v3 TwilightService: - Add support for locking on/off twilight globally - Change twilight state to have float amount rather than having clients calculate it using the sunrise/set values - State controlled through secure setting - Override mode which locks to a state for a couple hours then resets - Add broadcast for SysUI to listen to Brightness/Power: - Updates to handle TwilightService changes - Added secure setting to control whether or not to use twilight when calculating brightness. Tuner: - UI Overhall - NightModeController will set the values of the custom color matrix taking into account the current twilight service state and any custom calibration set by the user. - Probably other stuff. Change-Id: I213f1f76a143e711c507b2ba7d784f581bfc32b4
owerManagerService.java
|
099e4c042b9b5029a78a4c030715a36c538e0ee3 |
17-Feb-2016 |
Sami Tolvanen <samitolvanen@google.com> |
resolve merge conflicts of dcc79d83cb to nyc-dev-plus-aosp am: 37e394e7d5 * commit '37e394e7d5965ac2b29e5681fe4107d6f4dbb38c': Support persist.sys.audit_safemode
|
37e394e7d5965ac2b29e5681fe4107d6f4dbb38c |
17-Feb-2016 |
Sami Tolvanen <samitolvanen@google.com> |
resolve merge conflicts of dcc79d83cb to nyc-dev-plus-aosp Change-Id: I9694d443db9ddfe7b44ffb13dd922fbc233876b4
|
05a9f1d89ab473be2959e4a9ad78dfa5ea9c7d7a |
12-Feb-2016 |
Dianne Hackborn <hackbod@google.com> |
Fix crash during boot. Broadcast should only be going to registered receivers. Change-Id: I7b70cd2bd38f0ff0448cb9786d821c7e41a0e269
owerManagerService.java
|
ee2b49283261f7b4518ec7c98f568f883f817c9d |
05-Feb-2016 |
Sami Tolvanen <samitolvanen@google.com> |
Support persist.sys.audit_safemode Don't leave safe more if persist.sys.audit_safemode is set, unless the current build date is newer than the specified value. This allows us to keep the device in safe mode across reboots until an OTA has been applied or user data is wiped. Bug: 26902605 Change-Id: I781c3059ea8d4fb2f0c923e4488b1932d69678d3
hutdownThread.java
|
0abc001275d6cf0af4990f521ccff7346a7cd2bf |
12-Jan-2016 |
Ruchi Kandoi <kandoiruchi@google.com> |
PowerManager: Adds the Sustained performance API. Adds a new type of wakelock - SUSTAINED_PERFORMANCE_WAKELOCK. This wakelock can only be acquired when the application is in the foreground. And it is not effective when the application is no longer in the foreground. Acquiring this wakelock enables the Sustained performance mode which guarantees a certain level of performance. Bug: 22864186 Change-Id: Id0ececc756fe014779db6efde7aede23ea181dc5 Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
owerManagerService.java
|
afae4bd437563c3997740ff6a537108409f7884c |
15-Dec-2015 |
Jason Monk <jmonk@google.com> |
Add internal power mode changed broadcast This broadcast allows settings to be (rarely) be started by a power change event. Settings will have a conditional item informing the user of battery saving mode, when they dismiss it, the item will not show up again until after power saving mode has been exited and re-entered. Settings will catch the exit of power saving mode by enabling a receiver for this broadcast only when in this state. Change-Id: I62385413e4b8b004d4e1e0e5ba250730848ba013
owerManagerService.java
|
08c47a5dece977a55d250d98bda9e2a8df8b6ed0 |
15-Oct-2015 |
Dianne Hackborn <hackbod@google.com> |
Initial implementation of light-weight idle mode. This mode turns on after the screen has been off for 15 minutes, and then cycles through 15 minutes of idle and 1 minute of maintenance, ragardless of whether the device is moving around. It currently only impacts network access and sync/job scheduling. It does not remove access to wake locks or alarms for any apps. It also doesn't report in the public API that the device is in idle mode (since it isn't modifying the behavior of the power manager) -- this is probably what we desire, since we don't want stuff like GCM to be reporting these frequent changes. We'll probably at least want to have the alarm manager do some kind of more aggressive batching of alarms in this most (not allowing more than one wakeup every minute?). That's for the future. Also updated batterystats to include this new information, which means the format of some of the data has changed -- device_idle is no longer a flag, but an enum of (off, light, full), and there is no information about time spent in light modes. Also added new data about the maximum duration spent in both light and full idle modes, to get a better understanding of how those are behaving. And did a little cleanup of DeviceIdleController, removing the sensing alarm which was redundant with the regular alarm. Change-Id: Ibeea6659577dc02deff58f048f97fcd9b0223307
owerManagerService.java
|
dd62fb4392664c3c7dc43c7556351b36cf17dcf2 |
05-Oct-2015 |
Nick Armstrong-Crews <strongarm@google.com> |
am f107709f: am 13a71fbc: Merge "Fix the logging of wake time saved by Ungaze." into cw-e-dev * commit 'f107709fb3f884f904deb1f3c09a88dd411ea30d': Fix the logging of wake time saved by Ungaze.
|
024872ea70bf82a8526e7b91a28a936cb432b095 |
01-Oct-2015 |
Nick Armstrong-Crews <strongarm@google.com> |
Fix the logging of wake time saved by Ungaze. The logging of saved time was erroneously being called more than once per wake period. Moved the logging logic to be called from finishWakefulnessChange(), which is only called once per wake period. Change-Id: I268ef44edce5807644fcc8fb0dcaa1a96cae6c9e
owerManagerService.java
|
08dcdb1a5beac29643dca2a03c2e308760de636d |
23-Sep-2015 |
Mojtaba Seyedhosseini <mseyed@google.com> |
am d70a7737: am 6e7cbb7c: Merge "Add logs for the ungaze gesture." into cw-e-dev * commit 'd70a773793bf9fce06ba8888908601b94090236d': Add logs for the ungaze gesture.
|
2d80edc232cad7d5fe17c2eb14d4263cbe2c757c |
19-Sep-2015 |
Mojtaba <mseyed@google.com> |
Add logs for the ungaze gesture. -We add logs to track how much screen time we save with the ungaze feature. Change-Id: I02bce959ce7ed5bc6c848e51256063c946ff3e87
owerManagerService.java
|
0816319a29709ed746682b17400b34b6f540ca56 |
17-Sep-2015 |
Tim Murray <timmurray@google.com> |
am 4816ea0e: am a02f9823: am 952d5b33: Merge "Send power hint on fling gestures." into mnc-dr-dev * commit '4816ea0e120fd4e2892d372f33c8ca21e4b2efb6': Send power hint on fling gestures.
|
a02f98239ea683b802ede31382f51eb88eda05d3 |
17-Sep-2015 |
Tim Murray <timmurray@google.com> |
am 952d5b33: Merge "Send power hint on fling gestures." into mnc-dr-dev * commit '952d5b334ccdf9cab0f56673861906e59d4e9933': Send power hint on fling gestures.
|
a4d22d718affbc7145d1012157feb819557b5c06 |
17-Sep-2015 |
Michael Wright <michaelwr@google.com> |
Send power hint on fling gestures. Use the existing PointerEventListener infrastructure to listen for gestures that look like flings and hint to the power system when they happen. Since we don't actually have a bound for the fling like a regular application would, limit them to five seconds and refresh every time a new fling is seen until the five second time period is up. bug 24059298 Change-Id: I5757a1e88f2ab2ef08cccefa8221d809ae71bb6f
owerManagerService.java
|
13d2fa50b0815c63d2d289c27d8edacf1ace01eb |
08-Sep-2015 |
Nick Armstrong-Crews <strongarm@google.com> |
am 740cf71c: am 56ecfcce: Handle KEYCODE_SOFT_SLEEP from Ungaze. * commit '740cf71c9978e5dcb0a68b6558531a52dc26d44f': Handle KEYCODE_SOFT_SLEEP from Ungaze.
|
56ecfcce6c88fc80cf509effcebb124bbe0c79f8 |
08-Sep-2015 |
Nick Armstrong-Crews <strongarm@google.com> |
Handle KEYCODE_SOFT_SLEEP from Ungaze. Needed for Ungaze to trigger "soft sleep" (respecting wake locks); operates by sending new KEYCODE_SOFT_SLEEP to PhoneWindowManager, which calls PowerManagerService's new method setUserInactiveOverride (thereby causing immediate sleep, modulo wakelocks, upon next iteration of PowerManagerService's main loop). BUG: b/23589870 Change-Id: Iddafdde923605d119075e890eeda5d3fd3fd2bc7
owerManagerService.java
|
d70377b537450d03d5cdc2efb15977d48e5cfebd |
08-Sep-2015 |
Nick Armstrong-Crews <strongarm@google.com> |
am 36afc2b7: am 9b8f82a3: Merge "Revert "Handle KEYCODE_SOFT_SLEEP from Ungaze."" into cw-e-dev * commit '36afc2b76743b2b2803da20dc6a8b2142d1f9b17': Revert "Handle KEYCODE_SOFT_SLEEP from Ungaze."
|
b331bf951499396111cb47b477ac35e82c805322 |
08-Sep-2015 |
Nick Armstrong-Crews <strongarm@google.com> |
Revert "Handle KEYCODE_SOFT_SLEEP from Ungaze." This reverts commit 677adf1e66ba83b8fb2c849c181303b35bd489bc. Hiding new keycode to prevent change to public API before resubmitting. Change-Id: Ic43273dd0c7ade1d51a36b77f363543f1df466e8
owerManagerService.java
|
7f37402d8c5667f72c1ef02a20112d49d7a149b8 |
04-Sep-2015 |
Nick Armstrong-Crews <strongarm@google.com> |
am 43c4459d: am 6f0ba402: Merge "Handle KEYCODE_SOFT_SLEEP from Ungaze." into cw-e-dev * commit '43c4459d995ce7a723d92945a7e4ccb81d48e224': Handle KEYCODE_SOFT_SLEEP from Ungaze.
|
677adf1e66ba83b8fb2c849c181303b35bd489bc |
27-Aug-2015 |
Nick Armstrong-Crews <strongarm@google.com> |
Handle KEYCODE_SOFT_SLEEP from Ungaze. Needed for Ungaze to trigger "soft sleep" (respecting wake locks); operates by sending new KEYCODE_SOFT_SLEEP to PhoneWindowManager, which calls PowerManagerService's new method setUserInactiveOverride (thereby causing immediate sleep, modulo wakelocks, upon next iteration of PowerManagerService's main loop). BUG: b/23589870 Change-Id: I24a96bd6db8ff28674c907f2898e49c4f6140209
owerManagerService.java
|
82e780743046e620b724c28023b580e0e624bb15 |
03-Aug-2015 |
Yusuke Sato <yusukes@google.com> |
am b98e2353: am 158560ad: Merge "Distinguish user-requested shutdown from power-related ones" * commit 'b98e235364c2b221521f622c546733b2862e4677': Distinguish user-requested shutdown from power-related ones
|
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
owerManagerService.java
hutdownThread.java
|
6ad2d66072795dd9836350b273dcde52910ab4c3 |
18-Jul-2015 |
Billy Lau <billylau@google.com> |
Bug: 21589105 Rescope WRITE_SETTINGS permission (framework services perm check changes) AppOpsManager: Changed the default operating mode for WRITE_SETTINGS to MODE_DEFAULT from MODE_ALLOWED. packages/SettingsProvider: We no longer do static permission checks for WRITE_SETTINGS in early checks and defer that to app op when MODE_DEFAULT is returned. For some operations, checking against WRITE_SECURE_SETTINGS is sufficient. ActivityManagerService & PowerManagerService: Incorporated app op checks and handled the MODE_DEFAULT case. provider/Settings: Added helper function to do checks on whether app ops protected operations can be performed by a caller. This includes checks for WRITE_SETTINGS and SYSTEM_ALERT_WINDOW. Also added a public API (with javadocs) for apps to query if they can modify system settings. Changed the javadocs description for ACTION_MANAGE_WRITE_SETTINGS and ACTION_MANAGE_OVERLAY_PERMISSION. Added public API (with javadocs) for apps to query whether they can draw overlays or not, and also javadocs description on how to use that check. Change-Id: I7b651fe8af836c2074defdbd6acfec3f32acdbe9
owerManagerService.java
|
fa6e0a80e20a4917b403fd330e01a9edd021aabc |
24-Jul-2015 |
Yohei Yukawa <yukawa@google.com> |
Don't rely on broadcast intent for waking up input method. Basically this is a copy of Iabef96921dd554ce3768fb18619cefc for InputMethodManagerService. As described in JavaDoc of Intent#ACTION_SCREEN_OFF and Intent#ACTION_SCREEN_ON, one can use those Intents to be notified when the device becomes non-interactive and interactive. IMMS has relied on them to enable and disable InputConnection between the IME and the application so as not to allow IMEs to update text when the user does not present. This is actually our design goal as documented in JavaDoc of InputMethodManager. An IME can never interact with an InputConnection while the screen is off. This is enforced by making all clients inactive while the screen is off, and prevents bad IMEs from driving the UI when the user can not be aware of its behavior. The goal of this CL is to improve the timeliness of above mechianism by introducing a direct communication channel from PowerManagerService to InputMethodManagerService via Notifier. Actually this is what InputManager has been doing since Iabef96921dd554ce3768fb18619cefc3230b5fb0. Reasons behind this change are: 1. There are several bugreports that imply those Intents can dispatch tens of seconds after it is enqueued. This is indeed problematic because the user cannot type password to unlock their devices until queued Intent#ACTION_SCREEN_ON is dispatched. This CL addresses such an issue without waiting for figuring out the root cause of the delay. 2. Intent#ACTION_SCREEN_OFF and Intent#ACTION_SCREEN_ON are sent as a ordered broadcast, which may not be suitable for tasks that require a certain level of timeliness, and what IMMS wants is to enable users to start typing immediately after the system. This CL was originally authored by Seigo Nonaka. Bug: 22423200 Bug: 22555778 Change-Id: I747c37ff6dd8f233faef43f2b5713a4320e848eb
otifier.java
|
280a64e793d081847c5dcea23ed9be38aa5332d2 |
13-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Improve tracking of screen on reasons. - New screen on app op to record the last time each app has caused the screen to be turned on. - New battery stats event that tells us the reason the screen has been asked to turn on. - Propagate out power manager API to specify the reason a caller is asking to have the screen turned on. Note that currently the window flag to turn the screen on bypasses much of this because it is being handled in the window manager by just directly telling the power manager to turn the screen on. To make this better we need a new API where it can specify who it is calling the API for. Change-Id: I667e56cb1f80508d054da004db667efbcc22e971
otifier.java
owerManagerService.java
|
3b16cf4f47142a845bf0ede54ef8ef956506c6c3 |
02-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Device idle fixes: issue #22209630 and issue #22225665 Issue #22209630: Only allow whitelisted apps to put apps on the temp whitelist We now check whether the calling app is a system uid or in the whitelist and, if not, throw an exception. Issue #22225665: Alarm still goes off in idle mode (doze) Fix a bug where we were not clearing the calling identity when coming through the dump command to the service, and as a result when we would eventually call out to the alarm manager it wouldn't do what we want. This was only broken when being controlled by the shell. Also adjust the network policy manager service's handling of device idle transitions to only toggle the device idle state, which gets rid of the long delay we have coming out of idle mode. And add in a bit of logging around going in/out of idle mode to try to understand where things may be slow in the future. Change-Id: I4a41f790e9b0bb31330314b94111557d479f2ba5
owerManagerService.java
|
63ec93d57094be624f2069d063146ca713574530 |
26-Jun-2015 |
Jim Miller <jaggies@google.com> |
Merge "Have FingerprintService keep the device awake on relevant events." into mnc-dev
|
c4bd42c1eedefca4f15816e4e00af617dcfc8993 |
13-Jun-2015 |
Jeff Brown <jeffbrown@google.com> |
Fix reporting of wakelocks to battery stats. Fixed certain wake lock types which were being incorrectly reported to BatteryStats as WAKE_TYPE_FULL due to incomplete decoding of the wake lock level. Bug: 21949905 Change-Id: Ie3abfc9f473ce721ad042d228175592c7b8ede33
otifier.java
owerManagerService.java
|
dca15d22e8f37d4bc2dfb6db4522ea166149525b |
17-Jun-2015 |
Jim Miller <jaggies@google.com> |
Have FingerprintService keep the device awake on relevant events. Fixes bug 20732273 Change-Id: I61b827dd7b1bc706a0288571751032301fd5479f
owerManagerService.java
|
f2a91ee148a3b753f85abff0d8adeace0c713726 |
03-Jun-2015 |
Tao Bao <tbao@google.com> |
Improve the reboot-to-recovery dialogs To address the UX comments, this CL modifies the dialogs when the device is rebooted to install an update or to perform factory data reset. Bug: 20949086 (cherry picked from commit 81dce6631396012e8b722bbed6d003f584800ae1) Change-Id: I6d0cbbbaf184806366c6581c1c2e7dbcc5d89a17
hutdownThread.java
|
fa861429f7ec0b9f83a2baacc3c6fb680467039b |
22-May-2015 |
Tao Bao <tbao@google.com> |
Wait for uncrypt to finish before rebooting /system/bin/uncrypt needs to be triggered to prepare the OTA package before rebooting into the recovery. For larger packages, uncrypt may be killed before it finishes the work after the timeout. Change to monitor the uncrypt status and show the progress to user. Needs matching changes in bootable/recovery/uncrypt, system/core and external/sepolicy. Also pick up the two NPE fixes in commits 9bb765448df43d41e0a3edb7de1d1641c9251c35 and da3f63ffb87397943546a7c5c893ce98f2489df2. Bug: 20012567 Bug: 20949086 (cherry picked from commit 90237f7beb55dae79cdcba5271f96be778573737) Change-Id: Ibf2fc80032967e5f6cda3cd469005dd29665c87c
owerManagerService.java
hutdownThread.java
|
81dce6631396012e8b722bbed6d003f584800ae1 |
03-Jun-2015 |
Tao Bao <tbao@google.com> |
Improve the reboot-to-recovery dialogs To address the UX comments, this CL modifies the dialogs when the device is rebooted to install an update or to perform factory data reset. Bug: 20949086 Change-Id: Icc1cdec7e0336ae37c17fffde7dae7ff882e5470
hutdownThread.java
|
ff3b76d04672d09214cd0ceb29ec548c8abb2330 |
02-Jun-2015 |
Amith Yamasani <yamasani@google.com> |
Merge "Temporarily whitelist an app for network during doze" into mnc-dev
|
983d449a84b6040e15368da925149419fc6b7010 |
02-Jun-2015 |
Tao Bao <tbao@google.com> |
Fix the NPE when checking mRebootReason Bug: 21584198 Change-Id: Ie11092dbc771b54bd049d258dc705835a3eda494
hutdownThread.java
|
af575b9f8e1b59be9c8862b6a65c0dcb88145a23 |
30-May-2015 |
Amith Yamasani <yamasani@google.com> |
Temporarily whitelist an app for network during doze API to allow an app to be whitelisted for network and wakelock access for a short period. So even if the device is in idle mode, such apps can be given a chance to download the payload related to a high priority cloud-to-device message. This API is meant for system apps only. A new permission CHANGE_DEVICE_IDLE_TEMP_WHITELIST is required to make this call. Bug: 21525864 Change-Id: Id7a761a664f21af5d7ff55aa56e8df98d15511ca
owerManagerService.java
|
cb81d183672a3d9858ade10a997990c5d66a1be3 |
30-May-2015 |
Jeff Brown <jeffbrown@google.com> |
Merge "Tell PhoneWindowManager when we start/finish interactive changes." into mnc-dev
|
416c49c4049f572134273e228d7988904a51b990 |
27-May-2015 |
Jeff Brown <jeffbrown@google.com> |
Tell PhoneWindowManager when we start/finish interactive changes. Added some new callbacks that can be used to more precisely trigger certain behaviors that need to happen around the time the device is put to sleep and locked. Fixed an issue where the going to sleep signal might be sent too early on devices that don't support ambient mode due to the extra wakefulness change between DOZING and ASLEEP. We are now track the early / late interactive change work separately from the rest. Bug: 21375811 Change-Id: I95387195e216ae92a6e45485bd1bd362e41aa45a
otifier.java
owerManagerService.java
|
9bb765448df43d41e0a3edb7de1d1641c9251c35 |
29-May-2015 |
Guang Zhu <guangzhu@google.com> |
fix NPE in shutdown thread null reboot reason is used when it's a simple reboot. Change-Id: I9d3110ca733a1b0401721fde907924c101997c4f
hutdownThread.java
|
165102f350e08bd186b25b90dd8a42aad8975890 |
28-May-2015 |
Tao Bao <tbao@google.com> |
Merge "Wait for uncrypt to finish before rebooting" into mnc-dev
|
90237f7beb55dae79cdcba5271f96be778573737 |
22-May-2015 |
Tao Bao <tbao@google.com> |
Wait for uncrypt to finish before rebooting /system/bin/uncrypt needs to be triggered to prepare the OTA package before rebooting into the recovery. For larger packages, uncrypt may be killed before it finishes the work after the timeout. Change to monitor the uncrypt status and show the progress to user. Needs matching changes in bootable/recovery/uncrypt, system/core and external/sepolicy. Bug: 20012567 Bug: 20949086 Change-Id: I2348a98312c4dae81f618b45a2ee3b4cf6246ff5
owerManagerService.java
hutdownThread.java
|
d23e0d6901935588f9472bd7073fea0009581e9b |
16-May-2015 |
Dianne Hackborn <hackbod@google.com> |
Update power manager to track uid state like netstats. To follow the correct semantics for when restricts due to device idle can be applied, power manager need to know about uid process states like net policy so that it can allow wake locks from apps that are in the foreground. Since this is being added to a second place, I reworked things so that the activity manager now keeps track of per-uid process states and allows apps to register to listen to those, rather than having to track lower-level process states and transform them into an overall uid state. Both net policy and power manager use this new facility. Change-Id: I77359164c40d0f36fe1ef296dd9f9c3062431148
owerManagerService.java
|
27bbb2d0a1c8a3bb38768511ac840c3388b0fb03 |
31-Mar-2015 |
Jason Monk <jmonk@google.com> |
Add control for double tap to wake setting Bug: 16875464 Change-Id: Ic1ad910dd38acbc68ef040b2acdf3696ec2c2e4e
owerManagerService.java
|
9c8600e1af1af6eb2f57a965bbfe941fbd082786 |
12-May-2015 |
Dianne Hackborn <hackbod@google.com> |
Merge "Implement device idle in power manager." into mnc-dev
|
8d66b3fbf5d8036e25d64a8472bcd2b6b7892a1a |
09-May-2015 |
Dianne Hackborn <hackbod@google.com> |
Implement device idle in power manager. When in device idle mode, we now prevent most apps from being able to hold partial wake locks. The device idle controller now pushes its white list of app uids into the power manager, so it can apply this policy correctly to only apps that are not whitelisted. The implementation adds a new "disabled" flag to a wake lock which is set when we want to apply this policy. When set, we ensure that we tell battery stats that the wake lock is not being held and ignore that wake lock when computing the power state summary. Also add new SDK APIs to schedule alarms that are allowed to execute while in idle mode. Finally add new dumpsys commands to the device idle controller to completely disable and re-enable its operation, to use for testing. Change-Id: I1f16672c6ac06d03bb538f9854d5843db9aa6f27
owerManagerService.java
|
51a871d48a9f4d912b2c12c29bbddcc5ec175825 |
06-May-2015 |
John Spurlock <jspurlock@google.com> |
Add setting to mute wireless charging sound. Bug: 19538553 Change-Id: I1af971b35ae9eeb38d8ec38c57b22152095e2725
otifier.java
|
df7f02b6e098dbcda6a6d52252c31ee2e02d8e00 |
30-Apr-2015 |
John Spurlock <jspurlock@google.com> |
am ad61b833: Merge "Fix no vibration during shutdown." * commit 'ad61b8336aa9627a6ae19580bbdc370dc8bd6810': Fix no vibration during shutdown.
|
0b4daca9ba54b7252ea8c159218391380eb00c8a |
27-Apr-2015 |
Dianne Hackborn <hackbod@google.com> |
Implement user-settable power save whitelist. The whitelist is now maintained by DeviceIdleController, which is moving out into its own independent system service. Network stats now queries it for the whitelist, instead of collecting that itself. Also did a few improvements in alarm manager -- made the code for moving alarms out of the pending list more robust, and fixed the debug output to always print the contents of the pending list even if we aren't in a pending state. (That would have helped me identify the problem much earlier.) Change-Id: I0f7119d4c553c3af4d77b2f71246fa6e2c13c561
eviceIdleController.java
|
a576b4d3be8687f0a65fc5777424955d551604e4 |
24-Apr-2015 |
Jeff Brown <jeffbrown@google.com> |
Add code to collect data about auto-brightness adjustments. Write samples of the old and new state to the binary event log whenever the user modifies the auto-brightness adjustment. We wait a few seconds before logging to ensure that the user is satisfied with the adjustment. Bug: 19786916 Change-Id: I41402decd1034d0839aa0f47495bc00907ab9c08
owerManagerService.java
|
f70faed503c8482266e6acb94dd5281488a9117e |
21-Apr-2015 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #20401752: device idle and alarms. Main change is to fix problems in the alarm manager where it was not doing a good job at scheduling the device idle wakeup before an alarm. To fix this, we now keep explicit track of the next "wake from idle" alarm so we can consistently use that to adjust the time of the device idle alarm if needed. Also a bunch of debugging stuff to help further diagnose this problem: - Alarm summary now includes the last time the alarm went off. - Improved dumpsys output of alarms. - New event log tags for changes related to idle state. Change-Id: Idd2c8d24ae23379f7c75815ddbc6835c2a04656c
eviceIdleController.java
|
4870e9d5eba59fb257a87f97f1adf0b734cf48d3 |
09-Apr-2015 |
Dianne Hackborn <hackbod@google.com> |
More work on device idle mode and other power stuff. Add idle mode support to the alarm manager. Introduce a new concept of flags associated with alarms to tell the alarm manager how to treat the alarm -- they allow everything from the alarm that will bring us out of idle mode, to alarms that are allowed when idle or should also bring us out of idle. The standalone boolean is now also a flag. (Note there is currently no protection from user space setting the flags however it wants; I will be working on that in a follow-up change.) When in idle mode, the alarm manager pushes all alarms that shouldn't execute during that time over to a separate list that is not executed until out of idle. To help with this, I reworked a bit how Alarm objects are managed, so that when rebatching or moving between lists we don't have to allocated new objects but can just use the same existing instance. Also tweaked the sync manager to deal with idle mode, which currently just means doing the same thing as when low on storage -- turning off sync. Add new ACTION_CHARGING and ACTION_DISCHARGING broadcasts that apps can listen for to know when the device is actively charging and discharging. These are better than the old POWER_CONNECTED and POWER_DISCONNECTED ones because we only report charging when we actually see that there is enough power being provided to charge the battery (and will report discharging if there is not enough power). The job controller uses these new actions for scheduling jobs that want to run while plugged in. Removed the "stable charging" stuff while doing so, since the new charging state serves as an even better signal for that. Introduced two new process states: FOREGROUND_SERVICE and TOP_SLEEPING. This will allow us to treat foreground services specially (such as still allowing network access to them for background music playback) while not mixing them together with whatever happens to be the top activity while the device is asleep. Also some other small cleanup here and there. Change-Id: I7a9808b578bad6f50deb8e1baf919298512a0d3a
eviceIdleController.java
|
a223d658306fea5c0a6d30c9850058d5afadb2d1 |
25-Mar-2015 |
Bryce Lee <brycelee@google.com> |
am 3309be5e: am 21b7e6de: am c831b978: Merge "Add isScreenBrightnessBoosted and a broadcast when underlying value changes." into lmp-mr1-modular-dev * commit '3309be5e7bc782d89adaf4abca5f1f81649c655f': Add isScreenBrightnessBoosted and a broadcast when underlying value changes.
|
c831b978238d5ed200ca329c540eff00faba77e3 |
25-Mar-2015 |
Bryce Lee <brycelee@google.com> |
Merge "Add isScreenBrightnessBoosted and a broadcast when underlying value changes." into lmp-mr1-modular-dev
|
88e98dfa59e68a860d8c3b462ec03bc0b06d6b5c |
23-Mar-2015 |
Dianne Hackborn <hackbod@google.com> |
More work on device idle mode. - There is now an API for people to find out about its state. - Moved DeviceIdleController to be closer to the power manager implementation, since they are closely related. - Job scheduler now knows about idle state and doesn't run jobs while the device is idle. - Battery stats now keeps track of "idling" vs "idle mode". Idling is when we consider the device to be idle, independent of whether we are actually in deep idle mode. This allows us to keep track of longer-term changes independently of cycling in and out of idle mode. - Battery stats also now keeps track of package changes in its daily stats. - Small optimization to network policy manager service to not touch uids that do not have the NETWORK permission. Change-Id: I0b3304fb3722c78cdfdd0c1eada7369ece7cbcf9
eviceIdleController.java
owerManagerService.java
|
bff46bac807ae8a9ebdc22c449a8d4f78711b4d2 |
05-Mar-2015 |
Benjamin Franz <bfranz@google.com> |
Add DO policy to disable safe boot mode. Bug: 19615843 Change-Id: I14dbe911995ec216c57bd285d6b7b04c9684591a
hutdownThread.java
|
d3b371755df509cabbc5b4451df83309be5439b0 |
18-Mar-2015 |
riddle_hsu <riddle_hsu@htc.com> |
Fix no vibration during shutdown. In ShutdownThread:rebootOrShutdown, the vibrator is created by "new SystemVibrator()" which will use default constructor of Vibrator. And because system server is not bound application, ActivityThread.currentPackageName will be null. Then the member mPackageName of Vibrator is null. When doing vibration: VibratorService.startVibrationLocked -> mAppOpsService.startOperation -> getOpsLocked (null package will get null op) -> return MODE_ERRORED -> no vibration https://code.google.com/p/android/issues/detail?id=160830 Pass null context in SystemServer.performPendingShutdown because vibrator service is not ready, and from the call sequence, there is no available context to use. Change-Id: I3e0175ba6dc2e1a92787873eda4461fba6e89783
hutdownThread.java
|
84d6c0fbf6e513d68330234503b809751d0e3564 |
17-Mar-2015 |
Bryce Lee <brycelee@google.com> |
Add isScreenBrightnessBoosted and a broadcast when underlying value changes. Bug: 18334219 Change-Id: I20051e97633017711574a063b8061f95c3b616c5
otifier.java
owerManagerService.java
|
9779e128d611f13cdb44d31b0509ff43c62a35f6 |
14-Mar-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Option for going home when going to sleep for devices without physical button. Bug: 19623388 Change-Id: Iec16f83c64646ded12ec97d4b540510b7f9dfd47
owerManagerService.java
|
c2932a1be3e320679034212698aff376d5104dbe |
21-Nov-2014 |
Jeff Brown <jeffbrown@google.com> |
Hold a wake lock while dozing when display updates are pending. When the display state is DOZE or DOZE_SUSPEND, assume this means that the AP may go to sleep at any time so hold a wake lock for a little while starting when traversals are scheduled to ensure that the AP remains awake long enough to draw and post the frame to the display hardware. This patch is somewhat approximate but should be good enough for most devices today. Note that the implementation uses the window manager to ensure that the window which wants to draw is actually visible before acquiring the wake lock. There is a cost to this test (a round-trip) which should not be significant today since we do not expect apps to draw more than one frame or two while dozing. However, if we wanted to support animations in general, we might want to optimize it or eliminate the check altogether (since we can already account for the app's use of the wake lock). Another way to implement this functionality might be for the view hierarchy to listen for the power manager to report that it has entered a non-interactive power state before deciding to poke draw locks. This would be somewhat more accurate than watching the display state. Also, the draw lock timeout logic could be implemented more directly instead of using an ordinary timed wake lock. Bug: 18284212 Change-Id: I84b341c678303e8b7481bd1620e634fe82cc4350
owerManagerService.java
|
01c06dfb076b71cb72c4bff9175bec9d59d2efde |
17-Dec-2014 |
Michael Runge <mrunge@google.com> |
Increase timeout when uncrypting OTA Larger OTAs (750 MB tested) are taking 3-4 minutes to write, due to the O_SYNC needed to ensure that the data is actually committed to disk prior to reboot. Bug: 18750317 Change-Id: Idfab3ffd0276df4548f69a09c72ad6f4a344b6e6
owerManagerService.java
|
9ef94019386183cb88ad090965418ef294bbb79a |
21-Nov-2014 |
Jeff Brown <jeffbrown@google.com> |
resolved conflicts for merge of 694c1d2b to lmp-mr1-dev Change-Id: I9a9b724e0fd12aa161ff276540431b9d8e218e2b
|
fbe96706bb9754f9ea3f6345f32e058a45ad10b4 |
20-Nov-2014 |
Jeff Brown <jeffbrown@google.com> |
Support keeping activities resumed while dozing. If the lock screen is not shown, then let activities keep running while dozing. This is important to support ambient mode on watches since it allows the home app to keep running. To make this possible, we need to inform the activity manager about the exact wakefulness state, not just the overall boolean interactive state. Bug: 18284212 Change-Id: Ia35c99127ce51ffc178f3a2f51fca67d24061c71
otifier.java
owerManagerService.java
|
cb906677fc65fd1b43f6dc3b8e029711ec8e86dc |
13-Nov-2014 |
Jeff Brown <jeffbrown@google.com> |
am 24c1d664: Merge "Remove an unnecessary condition from previous change." into lmp-sprout-dev * commit '24c1d664c4f95a8c997bfc4683844e05b788c3db': Remove an unnecessary condition from previous change.
|
72f1e3b9c9992bfc3449c5441bc8e50e7b05f083 |
13-Nov-2014 |
Jeff Brown <jeffbrown@google.com> |
am 1cbff0e3: Merge "Improve screen brightness boost behavior." into lmp-sprout-dev * commit '1cbff0e310b0fba6b25ca1c1e14eaefeabdee0d9': Improve screen brightness boost behavior.
|
a191aa99ab67d05bc72e5e20f854bbdd1ea474c1 |
13-Nov-2014 |
Jeff Brown <jeffbrown@google.com> |
Remove an unnecessary condition from previous change. Change-Id: Ib966fbb373294ad60caf7f1d9cbb7fafd05ded6b
owerManagerService.java
|
7b5be5e2a738859d36e1977cdc756cf83361d72f |
13-Nov-2014 |
Jeff Brown <jeffbrown@google.com> |
Improve screen brightness boost behavior. Wake-up when entering brightness boost mode, don't boost in ambient mode since some display device drivers do strange things in that mode and boost doesn't work. Waking up feels more natural as well. Don't flutter the power HAL's interactive mode bit simply due to changes in display ready state since that may result in visible artifacts such as display flashes. Don't stop the auto-brightness sensor while temporarily boosted. Don't prevent the display from entering the ready state while in brightness boost since that would unnecessarily delay the transition from DOZING to AWAKE until boost is finished. Restart the user activity timeout when brightness boost ends and prevent the display from dimming while boosted. The pixel fairies basked in the sunlight. Bug: 18262044 Bug: 18261782 Change-Id: I8c42a1e6091b0fe1253e90265ac248087ebc24e1
owerManagerService.java
|
5ce1cb240b13db98fbdc21e1ef069b5f9cec8d72 |
07-Nov-2014 |
Jeff Brown <jeffbrown@google.com> |
Move device admin max screen off timeout to internal interface. The setting was previously exposed in IPowerManager but it doesn't need to be there. Bug: 17656076 Change-Id: If3ed0cbe89f67c60aa00376be0c54b1bd9656144
owerManagerService.java
|
e333e674a758c39885d4d9779a1aad387fb0e6aa |
28-Oct-2014 |
Jeff Brown <jeffbrown@google.com> |
Add a function to boost screen brightness temporarily. When PowerManager.boostScreenBrightness() is called, the screen brightness is set to maximum for 5 seconds. This action is also considered to be user activity. Bug: 17934954 Change-Id: I1cb4a03a60705c6c1c5cc9ff84b1c5dbd2932fcd
owerManagerService.java
|
584a44517950204a04ef01345be70b33d8ba43f9 |
22-Oct-2014 |
Bryce Lee <brycelee@google.com> |
[Theater Mode] framework implementation through global setting Bug: 17684570 Change-Id: I64a9c9c0620049cdfcca0150648fa201281f7178
owerManagerService.java
|
c338784bf6bfcce3cd7db40f46b0e6c815e9ed3a |
02-Oct-2014 |
Dianne Hackborn <hackbod@google.com> |
Merge "More work on issue #17656716: Unhandled exception in Window Manager" into lmp-dev
|
8d05172112436a81bed6e4a0810f8914509d8a4d |
01-Oct-2014 |
Dianne Hackborn <hackbod@google.com> |
More work on issue #17656716: Unhandled exception in Window Manager Fix Slog.wtf to not acquire the activity manager lock in its code path, so that it can never deadlock. This was the original intention of it, but part was missed. Now we can put back in the code to detect when strict mode data is getting large (a little more targeted now to the actual problem), and use Slog.wtf to report it. And as a bonus, when this happens we will now clear all of the collected violations, to avoid getting in to the bad case where IPCs start failing. So this should be good enough for L to fix the problem, with wtf reports for us to see if the underlying issue is still happening. Finally, switch a butch of stuff in the system process from Log.wtf to Slog.wtf, since many of those are deadlocks waiting to happen. Oh and fix a crash in the settings provider I noticed in APR. Change-Id: I307d51b7a4db238fd1e5fe2f3f9bf1b9c6f1c041
owerManagerService.java
|
05af6adb8d4fd5ea069c9aead5a877da9085daa8 |
01-Oct-2014 |
Jeff Brown <jeffbrown@google.com> |
Implement auto-sleep functionality. Added a new SLEEP_TIMEOUT setting which governs how long the device will remain awake or dreaming without user activity. By default this value is set to -1 which maintains today's existing behavior. We basically represent the time we are allowed to be dreaming as a new kind of user activity summary state called DREAM, similar to BRIGHT and DIM. When the sleep timeout expires, the state is cleared and the dream ends. Bug: 17665809 Change-Id: I59aa7648dcec215f1285464fc1134934a09230e5
owerManagerService.java
|
3ee549ca2404067bb8b2fcbaa741ec118c76bf3e |
23-Sep-2014 |
Jeff Brown <jeffbrown@google.com> |
Fix window manager policy state when waking from doze. Once upon a time when the world was fresh and new, the heavens had an easy rhythm. Day and night. Night and day. In the day, the pixel fairies would cavort and play in the bright gardens with narry a mark of shadow or gloom. In the night, they would rest peacefully, dreaming no dreams and knowing no fear. Then one night a fairy dreamed the first dream. At first the dream was peaceful, full of colors and delight, hopes and memories. Then all at once, jarringly, it awoke in bright daylight. The pixel fairy knew fear, for the world had changed and it was unprepared. Time passed and the pixel fairies grew accustomed to their fate, day and night, night and day, sometimes dreaming, until there came a night when a fairy did not sleep. It roamed the land in a dreamless doze, lost and afraid amid a grim haze of grey and darkness. The fairy despaired. It wanted no part of this place. It pretended for a time to be awake but the bright daylight would not come. It pretended for a time to be dreaming but the colors and memories would not come. That is when the fairy wished for oblivion. Then just as suddenly, it awoke in the daylight. It fell to the ground, stunned as if it had forgotten how to walk in the too bright daylight. Though the world again grew softer and kinder in time, the pixel fairies were never the same. For the night is dark and full of terrors. --- It used to be easy. Screen on and screen off could explain almost everything about the state of the device but it's different now with ambient display. We need to be able to wait for all windows to be drawn even in the case where the device is still nominally asleep. In truth, the window manager policy which drives a lot of these interactions is a thicket of outdated assumptions. Added a new method to tell the window manager policy when the screen is being turned off so that it can correctly account for changes to the interactive state (wakeUp and goingToSleep) and screen state (screenTurningOn and screenTurnedOff). Now we can independently poke keyguard during interactive state changes and we can apply screen on blocking during screen state changes. Moved the code which manages screen on blocking (which is what ensures the UI has fully drawn before revealing screen contents) from the power manager to the display manager since the display manager is in a better position to accurately track the state of the screen, particularly when the screen is being turned off. Fixed a bunch of synchronization issues. Previously some work had been moved to a handler without considering what might happen if it became reordered relative to other work happening elsewhere. Documented the desired behavior in the code to prevent this from happening again. There's still a bunch of stuff in here that isn't quite right, particularly the assumption that there's only one screen, but it's good enough for now. Hopefully there aren't too many bugs. Bug: 17605802 Change-Id: Ic7319e09948c8a3cda014d7e169c964a3ad86f14
otifier.java
owerManagerService.java
|
36c4db8bd3bd7dad4b6cb8abd9cdc1a627fe3bbc |
19-Sep-2014 |
Jeff Brown <jeffbrown@google.com> |
Decouple turning screen on from waking up in policy. This allows us to ensure windows are fully drawn before unblocking screen on while dozing. Bug: 17516245 Change-Id: Ibe63c212b8db855ce26a34a8169f33764b266ee6
otifier.java
owerManagerService.java
|
8d4e6cb06005a2ce994360340a6191f0690db8f4 |
14-Sep-2014 |
John Spurlock <jspurlock@google.com> |
Saver: PowerManager call to set low power mode. - Add an explicit power manager call to set the low power mode state, instead of trying manage everything around a single setting. - When low-power mode is triggered by falling below the configured threshold, it does not update the setting. - The "is-enabled" api returns setting || below configured trigger. - Move the snooze management into the new api call. - Callers (sysui + settings) updated to use the api instead of the setting. - Handles the case where the level does an unpowered leap out of the low battery level. (Possible if powered in-between while the device is off) Bug:17460535 Change-Id: Ic030504c9cad9868a7137abbe837b170da37852b
owerManagerService.java
|
2175e9c366998ed7bd1a4501b94a02f4f49b932c |
13-Sep-2014 |
Jeff Brown <jeffbrown@google.com> |
Add support for dozing after screen off. On some devices, we want the screen off transition to complete before we start dozing. Added a new config.xml attribute config_dozeAfterScreenOff to configure this behavior. Defer starting dreams until the display is ready. Fixed some minor issues in the system UI doze service when setting the display state. Bug: 16187655 Change-Id: Ib1bc60de5457166f4b4880732db5df989dda67a4
owerManagerService.java
|
1208e2718daeae538dc89c37198092ccb32798a2 |
09-Sep-2014 |
Michael Wright <michaelwr@google.com> |
Change constant to PowerManager.RELEAES_FLAG_WAIT_FOR_NO_PROXIMITY Bug: 17290118 Change-Id: Iae3866bf3f7ac24f756ec4c183e848a79d1f779b
owerManagerService.java
|
6e2f395a86d557d2de4b52dda419a5f3eee00c84 |
09-Sep-2014 |
Craig Mautner <cmautner@google.com> |
Wait for animation complete before completing boot Defer the boot process in ActivityManagerService, WindowManagerService and PowerManagerService until the boot animation has completed. Fixes bug 16309312. Change-Id: Ic5e0d627ca4ded3e211c5d2afece89da40d34642
owerManagerService.java
|
219857b900e2a15464c6254d8d64b68db7d548c0 |
28-Aug-2014 |
Michael Wright <michaelwr@google.com> |
Change constant to PowerManager#FLAG_WAIT_FOR_DISTANT_PROXIMITY Also add docs to PowerManager.WakeLock#release(int) Bug: 17290118 Change-Id: Ibcbc4279efdd0f275808042356e6ff843958e23f
owerManagerService.java
|
0a571123544058578b4ef1558c276a4050519652 |
22-Aug-2014 |
Jeff Brown <jeffbrown@google.com> |
Poke interactive hint from userActivity and add @SystemApi. Previously we only poked the interactive hint for input events that were dispatched through the regular input system. However, when using a car dock in projection mode input events are directly delivered to apps by other system components, bypassing user activity. So now we poke the interactive hint on all user activity. Added an @SystemApi version of userActivity. Added a new signature|system permission called USER_ACTIVITY to allow system apps to poke userActivity. For now it seems prudent to keep DEVICE_POWER signature only. Bug: 17043684 Change-Id: Ia84bd03083065b8938a9853c08901fbf71b2e56b
owerManagerService.java
|
72671fbb2036e13fccb0b8eeb98be606de1819dd |
22-Aug-2014 |
Jeff Brown <jeffbrown@google.com> |
Require DEVICE_POWER permission for DOZE_WAKE_LOCK. This wake lock is only intended to be used internally. Change-Id: I8d109c492605673616cf7f4f31f082a42fb1d912
owerManagerService.java
|
bd7723637b14d1895c043c2257f1cd9560322d4e |
02-Aug-2014 |
Naveen Kalla <nkalla@codeaurora.org> |
Invoke shutdownMobileRadios Telephony APIs from ShutdownThread shutdownMobileRadios API shuts down multiple Radios on MSIM devices and also gracefully shuts down Radios and SIM cards on single SIM and MSIM devices. Use this API instead of the old setRadio APIs. Add RIL_REQUEST_SHUTDOWN to RILConstants. Message is sent to notify RIL that the device is shutting down. Bug: 9773278 Change-Id: I6afa9e810cefc7855f7ae42e51f39cc51fa2aa6e
hutdownThread.java
|
89e4ae2f504b4c55d7823c3f04d4894de0d8e471 |
18-Aug-2014 |
Dianne Hackborn <hackbod@google.com> |
Merge "Work on issue #16629489: Google (Play?) Services eating through battery" into lmp-dev
|
d953c53d3b04d772bb1b62ede1c2011641ca82b5 |
17-Aug-2014 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #16629489: Google (Play?) Services eating through battery There is a bug in how we deal with name overflows combined with resetting the battery stats data. If we do a reset while a wakelock is being actively held that has been put into the overflow bucket, then we can end up reducing the number of known wake locks in the list so when after that it is released we try to release it under its real name rather than the overflow name. This means we need to keep track of which wake locks have been placed in the overflow bucket while they are actively being used, so we can be sure to properly handle it as part of that bucket until it is eventually released. This makes things... somewhat more complicated. So now we have a class to take care of all these details, and also use it for other places where we have the same overflow semantics sync and job stats. Also fix potential deadlock -- BatteryStatsHelper needs to call on to ConnectivityManager to find out of there is telepohny, however we use that class when doing a dump while the battery stats lock is held. To fix this, we check the connectivity state up in the battery stats service before acquiring the lock and propagate that information through to the dump code. Change-Id: Ib452206af5c36f4b0f03cc94d2845d36613d1ba5
owerManagerService.java
|
3edf5272fb2185403dfe64b9722b9fc9b9de80f8 |
15-Aug-2014 |
Jeff Brown <jeffbrown@google.com> |
Add trace tag for power management. Instrumented the basic power manager state transitions, calling into the Power HAL, setting the display power mode, and setting the backlight. Bug: 17004602 Change-Id: I4e362162ddfd7292a7eea8b5d029ce3f6593c4a9
otifier.java
owerManagerService.java
|
3d69256fdf3f2006d312824386a4b68b4c6f79bd |
15-Aug-2014 |
Ruchi Kandoi <kandoiruchi@google.com> |
Revert "PowerManager: Adds a call to reduce refresh rate while device is in BatterySaverMode" This reverts commit d54157e2e92f58e997c4bdb50e026e6a0d0121fd. Bug: 16654179 Change-Id: Id4f22c0a4e23518881ac58ad969c16c4612306a2
owerManagerService.java
|
c12035cd40d01b032013f515cb509e6c8791cf65 |
14-Aug-2014 |
Jeff Brown <jeffbrown@google.com> |
Log who is calling goToSleep(). Change-Id: Ibae61c90ee115735835e878bb3bf79eedaa0ae44
owerManagerService.java
|
6d2a9492e2b19421165f0cd918d9f28595bfb770 |
08-Aug-2014 |
Jeff Brown <jeffbrown@google.com> |
Eliminate power manager latency for boot completed. The power manager disables the power button until boot completed occurs. If there are many pending broadcasts in the queue, it may be possible for BOOT_COMPLETED to be delayed for several seconds after boot. To avoid the delay, introduced a new boot phase which is sent to system services immediately when boot completed happens. Bug: 13398280 Change-Id: I1833d2ffb20305009dd76363b43e534034f1d0a2
owerManagerService.java
|
1bb480a3a4ce2ce63c5d09fa7f5cc38ec160ebf4 |
02-Aug-2014 |
John Spurlock <jspurlock@google.com> |
Battery saver: new policy changes + SystemUI tweaks. - Service policy changes: allow the user to turn off (snooze) saver mode below the auto-trigger level. Plugging in the device always exits saver mode. - Default trigger level is now 0 (never) instead of 15. - SystemUI now also listens to a new POWER_SAVE_MODE_CHANGING, since waiting for _CHANGED can take seconds. - Move shared feature description text into the framework so it can be shared. - Tweak dialog title + action strings. - Remove trigger-level from SystemUI, it no longer needs it. - Add the ability to turn off saver mode directly from the notification. - Migrate saver confirmation dialog to common system UI dialog helper, and add a few convenience methods. - Fix bug where the status bar area would be orange over the keyguard in SHADE_LOCKED mode. Bug:16214395 Change-Id: I3d1ded1eec9e63e7d97469486f6a320e1bebbccd
owerManagerService.java
|
6714e86a545a38d8726e75fcd271947b4259c759 |
24-Jul-2014 |
Craig Mautner <cmautner@google.com> |
Refactor screen blocking logic. Because of the call to turn on the screen introduced in ag/495255 is now made earlier we may not have sent the wakeup broadcast by the time the windows have all drawn. In such a case onScreenOn() did not release the wakelock and the screen stayed off. This change ensures that no matter the timing of onScreenOn() the wakelock will be released but only for the onScreenOn() called in response to the most recent screen on transition. Fixes bug 16404078. Change-Id: Ic1e3e61e16c1fc34d4ec657e0e53ac49a05ca6a4
otifier.java
|
970d4132ea28e748c1010be39450a98bbf7466f3 |
19-Jul-2014 |
Jeff Brown <jeffbrown@google.com> |
Allow dreams to control screen state and brightness. Added setDozeScreenState() and setDozeScreenBrightness() methods to DreamService. The values specified here only take effect once startDozing is called and can be changed while dozing. This required some significant rework of the display power controller but the result seems quite nice and better represents the policy we want to apply. Changed the test dream a little bit to make it flash the screen every minute using the new functions. Bug: 15903322 Change-Id: I83bcc34503f1b87727d2b2b3c0ef08507f9f0808
owerManagerService.java
|
7b41467704f941b11af6aace3e40993afc7f6c6f |
18-Jul-2014 |
John Spurlock <jspurlock@google.com> |
Zen mode filtering should use new usage constants. Refactor stream-based calls to usage-based calls. Bug:15279516 Change-Id: I3f7757d8123c14670e2ad5f8e6aa4e9803efe7ec
hutdownThread.java
|
f6d466895b74d620d646abbec1c8911f3a0ce0bb |
18-Jul-2014 |
Jeff Brown <jeffbrown@google.com> |
Allow dreams to wake up gently. This change adds a new DreamService.wakeUp() method to allow a dream to wake itself up gently and perform a transition before finally finishing. The power manager will ask a dream to wake up gently in most cases but may force it to happen immediately when necessary. If the dream takes too long to finish itself then the dream controller will douse it with water summarily after 5 seconds. Change-Id: Ib0564c5650cd5a454e1acc5aa91fe46995eecfa7
owerManagerService.java
|
0d192a9e279133f80a288d34e50c64a5c91c1a5b |
16-Jul-2014 |
Dianne Hackborn <hackbod@google.com> |
Maybe fix issue #16167054: Wakelock is acquired and released in... ...battery history even though CPU is in suspend There is a race in the power manager between noting a wake lock acquire and ensuring the device is staying awake. Change-Id: I3d76f99d73dca119b09f253f0e31448408c88a3c
owerManagerService.java
|
0fe32ae50bcbf6d2a281bdc407ce56f3d05632c5 |
11-Jul-2014 |
Ruchi Kandoi <kandoiruchi@google.com> |
PowerManager: Adds a call to reduce refresh rate while device is in BatterySaverMode. Adds a binder call to the surface flinger to change the refresh rate while the device is in BatterySaverMode. Change-Id: I9b5fdcc279757ceb4b9917cb0445643b50133a04
owerManagerService.java
|
ddef7e776b35aba0f7b4eb4978e93361b49c145f |
10-Jul-2014 |
Dianne Hackborn <hackbod@google.com> |
Get rid of security exception spam during boot. Change-Id: If7a516e463722280bf597f7dd601e7a0f6e379c8
owerManagerService.java
|
c522d1646ac353aec302252fa53976c1fa46ad3d |
02-Jul-2014 |
Jim Miller <jaggies@google.com> |
Decouple critical policy power update from SCREEN_ON broadcast This attempts to fix a bug where ordered broadcasts like ACTION_SCREEN_ON are substantially delayed by misbehaving receivers. Instead, we immediately send the state to mPolicy so that it can wake/sleep the device without delay. Fixes bug 14313639 Change-Id: I21a191f90e0a19f1ee75c160ecc4e63e8def709e
otifier.java
|
2139276ce8b54aba5faa858ca69ed5f01445c269 |
14-Jun-2014 |
Jeff Brown <jeffbrown@google.com> |
Refactor BatteryService to new pattern. Apply SystemService pattern to BatteryService. Change-Id: I4971b2da8d2aed4d14440fb65863a8b916bab03c
owerManagerService.java
|
2c43c339de5aaf4fef58aa9b5ac3af48609263a8 |
13-Jun-2014 |
Jeff Brown <jeffbrown@google.com> |
Resolve boot time dependencies related to the power manager. This change fixes a bug where native daemons may try to communicate with the power manager before it was fully initialized due to a race between publishing the binder service and completing init(). The solution was to simplify the dependencies related to the power manager. It turns out that most services that were passed in init are not actually needed until systemReady. What remained was a dependency on the activity manager to check permissions for incoming calls. So now we start activity manager first. However, the activity manager also depends on power manager for wakelocks. To break the cycle, we now defer initializing the activity manager's wakelocks until after the power manager has been started. Cleaned up a bunch of boot-time service dependencies so that we can have better confidence that they are correctly maintained. Bug: 13884219 Change-Id: If08e2d7ccd44e7026a72441bb6bd5afd7bb9fffe
owerManagerService.java
|
14272302a8b635bd8e9267c1411d0a7ef11bff45 |
11-Jun-2014 |
Dianne Hackborn <hackbod@google.com> |
Implement control of auto power save mode. Follow the setting for auto power save mode in both battery service and battery UI. Default level is 15 when setting is not set; otherwise it is whatever the setting gives, with 0 meaning auto battery save is off. Change how we define the "turn off warn" level to be an adjustment from the warn level, so we can have a good value for whatever auto setting is set. Fix power manager to never go in to power save mode when plugged in, even if the user has manually turned it on. Add new delete option to settings command, because I needed it for testing. Change-Id: I512b691df84399d50b8e751fd50732c6093ebe85
owerManagerService.java
|
eb94fa7975b1e8742f3b00cec6bd4f9d6b329e3a |
04-Jun-2014 |
Dianne Hackborn <hackbod@google.com> |
Improvements to low power mode. Add new public API for monitoring low power mode. BatteryService now puts device in to low power mode when battery level is low. Window manager now watches low power mode to turn off animations. Modifying the animator scale now gets propagated to all processes. Change-Id: I8fa566994764ddd4e1977631e28381ab9409f8ee
owerManagerService.java
|
d862ebb6036a769cb3be371b396e9e33f89ee365 |
21-May-2014 |
Narayan Kamath <narayan@google.com> |
resolved conflicts for merge of fcc4fed3 to master Change-Id: Icebca982b01debd67a1470c02651ef8936f6e5b0
|
fcc4fed3c16a57ef713a96b7298ed43aaeef2df4 |
21-May-2014 |
Jeff Brown <jeffbrown@google.com> |
am 6fb904bf: Merge "Make power button behavior configurable." into klp-modular-dev * commit '6fb904bfd1f943547d6e5bc6f199ffec2290da01': Make power button behavior configurable.
|
6d8fd27e51d799cf7418b14092b5e806d9792812 |
21-May-2014 |
Jeff Brown <jeffbrown@google.com> |
Make power button behavior configurable. Allow power button to be used to either go to sleep as usual, which may doze, or skip that completely and really go to sleep. May also really go to sleep and go home all at once. Bug: 14406056 Change-Id: Ia19e2551b9c2a72271bb2eddd5c0d1749761e019
owerManagerService.java
|
df3bad37d2e3b52a86b18e0d9c84ede4d5098f92 |
21-May-2014 |
Jeff Brown <jeffbrown@google.com> |
am 8f120dd6: am 0702786d: Merge "Allow display timeouts to be set in config.xml." into klp-modular-dev * commit '8f120dd6d631ac632d3356b81403a53f958021f0': Allow display timeouts to be set in config.xml.
|
8f120dd6d631ac632d3356b81403a53f958021f0 |
21-May-2014 |
Jeff Brown <jeffbrown@google.com> |
am 0702786d: Merge "Allow display timeouts to be set in config.xml." into klp-modular-dev * commit '0702786d81eb9f9bf47c3a0827d3f2824c3f4228': Allow display timeouts to be set in config.xml.
|
27736f5c0ada99bf2a7e007a1dec0ad51f65fa52 |
21-May-2014 |
Jeff Brown <jeffbrown@google.com> |
Allow display timeouts to be set in config.xml. Bug: 13671523 Change-Id: I79fc21999bc62743178d2d22071455a0c11070c9
owerManagerService.java
|
cbefd8dd2befcb768f911a63becc427ec4c13250 |
14-May-2014 |
Dianne Hackborn <hackbod@google.com> |
Battery stats more wake history, power save mode. Add new option for battery stats to record the full wake lock history, and recording the current power save mode. Also add in some additional error constants when generating Binder error exceptions. And fix issue #14974572: Avoid repeating wakeup_reason at the beginning of history Change-Id: I7c1a2ab9569de216634f63d8ad69f1294ef1d235
otifier.java
owerManagerService.java
|
6dee605c834fe4926cc1ae5c584563bdb2b608a1 |
14-May-2014 |
Adrian Roos <roosa@google.com> |
Fix adaptive auto brightness bugs Fix update of the light sensor in AutoBrightnessController. Register observer for Settings.System.SCREEN_AUTO_BRIGHTNESS_ADJ. Change-Id: I5201259c4efc0afa200fea3ad9fe3af2991d8676
owerManagerService.java
|
15aedf5bfceb7267f0c79e0d29e149f193b15b0a |
10-May-2014 |
Ruchi Kandoi <kandoiruchi@google.com> |
PowerManager: Minor Coding style issues. Corrects coding style errors caused by Ibed319e734340dfd5348dbeb8fe20c01b1adaac5 Change-Id: I81eb0a2bcc4fb45804a1f47aef76d94142f6aba7
owerManagerService.java
|
f974cc870635227ae13201480fb2f019d153af22 |
01-May-2014 |
Ruchi Kandoi <kandoiruchi@google.com> |
Display: Brightness: Low power mode scales the brightness to 50 percent. When the device is in low power mode all changes to brightness will be scaled to half of the brightness that would be normally set when not in low power mode. Change-Id: I03be820ef64c1d5631ded35f7dfc2799e807226b Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
owerManagerService.java
|
6422abef786632e53337c6c298ffa64f7ddf4d90 |
07-May-2014 |
Brian Carlstrom <bdc@google.com> |
resolved conflicts for merge of 3bbef521 to master Change-Id: I0bbb7c80f6c4f003779da784475d7acbfb898c94
|
3bbef521d4b07f86010ba0729a36ff8b73bcb0ac |
07-May-2014 |
Brian Carlstrom <bdc@google.com> |
resolved conflicts for merge of f2db00fd to klp-modular-dev-plus-aosp Change-Id: I745164033962f6222832f8f19fa316a2e2634fd0
|
e95c3cd89591ba586aa8a0f7a17660c6fb8770bc |
03-May-2014 |
Jeff Brown <jeffbrown@google.com> |
Plumb display state and interactive information to BatteryStats. Fixes an issue where dozing was treated the same as the screen being fully on. Now dozing is treated the same as the screen being fully off which is slightly better. The decision of how to represent this state is now internal to the battery stats so it can be improved later. Removed noteInputEvent() since it is unused. Bug: 14480844 Change-Id: Iee8cf8dce1a1f91c62678bb6d3d9fe567ad6db42
otifier.java
|
01ee6f6cf7de9fb98fc3a88509b43416caa71040 |
03-May-2014 |
Jeff Brown <jeffbrown@google.com> |
Plumb display state and interactive information to BatteryStats. (DO NOT MERGE) Fixes an issue where dozing was treated the same as the screen being fully on. Now dozing is treated the same as the screen being fully off which is slightly better. The decision of how to represent this state is now internal to the battery stats so it can be improved later. Removed noteInputEvent() since it is unused. Bug: 14480844 Change-Id: Iee8cf8dce1a1f91c62678bb6d3d9fe567ad6db42
otifier.java
|
d83a096f299abd9c7fe5e441ef1bb169c314b575 |
03-May-2014 |
Dianne Hackborn <hackbod@google.com> |
Bump up priority of system receiving BOOT_COMPLETED. Change-Id: I5166f88f11f781914312e867cb653c8ecbefa705
owerManagerService.java
|
fb0448ab4b42c1b390cd75c3660ec0de511b7b3b |
02-May-2014 |
Jeff Brown <jeffbrown@google.com> |
resolved conflicts for merge of 4f8cd188 to master Change-Id: I148cd616cd14d834915978aa2dc3f9e27188dbd3
|
140ffc783c50bbe3b62e817c117a31b93e7f627e |
02-May-2014 |
Jeff Brown <jeffbrown@google.com> |
Clean up some terminology related to interactive state. Change-Id: Ife4445685a5314dea64332a3490fa8dd3ffd89a2
otifier.java
|
62b8a49856cc0822905dcb7a213f082b92fa69e3 |
18-Apr-2014 |
Ruchi Kandoi <kandoiruchi@google.com> |
Adds Content Observer for the Low power mode in developer options. Change-Id: Ibed319e734340dfd5348dbeb8fe20c01b1adaac5 Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
owerManagerService.java
|
4e5c089ef3e62e7f658e71c0be262d09bd3e399b |
11-Apr-2014 |
Jeff Brown <jeffbrown@google.com> |
resolved conflicts for merge of 337e764d to master Change-Id: I8168dbf42b68c2f7b5ccb300e0080dddc627af26
|
037c33eae74bee2774897d969d48947f9abe254f |
09-Apr-2014 |
Jeff Brown <jeffbrown@google.com> |
Plumb display power state through display manager. Declare a new method, Display.getState() to retrieve the actual power state of a display. Improved documentation for Intent.ACTION_SCREEN_ON and Intent.ACTION_SCREEN_OFF to clarify what they really mean in terms of the interactive state of the device. Deprecated PowerManager.isScreenOn() and replaced it with PowerManager.isInteractive() with a more suggestive name and better documentation. Redirect display power state changes to go through the display manager first and only then head over to the power manager for legacy compatibility. Eliminated the bright here and woke here policy flags since they were unused. Simplified the input dispatch policy somewhat. Ensure that screen wake locks are respected up until the point when dozing really begins. Fixed a regression in DreamService where onDreamingStarted might be called before onWindowAttached. Bug: 13133142 Bug: 13472578 Bug: 13929355 Bug: 13760290 Change-Id: Iabef96921dd554ce3768fb18619cefc3230b5fb0
otifier.java
owerManagerService.java
|
a981e3b01ae6af2b67e582f0d1cbb95560d05626 |
09-Apr-2014 |
Narayan Kamath <narayan@google.com> |
resolved conflicts for merge of 7289f3ab to klp-modular-dev-plus-aosp Change-Id: I788ca17503e2fd225e205a76d3e7062f71d58316
|
131206b8a9d07400d7c98aea50cc45c38769448f |
09-Apr-2014 |
Jeff Brown <jeffbrown@google.com> |
Move display power controller to display manager service. This refactoring is in preparation for enabling the display manager to have more control over the blanking state of individual displays. There are no functional changes. Some bits will be cleaned up in a subsequent patch. Bug: 13133142 Change-Id: I159a060088344d8e6fcdf9208a1f242960f7ab90
utomaticBrightnessController.java
isplayBlanker.java
isplayPowerController.java
isplayPowerRequest.java
isplayPowerState.java
lectronBeam.java
otifier.java
owerManagerService.java
ampAnimator.java
|
13014b5fe5967b3c7e232ffaf81581ed178e6df6 |
08-Apr-2014 |
Jeff Brown <jeffbrown@google.com> |
Move certain internal activity manager methods to new class. This is a little bit of refactoring in preparation for changing how the power manager notifies system components about changes in power state. Deleted the startRunning method since it is no longer useful. Bug: 13133142 Change-Id: I7f845c61ecc7ee890154ed0cbd90795de609b7ea
otifier.java
|
ad9ef191f50767d8d5b6f0fbd4b59bb1400dcd25 |
09-Apr-2014 |
Jeff Brown <jeffbrown@google.com> |
Move display power controller to display manager service. (DO NOT MERGE) This refactoring is in preparation for enabling the display manager to have more control over the blanking state of individual displays. There are no functional changes. Some bits will be cleaned up in a subsequent patch. Bug: 13133142 Change-Id: Ib811835e8757449c7899ac61807029baaf998161
isplayBlanker.java
isplayPowerController.java
isplayPowerRequest.java
isplayPowerState.java
lectronBeam.java
otifier.java
owerManagerService.java
ampAnimator.java
|
f20a5eb279035d462e1f5d9895f4eb66cc152215 |
02-Apr-2014 |
Ruchi Kandoi <kandoiruchi@google.com> |
PowerManager: add powerHint method Add powerHint method to IPowerManager for passing power hints from other processes. Change-Id: Ic596ace2ed1796a6da4cddb2163dcc4536115e55
owerManagerService.java
|
ef640cdfb29caf9d0abf4aba020afbc3eb3e0443 |
25-Mar-2014 |
Dianne Hackborn <hackbod@google.com> |
Don't allow -1 uids for wake locks. Change-Id: Ia1b412a166f69247be3b047138349e7b4031bd7d
owerManagerService.java
|
4590e52f3d0558e01322fe4dd55bb612afdfb079 |
24-Mar-2014 |
Dianne Hackborn <hackbod@google.com> |
Battery stats: wake locks, radio active, cleanup. - Improve wake lock work source updates to also update the current history tag, in case the new work source gets recorded in the history. - Fix bug in recording radio active time that was not distributing any time to apps. - No longer hold a wake lock while dispatching data conn active call, since it comes with its own timestamp. - Fix issue where the top app was not being cleared while the screen was off. - Remove obsolete STATS_LAST stats type. - Fix bug that was not clearing the total run time when resetting the stats. Change-Id: Iabe17a9edf34f762374ae09fcffb8a819cf72e30
owerManagerService.java
|
f9e1a0b369740e11ea1ed4f141ffb936fc1a6cdb |
20-Mar-2014 |
John Spurlock <jspurlock@google.com> |
Annotate framework vibrate calls with stream hints. Migrate existing framework usages of Vibrator.vibrate to use the new overload with an explicit stream hint. This prevents them from being blocked by rules targeting the unspecified stream. For calls that pass the existing appops check in VibrateService, pass streamHint down to the input device vibrator so we don't lose the signal, but leave it up to InputManager to decide what to do with it - currently unused. Change-Id: I65c944e4010edea29a412bf57d8d7d3b8098b746
hutdownThread.java
|
e5659baa4f439865658d11d6617773e0849f22a2 |
19-Mar-2014 |
Michael Wright <michaelwr@google.com> |
Use DisplayPowerRequest#wantLightSensorEnabled in ABC. Change-Id: I2cb869a40ed91331a55972d0ea557269733d5204
utomaticBrightnessController.java
|
08fc3a7fc24cf16c15f53bab3d061a8c32367655 |
13-Mar-2014 |
Dianne Hackborn <hackbod@google.com> |
Merge "Fix some uid issues in battery stats."
|
bbb7472b8e378a46a1e77747265c19d22bd6968c |
13-Mar-2014 |
Dianne Hackborn <hackbod@google.com> |
Fix some uid issues in battery stats. Change-Id: I9f7773568ff12603d51b26d50d758add09bedbb2
otifier.java
|
088a997defe5ac88d10c341af277bceb7c46f479 |
12-Mar-2014 |
Jeff Brown <jeffbrown@google.com> |
am 81cc19cf: am 236e174a: am 0575b185: Merge "Add a temporary hack to report screen on while dozing." into klp-modular-dev * commit '81cc19cf18dff969319c7d1ded4f285394e37aab': Add a temporary hack to report screen on while dozing.
|
141d88916647cada1c90448d5739a927fa508724 |
12-Mar-2014 |
Jeff Brown <jeffbrown@google.com> |
am 578e1938: am 3ce589e5: am 2d8a3908: Fix power manager display wake lock bugs. * commit '578e19381c2329511187083045d3ad5509428730': Fix power manager display wake lock bugs.
|
0575b185c618a79ede771389ed9a78436b5636bd |
12-Mar-2014 |
Jeff Brown <jeffbrown@google.com> |
Merge "Add a temporary hack to report screen on while dozing." into klp-modular-dev
|
2d8a3908d2b0a74ccdecd97e86e7bfda1caa218e |
12-Mar-2014 |
Jeff Brown <jeffbrown@google.com> |
Fix power manager display wake lock bugs. Under certain circumstances, the power manager might continue to hold the display wakelock long after the display had been turned off due to the mDisplayReady flag having an incorrect value. 1. An inverted conditional caused DisplayPowerState to incorrectly signal the screen on ready state. 2. The DisplayPowerController failed to clear the block screen on flag in the case where the screen was turned off before it became unblocked from turning on. This could happen when the display was rapidly turned on-off-on-off. Bug: 13248135 Change-Id: I8faa3034695c83c8cd35613d81acccf40d22128d
isplayPowerController.java
isplayPowerState.java
owerManagerService.java
|
e39ef098963df1c50912cfeb53c01868ad91a48b |
12-Mar-2014 |
Jeff Brown <jeffbrown@google.com> |
Add a temporary hack to report screen on while dozing. The window manager and view hierarchy currently disable all drawing when PowerManager.isScreenOn() returns false so no drawing occurs while dozing. This will be fixed in a future patch to take the display blanking state into account correctly. This patch is a workaround to unblock development in the meantime. Bug: 13133142 Change-Id: I2dc0b422c77285e657d73adca2606aa68264d987
owerManagerService.java
|
e5167ca61e2c5607aad9041b44158581bc61b4d8 |
08-Mar-2014 |
Dianne Hackborn <hackbod@google.com> |
Reduce wake lock noise in battery history. When the work source of a wake lock was changed, this would cause the old wake lock to be released in battery stats before the new one was acquired (the power manager would correctly keep holding the associated wake lock). This resulted in a pointless entry in the battery history showing the last wake lock being released and a new one acquired. This change adds a new path in to battery stats to report when a wake lock has changed, allowing it to acquire the new wake locks first before the old ones, so it can't drop down to zero wake locks. This also provides better timing information, as the same current time can be used for both operations. In addition, added a new kind of history entry for the current time, so you can tell when in actual world clock time the battery data is happening. Change-Id: Ibbf2eed83bb93f31f60267889b7bc5b9e71e355f
otifier.java
owerManagerService.java
|
ddb90b65f7a4bc2c7b0d1af01af00bd0358ed361 |
28-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
am 098bed6f: am bb689496: am 4c7e6900: Make meaning of PowerManager.isScreenOn() more consistent. * commit '098bed6f27b05c16ecc30f9d39005e5995f14263': Make meaning of PowerManager.isScreenOn() more consistent.
|
4c7e6900c8bfd57652fc1ceca724208ca7556196 |
28-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
Make meaning of PowerManager.isScreenOn() more consistent. The power manager sends SCREEN_ON and SCREEN_OFF broadcasts purely based on the current wakefulness state. In particular, when the system is awake, we consider the screen to be on even if the screen may actually be off due to the proximity sensor or some other condition. Likewise when the system is dozing or asleep, we consider the screen to be off although technically it may still be on and dozing. This behavior is maintained for compatibility with applications that interpret screen on / off as an indicator of user presence. As it happened, the value of PowerManager.isScreenOn() did not always match the state indicated by the broadcasts under certain situations. Instead, it was based on the desired screen state. These states used to be closely correlated but the addition of doze mode causes them to diverge in meaning. One consequence is that wake events from input devices might not always wake the device from sleep unless the display's power state was actually DOZING or OFF even if the power manager's wakefulness was already DOZING or ASLEEP. This is now fixed. Change-Id: Ie819c6d2c5a9ffaaf3101c5dee93ff72e9bc9f30
owerManagerService.java
|
a1f1a3c573acd91024fda0ceb3b921c73b186963 |
25-Feb-2014 |
Dianne Hackborn <hackbod@google.com> |
More battery stats. - Add events for sync. - Add more descriptive tags for wake events. - Fix battery reset. - Fix tracking of wifi data. Change-Id: Ic07f2a86a5ed33e7da57eb1108c31c777ecd801f
otifier.java
owerManagerService.java
|
eb1d804246f031889619e9c5466e899f95c249d0 |
25-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
am 01d63a35: am ae8106ef: am 2326acb5: Merge "Fix typo that causes dreaming on battery." into klp-modular-dev * commit '01d63a35245ad20cf5251b69777db5c81fc76a84': Fix typo that causes dreaming on battery.
|
966604f1599886989c954b9246f157bb47f4a4f8 |
25-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
Fix typo that causes dreaming on battery. Bug: 13173012 Change-Id: I611970a5b4c4b0072ce52e3fc6a57dd3a0c075b3
owerManagerService.java
|
d429710f8edf6aeacb79c2f8ae8a6dc404173c42 |
21-Feb-2014 |
Michael Wright <michaelwr@google.com> |
Merge "Unbreak manual brightness setting."
|
10102e4c0e501333a12b38a5cfe709d1558d84dd |
21-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
resolved conflicts for merge of baaa080b to master Change-Id: I3ee12321e298f7a2ea577a99f30c49f3bb497fae
|
5c977ea1b78046e54f9975c78290316fcc2d630a |
19-Feb-2014 |
Michael Wright <michaelwr@google.com> |
Unbreak manual brightness setting. Change-Id: I0ba5b82f60eacd66db0dcf4166e9a919ee06f2e0
isplayPowerController.java
|
2687550272ba061448f5d5b914700dc335299ee7 |
31-Jan-2014 |
Jeff Brown <jeffbrown@google.com> |
Add a new "doze mode" based on Dream components. When a doze component has been specified in a config.xml resource overlay, the power manager will try to start a preconfigured dream whenever it would have otherwise gone to sleep and turned the screen off. The dream should render whatever it intends to show then call startDozing() to tell the power manager to put the display into a low power "doze" state and allow the application processor to be suspended. The dream may wake up periodically using the alarm manager or other features to update the contents of the display. Added several new config.xml resources related to dreams and dozing. In particular for dozing there are two new resources that pertain to decoupling auto-suspend mode and interactive mode from the display state. This is a requirement to enable the application processor and other components to be suspended while dozing. Most devices do not support these features today. Consolidated the power manager's NAPPING and DREAMING states into one to simplify the logic. The NAPPING state was mostly superfluous and simply indicated that the power manager should attempt to start a new dream. This state is now tracked in the mSandmanSummoned field. Added a new DOZING state which is analoguous to DREAMING. The normal state transition is now: AWAKE -> DREAMING -> DOZING -> ASLEEP. The PowerManager.goToSleep() method now enters the DOZING state instead of immediately going to sleep. While in the doze state, the screen remains on. However, we actually tell the rest of the system that the screen is off. This is somewhat unfortunate but much of the system makes inappropriate assumptions about what it means for the screen to be on or off. In particular, screen on is usually taken to indicate an interactive state where the user is present but that's not at all true for dozing (and is only sometimes true while dreaming). We will probably need to add some more precise externally visible states at some point. The DozeHardware interface encapsulates a generic microcontroller interface to allow a doze dream for off-loading rendering or other functions while dozing. If the device possesses an MCU HAL for dozing then it is exposed to the DreamService here. Removed a number of catch blocks in DreamService that caught Throwable and attempted to cause the dream to finish itself. We actually just want to let the process crash. Cleanup will happen automatically if needed. Catching these exceptions results in mysterious undefined behavior and broken dreams. Bug: 12494706 Change-Id: Ie78336b37dde7250d1ce65b3d367879e3bfb2b8b
isplayPowerController.java
isplayPowerRequest.java
owerManagerService.java
|
88aaef71289177644f723d3d0f20f34a6f9b3d2c |
14-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
am ce0552f3: am 8a4c2bb1: am 567f7ca4: Refactor dream manager to new pattern. * commit 'ce0552f360d8c8f0bc45095293be369800ce9c93': Refactor dream manager to new pattern.
|
567f7ca424280ae957b04d4f3df690055f2d41df |
31-Jan-2014 |
Jeff Brown <jeffbrown@google.com> |
Refactor dream manager to new pattern. Change-Id: I99ab4bd98d56a290368dc4b24e5bb24e0656b522
owerManagerService.java
|
639c8becc6d0efe9c205f3abf1e9347464a95020 |
18-Jan-2014 |
Michael Wright <michaelwr@google.com> |
Extract automatic brightness strategy Pull the strategy for determining the automatic brightness levels into its own class. This cleans up DisplayPowerController a bit and lets us experiment with different automatic brightness strategies more easily. Change-Id: I8f4249da511e38f63260dbef81f97f5507aac948
utomaticBrightnessController.java
isplayPowerController.java
isplayPowerRequest.java
|
41a5cdf9862d4fa77153656e677567e707aa1d45 |
14-Nov-2013 |
Michael Wright <michaelwr@google.com> |
New ambient light level filtering for automatic brightness This new filtering method maintains a ring buffer of all light sensor measurements within the last ten seconds. Once all of the measurements are either above the brightening threshold or below the darkening threshold, adjust the screen brightness to the average of the recorded measurements. Change-Id: I012bd99f86149e02f03b05f19722aef9a07aba31
isplayPowerController.java
|
cab8617b8ccea3a99b1ee15e15915c512a10c738 |
11-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
am 25df673b: am 1b51c9cb: Merge "Make SystemService constructor take a Context." into klp-modular-dev * commit '25df673b849de374cf1de40250dfd8a48b7ac28b': Make SystemService constructor take a Context.
|
b880d880c6cd989eacc28c365fc9a41d31900da1 |
11-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
Make SystemService constructor take a Context. This change simplifies the process of initializing a SystemService by folding the onCreate() step back into the constructor. It removes some ambuiguity about what work should happen in the constructor and should make it possible for services to retain most of their final fields after refactoring into the new pattern. Change-Id: I25f41af0321bc01898658ab44b369f9c5d16800b
owerManagerService.java
|
3d658bf20e2d56e36941e7407deebeec1276fbcf |
05-Feb-2014 |
Dianne Hackborn <hackbod@google.com> |
Improve logging of first wake lock, history size. We now try to have a better label for the first wake lock that is acquired in the log. This is done in two ways: - The alarm manager now sorts the alarms it is going to execute so that wakeup alarms are first, which are more important w.r.t. which one should be logged. - There is a new power manager facility to make a wake lock as "unimportant for logging," which just means in battery stats that a wake lock acquired after that can be considered the actual one to log. This is only used by the alarm manager to mark its TIME_TICK alarms as unimportant for logging. Also reworked the battery history code to be cleaner and a bit smaller. There is no longer a separate EVENT command, instead the event code and tag are just another thing that can be included in an UPDATE command. The bits used in the first history int are also re-arrange, so that only the ones that really change a fair amount in the state bits are up at the top and there is no longer space used for the command code (since now it is always just UPDATE). This allows us to have more room for the time delta at the bottom, to better avoid situations where we need to write an int delta. Change-Id: I1bb860ae5b558a248800b090b03a84fbf7acd68a
isplayPowerController.java
otifier.java
|
509cc13b705f8c488774e7097ab17471c3dacd2e |
18-Jan-2014 |
Jeff Brown <jeffbrown@google.com> |
am e2c9cd58: Merge "Refactor display manager service to new pattern." into klp-modular-dev * commit 'e2c9cd583f4f706b48270b8cbe84df627c69af24': Refactor display manager service to new pattern.
|
4ccb823a9f62e57f9d221f83a97e82967e79a9e5 |
17-Jan-2014 |
Jeff Brown <jeffbrown@google.com> |
Refactor display manager service to new pattern. Transform DisplayManagerService into a SystemService and start cleaning up other local services that it uses from window manager and input manager. Clean up service thread initialization. Remove unnecessary static variables from ActivityManagerService. It's starting to become clear that we really need a better way to manage service dependencies. Boot phases don't quite cut it. Change-Id: If319dbd7cbfbd4812fe55ece969e818d4b20755b
isplayPowerController.java
lectronBeam.java
owerManagerService.java
|
3b0218b0ae1fad67f539ff3c10d6d2f3abec1a11 |
14-Jan-2014 |
Doug Zongker <dougz@android.com> |
boot into recovery via the pre-recovery service Change PowerManagerService to start the pre-recovery service rather than rebooting directly, when requested to reboot into recovery. Add a new RECOVERY permission which a caller needs (in addition to REBOOT) in order to go to recovery. Bug: 12188746 Change-Id: I39121b701c4724558fe751adfbad79f8567faa43
owerManagerService.java
|
6f357d3284a833cc50a990e14b39f389b8972254 |
16-Jan-2014 |
Jeff Brown <jeffbrown@google.com> |
Start untangling system server early bootstrapping. Refactored SystemServer to get rid of a bunch of legacy cruft related to how the ServerThread used to be started up. Create system context first when system server starts. This removes the tangled initialization order dependency that forced us to start the activity manager service before most anything else. Moved factory test related constants into the FactoryTest class. Partially migrated Installer, ActivityManagerService, and PowerManagerService to the new SystemService pattern. There's more work to be done here, particularly around the lifecycle of the power manager. Bug: 12172368 Change-Id: Ia527dd56e3b3fd90f9eeb41289dbe044921230d4
owerManagerService.java
|
02cc684e42b13454ba1a013340b41696323a4c2a |
16-Jan-2014 |
Jeff Brown <jeffbrown@google.com> |
Delete unused power manager functionality. timeSinceScreenWasLastOn() was used by Watchdog previously but is no longer so we can remove it. Change-Id: I91c324b6c98c1aeb85f64b0296a41240e6c2ef4f
owerManagerService.java
|
9158825f9c41869689d6b1786d7c7aa8bdd524ce |
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories Refactored the directory structure so that services can be optionally excluded. This is step 1. Will be followed by another change that makes it possible to remove services from the build. Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
isplayBlanker.java
isplayPowerController.java
isplayPowerRequest.java
isplayPowerState.java
lectronBeam.java
otifier.java
owerManagerService.java
ampAnimator.java
creenOnBlocker.java
hutdownThread.java
uspendBlocker.java
irelessChargerDetector.java
|