| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
...opening after selecting option "Youtube" as a luncher.
Also:
* Tweak window animations so that the wallpaper exist animations do not
stop too early (causing the wallpaper to suddenly disappear).
* Make sure no input is being processed while booting, to avoid
accidentally doing things especially in the upgrade dialog.
* Some other small cleanup.
Change-Id: I40a6b53731991d4e31ac4502e3d85f0e47507481
|
|/
|
|
|
|
|
|
|
|
|
|
| |
When the lockscreen is up we still enable the home and recent app buttons,
but the back button is only enabled if the lockscreen is not obscured by other activities
Fixes problem escaping from the DeskClock app when the screen is locked.
Bug: 5206013
Change-Id: I68c9e4513018f51e2ee4fc11254e42ecbef834e4
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|
|
|
|
|
| |
Gets rid of gapps between windows during animations.
Change-Id: I17d2ef0af214008f0eabd7eb19268f145fe83b39
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 5156144
Input channels could leak or simply live longer than they should
in some cases.
1. Monitor channels (used by the pointer location overlay) are never
unregistered, so they would leak.
Added code to handle failures in the receive callback by closing
the input channel.
2. The DragState held onto its input window and application handles
even after the input channel was disposed.
Added code to null these handles out when they are no longer needed.
3. Input channels previously used as input event targets would stick
around until the targets were cleared (usually on the next
event).
Added code to detect when the input dispatcher is in
an idle state and to proactively clear the targets then
to ensure that resources are released promptly.
4. Native input window handles held onto the input channel even
after the input window was removed from the input dispatcher.
Consequently, the input channel would not be disposed until
the input window handle itself was freed. Since the input
window handle is held from managed code, this meant that the
window's input channel could stick around until the next GC.
Refactored the input window handle to separate the properties
(info) and identify (handle) state into different objects.
Then modified the dispatcher to release the properties (info)
when no longer needed, including the input channel.
7. The pointer location overlay does not actually use its
standard input channel, only the monitor input channel.
Added INPUT_FEATURE_NO_INPUT_CHANNEL to allow windows to
request that they not be provided with an input channel
at all.
Improved some of the error handling logic to emit the status
code as part of the exception message.
Change-Id: I01988d4391a70c6678c8b0e936ca051af680b1a5
|
| |
| |
| |
| |
| |
| |
| |
| | |
When showing lockscreen, hide clock and navigation. Clean up logic
to be easier to understand.
Bug: 5112812
Change-Id: I20e3563aa36644db678c7839d47f01f223fe8d37
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This integrates a new version of TransportControlView into LockScreen
and adds plumbing to handle new AudioService events to show/hide the view
and updates the required assets for all devices.
Updated to use new AudioManager API. Since the current API only supports
one RCD, the handler now lives in TransportControlView.
Change-Id: I220d4dd760bef35bd84209adc3c5829bf5bc9a2c
|
|/
|
|
|
|
|
|
|
| |
On devices that do not require showing lock before unlock, we now only create
just the unlock screen. In addition to simplifying the code, this also
prevents keeping around a potentially unusued lock screen and saves ~1MB
in the system process on devices with only a secure lockscreen.
Change-Id: I533f2692b44a7991d4850cecc874c76166e7ce71
|
|
|
|
|
|
|
| |
Don't try to "close" the menu after completing a shortcut action if an
action bar is present.
Change-Id: I54a75543cf9a52e3186ff464924a0b37d0b20b9d
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Since LockScreen provides its own PIN entry keyboard, we don't need to show
the IME switcher button.
Change-Id: I04528acaee66e5109d631c0c79a3e7c64876e4c5
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1. The lock screen goes off after a certain timeout but a blind
user performing touch exploration of that screen needs more
time to find controls and interact with them. Therfore, we
reset the lock timeout by poking the wake lock on the last
hover event so the lock timeout will start ticking after
the user has stopped interacting with the lock screen.
bug:5133879
Change-Id: I340d2a820e90f6fd63a45d65a5457ce6e570189c
|
|/
|
|
|
|
| |
Change-Id: Iff2cfec5280a314989d915aa830c16124f921611
5214105: taking a screenshot while "Android is upgrading..." crashes device
5109947: Race condition between retrieving a content provider and updating its oom adj
|
|
|
|
|
|
|
|
|
|
| |
...(when turning display on after recently turning it off)
Also clean up when we decide to turn the screen on to improve that
transition. There are still problems here with turning it on
before the wallpaper gets dispayed.
Change-Id: I2bc56c12e5ad75a1ce5a0546f43a845bf0823e66
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
targetSdk < ICS
Compatibility support for existing apps. Apps in the wild that
properly target <=GB phones and HC tablets should be able to expect
that their small-screen UI will continue to work as intended on ICS
devices. Make sure that we show the soft menu button in the nav bar if
the current device was not officially supported in Honeycomb, the app
does not target ICS or newer, and the window does not have an action
bar.
Change-Id: I069c30841d3827a60ef8040831fde6f4c051d0ee
|
|
|
|
|
| |
Bug: 5185650
Change-Id: I56541d4967b90b150a734be1bbeff696eb6a4fb3
|
|
|
|
|
|
|
|
|
|
| |
This introduces a new facility for code during the boot process
to display messages to the user through a progress dialog. This
is only for use when performing longer-than-usual post-upgrade
operations such as running dexopt on applications or upgrading
databases.
Change-Id: I0e78439ccec3850fb67872c22f235bf12a158dae
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this change, we didn't have a mechanism to warn the user when
they were approaching the wipe data threshold dictated by active DPMs.
Here's the new flow:
- If a device policy manager is installed and sets the max
password attempts, we start warning the user when they are within
a grace period of hitting the max (currently hard-wired to 5).
- We continue to show a dialog after each continued attempt
until the user reaches 0 remaining attempts.
- We now show a message when they hit 0 so they know why their device is
being reset. The device will reboot and wipe data shortly after this final
dialog is shown.
Also increased the criteria for a pattern attempt from 3 dots to 4 dots
since the user can never set a pattern less than 4 in length. This will
greatly reduce the likelihood of a false wipe on the pattern unlock screens
without compromising security.
Change-Id: I28825ef21dfa2e2b6540e743252c6d50c41e5ad7
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This adds an IME switcher button to lock screen. It is only
shown if the user has more than one applicable and enabled IME installed.
Change-Id: I5f9503a205c2edb27170825539ba4a6ef25418ed
|
| |
| |
| |
| |
| |
| | |
Locking good. Races bad.
Change-Id: I59dd0ec2de47973c38fd646c2f441dd174eba444
|
|\ \
| |/
|/|
| | |
views in the MATCH_PARENT case"
|
| |
| |
| |
| |
| |
| | |
views in the MATCH_PARENT case
Change-Id: I11c4a58303fa3c4a9f3540908c6409bacd84a35e
|
|/
|
|
|
|
|
|
| |
This adds a slight delay before the first ping animation runs. The
idea is to ensure enough time for the display to come on and the user
to notice the animation.
Change-Id: I3d981f5d50efa14683bb08cf6a1430244ce67e55
|
|
|
|
| |
Change-Id: I15beb7b55ff5809b95dc869a9b0c43c49d1571c6
|
|
|
|
|
|
|
|
|
| |
The codepath that honored this flag had been routed around
when notification peeks were disabled. (The bug was allowing
notifications to be accessed from a secure lockscreen.)
Bug: 5173959
Change-Id: I35dee343ee4f0288530580054f8bb9f511ebe6af
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We now do the screenshot in a separate process.
Also change the recents panel to not use hardware acceleration
on lower-end devices. And improve how it gets shown to not
load all data up-front which results in a long delay when you have
lots of recents.
Change-Id: Ia309a90f9939e5405758621b3f7114597bd0c02a
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
Don't open the options menu in response to the menu key when an action
mode is active.
Change-Id: I89cd251dd14276fc381e20f82725d42ac9264181
|
|/
|
|
| |
Change-Id: Ife3ca80f593c141f680fcc5178687112a538474d
|
|
|
|
|
|
| |
menu
Change-Id: If28630cb21e74bde7a2474ce060078ea30170b9d
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
When the native orientation of the device is not landscape HDMI display
will be wrong.
Change-Id: Ie1d4f6b7247e0a43ff13b5318b644ec7cff293f2
Signed-off-by: Erik Gilling <konkers@android.com>
|
| |
| |
| |
| | |
Change-Id: I36aaff982767f8984c468e8c13f8d5ec8c3c0040
|
|/
|
|
| |
Change-Id: Ie71a8043eafe41f53a0b3dbb5170276d87acbc9b
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This saves about 8MB in the system process because we don't need
to do HW accelerated drawing there anymore.
Change-Id: Ieaf72fe772536e12d10cf129d9338ca9fce6a6d4
|
|/
|
|
|
|
|
| |
(Broken implementation appeared in change I967e455.)
Bug: 5158885
Change-Id: I0e22c269ff76d19bcdd5e51e1722e34fdc025dfa
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Its region is now treated like the system bar: inaccessible
to applications and therefore not worth reporting as part of
the display.
(Note that using setSystemUiVisibility you can gain
temporary access to the navigation bar region, unlike the
sempiternal system bar.)
The navigation bar is now considerably less in control of
its own behavior (the window manager assumes it will be a
certain size and in a certain position in landscape and
portrait). This change also fixes the navbar so that it
becomes GONE instead of merely INVISIBLE (allowing
underlying windows to expand in size accordingly).
Bug: 5052456 // the feature
Bug: 5067627 // notification shade falling behind the navbar
Bug: 4959805 // fix third-party apps relying on DisplayMetrics
Change-Id: I60257fc5c858e0edcaba8cfc1f8d58dd99a68258
|
|/
|
|
|
|
|
|
|
|
|
| |
The special touch target and fancy animations (see bug
5052059) aren't there yet; we'll probably need a different
flavor of DISABLE_EXPAND to specify that state. But this is
a start and should get the basic feature into testers'
hands.
Bug: 5052059
Change-Id: I967e4557e467d1762d6566643bb401eb84f94e92
|
|
|
|
|
|
|
|
|
|
|
| |
onPrepareOptionsMenu will be lost
Change the ordering of restoring action views. Restoration now comes
after onCreate but before onPrepare in the menu setup rather than
after both. This allows apps to mutate the restored state in
onPrepare.
Change-Id: I822a716415d01112eb517ac093eaf6929f041aad
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The new Holo-style overflow menu now appears from the edge of the screen
where the device's physical menu key can be found. The policy determining
this lives in getPreferredOptionsPanelGravity() in WindowManagerService.
Change-Id: I8851a2265547156591e82044e50b5cfc58d3eefa
|
|/
|
|
| |
Change-Id: Iefa103e867e870dfe587271e0555404589d9e5b3
|
|\ |
|
| |
| |
| |
| | |
Change-Id: If870760f7dcafe02084af4c82db7dbb809c31c75
|