Added descriptio about preferred way to close camera faster.
Test: build (doc only update)
Bug: 175104220
Change-Id: I750b57afab65b4e77fff6ef79ec64dcebe74e47f
This change adds the simple getters and setters for the state of the
toggles. The persisted xml format is backwards compatible so no
migration is needed.
Test: None for new state
Verify old sensor mute works the same
Bug: 162549680
Change-Id: I6a1ef9c703cc5d175c1a5f788a3559eabf0054ad
Store CEC version for each device. Defaults to HDMI CEC 1.4b.
Bug: 174732339
Test: make; atest HdmiDeviceInfoTest
Change-Id: I97c962d58b16ddfab9010a1738670a107e12481f
This is so that regular apps don't get to know when camera devices
are opened / closed (as oppsed to being available / unavailable), in addition to not knowing the
package names of the processes that open / close the devices.
Bug: 147710835
Bug: 170870941
Test: builds
Test: atest CameraManagerTest#testCameraManagerListenerCallbacks
Change-Id: I5cad3cb5dd70775d74c5be20d7adf434fd37bfa7
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
Bug: 174932174
Test: I solemnly swear I tested this conflict resolution.
Exempt-From-Owner-Approval: refactoring with team leads buy-in
Change-Id: I9262a08ffc1ccede8e519d0eed90ed2bfcf0232c
As general background, OWNERS files expedite code reviews by helping
code authors quickly find relevant reviewers, and they also ensure
that stakeholders are involved in code changes in their areas.
Some teams under frameworks/base/ have been using OWNERS files
successfully for many years, and we're ready to expand them to cover
more areas. Here's the historical coverage statistics for the last
two years of changes before these new OWNERS changes land:
-- 56% of changes are fully covered by OWNERS
-- 17% of changes are partially covered by OWNERS
-- 25% of changes have no OWNERS coverage
Working closely with team leads, we've now identified clear OWNERS on
a per-package basis, and we're using "include" directives whenever
possible to to simplify future maintenance. With this extensive
effort, we've now improved our coverage as follows:
-- 98% of changes are fully covered by OWNERS
-- 1% of changes are partially covered by OWNERS
-- 1% of changes have no OWNERS coverage
This specific change is automatically generated by a script that
identifies relevant "include" directives.
Bug: 174932174
Test: manual
Exempt-From-Owner-Approval: refactoring with team leads buy-in
Merged-In: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813
Change-Id: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813
As general background, OWNERS files expedite code reviews by helping
code authors quickly find relevant reviewers, and they also ensure
that stakeholders are involved in code changes in their areas.
Some teams under frameworks/base/ have been using OWNERS files
successfully for many years, and we're ready to expand them to cover
more areas. Here's the historical coverage statistics for the last
two years of changes before these new OWNERS changes land:
-- 56% of changes are fully covered by OWNERS
-- 17% of changes are partially covered by OWNERS
-- 25% of changes have no OWNERS coverage
Working closely with team leads, we've now identified clear OWNERS on
a per-package basis, and we're using "include" directives whenever
possible to to simplify future maintenance. With this extensive
effort, we've now improved our coverage as follows:
-- 98% of changes are fully covered by OWNERS
-- 1% of changes are partially covered by OWNERS
-- 1% of changes have no OWNERS coverage
This specific change is automatically generated by a script from
detailed ownership information confirmed by team leads.
Bug: 174932174
Test: manual
Exempt-From-Owner-Approval: refactoring with team leads buy-in
Merged-In: I9789c97c1de8e5d962b48c29c57d82fe83729eba
Change-Id: I9789c97c1de8e5d962b48c29c57d82fe83729eba
* changes:
Hand-migration to TypedXml interface.
Mechanically apply TypedXml refaster template.
Mechanical refactoring to new typed XML classes.
Additional hand-migration to TypedXml interface.
"Resolve" both human-readable and binary XML.
We need to figure out whether any apps are using FLAG_SLIPPERY. Ideally,
we should lock this down and only allow it for system uses. Add a change
id for this logging here.
Bug: 157929241
Test: adb shell dumpsys platform_compat
Change-Id: I7a12828e768a145054d31fbf07f130a2f06735de
Updated the name to better represent the usage of this setting.
The values of the constants remain the same to ensure compatibility.
Bug: 169145038
Test: atest HdmiCecLocalDevicePlaybackTest
Change-Id: Ieba3d94d5db52d39f717b525a8b8ed6e6587b132
Some Int Def annotations were marked with `flag=true` by mistake.
This commit will remove the definition so that the flag
will be marked as false by default.
Bug: 174239412
Test: full build pass
Change-Id: I32328d76699e396c53dfc62768b2cd24ab48cabd
Previous changes have applied mechanical refactorings, but this change
hand-migrates the remaining logic which was too complex to identify.
This change should have no behavior change; famous last words.
Bug: 171832118
Test: manual
Exempt-From-Owner-Approval: trivial refactoring
Change-Id: I85cd830eb6bfde18fca6e73ee7adfdc385a890de
