* changes:
Turn down the logging a little bit.
Turn down the logging a little bit and don't do a log wrapper function.
Turn down the logging a little bit.
Turn down the logging a little bit.
Turn down the logging a little bit.
Turn down the logging a little bit.
Turn down the logging a little bit.
Add the public interface for starting/stopping PNO scan.
This is the internal flow that is going to be used for PNO scan:
1. Set Pno list
2. Start background scan
This flow will not work as is for supplicant, since background scan is
done manually today. So, we'll need a flag to indicate that this
background scan is targetted for PNO.
BUG: 27167559
Change-Id: I3f6921c5d03f7d9e8ad1847e57e12fb38df6c9c9
TEST: Compiles & unit-test passes
This reverts commit 24e46045956da911b385be33cff473bdacebf780.
Un-hiding this for continued development in nyc-dev.
Based on conversations between those at higher paygrades, we'll either leave this visible or re-hide prior to next dev release.
Change-Id: I235eb0f593daa7b34ea10ed4c9df4eaa6c68078c
- This guarantees that they won’t collide, where as the override task
progresses will as tasks animate while dragging to dismiss.
Change-Id: I25eded22c13b38428d849062c6d95893f3fff5c5
- Use new dynamic black level result key when available
- Write rational black level instead of integral value
- Fix incorrect thumbnail BitsPerSample metadata
- Fix incorrect date/time format string
- Fix unknown orientation
Test: dng_validate for captured DNGs is clean
Bug: 27452979
Bug: 25862995
Change-Id: I87b73f7a4f4ecc3cf6498c7db16df68dd0b0b43a
Propagate setVisible calls to current drawable. Take window visibility
into account when determining drawable visibility.
Bug 27461595
Change-Id: Ia1de1d1686f26c2cf27630c5bde70f23c2c332bd
Do not merge because the resource implementation has changed in N and
the change is no longer valid there.
This is a very hacky fix to make layoutlib work with the latest support
lib. Inject a couple of fields in android.content.res.Resources to
allow using most of the earlier code as is.
Bug: 27403642
Bug: http://b.android.com/201934
Change-Id: I186cad32b1b4de64164fbad937d989e0110c6976
Also includes a regenerated test-current.txt.
bug: 27426688
(cherry picked from commit 7d18ce744fff219ab60470ec095d585b854b91e1)
Change-Id: I754803d51d365ac1fe26c638b12efb88d23b35c6
Includes generated changes for test-current.txt.
bug: 27426688
(cherry picked from commit de33c660df4a6ff8a138e3033c9e1d446bd6b570)
Change-Id: Idd323fe7458a2b124aae0009b4de83039e2ade21
The main purpose is to fix the security flaw that
user can force isDeviceOwnerProvisioningAllowed to return true
by setting the device_provisioned without factory reset
Check UserSetupComplete instead, as it's cached by DPMS if it's ever set to true
Refactor common code of isDeviceOwnerProvisioningAllowed and enforceCanSetDeviceOwnerLocked
The functionality of enforceCanSetDeviceOwnerLocked should be exactly the same.
DPM Unit Test all pass
Bug:27403225
Change-Id: I32dae8e222e01e08664abb313ead3a92d4186658
