383db5ebcc3a4a615faf249bf4f126f42e80b82e |
|
22-Jun-2016 |
Tamas Berghammer <tberghammer@google.com> |
Update package names to work with the proto3 compiler Bug: b/28974522 Change-Id: I5f3adf4946ee4ba1e09e4f40afe83c151405972a
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.java
|
ac2561e8206ac42921bb6ddbb0a5972fb360e394 |
|
01-Nov-2016 |
Wale Ogunwale <ogunwale@google.com> |
Make window token add/remove APIs require displayId Window tokens can now only be on one display, so we now require clients that want to add/remove window tokens to specify the display they would like the token to be created on. This simplifies the token handling code in WM and will be useful moving forward for clients that want to add windows to external displays. Test: Existing tests pass Change-Id: I6b2d8d58a913b3624f1a9a7bebbb99315613f103
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.java
|
9ede1d260284bbf0b47ca6f0315e943058624520 |
|
23-Sep-2016 |
Adrian Roos <roosa@google.com> |
Fix wake lock logic during Dream startup Fixes a crash that would happen in all dreams that did not have permission to acquire wake locks. Instead moves the wake lock logic into the system process. Also fixes a bug in DozeService where the wake lock was not held until dozing was actually properly initialized. Fixes: 31612287 Bug: 31044352 Related-CL: I85955a2b7d6bad5171accbc336117a9660b1b198 Test: adb shell settings put secure screensaver_components com.android.dreams.basic/.Colors; adb shell service call dreams 1 Change-Id: Idb3f921ee71b6da6c2ab0c44c332ef91f93ddbc0
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.java
|
7445c0bb86c57172eb88a4e37183634abce2e37b |
|
07-Sep-2016 |
Adrian Roos <roosa@google.com> |
Hold WakeLock while DreamService starts Fixes a bug where DozeService would not properly initialize because the CPU went to sleep before onDreamingStarted completed, causing the pickup gesture to not work. Change-Id: I85955a2b7d6bad5171accbc336117a9660b1b198 Fixes: 31044352
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.java
|
f6e9228b8a97603d3ceb8f0d61e8d87cf19bd21f |
|
27-Jan-2016 |
Chris Wren <cwren@android.com> |
move framework metrics over to new proto Change-Id: Ie46e946dc787350c15c10aa4385a6b7df7e181a8
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.java
|
57dd737443a174379eb638450e4888500d8e4a23 |
|
28-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #21516866: Implement voice interaction in ResolverActivity The main change here is to not allow the dialog to go in to its "focus on the last app the user selected" when running in voice interaction mode, instead just always giving a simple list. This also fixes some problems with cleaning up active commands when an activity finishes and not forcing the current session to go away when the screen is turned off. Also added some debug help, having activity print the state of the voice interactor. Change-Id: Ifebee9c74d78398a730a280bb4970f47789dadf5
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.java
|
9bb290bcc36fe11f96312feb40aaf3323a96ebae |
|
29-Jun-2015 |
Chris Wren <cwren@android.com> |
add more power manager metrics dream start/stop dream duration screen timeout setting Bug: 21893298 Change-Id: I783f72953fc40c0d276a7845daa048e2fe0db78c
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.java
|
d69e4c1460017062e7c36be55801cb434ad19d97 |
|
24-Apr-2015 |
Dianne Hackborn <hackbod@google.com> |
Update use of procstate for services. Now that we have a separate foreground service proc state (above a sleeping top app), update various system services to put their bindings into this state when appropriate. There are two new bind flags for this -- one that just always makes it a foreground service, another that only does it when the device is awake (useful for things like the wallpaper). And with all of that, tweak network policy manager to only include apps that are at least foreground service state when in power save and device idle modes. This will allow us to further reduce the set of apps that have network access (in particular not giving access to the current top app when the screen is off), hopefully leading to even better battery life. Change-Id: I91d85a5c5ed64e856149e9a5d94a634a7925ec7f
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.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
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.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
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.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
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.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
/frameworks/base/services/core/java/com/android/server/dreams/DreamController.java
|