| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| | |
camera." into lmp-mr1-dev
automerge: 701d816
* commit '701d8166550e1ddfd62bd82b7ea0f6a91c75a699':
Avoid crashing on startup when policy forbids lockscreen camera.
|
| |\
| | |
| | |
| | | |
into lmp-mr1-dev
|
| | |
| | |
| | |
| | |
| | | |
Bug: 19554426
Change-Id: I5b2898d7d114de87d925b5eccc8e4b189e4713de
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
automerge: d3c532e
* commit 'd3c532ef254881fc5bfac198651c9032f8108db9':
MediaProjectionPermissionActivity: Fix NPE.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Avoid dismissing a null dialog.
Bug: 19492919
Change-Id: I6642bb5194d9818ff3db1266c7c78ed752e23ecf
(cherry picked from commit 3d332f4e67a484abe597576bf329d89655afe720)
|
|/ /
| |
| |
| |
| | |
bug:19416574
Change-Id: I55cedd2a3e1c1c3192ece860f37c82a55cb6d7c0
|
|/
|
|
|
|
|
|
|
| |
The keyguard needs to show either 'emergency calls only' or 'no service'
depending on whether there is service available, so try to pull this from
the old sticky broadcast containing plmn/spn.
Bug: 19476978
Change-Id: I83523cc4c7dd5f46bd97df2cc9ecdb38d1c2e001
|
|
|
|
|
| |
Bug: 19434845
Change-Id: I28be1d8efb61d47abdce168b07a0846056eb650d
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The notification_stack_scroller view of the new uber statusbar should
not be focusable for accessibility
Fixes bug 19296202
Change-Id: I1b3f43ee3c480c705044cb3d565c7c7f7019bcc3
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
An OutputStream buffers only by explicit contract. OutputStreamWriter
buffers internally, always. Do not get these behaviors confused.
Bug 19341967
Change-Id: I0610ed625b0175620083dd286f3a73c24956b171
|
|/
|
|
|
|
|
|
|
|
| |
Also removes the Klondike from the content description.
This reverts commit c199ef37594b946cb295c29df321e74332ee5408
from change I3dd05fa1714da36795f448718fd70f1cdbfe2584
Bug: 18528774
Change-Id: I8a85076f939a8b78075b5a6322009ebfd78bf8d3
|
|
|
|
|
|
|
|
|
|
|
| |
The root view of the new uber statusbar should not be focusable.
Based on history, it looks like this was an oversight when this view
was refactored.
Fixes bug 19296202
Change-Id: Ib7f6908c30ab37384aa50f4fa4198c15593a96a4
|
|
|
|
|
|
|
| |
Remove the trailing pulse @ 2 minutes, and only allow 2 schedule resets.
Bug: 19330195
Change-Id: I492581c081fafd2a1e5e09f7cce08d7a14da6d6b
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Also creates a TextView-like accessibility node
and populates accessibility events with text if
required.
Bug: 18528774
Change-Id: I4a918a092b1e97879c31f54604cf957e01f4bc86
|
|/
|
|
|
| |
Bug: 19250277
Change-Id: I881b08ebc6900ba43289b772ed0d039dbb62149c
|
|
|
|
|
| |
Bug: 19262637
Change-Id: I395125a7c00e558e914aff9cf9c48a363435a9b2
|
|
|
|
|
| |
Bug: 18996476
Change-Id: I0e402aa198263807e3013c7fb151f28d049ea51a
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bluetooth tile was not announcing its state when the top half was
clicked. This is because if handleUpdateState was triggered on
the view before it became dual then it would not get all of the dual
accessibility information. So if the dual state changes on a tile
make sure to call handleUpdateState so it can be handled appropriately.
Bug: 19155633
Change-Id: Ifd053c67d8ddd3230086517c9d479069556e8b56
|
|/
|
|
|
|
|
|
| |
Use the same mechanism as the two finger gesture to get it to open
correctly.
Bug: 19196800
Change-Id: I952e14d3ccd796889ed54cb98c017542a25f28c9
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't assume the pickup sensor will perform a proximity check before
starting to pulse. This will add some latency, but necessary if
we can't trust the sensor.
Bug: 19083596
Change-Id: I51b7daf5ed76b2780ec5c949a75cc1fca247ddad
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Encryption is required when using 'adb backup' on encrypted devices,
but the UI has not been enforcing this. The failure mode is quite
confusing: the user can tap "back up my data" with no encryption
phrase supplied, and the confirmation activity disappears, but
the backup doesn't actually happen.
We now disallow confirming the backup unless a non-empty passphrase
has been entered into the UI.
In addition, tapping "do not back up my data" now finishes
the confirmation activity instead of just leaving it in a
confusing "dead" state.
Bug 19081192
Change-Id: I9ca69a08ff4322fe25129f9ca880b066c31525d0
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Ensure that we always show the data icon in both Quick Settings and
the status bar, or in neither, but never one or the other.
The particular inconsistency this is intended to fix is that in some
circumstances, Wi-Fi may be connected, but the cell radio may be still
be used by certain apps, due to new multinetworking APIs in L. In this
case, we should always show the data icon; currently appears in the
status bar, but not Quick Settings, which was unconditionally dropping
the icon if any Wi-Fi connection was up.
Bug: 19112322
Change-Id: I9942f6b24081e061a72804ef47ad4fe719f32ec2
|
|/ /
| |
| |
| |
| |
| | |
bug:19120603
Change-Id: Id33c77696a47ef48b0095fd8289f92d7bba71f19
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A clicked notification is not guaranteed to be removed,
so instead of dropping a clicked HUN notification we have
to release it to the shade.
Bug: 19093631
Change-Id: I73b88af774e49e89c8a601873c48cc5f5eed0224
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QSDualTileLabel is no longer a FrameLayout (now a LinearLayout),
so it does not need the top padding based on the caret size
anymore.
Bug: 18725348
Change-Id: Ibd3aaa20e7cdb35ba585cc5c8981c64efb5c66fe
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use startSettingsActivity (QSTileHost) to make sure we use the right flags
and get the keyguard out of the way so the user always sees the
connect dialog for secure networks when they are sent to settings.
Bug: 18987307
Change-Id: I9027393ab8743e6dfe702221cb3bc1bb4e213708
|
|\ \ \ \
| |/ / /
|/| | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Only run if entitlement is needed and tethering is running.
bug:18356505
Change-Id: Ifc50189bf573e4575f747975edcce093c4870356
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It turns out that sysUI visibility / interactivity is racing with
boot, and it's possible in some circumstances for the user to start
the secure camera swipe gesture before formal boot-completed. Make
sure we only send the camera-related broadcast to registered
receivers in that case, otherwise we'll implicitly be asking to
launch other apps before boot, which is forbidden.
Bug 19060618
Change-Id: I7fcf13b5af7b2edfbb4aac06ef04a0fde2c6a0f7
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Change-Id: Ib02415ea924e876ae776b34ed271dcae2b9afbb1
Auto-generated-cl: translation import
|
|\ \ \ \
| |/ / /
|/| | |
| | | | |
dismiss Recents. (Bug 18802531)" into lmp-mr1-dev
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Recents. (Bug 18802531)
We can use our normal visibility check to dismiss Recents when the screen is off,
since the system broadcast can occur after the activity is stopped. We should use
the same mechanism we use to test visibility when launching Recents and just see
if it is the top most activity.
Change-Id: Ib9c01e78fd9221c4fb0ffcc80a01a0c58fb96836
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
Release SurfaceTexture after use in ColorFade and delete GL resources
in ImageWallpaper.
Bug: 17871993
Change-Id: I05bda03657ca502ba35b7187b6f361018f7ef687
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Log the following lockscreen gestures:
* Swipe up to unlock
* Swipe down to enter full shade
* Tap in empty area (causing unlock hint)
* Swipe to camera
* Swipe to dialer
* Tap on lock to lock device
* Tap on notification, activating it
For swipe gestures, includes length and velocity where available.
Bug: 18767135
Change-Id: Ib2c535e3a9d2b378f5a2a0a00c2be3fd916554ac
|
|\ \ \
| | | |
| | | |
| | | | |
lmp-mr1-dev
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
onSubscriptionInfoChanged gets called quite frequently whenever
something about the connectivity changes, which could lead that the
whole state of the Keyguard was reset. This change actually checks
whether the state has really changed and thus only resets Keyguard
when necessary.
Bug: 18821582
Change-Id: Ia70804d0337b11914c7d57aa4cdc47d585786f1d
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Logs the following keyguard and status bar states to
eventlog:
* statusBarState
* keyguardShowing
* keyguardOccluded
* bouncerShowing
* secure
* currentlyInsecure
Bug: 18767135
Change-Id: If27a9340dd1b5ec609f9940d9e0f32bd7aed1ed2
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
|