summaryrefslogtreecommitdiffstats
path: root/policy/src
Commit message (Collapse)AuthorAgeFilesLines
* AudioManager: Add support for master muteMike Lockwood2012-02-102-7/+5
| | | | Signed-off-by: Mike Lockwood <lockwood@android.com>
* PhoneWindowManager: stifle warning that ITelephony service does not existMike Lockwood2012-02-101-5/+1
| | | | Signed-off-by: Mike Lockwood <lockwood@android.com>
* Fix problems dispatching media button events on headless devicesMike Lockwood2012-02-101-4/+6
| | | | | | | | Signed-off-by: Mike Lockwood <lockwood@android.com> Conflicts: policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
* Add headless mode for running the framework without the surface flingerMike Lockwood2012-02-101-37/+60
| | | | | | | | | | | | | | | Enabled by setting system property ro.config.headless to 1 This will allow the framework to run without starting activities, system UI and the keyguard. Framework can still run services, content providers and broadcast receivers. Signed-off-by: Mike Lockwood <lockwood@android.com> Conflicts: policy/src/com/android/internal/policy/impl/PhoneWindowManager.java services/java/com/android/server/PowerManagerService.java services/java/com/android/server/am/ActivityManagerService.java
* PhoneWindowManager: Disable boot progress dialog on headless buildsMike Lockwood2012-02-101-0/+1
| | | | Signed-off-by: Mike Lockwood <lockwood@android.com>
* Extract code from performLayoutAndPlaceSurfacesInnerLocked() into multiple ↵Craig Mautner2012-02-061-2/+3
| | | | | | methods. Change-Id: I80152c38741ce73b92da9483cfed84efbac34f89
* Multi-user - 1st major checkinAmith Yamasani2012-02-031-9/+49
| | | | | | | | | | | | | | | Switching activity stacks Cache ContentProvider per user Long-press power to switch users (on phone) Added ServiceMap for separating services by user Launch PendingIntents on the correct user's uid Fix task switching from Recents list AppWidgetService is mostly working. Commands added to pm and am to allow creating and switching profiles. Change-Id: I15810e8cfbe50a04bd3323a7ef5a8ff4230870ed
* Fix 5906830: Don't crash on lock screens that lack a clock.Jim Miller2012-01-271-2/+4
| | | | | | | This fixes a crash seen in SIM unlock screen where the layout doesn't have a clock to update. Change-Id: Ic1473b60f6d32f3feae9e7aa4510f6e435fa9a73
* Fix 5906830: Update the clock earlier when lock screen comes back from suspend.Jim Miller2012-01-271-0/+7
| | | | | | | | This attempts to fix an issue where sometimes the time shown on lock screen was really old. The code now sets the time immediately when the screen turns on. Change-Id: Ic4649ea342499aea82f997ba488bc2cb45987739
* Merge "Fix 5620754: don't show pattern unlock after SIM unlock if not enabled."Jim Miller2012-01-261-6/+13
|\
| * Fix 5620754: don't show pattern unlock after SIM unlock if not enabled.Jim Miller2012-01-251-6/+13
| | | | | | | | | | | | | | | | This fixes a bug where the device would show pattern unlock after the user entered the SIM PUK unlock code. The code now correctly determines that the device isn't secure and thus shouldn't show the unlock screen. Change-Id: I49fd749592154a4c5840038b92d54ca7ca086074
* | Fix 5907237: dismiss keyguard after the camera app launches.Jim Miller2012-01-241-2/+13
|/ | | | | | | | This fixes a bug where either the home screen or the last app run shows briefly while we wait for the camera app to launch. Instead, we have ActivityManager dismiss keyguard once the camera app is up and running. Change-Id: I1c2986ad84024dce675216a76c19c937c3e2828d
* am 29cd79c7: am c986d6f0: Merge "Fix issue #5906017: Missing menu entries in ↵Dianne Hackborn2012-01-241-0/+6
|\ | | | | | | | | | | | | portrait when in compatibility mode" into ics-mr1 * commit '29cd79c7b0fecd2753fc27405794c0d5b5314302': Fix issue #5906017: Missing menu entries in portrait when in compatibility mode
| * Fix issue #5906017: Missing menu entries in portrait when in compatibility modeDianne Hackborn2012-01-231-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was a bug only when the status bar was hidden, the screen space for the nav bar would not be correctly removed for all frames used in layout computation. This code really $*#&^!! needs to be cleaned up, the whole "status bar is the system bar when on a tablet so it should take space from apps, but status bar doesn't do that on phones but on phones there is a nav bar that does the same thing" thing is whacked. Proof that evolution DOESN'T WORK!!!!!!!!!! Change-Id: I24e4994328480820cb638e7a40aa0b65b7ae2003
| * Fix issue #5823276 again: home repaints after full-screen app is exitedDianne Hackborn2012-01-201-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | Don't consider a window as a candidate for the top fullscreen window if it is not going to be a candiate for layout. This fix does not include the change to ignore app tokens that are hidden. This causes problems in some dialogs that stay hidden until their app is ready to display, but need to perform a series of relayouts during that time to get to the right size. Dropping this part of the change still (mostly?) seems to allow us to avoid the bad states. Change-Id: Ic052cb1499d3287f47e9ffeac5cd2470ee5a308c
| * DO NOT MERGE Revert "Fix issue #5823276: home repaints after full-screen app ↵Justin Ho2012-01-191-3/+3
| | | | | | | | | | | | | | | | is exited" This reverts commit 01b02a734d2988c22b00f5df6346ad03d8bf52b6. Change-Id: I848c01fc44eb9a51ead1116b2647ed838ec1825f
* | am ab9601cd: am 230a7092: Merge "Fix 5863053: Add method to lock screen ↵Jim Miller2012-01-201-0/+6
|\ \ | |/ | | | | | | | | | | immediately." into ics-mr1 * commit 'ab9601cdbb95ae94088750eff9a926a572c1a4d6': Fix 5863053: Add method to lock screen immediately.
| * Merge "Fix 5863053: Add method to lock screen immediately." into ics-mr1Jim Miller2012-01-181-0/+6
| |\
| | * Fix 5863053: Add method to lock screen immediately.Jim Miller2012-01-171-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a bug where the device fails to lock when DevicePolicyManagerService requests the device to be locked and the screen was off because the user hit the power button. The change allows DPMS to directly invoke screen lock, bypasssing the screen state. Change-Id: Iecdda6fc61e9c519119de495be23c69c3b983921
* | | am 10065177: am 2e282f35: Merge "Fix issue #5823276: home repaints after ↵Dianne Hackborn2012-01-131-3/+3
|\ \ \ | |/ / | | | | | | | | | | | | | | | full-screen app is exited" into ics-mr1 * commit '100651779fde99f7ae2a10719d688b51115f08e9': Fix issue #5823276: home repaints after full-screen app is exited
| * | Merge "Fix issue #5823276: home repaints after full-screen app is exited" ↵Dianne Hackborn2012-01-131-3/+3
| |\ \ | | |/ | |/| | | | into ics-mr1
| | * Fix issue #5823276: home repaints after full-screen app is exitedDianne Hackborn2012-01-121-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't consider a window as a candidate for the top fullscreen window if it is not going to be a candiate for layout. Also don't consider windows a candidate for layout if their app token is hidden. This fixes a transient state where we are preparing to unhide the window but have not done so yet. Change-Id: Ife5299ffa003c1df1a4f787b7a2809cbf614ec16
* | | Move where prop dev.bootcomplete is setGuang Zhu2012-01-121-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently test harnesses depends on this flag to determine when the system is fully booted, and start dismissing keyguard, launch tests etc. However, the flag is usually set when the boot animation is still running, and typically about 5 seconds before keyguard is up etc. Moving to to when BOOT_COMPLETE broadcast is sent makes it work more reliable. We also discussed about using sys.boot_completed instead, unfortunately this flag is not in all platform and we still have backwards compatibility to maintain in order to drive unbundled tests. Change-Id: I99b084cd70d8e4bcfe490ddeca868136d32712e2
* | | am 1aff11be: am 7a286d83: Merge "Fix 5620754: don\'t show pattern screen ↵Jim Miller2012-01-121-2/+1
|\ \ \ | |/ / | | | | | | | | | | | | | | | after SIM PUK unlock" into ics-mr1 * commit '1aff11be4585d6ddff784d7e74188963050805fa': Fix 5620754: don't show pattern screen after SIM PUK unlock
| * | Merge "Fix 5620754: don't show pattern screen after SIM PUK unlock" into ics-mr1Jim Miller2012-01-121-2/+1
| |\ \
| | * | Fix 5620754: don't show pattern screen after SIM PUK unlockJim Miller2012-01-101-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a bug introduced in testing 34a62348. The code now properly invokes the callbacks before returning. Change-Id: I637a8a792838379f0c8b42ef634da82787fcd961
| * | | Merge "DO NOT MERGE cherry-picked FU framework tablet commits" into ics-mr1Brian Colonna2012-01-121-9/+17
| |\ \ \ | | |/ / | |/| |
| | * | DO NOT MERGE cherry-picked FU framework tablet commitsBrian Colonna2012-01-091-9/+17
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - cherry-picking framework CLs from master into ics-mr1 that are needed for FU to work on tablets - needed for OEM partners even FU isn't going on xoom Squashed commit of the following: commit 3258f2528f558efdaf34ae15c5425f2d879848fe Author: Brian Colonna <bcolonna@google.com> Date: Tue Dec 13 15:49:48 2011 -0500 Added Face Unlock to tablet lockscreen layouts The Face Unlock Area was not part of the tablet layouts, so prior to this change, Face Unlock would not show up on tablets when selected as the unlock method. The backup unlock method would show up instead. The goal here is for the pattern and PIN unlock layouts (in both portrait and landscape mode) to look the same as before this change. This was a little harder than it was with the phone layouts for two reasons: 1) For the phones it was ok for Face Unlock to be sized such that it just covers the backup method. For the tablets we want Face Unlock to cover far more real estate. 2) The phones were based on a grid layout, whereas the tablet is a linear layout. Note that the diff makes the modifications look way more extensive than they actually are. Basically, in most cases I am putting a relative layout around some existing portion of the layout and putting the Face Unlock Area area inside of the new relative layout. Change-Id: I478becddf2a9ee9fe7b6d653e604fa3ad89b822f commit 821cfe85cf2b3daf074d9749dbf6e0a5663af0de Author: Brian Colonna <bcolonna@google.com> Date: Mon Dec 19 15:51:10 2011 -0500 Unbinding from FU when going to backup Lockscreen was stopping Face Unlock when going to the backup lock, but not unbinding from the Face Unlock service until the device was unlocked. This caused a bug on the tablets where Face Unlock would reappear when switching between portait and landscape orientations, even after the backup lock was exposed. On an orientation change, Face Unlock is restarted if the service is bound to during the orientation change. Since it was bound to when it should not have been, Face Unlock was restarting when it should not have been. The wakelock is also now being poked on an orientation change because on the tablet you can keep Face Unlock alive by switching the orientation back and forth, but eventually the screen would go dark with Face Unlock running. Also, a conditional was moved in activateFaceLockIfAble() so the whole section isn't executed if Face Unlock is not in use. Part of it was being executed with only the inner-most part having the check. This did not cause any issues that I am aware of. Change-Id: Ib452b8ced28a507bf9272dbf5d3477a8abd1ba90 commit fa90bb76ac6b311d12b55d23df4ac44cec62c7b3 Author: Brian Colonna <bcolonna@google.com> Date: Mon Dec 12 18:02:23 2011 -0500 Changed how Face Unlock coordinates are specified Was using View.getLeft() and View.getTop() to specify the upper-left corner of the Face Unlock area. That gives coordinates relative the view, which was fine for the phones. For the tablet it needs coordinates relative to the window (which still works for the phones). Also fixed a 'bug' where h and w were swapped. However, it wasn't causing a problem because it was swapped in two places. Change-Id: I86c1f68439f1dcef826cfe6b8fb56c9a4a6b8dc3 Change-Id: I962c0486be85949e002b0a2701286a6a39251f36
* | | am d3872f55: am 62fad768: Merge "Fix 4560303: Add setting to lock later when ↵Jim Miller2012-01-101-4/+11
|\ \ \ | |/ / | | | | | | | | | | | | | | | power button pressed" into ics-mr1 * commit 'd3872f55045b7ce7be7dd7ae5fff37d7988bdcb2': Fix 4560303: Add setting to lock later when power button pressed
| * | Fix 4560303: Add setting to lock later when power button pressedJim Miller2012-01-091-4/+11
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a feature to delay locking the device when the power button is pressed. This fixes a use case where the user wants to turn off the display (e.g. to save power) but doesn't want to lock the device. For the case of a secure device (user has a pin/password/pattern), this will lock the device immediately or not based on the setting. For the non-secure case, this always "locks" the device to provide easy access to the camera while preventing unwanted input. Change-Id: Ie328485c3f7559e26896d761cbf0e69d3f4df4e2
* | Merge "Unbinding from FU when going to backup"Brian Colonna2012-01-031-6/+11
|\ \
| * | Unbinding from FU when going to backupBrian Colonna2011-12-191-6/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lockscreen was stopping Face Unlock when going to the backup lock, but not unbinding from the Face Unlock service until the device was unlocked. This caused a bug on the tablets where Face Unlock would reappear when switching between portait and landscape orientations, even after the backup lock was exposed. On an orientation change, Face Unlock is restarted if the service is bound to during the orientation change. Since it was bound to when it should not have been, Face Unlock was restarting when it should not have been. The wakelock is also now being poked on an orientation change because on the tablet you can keep Face Unlock alive by switching the orientation back and forth, but eventually the screen would go dark with Face Unlock running. Also, a conditional was moved in activateFaceLockIfAble() so the whole section isn't executed if Face Unlock is not in use. Part of it was being executed with only the inner-most part having the check. This did not cause any issues that I am aware of. Change-Id: Ib452b8ced28a507bf9272dbf5d3477a8abd1ba90
* | | am c0139281: am c892e177: Merge "Hide emergency call text if not support ↵John Wang2011-12-201-12/+27
|\ \ \ | |/ / |/| / | |/ | | | | | | it." into ics-mr1 * commit 'c01392816fbb16ca76c738bc801f3b2c34548c06': Hide emergency call text if not support it.
| * Hide emergency call text if not support it.John Wang2011-12-141-12/+27
| | | | | | | | | | | | | | | | Show "emergency call only" text in carrier string only if phone supports emergency calls. bug:5570742 Change-Id: Ie826583fd55073e57c5fe4fe6e585781127caa6a
* | Add a new ui mode for "appliance"Joe Onorato2011-12-151-1/+3
| | | | | | | | | | | | | | | | The idea is that this is a device which is more-or-less headless. It might have some limited interaction capabilities, but it's not something that you want to rely on having. Change-Id: Ib92f53a120bf83de781728011721a4859def7d9f
* | am 0be53567: am 19a06fe9: Merge "Fix issue #5755172: Soft menu key ↵Dianne Hackborn2011-12-133-2/+4
|\ \ | |/ | | | | | | | | | | disappears when menu is open" into ics-mr1 * commit '0be53567c1c2299c548d3204d2b9240108fbd53a': Fix issue #5755172: Soft menu key disappears when menu is open
| * Fix issue #5755172: Soft menu key disappears when menu is openDianne Hackborn2011-12-133-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need to work more like before in determining whether the menu key is needed -- in some cases look back in the window list to determine this if we don't know the value from the current window. This requires adding a new private flag indicating whether the compat menu state is known for a window, which is set by PhoneWindow as part of its existing process of computing the flag for its own windows. Now we can have a new API on WindowState to determine the value of this flag for a window, which if needed walks back in the window list to find a window the value is known for (or stops at what the policy has determined is the top full-screen window, so we stop like we used to at things like the lock screen or the bottom of an application). Change-Id: I829de6d629b5af8bcb422cb85249ee4041c7205e
* | Changed how Face Unlock coordinates are specifiedBrian Colonna2011-12-121-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | Was using View.getLeft() and View.getTop() to specify the upper-left corner of the Face Unlock area. That gives coordinates relative the view, which was fine for the phones. For the tablet it needs coordinates relative to the window (which still works for the phones). Also fixed a 'bug' where h and w were swapped. However, it wasn't causing a problem because it was swapped in two places. Change-Id: I86c1f68439f1dcef826cfe6b8fb56c9a4a6b8dc3
* | Merge "Checking whether screen is on in constructor fixes 5658742"Steven Ross2011-12-091-2/+4
|\ \
| * | Checking whether screen is on in constructor fixes 5658742Steven Ross2011-12-091-2/+4
| | | | | | | | | | | | Change-Id: Ic96c8dd9ee9e86000b0cbe22a7d068a8ee424448
* | | am 03e63427: am 8e0ecbfc: Merge "Shortcut keys should be handled on down, ↵Jeff Brown2011-12-091-11/+31
|\ \ \ | | |/ | |/| | | | | | | | | | | | | not up." into ics-mr1 * commit '03e634270d880407316b51fac2278e604fc82703': Shortcut keys should be handled on down, not up.
| * | Merge "Shortcut keys should be handled on down, not up." into ics-mr1Jeff Brown2011-12-071-11/+31
| |\ \
| | * | Shortcut keys should be handled on down, not up.Jeff Brown2011-12-071-11/+31
| | | | | | | | | | | | | | | | | | | | Bug: 5720360 Change-Id: I3afc278e576ea992c76f024c8b6bad14b214239c
* | | | am 944c985b: am e0e9fd98: Merge "Fix system hotkey handling." into ics-mr1Jeff Brown2011-12-093-78/+102
|\ \ \ \ | |/ / / | | | / | |_|/ |/| | * commit '944c985b4199e6e029568ea87004c9727e469cc0': Fix system hotkey handling.
| * | Merge "Fix system hotkey handling." into ics-mr1Jeff Brown2011-12-073-78/+102
| |\ \ | | |/
| | * Fix system hotkey handling.Jeff Brown2011-12-073-78/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed a problem where the key up for the ALT or META key was not delivered to the task switcher dialog because it was deemed to be inconsistent with the window's observed state. Consequently the dialog would not be dismissed when the key was released. Moved global hotkey handling for META+* shortcuts and ALT/META-TAB into the window manager policy's interceptKeyBeforeDispatching method. This change prevents applications from hijacking these keys. The original idea was that these shortcuts would be handled only if the application did not handle them itself. That way certain applications, such as remote desktop tools, could deliberately override some of these less important system shortcuts. Unfortunately, that does make the behavior inconsistent across applications. What's more, bugs in the onKeyDown handler of applications can cause the shortcuts to not work at all, for no good reason. Perhaps we can add an opt-in feature later to enable specific applications to repurpose these keys when it makes sense. Bug: 5720358 Change-Id: I22bf17606d12dbea6549c60d20763e6608576cf7
* | | am 7377e593: am 0e385ee4: am b32785c6: Merge "More fixing for issue ↵Dianne Hackborn2011-12-071-0/+3
|\ \ \ | |/ / | | | | | | | | | | | | | | | #5366535: Lockscreen has wrong layout..." into ics-mr0 * commit '7377e59314885b8ef65bd19d04984998cb2e5ff4': More fixing for issue #5366535: Lockscreen has wrong layout...
| * | am b32785c6: Merge "More fixing for issue #5366535: Lockscreen has wrong ↵Dianne Hackborn2011-12-071-0/+3
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | layout..." into ics-mr0 * commit 'b32785c6e893743956e28b285b8e6f6fc7aa8edb': More fixing for issue #5366535: Lockscreen has wrong layout...
| | * | More fixing for issue #5366535: Lockscreen has wrong layout...Dianne Hackborn2011-12-071-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ...but corrects itself Change upgrade window to not allow the device to rotate while it is shown. Change-Id: I75b126ab8806b84a0351e2706ebea10570bde575
* | | | am 675a5ba8: am 3b5555fc: Merge "Make new ringer toggles on power menu ↵Amith Yamasani2011-12-071-2/+1
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | | | | | accessible and navigable with keyboard." into ics-mr1 * commit '675a5ba82f886d8a5f954219b6544a97acb17e29': Make new ringer toggles on power menu accessible and navigable with keyboard.
generated by cgit v1.1 at 2025-03-21 23:21:36 +0000