summaryrefslogtreecommitdiffstats
path: root/policy
Commit message (Collapse)AuthorAgeFilesLines
* Handle missing status/nav bar case inside hideybar check.John Spurlock2013-05-091-2/+5
| | | | | | | Don't assume mNavigationBar != null. Bug: 8890313 Change-Id: If2745b32a8502df629199edbf5493fe8d197a7d3
* Navigation hideybar via new system ui opt-in flag.John Spurlock2013-05-082-72/+264
| | | | | | | | | | | | | | | | | | Apps using SYSTEM_UI_FLAG_HIDE_NAVIGATION to hide the nav bar or SYSTEM_UI_FLAG_FULLSCREEN to hide the status bar can now opt into hideybars by also using a new public sysui flag: View.SYSTEM_UI_FLAG_ALLOW_OVERLAY When opting in, apps accept the fact that bars can be overlayed over their content, but gain the ability to use the entire gesture space - something that was not possible before, particularly when hiding the nav bar. Swiping from the nav bar edge of the screen will reveal the new hidey version of the nav bar, if applicable. Bug: 8682181 Change-Id: I6405bee50e6516667ba6b9a62d4f1e43490b5562
* Add new app ops for various interesting audio service things.Dianne Hackborn2013-05-061-1/+2
| | | | | | | | | | | | | Media buttons: note when an application tries to take ownership of the media buttons. Audio focus: note when an application tries to take audio focus. Volume levels: note changes to the volume level of the various streams. Maybe we should also have some ops for muting streams, soloing streams, etc? Change-Id: I79a5d477b0bad4ff61486cdb73ffb1196a674964
* Merge "Hideybar gesture clears flags if SYSTEM_UI_FLAG_FULLSCREEN"John Spurlock2013-04-291-0/+9
|\
| * Hideybar gesture clears flags if SYSTEM_UI_FLAG_FULLSCREENJohn Spurlock2013-04-261-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | If an app uses the system-clearable SYSTEM_UI_FLAG_FULLSCREEN to hide the status bar, swiping from the top of the screen should clear the clearable flags, revealing the system ui, and allowing apps to respond to the change. This differs from the behavior the gesture triggers when an app hides the status bar using the non-clearable WM.LP.FLAG_FULLSCREEN. In this case, we temporarily overlay the transparent auto-hiding bar. Bug: 8682504 Change-Id: Ie5dc885fd13c8d980c136f6babcea181565ef2a2
* | Generic refactoring for clarity.Craig Mautner2013-04-281-49/+47
| | | | | | | | | | | | | | | | - Log.* was being interspersed with Slog.*. - WindowState Rects were being converted to local variables making it harder to find all references to them. Change-Id: I868a32028604d46dbbc15b005a440f0571336293
* | Add keyguard background scrim and protection around keyguard APIsJim Miller2013-04-262-10/+59
|/ | | | | | | | | | | | | | With this change, the system process will put up a scrim in the event keyguard crashes to protect underlying content. It also adds permission checks to prevent unathorized access through the binder APIs. Cleaned up KeyguardTestActivity to build separately. Removed unused resources. Change-Id: I9e370c6bfb7dca68eae9eae304c815fb84a753d2
* Reveal hideybars using system gesture.John Spurlock2013-04-242-24/+180
| | | | | | | | | | Monitor input events using a dedicated input channel created by window manager. This new input event receiver could be used in the future for other system-wide gestures that do not consume events. Change-Id: Ib1be2fee0015332279fcf10f5b669fffd61acdcd
* am b0efef2f: am f535c820: Merge "Restore dock home support for car docks." ↵Daniel Sandler2013-04-191-2/+93
|\ | | | | | | | | | | | | into jb-mr2-dev * commit 'b0efef2f73533c8d434c47d014f66e1171b19277': Restore dock home support for car docks.
| * Merge "Restore dock home support for car docks." into jb-mr2-devDaniel Sandler2013-04-191-2/+93
| |\
| | * Restore dock home support for car docks.Daniel Sandler2013-04-181-2/+93
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While it's still not generally appropriate for the home key to do anything other than take you home, a car is a somewhat different context: because of the user's reduced ability to interact with the device, it's especially useful to temporarily replace the launcher with a car-optimized variant. While it would be ideal for the entire system (particularly the user's everyday Launcher) to dynamically reconfigure their UIs upon entering car mode, it's not the case today, and car home apps are a useful compromise. Quick test: $ adb shell am broadcast \ -a android.intent.action.DOCK_EVENT \ --ei android.intent.extra.DOCK_STATE 2 This reverts commit 7c135205f2f4c192299ad0215276e9e481bccaa5. Bug: 8234767 Change-Id: I17588fff46e7f5e3773d3ad202601a5642943444
* | | am 3b90af23: am ab15e6ab: Merge "Add a config resource to force HDMI ↵Jeff Brown2013-04-171-10/+21
|\ \ \ | |/ / | | | | | | | | | | | | | | | rotation on some devices." into jb-mr2-dev * commit '3b90af234303cb674ed29dc258240e7cef96e943': Add a config resource to force HDMI rotation on some devices.
| * | Merge "Add a config resource to force HDMI rotation on some devices." into ↵Jeff Brown2013-04-181-10/+21
| |\ \ | | | | | | | | | | | | jb-mr2-dev
| | * | Add a config resource to force HDMI rotation on some devices.Jeff Brown2013-04-171-10/+21
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the hardware composer HAL does not provide full support for multiple displays, it may be necessary to force the HDMI rotation when not docked. (When docked, we can use the dock's orientation.) This configuration is not expected to be used on newer devices with the requisite HAL support and may be removed in the future. Bug: 8511721 Change-Id: I1ff50f00ee7fe621aceff94bd938ecf6385c3f38
| * | Merge "Move owner info from Settings.Secure to LockSettings" into jb-mr2-devJim Miller2013-04-171-7/+19
| |\ \ | | |/ | |/|
| | * Move owner info from Settings.Secure to LockSettingsJim Miller2013-04-161-7/+19
| | | | | | | | | | | | | | | | | | Fixes bug 8512972 Change-Id: Ic046aff0332b78489dda08b1e9e71f4c16154f10
* | | Merge "Implement stack splitting and task movement."Craig Mautner2013-04-171-11/+15
|\ \ \
| * | | Implement stack splitting and task movement.Craig Mautner2013-04-151-11/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Split stacks and move tasks between them. Layout the windows according to the new stack split. After layout content rectangles are known split the available area between all stack boxes. Then use those values for future layout. Provide stack contents to ActivityManager. Change-Id: I9746e6185445633810d506be514d0b7b540a7f99
* | | | Hideybars part I - Overlay status bar via an intent.John Spurlock2013-04-161-3/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implement new mode for status bar, allowing it to overlay windows that use WM.LP.FLAG_FULLSCREEN, and introduce transparency. No gesture is implemented yet, for now the auto-hiding status bar can be shown using a debugging intent. android.intent.action.HIDEYBARS The auto-hiding status bar hides 3 seconds after shown, or 3 seconds after last user-interaction with the shade. Change-Id: Ie4bd625b9cbcddea8f818154719c7a6075972f2a
* | | | Translate MR2 status bar fix to master.John Spurlock2013-04-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix is different in master due to recent keyguard refactoring. Bug:8567697 Change-Id: Ie668ef0e3018e3f835166508afd9a72c3c1dda84
* | | | am 4f63f54f: am 5584737f: Merge "FLAG_DISMISS_KEYGUARD should not hide ↵John Spurlock2013-04-161-1/+2
|\ \ \ \ | |/ / / |/| / / | |/ / | | | | | | | | | status bar if secure." into jb-mr2-dev * commit '4f63f54fdea298358fe9c05a5f4cc975769a69af': FLAG_DISMISS_KEYGUARD should not hide status bar if secure.
| * | Merge "FLAG_DISMISS_KEYGUARD should not hide status bar if secure." into ↵John Spurlock2013-04-161-1/+2
| |\ \ | | |/ | |/| | | | jb-mr2-dev
| | * FLAG_DISMISS_KEYGUARD should not hide status bar if secure.John Spurlock2013-04-121-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Otherwise, setting both FLAG_DISMISS_KEYGUARD + FLAG_FULLSCREEN will hide the status bar (by not forcing it) when the secure keyguard is showing. Bug:8567697 Change-Id: I441d9c1bc0e106672b6d29427d291f41eaf1e697
| * | Enabling Face Unlock for user switching (bug 8495282)Brian Colonna2013-04-153-4/+22
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We had been intentionally disabling FUL when switching to a new user. The reason was that we were only getting a signal when the user switch started, not when it completed. If we started FUL at the beginning of the user switch, it could be completed by the time the user switch completed. We now have a signal to tell us that the switch completed. Prior to this change, FUL would start whenever keyguard is created. For a user switch, keyguard is recreated when we get onUserSwitching(), but we don't want FUL to start until we get onUserSwitchComplete(). So with this change, if onResume() happens because of a user switch it doesn't start FUL until we get onUserSwitchComplete(). Change-Id: I1d3da0a32b9b4cf0cfa5c577f1697d2a41ee4fda
* | am d9d9c17d: am 77216642: Merge "Implement #7341342 API request: way to ↵Dianne Hackborn2013-04-111-2/+11
|\ \ | |/ | | | | | | | | | | determine current orientation..." into jb-mr2-dev * commit 'd9d9c17dda9a343b8b5386d1b9233c89ab6f3419': Implement #7341342 API request: way to determine current orientation...
| * Merge "Implement #7341342 API request: way to determine current ↵Dianne Hackborn2013-04-121-2/+11
| |\ | | | | | | | | | orientation..." into jb-mr2-dev
| | * Implement #7341342 API request: way to determine current orientation...Dianne Hackborn2013-04-111-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ...to allow for orientation locking This doesn't add an API to get the current orientation, since that is inherantly racy. Instead there is a new "locked" orientation mode that locks the screen into whatever the current rotation is. While at it, added a few other useful orientation modes. Change-Id: I5c369e6511cb72294e9e922ea8acffd770df9440
| * | Merge "Fix bug where transport shows all the time in keyguard" into jb-mr2-devJim Miller2013-04-113-21/+58
| |\ \
| | * | Fix bug where transport shows all the time in keyguardJim Miller2013-04-093-21/+58
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a bug caused by not keeping track of previous play state properly in keyguard as well as showing the transport even when in STATE_INVISIBLE. Fixes bug 8473575 Change-Id: I28bd382c53645a7c44541b3139c0a60569865219
| * | Fix missing clock in keyguardJim Miller2013-04-102-3/+10
| |/ | | | | | | | | | | | | | | | | | | This fixes a bug where the clock sometimes doesn't show due to the alpha values not being reset when the widget page order changes due to removing a widget. Fixes bug 8545025. Change-Id: I17c531af4c844647b3262fcf56faa84fff8bafc5
* | Fix shortcut keys to operate as current userMichael Wright2013-04-101-5/+5
| | | | | | | | Change-Id: I967b52604b7faee0d5f341dbbe51b2a4734f4d91
* | am fc9b371e: am 04c83357: Merge "Awaken dreams on home + recents." into ↵John Spurlock2013-04-081-1/+20
|\ \ | |/ | | | | | | | | | | jb-mr2-dev * commit 'fc9b371e90545c9be46730a9d3ab555edfa7da39': Awaken dreams on home + recents.
| * Awaken dreams on home + recents.John Spurlock2013-04-081-1/+20
| | | | | | | | | | | | | | | | | | | | Fixes the KEYCODE_HOME case, awakes when home is started for any reason. Also awaken when toggling recents (and not locked). Bug:8557212 Change-Id: I6578ae3971740a03c27596b838d27a5ab9b03752
* | am 2987c218: am 728827ff: Merge "Uphold common ordering expectations around ↵Adam Powell2013-04-041-3/+12
|\ \ | |/ | | | | | | | | | | action bar Home/Up dispatch" into jb-mr2-dev * commit '2987c218e351c76941f09bddb3eb46a572ca6644': Uphold common ordering expectations around action bar Home/Up dispatch
| * Uphold common ordering expectations around action bar Home/Up dispatchAdam Powell2013-04-041-3/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some apps aren't particularly happy if a stray key event is dispatched to a newly created window before its menu is prepared, causing the action bar's Home/Up event to be dispatched. Ignore these clicks on the Home/Up button before the menu goes through its initial prepare step. Note that it is still possible (and valid!) for Home/Up to be dispatched even if the app chose to return false from onCreateOptionsMenu or similar. Bug 7085070 Change-Id: If4b7d5f8c5a08ce8a094f1919347604d78ddedfb
| * Merge "RemoteControlClient receives playback position change requests" into ↵Jean-Michel Trivi2013-04-032-2/+2
| |\ | | | | | | | | | jb-mr2-dev
| | * RemoteControlClient receives playback position change requestsJean-Michel Trivi2013-04-012-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | RemoteControlClient defines two listener interfaces for playback position, one to let the framework query the current playback position, the other to request playback to seek to a given position. Updated IRemoteControlDisplay interface to support passing info about whether the user of RemoteControlClient can provide a playback position, and receive a new one. Updated implementations of IRemoteControlDisplay to new interface. Bug 8120740 Change-Id: I1a5a969da4d0f8c9ad27f691919dd08f8653982b
* | | am 9d4ed1ec: am ddd168d6: Merge "Add global key configuration file" into ↵Justin Koh2013-04-022-0/+141
|\ \ \ | |/ / | | | | | | | | | | | | | | | jb-mr2-dev * commit '9d4ed1ec62a392e4b73ab7d3cd548e09bc792ab2': Add global key configuration file
| * | Merge "Add global key configuration file" into jb-mr2-devJustin Koh2013-04-032-0/+141
| |\ \
| | * | Add global key configuration fileJustin Koh2013-04-022-0/+141
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add global key configuration file. A global key is one that is handled by PhoneWindowManager before dispatching and sent to a given component via broadcast instead of going to the foreground app. Bug: 8510681 Change-Id: Ic6a8e559680d005613ed22874b27eb78bbfc4499
| * | | Change time format for default clock in keyguardJim Miller2013-04-021-1/+1
| |/ / | | | | | | | | | | | | | | | | | | | | | This changes the default clock format from "kk:mm" to "HH:mm" Fixes bug 8447801 Change-Id: I25f0c406dbecba8288773c9d13d0092485274af5
| * | FUL now restarts when flipping tablet 180 (bug 7484464)Brian Colonna2013-03-291-3/+65
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a tablet rotates, FUL must be stopped and restarted in a new position. 90 degree rotations cause a configuration change, causing FUL to be automatically reconstructed in the new location. However, a 180 degree rotation is not a configuration change, so FUL was not restarting. A 180 degree rotation happens more often than one might think. If you set the tablet down and later picked it up in the opposite orientation, FUL would not work prior to this fix. This change adds a rotation watcher to KeyguardFaceUnlockView. It watches for 180 degree rotations and stops and restarts FUL accordingly. The rotation watcher callback must be unregistered when KeyguardFaceUnlockView is recreated (as during 90 degree rotation changes), otherwise the number of rotation watcher callbacks will keep growing and they will never go away. This is a problem not just because there are many callbacks hanging around, but also because the old callbacks end up trying to access biometric unlock views that no longer exist, resulting in crashes. So, a simple function was added to the window manager to unregister a rotation watcher. Change-Id: Ie1ef20a9a22b8f4e39918987dff2b8ad444fcfd1
| * RemoteControlClient can report current position, speedJean-Michel Trivi2013-03-292-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | Extend RemoteControlClient class to support reporting the current playback position, and the playback speed. Define listener for an application to receive new playback position to seek to (use of listener to be implemented). Update IRemoteControlDisplay implementations to new interface. bug 8120740 Change-Id: I2654daeca1ac49713d325df8226dceb85943c020
* | am 0f3a3777: am 94eaab4a: am 3ae30483: am a19647d3: Merge "Correct ↵Elliott Hughes2013-03-281-0/+0
|\ \ | |/ | | | | | | | | | | executable bit for source files [Take 2]" * commit '0f3a3777026c20011f1b419daf12980715e594ff': Correct executable bit for source files [Take 2]
| * am 3ae30483: am a19647d3: Merge "Correct executable bit for source files ↵Elliott Hughes2013-03-281-0/+0
| |\ | | | | | | | | | | | | | | | | | | [Take 2]" * commit '3ae30483777708ff3a4f59a4fa75c6a76213cc30': Correct executable bit for source files [Take 2]
| | * Correct executable bit for source files [Take 2]Chirayu Desai2013-03-271-0/+0
| | | | | | | | | | | | | | | | | | | | | Change Ieb51bafb46c895a21d2e83696f5a901ba752b2c5 left out some files, this fixes them. Change-Id: Ia949a8581668836ea0251602e048f09c852f5169
* | | am 3f1be07f: am 6ceed12a: Merge "Fix an action bar menu order of operations ↵Adam Powell2013-03-271-0/+7
|\ \ \ | |/ / | | | | | | | | | | | | | | | bug" into jb-mr2-dev * commit '3f1be07f0a4183ae5e48a4a33f32ed1af949b7ae': Fix an action bar menu order of operations bug
| * | Fix an action bar menu order of operations bugAdam Powell2013-03-271-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As options menu invalidations in PhoneWindow are deferred, it was possible for a call to open the overflow menu (which involves an extra chance to prepare the menu) to happen before the pending menu invalidation was handled. Process any pending menu invalidations before attempting to show the overflow menu in response to one of these events. Bug 7209308 Change-Id: Id50f7f6ad5d3a631745207fa0bad8c356690e16c
* | | am e4ad1a74: am 7c566bf3: Merge "audio service: add config option for fixed ↵Eric Laurent2013-03-251-3/+7
|\ \ \ | |/ / | | | | | | | | | | | | | | | volume" into jb-mr2-dev * commit 'e4ad1a7420f6ad9b7f3b1d28205ed3d18e2dd04d': audio service: add config option for fixed volume
| * | audio service: add config option for fixed volumeEric Laurent2013-03-211-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a boolean configuration option config_useFixedVolume indicating if stream volumes or master volume can be modified. If the option is true, the AudioManager volume and mute APIs will be no ops and the volumes will be maxed out. To be consistent: - the ringer mode is forced to normal and cannot be modified - volume panel is never displayed - volume settings are not available - ringer mode global action is not displayed. The default for this option if false. This is useful for a class of devices intended for connection to a digital audio output only, where the volume is directly controlled on the audio sink. Bug 8161458 Change-Id: I2571d5ee79952ef0914d8fd1985816467a80adcd