| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I1be0be2753b479e6d2e4fc8e17d971d03ce01bb7
|
|
|
|
|
|
|
|
| |
- Collapse after dismissing the last notification
- Avoid duplicate code paths for collapsing
- Improve variable naming according to AOSP review suggestions
Change-Id: Ic6f26a61f263c5beebbcc9725fe8914d3858576f
|
|
|
|
|
|
| |
Use the same value as when removing all notifications.
Change-Id: Id11a48bc47487fd7763503dcbc769d9dbf5ad16a
|
|
|
|
|
|
|
|
| |
This commit adds multi user support for pie controls:
* React on user changes
* Respect per user expanded desktop settings
Change-Id: I513b00f2745f309bf21b971f96276da40003b224
|
|
|
|
| |
Change-Id: I0e434b989c16f5871ce56c7e3041ff3c7a436c73
|
|
|
|
|
|
| |
notification.
Change-Id: I4e5114f66e799a7c80e18b38abce5678da460846
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on "Pie controls: Introducing a pie delivery service" this
commit binds the pie controls to the newly created pie service.
Patch Set #2:
* Fixed glitch when displaying the search panel at the lock
screen.
Patch Set #5:
* Switch Position to com.android.internal.util.pie.Position
* Removed legacy and unused code
Patch Set #6:
* Fixed lock screen glitch, finally!
Patch Set #7:
* Rebase
Patch Set #9:
* Moved almost all of the pie logic to PieController
Patch Set #10:
* Remove window completely from WindowManager when not shown
Patch Set #13:
* Fixed Taichi's bug
* Removed observers in PieView
Patch Set #14 & #15:
* Rebase
Change-Id: I352f198068807694d95699618597d0927da3f324
|
|
|
|
|
|
|
|
|
|
|
| |
as the title says do not show on lockscreen or notification
drawer the snappoints on the disabled edges. Pass
trigger slots and mask trough and take into account
PatchSet 2:
- some refactoring
Change-Id: I0413ffe86169c5d1cb906598d6006bbf1463770b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on high end devices that is maybe not needed. But there
is in general no need to enable the obeserver/receiver
when PIE is disabled (or expanded mode is off)
This change destroy and disables the PIE in most parts
when it is disabled. + a small doubel register
correction
greetings SlimRoms
PatchSet 2:
- remove PieLayout observer completly - thanks Jens
PatchSet 3:
- remove unnecessary call to setupSnapPoints()
- reuse already created snap points
PatchSet 4:
- small corrections on setupSnapPoints() and call
- remove not needed second call of PieController attachTo()
- disable TelephonyManager listener
PatchSet 5:
- fix up detach logic
PatchSet 7:
- cleanup
PatchSet 8:
- Effective Java rule #41
- fixed some pie controller leak
Change-Id: I8ef8797e7d4f8ee73d31a8296f5747415567bbda
|
|
|
|
|
|
|
|
|
|
|
| |
exitKeyguardSecurely() will open the keyguard if it's currently disabled
by an app. As this is unwanted here (the user has either already
bypassed the keyguard or the keyguard isn't secure; otherwise he
couldn't click on a notification entry) and as the lockscreen already is
dismissed a few lines above, don't call exitKeyguardSecurely here.
Change-Id: I5582da350d8826e42f9edcd56845a59965865c8b
JIRA:CYAN-99
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on the commit series for pie controls, this commit
makes the Navigation Bar and Pie Controls share
the same button layout. However, there is no button layout
editor for pie controls, which makes the navigation bar
the leading entity when it comes to button layouts.
This commit introduces:
* A common notion of navigation buttons used in CyanogenMod.
(class NavigationButtons)
* Some setting constants changes to avoid clashes with PA.
* Removal of the pie search key, since it is no longer needed.
* Sophisticated key event injection.
* Virtual key sound effect
Change-Id: Id68f8d0b597d7d89c55c3f66f994e632d014f006
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some launchers have gestures for expanding/collapsing the status bar
from swipe gestures which call the respective StatusBarService methods
even if the status bar isn't visible due to expanded desktop. Because of
that, the status bar code internally thinks the expansion is carried out
(even if invisible), thus disabling the bottom pie controls in the
process.
Fix that by making PhoneStatusBar aware of it being hidden by expanded
desktop and ignoring the expand call in that case.
Change-Id: If386ca953517d9b5efcb6cb9054f5c5e6a9e0bc4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit brings some pie control tweaks to the Phone UI. These
tweaks make the pie controls react to several conditions that are
are special to the Phone UI. That means that this piece of code
is more deeply embedded within the SystemUI code.
This mostly adds the foloowing behaviour, that is Phone UI
dependent:
* Disable BOTTOM trigger when notification area is expanded
* Disable LEFT and RIGHT trigger when a keyguard is active
* Enable search light feature
Patch Set 3:
* CyanogenMod Code Style.
* setDisabledFlags now belongs to navigation bar callbacks
Patch Set 5:
* Removed duplicated .observe()
Patch Set 10:
* Fixed unintended trigger activation
Patch Set 13:
* Searchlight opens directly on the bottom (on the lock screen)
Patch Set 15:
* Fix conflict/rebase
Change-Id: I551745b69791adca75190c54282be19d85db75a9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on the multiple navigation key bar patch, this commit adds
basic pie controls to CyanogenMod. The implementation is inspired
by Paranoid Android but is completely rewritten.
The aim was to get as little intersection with existing code as
possible and provide a farily easy interface to extent these
controls by new slices (inherited from PieSlice).
The pie controls are only active when expanded screen is turned on.
Based on this commit there is another one that adds more optimizations
for Phone UI to pie controls. And there is a seperate commit for
the settings app, too.
Patch Set 2:
* Cyanogen Code Style.
* Some simplifications in PieSysInfo.java
Patch Set 3:
* Fixed NPE when pie controls are completely deactivated
* Preserve state of menu button
Patch Set 4:
* Fix display of Wifi SSID
* Some cleanup and coding style changes
Patch Set 5:
* Fix NPE when not connected to Wifi
* Remove AM/PM from time display (overlayed the other info)
* Fix menu button handling
Patch Set 6:
* Remove trailing whitespace in 12 hour time format
Patch Set 7:
* Tune colors
* Improve battery level and operator printout
* Remove some unused imports
Patch Set 8:
* Some refactoring on pie trigger management
* Copyright fix
* Make debug on PieLayout less noisy
Patch Set 9:
* Fix NPE one devices with no GSM/CDMA/LTE
* New color proposal
* Haptic feedback now respects system setting
Patch Set 10:
* Factor out haptic feedback into separate method
Patch Set 11:
* Prepare for "always on"
* David's color scheme
Change-Id: I90de7252d8301282d396c29bc9e9943acf7f2766
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
System UI was build with the assumption that there is only one
navigation bar at a time, and that this bar is managed by
Phone UI, Tablet UI or TV UI.
This commit adds simple call back facilities at BaseStatusBar
for both, navigation key hints and menu key visibility change
events. These call backs are wired up in Phone UI, Tablet UI
and the TV UI stub.
This allows us to have more than on navigation key bar
in the UI and define those navigation bars directly
in BaseStatusBar, where it is available for all UIs.
Patch Set 2:
* CyanogenMod Code Style
* Added documentation.
* One interface for all
* Added setDisabledFlags() to the list
Change-Id: Id4de440e21c2f5c78b5e185030f9c5e0f7e6bef7
|
|
|
|
|
|
|
|
|
|
| |
This allows up to 3 targets on the Navigation bar ring
or Home buttons with custom Quick launch shortcut actions.
Patchset 1 - 21 - Initial commits and edits
Patchset 22 - Update commit message
Change-Id: Ic5bc6021d55b9c266527463bb916283feb00ad06
|
|
|
|
|
|
|
| |
Patch Set 1: Signal / Clock / Battery / Notification Count
Patch Set 2: Updated commit message
Change-Id: Iecd4bb06b95b14888916331f5d36327f3206aeef
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated 4.2 support for the old T-Mobile theme engine, as usual
needs the provider and switcher apps installed as well.
I'm finally dropping the 400+ commit history on this, since everybody
else keeps picking it up from CM as a single patch anyway... But
for the record, nothing of this would be possible without Josh, Ed,
and the rest of the TMo guys who wrote and maintained it until 2.2:
amit chabra <amit.chabra@t-mobile.com>
Amit Kohli <amit.kohli@t-mobile.com>
Chris Cogar <chriscogar@t-mobile.com>
Dirk Sigurdson <dirk.sigurdson@t-mobile.com>
Ed Carrigan <edward.carrigan@t-mobile.com>
Gaurav Sharma <gaurav.sharma3@t-mobile.com>
Hui Feng <hui.feng@t-mobile.com>
John Ritz <john.ritz1@t-mobile.com>
Josh Guilfoyle <josh.guilfoyle@t-mobile.com>
Mark Roberts <mark.roberts48@t-mobile.com>
Pankaj Kumar <Pankaj.kumar6@t-mobile.com>
Samuel Cheung <samuel.cheung@t-mobile.com>
Sergey Ten <sergey.ten6@t-mobile.com>
Change-Id: I7148d51be48f28a2dc4bdf9ec9018f04b268ffc4
|
|
|
|
|
| |
Fixes regression introduced by:
738cfc91053fc888397ec2d139e0798f8c95b3ca
(Fixing wallpaper flash when going in/out of Recents)
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Bug: 7372516
Bug: 7216872
Change-Id: I2a2308a85caf9f2ad2d382c709e5f8867bd060be
|
|/
|
|
|
| |
Bug: 7361640
Change-Id: Ibd177bf01758fb8706b82dcf3bf234e052c38aa3
|
|
|
|
|
| |
Bug: 7282784
Change-Id: I686f8f0e36e3414ad30d23de80cbbfb2868069d4
|
|
|
|
|
| |
Change-Id: I377c389abe3ce2285a620e60f4c8de4727f4f5c9
Bug: 7229886
|
|
|
|
|
|
|
| |
Add animation where icon and description of the
primary activity fades and translates in
Change-Id: Ie21b5302ac9e58ee6af219b7cde98d12a8e82697
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
IStatusBarService.collapseQuickSettings is gone;
collapseNotifications is now collapsePanels, which does what
collapse() used to do. Similarly,
IStatusBar.animateCollapseQuickSettings is now simply
IStatusBar.animateCollapse().
Bug: 7245229
Change-Id: Id157d2fdf34926d3c85ffa8b81c741a5359aede4
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Various per-user settings such as rotation lock are relevant to the
singleton PhoneWindowManager object. We now listen for user-switch
broadcasts and reconfigure the active state based on the newly-
active user's settings.
The RotationPolicy toolset has also been updated to do the right
thing, as has the Quick Settings UI.
Bug 7213638
Change-Id: Iee2109e48df550b4c979d3f9c91b5d2b71a6a08e
|
|\
| |
| |
| |
| |
| | |
* changes:
Update references to migrated global settings.
Handle user switched for settings changes.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixed one setting that was migrated but not marked deprecated.
Removed a hidden setting that is no longer used by the new
power manager service.
Bug: 7231172
Change-Id: I332f020f876a18d519a1a20598a172f1c98036f7
|
|\ \
| | |
| | |
| | | |
jb-mr1-dev
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1. Added APIs for opening the quick settings to the StatusBarManagerService
and the local StatausBarManager. The new APIs are protected by the old
EXPAND_STATUS_BAR permission.
Renamed the expand* and collapse* non-public APIs that are expanding
the notifications to expandNotifications* collapseNotifications* to
better convey what they do given that this change adds
expandQuickSettings* and collapseQuickSettings*.
Added a global action to the accessibility layer to expand the quick
settings which is calling into the new status bar manager APIs.
bug:7030487
Change-Id: Ic7b46e1a132f1c0d71355f18e7c5a9a2424171c3
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
For apps that are only installed on secondary users, the SystemUI is
unable to see them by default. Added some methods to explicitly pass the
userId of the user the resources are requested for by the StatusBarIcon
Bug: 7214384
Also fix binding to remote views
Bug: 7192802
Change-Id: I5d6c5f624aa37fb231f3467f9764c8d99077a91d
|
|\
| |
| |
| | |
Change-Id: Ifc2328e30a52c2baebc1322c9b161104dcf21618
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Required wiring up startActivitiesAsUser()
Bug: 7224950
Also fix a bug in navigateUp in secondary user
Change-Id: I114ae2de0457362d62e899fdb94b12239a3eb778
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- As current user
- Dismissing keyguard if necessary
- Dismissing all status bar windows and panels
Also move some QS-specific stuff out of PanelView and into
SettingsPanelView.
Bug: 7217006
Change-Id: I4d8ac84cc0f43e78f70553599c3207305c4f5c74
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also fix a bunch of system services that should be doing this. And
while doing that, found I needed to fix PendingIntent to evaluate
USER_CURRENT at the point of sending, not creation.
Note that this may end up with us having some notification shown to
non-primary users that lead to settings UI that should only be for
the primary user (such as the vpn notification). I'm not sure what
to do about this, maybe we need a different UI to come up there or
something, but showing the actual notification for those users at
least seems less broken than not telling them at all.
Change-Id: Iffc51e2d7c847e3d05064d292ab93937646a1ab7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code in onMeasure that attempts to accommodate changing
child boundaries (i.e. an expanding/collapsing notification)
was locking the window size to the child measurement, even
though another window was trying to seesaw it closed. We now
only activate the rubberband behavior when the size of the
children changes, not on each onMeasure().
Lots of other small fixes to the panel expansion logic, too,
including ensuring that the expanded fraction doesn't jump
to 1.0f when the panel content hasn't been laid out yet
(causing the entire screen to become dim for a second thanks
to PhoneStatusBarView.panelExpansionChanged).
This change also restores the ability of Binder clients
(such as accessibility systems) to expand and collapse the
status bar.
Bug: 7008196
Bug: 6995518
Bug: 6628429
Change-Id: Ib0244a27aef2b4dbe19be98f7e039a9d38f1b80e
|
|
|
|
|
|
|
|
| |
We should only update the notification ticker area when
the notification is for the current user.
Bug:6924835
Change-Id: Ieaccbd8c972b3d0f62c74d29d42e0fa77ec3148c
|
|
|
|
|
|
| |
- Fixed for tablets and phones with hard nav buttons
Change-Id: I1dc2249376b3f376c283598f5cef6e326b191ace
|
|
|
|
|
|
|
|
|
|
| |
https://b.corp.google.com/7060284
- Throw exception before we try to start window
transition with null thumb
- also remove some old unneeded debug code
Change-Id: Ic9693372724cbfaa4c4cb2594128ca10677d9d8f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As a part of this change, Recents is now an
activity.
Known issues:
* Jank: jump-cut as app icon appears suddenly
after the aniamtion
* Preloading recents is broken on phones without
soft nav bar and on tablets
* Thumbnail window from animation lingers/flashes
sometimes
Change-Id: Ie6f991f3c2e1e67f9ed84eb6adba9174ed957248
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Split WindowManagerImpl into two parts, the WindowManager
interface implementation remains where it is but the global
communications with the window manager are now handled by
the WindowManagerGlobal class. This change greatly simplifies
the challenge of having separate WindowManager instances
for each Context.
Removed WindowManagerImpl.getDefault(). This represents the
bulk of this change. Most of the usages of this method were
either to perform global functions (now handled by WindowManagerGlobal)
or to obtain the default display (now handled by DisplayManager).
Explicitly associate each new window with a display and make
the Display object available to the View hierarchy.
Add stubs for some new display manager API features.
Start to split apart the concepts of display id and layer stack.
since they operate at different layers of abstraction.
While it's true that each logical display uniquely corresponds to a
surface flinger layer stack, it is not necessarily the case that
they must use the same ids. Added Display.getLayerStack()
and started using it in places where it was relatively easy to do.
Change-Id: I29ed909114dec86807c4d3a5059c3fa0358bea61
|
|
|
|
|
|
|
|
|
| |
Use AtomicFile for usermanager files.
Added a MANAGE_USERS permission that apps (signature permission) can use
to create/query/modify/remove users.
Change-Id: I5cf232232d0539e7508df8ec9b216e29c2351cd9
|
|
|
|
|
|
| |
This is the start of turning this into a formal public API.
Change-Id: I5786d2c320f1de41a06ed5d0f65adb68967287a0
|
|
|
|
|
|
|
|
|
|
|
|
| |
Notifications for background users are hidden from the
panel and status bar.
Still need to add a concept of "any user" notifications (for
things coming from the system) and notification visibility
controls (for access to icons + possibly masked text of
a background user's notifications).
Change-Id: Iba121f35a6c25c2e1c44db029d776a5a59a6a008
|
|
|
|
|
| |
Bug: 6538918
Change-Id: Ie4e79aa593ac2097d0e6402f84816df934160687
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For activities with a null taskAffinity, simply finish the current task.
(They probably shouldn't have specified a parentActivityName anyway.)
When launching into app info from ResolverActivity, launch the app info
page in the current task with FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET. Back
will return to the resolver, and Up will jump to Settings.
When launching into app info from RecentsPanelView or BaseStatusBar,
since this is a system affordance akin to notifications or widgets,
build the full task stack for the app info activity with
TaskStackBuilder and launch it as a new task.
Change-Id: I73b1941d0f52bd8b30382b5e17edd8ceb058c70d
|
|\
| |
| |
| |
| |
| |
| | |
not defocusing the shade" into jb-dev
* commit '4be93bbe911c1a4471f81f0e261e9b13d9212c36':
Maybe fix issue #6756472: Share button is not defocusing the shade
|