| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
texture size." into cm-10.1
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes an issue where OpenGL initialization succeeds but buffer allocation fails because the requested wallpaper size
is too large (or otherwise unsupported) by the graphics hardware. This fixes an issue where SystemUI crashes constantly
on the PandaBoard when connected to a full HD display. Tested only on PandaBoard, no access to alternative hardware.
Signed-off-by: Wim Vander Schelden <wim.vander.schelden@philips.com>
Change-Id: I8d2e1ae9fd9772977c4e365f23f2f58bbca3787c
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I624663149da1161c2cd4f4b20b388bd711d9883c
|
|/ /
| |
| |
| |
| | |
Change-Id: Ide0417768350081250af24518b6831d70196ba73
JIRA:CYAN-1189
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Battery tile upon being added relies on a battery level changed call
to update its status. Thus if upon adding, the battery level is not changing
or till the period when it updates, the tile shows an unknown state.
This patchset resolves this issue by making the controller store its last received value
and distributing it to the tiles when they register for changes.
https://jira.cyanogenmod.org/browse/CYAN-1374
Change-Id: Ia2e887e545430ed02c179a3c8f4b7e269a4817c8
|
|
|
|
|
|
|
|
|
|
|
| |
Commit "Merge Navigation Bar and Pie Controls button config (1/2)"
changed the tag field on the navigation bar buttons. This was not
reflected in NavigationBarView#dump() method, which lead to a NPE.
Also take into account that back and recents buttons may not be
present in the navigation bar.
Change-Id: Ie590608a4ad27753b673320132af7ec42d7a2ade
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit f6685c5ca84a42f5a47bf40827d6229dd998dee4 fixed this for the
two-finger pulldown. It reverted commit
c5e8dca7f11d3c085dd1e98692fcc21f1bcc0f6f in the process, which was
incorrect, but fixed another condition of this problem occuring
nevertheless. The actual problem the latter fix tried to fix was that
the flip decision was dependant on the timing of the view layout:
getMeasuredHeight() returned whatever was set in the last layout, which
might not have happened when hiding the view, so at the time of the next
ACTION_DOWN getMeasuredHeight() returned the height from the time the
panel was last visible.
Fix that problem by using the height scheduled for the next layout, so
we're always up-to-date.
Change-Id: Ib97f34f9aa0a6f28d48b4ec3e16c82a814cda0d0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
settings with two fingers.
Commit c5e8dca7f11d3c085dd1e98692fcc21f1bcc0f6f already tried to fix
this before, but was incomplete (and incorrect). The actual issue is
that on the first pointer down event, a 'peek' animation runs and
expands the notification panel by some pixels (on mako: 160). This
amount of pixels is significantly larger than the handle height (on
mako: 72). Depending on the timing between peek animation and the second
pointer down event, the flip animation would play (if animation already
revealed more than 72 pixels) or not.
Fix that by not playing the flip animation if only peeking, as the
actual panel content is not visible at that point anyway. Also remove
the previous incomplete fix in the process.
Change-Id: I8997dc7b70143940a519f41da29ffd4d738d8d0c
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As stated before there are still corner cases that may
deadlock pie controls.
This commit makes PieInputFilter respect ACTION_CANCEL,
simplifies monitoring mechanics in PieService and
fixes some corner cases in PieController that allowed that
activations got lost and thus pie controls got stuck.
Test case for PieController:
1) Enable pie controls
2) Enable top/bottom snap position for pie
2) Enable expanded desktop and check if it works
3) Disable expanded desktop
4) Lock your phone
5) Swipe from the top down/bottom up, as if you want to
activate the pie from that position
6) Dismiss the notification tray and unlock your phone
again
7) Enable extpanded desktop
8) Pie controls will no longer show up and
"dumpsys pieservice" will show a active record.
Change-Id: Id9d2df6b2735a743eec2fd1ba809fd72be9474cc
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On rare occasions the pie service will deadlock. When this
happens, full screen mode can no longer hide the
navigation bar, since it is masked out internally.
This commit switchs from a self cooked mask mechanism within
the WindowManager to the private flag
WindowManager.LayoutParams.PRIVATE_FLAG_FORCE_SHOW_NAV_BAR.
Note that this will avoid flickering when pie service get
stuck in the activation path, but it will not resolve the
deadlock.
Change-Id: I2b64867081b37d9d6070df8086975e4327d97f5d
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
onAttachToWindow() is not guaranteed to be called prior to the framework
invoking commands on the panel. This patchset moves over initialization
over to onFinishInflate();
Reproduction steps :
1. Activate search panel view (long press home/swipe up from navbar)
2. Rotate device
Change-Id: I37b5b0de180040bdf1b521bcb8fc014b23c238df
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add broadcast to indicate profile changes that does not
cause a profile to be selected.
Use the new broadcast to update the Profile Tile more
reliably.
Currently the tile update is triggered by a profile
selection. However, the active profile may change without
triggering a selection. This happens, for instance, on
locale changes.
The Profile Tile does handle locale changes, but is subject
to a race condition. If it handles the locale change before
the profile manager does, the name change will not be seen.
Change-Id: I193454f5100f1ae04dd24d50f25e75ec961f4d68
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With the introduction of pie service there is the need to
fine tune the parameters for activation again.
Patch Set #2:
* Base trigger thickness set to 10dp
* User settable activation sensitivity
Patch Set #4:
* Reverted #setSensitivity() in PieGestureTracker
* Added Sensitivity "Very High"
Change-Id: Ief7c1786467195f2ad52dcdb0efd3ad03a48834c
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, for each status bar icon view there is a observer that
listens for changes of STATUS_BAR_NOTIF_COUNT. With one
notification usually having one or more status bar icons
you may end up easily with 10+ more observers for ~5 notifications.
With this commit the internal observer class becomes a singleton.
This means there is now only one observer for all status bar icons
and additional binder calls on new notification are avoided.
See "dumpsys content"
Change-Id: I8c11b165b34b87e7363a8e96524ea70fe6b28342
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds some more informations about Dual-Carrier HSPAP
It allows displaying a "DC" icon on status bar for compatible devices
and add a "DCHSPAP" value in state phone
patch 1: add TelephonyManager to fix build
patch 2: modify ServiceState
patch 3: switch to cm_strings
patch 4: fix a mistake
patch 5: upload a new set of icons, a bit prettier than previous
patch 6: update icons (more opacity to match colors)
patch 7: removed drawable-sw*
here is a screenshot for example: http://imgur.com/mQ2du3l,PSyHoqC
Change-Id: I77d05e23c8ad3efdfeb19cf06ed92e7c57105ebe
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After the pie service commits, sound effects were broken for
HOME and BACK keys.
This commit fixes this, by moving the play back of the sound
effect from the injection directly to the onClick().
Change-Id: Id59848ccddac20cef80500f6e72d76afa97ae093
|
|/
|
|
|
|
|
|
| |
This commit reverts an error, introduced by the second pie
service commit, which causes the positions where the snap points
gets displayed to be inverted.
Change-Id: Iedaf6d4773c9ae45fb685d724fad6c35ecdeddf0
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Since the navbar now has updateResources(), there is no need to reinflate
it upon a theme change.
Change-Id: Ie4753a767a1cb45eb459ee692d16067f83cc7d23
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|
|
|
|
|
|
|
|
|
|
| |
if scaled size of the PIE is over or under the default size
the pie was either no using the whole screen space or
it was cutted off. To solve this take scale value
into account when calculating estimated width
greetings SlimRoms
Change-Id: Iccfc8362c0019e3b6ff4bd8066c313c67116c014
|
|
|
|
|
|
|
|
|
|
|
| |
The small dialog also deserves the chance to get updated
resources.
Thank you Jiangyi, for finding that one.
Patch Set 2: Unbreak things
Change-Id: I6e9de7c35abff52c2fcc2952771bb42b406496ed
|
|
|
|
|
|
|
| |
ContentObserver and BroadcastReceiver instances were dangling after the
status bar was recreated.
Change-Id: I0ef7ef134029e5deec066d405545b8d9ec58d76b
|
|
|
|
|
|
|
|
|
|
| |
QuickContact popup can only be used for phoning/messaging/emailing,
which doesn't make sense when you're opening your own contact.
Opening the full contact directly makes it easier to beam or share
with other (one less click)
Change-Id: I6b6002fd7ecccaf16f1e410c0c863989bf877711
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
part 1/2: frameworks/base PowerUI and Settings
http://review.cyanogenmod.org/#/c/35241/
part 2/2: packages/apps/Settings Sound settings
http://review.cyanogenmod.org/#/c/35242/
patchset 3:
shrink a couple of long lines
remove power_notifications_use_default option (folded into ringtone option)
load default settings in global instead of system
patchset 5:
support vibrate toggle
ignore first power state change (on boot) if it's a DISCONNECT
patchset 6:
fix ignore first power state change
patchset 7:
change vibrate to default to off
simplify first power state change ignore logic
Change-Id: I36a6b9f924d2cd52191a8e83a744745b37c5b068
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For QuickSettings and Power Widget check if there is
ConnectivityManager.TYPE_MOBILE network avaialbe directly instead of relying
on a checking for the PackageManager.FEATURE_TELEPHONY permission. Some
devices like tilapia (Nexus 7 GSM) has mobile data but does not set the
telephony permission.
Patchset 2:
- Use ConnectivityManager.isNetworkSupported() instead of checking for a null
value returned from ConnectivityManager.getNetworkInfo(). Thanks
- Have MobileNetworkTile use the QSUtil deviceSupportsMobileData method
Change-Id: I71bd6217cbe08622f805de4ae30a87df11340f5f
Fixes: CYAN-803
|
|
|
|
|
|
|
| |
Removed unnecessary references to QuickSettingsContainerView, LayoutInflater
Tile layout is set by constructor
Change-Id: Ied57bf6613594864db0201c2af514fbe4bb651ed
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ContentObservers are being registered without being unregistered,
causing old objects not to be garbage collected. This causes memory
leak if the classes are destroyed and recreated throughout the
device's uptime.
SearchPanelView is recreated every time the screen is turned on.
StatusBarIconView is created every time a notification is triggered.
JIRA: CYAN-650
Change-Id: Iabd3221fc2b0c848396af1790fd09424be602e7e
|
|
|
|
|
|
|
|
|
|
| |
Many media files and source code files were marked as executable in Git.
Remove those.
Also a shell script and python script were not marked as executable.
Change-Id: Ieb51bafb46c895a21d2e83696f5a901ba752b2c5
Signed-off-by: Chirayu Desai <cdesai@cyanogenmod.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit brings the navigation bar long press behaviour to
pie controls.
Two things will be considered for long press:
* Long press on HOME will open Google Now.
* Long press on BACK will kill an application if enabled within
the debug options.
Patch Set #2:
* Jacob's colours
Patch Set #3:
* More blueish colours
* Using a longer time out for long press
(getLongPressTimeout() * 2)
* Moved killForegroundAppication() around
Patch Set #5:
* Shortened long press time out a bit
* Adjust time for info shade dynamically
Change-Id: I8cfa87a5be0678f0452011d85d427439d7cf31e9
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
User feedback showed that it is sometimes difficult to interact
with pie controls. This commit adds some tweaks to how pie
controls react on user touch events.
This changes:
* Pie trigger on LEFT and RIGHT are now more forgiving in the
initial phase of a swipe. (This should reduce problems when
trying to activate the pie with a thumb.)
* Pie items are now more sloppy when it comes to focus.
Patch Set #2:
* Removed sloppy focus.
Change-Id: Ib21556ed7f7ff9c6cdbcd1760e94a17c8534706a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Patch Set 1: initial commit
* Patch Set 2: change tile title
* Patch Set 3: change tile title again
* Patch Set 4: updated to suggested drawable by blunden
* Patch Set 5: update drawables to fit to the bahavior of
the other icons used in QS
* Patch Set 6: rebase
only display tile if feature is enabled
* Patch Set 7: launch the proper long press activity
* Patch Set 8: correctly hide tiles if ED or profiles are turned off
style fixes
Change-Id: I2273f8f0bdb726ec34f00a6fb205b1bc6e795cfa
|
|/
|
|
|
|
|
|
|
|
| |
Add a dinamic tile for devices with dock battery
Patchset 2: New icon set
Rebased
Change-Id: I5e0e84da0b0f248fa9eb568c5d506b00cf3998b0
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
if 2 events have the same timestamp then FlingTracker in PanelView will divide
by zero causing NaNs. the bug is usually triggered by rapid StatusBar up/down
dragging activity and updateCarrierLabelVisibility can then loop indefinitely
looking at NaNs. the user visible symptom is that StatusBar refuses to pull
down and is burning cpu time.
Signed-off-by: Michael Bestas <mikeioannina@gmail.com>
Change-Id: I0791c6bea953bf03346185fc6aaf44aaea79aace
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|