summaryrefslogtreecommitdiffstats
path: root/policy
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Fix colored status bar panning issues" into lmp-mr1-devAdrian Roos2014-11-031-0/+20
|\
| * Fix colored status bar panning issuesAdrian Roos2014-10-291-0/+20
| | | | | | | | | | Bug: 17695293 Change-Id: I6a1267f8dff27e7b78ab312a71648ef16ab9483b
* | Merge "Improve dump of status bar service" into lmp-mr1-devAdrian Roos2014-11-031-2/+3
|\ \
| * | Improve dump of status bar serviceAdrian Roos2014-10-291-2/+3
| |/ | | | | | | | | | | | | | | Tracks which window caused the disable flags instead of just blaming PhoneWindowManager. Bug: 17830264 Change-Id: If6c957120bb2ee8e0083f80e35c71eb21b8672b6
* | am 13f00f07: Implement multi-press behavior for power key.Jeff Brown2014-11-011-162/+348
|\ \ | | | | | | | | | | | | * commit '13f00f07d69f087cf186c23ae6c6fc938e2be561': Implement multi-press behavior for power key.
| * | Implement multi-press behavior for power key.Jeff Brown2014-10-311-162/+348
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added support for brightness boost or setting theater mode from the power key. This behavior is disabled by default and must be enabled for specific products in a config.xml overlay. Because the power key is already so overloaded, refactored the code to split out handling of the similar ENDCALL button and renamed all of the state that has to do with screenshot chord detection to avoid confusion. Bug: 17949215 Change-Id: Id282133188e3781472aabb64fabcee7b98d0c77d
* | | Animate starting windows when keyguard dismissed.Craig Mautner2014-10-311-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Starting windows are displayed prior to their app windows visibility being set. Consequently the WindowToken.hidden boolean for starting windows is still true even when it is shown. The keyguard logic uses the method WindowState.isVisibleNow to determine whether to animate each window. This method incorrectly determined that starting windows were not visible based on WindowToken.hidden and consequently didn't animate in the starting window. This change fixes isVisibleNow() to correctly determine when starting windows are visible and animates them in as part of the keyguard transition. This change also adds keyguard debug. Partially fixes bug 15991916. Change-Id: Iac3e5f3f33876be5801ec619bbe7a1579e648322
* | | Merge "Add setters for window elevation and clipToOutline properties" into ↵Alan Viverette2014-10-291-0/+16
|\ \ \ | | | | | | | | | | | | lmp-mr1-dev
| * | | Add setters for window elevation and clipToOutline propertiesAlan Viverette2014-10-291-0/+16
| | |/ | |/| | | | | | | | | | | | | | | | | | | These are available as XML attributes but were lacking setters. None of the Window properties have getters, so just adding setters here. BUG: 16847753 Change-Id: I9c032903e94b7f12125210bd73c911243612df69
* | | Change boot screen title to "Android is starting" when not upgrading.Jeff Hao2014-10-291-1/+5
|/ / | | | | | | | | Bug: 17565501 Change-Id: Id5741e6e7a40750feee1cd7306e79f7baeec67de
* | Merge "APIs for an accessibility service to put interaction tracking ↵Svetoslav2014-10-231-5/+8
|\ \ | | | | | | | | | overlays." into lmp-mr1-dev
| * | APIs for an accessibility service to put interaction tracking overlays.Svetoslav2014-10-211-5/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An accessibility service may register to observe the interactive windows on the primary display. These windows are the one that has input focus and ones a sighted user can touch. It is sometimes beneficial for an accessibility service to overlay a window to intercept user interaction and based on that introspect and perform an action on the windows that are on the screen. This is problematic as overlaying a full screen window that is touchable prevents the accessibility service to introspect the content under this window. This change adds a special type of window that only an accessibility service can place which does not affect what an accessibility service can "see" on the screen. Hence, even putting such a window full screen the service will be able to interact with the other interactive windows it covers. Change-Id: I053ccc3a5c6360a98dc40bdb172b54dab35d8b31
* | | resolved conflicts for merge of f03ba4f1 to lmp-mr1-devBryce Lee2014-10-221-6/+45
|\ \ \ | | |/ | |/| | | | Change-Id: I9e4cabd2d8a34a348ae888f096c8d3c35226e960
| * | [Theater Mode] framework implementation through global settingBryce Lee2014-10-211-6/+45
| | | | | | | | | | | | | | | Bug: 17684570 Change-Id: I64a9c9c0620049cdfcca0150648fa201281f7178
* | | Fix issue #17789629: PopupWindow overlaps with navigation bar.Wale Ogunwale2014-10-212-4/+9
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Lollipop release introduced a feature that allowed apps to extend under the navigation bar. This also means any popup window that is anchored to the bottom of its parent window will overlap with the navigation bar if the parent window is extending underneath the navigation bar. This change introduces a new window flag (FLAG_LAYOUT_ATTACHED_IN_DECOR) that allows the app to specify if the popup window should be attached to the decor frame of the parent window thereby avoiding an overlap with the screen decorations. By default the flag is set on SDK version LOLLIPOP_MR1 or greater and cleared on lesser SDK versions. Also, replaced flags FLAG_NEEDS_MENU_KEY and PRIVATE_FLAG_NEEDS_MENU_KEY_SET with needsMenuKey state variable to make room for the new FLAG_LAYOUT_ATTACHED_IN_DECOR flag. Bug: 17789629 Change-Id: I2150e0c6ac688c966c0e8f7e54d42fd20285bea6
* | Merge "Retire RecentApplicationsDialog" into lmp-mr1-devAdrian Roos2014-10-202-349/+0
|\ \
| * | Retire RecentApplicationsDialogAdrian Roos2014-10-082-349/+0
| | | | | | | | | | | | | | | Bug: 5162991 Change-Id: I429da977502f33e2091496f3a075b2c507a88e1f
* | | Allow home to be pressed while in incoming call screenYorke Lee2014-10-101-9/+0
| |/ |/| | | | | | | Bug: 10692603 Change-Id: I2c213d553013bdd906f0ce54eba90a57bd7ae34c
* | Merge "Make GlobalKeyManager broadcasts send as foreground" into lmp-sprout-devJustin Koh2014-10-091-0/+1
|\ \
| * | Make GlobalKeyManager broadcasts send as foregroundJustin Koh2014-10-091-0/+1
| | | | | | | | | | | | | | | | | | Should prioritize these since they are due to user interaction. Change-Id: If36d5502dbd53de6102b05fd54caed56e22685da
* | | Implement issue #17906468: Allow search request to fall back to global searchDianne Hackborn2014-10-091-2/+12
|/ / | | | | | | Change-Id: I04834b2a9f1ec4a68c6a3fed14da2f8dd93b3be7
* | Merge "Put in real "code" (aka marketing) name." into lmp-devDianne Hackborn2014-10-081-1/+1
|\ \
| * | Put in real "code" (aka marketing) name.Dianne Hackborn2014-10-071-1/+1
| |/ | | | | | | Change-Id: Idb3976edfae37293ed75cb5b869b4b42d8042bbe
* | Suppress redundant power key presses while turning screen on.Jeff Brown2014-10-071-1/+6
|/ | | | | | | | | | | | | | | Sometimes it can take a long time to turn the screen on. That's not good but what's worse is that the user will often get impatient and press the power button again which effectively cancels the process and makes the screen not come on at all. The user may then conclude that the device ignored the power key press. This change suppresses power key presses while we're already in the process of turning the screen on so that at least the screen comes on eventually, even if it's slower than we would like. Bug: 17753363 Change-Id: I23083873e35a3dcfa5c20b6f870f53c18e465582
* Prevent monkey from triggering bugreportGuang Zhu2014-10-031-0/+6
| | | | Change-Id: Ifa6f06f7dfa63b740352ad7388f33911649afcb0
* Inset the non-overlay contextual action bar without a status guardAdam Powell2014-09-301-5/+5
| | | | | | | | | | When the status guard is not available, (e.g. when the window is not drawing system bars) do not consume the insets when an action mode is active. Bug 17691453 Change-Id: I459622eaf161a96152fb9ac5f60bb9508aa4de89
* Don't forward media keys to the app if the phone session is activeRoboErik2014-09-261-12/+7
| | | | | | | | | This checks if the phone app is currently getting or in a call when a media key event is sent and sends it to the phone session instead of the foreground app if it is. bug:17527302 Change-Id: Ie5d6cf0c897da81d106f2b1a0561b79f4fc35e82
* Merge "Don't start the keyguard until boot is done." into lmp-devDan Sandler2014-09-262-2/+5
|\
| * Don't start the keyguard until boot is done.Jason Monk2014-09-262-2/+5
| | | | | | | | | | | | | | | | | | Create the KeyguardServiceDelegate but don't bind until boot is done. Until the keyguard is bound, the delegate will assume it should be in a secure state. Bug: 17464800 Change-Id: I91650d1e3e3ea993168855bc3444b905aac9aac3
* | Merge "Turn the device on if the camera lens is uncovered." into lmp-devMichael Wright2014-09-261-0/+1
|\ \
| * | Turn the device on if the camera lens is uncovered.Michael Wright2014-09-251-0/+1
| |/ | | | | | | Bug: 17643810 Change-Id: I4747414224c3219bf91c0c83e969530cb20f96e5
* | Merge "Fix "Always apply window insets to action modes"" into lmp-devAlan Viverette2014-09-251-21/+39
|\ \ | |/ |/|
| * Fix "Always apply window insets to action modes"Alan Viverette2014-09-241-21/+39
| | | | | | | | | | BUG: 17628875 Change-Id: I03bf6cfd68d0ca2904b43e00f68d07d497ff9879
* | Merge "Add announcement of global actions dialog" into lmp-devJason Monk2014-09-241-0/+41
|\ \ | |/ |/|
| * Add announcement of global actions dialogJason Monk2014-09-241-0/+41
| | | | | | | | | | | | | | | | Rather than saying 'Alert', say 'Alert, ...' describing the contents of the menu. Bug: 17559783 Change-Id: I43b1b5ba9ce76b8c205f2d29f2f8ee7569517c19
* | Fix window manager policy state when waking from doze.Jeff Brown2014-09-231-100/+128
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Aggressively trim memory for system_processJohn Reck2014-09-221-0/+1
|/ | | | | | | | | | Bug: 16978006 Don't HWUI-accelerate KeyguardScrim Aggressively trim memory as soon as a ViewRootImpl dies or has its visibility changed. Change-Id: Ie1b7c9d30653456bd2e9f309128174f972999368
* Decouple turning screen on from waking up in policy.Jeff Brown2014-09-191-57/+85
| | | | | | | | This allows us to ensure windows are fully drawn before unblocking screen on while dozing. Bug: 17516245 Change-Id: Ibe63c212b8db855ce26a34a8169f33764b266ee6
* Merge "Make panel menu windows respect elevation" into lmp-devAdam Powell2014-09-191-0/+7
|\
| * Make panel menu windows respect elevationAdam Powell2014-09-181-0/+7
| | | | | | | | | | | | Bug 17430536 Change-Id: I962dfa10d3cb4f735dcaa68f17e7ff278d1580a2
* | Always apply window insets to action modesAlan Viverette2014-09-181-19/+22
|/ | | | | BUG: 17567245 Change-Id: I3c37d228e3a9d3060a4fd1a86abf2ffbf91802e8
* Merge "Use action bar theme for action modes, fix ViewStub inflation theme" ↵Alan Viverette2014-09-181-9/+25
|\ | | | | | | into lmp-dev
| * Use action bar theme for action modes, fix ViewStub inflation themeAlan Viverette2014-09-171-9/+25
| | | | | | | | | | | | BUG: 17262483 BUG: 17513621 Change-Id: I74764570a11da162a224e94978e21e52d17e2e84
* | Merge "Revert "Make starting window hw-accelerated"" into lmp-devJohn Reck2014-09-181-0/+2
|\ \
| * | Revert "Make starting window hw-accelerated"John Reck2014-09-181-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug: 17516789 This change corresponds to a sudden influx of bad surface crashes. Reverting to see if stability returns as this was an optimization CL This reverts commit 29ff1bc57ac2c995c56f15ed6e56e5fb247b2a44. Change-Id: I7835e89017161d94ad05fe46d81bd437c3dae3a7
* | | Fix bar visibility after restarting immersive activitiesAdrian Roos2014-09-171-22/+11
| |/ |/| | | | | | | | | | | | | | | This was a result of using the wrong systemUiVisibility listener. Instead, DecorView now follows the structure in ActionBarOverlayLayout, where we use onWindowSystemUiVisibilityChanged for everything. Bug: 17494017 Change-Id: I1be9165c5ff80021f3a7889d3811cf0c54f68e71
* | Properly redispatch systemUiVisibility flagsAdrian Roos2014-09-161-7/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes two bugs introduced by change I7bd32531130d199c0734ffcb800194e77b7e16c3: When the system window insets consumed by DecorView change as a result of changing flags, the insets must be redispatched to the hierarchy. Also fixes a bug where, as a result of removing the wrong implication of the SYSTEM_UI_FLAG_LAYOUT_STABLE flag by FLAG_DRAWS_SYSTEM_BAR_BACKGROUNDS, the status bar was being forced to black when returning from recents. Bug: 17489047 Bug: 15046646 Change-Id: I127b0ff3b17c4873a7c28d67020f84298ed09db2
* | Magic null-background filling for PhoneWindowsAdam Powell2014-09-141-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the past it's been a recommended approach to avoiding overdraw for apps to set their window background to null at runtime if their content view fully covers their window surface. The problem with this is the IME. The IME can force a resize of the window at unexpected times and unless an app has been configured to fit system windows and manually cover the padded area that the IME window covers, the asynchronous nature of the IME-show process can leave surface buffer garbage visible to the user. In previous platform versions this wasn't an issue since pre-renderthread we would always animate a crossfade from the closed to open state. This animation was always a bit of a hack since it could break the contract of requestLayout/invalidate on the view hierarchy - it could result in a draw happening into the saved "before" state of the crossfade before a pending layout. Now that this has been cleaned up the buffer garbage is sometimes visible. To prevent this, PhoneWindow now detects the state of a null window background and draws solid rects into the area not covered by a window's content. Which color is determined by the window context's theme, though this is not a public API available to apps. Bug 17006497 Change-Id: I714439a1608c4ae135f3d9d49bb165330d9fbe9f
* | Merge "Give a tablet a chance." into lmp-devCraig Mautner2014-09-131-8/+5
|\ \
| * | Give a tablet a chance.Craig Mautner2014-09-131-8/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 500 msec is apparently not enough time to push the pixels around on a Volantis (or Manta, or occasionally Deb). Increasing the timeout eliminates turning the screen on before the surface is completely drawn. Optimizing the drawing path so that we can return the timeout to 500ms has been filed as b/17496306. Fixes bug 16849724. Change-Id: Ic0fca68bc41caa67dba973b5c40915756dc4730f
generated by cgit v1.1 at 2024-12-25 14:14:44 +0000