summaryrefslogtreecommitdiffstats
path: root/policy
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Fix power key handling after volume change. Bug: 5497716" into ics-mr0Bart Sears2011-10-261-1/+3
|\
| * Fix power key handling after volume change.Jeff Brown2011-10-251-1/+3
| | | | | | | | | | | | | | | | | | Bug: 5497716 We should only cancel the pending power key when there actually is one pending. Change-Id: Iab684d24a643e1be4a8abde5cf905ca1819e9aa8
* | Fix 5479823: black patch was showing before resuming callBrian Colonna2011-10-241-4/+5
|/ | | | | | | | | | | | | | | | | | | | | - This issue was marked as RelTeamHotIssue - When Face Unlock is enabled, the black area is shown when going into the emergency dialer to prevent the backup lock from showing. However, it was doing this even if Face Unlock has already gone to the backup method. - Since the same code is used for returning to a call as is used for starting the emergency dialer, it was doing the same thing when resuming a call. - Just had to add a simple check to only display the black area if Face Unlock is still running. - Note that this did *not* cause a problem when Face Unlock was not the unlock method. Change-Id: Icc4deebcb47ceda035ea29c7d976342d3a8a60a7
* Merge "Added callback to allow Face Unlock to hide black area" into ics-mr0Brian Colonna2011-10-241-0/+7
|\
| * Added callback to allow Face Unlock to hide black areaBrian Colonna2011-10-241-0/+7
| | | | | | | | | | | | | | | | | | | | - Part of fix 5491362 (RelTeamHotIssue) - Because the fix closes the camera early, this change is needed so the black area isn't still hanging around while the camera fades to the backup lock. Change-Id: Iab7c264adab0fb05979fe2732048ccf2237e64c5
* | CherryPick 35530d from master to mr0. do not merge.Xavier Ducrohet2011-10-241-2/+2
|/ | | | | | | | qemu.hw.mainkeys indicates if the device has h/w main (home/back) keys. If it has main keys, then the navigation bar is *not* displayed. Change-Id: Idb36a1f787360363a009463f0c016a423594a5b9
* Fix 5493266: Properly restore background after playing musicJim Miller2011-10-202-20/+25
| | | | | | | | KeyguardViewBase maintains the transparent background for all lock screen views. The background was being overwritten by the change to make lock screen opaque when music was being shown. Change-Id: Id1ab415f68746b20c9229fa58fef9ec8be354f01
* Add hasNavigationBar() to the window manager.Daniel Sandler2011-10-191-0/+14
| | | | | | | | | | | | | | | | It is no longer sufficient to check the value of internal.R.bool.config_showNavigationBar to determine if a navigation bar (separate from the status bar) is shown on a device, because the emulator needs to be able to override this value (now possible by setting qemu.hw.mainkeys to "1" or "0", for navbar or no navbar, respectively). This logic is now contained in PhoneWindowManager, and any clients wishing to know whether the system has a software nav bar should consult the new hasNavigationBar() method. Bug: 5404945 Change-Id: I119d32a8c84b88b2ef46f63244e7f11dc5de0359
* Merge "Fix 5288804: Make music trasports in lockscreen more closely match ↵Jim Miller2011-10-181-0/+6
|\ | | | | | | design" into ics-mr0
| * Fix 5288804: Make music trasports in lockscreen more closely match designJim Miller2011-10-181-0/+6
| | | | | | | | | | | | | | | | | | This fixes three issues; - Make the background black while the transport is showing. - Show scrim sandwiched between artwork and overlapping UI. - Remove gaps in sides of background assets. Change-Id: I563fc680c4c042d8b25ec37332aeab528cf838ca
* | Merge "Fix 5433466 - FU out of position during orientation change" into ics-mr0Brian Colonna2011-10-181-12/+25
|\ \
| * | Fix 5433466 - FU out of position during orientation changeBrian Colonna2011-10-181-12/+25
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you turn the device from portrait to landscape mode and immediately invoke the lockscreen, it will come up in landscape mode and switch to the desired portrait mode within a couple of seconds. Previously, Face Unlock would come up in landscape mode, but its position would not change once lockscreen corrected itself, causing Face Unlock to be partly off the screen. This has been fixed by checking if we are already bound to Face Unlock when the layout is created. If this is true, then the layout is being created due to a change in orientation, and we stop Face Unlock, and restart it at the new position. This commit also adds a fix where we now use INVISIBLE for the Face Unlock area when it is not showing instead of using GONE. The dimensions of the Face Unlock area is 0-by-0 when set to GONE, and we want to avoid the possibility for the Face Unlock service being assigned a zero area. I'm not sure if this was ever causing problems, but it certainly is not the intended behavior. Also cleaned up some comments and logging. Change-Id: I68deb49cb26dafb5c238167d0c23f0eed2cfb75a
* | Merge "Fix 5452698: fix broken logic in reportFailedAttempt() in lockscreen" ↵Jim Miller2011-10-181-8/+12
|\ \ | |/ |/| | | into ics-mr0
| * Fix 5452698: fix broken logic in reportFailedAttempt() in lockscreenJim Miller2011-10-171-8/+12
| | | | | | | | | | | | | | | | | | | | | | This fixes a bug where we were no longer showing the countdown dialog every 5 attempts or "forgot pattern" button when the user has a fallback password enabled on the pattern unlock screen. It now correctly shows the dialog whenever the user hits a multiple of 5 bad attempts on any of the pin/pattern/password screens. Change-Id: I4eb47b4149958a93572d256a4a70f9d67bc1eb38
* | Merge "Updating screenshot animation and behaviour. (Bug: 5333706)" into ics-mr0Winson Chung2011-10-181-0/+5
|\ \
| * | Updating screenshot animation and behaviour. (Bug: 5333706)Winson Chung2011-10-181-0/+5
| |/ | | | | | | | | | | | | | | - Removing the second ticker text - Adding a new animation to the status bar - Adding a large icon to the notification Change-Id: I8778178519fc72ffc299e8d624069b684475191d
* | Merge "Fix 5466678: use new setSystemUiVisibility() API to enable clock in ↵Jim Miller2011-10-173-2/+8
|\ \ | |/ |/| | | statusbar" into ics-mr0
| * Fix 5466678: use new setSystemUiVisibility() API to enable clock in statusbarJim Miller2011-10-173-2/+8
| | | | | | | | | | | | | | This fixes a bug where the clock wasn't being shown in the statusbar while the music widget is showing. Change-Id: Ic1c52c4ab7fa1490fe14ddafaf2c494bcf51866d
* | Fix stupid bug breaking touch on devices without a nav bar.Dianne Hackborn2011-10-171-1/+1
|/ | | | Change-Id: Id76b7ab5625470fcc72541fb2fe8845cddba523f
* Merge "Fix issue #5398675: It's (too) easy to keep the navigation bar..." ↵Dianne Hackborn2011-10-161-32/+77
|\ | | | | | | into ics-mr0
| * Fix issue #5398675: It's (too) easy to keep the navigation bar...Dianne Hackborn2011-10-161-32/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ...from ever becoming visible Now there is a 1 second delay from when the user dismisses the nav bar until when it can be re-hidden. Also move the code for capturing touch events while nav bar is hidden out to be used even when there is no nav bar, so this API behaves consistently across devices whether or not they have some element of the UI that is being hidden. On devices with a nav bar, this will all work the same as prime (the flag is set, the app gets the callback about the flag being set, when the user touches that touch is captured so the app doesn't see it put does clear the flag and tell the app about this). Change-Id: Icb5ea0ddaf614aa3f12d2140796217f128761dee
* | Fix 5466793: Fix memory leak in system process when face lock is enabled.Jim Miller2011-10-161-0/+16
|/ | | | | | | | | | Previously, the code was not unregistering the callback when we unlocked the device, which kept a reference to LockPatternKeyguardView indirectly by a reference to mFaceLockCallback. It now correcly removes the callback when we unlock the device. Change-Id: Ie592d007a1dfc2416b9e8956aba2c34e3d0120ee
* Merge "going directly to backup after face unlock fails 15 times" into ics-mr0Uriel Rodriguez2011-10-151-2/+27
|\
| * going directly to backup after face unlock fails 15 timesUriel Rodriguez2011-10-141-2/+27
| | | | | | | | | | | | | | | | | | - after 15 failed face unlock attempts, go to backup until the backup method is successful - if the backup method times out (because too many unsuccessful unlocking attempts), face unlock will not be launched until the backup method is used sucessfully - fixes 5365919 Change-Id: I9aef7a4f1abcceefc5d6f1c0458ae5cbe8a902df
* | Fix 5458658: Fix memory leak in lock screenJim Miller2011-10-141-0/+1
| | | | | | | | | | | | | | This fixes a memory leak caused by not unregistering the info callback held when LockPatternKeyguardView gets destroyed. Change-Id: I8c008b6f8a5e8471bd0e1fd3939aa75175923ce5
* | Fix 5358124: Better transport control visibility management in lock screenJim Miller2011-10-131-5/+43
|/ | | | | | | | | | | | | | | | | | | This changes TransportControlView to be "sticky" on lockscreen. Basically, once it appears on lockscreen, it stays there until unlocked and then locked again in paused state. Tested basic design goals (using Music2): - play then lock -> shows - pause then lock -> not shown - toggle pause to play while locked and not shown -> shows - pause after played once while locked -> stays until we unlock and lock again while paused - remote control play while paused & sleeping -> resume lockscreen -> shows Also tested: - configuration changes (orientation) to ensure widget continues to show after it once appears - remote events while lock screen on -> keeps lockscreen on. - remote events while sleeping -> doesn't wake. Change-Id: I23418c5f7dfd1457c0844d2683772e8a3ed0abd1
* Merge "Making FaceUnlock not pop up for overlays Fixes 5451837 Fixes ↵Steven Ross2011-10-131-21/+19
|\ | | | | | | 5446341" into ics-mr0
| * Making FaceUnlock not pop up for overlays Fixes 5451837 Fixes 5446341Steven Ross2011-10-131-21/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the screen turns on because of an incoming phone call or when the emergency dialer is selected, FaceUnlock is deactivated until the phone call is completed and the screen is turned off. This also checks for non-phone overlays. If the lockscreen becomes unfocused while the screen is on, we assume that the reason is an overlay and prevent FaceUnlock from starting. The normal clock app is not considered an overlay by this approach, and thus it works as intended (back button brings up FaceUnlock). Also reverts: https://android-git.corp.google.com/g/#/c/139885/2 to make FaceUnlock appear when music is playing again Change-Id: Id715878556667d2b7e35c30a28d91be6a4eee575
* | Fixed problem where Face Unlock area was showingBrian Colonna2011-10-131-2/+8
|/ | | | | | | | | | | I introduced a bug cl https://android-git.corp.google.com/g/#/c/141926 that caused black box to hide lock pattern even when not using Face Unlock. Fixed by adding the corresponding check to make sure Face Unlock is being used. Change-Id: I9c429c99d7db4d1ab831080f23a1e10123dbfe3e
* Merge "Fix 5451144: Poking wakelock upon fallback" into ics-mr0Brian Colonna2011-10-131-0/+8
|\
| * Fix 5451144: Poking wakelock upon fallbackBrian Colonna2011-10-131-0/+8
| | | | | | | | | | | | | | | | | | | | | | Now poking the wakelock when Face Unlock goes to the fallback method. Previously, the backup lock would stay up for a varying amount of time depending on how long Face Unlock took before fallback. The backup is now consistently displayed for 5 seconds. Also added comments to some older code. Change-Id: I9f6bdd2d3015e7eb9cb90143737a3cdc87189993
* | Merge "Send ACTION_USER_PRESENT when provisioning is completed." into ics-mr0Martijn Coenen2011-10-134-5/+39
|\ \
| * | Send ACTION_USER_PRESENT when provisioning is completed.Nick Pelly2011-10-114-5/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is needed for application to know when the keyguard becomes unlocked, because isKeyguardLocked() is typically true while provisioning (setup wizard), but ACTION_USER_PRSENT was not sent when it transitions to false after provisioning. Bug: 5436867 Bug: 5430833 Change-Id: Icae13ff9cab84774a002a426eb9cb353fa1dc530
* | | Merge "Bug 5312828 - Menu button not responding" into ics-mr0Adam Powell2011-10-131-6/+16
|\ \ \ | |_|/ |/| |
| * | Bug 5312828 - Menu button not respondingAdam Powell2011-10-131-6/+16
| | | | | | | | | | | | | | | | | | | | | Increase tolerance for apps calling invalidateOptionsMenu at inconvenient times. Change-Id: I712b20002afd0f056c3f05b160c5fa9c2ef0b552
* | | Merge "Fix issue #5446988: WindowManager warns BOOT TIMEOUT,..." into ics-mr0Dianne Hackborn2011-10-131-13/+12
|\ \ \
| * | | Fix issue #5446988: WindowManager warns BOOT TIMEOUT,...Dianne Hackborn2011-10-131-13/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ...dev.bootcomplete flags is set before boot animation is out Also: - Fix crash in recent apps if the intent for an old app didn't happen to have the new task flag set. - Fix issue where a crash in system UI would cause the crash dialog to be displayed below it, effectively locking the UI. Now the crash dialog for persistent processes is shown above everything else. Change-Id: I0312001a92beeae5f644c7c3e5c5e19f6716df36
* | | | Merge "Fix 5437700: Underlying backup method was exposed" into ics-mr0Brian Colonna2011-10-131-19/+54
|\ \ \ \
| * | | | Fix 5437700: Underlying backup method was exposedBrian Colonna2011-10-131-19/+54
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At one point we added a timeout to the black box that covers the underlying backup unlock method so if Face Unlock doesn't start or crashes, the user will see the backup method rather than being stuck looking at a black box. However, when powering the phone on and off quickly, the message to time out the black box could be received at the wrong time, causing it to expose the underlying backup method when it shouldn't. This solution clears the existing SHOW/HIDE messages from the handler's message queue before sending a new SHOW/HIDE message. In particular, it clears out a delayed HIDE message when a SHOW is sent so the SHOW can't be undone by a pending delayed HIDE message. Also, logging errors for a couple of exceptions instead of rethrowing so we can gracefully go to the backup in these cases. Patch set 2 fixes problem where rare exceptions could prevent ever binding to the service again because mBoundToFaceLockService was still true. Change-Id: Ieb7b6723161070f509277f67dc9ef100cf7c1aa6
* | | | Break apart DISABLE_HOME and DISABLE_RECENT.Daniel Sandler2011-10-133-13/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Additionally, start using setSystemUiVisibility() where possible in the keyguard to allow activities and dialogs to re-enable some of the navigation keys (notably: home but not recents). Finally, stop disabling MENU for activities atop the keyguard. Bug: 5380495 // no home in driveabout, clock Bug: 5396134 // able to show home/recent in keyguard Change-Id: I04eb224554ee8cff79476b85148c4cda75bb0b62
* | | | Merge "Stop enabling all disabled status bar features from GlobalActions. ↵Daniel Sandler2011-10-131-6/+1
|\ \ \ \ | |/ / / |/| | | | | | | (DO NOT MERGE)" into ics-mr0
| * | | Stop enabling all disabled status bar features from GlobalActions. (DO NOT ↵Daniel Sandler2011-10-121-6/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MERGE) Leaky singleton bug! GlobalActions, recents, and the keyguard are all in the same process and therefore receive the same StatusBarManager instance. Therefore, their calls to enable() and disable() clobber one another. Bug: 5423182 Change-Id: Ie535d88f5a5bb940dabee5f1ac176027e1793c5c
* | | | Merge "Fixes 5446301" into ics-mr0Brian Colonna2011-10-121-1/+11
|\ \ \ \
| * | | | Fixes 5446301Steven Ross2011-10-121-1/+11
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | If the user is making an emergency call, don't bring up Facelock Has the side effect of not bringing up Facelock if they cancel dialing Change-Id: I5d23e89b7f687f260670d41f1cc55ebf2a135181
* | | | Fix 5444675: Fix vibrate regression on Pattern and PIN unlock screens.Jim Miller2011-10-121-3/+5
| |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a regression caused by a resource change to the vibrate pattern. It used to contain an array of delays and values. Now it has another mode with just one value with an associated change to the vibrate API. Instead of using a custom vibration pattern, it now just follows the system vibrate pattern for HapticFeedbackConstants.VIRTUAL_KEY, which is shared by the home key, among other things. Change-Id: Ib58493a96a42383955ae59f8ac3865bb46a86a31
* | | DO NOT MERGE. Improve screenshot chord debouncing.Jeff Brown2011-10-121-130/+180
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug: 5011907 Introduce a 150ms delay in handling volume down keys while waiting to see if a power key will follow. Don't trigger the screenshot chord if both volume up and volume down are pressed together. Don't trigger the long-press power menu if volume keys are also pressed. Require the user to press both keys in the chord within the debounce time and continue long-pressing them in order to trigger the screenshot action. Change-Id: I248968d37b73c09d6d08e7f62667c443eba32da0
* | Fix bug 5396097 - menu theme consistencyAdam Powell2011-10-111-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix a bug where action bar menus were using the wrong context to inflate stock views. This was causing them to use the action bar's themed widget context instead of the current theme's specific action bar items. Note that action views in the menu will still be inflated using the themed widget context. This can produce some weird side effects if the action views use theme attributes relating to these action bar item attributes. Change-Id: Ied3614d1fedb10a0f5366bbe7b90cd5f2f1ff969
* | Fix 5386408: Fix battery state information propagation in Lock ScreenJim Miller2011-10-101-1/+1
| | | | | | | | | | | | | | | | | | | | This fixes a bug where Lock Screen would sometimes inappropriately show "charged" if it took a while for Lock Screen to get an update on the battery state. It now starts with the state set to BATTERY_STATUS_UNKNOWN so we properly update listeners when we finally get battery information in handleBatteryUpdate(). Change-Id: I71018a233f38b2f897ff2e6592d7e310550fa016
* | Merge "Fix 5406921: Register for receiving phone state changes when KGSVM ↵Jim Miller2011-10-101-0/+3
|\ \ | | | | | | | | | gets created."
| * | Fix 5406921: Register for receiving phone state changes when KGSVM gets created.Jim Miller2011-10-071-0/+3
| | | | | | | | | | | | | | | | | | | | | This fixes a bug where the state wasn't being updated because it wasn't registered for KeyguardUpdateMonitor state changes when the view first created, like on first boot. Change-Id: Ic6838afffd0de51decdc43a8e8a796696aed49df
generated by cgit v1.1 at 2025-08-06 18:51:12 +0000