| cf388c2eec17fe3d1ade1f97d9d702a6574ae4d0 |
16-May-2018 |
Christine Franks <christyfranks@google.com> |
Initialize color mode if set
ColorDisplayService doesn't start listening for changes until the end
of user setup, and color mode was previously unintialized at service
setup, so restored settings were ignored.
Bug: 79591550
Test: atest FrameworksServicesTest:ColorDisplayServiceTest
Change-Id: I00baed15e1248572d3dfd8f251dee7dc5a355a6c
olorDisplayServiceTest.java
|
| 2b326bfd9288141343cbe6f8d998a7536994af33 |
18-Apr-2018 |
Kenny Guy <kennyguy@google.com> |
Record timestamp when brightness tracker is called
Associate the brightness slider event timestamp with
the time the tracker is called rather than when
the background handler handles the call.
Bug: 78224086
Test: atest BrightnessTrackerTest
Change-Id: I083fdcc10f223ab7398911d9cb63dca5d8681fc4
rightnessTrackerTest.java
|
| 02fea072ab9390eb263128eea540964a646e72a0 |
11-Apr-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Added gamma correction tests." into pi-dev
|
| c8a6db8c1070a2e970083a93ac2de916608536d9 |
03-Apr-2018 |
Dan Gittik <dangittik@google.com> |
Added gamma correction tests.
Test: atest BrightnessMappingStrategy
Fixes: 77578319
Change-Id: Ic8a693a71cf8de14fb5bfdf0325f3aefe537438d
rightnessMappingStrategyTest.java
|
| 122df868919f3e2b9a92d6e9dc66808884f3f080 |
28-Mar-2018 |
Dan Gittik <dangittik@google.com> |
Added system-wide minimum brightness curve.
The minimum brightness curve guarantess that any brightness curve
that dips below it is rejected by the system.
This prevent auto-brightness from setting the screen so dark as to
prevent the user from resetting or disabling it, and maps lux to
the absolute minimum nits that are still readable in that ambient
brightness.
Test: atest BrightnessConfigurationTest.
Fixes: 77176207
Change-Id: Ibd1e83e9b147f3849d6c907f828cbe5950c8367f
isplayManagerServiceTest.java
|
| 637f8be6b6156b2dbcdccca4e9408b180ed1e7c5 |
03-Apr-2018 |
Kenny Guy <kennyguy@google.com> |
Avoid null pointer when in getAmbientBrightnessStats
Check whether the tracker has been started before
trying to return stats.
Add unit test to check empty lists are returned
rather than null.
Bug: 76008231
Test: atest BrightnessTrackerTest
Change-Id: Icc7ef0ee43a95eb182cb1b0b9452f122363e67ba
rightnessTrackerTest.java
|
| e5cd25ec0a11784ef9b13b6ea99f32036a64ee8f |
28-Mar-2018 |
Artem Iglikov <artikz@google.com> |
Revert "Added safeguards for pushed brighntess curve."
This reverts commit f1e673649e11b98f537489b7889f1d6efa6e7ff9.
Reason for revert: crashes system server
Bug: 77176207
Change-Id: I574e6e1f60d83f14701a643a1c7b8f7ef8659ed5
rightnessMappingStrategyTest.java
|
| f1e673649e11b98f537489b7889f1d6efa6e7ff9 |
23-Mar-2018 |
Dan Gittik <dangittik@google.com> |
Added safeguards for pushed brighntess curve.
Currently, the only safeguard is making sure the brightness curve isn't too dark to turn
auto-brightness off (or connect the phone to a computer and reset the curve with ADB).
Test: atest BrightnessMappingStrategyTest.
Change-Id: Ic87292fe51639a0001d0d5643ca24cda37de5753
Fixes: 74439069
rightnessMappingStrategyTest.java
|
| 96fd5d9ed2f5ff2d2944e843144d7f467fa8af7b |
21-Mar-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Unregister lux sensor when not in adaptive mode." into pi-dev
|
| 3d7172c9d436d90cb4d859c7888b69b066728289 |
19-Mar-2018 |
Kenny Guy <kennyguy@google.com> |
Unregister lux sensor when not in adaptive mode.
Unregister the lux sensor used to track
user slider events and ambient brightness
stats when user is in manual mode.
Test: atest BrightnessTrackerTest
Bug: 73231445
Change-Id: Ie389956bd85794ac9428e7904c501773a968102c
rightnessTrackerTest.java
|
| ae606b44578419b70fdc346525905778528fb7f6 |
16-Feb-2018 |
Robert Carr <racarr@google.com> |
Eliminate usage of global transaction for display configuration.
For seamless rotation to work in the brave new world we need the setting
of the display projection to occur in the same transaction as the
reconfiguration of the stack SurfaceControl. To understand this simply see
that the inverse rotation for seamless rotation happens at the
WindowStateAnimator level so if the stack bounds weren't updated to the new
rotation we would clip. This means: We need to use the pending transaction.
We also need to port the rotation animation to use the pending transaction
as it needs to perform transactions at the same time as setting the display
projection. A pleasant consequence is we can eliminate some "inTransaction"
code-paths that always seemed to be a bit of a wart.
Bug: 72038766
Test: Manual. go/wm-smoke.
Change-Id: I949fbe8150d452c1ef5c13e704ddf87269f824f3
isplayManagerServiceTest.java
|
| 6c90d8a7ecbd8ebb3ce87e59f5930a8c09ec157f |
20-Feb-2018 |
Kenny Guy <kennyguy@google.com> |
Include slider events from managed profile.
Include the slider events from profiles of the
requested user however redact the package name
from the event.
Bug: 72484845
Test: atest BrightnessTrackerTest
Test: atest BrightnessTest
Change-Id: I4a7d02c93646581982102f01bd9f237d849b87d9
rightnessTrackerTest.java
|
| 9d3986bdc3b9fe5a85a54bf6a4f787e198eade40 |
01-Feb-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Add Ambient Brightness tracker API"
|
| cc155ddc69efce0579118e873ae991cebc083ca6 |
10-Jan-2018 |
Peeyush Agarwal <apeeyush@google.com> |
Add Ambient Brightness tracker API
Test: atest com.android.server.display.AmbientBrightnessStatsTrackerTest
&& atest android.hardware.display.AmbientBrightnessDayStatsTest
Bug: 69406079
Change-Id: I4b13c6bdd3e9fdded8086371f46dba0fd3102b98
mbientBrightnessStatsTrackerTest.java
rightnessTrackerTest.java
|
| 53d0661f38d6ada39aefaac5ce016f802e74bd44 |
30-Jan-2018 |
Kenny Guy <kennyguy@google.com> |
Add information about brightness config to slider events.
Whether the config is using the default curve.
Whether the config has a user data point.
Whether the config has a power save offset.
Bug: 72482479
Test: atest BrightnessTrackerTest
Change-Id: I137a919ae2604244b0b2f78e00e31b7a72df4967
rightnessTrackerTest.java
|
| d846023804ddadcd692666152db420c54594ddb9 |
16-Jan-2018 |
Michael Wright <michaelwr@google.com> |
Slider always represents absolute brightness
Currently the slider represents a gamma adjustment to the brightness
curve when auto brightness is enabled and the absolute screen brightness
when it's not. This is a fairly confusing behavior to most people, so
this consolidates them to a single behavior: the slider always
represents the current brightness and auto-brightness will automatically
adjust it.
This also moves a bunch of the brightness methods from PowerManager over
to DisplayManager, since it's really the DisplayPowerController that's
responsible for determining and setting the display brightness.
Test: atest com.android.server.display.BrightnessMappingStrategyTest
Bug: 69406898
Change-Id: I73b5982809a94cd50d563426a72d7965e923c994
rightnessMappingStrategyTest.java
|
| 0ae08d0ca6ed7af8828e43a06f65d58e2dcf7c83 |
22-Jan-2018 |
Kenny Guy <kennyguy@google.com> |
Accept null brightness configs.
Use null brightness config as reverting
to OEM supplied curve.
Test: atest PersistentDataStoreTest
Bug: 72083823
Change-Id: Ibb0cd70c07035e85a5512b831b5bf6bcec0c5993
ersistentDataStoreTest.java
|
| 05ce809b82b3846516560b0232691d08389898f2 |
17-Jan-2018 |
Kenny Guy <kennyguy@google.com> |
Add more brightness config details to dumpsys
Allow client to add a description to a brightness
config and dump to dumpsys
Dump time and package name of system app that
set the last brightness config.
Bug: 71854421
Test: atest PersistentDataStoreTest
Test: manaual - check adb shell dumpsys display
Change-Id: I5ff0c0d3a4c5e30c9d4aa7eea850c7174ee20450
ersistentDataStoreTest.java
|
| 0ff4489cc5429b306b21ba00076b097412de9ac1 |
10-Jan-2018 |
Kenny Guy <kennyguy@google.com> |
Tag brightness APIs with @SystemAPI
Make the API for tracking brightness
slider events and setting brightness
curves @SystemAPI and @TestAPI
Add developement scope to the brightness
slider events permission to allow cts
testing.
Bug: 69405990
Test: atest android.permission2.cts.PermissionPolicyTest#testPlatformPermissionPolicyUnaltered
Test: atest BrightnessTrackerTest
Change-Id: I39b0b26454528425b62cf99dc8bbccded4e14a18
rightnessTrackerTest.java
|
| d5df361ae1bc7e6cd8b171585b59b86e327ef46e |
02-Jan-2018 |
Michael Wright <michaelwr@google.com> |
Clean-up brightness configuration.
Remove unused default config since that's now stored in the mapping
strategy and eliminate erroneous error logging on devices that don't
support brightness configurations.
Fixes: 71527790
Test: atest com.android.server.display.BrightnessMappingStrategyTest
Change-Id: I9b2eeb5270200af8b59e4374e1afc9fd9447a73f
rightnessMappingStrategyTest.java
|
| 144aac9dfeb4e3f48af874b438a84261202affe1 |
21-Dec-2017 |
Michael Wright <michaelwr@google.com> |
Track brightness changes in nits rather than backlight values.
For the moment, the only one that actually knows the true brightness
value is the DisplayPowerController, so have that tell the
BrightnessTracker directly when brightness changes.
Bug: 69405990
Test: atest com.android.server.display.BrightnessTrackerTest
atest com.android.server.display.BrightnessMappingStrategyTest
Change-Id: Ibf4e501ce2f7b071360bfac501dbbafb3ba55fa5
rightnessMappingStrategyTest.java
rightnessTrackerTest.java
|
| eef0e13f018f33bf3db2f8311bbb429369e13394 |
21-Nov-2017 |
Michael Wright <michaelwr@google.com> |
Add an API for setting a new brightness curve.
In addition, this also provides multiple strategies for mapping from
ambient room brightness in lux to display brightness. The default one is
the classic strategy, where we map directly from lux to backlight
brightness in an arbitrary unit. The newer and preferred strategy is to
use the physical brightness of the display, but requires that the
brightness properties of the display are appropriately configured.
Bug: 69406783
Test: atest com.android.server.display.BrightnessMappingStrategyTest &&
atest android.hardware.display.BrightnessConfigurationTest &&
atest android.hardware.display.PersistentDataStoreTeset
Change-Id: I60227bdb6c299d0fa92686cbf3e5994b336a3a79
rightnessMappingStrategyTest.java
ersistentDataStoreTest.java
|
| 29aa30e56c0e0ffb3f4a91c4212bb9c5d7eb9d03 |
30-Nov-2017 |
Kenny Guy <kennyguy@google.com> |
Limit access to package names in brightness slider data.
Only allow access to package names if the calling package
has PACKAGE_USAGE_STATS.
Bug: 69405990
Test: runtest -c com.android.server.display.BrightnessTrackerTest frameworks-services
Change-Id: I1c924d408a7c74620b9aa9d672c99a6424bb85ca
rightnessTrackerTest.java
|
| 689ab8fa03462f183c33439dd83fadbd989d48ea |
29-Nov-2017 |
Kenny Guy <kennyguy@google.com> |
Don't keep sensor listener while screen is off.
Register / unregister on screen off / on intents.
Bug: 69564178
Test: runtest -c com.android.server.display.BrightnessTrackerTest frameworks-service
Test: manual, turn on/off screen and check adb shell dumpsys sensorservice
Change-Id: I7bfb6b35108887baf40d9134d16d13a9f5aa839f
rightnessTrackerTest.java
|
| e99bc0501a288735d337f2ff64f8fa47f766a59b |
20-Nov-2017 |
Adrian Roos <roosa@google.com> |
WM: Move WindowManagerPolicy, DisplayFrames and WindowManagerInternal into services
Splits WindowManagerPolicy into a framework and a services part, preventing concepts that are
internal to the window manager from leaking out into the framework.
Test: make droid
Change-Id: I7b6a54f55f76f6fbb5f27090981b8f1d4d8be88b
isplayManagerServiceTest.java
|
| cfe7b70e99467069c813449a1792958906dffbb3 |
14-Nov-2017 |
Kenny Guy <kennyguy@google.com> |
Daily idle job for writing out brightness events.
Schedule a job for idle + charging to kick off
writing out brighness slider events.
While writing events discard ones outside our
time window.
Bug: 69405990
Test: Manual using adb to kick off job.
Test: runtest -c com.android.server.display.BrightnessTrackerTest frameworks-services
Change-Id: Ibc79d1c80ced26827d6f985bc70ae165df106a42
rightnessTrackerTest.java
|
| 22bd044b0c9af7643a5c3092f080a5b942a67720 |
26-Oct-2017 |
Kenny Guy <kennyguy@google.com> |
New class to track brightness slider interactions.
Provides system apps with access to the users
brightness slider interactions and context from
when the brightness level was changed.
Test: runtest -c com.android.server.display.BrightnessTrackerTest frameworks-services
Change-Id: Ibdb3c78cb1d11887cb38b24c30754ff2e6f3bda8
rightnessTrackerTest.java
|
| c22c56397636729b3717c3935816b88dc72fac26 |
22-Jun-2017 |
Santos Cordon <santoscordon@google.com> |
Always run Virtual Display when in a BootsToVR device.
This CL:
1) Moved initialization of the virtual display adapter to happen along
side the default display. On standalone VR devices, a virtual display
is used as the main display for 2D UI so it is necessary that the virtual
display system is ready after PHASE_WAIT_FOR_DEFAULT_DISPLAY.
2) Add knowledge of bootsToVr in Vr2dDisplay, indicating that the device
is a standalone device that boots into VR. This forces Vr2dDisplay to
create the virtualDisplay at PHASE_SYSTEM_SERVICES_READY and never
destroy it (so that the activity stack doesn't go away).
3) Add tests to ensure default display and virtual display startup
sequence doesn't change.
Change-Id: Ie748771abd0b115db3c65a66a4b7a98dd1b28f2e
Bug:62842592
Test: Start a polaris device for first time, ensure SUW runs with
Virtual display dimentions.
Test: DisplayManagerServiceTest.java
isplayManagerServiceTest.java
|
| 879d24f4237f5c9c6def64087845578513711386 |
21-Jun-2017 |
Alex Sakhartchouk <alexst@google.com> |
Allow VR Virtual display to rotate with content.
VR Virtual display was getting letterboxing for apps that
had a fixed orientation in the manifest.
Bug: 62670868
Test: Run orientation locked app, observe requested orientation in VR
testCreateVirtualDisplayRotatesWithContent to verify propagation.
Change-Id: I10eb4f6e54404aa7b66471ab5dc929a4baa49432
isplayManagerServiceTest.java
|
| ee8931e258c07410b2affd6d5e8b9239b170c504 |
05-Apr-2017 |
Santos Cordon <santoscordon@google.com> |
Add uniqueId to Virtual Display and pass through to inputflinger (1/2)
This CL adds:
1) Adds uniqueId (protected via system/sig permission) to virtual
displays.
2) Add support for N virtual display viewports into inputflinger.
3) Set the virtual display's viewports in inputflinger if it has the
uniqueId value set to non-null. (a) Moving the new viewport from java to
native inputflinger and (b) adding "uniqueId" value to viewports makes
up the great majority of this change.
4) From the inputflinger side, we also read in a new value from the
input device configuration files called 'touch.displayId'.
5) When touch.displayId and the virtual display's uniqueId match,
inputflinger links the two.
Test: Start VR and ensure that the virtual viewport shows up when running
'adb shell dump input". Run a VR app, and ensure that the virtual input
device is associated with the new virtual viewport.
Test: com.android.server.display.DisplayManagerServiceTest
Bug: 36051620
Change-Id: Ic2117eb8e19f7f3c59687160591f8bc6692c1f12
isplayManagerServiceTest.java
|