summaryrefslogtreecommitdiffstats
path: root/policy
Commit message (Collapse)AuthorAgeFilesLines
* Fix issue #4603422: Compatibility mode button doesn't always updateDianne Hackborn2011-06-141-23/+19
| | | | | | | | | | | | | We now tell the system bar every time the top activity has changed for it to re-evaluate its UI state. Also fix issue #: 4607102 Low rider notifications. It turns out this was due to the change in the dialog asset; the notification UI was relying on this having a lot of padding to make it sit above the status bar. Now we have an explicitly mechanism to set how much it overlaps (or doesn't) the status bar. Change-Id: Iab5ebd86e620ff4fc4cd77206e18af962ec2830e
* Work on issue #4518815: Compatibility mode introduces compatibility ↵Dianne Hackborn2011-06-081-5/+4
| | | | | | | | | | | | | | | | | | | regression... ...for Market App iRunner There were a lot of serious issues with how we updated (or often didn't update) the display and resource state when switching compatibility mode in conjunction with restarting and updating application components. This addresses everything I could find. Unfortunately it does *not* fix this particular app. I am starting to think this is just an issue in the app. This change does fix a number of other problems I could repro, such as switching the compatibility mode of an IME. Also a few changes here and there to get rid of $#*&^!! debug logs. Change-Id: Ib15572eac9ec93b4b9966ddcbbc830ce9dec1317
* DO NOT MERGE. Restore status bar on phones.Daniel Sandler2011-06-031-2/+3
| | | | | Bug: 4529373 Change-Id: Ie08522dbf762e80ac077ce403ff83312cec907f7
* Fix issue #4500511: Holo effect background doesn't reach top of screen anymoreDianne Hackborn2011-06-011-36/+38
| | | | Change-Id: Iebefe924e71206f3e6388eaee64f7b1416bc3239
* Fix issue #4502672: Wrong xml resources used for homescreen widgets.Dianne Hackborn2011-05-311-4/+9
| | | | | | | | | | | | | | | There was a race in the system process between applying the initial configuration and executing code in higher-level system services like the app widget service that relies on the config. For some reason it starting showing up more after my code changes; it should now be completely fixed. Also fix the activity starting window to run in compatibility mode if its application is going to be in compatibility mode. And some various cleanup and small fixes. Change-Id: I0566933bf1bbb4259c1d99a60c0a3c19af1542e5
* Rework how we decide whether to use system or status bar.Dianne Hackborn2011-05-261-10/+19
| | | | | | | | | | | The PhoneWindowManager is now responsible for determing this, since it needs to do this before we can generate the configuration since we need to take into account the system bar size we will use. Also the Display should now report the screen height without including the system bar. Change-Id: I82dfcc5e327e4d13d82c373c6c870f557a99b757
* Minor Alt-TAB / Recent Apps Dialog improvements. (DO NOT MERGE)Jeff Brown2011-05-252-26/+61
| | | | | | | | | | | | | | | Alt-TAB should have different semantics from the APP_SWITCH key or long-press on HOME. Accordingly, remove the fallback action for Alt-TAB and initiate the task switching behavior directly in the policy. Modified RecentApplicationsDialog to be more precise about the initial modifiers that it considers to be holding the dialog. The dialog is now dismissed by a second press on the APP_SWITCH key or by a second long press on HOME. Change-Id: I07e72dc4e1f3cd8edaf357c1d49e79f60d6d1604
* Support primitive ALT-TAB style navigation using Recent Apps. (DO NOT MERGE)Jeff Brown2011-05-252-26/+92
| | | | Change-Id: I0296a09519ba9417c208d197ebd996b586ee3daa
* Support chorded fallback keys. (DO NOT MERGE)Jeff Brown2011-05-241-6/+11
| | | | | | | | | | | | | | | | Also be more careful about canceling fallback keys during focus transitions, when the application handles the key, or when the policy decides to do something different. Fixed a crash due to JNI CallObjectMethod returning an undefined value (not null) when an exception is thrown. Fixed a crash due to the policy trying to create a Dialog for recent apps on the dispatcher thread. It should happen on the policy's Looper instead. Bug: 4187302 Change-Id: I043f82913830f411b3bb4018d6422467b6ca454f
* Add new "-swNNNdp" resource qualifier.Dianne Hackborn2011-05-191-6/+14
| | | | Change-Id: I0101e88ca9d8d44138bdcaf571f24b0352f4f6ce
* Merge "DO NOT MERGE Use action bar overflow menus on large configurations as ↵Adam Powell2011-05-171-3/+2
|\ | | | | | | well as xlarge." into honeycomb-mr2
| * DO NOT MERGE Use action bar overflow menus on large configurations asAdam Powell2011-05-161-3/+2
| | | | | | | | | | | | | | | | well as xlarge. ICS will have a more intelligent way of determining this. Change-Id: I1ba6460dec09b8259db858c78a9157bb7742c85d
* | DO NOT MERGE. From main -- Start work on simulating landscape/portrait when ↵Dianne Hackborn2011-05-161-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | orientation is locked. Not yet working, so turned off. Also fix a bug where the display size configuration became inconsistent after a configuration change -- we now figure out everything about the display size when computing a new configuration. Change-Id: Id155f133c0bf108508a225ef64ed3ca398a90a58
* | DO NOT MERGE: From master -- Fix bug in deciding which rotation to use for ↵Dianne Hackborn2011-05-161-37/+32
|/ | | | | | an orientation. Change-Id: Ie271123271a662f3f753f381ce4c43ad7904dc4a
* Better compat mode part one: start scaling windows.Dianne Hackborn2011-05-091-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | First step of improving app screen size compatibility mode. When running in compat mode, an application's windows are scaled up on the screen rather than being small with 1:1 pixels. Currently we scale the application to fill the entire screen, so don't use an even pixel scaling. Though this may have some negative impact on the appearance (it looks okay to me), it has a big benefit of allowing us to now treat these apps as normal full-screens apps and do the normal transition animations as you move in and out and around in them. This introduces fun stuff in the input system to take care of modifying pointer coordinates to account for the app window surface scaling. The input dispatcher is told about the scale that is being applied to each window and, when there is one, adjusts pointer events appropriately as they are being sent to the transport. Also modified is CompatibilityInfo, which has been greatly simplified to not be so insane and incomprehendible. It is now simple -- when constructed it determines if the given app is compatible with the current screen size and density, and that is that. There are new APIs on ActivityManagerService to put applications that we would traditionally consider compatible with larger screens in compatibility mode. This is the start of a facility to have a UI affordance for a user to switch apps in and out of compatibility. To test switching of modes, there is a new variation of the "am" command to do this: am screen-compat [on|off] [package] This mode switching has the fundamentals of restarting activities when it is changed, though the state still needs to be persisted and the overall mode switch cleaned up. For the few small apps I have tested, things mostly seem to be working well. I know of one problem with the text selection handles being drawn at the wrong position because at some point the window offset is being scaled incorrectly. There are probably other similar issues around the interaction between two windows because the different window coordinate spaces are done in a hacky way instead of being formally integrated into the window manager layout process. Change-Id: Ie038e3746b448135117bd860859d74e360938557
* Fix 3201849: Enable hardware acceleration in LockScreen WaveView [DO NOT MERGE]Jim Miller2011-03-102-1/+5
| | | | Change-Id: I07bbed7843857158cd2c1ffd9b184bde7fd5860d
* Remove guard preventing onDetachedFromWindow() from being calledPatrick Dubroy2011-03-071-1/+1
| | | | | | This was the cause of 3510699: Launcher has leaked IntentReceiver. Change-Id: I7d0e4662314d657f6ac06a9a9d37861f8d8ee975
* Wake screen from external HID peripherals.Jeff Brown2011-03-024-2/+45
| | | | | | | | | | | | | | | | | | Added some plumbing to enable the policy to intercept motion events when the screen is off to handle wakeup if needed. Added a basic concept of an external device to limit the scope of the wakeup policy to external devices only. The wakeup policy for internal devices should be based on explicit rules such as policy flags in key layout files. Moved isTouchEvent to native. Ensure the dispatcher sends the right event type to userActivity for non-touch pointer events like HOVER_MOVE and SCROLL. Bug: 3193114 Change-Id: I15dbd48a16810dfaf226ff7ad117d46908ca4f86
* am 4b8c9b74: am 7fff2d19: am 1de4a2ca: am 62619392: Merge "Fix leak when ↵Dianne Hackborn2011-03-021-1/+14
|\ | | | | | | | | | | | | keylock is recreated." * commit '4b8c9b740528301d3ca60fe3b4b861fcd85ceb0a': Fix leak when keylock is recreated.
| * am 7fff2d19: am 1de4a2ca: am 62619392: Merge "Fix leak when keylock is ↵Dianne Hackborn2011-03-011-1/+14
| |\ | | | | | | | | | | | | | | | | | | recreated." * commit '7fff2d19a24f9f9b669676864dc5652ab179d2fc': Fix leak when keylock is recreated.
| | * am 62619392: Merge "Fix leak when keylock is recreated."Dianne Hackborn2011-02-281-1/+14
| | |\ | | | | | | | | | | | | | | | | * commit '626193926df0b3c7236e5c244f30d797d9192e0d': Fix leak when keylock is recreated.
| | | * Fix leak when keylock is recreated.Kenneth Andersson2011-02-281-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | DigitalClock could sometimes leak when the keylock was recreated. This happened because onDetachedFromWindow() was called BEFORE onAttachedFromWindow(). This is the flow that causes the memory leak: 1) The LockPatternKeyGuardView is created and added. This will start a loop dispatching onAttachedToWindow() to all views involved. 2) PatternUnlockScreen.onAttachedToWindow() is called 3) If the configuration has changed since creation, recreateMe() in LockPatternKeyguardView.java is called. 4) recreateScreens() is called 5) PatternUnlockScreen is removed (to be re-added later) in LockPatternKeyguardView.recreateUnlockScreen() 6) Since DigitalClock is a part of PatternUnlockScreen, its onDetachedFromWindow() will be called. 7) The loop started in 1) will continue to dispatch onAttachedToWindow() - and will eventually call DigitalClock.onAttachedToWindow() 8) DigitalClock.onAttachedToWindow() registers a receiver that is normally unregistered in onDetachedFromWindow(). But since onDetachedFromWindow was already called in 6), it will not be called again. 9) The receiver has leaked, and it has a reference to DigitalClock, so that will leak as well, together with its parents e.g. PatternUnlockScreen and LockPatternKeyguardView The fix is to wait with the recreation of the screens (in 4) until the loop (in 1) is finished. This is done by posting this as an event instead of calling recreateScreens() immediately. It is possible that this a fix for the root cause mentioned in "Fix 3106227: use WeakReferences for receivers in DigitalClock class" 8b886fab5496b0b1f5193f21855220176deddc37 by Jim Miller <jaggies@google.com>. Change-Id: I6a5f6f49a565d459bf4e285f34f053cc1022286f
| | | * Make the Phone options dialog use current languageAnders Hammar12011-01-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The title of the Phone options dialog is displayed using wrong translation if the user changes the current language setting. Moving the setTitle call to prepareDialog to ensure that the title gets updated before the dialog is shown. Change-Id: I03ff59c7f4ff711a06b05de7cca94fa928cf67ef
| | * | Merge "Fix 3391330: Use BATTERY_STATUS_FULL as "Charged" state [DO NOT ↵Jim Miller2011-01-273-17/+31
| | |\ \ | | | | | | | | | | | | | | | MERGE]" into gingerbread
| | | * | Fix 3391330: Use BATTERY_STATUS_FULL as "Charged" state [DO NOT MERGE]Jim Miller2011-01-273-17/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some devices that use LiPo batteries do not charge them to 100% as a safety margin and to preserve battery longevity. This change allows KeyguardUpdateMonitor to determine when the battery state should be reported as "Charged", provided the device sets BATTERY_STATUS_FULL in that case. Change-Id: Iac6cb78e24f9a696017459cc773c38ef7fe7779f
| | * | | Fix SENSOR_LANDSCAPE and SENSOR_PORTRAIT (DO NOT MERGE)Jeff Brown2011-01-241-2/+4
| | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed a bug in the handling of SENSOR_LANDSCAPE and SENSOR_PORTAIT on devices that have a natural landscape orientation. The old code was disabling 180 degree orientation detection when it shouldn't have. Bug: 3381359 Change-Id: I19bd2519e7f69a24835840fbf542aa7349981029
| * | | DO NOT MERGE: KeyguardManager: Add isKeyguardLocked() and isKeyguardSecure()Mike Lockwood2011-02-261-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | BUG: 3402847 Change-Id: I7cb199763e8d5386914b4c2173c9e1579b08674c Signed-off-by: Mike Lockwood <lockwood@android.com>
| * | | Mass merge from gingerbread - do not mergeThe Android Open Source Project2011-01-305-11/+22
| |\ \ \ | | | | | | | | | | | | | | | Change-Id: I45dc3596bf4211d8f91c64f2d1d00588878df629
| | * \ \ resolved conflicts for merge of 6687ecb4 to honeycomb-mergeJeff Hamilton2011-01-275-11/+22
| | |\ \ \ | | | |/ / | | | | | | | | | | Change-Id: Id9677d2ef1c03191cf73a7d90e80b57ea686afec
* | | | | Merge "Fix issue #3387676 com.android.browser: ↵Dianne Hackborn2011-03-011-42/+59
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | java.lang.NullPointerException..."
| * | | | | Fix issue #3387676 com.android.browser: java.lang.NullPointerException...Dianne Hackborn2011-03-011-42/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Unable to destroy activity {com.android.browser/com.android.browser.BrowserActivity}: java.lang.NullPointerException at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:2809) Add a bunch of guards to not call on to the window callback after the window is destroyed. Change-Id: I66ca0705f421bafdfe953d03654c8f78d9e68249
* | | | | | Merge "Fix 3463772: Bring back alarm icon on LockScreen"Jim Miller2011-03-011-1/+1
|\ \ \ \ \ \
| * | | | | | Fix 3463772: Bring back alarm icon on LockScreenJim Miller2011-03-011-1/+1
| |/ / / / / | | | | | | | | | | | | | | | | | | Change-Id: Icdf948c774d280e22da84e9241b345244a56befd
* | | | | | Fix bug 3497307 - Fix issues with FEATURE_ACTION_MODE_OVERLAYAdam Powell2011-02-281-2/+17
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Properly close down overlay windows when decor is detached. Delay opening popup overlays to prevent issues when restoring instance state. Change-Id: I7ff44ce65e78c0172a12a9ddfe11460c885593ca
* | | | | Add support for mouse hover and scroll wheel.Jeff Brown2011-02-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Dispatch ACTION_HOVER_MOVE and ACTION_SCROLL through the View hierarchy as onGenericTouchEvent. Pointer events dispatched this way are delivered to the view under the pointer. Non-pointer events continue to be delivered to the focused view. Added scroll wheel support to AbsListView, ScrollView, HorizontalScrollView and WebView. Shift+VSCROLL is translated to HSCROLL as appropriate. Added logging of new pointer events in PointerLocationView. Fixed a problem in EventHub when a USB device is removed that resulted in a long stream of ENODEV errors being logged until INotify noticed the device was gone. Note that the new events are not supported by wallpapers at this time because the wallpaper engine only delivers touch events. Make all mouse buttons behave identically. (Effectively we only support one button.) Change-Id: I9ab445ffb63c813fcb07db6693987b02475f3756
* | | | | Fix 3272590: Long-press on home & menu should be same as clickPatrick Dubroy2011-02-242-31/+18
| | | | | | | | | | | | | | | | | | | | Change-Id: I151571900f4bb63910ccfb77fc64c8be9676a224
* | | | | Merge "Rotation lock fix for sensor{Landscape,Portrait} activities."Daniel Sandler2011-02-231-0/+20
|\ \ \ \ \
| * | | | | Rotation lock fix for sensor{Landscape,Portrait} activities.Daniel Sandler2011-02-221-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | E.g. if an app is sensorLandscape and the device rotation is locked to landscape, the activity should not be allowed to flip to seascape even if the device is inverted. If the rotation is locked 90° from the activity's supported orientations, we must override the lock as before, but we now suppress the sensor input (confining the activity to one of its two orientations). This best preserves the spirit of the rotation lock while still allowing the activity to run in a supported configuration. Bug: 3453407 Change-Id: I8ee255e0250ba7e4534f4622ac37b82d31cf9936
* | | | | | Merge "Be more precise about tracking fallback keys."Jeff Brown2011-02-221-1/+7
|\ \ \ \ \ \
| * | | | | | Be more precise about tracking fallback keys.Jeff Brown2011-02-221-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Only initiate fallback key handling if the first key down was not handled and there is no other fallback key already in progress. This prevents spurious fallbacks from being generated when applications handle the initial down but not repeated downs or the up. Change-Id: I8a513896cf96b16dc502cd72291926d5532aa2ab
* | | | | | | Merge "KeyguardManager: Add isKeyguardLocked() and isKeyguardSecure()"Mike Lockwood2011-02-221-0/+11
|\ \ \ \ \ \ \ | |_|/ / / / / |/| | | | | |
| * | | | | | KeyguardManager: Add isKeyguardLocked() and isKeyguardSecure()Mike Lockwood2011-02-181-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BUG: 3402847 Change-Id: I725838c9d96617dd4497f9c80417cd623eceb846 Signed-off-by: Mike Lockwood <lockwood@android.com>
* | | | | | | Fix the flipping orientation lock.Daniel Sandler2011-02-221-6/+15
| |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We were setting ACCELEROMETER_ROTATION to 0 before putting in the proper USER_ROTATION value, and PhoneWindowManager's content observer would eagerly rotate the screen to the last locked orientation before re-rotating to the updated locked rotation. Now we set USER_ROTATION first. Additionally, the content observer is now the only place we set mUserRotation{,Mode} (previously we would race with it in setUserRotationMode()). Bug: 3425657 Change-Id: I04ba1a3631c6d985c2e406c4d148c39fb5c36216
* | | | | | Add new hover move action and scroll wheel plumbing.Jeff Brown2011-02-191-4/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added support for tracking the mouse position even when the mouse button is not pressed. To avoid confusing existing applications, mouse movements are reported using the new ACTION_HOVER_MOVE action when the mouse button is not pressed. Added some more plumbing for the scroll wheel axes. The values are reported to Views but they are not yet handled by the framework. Change-Id: I1706be850d25cf34e5adf880bbed5cc3265cf4b1
* | | | | | Add new axes for joysticks and mouse wheels.Jeff Brown2011-02-191-1/+12
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added API on InputDevice to query the set of axes available. Added API on KeyEvent and MotionEvent to convert keycodes and axes to symbolic name strings for diagnostic purposes. Added API on KeyEvent to query if a given key code is a gamepad button. Added a new "axis" element to key layout files to specify the mapping between raw absolute axis values and motion axis ids. Expanded the axis bitfield to 64bits to allow for future growth. Modified the Makefile for keyboard prebuilts to run the keymap validation tool during the build. Added layouts for two game controllers. Added default actions for game pad button keys. Added more tests. Fixed a bunch of bugs. Change-Id: I73f9166c3b3c5bcf4970845b58088ad467525525
* | | | | Start window manager refactoring.Dianne Hackborn2011-02-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move all of the pieces into a new com.android.server.wm package. Change-Id: I942b7bcfb84ee0f843f47d58e55ffc5a93c0da94
* | | | | Fix 3391330: Use BATTERY_STATUS_FULL as "Charged" stateJim Miller2011-02-152-16/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some devices that use LiPo batteries do not charge them to 100% as a safety margin and to preserve battery longevity. This change allows KeyguardUpdateMonitor to determine when the battery state should be reported as "Charged", provided the device sets BATTERY_STATUS_FULL in that case. Manual merge of Change-Id: Iac6cb78e24f9a696017459cc773c38ef7fe7779f Change-Id: I15c316a17108c064bf2c7e657ca908f8767be936
* | | | | Fix 3409550: Fix crash caused when max pattern attempts met.Jim Miller2011-02-141-2/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a bug introduced by a recent change in GB that fixed a memory leak and subsequent OOM crash. The code in cleanUp() is now more aggressive about releasing unused references because the view is expected to go away afterwards. However, due to the immediate callback from reportFailedUnlockAttempt(), the member variables are cleared before we reach the end of the handler. The fix is to postpone reporting the failed attempt until after the rest of the logic has completed. Change-Id: Ic35eaf17e9921213c8793d00f9008d957a290b88
* | | | | Fix bug 2955651 - can open normal menu during action modesAdam Powell2011-02-101-11/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Prevent the usual menu pipeline from trying to open the action bar overflow menu when the action bar is not visible. Change-Id: I0708d142ad271368baa79351b97aad1533636fe7
* | | | | am 2e4b9985: am 6354dd0b: Merge "Fix 3403858: Remove lock icons from status1 ↵Jim Miller2011-01-281-4/+4
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | area." into honeycomb * commit '2e4b9985dba629eac5662c32a6684fb7b880aeff': Fix 3403858: Remove lock icons from status1 area.
generated by cgit v1.1 at 2025-02-04 18:37:04 +0000