-No more blue, black works throughout all screens
-removed blue line from drop down handle because it was very problematic when a user has several notifications in their scrollview combined with the removal of fadingEdge vertical
-title_bar_shadow has an increased height
Change-Id: I8a291039b9c47c32ce289787612b050fd95e1fc4
PhoneWindowManager now takes full responsibility for deciding where the
navigation bar goes. This gets rid of a bunch of race conditions with
determining layout while the nav bar is moving itself at the same time
the window manager is computing a new configuration.
Note that this breaks the "nav bar on left" option. The current nav
bar code could also be cleaned up some more to completely drive its
behavior based on onSizeChanged() happening during relayout.
Change-Id: I1651d74c3464ba0d588aab3049e099c78420146a
We weren't properly applying the disabled flags from one
orientation to the other. This crops up when the lockscreen
changes the flags and forces a reorientation at the same
time; the other orientation can become stale.
Bug: 5312123
Change-Id: I7cbb7bbf69e6d86cb47450bcdfa692a1f766cd5e
Bug: 5299191
Bug: 5300282
Only send keys when mCode != 0.
Simplified the logic for repeating / non-repeating keys.
Key down / up are always correlated with touch down / up, the
only thing that's special is that we detect long press for
repeating keys and not for others.
Ensure that up or cancel is always sent for every key
that is generated. Previously it was possible for keys to get
stuck down if touch moved out of the button's active area.
Removed the funky HOME long press timer. We don't need it
since we can rely on the long-press flag instead. Since the
system UI is in direct control of key repeating and long-press
behavior for the keys it inject, this eliminates the need for
special hacks to circumvent the timer.
Ensure that the same haptic feedback is provided for all keys,
including the recent apps key. Previously this only worked
because the code was injecting a bogus key with code 0.
Don't generate repeated haptic feedback for virtual keys
even when those keys are injected. This doesn't happen
for virtual keys synthesized by the InputReader because it
never injects repeats itself (the InputDispatcher synthesizes
them), but it is an issue for the KeyButtonView.
Change-Id: I8b3615dde738af28e76898d161d6ce9a883b59ec
We were carefully tracking the vertical offset between the view
origin and the user's incident touch, but not actually
including it when performing a fling. (This might have
worked at one point but been later buried under some
refactoring rubble.)
Bug: 5210198
Change-Id: I97ae883491a5dedf1b48683441096fe9938d118f
- Making thumbnails invisible until loaded (fixes regression)
- Speed up dismiss animation from menu
- Make the max swipe velocity greater
- Make only the thumbnail and app title long-clickable
- No more click sound when tapping outside the thumbnails to dismiss Recents
- Tweaking color of recents app label text
Change-Id: If7b6cd59e92feb0472eb3ea266733549cb9f4d4b
Bug: 5198231
Widgets always need to handle ACTION_CANCEL properly since
it can happen at any time, such as when the screen is turned
off or the screen is rotated, removed or reconfigured.
Change-Id: Ia30b14bb6f68cdde5286b4d72e69130e9fb38732
A core app is one that has coreApp="true" in its manifest tag.
The system can successfully boot (though a little painfully) with
only framework-res.apk, SettingsProvider.apk, SystemUI.apk,
DefaultContainerService.apk, and Launcher2.apk set as core apps.
Currently this boot mode is always turned off.
Change-Id: Ieaa4a8031c2c391a12996aa8d8b1d65fc2b09d6b
Back is hidden by DISABLE_BACK; Home, Recents, and Menu are
hidden by DISABLE_NAVIGATION.
Bug: 5261576
Bug: 5284740 (confusion about visible inactive icons)
Change-Id: I410c133b737cc11d61bac0318dc24458353ee7b3
(This only works if the keyguard is not secure, but then
again, the user can't access the notification panel in that
case anyway.)
Bug: 5173952
Change-Id: I8a6081d26c52843822b381d8ebe0fae94a03bef9
We were missing a case statement for HSPAP when picking icons.
Treat it the same as the other HSPA types.
bug: 5286238
Change-Id: Ia222cc600a5920e057698ba8b0d2cc8e4836b500
-added padding to portrait and landscape layout recent item
-updated drawable stroke on press and drag
Change-Id: I98e0073f5fba6d13f041871337e4dc534bbc1460
It was possible for a device to be configured to use a navigation bar
(by setting config_showNavigationBar to true in a config.xml file)
and to use a system bar (by being a tablet device of sufficient size).
The display metrics would be set up for both, but the SystemUI would ignore
the navigation bar, leading to conflict in what would be displayed and how
much room there was on the display. This change throws an exception,
causing SystemUI to fail, when this conflict is detected.
Change-Id: Ib5c19d50ff9444bc33fd53d3dcfa016adc4872ef
This also refreshes the data type icon when the data
connection state changes, so it'll pick up network speed
changes (3G->4G, e.g.) that aren't accompanied by some other
radio state change.
Bug: 5278165
Bug: 5274807
Change-Id: Ic97252a9fb29bd3f2a927f6a57666809297ad60e
Touching StatusBar.disable() directly can make the cached value over
in StatusBarManagerService stale. Instead, dispatch DISABLE_BACK
through setSystemUiVisibility() on tablets; it's unused on phones.
Also DISABLE_NOTIFICATION_TICKER when showing secure lockscreen, and
watch for TIME_CHANGED in DateView.
Bug: 5255469
Bug: 5242677
Change-Id: I4efaf9799b2f229f49d7024da5dafceacd5e08bb
(Only applies to high-end devices. In situations where
memory budget or GPU/overlay support are lacking these will
still be done in software.)
Bug: 5233443
Change-Id: I668def10598f6a818d8011ba6dd8d1dd5440ae5e
-Increased quicksettings and clearall inherent asset padding to 32 from 16dp
-new touchstates for quicksettings and clearall
-clear all remains on the right and quicksettings remains left aligned to the right of the date
Bug: 5076789
Change-Id: I45d7da2d79b94822c04aa162ebef99ac79ce0368
