| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: Ia2234c77193b64d5ff569215bd3c321ae452ef0c
Auto-generated-cl: translation import
|
|\ |
|
| |
| |
| |
| |
| | |
Change-Id: If91f4a3f2755a7f76cab09c6f3fafe09575c8e23
Auto-generated-cl: translation import
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Change-Id: Ied34352ea4e79b01a9b8549596a381fe08ee7e06
Auto-generated-cl: translation import
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
the notification shade is open." into jb-mr1-dev
* commit '7ee2f9d90e4e3b0926c4f4866652867920f057ef':
hide the redundant clock when the notification shade is open.
|
| |\ \
| | | |
| | | |
| | | | |
jb-mr1-dev
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 7204705
Change-Id: I88ef58938c5e96c4828dbda5d93f9874535b212f
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
raw query()s of moved-to-global keys" into jb-mr1-dev
* commit 'e827b3642f2dc9dd983b5513cd76e77c2da36db7':
Rewrite raw insert()s and some raw query()s of moved-to-global keys
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
into jb-mr1-dev
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The Settings put*() APIs fix up references via the old namespaces,
but the raw insert() interface didn't. Now it does. Also, when
possible we fix up direct query() operations on the old namespace
to point to the correct one. At present that is only done for
query() operations with Uris of the form
content://secure/adb_enabled
There is no rewriting done on queries of the form
content://secure WHERE name='adb_enabled'
since the app-supplied WHERE clause can be arbitrarily complex.
Bug 7267568
Change-Id: I5c8cecbea7f5b1da6247a53b1428d3effb0bbca5
|
|\ \ \ \ \
| |/ / / /
| | | | /
| |_|_|/
|/| | |
| | | |
| | | | |
registerContentObserver()" into jb-mr1-dev
* commit '5acd58a758ad9bb93d59d9d6f1dbe9f516096e3a':
Use myUserId() only in registerContentObserver()
|
| |\ \ \ |
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The reason for this is a bit subtle: we want to guarantee that
when a content observer is registered using the public API, it
is *always* bound to the host user's view of the data behind the
observed Uri, never the calling user's. Now, the reason it was
the calling user in the first place is that the Settings provider
(and potentially any singleton provider) needs the observers
underlying Cursors returned from query() to be tied to the caller's
user, not the provider's host user.
In order to accomplish that now that the public-facing behavior is
always tied to the host user, the concrete class that implements
the Cursor type handled by the Settings provider has been extended
with a new hidden API for setting a notification observer tied to
an arbitrary user; and then the provider explicitly downcasts the
query result's Cursor to that class in order to register the
notification observer. We can do this safely because this is platform
code; if we change the way that these underlying cursors are constructed,
we can just fix this point of call to follow along. If they get out
of sync in the future, the Settings provider will scream bloody
murder in the log and throw a crashing exception.
Bug 7231549
Change-Id: I0aaceebb8b4108c56f8b9964ca7f9e698ddd91c8
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
panels..." into jb-mr1-dev
* commit '0923060dc33fc78221823b26d28189e5839c48d0':
Fix a bug in double-swiping panels...
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
...that could cause them both to be shown at once.
Bug: 7179458
Change-Id: I32e51bd6d4f5773d0f4f5d3e99a84d299cd4b766
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
for ringer mode" into jb-mr1-dev
* commit '98845ef5ec995dd03f9039954eaf1bc1e747e086':
fix settings data base upgrade for ringer mode
|
| |\ \ \ \ |
|
| | | |/ /
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Ringer mode setting was moved from System to Global group
but a db upgrade cleanup step was missing.
Bug 7128886.
Change-Id: Id20994fe74575afa2b68154a620aa3c8807e8304
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
changes from jb-dev to jb-mr1-dev" into jb-mr1-dev
* commit '9f6cf431169b49e5f49e727843d2972a9bad69f0':
Port unmerged notification changes from jb-dev to jb-mr1-dev
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug 7150006
Single finger notification expansion.
If you liked these changes...
Change Ie4e79aa5
Change I8a6f8606
Change I824937e9
Change I957b6d50
You'll love this one!
Conflicts:
packages/SystemUI/res/values/config.xml
packages/SystemUI/res/values/dimens.xml
Fix notification gestures.
Broken by recent changes to ScaleGestureDetector, which we
were using incorrectly.
Conflicts:
packages/SystemUI/res/values/config.xml
packages/SystemUI/res/values/dimens.xml
Change-Id: Ie534c5b2d320296531a36a9b1c22f9dd6901e0b8
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
threshold for status bar flings." into jb-mr1-dev
* commit '55ae7beb228198d14d679f7082bbe2fda471be46':
Increase the anti-jitter threshold for status bar flings.
|
| |\ \ \
| | |/ /
| | | |
| | | | |
jb-mr1-dev
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
You must move the panel at least 20dp overall, or at a speed
of 150dp/sec or more (actually quite easy; most normal
flings are 500dp/s or more) for it to be considered a fling.
Bug: 7179458
Change-Id: Ic1f4edc641cd2aa1cde89b2ee02eefdf5a0cc044
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
connected state." into jb-mr1-dev
* commit '91490e933629b32d43c8bb512ab404e361f61bba':
change string for wifi not connected state.
|
| |\ \ \
| | | |/
| | |/| |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 7217026
Change-Id: I8b593b85fe32f37880ee1a0b3ef869b36e80ba5b
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
work in the new multi-user world" into jb-mr1-dev
* commit '11ebeae0b555942389b576d7275964618a40d992':
Make settings backup/restore work in the new multi-user world
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
jb-mr1-dev
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
1) Properly handle restores of settings elements that have been migrated
to the new global namespace
1) Back up and restore the new global settings namespace
3) Make sure to back up / restore the global entity
ENABLE_ACCESSIBILITY_GLOBAL_GESTURE_ENABLED
Bug 7249405
Change-Id: Ibfa9930ea4d0e16c7635697e8c631b155e4c0cb2
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
jb-mr1-dev
* commit 'dacd3ebe8d504d92735ceb85e0940cb1eb60cc99':
Panel physics changes.
|
| |\ \ \ \
| | | |_|/
| | |/| | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- You can start pulling down another panel before the first
one has fully expanded. (Protip: tap many times on the
statusbar to invoke Schwarzenegger Mode.)
- When starting to pull down a panel, other panels are
immediately sent running (rather than placing them on a
literal seesaw).
- Rubberbanding is a little less aggressive: if it looks
like you're moving your finger upward, we'll just close
the panel outright rather than sticking to the bottom of
the visible content. (tablets only)
- This has some implications for the background fade; you'll
see a brief increase in brightness as you swap panels
because the fade fraction is based on the sum of all the
panels' fractional visibility. At times there will not be
enough "panel" visible, in the aggregate, to justify
holding the fade steady.
Bug: 7260868 // can't pull down panel, possibly fixed
Bug: 7204435 // double-swipe for QS
Bug: 7179458 // fling & rubberbanding heuristics
Bug: 7172453 // collapse other panels when dragging a new one
Bug: 7221970 // grabbing a flying panel causes twitching
Change-Id: Iad7c1f92c4edab9102cdda45605ef0ead4cc16c5
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 4736039f3347675796a4d7e589584da3d1af275e
Change-Id: Ie271f9a3872578cea458389a5ba7ccaf93beff29
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
consistent with other quicksettings icons." into jb-mr1-dev
* commit '310430c73df90931c7c3c00698003db3ce21c064':
make bluetooth iconography consistent with other quicksettings icons.
|
| |\ \ \ \ \
| | | |_|_|/
| | |/| | |
| | | | | | |
icons." into jb-mr1-dev
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 7217026
Change-Id: I880ee26e1d92ffa49885cf53b8dbab6b13887423
|
| |\ \ \ \ \
| | | |/ / /
| | |/| | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: I40d09593fab0006cbe483fae9267ca93148a215b
Auto-generated-cl: translation import
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
gesture tracking." into jb-mr1-dev
* commit 'e004899bf80839e29bb2c9112701dd3565a40af2':
Disable statusbar pulldown gesture tracking.
|
| |\ \ \ \ \ \
| | |/ / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
jb-mr1-dev
* commit 'd14508f8c483f1b5c14e8f25b43ad5714b445e28':
Disable statusbar pulldown gesture tracking.
|
| | |\ \ \ \ \
| | | | |_|/ /
| | | |/| | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Bug: 7164602
Change-Id: Ie6569a7a8a9f462e844ef3088098c3256653f630
|
| |\ \ \ \ \ \
| | |/ / / / /
| |/| | | | | |
|
| | | |/ / /
| | |/| | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: I2ec20472e935fa6fe02d715424b1e89d8ff90f52
Auto-generated-cl: translation import
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
on background." into jb-mr1-dev
* commit 'ede625ac6544d68a1d3018a3c34a256f2a4b5d11':
Allow QS to be closed via drag on background.
|
| |\ \ \ \ \ |
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This was already working fine for the area of the panel
below the ScrollView, but intuitively it seems that dragging
in the unused portion of a partially-filled row would behave
the same way. Because it's part of the scrolling content,
though, drags in that region are (correctly) interpreted by
the ScrollView as scrolling requests.
The new QuickSettingsScrollView works around this by
ignoring touch events if its contents are too small to be
scrolled. So in the common case (QS tiles on a phone) you
will be able to drag in any empty area and have your taps
interpreted by the PanelView (which hands them off to the
handle to collapse the view).
We don't handle drags in empty areas when there are too many
tiles to show on-screen, and really, it's impossible to do
so: this gesture should then definitely be interpreted as a
scroll.
Bug: 7203193
Change-Id: I4cfcb029481a88d3604c7105185e8bcb7dbde8a5
|