summaryrefslogtreecommitdiffstats
path: root/cmds/wm
Commit message (Collapse)AuthorAgeFilesLines
* Add support for disabling display scaling for development.Jeff Brown2015-04-151-4/+42
| | | | | | | | | | | | | | | | | | | Added two new options to the wm command. 1. Set the screen size based on dips rather than pixels using the current screen density. eg. adb shell wm size 320dpx320dp 2. Disable automatic scaling of the contents of the display. When combined with the previous command, this is useful for seeing how the UI would behave if the screen remained at its current density but changed physical size. eg. adb shell wm scaling off Bug: 19899223 Change-Id: I545f893ba4861494e995cf0457ebeba1050d28dc
* Have audio service clean up new receivers in crashing processes.Dianne Hackborn2013-04-081-92/+22
| | | | | | | | | | | | | | | | | | | | The new media button receiver with only a pending intent (no component name) could be left hanging if the process that registered it went away. These semantically need to be tied to the calling process's lifetime; we now clean them up when the calling process goes away. Also added some additional cleanup of media button receivers when packages change (updated, cleared). And on top of that, a new "media" command for doing media things. Currently lets you send media keys and monitor remote display data. Oh and finally added a new BaseCommand base class for implementing these command line utilities. Change-Id: Iba1d56f10bab1eec4a94a7bb1d1c2ae614c8bcf5
* Change wm commands to return size and density info.Dianne Hackborn2013-03-261-5/+30
| | | | Change-Id: Id25722fe5f0cd9470d04d657f067e5ad29927c98
* Use BUILD_PREBUILT to install the shell scriptYing Wang2013-02-191-19/+6
| | | | | | NOTICE files will be picked up automatically. Change-Id: Ia4938aff013f1c010cbbfceacf5685722c86c39a
* Implement display overscan support.Dianne Hackborn2013-02-195-0/+465
The window manager now keeps track of the overscan of each display, with an API to set it. The overscan impacts how it positions windows in the display. There is a new set of APIs for windows to say they would like to go into the overscan region. There is a call into the window manager to set the overscan region for a display, and it now has a concept of display settings that it stores presistently. Also added a new "wm" command, moving the window manager specific commands from the "am" command to there and adding a new now to set the overscan region. Change-Id: Id2c8092db64fd0a982274fedac7658d82f30f9ff