fe74fb95b91a5d58a8d2d238c525e2f1891ca0c7 |
14-Sep-2015 |
Guang Zhu <guangzhu@google.com> |
extend svc command to control NFC state Change-Id: I599e4000fa17384089410e63b3150f25aa9458f7
ndroid/commands/svc/NfcCommand.java
ndroid/commands/svc/Svc.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
ndroid/commands/svc/PowerCommand.java
|
fcf10f7c12cb3107bdfedce6f76a8c866d154f3c |
13-May-2015 |
Nick Kralevich <nnk@google.com> |
Modify how USB connections are handled. * Introduce a new "charger only" mode. In this mode, MTP is disabled, and no file transfers can occur. * Make charger only mode the default. * Modify "persist.sys.usb.config" so it now only holds the adb status. * Make the USB settings non-persistent. Unplugging the USB connection will reset the device back to "charger only" mode. * Fixup wording per UI guidelines. TODO: Re-implement MDM restrictions for USB / MTP access controls. Bug: 18905620 Change-Id: I99a50d9132a81e98187f431166fd9fef4d437e4f
ndroid/commands/svc/UsbCommand.java
|
08c7116ab9cd04ad6dd3c04aa1017237e7f409ac |
28-Feb-2015 |
John Spurlock <jspurlock@google.com> |
Remove unused imports in frameworks/base. Change-Id: I031443de83f93eb57a98863001826671b18f3b17
ndroid/commands/svc/DataCommand.java
ndroid/commands/svc/WifiCommand.java
|
7b81602f3c18df8a4ca0342c514af8f7e394c0d7 |
19-Apr-2014 |
Robert Greenwalt <rgreenwalt@google.com> |
Enabling internal msg apis NetworkFactory and NetworkAgent. First trying with wifi and getting rid of WifiStateTracker. Conflicts: api/current.txt services/core/java/com/android/server/ConnectivityService.java Change-Id: I7f0ec13d7d8988b32f3c6dc71f72012f3349fe02
ndroid/commands/svc/DataCommand.java
ndroid/commands/svc/WifiCommand.java
|
62aad7f66fcd673831029eb96dd49c95f76b17bd |
14-Mar-2013 |
Guang Zhu <guangzhu@google.com> |
add reboot and shutdown to `svc power` command a runtime shutdown will be performed first, then device will reboot with the provided reason or power off. Change-Id: I44cfbae19626c46147fad3bc8e91434970daa5d5
ndroid/commands/svc/PowerCommand.java
|
783f9e6615db5c90c184397cf1ee271e302c398b |
09-Sep-2012 |
Guang Zhu <guangzhu@google.com> |
Use correct PowerManager call to wake up screen The current implementation does not actually wakes up the screen. Change-Id: Ief2dca013cfe40e03b64273fe7b09822e9ad42a7
ndroid/commands/svc/PowerCommand.java
|
37a37f445cbcd64376af153dd79ea2a123d9405d |
15-Aug-2012 |
Brian Muramatsu <btmura@google.com> |
add wireless charger support bug: 6879638 - add new enum value BATTERY_PLUGGED_WIRELESS - check for sys online file with contents "Wireless" Change-Id: I22dc3c40f50573c98643e7b5cbcb237d0216530d
ndroid/commands/svc/PowerCommand.java
|
9630704ed3b265f008a8f64ec60a33cf9dcd3345 |
28-Jul-2012 |
Jeff Brown <jeffbrown@google.com> |
Power manager rewrite. The major goal of this rewrite is to make it easier to implement power management policies correctly. According, the new implementation primarily uses state-based rather than event-based triggers for applying changes to the current power state. For example, when an application requests that the proximity sensor be used to manage the screen state (by way of a wake lock), the power manager makes note of the fact that the set of wake locks changed. Then it executes a common update function that recalculates the entire state, first looking at wake locks, then considering user activity, and eventually determining whether the screen should be turned on or off. At this point it may make a request to a component called the DisplayPowerController to asynchronously update the display's powe state. Likewise, DisplayPowerController makes note of the updated power request and schedules its own update function to figure out what needs to be changed. The big benefit of this approach is that it's easy to mutate multiple properties of the power state simultaneously then apply their joint effects together all at once. Transitions between states are detected and resolved by the update in a consistent manner. The new power manager service has is implemented as a set of loosely coupled components. For the most part, information only flows one way through these components (by issuing a request to that component) although some components support sending a message back to indicate when the work has been completed. For example, the DisplayPowerController posts a callback runnable asynchronously to tell the PowerManagerService when the display is ready. An important feature of this approach is that each component neatly encapsulates its state and maintains its own invariants. Moreover, we do not need to worry about deadlocks or awkward mutual exclusion semantics because most of the requests are asynchronous. The benefits of this design are especially apparent in the implementation of the screen on / off and brightness control animations which are able to take advantage of framework features like properties, ObjectAnimator and Choreographer. The screen on / off animation is now the responsibility of the power manager (instead of surface flinger). This change makes it much easier to ensure that the animation is properly coordinated with other power state changes and eliminates the cause of race conditions in the older implementation. The because of the userActivity() function has been changed so that it never wakes the device from sleep. This change removes ambiguity around forcing or disabling user activity for various purposes. To wake the device, use wakeUp(). To put it to sleep, use goToSleep(). Simple. The power manager service interface and API has been significantly simplified and consolidated. Also fixed some inconsistencies related to how the minimum and maximum screen brightness setting was presented in brightness control widgets and enforced behind the scenes. At present the following features are implemented: - Wake locks. - User activity. - Wake up / go to sleep. - Power state broadcasts. - Battery stats and event log notifications. - Dreams. - Proximity screen off. - Animated screen on / off transitions. - Auto-dimming. - Auto-brightness control for the screen backlight with different timeouts for ramping up versus ramping down. - Auto-on when plugged or unplugged. - Stay on when plugged. - Device administration maximum user activity timeout. - Application controlled brightness via window manager. The following features are not yet implemented: - Reduced user activity timeout for the key guard. - Reduced user activity timeout for the phone application. - Coordinating screen on barriers with the window manager. - Preventing auto-rotation during power state changes. - Auto-brightness adjustment setting (feature was disabled in previous version of the power manager service pending an improved UI design so leaving it out for now). - Interpolated brightness control (a proposed new scheme for more compactly specifying auto-brightness levels in config.xml). - Button / keyboard backlight control. - Change window manager to associated WorkSource with KEEP_SCREEN_ON_FLAG wake lock instead of talking directly to the battery stats service. - Optionally support animating screen brightness when turning on/off instead of playing electron beam animation (config_animateScreenLights). Change-Id: I1d7a52e98f0449f76d70bf421f6a7f245957d1d7
ndroid/commands/svc/PowerCommand.java
|
f0e3edc0709dc190190e0ca386478f4a0da92e7a |
01-May-2012 |
Guang Zhu <guangzhu@google.com> |
remove extra semi colon Eclipse has been complaining about it... Change-Id: I39fb4eeab26af883dd2287baf49ec244db453365
ndroid/commands/svc/UsbCommand.java
|
59d3d868112f8bbd14f466d0096789548b176d34 |
27-Apr-2012 |
Robert Greenwalt <rgreenwalt@google.com> |
Add Usb control to svc. We used to have control over usb via ndc but recent changes removed that. The reverse_tether.sh script needs control (on rooted devices) to run so added this. bug:4208971 Change-Id: I722fc0e14540890be0d79a0b7d22f23b2d57f20c
ndroid/commands/svc/Svc.java
ndroid/commands/svc/UsbCommand.java
|
7e9f4eb2608148436cef36c9969bf8a599b39e72 |
11-Sep-2010 |
Dianne Hackborn <hackbod@google.com> |
Track client requests through location manager. This fixes a problem where applications could ask the location manager to do very heavy-weight things (like... say... update location every minute), which would get accounted against the system instead of the application because ultimately it is the system making the heavy calls (wake locks, etc). To solve this, we introduce a new class WorkSource representing the source of some work. Wake locks and Wifi locks allow you to set the source to use (but only if you are system code and thus can get the permission to do so), which is what will be reported to the battery stats until the actual caller. For the initial implementation, the location manager keeps track of all clients requesting periodic updates, and tells its providers about them as a WorkSource param when setting their min update time. The network location provider uses this to set the source on the wake and wifi locks it acquires, when doing work because of the update period. This should also be used elsewhere, such as in the GPS provider, but this is a good start. Change-Id: I2b6ffafad9e90ecf15d7c502e2db675fd52ae3cf
ndroid/commands/svc/PowerCommand.java
|
0e39ea83c5578e0d55e120c91ff7cfeeb0c1cb2f |
18-Nov-2009 |
Mike Lockwood <lockwood@android.com> |
Fixes for proximity sensor behavior: Add optional flag to Wakelock.release() to specify whether we should wait for proximity sensor to go negative before turning on the screen. Clear the "waiting for proximity sensor to go negative" state when the power key is pressed. Part of the fix for b/2243198 (Black screen lockup after ending call) Change-Id: I813fdb7aa4192cd3384a25be9e59d7d4b90da53a Signed-off-by: Mike Lockwood <lockwood@android.com>
ndroid/commands/svc/PowerCommand.java
|
401ad721aded1e3e57ff51b8c2f98578b588ac43 |
14-Aug-2009 |
Guang Zhu <guangzhu@google.com> |
Modify svc power command so it pokes the wake lock when called. This will ensure screen is not asleep if stayon is requested.
ndroid/commands/svc/PowerCommand.java
|
9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
ndroid/commands/svc/DataCommand.java
ndroid/commands/svc/PowerCommand.java
ndroid/commands/svc/Svc.java
ndroid/commands/svc/WifiCommand.java
|
d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
ndroid/commands/svc/DataCommand.java
ndroid/commands/svc/PowerCommand.java
ndroid/commands/svc/Svc.java
ndroid/commands/svc/WifiCommand.java
|
f013e1afd1e68af5e3b868c26a653bbfb39538f8 |
18-Dec-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Code drop from //branches/cupcake/...@124589
ndroid/commands/svc/DataCommand.java
ndroid/commands/svc/PowerCommand.java
ndroid/commands/svc/Svc.java
ndroid/commands/svc/WifiCommand.java
|
54b6cfa9a9e5b861a9930af873580d6dc20f773c |
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
ndroid/commands/svc/PowerCommand.java
ndroid/commands/svc/Svc.java
|